[asterisk-bugs] [Asterisk 0019234]: SIP stack stops working if a Dial command if forwarded by a SIP physical phone

Asterisk Bug Tracker noreply at bugs.digium.com
Mon May 30 02:48:08 CDT 2011


A NOTE has been added to this issue. 
====================================================================== 
https://issues.asterisk.org/view.php?id=19234 
====================================================================== 
Reported By:                tiziano
Assigned To:                
====================================================================== 
Project:                    Asterisk
Issue ID:                   19234
Category:                   Applications/app_dial
Reproducibility:            always
Severity:                   major
Priority:                   normal
Status:                     feedback
Asterisk Version:           1.8.3.3 
JIRA:                        
Regression:                 No 
Reviewboard Link:            
SVN Branch (only for SVN checkouts, not tarball releases): N/A 
SVN Revision (number only!):  
Request Review:              
====================================================================== 
Date Submitted:             2011-05-05 07:49 CDT
Last Modified:              2011-05-30 02:48 CDT
====================================================================== 
Summary:                    SIP stack stops working if a Dial command if
forwarded by a SIP physical phone
Description: 
If you enable the call forward feature on a registered SIP phone  - I've
tried with two different SNOM models a a Cisco/Linksys SPA9xx - when a call
reach the phone you'll see (on asterisk CLI):

 Got SIP response 302 "Moved Temporarily" back from (PHONE IP:PORT)
 Now forwarding SIP/(CHANNEL) to 'Local/....@(CONTEXT)' (thanks to
SIP/(FORWARDING PHONE CHANNEL)
 Not accepting call completion offers from call-forward recipient
Local/... at ....

then all SIP activity ceased, both incoming and outgoing calls, while
asterisk remains up and running
======================================================================
Relationships       ID      Summary
----------------------------------------------------------------------
related to          0019308 Asterisk always deadlocks in queue afte...
related to          0018818 [patch] Crashing when using local chann...
====================================================================== 

---------------------------------------------------------------------- 
 (0135549) tiziano (reporter) - 2011-05-30 02:48
 https://issues.asterisk.org/view.php?id=19234#c135549 
---------------------------------------------------------------------- 
I can confirm that the Local channel fix solved the SIP Call forward
problem.
Now, I've another problem to submit. Because I think it's related to SIP
deadlocks, I'll expose it here and, if you think it's a new issue, I could
open it. On this particular machine (the one I've already talked about)
there are 231 SIP peers registered: 4 are SIP thunks, all the others are
SIP peers (phones).
As you can imagine, there are a lot of SIP transfer operations every day,
both blind and attended. The first asterisk release I've installed on this
machine is 1.8.2.2 (it does not have neither the blind-deadlock patch for
the 18403 issue nor the attended-transfer patch for the 18837 issue). The
machine deadlocked lot of times every day (more then 20) so, when 1.8.3.3
(patched for issue 18403) comes out, I've upgraded and the numbers of
deadlocks lowers to about 10 every day. Now I've upgraded again to 1.8.4
(patched for issue 18837) and, despite all my expectations, there are still
three or four SIP deadlocks every day. I've attached both the "core show
locks" and the "backtrace threads" outputs of the two deadlock of this
morning. Could you help me? 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2011-05-30 02:48 tiziano        Note Added: 0135549                          
======================================================================




More information about the asterisk-bugs mailing list