vicidial.org

VERSION: 2.4-309a
BUILD: 110430-1642
Asterisk: 1.4.39.1-vici
GoAutoDial CE 2.1

When i attempt to dial out from my sip phone the asterisk log shows the following lines:

Aug 18 18:42:08] VERBOSE[2783] logger.c: [Aug 18 18:42:08] -- Registered SIP '8001' at 192.168.1.66 port 5060
[Aug 18 18:42:08] VERBOSE[2783] logger.c: [Aug 18 18:42:08] -- Saved useragent "Twinkle/1.4.2" for peer 8001
[Aug 18 18:42:08] NOTICE[2783] chan_sip.c: Peer '8001' is now Reachable. (3ms / 5000ms)
[Aug 18 18:42:15] NOTICE[2783] chan_sip.c: Call from '8001' to extension '17543681986' rejected because extension not found.

In asterisk i can see that the sip phone is registered and the status is ok. I also noticed that my sip provider (voicepulse) was not listed as a peer. On voicepulse's end it shows my ip as registered and status ok.

Since attempting to use vicidial, this is where i am continuing to get stuck. Any help would be greatly appreciated....again .

Made some changes and now my back up and primary peers from my sip provider are registered also my sip phone. All statuses OK.

Outbound calls are still being rejected. Thanks guys.

! You listed your Vicidial version (ok, without the word vicidial, but that's cool) AND your GoAutoDial installer version! Cool

Your phone is registered. Your Phone calls the vicidial system and requests a number. The Vicidial system cannot match that number with a dialable pattern in the "[default]" context in extensions-vicidial.conf, and the call fails. Show your dial plan entry for the carrier you set up.

Also, where are you in the Vicidial Manager's Manual (which has exercises for getting the system set up to avoid saying the same thing to Every New User). Of course it can get confusing, so if you get stuck somewhere ... tell us where you are in the manual and we'll walk you through. Right now you are lacking in a "path" for that call to take to exit the vicidial box.

The extensions-vicidial.conf entry will contain three lines. The first one is the agi line (this activates the Vicidial scripts and attaches them to the call so Vicidial can control the call). The second line will "dial", and the third line will hang up. ALL THREE lines must have a number or pattern match for this outbound call to activate it. Something like "_91NXXNXXXXXX" will match a number like 913512345678 ... all three lines would then start with "exten => _91NXXNXXXXXX" and would continue with a comma, the line number which sets the execution order, and then the command to execute. A mini-program (call it the dial plan language if you like).

I had a feeling that the issues had to do with the dial plan. The manager manual has provided a dial plan:

exten => _91NXXNXXXXXX,1,AGI(agi://127.0.0.1:4577/call_log)
exten => _91NXXNXXXXXX,2,Dial(newsip:test@10.10.10.15:5060/${EXTEN:2},,tTor)
exten => _91NXXNXXXXXX,3,Hangup

which lead me to try:
exten => _91NXXNXXXXXX,1,AGI(agi://192.168.1.75:4577/call_log)
exten => _91NXXNXXXXXX,2,Dial(*USER*:*PASS*@jfk-primary.voicepulse.com/${EXTEN:2},,tTor)
exten => _91NXXNXXXXXX,3,Hangup

and im currently using a dial plan from the providers configuration files:

exten => _1NXXNXXXXXX,n,Dial(SIP/+${EXTEN}@${voicepulse-primary})
exten => _1NXXNXXXXXX,n,GotoIf($[${DIALSTATUS}=CHANUNAVAIL]?${EXTEN}|GatewayB)
exten => _1NXXNXXXXXX,n(GatewayB),Dial(SIP/+${EXTEN}@${voicepulse-backup})

I've tried several different variations that ive found online but didnt get any insight from the error log to know what would need to be changed. I was actually tempted to pick up an Asterisk for Dummies book

First: You should not have your credentials/carrier info directly in the "dial" command. it can work, technically, but it leads to issues easily avoided by using a variable instead.

So you'll need the information to populate the "account entry" properly. The account entry is where the user/pass is stored, along with the rest of the information for that provider. The name inside the [xxxxx] brackets in the account entry (at the top if it, actually) is used in the declaration of the variable in "Globals String".

Globals String (taking the xxxxx sip account example from above)

Code: Select all

TRUNK9=SIP/xxxxx

Now the dial command instead of all that drama all you need is

Code: Select all

exten =>_91NXXNXXXXXX,1,AGI(agi://127.0.0.1:4577/call_log)
exten =>_91NXXNXXXXXX,2,Dial(${TRUNK9}/${EXTEN:1},,tTor)
exten =>_91NXXNXXXXXX,3,Hangup

Note that you now must dial "9" before any number you dial which selects THIS carrier, allowing for multiple carriers in a single system. This will also be your "Dial Prefix" when you set up your Campaign.

example account entry (modify to suit, based on standard asterisk rules):

Code: Select all

[xxxxx]
host=22.22.22.22
context=trunkinbound
type=friend
qualify=1000
dtmfmode=rfc2833
canreinvite=no
allow=ulaw
port=5060
nat=no

Your provider should have a sample asterisk sip context entry for you, as well as a registration string (but the registration string is fairly easy to assemble). Do not change the "context=" entry. That's only for inbound calls from the provider and needs to go where it is for vicidial to "catch" and process the calls.

That took care of it. i see what i was doing wrong now. Im having a new issue now when logging into vicidial but i see someone else is having the same issue so ill try your suggestions on there thread. Thank you!!

Now buy that Manager's Manual from Matt which will give you valuable information (and save hair pulling next week in addition to showing you some of the Power of this software) in addition to sending a little cash to the guy whose FREE software you are using. Win-Win. EFLO.net