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:[EMAIL PROTECTED] Sent: Wednesday, March 02, 2005 7:28 AM To: [email protected] 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 [email protected] http://lists.digium.com/mailman/listinfo/asterisk-users To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
