[asterisk-bugs] [Asterisk 0015784]: [regression] Simultaneous calls from same Call-ID silently ignored by asterisk

Asterisk Bug Tracker noreply at bugs.digium.com
Fri Feb 12 04:03:33 CST 2010


A NOTE has been added to this issue. 
====================================================================== 
https://issues.asterisk.org/view.php?id=15784 
====================================================================== 
Reported By:                m0bius
Assigned To:                
====================================================================== 
Project:                    Asterisk
Issue ID:                   15784
Category:                   Channels/chan_sip/General
Reproducibility:            always
Severity:                   minor
Priority:                   normal
Status:                     acknowledged
Asterisk Version:           SVN 
JIRA:                       SWP-221 
Regression:                 Yes 
Reviewboard Link:            
SVN Branch (only for SVN checkouts, not tarball releases): N/A 
SVN Revision (number only!):  
Request Review:              
====================================================================== 
Date Submitted:             2009-08-27 05:40 CDT
Last Modified:              2010-02-12 04:03 CST
====================================================================== 
Summary:                    [regression] Simultaneous calls from same Call-ID
silently ignored by asterisk
Description: 
Hello everyone,

We have a follow-me system which terminates calls to an Asterisk server
which holds registrations for our VoIP users. In our follow-me system we
give the capability to the users to perform simultaneous follow-me to the
Asterisk Server (thus ringing two different voip accounts).

However I've noticed that on asterisk 1.6.1.1 and 1.6.1.4 when two calls
are sent simultaneously to different dialled numbers with the same Call-ID,
the second call does not enter the context. In a trace I did, I've seen
that asterisk responds to the SIP INVITE with Trying; however, that calls
stays there until it times out from the remote peer. 

The same thing has been tested on Asterisk 1.6.0.7 and 1.6.0.13 and it
works properly. I will attaching two traces (one from asterisk 1.6.0.7 and
one from asterisk 1.6.1.4)
======================================================================
Relationships       ID      Summary
----------------------------------------------------------------------
related to          0016116 [patch] Fix/improve transaction/dialog-...
====================================================================== 

---------------------------------------------------------------------- 
 (0118028) m0bius (reporter) - 2010-02-12 04:03
 https://issues.asterisk.org/view.php?id=15784#c118028 
---------------------------------------------------------------------- 
Sorry for taking so long to respond. I would like to share with everyone
that the fix mentioned above has been working on production environment for
a few months without any issues. 

I am not entirely sure that this still is the best way to go, but it could
serve as a workaround until then. 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2010-02-12 04:03 m0bius         Note Added: 0118028                          
======================================================================




More information about the asterisk-bugs mailing list