Help Troubleshooting All Circuits Busy to SPA112

I’ve got a Cisco SPA112 that has been configured and working for several months. Yesterday, it started to have issues. I can not dial out or receive calls through it. The SPA shows registered to FPBX and FPBX shows that the device is registered and “available.” When I try to dial out, I get “All circuits are busy” and when I call the SPA, I can see activity in the logs, but the phone never rings.

This is the registration I see in FPBX:

Endpoint: 300/300 Not in use 0 of inf
InAuth: 300-auth/300
Aor: 300 1
Contact: 300/sip:[email protected]:5061 39d1c4c4e2 Avail 23.406

This is what I see in the logs when I call the number connected to the SPA112:

324601 [2024-06-06 12:00:51] VERBOSE[2611] res_pjsip_logger.c: <— Transmitting SIP request (436 bytes) to UDP:192.168.1.180:5060 —>
324602 OPTIONS sip:[email protected]:5060;transport=udp SIP/2.0
324603 Via: SIP/2.0/UDP 192.168.1.43:5060;rport;branch=z9hG4bKPjb3a769f2-e5b0-47c7-b065-66be5c96f8ba
324604 From: sip:[email protected];tag=494754b4-3723-4b6a-b23c-fca24dc06978
324605 To: sip:[email protected]
324606 Contact: sip:[email protected]:5060
324607 Call-ID: f45952ce-d958-4e70-8457-73c70b7a6df9
324608 CSeq: 28510 OPTIONS
324609 Max-Forwards: 70
324610 User-Agent: FPBX-16.0.40.7(18.20.2)
324611 Content-Length: 0
324612
324613
324614 [2024-06-06 12:00:51] VERBOSE[2610] res_pjsip_logger.c: <— Received SIP response (1136 bytes) from UDP:192.168.1.180:49239 —>
324615 SIP/2.0 200 OK
324616 Via: SIP/2.0/UDP 192.168.1.43:5060;rport;branch=z9hG4bKPjb3a769f2-e5b0-47c7-b065-66be5c96f8ba
324617 From: sip:[email protected];tag=494754b4-3723-4b6a-b23c-fca24dc06978
324618 To: sip:[email protected];tag=0024c4be21e61da8cff51495-48d1f4fc
324619 Call-ID: f45952ce-d958-4e70-8457-73c70b7a6df9
324620 Date: Thu, 06 Jun 2024 17:00:43 GMT
324621 CSeq: 28510 OPTIONS
324622 Server: Cisco-CP7970G/8.5.2
324623 Allow: ACK,BYE,CANCEL,INVITE,NOTIFY,OPTIONS,REFER,REGISTER,UPDATE
324624 Allow-Events: kpml,dialog,refer
324625 Accept: application/sdp,multipart/mixed,multipart/alternative
324626 Accept-Encoding: identity
324627 Accept-Language: en
324628 Supported: replaces,join,norefersub,extended-refer,X-cisco-callinfo,X-cisco-serviceuri,X-cisco-escapecodes,X-cisco-service-control,X-cisco-srtp-fallback,X-cisco-monrec,X-cisco-config,X-cisco-sis-3.0.0
324629 Content-Length: 238
324630 Content-Type: application/sdp
324631 Content-Disposition: session;handling=optional
324632
324633 v=0
324634 o=Cisco-SIPUA 16597 0 IN IP4 192.168.1.180
324635 s=SIP Call
324636 t=0 0
324637 m=audio 0 RTP/AVP 0 8 18 101
324638 a=rtpmap:0 PCMU/8000
324639 a=rtpmap:8 PCMA/8000
324640 a=rtpmap:18 G729/8000
324641 a=fmtp:18 annexb=no
324642 a=rtpmap:101 telephone-event/8000
324643 a=fmtp:101 0-15
324644
324645 [2024-06-06 12:00:58] VERBOSE[2610] res_pjsip_logger.c: <— Received SIP request (768 bytes) from UDP:192.168.1.180:49193 —>
324646 REGISTER sip:192.168.1.43 SIP/2.0
324647 Via: SIP/2.0/UDP 192.168.1.180:5060;branch=z9hG4bK3e8a4c88
324648 From: sip:[email protected];tag=0024c4be21e61da9128c887b-48dad3ba
324649 To: sip:[email protected]
324650 Call-ID: [email protected]
324651 Max-Forwards: 70
324652 Date: Thu, 06 Jun 2024 17:00:50 GMT
324653 CSeq: 230901 REGISTER
324654 User-Agent: Cisco-CP7970G/8.5.2
324655 Contact: sip:[email protected]:5060;transport=udp;+sip.instance=“urn:uuid:00000000-0000-0000-0000-0024c4be21e6”;+u.sip!model.ccm.cisco.com=“30006”
324656 Supported: replaces,join,norefersub,extended-refer,X-cisco-callinfo,X-cisco-serviceuri,X-cisco-escapecodes,X-cisco-service-control,X-cisco-srtp-fallback,X-cisco-monrec,X-cisco-config,X-cisco-sis-3.0.0,X-cisco-xsi-7.0.1
324657 Content-Length: 0
324658 Expires: 60
324659
324660
324661 [2024-06-06 12:00:58] VERBOSE[2611] res_pjsip_logger.c: <— Transmitting SIP response (509 bytes) to UDP:192.168.1.180:5060 —>
324662 SIP/2.0 401 Unauthorized
324663 Via: SIP/2.0/UDP 192.168.1.180:5060;received=192.168.1.180;branch=z9hG4bK3e8a4c88
324664 Call-ID: [email protected]
324665 From: sip:[email protected];tag=0024c4be21e61da9128c887b-48dad3ba
324666 To: sip:[email protected];tag=z9hG4bK3e8a4c88
324667 CSeq: 230901 REGISTER
324668 WWW-Authenticate: Digest realm=“asterisk”,nonce=“1717693258/7fd390a3e2a0dd9aa08cafe9d4a9bef5”,opaque=“12c8c7fd37642547”,algorithm=MD5,qop=“auth”
324669 Server: FPBX-16.0.40.7(18.20.2)
324670 Content-Length: 0
324671
324672
324673 [2024-06-06 12:00:58] VERBOSE[2610] res_pjsip_logger.c: <— Received SIP request (1021 bytes) from UDP:192.168.1.180:49193 —>
324674 REGISTER sip:192.168.1.43 SIP/2.0
324675 Via: SIP/2.0/UDP 192.168.1.180:5060;branch=z9hG4bK99b3b506
324676 From: sip:[email protected];tag=0024c4be21e61da9128c887b-48dad3ba
324677 To: sip:[email protected]
324678 Call-ID: [email protected]
324679 Max-Forwards: 70
324680 Date: Thu, 06 Jun 2024 17:00:50 GMT
324681 CSeq: 230902 REGISTER
324682 User-Agent: Cisco-CP7970G/8.5.2
324683 Contact: sip:[email protected]:5060;transport=udp;+sip.instance=“urn:uuid:00000000-0000-0000-0000-0024c4be21e6”;+u.sip!model.ccm.cisco.com=“30006”
324684 Authorization: Digest username=“701”,realm=“asterisk”,uri=“sip:192.168.1.43”,response=“d9218fd0d2854176a2c6b170af48cb6b”,nonce=“1717693258/7fd390a3e2a0dd9aa08cafe9d4a9bef5”,opaque=“12c8c7fd37642547”,cnonce=“c263bc31”,qop=auth,nc=00000001,algorithm=MD5
324685 Supported: replaces,join,norefersub,extended-refer,X-cisco-callinfo,X-cisco-serviceuri,X-cisco-escapecodes,X-cisco-service-control,X-cisco-srtp-fallback,X-cisco-monrec,X-cisco-config,X-cisco-sis-3.0.0,X-cisco-xsi-7.0.1
324686 Content-Length: 0
324687 Expires: 60
324688
324689
324690 [2024-06-06 12:00:58] VERBOSE[2611] res_pjsip_logger.c: <— Transmitting SIP response (467 bytes) to UDP:192.168.1.180:5060 —>
324691 SIP/2.0 200 OK
324692 Via: SIP/2.0/UDP 192.168.1.180:5060;received=192.168.1.180;branch=z9hG4bK99b3b506
324693 Call-ID: [email protected]
324694 From: sip:[email protected];tag=0024c4be21e61da9128c887b-48dad3ba
324695 To: sip:[email protected];tag=z9hG4bK99b3b506
324696 CSeq: 230902 REGISTER
324697 Date: Thu, 06 Jun 2024 17:00:58 GMT
324698 Contact: sip:[email protected]:5060;transport=udp;expires=59
324699 Expires: 60
324700 Server: FPBX-16.0.40.7(18.20.2)
324701 Content-Length: 0

There are no SIP calls in that log. (Searching for “invite sip” finds no hits.)

Paste the Asterisk log (with pjsip logger on) for an incoming call to ext. 300 at pastebin.com and post the link here. Likewise for an attempted outgoing call from ext. 300.

These may each be several hundred lines.

Thanks for the guidance guys. I turned PJSIP logger on. Inbound test call log here.

Outbound log here

The inbound log contains no calls. The outbound log indeed shows a failing call, but it originated from a Poly VVX 500, with attempted routing to the FXO port on an OBi110, which was not registered or was misconfigured. No sign of an SPA112 anywhere.

And that is why we have logs. I was mistaken - the Obi was the device linked to the line, NOT the SPA112. The Obi had gotten knocked offline somehow. A reboot resolved the issue.

Thanks for you help. Out of curiosity to learn, what search terms did you use to find that in the logs?

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