asterisk users - Sep 2012 - Peculiar problem with failover provision.

I have noticed a peculiar problem recently with the way that the 
failover operates in my dialplan.

I normally have:

	1,Dial(SIP/<provider-1>/extension)
	n,Dial(SIP/<provider-2>/extension)

(or something similar).

This has up until now worked flawlessly.

If there is an error with the first provider, the call is completed with 
the second one.

Now, what is happening is, if the remote party hags up first, then the 
call progresses to the next priority and re-dials them.

Is this a change in default behaviour?
Do I need to add a particular flag / config directive to my dialplan

I am running Asterisk 10.6.0.

Thanks for any help in solving this.

Why not use the DIALSTATUS channel variable to determine if a fail over is
necessary?

- Logan
On Sep 24, 2012 6:00 AM, "Thomas Kenyon" <digium at
sanguinarius.co.uk> wrote:
> I have noticed a peculiar problem recently with the way that the failover
> operates in my dialplan.
>
> I normally have:
>
>         1,Dial(SIP/<provider-1>/**extension)
>         n,Dial(SIP/<provider-2>/**extension)
>
> (or something similar).
>
> This has up until now worked flawlessly.
>
> If there is an error with the first provider, the call is completed with
> the second one.
>
> Now, what is happening is, if the remote party hags up first, then the
> call progresses to the next priority and re-dials them.
>
> Is this a change in default behaviour?
> Do I need to add a particular flag / config directive to my dialplan
>
> I am running Asterisk 10.6.0.
>
> Thanks for any help in solving this.
>
> --
> ______________________________**______________________________**_________
> -- 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<http://lists.digium.com/mailman/listinfo/asterisk-users>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://lists.digium.com/pipermail/asterisk-users/attachments/20120924/9aa34397/attachment.htm>

You are doing it wrong.  I know 50 bazillion Asterisk dialplan examples on the
internet do it the same way.  It is still wrong.

When you do a Dial on the dialplan you need check the value of DIALSTATUS or
HANGUPCAUSE before dialing again.  Both variables will give you some indication
of why the first call ended.  Then your dialplan logic can decide how to
proceed.

-----Original Message-----
From: asterisk-users-bounces at lists.digium.com [mailto:asterisk-users-bounces
at lists.digium.com] On Behalf Of Thomas Kenyon
Sent: Monday, September 24, 2012 7:00 AM
To: asterisk-users at lists.digium.com
Subject: [asterisk-users] Peculiar problem with failover provision.

I have noticed a peculiar problem recently with the way that the failover
operates in my dialplan.

I normally have:

	1,Dial(SIP/<provider-1>/extension)
	n,Dial(SIP/<provider-2>/extension)

(or something similar).

This has up until now worked flawlessly.

If there is an error with the first provider, the call is completed with the
second one.

Now, what is happening is, if the remote party hags up first, then the call
progresses to the next priority and re-dials them.

Is this a change in default behaviour?
Do I need to add a particular flag / config directive to my dialplan

I am running Asterisk 10.6.0.

Thanks for any help in solving this.

--
_____________________________________________________________________
-- 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