[Asterisk-Users] actionID on manager events

2005-09-14 Thread Michael George
Hello, all!

I'm looking at the wiki page and info on the mailing list and I'm getting
conflicting info...

I am using the manager API from the telnet CLI and I am testing creating calls
with it.  I login with events: on and I can originate calls just fine.

However, when I set ActionID on an Originate, I cannot see anywhere where that
actionid carries into the Event output.

But I found this on a post from January:
   Yes, ActionID is a value you can use when issuing a command.  It there so
that you can be sure you respond to your own responses not to someone 
else's
or that you respond to an response instance in the correct way.  In a
multi-threaded app you might have several actions outstanding so you 
will
need to know what response corresponds to which command.

Which indicates that the actionid should be coming through.  Is there perhaps
some setting I'm missing?

Thanks!

-- 
-M

There are 10 kinds of people in this world:
Those who can count in binary and those who cannot.
___
--Bandwidth and Colocation sponsored by Easynews.com --

Asterisk-Users mailing list
Asterisk-Users@lists.digium.com
http://lists.digium.com/mailman/listinfo/asterisk-users
To UNSUBSCRIBE or update options visit:
   http://lists.digium.com/mailman/listinfo/asterisk-users


Re: ***SPAM*** [Asterisk-Users] actionID on manager events

2005-09-15 Thread Joerg Lauer



Michael George wrote:

Hello, all!

I'm looking at the wiki page and info on the mailing list and I'm getting
conflicting info...

I am using the manager API from the telnet CLI and I am testing creating calls
with it.  I login with events: on and I can originate calls just fine.

However, when I set ActionID on an Originate, I cannot see anywhere where that
actionid carries into the Event output.

But I found this on a post from January:
   Yes, ActionID is a value you can use when issuing a command.  It there so
that you can be sure you respond to your own responses not to someone 
else's
or that you respond to an response instance in the correct way.  In a
multi-threaded app you might have several actions outstanding so you 
will
need to know what response corresponds to which command.

Which indicates that the actionid should be coming through.  Is there perhaps
some setting I'm missing?

Thanks!



Hi,

have you set Async attribute of your Originate Action to 'true'?

Because as far as I know Events are only generated if it is set to true.

Joerg
___
--Bandwidth and Colocation sponsored by Easynews.com --

Asterisk-Users mailing list
Asterisk-Users@lists.digium.com
http://lists.digium.com/mailman/listinfo/asterisk-users
To UNSUBSCRIBE or update options visit:
  http://lists.digium.com/mailman/listinfo/asterisk-users


AW: ***SPAM*** [Asterisk-Users] actionID on manager events

2005-09-15 Thread Anton Kostanjsek
hi,

afaik, the action-id provided with the OriginateAction should only show up in 
the OriginateSuccess or OriginateFailure event. Intermediate events that are 
generated when the channels are create will NOT carry the action-id of the 
originate.

The async flag tells asterisk to process originates in parallel, i.e. if you 
have two users originating calls and NO async flag set, the second originate 
will be processed AFTER the first one was either picked up or timed out. So, I 
suggest you always set the async flag or you'll get horrible originate-timeout 
scenarios and the interface will look broken where in fact its only working 
strictly sequentially. (do I sound like I've been bitten by this? ;) This flag 
should have no effect on events created for the action. They're always visible, 
you just have to figure out which channels resemble the call you just created 
with the OriginateAction.

hth,
Tony

-Ursprüngliche Nachricht-
Von: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] Auftrag von Joerg
Lauer
Gesendet: Donnerstag, 15. September 2005 11:16
An: Asterisk Users Mailing List - Non-Commercial Discussion
Betreff: Re: ***SPAM*** [Asterisk-Users] actionID on manager events




Michael George wrote:
> Hello, all!
> 
> I'm looking at the wiki page and info on the mailing list and I'm getting
> conflicting info...
> 
> I am using the manager API from the telnet CLI and I am testing creating calls
> with it.  I login with events: on and I can originate calls just fine.
> 
> However, when I set ActionID on an Originate, I cannot see anywhere where that
> actionid carries into the Event output.
> 
> But I found this on a post from January:
>Yes, ActionID is a value you can use when issuing a command.  It there so
>   that you can be sure you respond to your own responses not to someone 
> else's
>   or that you respond to an response instance in the correct way.  In a
>   multi-threaded app you might have several actions outstanding so you 
> will
>   need to know what response corresponds to which command.
> 
> Which indicates that the actionid should be coming through.  Is there perhaps
> some setting I'm missing?
> 
> Thanks!
> 

Hi,

have you set Async attribute of your Originate Action to 'true'?

Because as far as I know Events are only generated if it is set to true.

Joerg
___
--Bandwidth and Colocation sponsored by Easynews.com --

Asterisk-Users mailing list
Asterisk-Users@lists.digium.com
http://lists.digium.com/mailman/listinfo/asterisk-users
To UNSUBSCRIBE or update options visit:
   http://lists.digium.com/mailman/listinfo/asterisk-users
___
--Bandwidth and Colocation sponsored by Easynews.com --

Asterisk-Users mailing list
Asterisk-Users@lists.digium.com
http://lists.digium.com/mailman/listinfo/asterisk-users
To UNSUBSCRIBE or update options visit:
   http://lists.digium.com/mailman/listinfo/asterisk-users