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

Please help. Asterisk 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:

Here’s a screenshot from our DID provider:

Any help appreciated, flabbergasted by this

You may find more useful help on a FreePBX support site.

Here, all that matters is the packets.

What packets are you sending and what packets are you receiving?

Give me 30 seconds and I’ll take a packet capture…

so… I mean yeah, this is obviously the problem:

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 dont understand why it’s failing to register. Can you point me in the right direction?

Trace the INVITE request not the REGISTER request, and assuming your provider require you need to be registered to allow you to call out, verify your SIP credentials,

You’re only looking at part of the process.

The ‘401 Unauthorized’ is just the first step in the authorization dance. It’s a ‘challenge/response’ kind of thing. Note the ‘200 OK.’

I’m just a lowly ‘chan SIP’ guy, but ‘sip show registry’ (or the PJSIP equivalent) should show ‘Registered.’

As noted above, you should look at INVITEs. REGISTER tells your provider where you are. INVITE is the start of a call.

Personally, I like to use ‘sudo tcpdump -i any -n -s 0 -w call-issue.pcap port 5060’ to capture packets and ‘sngrep -I call-issue.pcap’ as my ‘secret decoder ring.’ The Asterisk console log with SIP debugging enabled can be useful as well. I just really like the way sngrep groups all the packets in a dialog and displays ladder diagrams. Comparing packets to identify differences can be a big help where needed.

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.