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.
-
@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
-
@samsmart84 said in FreePBX inbound call issue:
@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
umm, ok.. /me racks brain cells
So first, shut off iptables and see if the problem goes away.
service iptables stopYour system if not direct ont he internet right? So this should be safe enough for a short term test.
-
@jaredbusch said in FreePBX inbound call issue:
@samsmart84 said in FreePBX inbound call issue:
@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
umm, ok.. /me racks brain cells
So first, shut off iptables and see if the problem goes away.
service iptables stopYour system if not direct ont he internet right? So this should be safe enough for a short term test.
No it is not direct so should be safe. Issue remains after shutting off iptables
-
@samsmart84 said in FreePBX inbound call issue:
@jaredbusch said in FreePBX inbound call issue:
@samsmart84 said in FreePBX inbound call issue:
@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
umm, ok.. /me racks brain cells
So first, shut off iptables and see if the problem goes away.
service iptables stopYour system if not direct ont he internet right? So this should be safe enough for a short term test.
No it is not direct so should be safe. Issue remains after shutting off iptables
Well that points back to your routing which is the root cause of this circle jerk.
Because in 2.8, the only firewalling was
iptables.If that is not running, but you are not seeing anything hit the PBX, then it is like the call is not making to it.
-
I am trying to think where else to look, but not getting anywhere.
-
@jaredbusch said in FreePBX inbound call issue:
I am trying to think where else to look, but not getting anywhere.
Yeah it's just so odd.. I can't wrap my head around why the SIP trunk IP changing would break inbound. On the old router config there was literally no reference to the actual SIP trunk IP or anything else I could see that would be affecting it
-
@samsmart84 Maybe this Sophos KB article will help?
-
@triple9 said in FreePBX inbound call issue:
@samsmart84 Maybe this Sophos KB article will help?
Success! So basically some trial and error with the settings.. I had to turn OFF the Sophos VOIP options as that was actually BLOCKING everything (Go figure). I had made the DNAT rule listed in that link before but didn't have any success - the auto firewall rules with it didn't work evidently. Running the DNAT mixed with creating manual firewall rules for outbound calling and it all seems to be working. I've been testing for about an hour - when I turn the DNAT off it stops working and when it's on it works just fine so I think we've got the right combo at this point.
Thanks for all your help everyone! That was a pain in the butt to track down.
-
@samsmart84 said in FreePBX inbound call issue:
@triple9 said in FreePBX inbound call issue:
@samsmart84 Maybe this Sophos KB article will help?
Success! So basically some trial and error with the settings.. I had to turn OFF the Sophos VOIP options as that was actually BLOCKING everything (Go figure).
That’s actually expected. That’s SIP-ALG. Always have to disable that. It’s basically just SIP blocking.
