On Thu, Jul 18, 2013 at 3:40 AM, Alexander Frolkin <a...@eldamar.org.uk>wrote:
> Hi, > > > When you execute an Originate action, are you doing so synchronously or > > asynchronously? > > > > A synchronous Originate performs the full outbound dial operation on the > > thread servicing the AMI request. Since each session in AMI gets its own > > thread that services both actions and events, a synchronous Originate can > > block that session from receiving events until it completes. > > I may be misunderstanding, but would your suggestion be to open a new > AMI connection for each action? (Or at least each action that can > block.) > Not at all. The Originate action has a parameter 'async' that, when present and set to True, will not block the thread servicing the AMI session. https://wiki.asterisk.org/wiki/display/AST/Asterisk+11+ManagerAction_Originate I would suggest setting that field to True in your Originate actions. Matt -- Matthew Jordan Digium, Inc. | Engineering Manager 445 Jan Davis Drive NW - Huntsville, AL 35806 - USA Check us out at: http://digium.com & http://asterisk.org
-- _____________________________________________________________________ -- Bandwidth and Colocation Provided by http://www.api-digital.com -- New to Asterisk? Join us for a live introductory webinar every Thurs: http://www.asterisk.org/hello asterisk-users mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
