[asterisk-bugs] [Asterisk 0013136]: [patch] sip peer qualified failed, asterisk lock.

[Asterisk Bug Tracker]

A NOTE has been added to this issue. 
====================================================================== 
https://issues.asterisk.org/view.php?id=13136 
====================================================================== 
Reported By:                pabelanger
Assigned To:                dvossel
====================================================================== 
Project:                    Asterisk
Issue ID:                   13136
Category:                   Channels/chan_sip/General
Reproducibility:            always
Severity:                   major
Priority:                   normal
Status:                     assigned
Asterisk Version:           SVN 
JIRA:                        
Regression:                 No 
SVN Branch (only for SVN checkouts, not tarball releases): N/A 
SVN Revision (number only!):  
Request Review:              
====================================================================== 
Date Submitted:             2008-07-23 02:32 CDT
Last Modified:              2009-09-30 12:48 CDT
====================================================================== 
Summary:                    [patch] sip peer qualified failed, asterisk lock.
Description: 
We just had asterisk lock on us tonight.  Best we can guess is because we
lost our SIP PEER (via qualify).

See output from 'show core locks'.
======================================================================
Relationships       ID      Summary
----------------------------------------------------------------------
parent of           0015894 SIP register via tls causes lock on sip...
====================================================================== 

---------------------------------------------------------------------- 
 (0111661) whys (reporter) - 2009-09-30 12:48
 https://issues.asterisk.org/view.php?id=13136#c111661 
---------------------------------------------------------------------- 
Kudos to dvossel!  This fix now allows a trunk to connect to Microsoft
Exchange Unified messaging, with it's stealth firewall on. (need to dial
two extensions simultaneously, knowing that only one will answer.
Previously this call blocked waiting for both extensions to respond, but
now it seems to work flawlessly. )

I can't speak for all the issues above, but my tests work. 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2009-09-30 12:48 whys           Note Added: 0111661                          
======================================================================