Page 1 of 1

Problem With Vtiger-vicidial

PostPosted: Tue Mar 18, 2014 7:01 pm
by lelloXD
hi ,
my vicidial works good at 100% but
i configure the click-to-dial on vtiger after i click on a lead's number my softphone ring but when i answer a voice says : "Sorry this is not a valid extension ...".
where can be the problem?

thanks

Re: Problem With Vtiger-vicidial

PostPosted: Wed Mar 19, 2014 5:14 am
by boybawang
check dialplan

Re: Problem With Vtiger-vicidial

PostPosted: Wed Mar 19, 2014 7:49 am
by lelloXD
how can i do it ?
sorry im kinda Newbie..

Re: Problem With Vtiger-vicidial

PostPosted: Wed Mar 19, 2014 11:00 am
by williamconley
1) Welcome to the Party! 8-)

2) As you are obviously new here, I have some suggestions to help us all help you:

When you post, please post your entire configuration including (but not limited to) your installation method and vicidial version with build.

This IS a requirement for posting along with reading the stickies (at the top of each forum) and the manager's manual (available on EFLO.net, both free and paid versions)

You should also post: Asterisk version, telephony hardware (model number is helpful here), cluster information if you have one, and whether any other software is installed in the box. If your installation method is "from scratch" you must post your operating system and should also post the .iso version from which you installed your original operating system. If your installation is "Hosted" list the site name of the host.

If this is a "Cloud" or "Virtual" server, please note the technology involved along with the version of that techology (ie: VMware Server Version 2.0.2). If it is not, merely stating the Motherboard model # and CPU would be helpful.

Similar to This:

Vicibox X.X from .iso | Vicidial X.X.X-XXX Build XXXXXX-XXXX | Asterisk X.X.X | Single Server | No Digium/Sangoma Hardware | No Extra Software After Installation | Intel DG35EC | Core2Quad Q6600

3) In your case, you should also include your vTiger information (version with installation method) and confirm your vicidial configuration for vTiger integration is set up and syncs users successfully (if you're using that).

4) For technical support, we'll need to know what is happening (technically). The best way to start showing this is to post the Asterisk CLI output from an attempt and be sure to explain (button for button) what you pushed on which web page in which application to make this happen.

Re: Problem With Vtiger-vicidial

PostPosted: Wed Mar 19, 2014 11:38 am
by lelloXD
Asterisk Version 1.4
Single Server
Vtigercrm 5.4.0
Vicidial version 2.7-401a

the console output its :
[Mar 19 17:35:40] == Parsing '/etc/asterisk/manager.conf': [Mar 19 17:35:40] Found
[Mar 19 17:35:40] == Manager '1000' logged on from 127.0.0.1
[Mar 19 17:35:41] == Manager '1000' logged off from 127.0.0.1
[Mar 19 17:35:44] > Channel SIP/8012-0000000e was answered.
[Mar 19 17:35:44] == Starting SIP/8012-0000000e at default,3204691855,1 failed so falling back to exten 's'
[Mar 19 17:35:44] == Starting SIP/8012-0000000e at default,s,1 still failed so falling back to context 'default'
[Mar 19 17:35:44] -- Sent into invalid extension 's' in context 'default' on SIP/8012-0000000e
[Mar 19 17:35:44] -- Executing [i@default:1] Playback("SIP/8012-0000000e", "invalid") in new stack
[Mar 19 17:35:44] -- <SIP/8012-0000000e> Playing 'invalid' (language 'en')
[Mar 19 17:35:48] == Auto fallthrough, channel 'SIP/8012-0000000e' status is 'UNKNOWN'
[Mar 19 17:35:48] -- Executing [h@default:1] DeadAGI("SIP/8012-0000000e", "agi://127.0.0.1:4577/call_log--HVcauses--PRI-----NODEBUG-----16---------------") in new stack
[Mar 19 17:35:48] -- AGI Script agi://127.0.0.1:4577/call_log--HVcauses ... ---------- completed, returning 0
[Mar 19 17:36:02] == Parsing '/etc/asterisk/manager.conf': [Mar 19 17:36:02] Found

THANKS

if you need more information just ask

Re: Problem With Vtiger-vicidial

PostPosted: Thu Mar 20, 2014 7:59 am
by williamconley
Starting SIP/8012-0000000e at default,3204691855,1 failed so falling back to exten 's'

You do not have a "dialplan entry" in "Admin->Carriers" with a dial pattern matching "3204691855". So this fails instead of calling. Modify your click-to-dial settings to make this match your dialplan entry's dial pattern OR modify your dial pattern to match this number pattern. For instance if you have "91NXXNXXXXXX" you would cause the click to dial to add "91" in front of the phone number to match the pattern. Or you could modify the pattern to match the number. If you post your dialplan entry, we can help modify it to allow this number to dial successfully through the existing carrier.

Be careful making changes in there, do not lose your working configuration ... 8-)

Re: Problem With Vtiger-vicidial

PostPosted: Thu Mar 20, 2014 2:16 pm
by lelloXD
i need to modify the dial plan in vicidial or its a setting in vtiger?
this is vicidial configuration :
disallow=all
allow=gsm
type=friend
dtmfmode=rfc2833
context=trunkinbound
qualify=yes
insecure=very
nat=yes
host=sip1.iplabs.it
username=*****
secret=****
allow=alaw

Re: Problem With Vtiger-vicidial

PostPosted: Fri Mar 21, 2014 10:44 pm
by williamconley
If you know how to do one of those two, do it. Either will work if you know how to do it.

Hint: it is in NO way related to the "account entry" field of any carrier in Vicidial. It IS related to the "dialplan entry" field.

Re: Problem With Vtiger-vicidial

PostPosted: Sat Mar 22, 2014 5:09 am
by lelloXD
all i need to do is edit extensions.conf right?

Re: Problem With Vtiger-vicidial

PostPosted: Sun Mar 23, 2014 3:08 pm
by williamconley
Do not ever edit a ".conf" file. If you have done so, you are quite likely going to regret it.

The phrase I used was:

Code: Select all
 It IS related to the "dialplan entry" field

Modifying this field is a way to modify the extensions built by extensions.conf, but without modifying the file directly.

Extensions.conf includes several other .conf files in asterisk when it is loaded (with its own language methodology of "#include ..."). One of those included files is created by Vicidial.

Modifying the dialplan entry will cause Vicidial to modify the extensions-vicidial.conf. So you get the same result WITHOUT the danger of permanently breaking Vicidial but WITH the likelihood that an upgrade will still work (without losing your customizations).