Autodialed calls hung up on once answered problem

All installation and configuration problems and questions

Moderators: gerski, enjay, williamconley, Op3r, Staydog, gardo, mflorell, MJCoate, mcargile, Kumba, Michael_N

Autodialed calls hung up on once answered problem

Postby klumix » Wed Aug 16, 2006 10:17 am

Hello, I have vicidial configured and working to the point where an agent can login and the system will begin auto dialing. Calls are going out but when the call is answered it is not transferred to the agent and appears to be hanging up. Currently strictly VOIP trunk to termination provider. No cards install using ztdummy for timing. Meetme conferences work ok when dialed in from extensions. Can you point me in the right direction.


-- Executing AGI("Local/16027502051@default-9c14,2", "call_log.agi|1602750 2051") in new stack
-- Launched AGI Script /var/lib/asterisk/agi-bin/call_log.agi
-- AGI Script call_log.agi completed, returning 0
-- Executing Set("Local/16027502051@default-9c14,2", "CALLERID(number)=480 5038553") in new stack
-- Executing Dial("Local/16027502051@default-9c14,2", "SIP/16027502051@vit el-outbound") in new stack
-- Called 16027502051@vitel-outbound
-- SIP/vitel-outbound-dd47 is making progress passing it to Local/16027502 051@default-9c14,2
-- SIP/vitel-outbound-9a57 is making progress passing it to Local/16027502 051@default-cf62,2
-- SIP/vitel-outbound-9a57 is ringing
-- SIP/vitel-outbound-9a57 answered Local/16027502051@default-cf62,2
> Channel Local/16027502051@default-cf62,1 was answered.
== Manager 'sendcron' logged off from 127.0.0.1
-- Executing AGI("Local/16027502051@default-cf62,1", "call_log.agi|8365") in new stack
-- Launched AGI Script /var/lib/asterisk/agi-bin/call_log.agi
== Spawn extension (default, 16027502051, 3) exited non-zero on 'Local/16027 502051@default-cf62,2'
-- Executing DeadAGI("Local/16027502051@default-cf62,2", "call_log.agi|h") in new stack
-- Launched AGI Script /var/lib/asterisk/agi-bin/call_log.agi
-- AGI Script call_log.agi completed, returning 0
-- Executing AGI("SIP/vitel-outbound-9a57", "agi-VDADtransfer.agi|8365") i n new stack
-- Launched AGI Script /var/lib/asterisk/agi-bin/agi-VDADtransfer.agi
-- AGI Script call_log.agi completed, returning 0
-- Executing DeadAGI("Local/16027502051@default-cf62,2", "VD_hangup.agi|PR I-----NODEBUG-----16-----ANSWER-----7-----0") in new stack
-- Launched AGI Script /var/lib/asterisk/agi-bin/VD_hangup.agi
-- AGI Script VD_hangup.agi completed, returning 0
-- SIP/vitel-outbound-dd47 answered Local/16027502051@default-9c14,2
> Channel Local/16027502051@default-9c14,1 was answered.
== Manager 'sendcron' logged off from 127.0.0.1
-- Executing AGI("Local/16027502051@default-9c14,1", "call_log.ag
klumix
 
Posts: 6
Joined: Tue Aug 08, 2006 4:37 pm

Postby mflorell » Wed Aug 16, 2006 11:36 am

You need to post Real Asteirsk CLI output(asterisk -vvvvvvvvvvvvvvvvgc), not asterisk -r output.

The issue is usually caused by your SIP trunk now being registered, or the Dial string not matching your SIP registration string.
mflorell
Site Admin
 
Posts: 18384
Joined: Wed Jun 07, 2006 2:45 pm
Location: Florida

Postby klumix » Wed Aug 16, 2006 3:08 pm

Ok here is the out put. FYI i just tried it with autodial set to 0 so that agent must manully press dial etc. and the call connects properly. But not with autodial which is what i would prefer to use.


== Manager 'sendcron' logged on from 127.0.0.1
-- Executing AGI("Local/16027502051@default-78d8,2", "call_log.agi|16027502051") in new stack
-- Launched AGI Script /var/lib/asterisk/agi-bin/call_log.agi
+++++ CALL LOG START : |1155758164.6|Local/16027502051@default-78d8,2|16027502051|Local|V0816125604000000024|2006-08-16 12:56:04
-- AGI Script call_log.agi completed, returning 0
-- Executing Set("Local/16027502051@default-78d8,2", "CALLERID(number)=4805038553") in new stack
-- Executing Dial("Local/16027502051@default-78d8,2", "SIP/16027502051@vitel-outbound") in new stack
-- Called 16027502051@vitel-outbound
== Parsing '/etc/asterisk/manager.conf': Found
== Manager 'updatecron' logged on from 127.0.0.1
-- SIP/vitel-outbound-10c5 is making progress passing it to Local/16027502051@default-78d8,2
-- SIP/vitel-outbound-10c5 answered Local/16027502051@default-78d8,2
> Channel Local/16027502051@default-78d8,1 was answered.
== Manager 'sendcron' logged off from 127.0.0.1
-- Executing AGI("Local/16027502051@default-78d8,1", "call_log.agi|8365") in new stack
-- Launched AGI Script /var/lib/asterisk/agi-bin/call_log.agi
== Spawn extension (default, 16027502051, 3) exited non-zero on 'Local/16027502051@default-78d8,2'
-- Executing DeadAGI("Local/16027502051@default-78d8,2", "call_log.agi|h") in new stack
-- Launched AGI Script /var/lib/asterisk/agi-bin/call_log.agi
+++++ CALL LOG START : |1155758164.5|Local/16027502051@default-78d8,1|8365|Local|V0816125604000000024|2006-08-16 12:56:11
-- AGI Script call_log.agi completed, returning 0
-- Executing AGI("SIP/vitel-outbound-10c5", "agi-VDADtransfer.agi|8365") in new stack
-- Launched AGI Script /var/lib/asterisk/agi-bin/agi-VDADtransfer.agi
+++++ CALL LOG HUNGUP: |1155758164.6|Local/16027502051@default-78d8,2|h|2006-08-16 12:56:11|min: 0.12|
-- AGI Script call_log.agi completed, returning 0
-- Executing DeadAGI("Local/16027502051@default-78d8,2", "VD_hangup.agi|PRI-----NODEBUG-----16-----ANSWER-----7-----0") in new stack
-- Launched AGI Script /var/lib/asterisk/agi-bin/VD_hangup.agi
Perl Environment Dump:
0|8365|
AGI Environment Dump:
-- accountcode =
-- callerid = 16027502051
-- calleridname = unknown
-- callingani2 = 0
-- callingpres = 0
-- callingtns = 0
-- callington = 0
-- channel = SIP/vitel-outbound-10c5
-- context = default
-- dnid = unknown
-- enhanced = 0.0
-- extension = 8365
-- language = en
-- priority = 2
-- rdnis = unknown
-- request = agi-VDADtransfer.agi
-- type = SIP
-- uniqueid = 1155758164.5
AGI Environment Dump: |1155758164.5|SIP/vitel-outbound-10c5|8365|SIP|16027502051|unknown|2|

CALL RECEIVED IN FROM VDAD: 16027502051 SIP/vitel-outbound-10c5 2
+++++ VDAD START : |1155758164.5|SIP/vitel-outbound-10c5|8365|SIP|16027502051|0|2006-08-16 12:56:12||2|
-- VDAD : |0|update of vac table: 16027502051
|UPDATE vicidial_auto_calls set uniqueid='1155758164.5', channel='SIP/vitel-outbound-10c5',status='LIVE' where callerid='16027502051' order by call_time desc limit 1;|


|SELECT count(*) FROM vicidial_auto_calls where status = 'LIVE' and server_ip='192.168.1.100' and campaign_id = '' and call_time < "" and lead_id != '';|
-- VDAD get agent: |0|update of vla table: |192.168.1.100
|UPDATE vicidial_live_agents set status='QUEUE',lead_id='0',uniqueid='1155758164.5', channel='SIP/vitel-outbound-10c5', callerid='16027502051' where status = 'READY' and server_ip='192.168.1.100' and campaign_id='' and last_update_time > '19691231165955' limit 1;|
Perl Environment Dump:
0|PRI-----NODEBUG-----16-----ANSWER-----7-----0|
AGI Environment Dump:
-- accountcode =
-- callerid = 4805038553
-- calleridname = V0816125604000000024
-- callingani2 = 0
-- callingpres = 0
-- callingtns = 0
-- callington = 0
-- channel = Local/16027502051@default-78d8,2
-- context = default
-- dnid = unknown
-- enhanced = 0.0
-- extension = h
-- language = en
-- priority = 2
-- rdnis = unknown
-- request = VD_hangup.agi
-- type = Local
-- uniqueid = 1155758164.6
AGI Environment Dump: |1155758164.6|Local/16027502051@default-78d8,2|h|Local|V0816125604000000024|V0816125604000000024|2|

DEBUG: NODEBUG

VD_hangup : V0816125604000000024 Local/16027502051@default-78d8,2 2
+++++ VD hangup START : |1155758164.6|Local/16027502051@default-78d8,2|h|Local|V0816125604000000024|24|2006-08-16 12:56:12||2|V0816125604000000024|
-- VDhangup Local DEBUG: |PRI|V0816125604000000024|ANSWER|16|
+++++ VDAD START LOCAL CHANNEL: EXITING- 2
-- AGI Script VD_hangup.agi completed, returning 0



klumix
 
Posts: 6
Joined: Tue Aug 08, 2006 4:37 pm

Postby mflorell » Wed Aug 16, 2006 3:22 pm

Looks like you don't have the 'o' flag on your Dial function in extensions.conf.

Add that and try again.
mflorell
Site Admin
 
Posts: 18384
Joined: Wed Jun 07, 2006 2:45 pm
Location: Florida

o flag it is

Postby klumix » Wed Aug 16, 2006 4:04 pm

that worked thanks
klumix
 
Posts: 6
Joined: Tue Aug 08, 2006 4:37 pm

Postby klumix » Wed Aug 16, 2006 4:22 pm

is there anything else in the dial plan that requires the o flag to work properly with vicidial? I'm going through and testing it all out. Just curious may save me some headache.
klumix
 
Posts: 6
Joined: Tue Aug 08, 2006 4:37 pm

Postby mflorell » Wed Aug 16, 2006 4:27 pm

any outbound line dialing extens that VICIDIAL would use need the 'o' flag, it is because the CallerID is changed to the number dialed out as soon as the call is placed. For some reason that's an Asterisk "feature" so they created the "o" flag to disable the feature.
mflorell
Site Admin
 
Posts: 18384
Joined: Wed Jun 07, 2006 2:45 pm
Location: Florida


Return to Support

Who is online

Users browsing this forum: Google [Bot] and 74 guests