Page 1 of 1

Failover Dialplan

PostPosted: Thu Jun 13, 2019 2:57 pm
by rameez.amjad4
Good Day,
I am trying to use failover dialplan for 3 carriers by some how it is not working please check and update about mistake, Thanks.

System Settings:
Version: 2.14b0.5
SVN Version: 3112
DB Schema Version: 1571
DB Schema Update Date: 2019-06-12 15:13:18
Password Encryption: DISABLED - S1 - C1
Auto User-add Value: 101
Recording Prompt Count: 0
Install Date: 2019-06-12

Current Failover Dialplan Settings:

Account Entry: Empty

Protocol: Sip

Globals String: Failover=SIP/Failover

Dialplan Entry:

exten => _21X.,1,AGI(agi://127.0.0.1:4577/call_log)
exten => _21X.,n,Set(CALLERID(num)=${EXTEN:1:6}${RAND(10001,99999)})
exten => _21X.,n,Dial(SIP/${EXTEN:1}@AAA,,tTo)
exten => _21X.,n,Dial(SIP/${EXTEN:1}@BBB,,tTo)
exten => _21X.,n,Dial(SIP/${EXTEN:1}@CCC,,tTo)
exten => _21X.,n,Hangup

I have these dialplans in CARRIER listings active, but when i use failover dialplan with dial prefix 2 it only sends calls to
exten => _21X.,n,Dial(SIP/${EXTEN:1}@AAA,,tTo)
not to
exten => _21X.,n,Dial(SIP/${EXTEN:1}@BBB,,tTo) OR exten => _21X.,n,Dial(SIP/${EXTEN:1}@CCC,,tTo)

Failover is not working.

Please check and update, Thanks.

Re: Failover Dialplan

PostPosted: Thu Jun 13, 2019 3:13 pm
by williamconley
1) While you did post some of your Vicidial Version, you left off the BUILD. It is a requirement to post the Full Vicidial Version Including Build to get free support on this site.

2) You should also post your installation CD name with version, and a link to the installation instructions if that is not a Vicidial .iso installer.

3) you left out a key point: did the call to AAA fail? If so .. how? Remember that "answer, terminate" is NOT a fail. Once a call has hit "answer" it leaves this dialplan entirely and switches to the Campaign Routing Extension instead. If you did not get a "human answer", there is a method in Vicidial to call alternate numbers for this lead or (of course) you can set the dispo_url or no_agent_url to make this lead dialable again, but "not a human answer" is not the same as "failover", different concept entirely.

4) Set(CALLERID(num)=${EXTEN:1:6}${RAND(10001,99999)}? seriously? If you're in the US, I honestly hope the FCC hunts you down. Better method: Vicidial campaigns can have a custom caller ID which can be set "per area code" or "per lead". In other words, you can set the caller ID for each call to a specific number based on what you uploaded with the lead. If you use a random number generator there, people like me won't see it in the dialplan and become annoying. Or you could rotate through numbers you actually own instead. Avoid that Federal inconvenience with the badges and such.

Re: Failover Dialplan

PostPosted: Fri Jun 14, 2019 1:07 pm
by rameez.amjad4
Here is the Iso Name: ViciBox_v.7.x86_64-7.0.4.iso
Download Link: http://download.vicidial.com/iso/vicibo ... -7.0.4.iso

An this is vicidial not any other software.

Re: Failover Dialplan

PostPosted: Fri Jun 14, 2019 1:14 pm
by williamconley
williamconley wrote:1) While you did post some of your Vicidial Version, you left off the BUILD.


williamconley wrote:3) you left out a key point: did the call to AAA fail? If so .. how? Remember that "answer, terminate" is NOT a fail. Once a call has hit "answer" it leaves this dialplan entirely and switches to the Campaign Routing Extension instead. If you did not get a "human answer", there is a method in Vicidial to call alternate numbers for this lead or (of course) you can set the dispo_url or no_agent_url to make this lead dialable again, but "not a human answer" is not the same as "failover", different concept entirely.