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

Asterisk Bug Tracker noreply at bugs.digium.com
Fri May 6 18:55:41 CDT 2011


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:                     ready for testing
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:              2011-05-06 18:55 CDT
====================================================================== 
Summary:                    [patch] [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-...
====================================================================== 

---------------------------------------------------------------------- 
 (0134626) lmadsen (administrator) - 2011-05-06 18:55
 https://issues.asterisk.org/view.php?id=15784#c134626 
---------------------------------------------------------------------- 
This issue is pretty old now, and it would be ideal if someone could
comment on if this issue may now be resolved. A lot of work has been done
in areas similar to this, and someone going through and testing again would
be ideal. Beyond that, it would be nice to know if we're at the same spot,
or if we're closer, but there are still things to clean up. If that is the
case, a detailed analysis would be extremely helpful.

I asked mmichelson about this issue today, and he doesn't quite recall it,
but here is his statement:

<putnopvut> Taking the issue as stated, I think it *may* be fixed though.
I think it may be worthwhile to do a ping on the issue since lots of work
has been done to properly ID calls. One of the big things that was done was
to observe the branch parameter in Via headers, but I'm not sure this issue
deals with that. 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2011-05-06 18:55 lmadsen        Note Added: 0134626                          
======================================================================




More information about the asterisk-bugs mailing list