VoIP Mailing List Archives
Mailing list archives for the VoIP community |
|
View previous topic :: View next topic |
Author |
Message |
ggraudins at hotmail.com Guest
|
Posted: Sun May 25, 2008 7:35 pm Post subject: [asterisk-users] AMI Redirect between MeetMe rooms |
|
|
Hello group,
We were running Asterisk 1.4.9 until we ran into the bug where Monitor()ing a channel that's sitting in a MeetMe() room would only record one leg of the conversation. Shucks. Did some checking around, saw some similar issues on the list, decided to upgrade to see if it's been fixed.
Upgraded to 1.4.20. The good news - it's fixed, works like a charm. The bad news - now it seems doing an AMI redirect of a channel between two MeetMe() conferences successfully puts the channel in the new MeetMe() (the target), but the old MeetMe() (the source) still hears the channel, even though AMI tells us that there was a MeetMeLeave event, etc. Looks very much like a bug. Anyone seen this bizarre behavior?
The setup is as follows:
The channel is a Zap channel - Zap/N-1
The meetmes are very straight forward:
[conf]
exten => _X.,1,MeetMe(${EXTEN},d)
The scenario is equally simple - let's say Zap/1-1 is sitting in 1 at conf. If I do an
action: redirect
channel: Zap/1-1
context: conf
exten: 2
priority: 1
2 at conf now hears Zap/1-1 and all is well, except that 1 at conf also (still!) hears Zap/1-1. Didn't work that way before. When was this introduced?
Thoughts?
Girts
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.digium.com/pipermail/asterisk-users/attachments/20080525/1fdab546/attachment.htm |
|
Back to top |
|
|
tony at softins.clara.... Guest
|
Posted: Mon May 26, 2008 6:03 am Post subject: [asterisk-users] AMI Redirect between MeetMe rooms |
|
|
In article <BLU140-W5DED69E2E3E1888995586B9C20 at phx.gbl>,
Girts Graudins <ggraudins at hotmail.com> wrote:
Quote: | The setup is as follows:
The channel is a Zap channel - Zap/N-1
The meetmes are very straight forward:
[conf]
exten => _X.,1,MeetMe(${EXTEN},d)
The scenario is equally simple - let's say Zap/1-1 is sitting in 1 at conf. If I do an
action: redirect
channel: Zap/1-1
context: conf
exten: 2
priority: 1
2 at conf now hears Zap/1-1 and all is well, except that 1 at conf also (still!) hears Zap/1-1.
Didn't work that way before. When was this introduced?
|
Are you sure the redirect succeeded? Is the above exactly what you do,
or just an illustrative example? The reason I ask is because _X. will NOT
match the extension "2". A dot matches *one* or more characters.
If you really are using one-digit extension and conference numbers, change
your pattern to _X! instead, and try again. A "!" will match zero or more.
Of course, if that was just an illustration, your problem could be completely
different.
Cheers
Tony
--
Tony Mountifield
Work: tony at softins.co.uk - http://www.softins.co.uk
Play: tony at mountifield.org - http://tony.mountifield.org |
|
Back to top |
|
|
ggraudins at hotmail.com Guest
|
Posted: Thu May 29, 2008 4:48 pm Post subject: [asterisk-users] AMI Redirect between MeetMe rooms |
|
|
Hello group,
So, if anyone encounters this in the future here's the solution. We were doing the Monitor() on the channel from the AMI right as it was entering the conference. This was resulting in the voice sticking around in the conf. even when the channel itself was AMI redirected elsewhere.
We changed the setup to start Monitor on the channel from the dialplan _before_ the call was placed in the conference. That fixed the issue. Now the channel and the voice leaves properly upon an AMI redirect.
Girts
Quote: | To: asterisk-users at lists.digium.com
From: tony at softins.clara.co.uk
Date: Mon, 26 May 2008 11:03:50 +0000
Subject: Re: [asterisk-users] AMI Redirect between MeetMe rooms
In article <BLU140-W5DED69E2E3E1888995586B9C20 at phx.gbl>,
Girts Graudins <ggraudins at hotmail.com> wrote:
Quote: | The setup is as follows:
The channel is a Zap channel - Zap/N-1
The meetmes are very straight forward:
[conf]
exten => _X.,1,MeetMe(${EXTEN},d)
The scenario is equally simple - let's say Zap/1-1 is sitting in 1 at conf. If I do an
action: redirect
channel: Zap/1-1
context: conf
exten: 2
priority: 1
2 at conf now hears Zap/1-1 and all is well, except that 1 at conf also (still!) hears Zap/1-1.
Didn't work that way before. When was this introduced?
|
Are you sure the redirect succeeded? Is the above exactly what you do,
or just an illustrative example? The reason I ask is because _X. will NOT
match the extension "2". A dot matches *one* or more characters.
If you really are using one-digit extension and conference numbers, change
your pattern to _X! instead, and try again. A "!" will match zero or more.
Of course, if that was just an illustration, your problem could be completely
different.
Cheers
Tony
--
Tony Mountifield
Work: tony at softins.co.uk - http://www.softins.co.uk
Play: tony at mountifield.org - http://tony.mountifield.org
_______________________________________________
-- Bandwidth and Colocation Provided by http://www.api-digital.com --
asterisk-users mailing list
To UNSUBSCRIBE or update options visit:
http://lists.digium.com/mailman/listinfo/asterisk-users
| -------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.digium.com/pipermail/asterisk-users/attachments/20080529/a6d2d18c/attachment.htm |
|
Back to top |
|
|
|
|
|
You cannot post new topics in this forum You cannot reply to topics in this forum You cannot edit your posts in this forum You cannot delete your posts in this forum You cannot vote in polls in this forum
|
Powered by phpBB © 2001, 2005 phpBB Group
|