[asterisk-bugs] [Asterisk 0011800]: asterisk 1.6-beta1 destroys cisco 7960 (sip firmware 7.4) outbound calls after 20sec due to no response to 200 OK

[noreply at bugs.digium.com]

A NOTE has been added to this issue. 
====================================================================== 
http://bugs.digium.com/view.php?id=11800 
====================================================================== 
Reported By:                hmodes
Assigned To:                
====================================================================== 
Project:                    Asterisk
Issue ID:                   11800
Category:                   Channels/chan_sip/Interoperability
Reproducibility:            always
Severity:                   major
Priority:                   normal
Status:                     new
Asterisk Version:           1.6.0-beta1 
SVN Branch (only for SVN checkouts, not tarball releases): 1.6 
SVN Revision (number only!):  
Disclaimer on File?:        N/A 
Request Review:              
====================================================================== 
Date Submitted:             01-19-2008 23:04 CST
Last Modified:              01-22-2008 08:58 CST
====================================================================== 
Summary:                    asterisk 1.6-beta1 destroys cisco 7960 (sip firmware
7.4) outbound calls after 20sec due to no response to 200 OK
Description: 
Version tag on this report is incorrect as there is no 1.6-beta1 tag yet.

1.6-beta1 appears to have an issue with sip timers that causes cisco 7960
sip firmware 7.4 clients to be disconnected after 20 seconds for not
responding to 200 OK (marked as 'critical packet') once call setup is
complete.  See debug.  Incoming calls to the client do not experience the
disconnect.  This is reproducible on two phones both on the lan with
asterisk and at a remote site. 
====================================================================== 

---------------------------------------------------------------------- 
 oej - 01-22-08 08:58  
---------------------------------------------------------------------- 
The contact in the 200 OK is obviously wrong. It specifies a port that
Asterisk normally doesn't listen to and the phone is supposed to send the
ACK there. I don't know if the addition of TCP/TLS stuff changed the
contact process or not, but it certainly looks weird.

Please upload SIP debugs as attachments in the future to make it easier to
work with the bug tracker. Thanks. 

Issue History 
Date Modified   Username       Field                    Change               
====================================================================== 
01-22-08 08:58  oej            Note Added: 0081005                          
======================================================================