RE: [Asterisk-Users] Asterisk Manager API - multi "Originate" cal ls

[mattf]

ActionID does not return in all events related to an Action sent, sometimes it will just send you a success message and nothing more. Just try Originating a call from a meetme room over an outside line. You will get about 150 lines of output and only one message will have the ActionID in it, the success message. On the other hand the callerID is placed on many more of the events in the output. It is still the case that if you do complex Manager Actions, the ONLY solution for tracking a call is to use a custom CallerID.   Action: Originate Exten: 8600080 Channel: local/[EMAIL PROTECTED] Context: default Priority: 1 Callerid: DF345678901234567890 Actionid: AID45678901234567890   MATT---   -----Original Message----- From: Bill Seddon [mailto:[EMAIL PROTECTED] Sent: Wednesday, March 02, 2005 8:06 AM To: Stephen Owen hosted; Asterisk Users Mailing List - Non-Commercial Discussion Subject: RE: [Asterisk-Users] Asterisk Manager API - multi "Originate" calls << read in places that you use "originate" command and wait for an event back, does that mean you cannot place another "originate" until the event comes back ?>>   Not in my experience.  Originate will not send an event to the caller until either the intended caller (that is the extension used in Originate) has picked up their phone or a timeout occurs because the intended caller does not pick up their phone.  You can send as many originate requests as you like but they will fail if more than one uses the same extension at the same time.   The issue you will face is determining which event generated by Asterisk belongs to which origination request.  For this reason, the Manager API allows you to specify an “ActionID” on any command. An ActionID is any string of characters that you use to uniquely identify each command use issue.  Asterisk will include the ActionID with each related event so you know which events to respond to and which to ignore.  You will see many events generated by Asterisk only some of which will relate to your command.  The others will be events that Asterisk raises (for example when a phone registers) or events in response to commands issues by other Manager API users and at the command line.   Take a look at Nicolas Gudino’s Flash Operator Panel (www.asternic.org) as it used the manager API extensively (albeit through a proxy) and will typically make many requests via the Manger API.    <<Is it true that multiple API connections to Asterisk Manager API will crash it (thinking of alternative way to crack the nut)>>   Again, not in my experience.    Lyquidity Solutions Limited +44 (0) 208 241 0500 From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Stephen Owen hosted Sent: March 02, 2005 12:28 PM To: asterisk-users@lists.digium.com Subject: [Asterisk-Users] Asterisk Manager API - multi "Originate" calls   Been researching connecting over TCP\IP to Asterisk Manager API to initiate several concurrent calls to dial out. Prefer not to generate ASCII .call files.   Question : I read in places that you use "originate" command and wait for an event back, does that mean you cannot place another "originate" until the event comes back ?   Is it true that multiple API connections to Asterisk Manager API will crash it (thinking of alternative way to crack the nut)   All help would be welcome - thanks   Stephen Owen   sip:[EMAIL PROTECTED] IM:[EMAIL PROTECTED]

_______________________________________________
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