vicidial.org

Hi Every One,
Need Help,

Following are my server details

1. Asterisk 1.4.42
2. vicidial 2.2.1
3. 4 Port Digium Card
4. Cent OS
5. Soft Phone Zoiper

Installation Method : Vicidialnow
$version = '2.2.1-259';
$build = '100510-2014';
Asterisk version: 1.4.42-vici

I am using the vicidial application from past five years, it is very nice. Suddenly in my agent application I am getting issue with outbound dialing. Most of the times the agent dialed outbound call is not getting connected, when I check the asterisk log I am unable to see the log for that number (I have kept NoOP statements in my outbound patterns.) but I am able to see that, it is routing to 8309 extension which is configured for update recordings file names.

My success case scenario is, after connected to outbound patterns, it will be redirected any of the pattern and after that the recording extension 8309 will be called.

Please help me on this. Your help will be very much appreciated.

Thanks,
Srinivas

I have analysed my issue.

AS per my analysis, I have configured recordings as ALLFORCE for my campaign. So that's why it is routing to 8309 extension.

Success Case:

Whenever user dials the number, user conference created in meetme and after that it searches for pattern and it redirects to matching pattern then the call will be routed to dialed number.

Configuration Code:

Code: Select all

[default]
exten => _86000[5-9]X,1,Meetme,${EXTEN}|q

exten => _58600XXX,1,Meetme,${EXTEN:1}|Fmq

exten => _91XXXXXXXXXX,1,AGI(agi://127.0.0.1:4577/call_log)
exten => _91XXXXXXXXXX,n,Set(test3=${EXTEN})
exten => _91XXXXXXXXXX,n,Set(str3=${test3:2:11})
exten => _91XXXXXXXXXX,n,Dial(Zap/g2/${str3},30)
exten => _91XXXXXXXXXX,n,Hangup


exten => 8309,1,Answer
exten => 8309,n,Set(FILENAME=${CALLERIDNAME})
exten => 8309,n,AGI(agi://${IP}/UpdateRecordings.agi)
exten => 8309,n,Monitor(wav,${FILENAME})
exten => 8309,n,Wait,3600
exten => 8309,n,Hangup


Success Log:

-- Executing [8600069@default:1] MeetMe("Local/8600069@default-42a8,2", "8600069|q") in new stack
> Channel Local/8600069@default-42a8,1 was answered.
-- Executing [919885098850@default:1] AGI("Local/8600069@default-42a8,1", "agi://127.0.0.1:4577/call_log") in new stack
-- AGI Script agi://127.0.0.1:4577/call_log completed, returning 0
-- Executing [919885098850@default:2] Playback("Local/8600069@default-42a8,1", "/var/UPCL/english/wel2") in new stack
-- Executing [919885098850@default:3] Set("Local/8600069@default-42a8,1", "test3=919885098850") in new stack
-- Executing [919885098850@default:4] Set("Local/8600069@default-42a8,1", "str3=9885098850") in new stack
-- Executing [919885098850@default:5] Dial("Local/8600069@default-42a8,1", "Zap/g2/9885098850|30") in new stack
-- Requested transfer capability: 0x00 - SPEECH
-- Called g2/9885098850
-- Zap/29-1 is proceeding passing it to Local/8600069@default-42a8,1
== Parsing '/etc/asterisk/manager.conf': Found
== Manager 'sendcron' logged on from 127.0.0.1
-- Executing [58600069@default:3] MeetMe("Local/58600069@default-3dd8,2", "58600069|Fmq") in new stack
> Channel Local/58600069@default-3dd8,1 was answered.
== Parsing '/etc/asterisk/meetme.conf': Found
-- Executing [8309@default:1] Answer("Local/58600069@default-3dd8,1", "") in new stack
-- Executing [8309@default:2] Set("Local/58600069@default-3dd8,1", "FILENAME=") in new stack
-- Executing [8309@default:3] NoOp("Local/58600069@default-3dd8,1", "") in new stack
-- Executing [8309@default:4] AGI("Local/58600069@default-3dd8,1", "agi://localhost/UpdateRecordings.agi") in new stack
-- <Local/58600069@default-3dd8,2> Playing 'conf-invalid' (language 'en')
-- Zap/29-1 is making progress passing it to Local/8600069@default-42a8,1
-- Zap/29-1 is making progress passing it to Local/8600069@default-42a8,1
-- Zap/29-1 is ringing


Failure Case:

With the same configuration if I dial the same number after some time it is not routing to first meetme extension in the default context.
My number is not at all routing to asterisk .

please help me.

Why no failure log?

Also, I would strongly recommend upgrading your system, we have fixed hundreds of bugs and security issues in the last 5 years.