FreePBX inbound call issue
-
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.
-
@samsmart84 said in FreePBX inbound call issue:
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.
We have great luck with Ubiquiti gear. Fraction of the cost of Sophos and I dare say, better quality.
-
@scottalanmiller said in FreePBX inbound call issue:
@samsmart84 said in FreePBX inbound call issue:
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.
We have great luck with Ubiquiti gear. Fraction of the cost of Sophos and I dare say, better quality.
I love Ubiquiti stuff. I built out our WiFi and our IP camera system using all Ubiquiti gear. Awesome quality and reliability for the cost.
-
I will say.. I like the Sophos box, but I hate the GUI and how "proprietary" everything feels. It's difficult to navigate and determine how to properly open ports, etc. for this to work. Still no outbound or inbound calling working.
-
So made some progress.. If I call OUT now to my cell my cell will see it. There is no ring from the internal phone and once connected there is zero audio. Still cannot call IN.
-
OKAY. So.. we are back to the original problem but I have fully migrated the PBX to the newer infrastructure PBX > Sophos UTM > Fiber vs PBX > Linksys router > Comcast Business Modem
I can call out, I have audio, but I can only call in for a short duration AFTER an outbound call is made.
-
@samsmart84 okay, so this confirms shit is just fucked up.
Ok. The hard part here is making sure you have no outbound calls.
Then when you make an inbound call monitor the CLI
asterisk -rvvvvvAnd then call in.
-
@samsmart84 said in FreePBX inbound call issue:
I will say.. I like the Sophos box, but I hate the GUI and how "proprietary" everything feels. It's difficult to navigate and determine how to properly open ports, etc. for this to work. Still no outbound or inbound calling working.
Check the price difference and see if you still like it
-
@jaredbusch said in FreePBX inbound call issue:
@samsmart84 okay, so this confirms shit is just fucked up.
Ok. The hard part here is making sure you have no outbound calls.
Then when you make an inbound call monitor the CLI
asterisk -rvvvvvAnd then call in.
I get nothing in the CLI for inbound calling when it fails. When I call out first then call in, stuff shows up obviously but not seeing anything that would indicate an issue (as far as I can tell)
-
@samsmart84 said in FreePBX inbound call issue:
@jaredbusch said in FreePBX inbound call issue:
@samsmart84 okay, so this confirms shit is just fucked up.
Ok. The hard part here is making sure you have no outbound calls.
Then when you make an inbound call monitor the CLI
asterisk -rvvvvvAnd then call in.
I get nothing in the CLI for inbound calling when it fails. When I call out first then call in, stuff shows up obviously but not seeing anything that would indicate an issue (as far as I can tell)
What version of FreePBX?
-
@jaredbusch said in FreePBX inbound call issue:
@samsmart84 said in FreePBX inbound call issue:
@jaredbusch said in FreePBX inbound call issue:
@samsmart84 okay, so this confirms shit is just fucked up.
Ok. The hard part here is making sure you have no outbound calls.
Then when you make an inbound call monitor the CLI
asterisk -rvvvvvAnd then call in.
I get nothing in the CLI for inbound calling when it fails. When I call out first then call in, stuff shows up obviously but not seeing anything that would indicate an issue (as far as I can tell)
What version of FreePBX?
Old. 2.8.1.5
-
I really need to just trash the whole thing and start with a setup that's actually modern/supported
