[asterisk-bugs] [Asterisk 0009910]: When Asterisk is issued 2 Invites with the same CSeq it does not read the corrisponding ACKs

[noreply at bugs.digium.com]

The following issue has been CLOSED 
====================================================================== 
http://bugs.digium.com/view.php?id=9910 
====================================================================== 
Reported By:                cburnett
Assigned To:                
====================================================================== 
Project:                    Asterisk
Issue ID:                   9910
Category:                   Channels/chan_sip/Interoperability
Reproducibility:            always
Severity:                   major
Priority:                   normal
Status:                     closed
Asterisk Version:            1.2.14  
SVN Branch (only for SVN checkouts, not tarball releases):  1.2  
SVN Revision (number only!):  
Disclaimer on File?:        No 
Request Review:              
Resolution:                 open
Fixed in Version:           
====================================================================== 
Date Submitted:             06-07-2007 10:30 CDT
Last Modified:              08-02-2007 15:52 CDT
====================================================================== 
Summary:                    When Asterisk is issued 2 Invites with the same CSeq
it does not read the corrisponding ACKs
Description: 
Call flow is;

PSTN to SIP(ITSP) to Asterisk(trixbox)

The ITSP generates 2 Invites for one incomming call, both of them have the
same callid and both have the same CSeq.

Asterisk receives an ACK and never reads it so the call eventually times
out.  To the caller this just sounds like audio drop.  

 

====================================================================== 

---------------------------------------------------------------------- 
 murf - 08-02-07 15:52  
---------------------------------------------------------------------- 
I hate to do this to you, as you might get the wrong idea and think we
aren't interested in solving this problem, but... well... I have to close
this bug, as the support for 1.2 has expired. From here on out, the only
thing we'll shipping updates for is security problems, and that for a
generous, but limited amount of time.

But, all hope is not lost! We encourage you to see if this problem
persists in 1.4; and if it does, you more than welcome to re-open this bug
(we'll reclassify it), or open a new one, and we'll see we can't help solve
the problem.

So, please, please, see if it possible to try out 1.4 in your environment,
and see if this bug persists. If it does, it looks nasty and needs to be
resolved. 

Issue History 
Date Modified   Username       Field                    Change               
====================================================================== 
08-02-07 15:52  murf           Status                   feedback => closed  
08-02-07 15:52  murf           Note Added: 0068350                          
======================================================================