asterisk users - Jan 2006 - Manage api- Matching 'Newchannel' event with the 'Originate' command

Hi all,

When the 'Originate' command is issued with 'Async' open set to
'yes', I got the response right away with the correct
'ActionID'. What follows is the 'Newchannel' event with a
'Channel' ID, but their is no 'ActionID' to tie it back to the
command. How do you guys deal with this?
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
http://lists.digium.com/pipermail/asterisk-users/attachments/20060130/c6eedbd5/attachment.htm

Hello,

It's kind of sad, but the only way to have the events of a specific
call in EVERY instance have a unique tag to follow is to use the
CallerIDname field.

Call variables(that you can set at Origination) and variable
inheritance have gotten much better in the last year, but they still
don't work in all cases for call identification in the Manager API
output.

CallerIDname is able to be set at almost any stage of a call and is
printed with most Manager API outputs for channel events. Also, on the
USA PSTN network you cannot send out custom CallerIDname anyway so
this makes it a little less painful in terms of causing crazy
callerIDnames being sent out. This is how we track calls with the
astGUIclient Asterisk Central Queue System(ACQS):
     http://astguiclient.sourceforge.net/acqs.html

Hope that helps,

MATT---

On 1/30/06, Wai Wu <wwu@calltrol.com> wrote:
>
>
> Hi all,
>
> When the 'Originate' command is issued with 'Async' open
set to 'yes', I got
> the response right away with the correct 'ActionID'. What follows
is the
> 'Newchannel' event with a 'Channel' ID, but their is no
'ActionID' to tie it
> back to the command. How do you guys deal with this?
> _______________________________________________
> --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
>
>
>