vicidial.org

we did a new install of vici VERSION: 2.12-538a BUILD: 160122-1401 and have a cluster set up with webserver on one and asterisk on the other 2. I copied the dialplans and carriers from the original vici and when trying to make a call i get "thats not a valid extention"

here is my dialplan



exten => _NXXNXXXXXX,1,AGI(agi://127.0.0.1:4577/call_log)
exten => _NXXNXXXXXX,n,Dial(SIP/Voipesst/1${EXTEN},,tTo)
exten => _NXXNXXXXXX,n,Hangup

exten => _1NXXNXXXXXX,1,AGI(agi://127.0.0.1:4577/call_log)
exten => _1NXXNXXXXXX,n,Dial(SIP/Voipesst/${EXTEN:1},,tTo)
exten => _1NXXNXXXXXX,n,Hangup

exten => _7NXXNXXXXXX,1,AGI(agi://127.0.0.1:4577/call_log)
exten => _7NXXNXXXXXX,n,Dial(SIP/Voipesst/7291${EXTEN:1},,tTo)
exten => _7NXXNXXXXXX,n,Hangup

1) You should include your installation method with version. Good job including your Vicidial version with build. A lot of people forget that.

2) Your first and second dialplan segments compete. The first one puts in a "1" if it was omitted. The second one omits the "1" if it was included. Seems like you should either send the "1" or not based on your carrier's expectation, not just switch to whichever one disagrees with what the caller dialed. LOL.

3) Your third dialplan segment adds "7291" in front of any dialed number matching 7NXXNXXXXXX after removing the 7, resulting in 7291NXXNXXXXXX. Also an oddity and may not mesh with the requirements of your carrier.

4) MOST importantly, however, is the fact that you did not bother to post the actual error problem. You posted a summary of how you interpreted an error message. What you should always post is both the actual error message (the whole line) and the line that caused the error message. Sometimes a few lines above it just to be sure. Otherwise, we're just guessing.

5) While we're here: "This is my dialplan" is also inaccurate. That would appear to be your "Dialplan Entry" for a specific carrier which may or may not be active. In situations like this it is usually best to post the entire Carrier entry (change any ID/Password/IP information to fakes ... "User" "Password" "xxx.xxx.xxx.xxx" instead ... if those are in any way security risks to release).