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?

Reviving my thread -

Weirdest thing. We had a power failure/surge over the weekend which knocked down all my servers, switching, etc.

My phones have been working FLAWLESSLY since I last posted. But now, after getting everything back up and running, the SAME issue is back.. but the rules that fixed it before are still in place! Outgoing calling works (though it seems highly delayed now.. like 5-8 seconds after dialing a number for it to start ringing) but I CANNOT call in UNLESS I call out first, which fixes it for 2-3 minutes.

Once again, it's gotta be a firewall issue. This is stupid.

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

Also if you post the solution on Spiceworks as well I'll give you a best answer since you were responding on both

Hi all,

First off, I'm not super good with PBX stuff. We're using an older system which is soon to be upgraded. However, last week our trunk provider informed us that we needed to swap the IP for our inbound/outbound config. I did the swap (as far as I can tell the only place this IP is listed is under our PEER section for trunks and no other config settings were changed - just the new IP), called out and in and all seemed well. Here we are a few days later and my OUTBOUND calling works 100% of the time, however my INBOUND now works maybe 20% of the time - randomly. The rest of the time I get a busy signal when calling in. Trunk provider is literally zero help so... what could be causing this?

Update: Another oddity.. if I call OUT to someone, it appears to fix the ability to call IN for a short duration (5-10 mins)

Looks like when the call goes to a busy signal that it's indeed not hitting the PBX as I get zero incoming call info in Asterisk

I don't see any SIP and/or ALG type settings on the router. It's a Linksys WRT54G running Tomato 1.28

Just noticed a line on Asterisk that says -

Got SIP Response 486 "Busy Here" back from <trunk IP>

Alright I'm tired of dinking with this old equipment. My primary network is running on a Sophos SG 230 connected to fiber. No more Linksys, no more Comcast! If I'm going to fix this I might as well do it right.

So I messed with my SIP trunk settings and inbound calling changed from dead silence to a busy signal so it's definitely getting through the firewall.