Peculiar Problem With Failover Provision.

Home » Asterisk Users » Peculiar Problem With Failover Provision.
Asterisk Users 4 Comments

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

I normally have:

1,Dial(SIP//extension)
n,Dial(SIP//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.

4 thoughts on - Peculiar Problem With Failover Provision.

  • 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—

  • I think a lot of people leave it out in examples for simplicity’s sake. It doesn’t instil proper practices in folks’ heads.

    – Logan

  • Eric Wieling wrote:

    Thanks for your help.

    In previous versions of asterisk it worked, and iirc after the called party hung up, the dialplan only progressed if there was a particular flag used with Dial (g?).

    It’s going to cause a heck of a headache but I’ll look into doing this properly in the week.