FreePBX inbound call issue
-
We would need a lot more detail to actually troubleshoot this.
But, I am very confident that you need to look at your firewall settings.
If you are changing IP addresses, then you are likely not using registration for trunk authentication.
You are likely using IP authentication. This means that your PBX is simply open to anything coming from that IP.
Your firewall probably doesn't know about this change. So nothing is being allowed in until you make an outbound call and then the IP is getting allowed for established/related connections.
-
@jaredbusch said in FreePBX inbound call issue:
@samsmart84 no clue, but likely your provider. If it was your firewall/NAT you should never get inbound calls.
I agree, provider is pretty likely. Maybe they have more than one entry for you in their system and four out of five times they are hitting the wrong IP address for you.
Are you registered with them as an IP or a hostname, perchance?
-
@jaredbusch said in FreePBX inbound call issue:
@samsmart84 said in FreePBX inbound call issue:
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)
Oh, that changes my answer. The problem is your firewall/NAT setup.
Or a registration one. What if registration is timing out, but calling out first is triggering the registration and if no calls are made it expires?
-
Assuming this is Asterisk (I think that was said) and that you are using chan_sip (since you said this is an older system, this seems safe), then maybe do...
asterisk -rAnd then do a ...
sip show peersAnd check the status of the trunks and see how they look when you call out. Then watch them with subsequent sip show peers to see if they change. If they deregister and then the incoming calls don't work, that's likely a registration issue. If not, more likely a firewall one.
-
Our provider uses our IP for authentication so no registration settings are configuring on the PBX side. They updated their IP configuration and sent us an email saying we needed to update it on our end. Once that was done, I let them know that the IP had been changed so they could remove the old IP from our config on their end. I've talked with them a little this morning and they have told me that everything is set correctly on their end.
-
Worth watching Asterisk and the firewall to see if when their calls fail on inbound if there is any traffic going to you whatsoever. If Asterisk sees it but has an issue, that means that we can rule out network issues or provider issues and it is something with the PBX. But my guess is that the call never gets to Asterisk at all.
-
For the firewall side, the PBX is just running through an old Linksys router/Cable modem setup. I've checked through the router and modem and can't find any references to the trunk IP, just the routes from our static IP to the internal PBX IP. What could I be missing there?
-
@samsmart84 said in FreePBX inbound call issue:
For the firewall side, the PBX is just running through an old Linksys router/Cable modem setup. I've checked through the router and modem and can't find any references to the trunk IP, just the routes from our static IP to the internal PBX IP. What could I be missing there?
Has it been rebooted since the change?
-
Yeah the router has been rebooted 2-3 times today. Trunk provider suggested that too - I've done reboots on it, the PBX and the gateway.
I did the "sip show peers" command and I only see the new IP in the list. Watched a call out and a call in (that worked right after) and everything looked in order as far I could tell.
-
@samsmart84 said in FreePBX inbound call issue:
For the firewall side, the PBX is just running through an old Linksys router/Cable modem setup. I've checked through the router and modem and can't find any references to the trunk IP, just the routes from our static IP to the internal PBX IP. What could I be missing there?
Unlikely that something is wrong there. It is possible that SIP-ALG is activated somewhere and causing an issue, but this would have been expected to have already been an issue before the change if this was the case.
We don't expect that the firewall is set up wrong, only that it might be "confused" for some reason. Try restarting it. But take a peek to see if any ALG settings are on in there, and definitely set up the STUN settings on your phones.
-
@samsmart84 said in FreePBX inbound call issue:
I did the "sip show peers" command and I only see the new IP in the list. Watched a call out and a call in (that worked right after) and everything looked in order as far I could tell.
It's watching it over time that might be telling.
-
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
-
That's a start. I'd check the firewall and see if it logs any traffic when a call comes in from the trunk provider.
-
-
Not my doing, on my list to upgrade/replace..
-
@samsmart84 said in FreePBX inbound call issue:
Not my doing, on my list to upgrade/replace..
Ubiquiti ER-L
$95, excellent quality.
-
Just noticed a line on Asterisk that says -
Got SIP Response 486 "Busy Here" back from <trunk IP>
-
@samsmart84 said in FreePBX inbound call issue:
Just noticed a line on Asterisk that says -
Got SIP Response 486 "Busy Here" back from <trunk IP>
Does that come up reliably when an incoming call has the problem that you mention?
-
@scottalanmiller said in FreePBX inbound call issue:
@samsmart84 said in FreePBX inbound call issue:
Just noticed a line on Asterisk that says -
Got SIP Response 486 "Busy Here" back from <trunk IP>
Does that come up reliably when an incoming call has the problem that you mention?
That's the first one I've seen go through.. underneath that it has a few lines stating everyone is busy/congested at this time, dial failed due to trunk reporting busy, etc.
Update: Looks like that was an outgoing call. Incoming calls are going through right now as people keep calling out, which fixes the issue for a bit as stated before.
-
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.
