Upgraded to vici 2.2 & vtiger 5.1 do I upgrade asterisk

[TritenTech]

Hi everyone. I have a quick question. I have just upgraded from 2.0.5 to the newer 2.2 svn vici. I have upgraded and loaded the newest vtiger 5.1. Vicidial seems to be running fine and doing what I need it to. Vtiger is up and running. Do I need to upgrade asterisk as well? I am running asterisk 1.2.302. I do not want to have the two intergrated but would like them to both use the same asterisk engine. Registering two different extensions with the softphone. One for vici and the other for Vtiger click to call. Everything is on one server using sip trunking. Has anyone done this without having to upgrade asterisk.

Thanks in advance

[gardo]

If it's working fine for you (Asterisk 1.2.30.2) then there really is no need to upgrade it. Vicidial (and Vtiger) works fine on that particular version. In our experience the 1.2.30.X is one of the most stable Asterisk version there is.

[williamconley]

i gotta ask: what makes you think you need to change anything if everything is working (curious, not being rude! really!)

[TritenTech]

I am geting the invalid extension playback when I click to dial in Vtiger. The cli message show the following. Could someone point me in the right direction to fix this.

Thanks



[Aug 11 09:40:21] == Manager 'cron' logged on from 192.168.1.111
[Aug 11 09:40:22] == Manager 'cron' logged off from 192.168.1.111
[Aug 11 09:40:29] > Channel SIP/cc130-089696d8 was answered.
[Aug 11 09:40:29] == Starting SIP/cc130-089696d8 at default,(619) 294-2707,1 failed so falling back to exten 's'
[Aug 11 09:40:29] == Starting SIP/cc130-089696d8 at default,s,1 still failed so falling back to context 'default'
[Aug 11 09:40:29] -- Sent into invalid extension 's' i n context 'default' on SIP/cc130-089696d8
[Aug 11 09:40:29] -- Executing Playback("SIP/cc130-089696d8", "invalid") in new stack
[Aug 11 09:40:29] -- Playing 'invalid' (language 'en')
[Aug 11 09:40:43] -- Executing DeadAGI("SIP/cc130-0896 96d8", "agi://127.0.0.1:4577/call_log--HVcauses--PRI-----NODEBUG-----16---------------") in new stack
[Aug 11 09:40:43] -- AGI Script agi://127.0.0.1:4577/c all_log--HVcauses--PRI-----NODEBUG-----16--------------- completed, returning 0

[williamconley]

Starting SIP/cc130-089696d8 at default,(619) 294-2707,1

the phone number can ONLY have digits in it, no parens or dashes and should also have your dial prefix (9) and the dial code (1) depending on your dialplan.

[TritenTech]

Thanks Bill you were right (of Course), When I add a 91 and take out the () and - from the numbers in Vtiger the call connected as needed. So how can I add this into the dialplan and not have to add a 91 in front of all the numbers.


exten => _NXXNXXXXXX,1,AGI(agi://127.0.0.1:4577/call_log)
exten => _NXXNXXXXXX,2,Dial(${voipms}/${EXTEN:1},,tTo)
exten => _NXXNXXXXXX,3,Hangup

[williamconley]

i would recommend adding 91 to the front of your numbers in the click-to-dial instead, but you could also post your "dial plan" from the "Admin->Carrier" for the carrier you want to use and we could give you a modified version with "no 9 or 1 required" to dial in addition to the existing dial plan.

given the odds adding the sample you have above to the existing dial plan would work.