[asterisk-bugs] [Asterisk 0018322]: Redirect two bridged channels to the same conference

Asterisk Bug Tracker noreply at bugs.digium.com
Wed Nov 17 09:45:22 CST 2010


The following issue has been set as RELATED TO issue 0018230. 
====================================================================== 
https://issues.asterisk.org/view.php?id=18322 
====================================================================== 
Reported By:                nerbos
Assigned To:                
====================================================================== 
Project:                    Asterisk
Issue ID:                   18322
Category:                   Applications/app_meetme
Reproducibility:            sometimes
Severity:                   major
Priority:                   normal
Status:                     new
Asterisk Version:           1.8.0 
JIRA:                        
Regression:                 No 
Reviewboard Link:            
SVN Branch (only for SVN checkouts, not tarball releases): N/A 
SVN Revision (number only!):  
Request Review:              
====================================================================== 
Date Submitted:             2010-11-17 09:26 CST
Last Modified:              2010-11-17 09:45 CST
====================================================================== 
Summary:                    Redirect two bridged channels to the same conference
Description: 
Greetings,

OS: centOS 5.5
Libpri: 1.4.11.4
Dahdi: 2.4.0
Asterisk: 1.8.0

Situation, i have two channels bridged together and i want to pass both
channels to a conference room, so i decided to send a Redirect in the AMI
console:

Action: Redirect
Channel: CHANNEL_1
ExtraChannel: CHANNEL_2
Exten: 1001
ExtraExten: 1001
Context: my_conference
ExtraContext: my_conference
Priority: 1
ExtraPriority: 1
ActionID: XXXX

Sometimes one of the channels fails to stay in the conference, other times
both channels stay in conference (as expected). The AMI events are
different in the two cenarios (the order of the events), when it fails, the
channel that didn't get masquerade is the first to send the MeetMeJoin
event, proceeded by a MeetMeLeave. When it works the first MeetMeJoin is
send by the masquerade channel. I don't know if this order is related to
this issue, but i found it important to report.

Best regards.

P.S.: My conference context is pretty simple...

[my_conference]
exten => _X.,1,MeetMe(${EXTEN},dq)
exten => _X.,2,Hangup

======================================================================
Relationships       ID      Summary
----------------------------------------------------------------------
related to          0018230 [regression] Redirect function (over co...
====================================================================== 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2010-11-17 09:45 rmudgett       Relationship added       related to 0018230  
======================================================================




More information about the asterisk-bugs mailing list