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.
Posts made by SamSmart84
-
RE: Changed local IP on PBX, can't call out or receive calls now
-
RE: 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
-
RE: 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. -
RE: Changed local IP on PBX, can't call out or receive calls 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.
-
RE: Changed local IP on PBX, can't call out or receive calls now
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.
-
RE: Changed local IP on PBX, can't call out or receive calls now
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.
-
RE: Changed local IP on PBX, can't call out or receive calls now
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
-
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?