cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
2020
Views
0
Helpful
2
Replies

SPA112 hangs after long qualify delays with Asterisk

syncrotechnology
Beginner
Beginner

New unit with latest firmware (1.2.1).  SPA112 qualify response times are usually between 48-60 ms (my polycom phones are 5-6).  After some number of hours, it suddenly won't respond to the once a minute asterisk qualify and returns very long response times ( > 2 sec) causing asterisk to de-register it.  And we're dead.  Asterisk log from Saturday afternoon - nobody working, network very quiet.  Extensions 401/402 are the SPA.

Oct 20 13:31:41] VERBOSE[24353] pbx.c:   == Spawn extension (from-trunk-xo, #########, 13) exited non-zero on 'SIP/xo-1-000002dc'

[Oct 20 16:02:17] NOTICE[5014] chan_sip.c: Peer '402' is now Lagged. (2184ms / 2000ms)

[Oct 20 16:02:27] NOTICE[5014] chan_sip.c: Peer '402' is now Reachable. (14ms / 2000ms)

[Oct 20 16:03:20] NOTICE[5014] chan_sip.c: Peer '401' is now UNREACHABLE!  Last qualify: 1853

[Oct 20 16:03:31] NOTICE[5014] chan_sip.c: Peer '402' is now UNREACHABLE!  Last qualify: 14

[Oct 20 16:03:41] NOTICE[5014] chan_sip.c: Peer '402' is now Reachable. (706ms / 2000ms)

[Oct 20 16:04:16] NOTICE[5014] chan_sip.c: Peer '401' is now UNREACHABLE!  Last qualify: 3457

[Oct 20 16:04:45] NOTICE[5014] chan_sip.c: Peer '402' is now UNREACHABLE!  Last qualify: 706

[Oct 20 16:18:54] VERBOSE[5014] netsock.c:   == Using SIP RTP TOS bits 184

[Oct 20 16:18:54] VERBOSE[5014] netsock.c:   == Using SIP RTP CoS mark 5

[Oct 20 16:18:54] VERBOSE[15305] pbx.c:     -- Executing [########@from-trunk-xo:1] NoOp("SIP/xo-1-000002dd", "Entering from-trunk-xo, DID: 2##########") in new stack

I read the earlier discussion on this and see that it has been noted and possibly "fixed" in the latest firmware but not that I can tell.  Long ping times suggest the linux box is very busy or running out of memory or both.  I had to reboot this immediately this AM so no chance to look at the logs but I will watch for any clues next time.

This appears to be a common problem - any guidance, Cisco?

2 Replies 2

syncrotechnology
Beginner
Beginner

Ok, got some more data on this issue:

It hung again this afternoon.  Would not ping, could not use the web interface, it just hosed.  Syslog was running and the SPA112 spit out these two lines before it jumped off the cliff:


Wed Oct 24 15:47:16 2012 10.10.1.10 <29>Oct 24 15:47:16 SPA112 msgswitchd[1385]:   MSGSWD RTCP Reqt len 12 Data 2,1092717788,2629110,0

Wed Oct 24 15:47:16 2012 10.10.1.10 <29>Oct 24 15:47:16 SPA112 msgswitchd[1385]:   MSGSWD RTCP Reqt len 12 Data 2,2874904,7312,0

Those were its last words, so to speak.  The asterisk logs were not helpful, just normal activity right up to where it was unreachable.  Problem is I can't reboot this remotely when it gets in this condition.  It requires a manual power cycle - this is not workable.

Cisco, you've been quiet - can you help here?

Could be related to https://supportforums.cisco.com/message/3781736#3781736

Patrick

----------

Getting Started

Find answers to your questions by entering keywords or phrases in the Search bar above. New here? Use these resources to familiarize yourself with the community:

Recognize Your Peers