Allworx Technical Support Forum

I recently took over an IT consulting client and am tasked with also maintaining their Allworx system. It's been pretty straightforward and easy to work with. Though the other day I moved the Allworx system behind a Cisco ASA and changed the Networking settings (set to Lan and changed WAN and LAN IP). Calls still come in and can be placed, but the PFK's flash an amber color, and the Call Monitor that they're associated with no longer works. The routing works, I can route to specific extensions but when I change the route back to the Call Monitor none of the handsets ring.

Thanks for the help,
Andrew in Chicago

Well I figured out my problem
When changing things around we moved the Allworx WAN side to 192.168.41.0/24 and the LAN side to192.168.40.0/24 but the phones were pulling from DHCP which was configured with 192.168.40.0/23. I read on here that the PFK's broadcast on 2088 which led me the realization that the conflict probably had to do with broadcasts and the subnet. Manually assigning the handsets to 192.168.40.0/24 resolved the issue.

Make sure only one device is doing DHCP. either the allworx or the router. It is easier for the allworx phones if the Allworx is doing DHCP. otherwise you
need to set a boot ip address on each phone or option 66 on the router DHCP (if supported).

In LAN host mode the WAN port should not be connected on the allworx and must be a unique subnet that is not in use either in your internal or external network.

It was the unique subnet that caused an issue. One was unique (255.255.255.0) but the other (255.255.254.0) covered both IP scopes. The phones have been assigned static IP's for now. One of these days when I have more time I'll look into configuring the switches so the Allworx can provide DHCP on VLAN 2, but for now assigning static IP's ans subnets fixed the issue.