Geoff Karl wrote:
> Thanks Matt, that is a good strategy.
>
> Any idea on how to pass the reason a call failed back through the
> Asterisk Manager Interface? It would be great to send something back
> like Busy, NoAnswer, etc...
You could use the dialstatus variable. Bear that if you were usin
On 8/28/05, Matt Riddell <[EMAIL PROTECTED]> wrote:
> Steve Edwards wrote:
> >> Normally the way I do it is to program the failover into the dialplan
> >> and then
> >> send the call to Local/[EMAIL PROTECTED] to initiate it.
> >
> > How about a snippet? (Local channels somewhat escape me.)
>
> Ok
Steve Edwards wrote:
>> Normally the way I do it is to program the failover into the dialplan
>> and then
>> send the call to Local/[EMAIL PROTECTED] to initiate it.
>
> How about a snippet? (Local channels somewhat escape me.)
Ok,
If you had something like this (we're assuming +101 jumping for
Normally the way I do it is to program the failover into the dialplan and then
send the call to Local/[EMAIL PROTECTED] to initiate it.
How about a snippet? (Local channels somewhat escape me.)
On Mon, 29 Aug 2005, Matt Riddell wrote:
Geoff Karl wrote:
I am currently using the Manager API to
Geoff Karl wrote:
> I am currently using the Manager API to place a few calls. I have more than
> one VSP available.
>
> I was wondering how to best tell a call failed to move on to the next VSP.
>
> I see messages like this, which is an obvious failure, and I would then move
> on to the next V
I am currently using the Manager API to place a few calls. I have more than one VSP available.
I was wondering how to best tell a call failed to move on to the next VSP.
I see messages like this, which is an obvious failure, and I would then move on to the next VSP.
Event: Hangup
Cause: 3
Cause
