Page 1 of 1

OutBound Not Working(Not a valid Extension)

PostPosted: Wed Oct 27, 2010 7:05 am
by Moeed
GoAutoDial CE 2.0 from .iso | Vicidial 2.2.1 kernel 2.6.18-194.8.1.e15.goPAE | Asterisk 1.4.27.1-vici | Single Server | No Digium/Sangoma Hardware | No Extra Software After Installation
Dahdi 2.3
VtigerCRM 5.1.0
Sangoma 3.5.14
CentOS 5.5


I am just a newbie to vicidial. I was trying out GoAutoDial CE 2.0.
I followed out the how to get started provided and the installation went well
until the part where I tested it out. I cant make outbound calls.

I have set carrier , phone and user setup and successfully connected xlite v3.0 build 56125 with new loaded leads as well..

when the agent logs in , it calls on xlite and i can hear that you r the only one in conference. but when it dials , it gives (i m sorry that is not a valid extension)

at manual dialing, the same response appears.

PEER DETIALS
type=friend
secret=xxxxx
username=xxxxxxxx
fromuser=xxxxxxxx
fromdomain=xxxxxxxxx
host=xxxxxxxx
insecure=very
qualify=yes
dtmfmode=rfc2833
context=xxxxxxxxxxxxxxx
nat=yes (as server is behind router’s firewal)


Global String TRUNK = SIP/carriername


I read managers manual as well and tried many dial patterns but the same response....

(1)
exten => _91NXXNXXXXXX,1,AGI(agi://127.0.0.1:4577/call_log)
exten => _91NXXNXXXXXX,2,Dial(sip/${EXTEN}@SIPtrunk,55,o)
exten => _91NXXNXXXXXX,3,Hangup

(2)
_.,1,Dial(SIP/123)

(3)

exten => _X,1,AGI(agi://127.0.0.1:4577/call_log)
exten => _X,2,Dial(sip/${EXTEN}@SIPtrunk,55,o)
exten => _X,3,Hangup


My carrier is registered as i checked through cli.. the important thing is i m pretty new to asterisks and located in pakistan... have to call all over the world as have a small setup here with such a project.....


Please help me out as i m a bit sure that there is some problem with my dial plan.........
please tell me the command as well to check cli when attempting call :)

PostPosted: Wed Oct 27, 2010 4:16 pm
by williamconley
excellent first post (although you did not specify that you have read all the stickies AND the free version of the manager's manual, somehow i suspect that you have :) )

let's start here:
(1)
exten => _91NXXNXXXXXX,1,AGI(agi://127.0.0.1:4577/call_log)
exten => _91NXXNXXXXXX,2,Dial(sip/${EXTEN}@SIPtrunk,55,o)
exten => _91NXXNXXXXXX,3,Hangup

(2)
_.,1,Dial(SIP/123)

(3)

exten => _X,1,AGI(agi://127.0.0.1:4577/call_log)
exten => _X,2,Dial(sip/${EXTEN}@SIPtrunk,55,o)
exten => _X,3,Hangup
none of these are "viable":

1) missing the ":1" after EXTEN ({EXTEN:1}. This will "strip" the 9 from the number dialed (assuming you have dial prefix "9" in your campaign and the 9 was actually dialed, which we don't know, but we'll get there soon). Of course, your carrier is expecting 1NXXNXXXXXX (1 plus 10 digit us phone number which cannot start with 0 or 1 and cannot have 0 or 1 as the fourth digit, that's what the NXXNXXXXXX is about). So put in the :1 and that may fix the first one.

2) Just never do that again, not worth it. :)

3) _X represents a pattern of "singledigit" (any number, but one single digit). Not likely to fit many of the 10 digit phone numbers you are dialing.

It could be modified to _X. which would be any length of number dialed (from 1 digit to 500 digits) ... but would kill the entire system by capture ALL numbers dialed (vicidial dials many numbers to run the system, and those would be captured as well, and sent to your provider! awkward! perhaps we'll avoid that as well.)

Another (not quite so horrible) possibility is "_XXXXXXXXX." which would be any number dialed with at least 9 digits ... unfortunately this (although some try it and it may work for some basic functions) will catch some of the ... weirder vicidial programming off guard and still crash horribly when you try to use some features of vicidial later, and you'll not know why.

So ... stick with #1 and create a pattern that actually fits the numbers you are dialing. At least match the number of digits for the phone numbers you'll be dialing. If you have questions, google "asterisk dial pattern" and try to match your country's pattern as closely as possible. If it's USA: NXXNXXXXXX and you likely need the 1 in front of it. And do not forget that you will want to be able to Choose your carrier (one carrier is a recipe for disaster! you must have at least three!): so you'll want to add 9 in front and strip it off with EXTEN:1 thus starting with 91NXXNXXXXXX but sending 1NXXNXXXXXX to the carrier. Which is what I showed earlier.
___________________

If you got through that and you're eyes are not droopy: please post a single call CLI output so we know why it failed. :)

NOT 3000 lines of code, not from startup until shutdown, just the "dial command" or the first line with the number being dialed on it, ending with the "reason for failure" line. Usually less than a dozen lines. :)

PostPosted: Wed Nov 03, 2010 7:55 am
by Moeed
i did everything but the same response...........please tell me the command to check cli when attempting call ....

PostPosted: Wed Nov 03, 2010 8:42 am
by williamconley

PostPosted: Thu Nov 04, 2010 12:56 am
by boybawang
try _X. instead of _X

PostPosted: Fri Nov 05, 2010 7:50 am
by Moeed
I tried this and now it is saying sorry ur call cannot be connected , try again.....


exten => _X.,1,AGI(agi://127.0.0.1:4577/call_log)
exten => _X.,2,Dial(sip/${EXTEN}@trunk,55,o)
exten => _X.,3,Hangup

Remember, at first and on other dial patterns tried before , it is saying , not a valid extension.......

PostPosted: Fri Nov 05, 2010 8:03 am
by Moeed
I m debugging at the server and actually operating it from the different system at lan..... so i cannot copy paste the output but it is saying when i dialed a no , on the first line....ast_rtp_read RTP read too short kind of message just next to the no dialed.......

PostPosted: Fri Nov 05, 2010 9:50 am
by williamconley
trunk <> TRUNK (these are not the same thing, asterisk is CaSe SeNSiTiVe

also: _X. is a bad idea, it will capture internal calls that it should not capture.

And i note that you are discussing the cli, but have not posted any output from it. So we really are just guessing what your problem is.

Re: OutBound Not Working(Not a valid Extension)

PostPosted: Thu May 30, 2013 5:53 am
by Lighto27
Hi, im a newbie on vicidial and im having a problem on the dialplan entry too.

i created a carrier for UK but whats happening is i can call all the mobile phone numbers of UK the starting 7********* numbers

but when im trying to call landline phone numbers on UK with starting 1 or 2 numbers (total of 10 digit numbers), its always says

Error: Not a valid extension number or chanunavail or congestion


but as i can see its working properly because i can call mobile phone numbers on UK

Here's my dialplan entry

exten =>_944XXXXXXXXXX,1,AGI(agi://127.0.0.1:4577/call_log)
exten =>_944XXXXXXXXXX,2,Dial(${myvoip}/${EXTEN:44},,to)
exten =>_944XXXXXXXXXX,3,Hangup



hope i can fix this as soon as possible

Thanks for replying

Re: OutBound Not Working(Not a valid Extension)

PostPosted: Thu May 30, 2013 1:40 pm
by gerski

exten =>_944XXXXXXXXXX,1,AGI(agi://127.0.0.1:4577/call_log)
exten =>_944XXXXXXXXXX,2,Dial(${myvoip}/${EXTEN:44},,to)
exten =>_944XXXXXXXXXX,3,Hangup


it should be EXTEN:1 not EXTEN:44 as it will remove 44 numbers lolz (it will remove the first number which is in your dialplan is 9)

exten =>_944XXXXXXXXXX,1,AGI(agi://127.0.0.1:4577/call_log)
exten =>_944XXXXXXXXXX,2,Dial(${myvoip}/${EXTEN:1},,to)
exten =>_944XXXXXXXXXX,3,Hangup