Excuse me if I am off the mark here, I don't have the chance to read too well into your post. But if it is what I think it is, I remember I had a similar situation a few years ago, and I ended up having to create an internal table in my code, so that I could keep track of the channel ids + action ids .
Please never mind if it is something else
CS
-------- Original Message --------
Subject: Re: [asterisk-users] AMI: anything to glue originate to
events?
From: "giovanni.v" <[email protected]>
Date: Thu, November 17, 2011 11:22 am
To: [email protected]
On 17/11/2011 13.11, Yaroslav Panych wrote:
> exten => 384087,1,UserEvent(LinkOriginate,CHANNEL:${CHANNEL(name),ACTIONID:${ActionID}}
> ....
> UserEvent application will generate event into AMI in form
> Event: LinkOriginate
> CHANNEL: channle-name (channel id created by asterisk)
> ACTIONID: FFA02C6A03 (action id you set in originate)
Thanks Yaroslav,
unfortunately this doesn't add much because only generate another event
but nothing will propagate to Originate child events.
Also the event is fired in asynchronous mode... usually reported later
in the middle of other events when almost of the call flow was already
processed.
Thanks anyway.
--
_____________________________________________________________________
-- Bandwidth and Colocation Provided by http://www.api-digital.com --
New to Asterisk? Join us for a live introductory webinar every Thurs:
http://www.asterisk.org/hello
asterisk-users mailing list
To UNSUBSCRIBE or update options visit:
http://lists.digium.com/mailman/listinfo/asterisk-users
-- _____________________________________________________________________ -- Bandwidth and Colocation Provided by http://www.api-digital.com -- New to Asterisk? Join us for a live introductory webinar every Thurs: http://www.asterisk.org/hello
asterisk-users mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
