Tony Mountifield wrote:
In article <[EMAIL PROTECTED]>, John Daragon <[EMAIL PROTECTED]> wrote:
Hi;
I've been looking for an arbitrary way of discovering when the last
user has left a Meetme conference...
It occurred to me that I could launch an agi script to keep watch over
the conference and do something when the user count reaches zero... And
of course, I can do that directly from the dialplan.
But I was looking at app_meetme, and the docs say:
* 'b' — run AGI script specified in ${MEETME_AGI_BACKGROUND}
o Default: conf-background.agi (Note: This does not work
with non-Zap channels in the same conference)
I can't see anything in the code to explain this; does anyone understand
why it might be ?
To explain which part? That it doesn't work with non-Zap channels?
For Zap channels, the mixing is automatically done at the driver level
once MeetMe has told the driver which channels to mix.
For a non-Zap channel, a proxy Zap channel (pseudo) is created to
participate in the driver-level mix. The meetme thread on the channel
then enters a loop to copy audio back and forth between the non-Zap
channel and the proxy pseudo-channel.
When an AGI background script is specified, it runs INSTEAD OF the
copying loop mentioned above. Therefore there is nothing to move the
audio to and from the non-Zap channel.
Hope this helps!
It does, indeed ! Thanks for the succinct explanation.
I owe you a beer.
jd
--
John Daragon [EMAIL PROTECTED]
argv[0] limited
Lambs Lawn Cottage, Staple Fitzpaine, Taunton, TA3 5SL, UK
v +44 (0) 1460 234068 f +44 (0) 1460 234069 m +44 (0) 7836 576127
_______________________________________________
--Bandwidth and Colocation provided by Easynews.com --
Asterisk-Users mailing list
To UNSUBSCRIBE or update options visit:
http://lists.digium.com/mailman/listinfo/asterisk-users
