I haven't tested this, it's just a thought. What about sending
through a variable as part of the Originate message, then
Noop(${Variable} ${CHANNEL}) in the extension after the call setup. I
think that would send back a manager message with the variable
(supplied at originate) and the channel_ID. Would that let you
correlate the two?
Do I understand what you're asking correctly?
I think the ideal thing would be for messages to include the ACTIONID
of the manager command that spawned them if that's possible.
Dave
On 1/24/06, Mike C. Fletcher <[EMAIL PROTECTED]> wrote:
> Shidan wrote:
> > I think you would look for the Link event for this, with the
> > associated id. But if its transcoding ( Protocol and Codec) there will
> > be more than one Links coming in.
> >
> Actually, the Link events suffer the same problem as the others, the
> channel event has no connection to the Action which spawned the channel,
> so you can't de-multiplex the creation of multiple events back to their
> originators. I've also tried specifying a channel attribute and then
> reading that out, no go, always comes out Null.
>
> Thanks,
> Mike
>
> --
> ________________________________________________
> Mike C. Fletcher
> Designer, VR Plumber, Coder
> http://www.vrplumber.com
> http://blog.vrplumber.com
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>
--
David Donovan
Consultant
Fulcrum Solutions
