B.H.
Hello, i'm using AMI Originate action (with async=true) to send outgoing
calls to a SIP trunk (using asterisk-java library to connect to AMI).
The problem is that in case of failed originate, OriginateResponse event is
returning only the reason code which is sometimes not sufficient to
deter
You can use AMI Commands and run sip set debug from that you have to
capture the response code.
http://www.voip-info.org/wiki/view/Asterisk+Manager+API+Action+Command
Regards,
On Thu, Aug 22, 2013 at 10:43 PM, Mordechay Kaganer wrote:
> B.H.
>
> Hello, i'm using AMI Originate action (with asyn
On 22/08/13 15:43, Mordechay Kaganer wrote:
B.H.
Hello, i'm using AMI Originate action (with async=true) to send
outgoing calls to a SIP trunk (using asterisk-java library to connect
to AMI).
The problem is that in case of failed originate, OriginateResponse
event is returning only the reas
B.H.
Thanks for your response
On Aug 23, 2013 11:21 AM, "Gareth Blades"
wrote:
>
> On 22/08/13 15:43, Mordechay Kaganer wrote:
>>
>> B.H.
>>
>> Hello, i'm using AMI Originate action (with async=true) to send outgoing
calls to a SIP trunk (using asterisk-java library to connect to AMI).
>>
>> The
On 23/08/13 10:44, Mordechay Kaganer wrote:
In my experience with local channels, they cause a huge performance
problems, even without sipstorecause. We are dialing on about 100
channels in parallel and looks like this will kill my CPU :-)
Really?
We had Asterisk 1.8 with this setup and pushe
