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

[Asterisk Bug Tracker]

A NOTE has been added to this issue. 
====================================================================== 
http://bugs.digium.com/view.php?id=13136 
====================================================================== 
Reported By:                pabelanger
Assigned To:                
====================================================================== 
Project:                    Asterisk
Issue ID:                   13136
Category:                   Channels/chan_sip/General
Reproducibility:            always
Severity:                   minor
Priority:                   normal
Status:                     confirmed
Asterisk Version:           1.6.0 
SVN Branch (only for SVN checkouts, not tarball releases): N/A 
SVN Revision (number only!):  
Disclaimer on File?:        N/A 
Request Review:              
====================================================================== 
Date Submitted:             2008-07-23 02:32 CDT
Last Modified:              2008-11-19 11:35 CST
====================================================================== 
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'.
====================================================================== 

---------------------------------------------------------------------- 
 (0095084) blitzrage (administrator) - 2008-11-19 11:35
 http://bugs.digium.com/view.php?id=13136#c95084 
---------------------------------------------------------------------- 
My test setup includes 3 devices: a Polycom (that has TCP support), Zoiper
(which I don't think has TCP support, but seems to respond to the NOTIFY
packets regardless...) and X-Lite, which explicitly seems to reject the
packets.

I believe I was seeing the error you mentioned when trying X-Lite

(...some time passes as he gets the exact error)

*CLI> [Nov 19 08:29:34] ERROR[26147]: tcptls.c:252
ast_tcptls_client_start: Unable to connect SIP socket to
192.168.128.129:59668: Connection refused

And some more if it is useful...


[Nov 19 08:29:35] ERROR[26147]: chan_sip.c:10543 register_verify: 'UDP' is
not a valid transport for '102'. we only use 'TCP'! ending call.
[Nov 19 08:29:35] NOTICE[26147]: chan_sip.c:18293 handle_request_register:
Registration from '"X-Lite"<sip:102 at 192.168.128.50>' failed for
'192.168.128.129' - Device not configured to use this transport type


The way I reproduce is a bit tricky...

Basically I block the incoming SIP signalling port (in my case it is 5430,
but most devices would be 5060) in the RH-Firewall-1-INPUT chain. Then
after I see the UNREACHABLE message, I then block the connection in the
OUTPUT chain of iptables. After a little bit of time (60-120 seconds
roughly), then I get the lock showing in 'core show locks'.


That seems to be the only way I was able to reliably reproduce it.
Sometimes is hit or miss, but that seems to be the most reliable way that I
could find. 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2008-11-19 11:35 blitzrage      Note Added: 0095084                          
======================================================================