Changed local IP on PBX, can't call out or receive calls now
-
First time poster! Posted this on Spiceworks and was given advice from Scott Alan Miller to come here looking for some additional help
Local Elastix/FreePBX install. Currently the PBX connects to a WRT54GL running Tomato which then goes out to the WAN. Local IP was set to 192.168.0.0 network, switched to 192.168.3.0 and now I cannot call out/call in. Local phones CAN call each other. SIP Trunk Provider is Voxox and authentication is done through WAN IP, which has not changed. I've changed the 192.168.0.0 network to the 192.168.3.0 everywhere that I can think of - any device on the network can see the web, and I can ping my SIP provided IP, but still no communication.
Any ideas?
-
Do you have any firewall rules configured that are attempting to send the traffic to 192.168.0.0 instead of the new address of 192.168.3.0
Only thing I can think of off hand, as you've said internal calls are functional, but you're unable to call out / receive in calls.
Firewall rules would be where I would go digging.
-
Check your port forwarding rules on your WRTG54GL to make sure they forward to the new address.
-
I've checked the settings on both the WRT54GL and the FreePBX firewall. The WRT54GL only had some port forwarding rules for the 192.168.0.0 FreePBX host but those have been updated to match the new 192.168.3.0 address. I had an issue with the local GUI connections through the FreePBX firewall but someone assisted me in getting that switched to the 192.168.3.0 network so that should be good I hope.
I'm looking at the logs and I'm getting a "network is unreachable" error for my SIP provider IP when attempting to dial out and also "Dial failed for some reason with DIALSTATUS = CONGESTION and HANGUPCAUSE = 0"
When I call out, I get a few seconds of silence and then eventually an "all circuits are busy" message
-
Is it possible that your equipment needs to be restarted? The WRT54GL is an older unit, isn't it?
Have you tried restarting all components once these changes have been made?
-
I have tried restarting (both the router and the PBX box) and that hasn't changed anything. Oddly on my PBX status screen all of the indicators are green, including the SIP trunk connection.
-
@SamSmart84 said in Changed local IP on PBX, can't call out or receive calls now:
I'm looking at the logs and I'm getting a "network is unreachable" error for my SIP provider IP when attempting to dial out and also "Dial failed for some reason with DIALSTATUS = CONGESTION and HANGUPCAUSE = 0"
What logs are you looking at, are you able to provide those?
-
@SamSmart84 said in Changed local IP on PBX, can't call out or receive calls now:
I'm looking at the logs and I'm getting a "network is unreachable" error for my SIP provider IP when attempting to dial out and also "Dial failed for some reason with DIALSTATUS = CONGESTION and HANGUPCAUSE = 0"
When I call out, I get a few seconds of silence and then eventually an "all circuits are busy" message
That is a standard message that the call was not able to be completed because the trunk is not available.
-
Who is the provider? You SW thread said that there is no IP restriction place.
What version of FreePBX?
-
Unrelated to your actual question, but gods, throw that router away. Buy real equipment.
-
The SIP provider is Voxox (Telcentris). As for the router, this is step #1 in throwing it away. I run a Sophos firewall for our primary connection and getting the phones switched over and running through that will be the next step. I just need the inbound/outbound to work for now.
-
-
Upon some further investigating, the FreePBX box CANNOT ping the SIP Host, but the WRT54GL can talk both ways. The PBX box can see all other items on the 192.168.3.0 network, including the router.
-
I asked you what version of FreePBX it was?
-
2.8.1.5
-
what does
route -nshow on your freepbx box? -
Or more to the point can you ping anything on the internet?
-
cat /etc/sysconfig/network-scripts/ifcfg-eth0
and
cat /etc/sysconfig/network -
It shows the 192.168.3.0 for the Destination, the gateway was defaulted to 0.0.0.0. Just switched that to the router IP and it works now.
Gah.. knew it would be something simple. -
@SamSmart84 said in Changed local IP on PBX, can't call out or receive calls now:
It shows the 192.168.3.0 for the Destination, the gateway was defaulted to 0.0.0.0. Just switched that to the router IP and it works now.
Gah.. knew it would be something simple.- You did not do what you were told.
- I did not tell you to change anything.
- The gateway SHOULD be 0.0.0.0 for everything.
- Do what you are told, not what you think you should do.
