Changed local IP on PBX, can't call out or receive calls now
-
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.
-
You should then have a single default gateway line with destination 0.0.0.0 and a gateway of your router.
Something like this.
root@pbx:~ $ route -n Kernel IP routing table Destination Gateway Genmask Flags Metric Ref Use Iface 10.254.0.0 0.0.0.0 255.255.255.0 U 0 0 0 eth0 10.254.1.0 0.0.0.0 255.255.255.0 U 0 0 0 zt0 169.254.0.0 0.0.0.0 255.255.0.0 U 1002 0 0 eth0 0.0.0.0 10.254.0.1 0.0.0.0 UG 0 0 0 eth0 root@pbx:~ $ -
I figured the IP change somehow defaulted that since switching it to the router is allowing calls in/out. However, it isn't letting me swap that back to 0.0.0.0, tells me I have a validation error. This is under Network Parameters in Elastix for the asterisk.pbx.com host
-
@SamSmart84 said in Changed local IP on PBX, can't call out or receive calls now:
I figured the IP change somehow defaulted that since switching it to the router is allowing calls in/out. However, it isn't letting me swap that back to 0.0.0.0, tells me I have a validation error. This is under Network Parameters in Elastix for the asterisk.pbx.com host
Elastix is not FreePBX. Details matter.............
-
Sorry, new to the VOIP thing. So the routing table you posted looks similar to mine. I do see the Destination 0.0.0.0 and the Gate 192.168.3.x address for the gateway. This is correct then? The 192.168.3.0 destination still shows 0.0.0.0 for the gateway.
