mattf
2005-Mar-02 05:50 UTC
[Asterisk-Users] Asterisk Manager API - multi "Originate" cal ls
Hello, You can do either, you can send multiple Originate actions in a long line without waiting for a response back(although the responses do usually come back very fast) or you can open multiple connections using each one to Originate a new call. We use the multiple connection method in the astGUIclient suite because if you get a pause or lag in Manager output on a single connection(which does happen) it will hold up all of the Actions you are trying to send after it. Take a look at the ACQS(Asterisk Central Queue System) part of the astGUIclient suite. It allows you to queue up Actions in a database and the server will send the actions to the asterisk server almost immediately. We've been using this for quite a while now and it is very reliable. MATT--- -----Original Message----- From: Stephen Owen hosted [mailto:stephen.owen@hostedtelecom.com] Sent: Wednesday, March 02, 2005 7:28 AM 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:stephenowen@iptel.org IM:stephen_owen_2001@hotmail.com
Stephen Owen hosted
2005-Mar-02 05:59 UTC
[Asterisk-Users] Asterisk Manager API - multi "Originate" cal ls
your a star thanks ----- Original Message ----- From: "mattf" <mattf@vicimarketing.com> To: "'Stephen Owen hosted'" <stephen.owen@hostedtelecom.com>; "'Asterisk Users Mailing List - Non-Commercial Discussion'" <asterisk-users@lists.digium.com> Sent: Wednesday, March 02, 2005 12:50 PM Subject: RE: [Asterisk-Users] Asterisk Manager API - multi "Originate" cal ls> Hello, > You can do either, you can send multiple Originate actions in a long line > without waiting for a response back(although the responses do usually come > back very fast) or you can open multiple connections using each one to > Originate a new call. We use the multiple connection method in the > astGUIclient suite because if you get a pause or lag in Manager output ona> single connection(which does happen) it will hold up all of the Actionsyou> are trying to send after it. > > Take a look at the ACQS(Asterisk Central Queue System) part of the > astGUIclient suite. It allows you to queue up Actions in a database andthe> server will send the actions to the asterisk server almost immediately. > We've been using this for quite a while now and it is very reliable. > > MATT--- > > > -----Original Message----- > From: Stephen Owen hosted [mailto:stephen.owen@hostedtelecom.com] > Sent: Wednesday, March 02, 2005 7:28 AM > 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 toinitiate> 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 foran> 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 willcrash> it (thinking of alternative way to crack the nut) > > All help would be welcome - thanks > > Stephen Owen > > sip:stephenowen@iptel.org > IM:stephen_owen_2001@hotmail.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 > > Spam detection software, running on the system "zeus.avanzada7.com", has > identified this incoming email as possible spam. The original message > has been attached to this so you can view it (if it isn't spam) or label > similar future email. If you have any questions, see > the administrator of that system for details. > > Content preview: Hello, You can do either, you can send multiple > Originate actions in a long line without waiting for a response > back(although the responses do usually come back very fast) or you can > open multiple connections using each one to Originate a new call. We > use the multiple connection method in the astGUIclient suite because > if you get a pause or lag in Manager output on a single > connection(which does happen) it will hold up all of the Actions you > are trying to send after it. [...] > > Content analysis details: (0.1 points, 5.0 required) > > pts rule name description > ---- ---------------------- --------------------------------------------------> 0.1 FORGED_RCVD_HELO Received: contains a forged HELO
mattf
2005-Mar-02 08:24 UTC
[Asterisk-Users] Asterisk Manager API - multi "Originate" cal ls
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/917275551212@default Context: default Priority: 1 Callerid: DF345678901234567890 Actionid: AID45678901234567890 MATT--- -----Original Message----- From: Bill Seddon [mailto:bill.seddon@lyquidity.com] 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 <http://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: asterisk-users-bounces@lists.digium.com [mailto:asterisk-users-bounces@lists.digium.com] 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:stephenowen@iptel.org IM:stephen_owen_2001@hotmail.com -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.digium.com/pipermail/asterisk-users/attachments/20050302/8dcae8bc/attachment.htm
mattf
2005-Mar-02 12:29 UTC
[Asterisk-Users] Asterisk Manager API - multi "Originate" cal ls
Well, I'm not sure about the current release as I have not tested this, but on older releases for RBS T1s you would get a manager event showing a RING state. As for PRI, SIP and IAX2 I'm not sure, this is an inconsistent feature that differes depending on what kind of trunk you are using and what network the person you are calling is on. The only sure thing you can tell is a call pickup in all cases, ringing is much harder to detect. MATT--- -----Original Message----- From: Thomas Miller [mailto:thomasamiller@rocketmail.com] Sent: Wednesday, March 02, 2005 2:15 PM To: Asterisk Users Mailing List - Non-Commercial Discussion Subject: RE: [Asterisk-Users] Asterisk Manager API - multi "Originate" cal ls Hi Matt, in your experience is there a 100% reliable way to know that the callee phone is ringing? In my situation I don't need to know if they pick up or not, I need to know (as reliably as possible) if the calee phone number is ringing. Thanks, Tom --- mattf <mattf@vicimarketing.com> wrote:> 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/917275551212@default > Context: default > Priority: 1 > Callerid: DF345678901234567890 > Actionid: AID45678901234567890 > > > MATT--- > > > -----Original Message----- > From: Bill Seddon [mailto:bill.seddon@lyquidity.com] > 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 > <http://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: asterisk-users-bounces@lists.digium.com > [mailto:asterisk-users-bounces@lists.digium.com] 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:stephenowen@iptel.org > IM:stephen_owen_2001@hotmail.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 __________________________________ Celebrate Yahoo!'s 10th Birthday! Yahoo! Netrospective: 100 Moments of the Web http://birthday.yahoo.com/netrospective/ _______________________________________________ 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