Everyone is busy/congested at this time - outbound calls failing


(Braelef) #1

Freepbx noob here. We had outbound calls working, and then all of a sudden we started getting this:

app_dial.c: Called PJSIP/9876541230@Livingston-Vitelity-543-210-4567
app_dial.c: Everyone is busy/congested at this time (1:0/0/1)
Executing [s@macro-dialout-trunk:34] NoOp("PJSIP/3325-00000061", "Dial failed for some reason with DIALSTATUS = CHANUNAVAIL and HANGUPCAUSE = 21") in new stack

On the line it says, “All circuits are busy. Please try again later.”

Here’s a screenshot of my Outbound Route settings:


(Lorne Gaetz) #2

This is not an outbound routes issue. From the tiny bit provided we can see the dial was attempted on the trunk, and the provided did not terminate the call.


(Braelef) #3

This is what I see in the packet capture.

21:19:49.255401 IP voip.justanexample.org.sip > 98.7.654.32.sip: SIP: REGISTER sip:inbound3.example.net:5060 SIP/2.0
21:19:49.255420 IP voip.justanexample.org.sip > 98.7.654.32.sip: SIP: REGISTER sip:inbound3.example.net:5060 SIP/2.0
21:19:49.275798 IP 98.7.654.32.sip > voip.justanexample.org.sip: SIP: SIP/2.0 100 Trying
21:19:49.275828 IP 98.7.654.32.sip > voip.justanexample.org.sip: SIP: SIP/2.0 401 Unauthorized
21:19:49.276079 IP 98.7.654.32.sip > voip.justanexample.org.sip: SIP: SIP/2.0 100 Trying
21:19:49.276089 IP 98.7.654.32.sip > voip.justanexample.org.sip: SIP: SIP/2.0 401 Unauthorized
21:19:49.276630 IP voip.justanexample.org.sip > 98.7.654.32.sip: SIP: REGISTER sip:inbound3.example.net:5060 SIP/2.0
21:19:49.276684 IP voip.justanexample.org.sip > 98.7.654.32.sip: SIP: REGISTER sip:inbound3.example.net:5060 SIP/2.0
21:19:49.297043 IP 98.7.654.32.sip > voip.justanexample.org.sip: SIP: SIP/2.0 100 Trying
21:19:49.297694 IP 98.7.654.32.sip > voip.justanexample.org.sip: SIP: SIP/2.0 200 OK
21:19:49.297910 IP 98.7.654.32.sip > voip.justanexample.org.sip: SIP: SIP/2.0 100 Trying
21:19:49.298786 IP 98.7.654.32.sip > voip.justanexample.org.sip: SIP: SIP/2.0 200 OK
21:19:49.559521 IP c-73-169-180-14.hsd1.wa.comcast.net.57345 > voip.justanexample.org.sip: SIP
21:19:50.280839 IP voip.justanexample.org.sip > 98.7.654.32.sip: SIP: REGISTER sip:inbound3.example.net:5060 SIP/2.0
21:19:50.301335 IP 98.7.654.32.sip > voip.justanexample.org.sip: SIP: SIP/2.0 100 Trying
21:19:50.301375 IP 98.7.654.32.sip > voip.justanexample.org.sip: SIP: SIP/2.0 401 Unauthorized
21:19:50.301954 IP voip.justanexample.org.sip > 98.7.654.32.sip: SIP: REGISTER sip:inbound3.example.net:5060 SIP/2.0
21:19:50.322276 IP 98.7.654.32.sip > voip.justanexample.org.sip: SIP: SIP/2.0 100 Trying
21:19:50.322839 IP 98.7.654.32.sip > voip.justanexample.org.sip: SIP: SIP/2.0 200 OK
21:19:51.316012 IP voip.justanexample.org.sip > 98.7.654.32.sip: SIP: REGISTER sip:inbound3.example.net:5060 SIP/2.0
21:19:51.336380 IP 98.7.654.32.sip > voip.justanexample.org.sip: SIP: SIP/2.0 100 Trying
21:19:51.336399 IP 98.7.654.32.sip > voip.justanexample.org.sip: SIP: SIP/2.0 401 Unauthorized
21:19:51.337046 IP voip.justanexample.org.sip > 98.7.654.32.sip: SIP: REGISTER sip:inbound3.example.net:5060 SIP/2.0
21:19:51.357388 IP 98.7.654.32.sip > voip.justanexample.org.sip: SIP: SIP/2.0 100 Trying
21:19:51.357762 IP 98.7.654.32.sip > voip.justanexample.org.sip: SIP: SIP/2.0 200 OK

I just don’t know enough to know why it could be failing to register.


(Ricardo) #4

Well one of the reason becomes from cause release code indicated on verbose as “call rejected” therefore you need to check with trunk provider support.
By the way on capture file it seems have trouble with registering SIP trunk it could presume all problem could becomes from the same reason, so you should see with your sip trunk services.
Good luck.


(Braelef) #5

Thanks for the info. I’ll check with them