Frustrated

[kdc]

Hi all,

Some time ago I tried to set up Vicidial and I've tried again, and I'm running into several issues. I've managed a VICIDial system before, but never built one, so I'm at a loss for some issues. I have some knowledge of Linux, but I am no master.

I have used the Vicibox installation ISO, and I have Vicidial version 2.6-354c, build 121029-0122.

I am using vitelity.com as a provider, and have pasted in their support code for sip.conf and extensions.conf. I have the webGUI successfully working, but not much beyond that.

(Please note I have changed the telephone numbers below)

My issues are:

1) When I dial in on my DID number assigned through Vitelity, I get a connect and disconnect without ringing. Here is what the asterisk log on high verbosity says.

[Nov 4 22:19:47] -- Executing [2269991122@inbound:1] Answer("SIP/vitel-inbound-00000007", "") in new stack
[Nov 4 22:19:47] -- Executing [2269991122@inbound:2] Answer("SIP/vitel-inbound-00000007", "") in new stack
[Nov 4 22:19:47] == Auto fallthrough, channel 'SIP/vitel-inbound-00000007' status is 'UNKNOWN'

2) I have a SNOM 300 hard phone, which I have set up as an extension on the Vicidial GUI. When I try to make an outbound call, it says the number I am calling is not found. Here is what the asterisk log on high verbosity says:

[Nov 4 22:22:31] NOTICE[2617]: chan_sip.c:15804 handle_request_invite: Call from '285' to extension '91228881133' rejected because extension not found.

3) I have tried to load a test campaign to force outbound through a broadcast campaign to test the lines, but I cannot force the hopper to load the leads (and thus cannot log in a user without leads in the campaign).

Can anyone offer advice, or professional services to get me off the ground?

Thanks,

J.

[williamconley]

when setting up an account for a provider, you cannot use their setup routines. do not alter any .conf files on your server directly.

all configuration is performed in the vicidial gui.

there are "sample" carrier settings provided under Admin->Carriers, but you have to change the "extension" to something similar to _91NXXNXXXXXX for outbound and put in a "context=trunkinbound" for inbound calls to work.

also: if you search this forum (with google which has a better algorithm for searching than phpBB does) for NXXNXXXXXX you will likely find quite a few sample dialplans, including specifically for vitelity (searching for that string plus vitelity plus vicidial may just hit it on the head).

Please remember to post the Version of your installation .iso CD (the filename generally contains this, so just posting the filename will usually suffice). This comes in handy during support.

Welcome to the Party!

[kdc]

Hi William -- thanks for responding!

When I last managed a much older version of Vicidial, and we didn't have the GUI paste option a few years back.

OK ... if I'm working through the GUI, and I want to tackle my inbound issue for now. I want any inbound call to ring to my SIP phone (Extension 285). I have pasted into the carrier information (replacing our password key):

REGISTRATION STRING:
register => kdc:PASSWORD@inbound24.vitelity.net:5060

TEMPLATE SETTING:
SIP Generic

ACCOUNT ENTRY:
[vitel-inbound]
type=friend
dtmfmode=auto
host=inbound24.vitelity.net
context=inbound
username=kdc
secret=PASSWORD
allow=all
insecure=port,invite
canreinvite=no

[vitel-outbound]
type=friend
dtmfmode=auto
host=outbound.vitelity.net
username=kdc
fromuser=kdc
secret=PASSWORD
trustrpid=yes
sendrpid=yes
allow=all
canreinvite=no
nat=yes
context=outbound

GLOBALS STRING:
COLLECTORS = SIP/285

DIALPLAN ENTRY:
(I don't have anything to paste here -- should I?)

[williamconley]

first be sure you get activity in the asterisk cli during an inbound call attempt. if that is not working, you MUST tackle that before anything else. I have already posted a rather lengthy explanation of that today, so "google is your friend" or just wander around the forum until you find one (which may or may not be mine from today).

after you have asterisk cli activity during the inbound attempt, you need:

context=trunkinbound for all "account entries". inbound or outbound makes no difference (because there is no context= entry for outbound)

that's it. then the call is turned over to the vicidial scripts and the gui settings take over (and that is what the manager's manual is for ... how to set the DID to route to wherever you want it).