[asterisk-bugs] [Asterisk 0013545]: Channel re-invited on destination ringing not re-invited back if ringing abandoned.

Asterisk Bug Tracker noreply at bugs.digium.com
Tue May 19 10:51:04 CDT 2009


The following issue has been RESOLVED. 
====================================================================== 
https://issues.asterisk.org/view.php?id=13545 
====================================================================== 
Reported By:                davidw
Assigned To:                file
====================================================================== 
Project:                    Asterisk
Issue ID:                   13545
Category:                   Channels/chan_sip/General
Reproducibility:            always
Severity:                   major
Priority:                   normal
Status:                     resolved
Asterisk Version:           1.4.21.2 
Regression:                 No 
SVN Branch (only for SVN checkouts, not tarball releases): N/A 
SVN Revision (number only!):  
Request Review:              
Resolution:                 fixed
Fixed in Version:           
====================================================================== 
Date Submitted:             2008-09-23 08:25 CDT
Last Modified:              2009-05-19 10:51 CDT
====================================================================== 
Summary:                    Channel re-invited on destination ringing not
re-invited back if ringing abandoned.
Description: 
An incoming SIP call is answered by an agent and then AMI transferred to a
PSTN line on Cisco CCM.  The Cisco provides SDP on the Ringing response and
Asterisk re-invites the incoming call immediately it gets that response.

The Dial command times out and cancels the outgoing call, but at no time
does the re-invite get undone, even when the dialplan eventually
successfully returns the call to the agent.  The result is a silent call.

The un-re-invite can be forced by parking the call and then unparking it
(in this case with an AMI Originate which queues it back to an agent).

This is a big problem for us as it is important for our application that
as many calls as possible have their speech path removed from the Asterisk
system.

I am also concerned that specifying multiple destinations in the Dial
command, may not inhibit the re-invite, leading to conflicting re-invites,
in the order of the Ringing events.  However, I haven't confirmed that this
is the case.
====================================================================== 

---------------------------------------------------------------------- 
 (0105014) file (administrator) - 2009-05-19 10:51
 https://issues.asterisk.org/view.php?id=13545#c105014 
---------------------------------------------------------------------- 
After further examination of the log files I believe my directrtpsetup
change fixed this. While this option may have been disabled it was still
being done on part of the leg, causing things to go weird. The change I
made now ensures directrtpsetup is indeed disabled if configured as such. 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2009-05-19 10:51 file           Note Added: 0105014                          
2009-05-19 10:51 file           Status                   assigned => resolved
2009-05-19 10:51 file           Resolution               reopened => fixed   
======================================================================




More information about the asterisk-bugs mailing list