I guess this was a question for Alexander. As far as I am concerned, I never had such a load
that slowed down AMI event processing (responses within at most 1/10 of a second), but for
future tests I should probably set up a real torture test.
For a robust PBX application, it would make sense to have an "event" thread and separate
"action" threads that handle actions and associated events. I think I see your point, Matt.
Thanks for all the fish.
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.
Matt
--
_____________________________________________________________________
-- 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
