[asterisk-bugs] [Asterisk 0013115]: could NOT get the channel lock

Asterisk Bug Tracker noreply at bugs.digium.com
Wed Sep 10 06:49:50 CDT 2008


A NOTE has been added to this issue. 
====================================================================== 
http://bugs.digium.com/view.php?id=13115 
====================================================================== 
Reported By:                pj
Assigned To:                
====================================================================== 
Project:                    Asterisk
Issue ID:                   13115
Category:                   Channels/chan_sip/General
Reproducibility:            random
Severity:                   major
Priority:                   normal
Status:                     acknowledged
Asterisk Version:           SVN 
SVN Branch (only for SVN checkouts, not tarball releases):  trunk 
SVN Revision (number only!): 132312 
Disclaimer on File?:        N/A 
Request Review:              
====================================================================== 
Date Submitted:             2008-07-20 07:13 CDT
Last Modified:              2008-09-10 06:49 CDT
====================================================================== 
Summary:                    could NOT get the channel lock
Description: 
Asterisk SVN-trunk-r132312 
I have lot of this error messages on CLI,
It seems, that it can be related to ilbc codec, because it happens mainly
when try to call echotest from xlite/eyebeam softphone with ilbc. 
When I tried same situation with gsm, it doesn't happened (or only
sporadically).


[Jul 20 14:13:17] ERROR[5827]: chan_sip.c:18837 handle_request_do: We
could NOT get the channel lock for SIP/324-083ae4e0!
[Jul 20 14:13:17] ERROR[5827]: chan_sip.c:18838 handle_request_do: SIP
transaction failed: YzcyMGFkMTgyNGNiMTRlMGFhNThkNTBkYjU0Y2FmMGY.
[Jul 20 14:13:18] ERROR[5827]: chan_sip.c:18837 handle_request_do: We
could NOT get the channel lock for SIP/324-083ae4e0!
[Jul 20 14:13:18] ERROR[5827]: chan_sip.c:18838 handle_request_do: SIP
transaction failed: YzcyMGFkMTgyNGNiMTRlMGFhNThkNTBkYjU0Y2FmMGY.

======================================================================
Relationships       ID      Summary
----------------------------------------------------------------------
related to          0013287 200 OK retransmitted even when first SI...
has duplicate       0013419 Can't get lock in sip to sip calls
====================================================================== 

---------------------------------------------------------------------- 
 (0092295) pj (reporter) - 2008-09-10 06:49
 http://bugs.digium.com/view.php?id=13115#c92295 
---------------------------------------------------------------------- 
not only SIP/OK is retransmitted, but also "Reguest Terminated" messages
(as reaction to SIP CANCEL) are retransmitted many times after "could NOT
get the channel lock" appears on asterisk console.
look at attached packet dump ReqTermResend.pcap and graph analysis
ReqTermResend.png


[Sep 10 13:43:44]     -- Executing [_ZXX at from-bill:36]
Playback("SIP/ipbx-gw-08480c88", "vlastni/nedostupny,noanswer") in new
stack
[Sep 10 13:43:44]     -- <SIP/ipbx-gw-08480c88> Playing
'vlastni/nedostupny.slin' (language 'cz')
[Sep 10 13:43:49] ERROR[22631]: chan_sip.c:19202 handle_request_do: We
could NOT get the channel lock for SIP/ipbx-gw-08480c88!
[Sep 10 13:43:49] ERROR[22631]: chan_sip.c:19203 handle_request_do: SIP
transaction failed: 4b06b4a7576129ba7e8a925d2384be3c at 192.168.40.4
[Sep 10 13:43:49]   == Spawn extension (from-bill, _ZXX, 36) exited
non-zero on 'SIP/ipbx-gw-08480c88'
[Sep 10 13:43:59] WARNING[22631]: chan_sip.c:2991 retrans_pkt: Maximum
retries exceeded on transmission
4b06b4a7576129ba7e8a925d2384be3c at 192.168.40.4 for seqno 103 (Critical
Response) -- See doc/sip-retransmit.txt. 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2008-09-10 06:49 pj             Note Added: 0092295                          
======================================================================




More information about the asterisk-bugs mailing list