[asterisk-bugs] [Asterisk 0016729]: [regression] Local channels broken for Originate and .callfiles : Call failed to go through, reason (3) Remote end Ringing

Asterisk Bug Tracker noreply at bugs.digium.com
Thu Feb 4 18:26:11 CST 2010


The following issue has been CLOSED 
====================================================================== 
https://issues.asterisk.org/view.php?id=16729 
====================================================================== 
Reported By:                kebl0155
Assigned To:                
====================================================================== 
Project:                    Asterisk
Issue ID:                   16729
Category:                   Core/Channels
Reproducibility:            always
Severity:                   major
Priority:                   normal
Status:                     closed
Asterisk Version:           SVN 
JIRA:                       SWP-825 
Regression:                 Yes 
Reviewboard Link:            
SVN Branch (only for SVN checkouts, not tarball releases): N/A 
SVN Revision (number only!):  
Request Review:              
Resolution:                 fixed
Fixed in Version:           1.6.2.3
====================================================================== 
Date Submitted:             2010-01-29 05:47 CST
Last Modified:              2010-02-04 18:26 CST
====================================================================== 
Summary:                    [regression] Local channels broken for Originate and
.callfiles : Call failed to go through, reason (3) Remote end Ringing
Description: 
Apologies if this is a dupe - I did look but couldn't find any similar.

This is an error in 1.6.2.1 (which isn't an option in the Product Version
pulldown - I'd be grateful if a bug marshall could please amend).

In all versions of Asterisk up to and including 1.6.2.0, it is possible to
launch a call to two different extensions using the Manager Originate
action, or by placing a file to /var/spool/asterisk/outgoing

Asterisk will ring the first extension, and when this is answered, launch
the second extension.

In 1.6.2.1, the second extension is never rung, so this is broken.

These mechanisms are the basis of all automatic Dialler applications, so
Asterisk will be unsuitable for any Dialler use until this bug is fixed.
======================================================================
Relationships       ID      Summary
----------------------------------------------------------------------
related to          0016525 [patch] Cannot spy on channel when a lo...
====================================================================== 

---------------------------------------------------------------------- 
 (0117767) tilghman (administrator) - 2010-02-04 18:26
 https://issues.asterisk.org/view.php?id=16729#c117767 
---------------------------------------------------------------------- 
That's because 1.6.2.2 is a security release.  It contained ONLY the
security fix over and above what was in 1.6.2.1.  The next full release of
1.6.2 (could be 1.6.2.3 or might not be, if we have to do another security
release) will have the fix. 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2010-02-04 18:26 tilghman       Asterisk Version         1.6.2.1 => SVN      
2010-02-04 18:26 tilghman       Note Added: 0117767                          
2010-02-04 18:26 tilghman       Status                   new => closed       
2010-02-04 18:26 tilghman       Resolution               reopened => fixed   
2010-02-04 18:26 tilghman       Description Updated                          
2010-02-04 18:26 tilghman       Additional Information Updated                  
 
======================================================================




More information about the asterisk-bugs mailing list