Weird Network Errors on SIP Trunks, FreePBX
-
FreePBX 14 system. Can't make outbound calls, but inbound are fine. Nothing changed on the PBX end. Was working for a while then suddenly stopped making outbounds. Should be dialing to an IPv4 address for the carrier, but we get this instead. Have tried multiple SIP Trunk providers, similar problems with all of them.
/etc/resolv.conf is set to Google addresses as primary and secondary.
WARNING[3736]: acl.c:974 ast_ouraddrfor: Cannot connect to 2607:fb90:7dcb:97f1:90d0:eadb:c6a2:6b57: Network is unreachableAnyone seen something like this before.
-
@scottalanmiller said in Weird Network Errors on SIP Trunks, FreePBX:
FreePBX 14 system. Can't make outbound calls, but inbound are fine. Nothing changed on the PBX end. Was working for a while then suddenly stopped making outbounds. Should be dialing to an IPv4 address for the carrier, but we get this instead. Have tried multiple SIP Trunk providers, similar problems with all of them.
/etc/resolv.conf is set to Google addresses as primary and secondary.
WARNING[3736]: acl.c:974 ast_ouraddrfor: Cannot connect to 2607:fb90:7dcb:97f1:90d0:eadb:c6a2:6b57: Network is unreachableAnyone seen something like this before.
Does the system can ping IpV6? looks like an T Mobile IPv6
-
That's being generated by the client somehow.
-
A totally different end point calling out the same number gets this...
res_pjsip_sdp_rtp.c:397 set_caps: No joint capabilities for 'video' media stream between our configuration((h264)) and incoming SDP((vp8)) -
Looks like we are getting...
Dial failed for some reason with DIALSTATUS = CONGESTION and HANGUPCAUSE -
Are the clients registering properly? I believe that has been the issue a lot of times even on FreePBX 12.
Also check if NAT configuration is setup properly.
-
@dbeato said in Weird Network Errors on SIP Trunks, FreePBX:
Are the clients registering properly? I believe that has been the issue a lot of times even on FreePBX 12.
Also check if NAT configuration is setup properly.
Yes and they can call internally no problem. And inbound calls work fine. So no issues with the SIP and points.
-
No NAT involved where the problem is. Server has a public IP address.
-
So the issue is that we are getting detection congestion, but I have no idea from where.
-
@scottalanmiller said in Weird Network Errors on SIP Trunks, FreePBX:
So the issue is that we are getting detection congestion, but I have no idea from where.
Yikes.
-
@dbeato said in Weird Network Errors on SIP Trunks, FreePBX:
@scottalanmiller said in Weird Network Errors on SIP Trunks, FreePBX:
So the issue is that we are getting detection congestion, but I have no idea from where.
Yikes.
Yeah
-
Sounds like you don't have enough outbound bandwidth
-
@crustachio said in Weird Network Errors on SIP Trunks, FreePBX:
Sounds like you don't have enough outbound bandwidth
We've got a Gig.
-
@scottalanmiller said in Weird Network Errors on SIP Trunks, FreePBX:
Dial failed for some reason with DIALSTATUS = CONGESTION and HANGUPCAUSE
Found someone recently with same problem here:
http://forum.issabel.org/d/1079-llamadas-entrantes-funcionan-y-salientes-no -
@scottalanmiller said in Weird Network Errors on SIP Trunks, FreePBX:
@crustachio said in Weird Network Errors on SIP Trunks, FreePBX:
Sounds like you don't have enough outbound bandwidth
We've got a Gig.
I was being Curtis.
-
-
Looks like it was a combination of factors. Calls started working during the night after two days of not working. From what we can tell.... four of our trunks were down because of a vendor-side congestion problem. So nothing we did changed anything. We just kept trying new things to no avail. But it just "started working" sometime this morning. Seems fine now.
The fifth trunk was failing coincidentally because of some failure to top up automatically and also started "just working" once the top up went through.
Everything was working this morning after sleeping on it.
-
@scottalanmiller said in Weird Network Errors on SIP Trunks, FreePBX:
Looks like it was a combination of factors. Calls started working during the night after two days of not working. From what we can tell.... four of our trunks were down because of a vendor-side congestion problem. So nothing we did changed anything. We just kept trying new things to no avail. But it just "started working" sometime this morning. Seems fine now.
The fifth trunk was failing coincidentally because of some failure to top up automatically and also started "just working" once the top up went through.
Everything was working this morning after sleeping on it.
Uck.
-
@scottalanmiller said in Weird Network Errors on SIP Trunks, FreePBX:
ter two days of not working. From what we can tell.... four of our trunks were down because of a vendor-side congestion problem. So nothing we did changed anything. We just kept trying new things to no avail. But it just "started working" sometime this morn
Yikes. I hate those types of "resolutions." From the post tags, I assume this was VoicePulse?
-
@scottalanmiller said in Weird Network Errors on SIP Trunks, FreePBX:
Looks like it was a combination of factors. Calls started working during the night after two days of not working. From what we can tell.... four of our trunks were down because of a vendor-side congestion problem. So nothing we did changed anything. We just kept trying new things to no avail. But it just "started working" sometime this morning. Seems fine now.
The fifth trunk was failing coincidentally because of some failure to top up automatically and also started "just working" once the top up went through.
Everything was working this morning after sleeping on it.
I dislike VoicePulse. I had a client with them and ended up porting everything to VoIP.ms 3 years ago.
