Thanks all for the suggestions.
1) ActionID. I was not using, so that could definitely have helped.
2) I was using Async already.
3) I changed to open multiple AMI connections - Worked like a champ.
4) Used to use call files but slow to first action... So changed to AMI
long time ago.
Thanks,
On 3/12/19 11:03 AM, Steve Edwards wrote:
On Mon, 11 Mar 2019, Jerry Geis wrote:
If I use the AMI interface to originate a call, close the connection,
open another connection etc...This works. but is slow...
Would opening multiple AMI connections be an option?
You should be able to
On Mon, 11 Mar 2019, Jerry Geis wrote:
If I use the AMI interface to originate a call, close the connection,
open another connection etc...This works. but is slow...
Would opening multiple AMI connections be an option?
--
Thanks in advance,
Hello,
since ipv6 doesn't really push ipv4 out of our networks, we still use
IAX (when possible) to not face NAT problems from SIP, Asterisk 16 included.
Question is, what is the future of IAX. Is it a dead protocol ? Will it
stay as is even only security problems resolved ? Will be (sooner
On Tue, Mar 12, 2019, at 3:05 AM, Stefan Viljoen wrote:
> Hi Joshua
>
> Does the survey imply that there are big changes coming for Asterisk?
>
> E. g. features or facilities will be dropped / deprecated from the open
> source version in new releases, big changes to existing facilities /
>
On Tuesday 12 March 2019 at 01:19:37, Jerry Geis wrote:
> Lets say I have to make 40 phone calls quickly.
>
> If I use the AMI interface to originate a call, close the connection, open
> another connection etc...
> This works. but is slow...
How about using call files instead?
Hi Joshua
Does the survey imply that there are big changes coming for Asterisk?
E. g. features or facilities will be dropped / deprecated from the open source
version in new releases, big changes to existing facilities / protocols, what
is supported officialy by Digium for the official
