[asterisk-bugs] [Asterisk 0011474]: Asterisk hangup calls if two identical invites are received

noreply at bugs.digium.com noreply at bugs.digium.com
Tue Mar 4 19:09:22 CST 2008


A NOTE has been added to this issue. 
====================================================================== 
http://bugs.digium.com/view.php?id=11474 
====================================================================== 
Reported By:                drencrom
Assigned To:                file
====================================================================== 
Project:                    Asterisk
Issue ID:                   11474
Category:                   Channels/chan_sip/Interoperability
Reproducibility:            always
Severity:                   major
Priority:                   normal
Status:                     feedback
Asterisk Version:            1.2.24  
SVN Branch (only for SVN checkouts, not tarball releases): N/A  
SVN Revision (number only!):  
Disclaimer on File?:        N/A 
Request Review:              
====================================================================== 
Date Submitted:             12-05-2007 08:06 CST
Last Modified:              03-04-2008 19:09 CST
====================================================================== 
Summary:                    Asterisk hangup calls if two identical invites are
received
Description: 
Context: 
Asterisk server receiving incoming SIP calls from a PortaSIP softswitch

Problem:
Sometimes the softswitch sends two identical INVITES in a row as if the
first OK from Asterisk was lost. When this happens Asterisk keeps resending
the 200 OK message although it in fact receives the PortaSIP ACKs and the
debug shows that it supposedly stopped retransmitting the 200 OK packet.
Then, after 6 retransmissions of the OK packet (all of them ACK'd by the
remote party) Asterisk hangs up a perfectly valid and working call.
The call works fine if there is no retransmission of the first INVITE
packet.

Debug:
I'll attach two log files with verbose and debug enabled. Also SIP debug
was active. One of them shows a valid call and the other shows the problem
I described above.
====================================================================== 

---------------------------------------------------------------------- 
 Tomba - 03-04-08 19:09  
---------------------------------------------------------------------- 
It Seems it has been fixed with the next update.
It happened on two differents systems, both work fine now.
I still don't know if it was a asterisk issue or my configuration.
Sorry for your time. 

Issue History 
Date Modified   Username       Field                    Change               
====================================================================== 
03-04-08 19:09  Tomba          Note Added: 0083391                          
======================================================================




More information about the asterisk-bugs mailing list