FILE CALL_LOG.AGI

All installation and configuration problems and questions

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

FILE CALL_LOG.AGI

Postby Freddy_rixcom » Fri Feb 15, 2008 7:24 am

Hi everybody!
I'm new from this forum and i'm trying installing VICIDIAL on a server machine running trixbox. I've already read posted messages about this, but i'm sure that is not impossible to implement both sistems. I've followed instructions for installation from scratch and my sistem goes up correctly. I've got admin page, user page and agent login page. Everything works fine but one thing: on debugging asterisk i see that it looks for a file agi named CALL_LOG.AGI. This file is an agi application so it should be placed on /var/lib/asterisk/agi-bin/ but it don't exist in my server. I can't find it anywhere. Someone can tell me where i can find it?
This don't seem to be a trixbox problem but when vicidial call the leads it seems to use this application... correct?
so if i've not this script i can't call my leads and i can't transfer calls to agents..
PLEASE EVERY HELP IS VERY VERY APPRECIATED...
Freddy_rixcom
 
Posts: 36
Joined: Fri Feb 15, 2008 7:16 am

Postby mcargile » Fri Feb 15, 2008 10:14 am

First off. call_log.agi was replaced a while ago with a fast agi called FastAGI_log.pl which can be found in /usr/share/astguiclient. The reason for this change was a performance improvement. A fast agi is infact a server that runs on your system and accepts connections via a network socket. If you look the call within the dialplan to the call_log agi in the h extension should look like this:

Code: Select all
exten => h,1,DeadAGI(agi://127.0.0.1:4577/call_log--HVcauses--PRI-----NODEBUG-----${HANGUPCAUSE}-----${DIALSTATUS}-----${DIALEDTIME}-----${ANSWEREDTIME})


Notice the agi://127.0.0.1:4577/ before call log. This is what lets you know that an agi script is infact a fast agi. This extension also needs to be in EVERY context and EVERY macro in order for Vicidial to work.


Now for the more pressing issue. Vicidial and Trixbox. As you might have heard, even if you get Vicidial and Trixbox working together you will have horrible performance. The main reason for this is that in order for Trixbox to place a single call it goes through something like 50 to 150 different steps in the dialplan. A straight Vicidial server can do this is as little as 3. I seriously suggest not using Trixbox and Vicidial on the same server.
Michael Cargile | Director of Engineering | ViciDialGroup | http://www.vicidial.com

The official source for VICIDIAL services and support. 1-888-894-VICI (8424)
mcargile
Site Admin
 
Posts: 617
Joined: Tue Jan 16, 2007 9:38 am

Another question

Postby Freddy_rixcom » Sat Feb 16, 2008 10:43 am

Thanks a lot for you help.
Now i'm able to call out with manual calling, i've changed to FastAGI and it's more quickly than ever.
At this time i'm triyng autodialing and i've got a problem that is very frequent: i'm not able to transfer the call to agent. I've posted the debug of * cli and i'm asking myself for a question: must i set asterisk agent in agent.conf as set in VICIDIAL Agent and REMOTE USERS????
Thanks in advance for your reply

== Manager 'sendcron' logged off from 127.0.0.1
-- Executing [8365@default:1] AGI("Local/900393404516236@default-bd99,1", "agi://127.0.0.1:4577/call_log|8365") in new stack
-- AGI Script agi://127.0.0.1:4577/call_log completed, returning 0
-- Executing [8365@default:2] AGI("Local/900393404516236@default-bd99,1", "agi://127.0.0.1:4577/agi-VDADtransfer|8365") in new stack
== Manager 'sendcron' logged off from 127.0.0.1
-- AGI Script agi://127.0.0.1:4577/agi-VDADtransfer completed, returning 0
-- Executing [8365@default:3] AGI("Local/900393404516236@default-bd99,1", "agi://127.0.0.1:4577/agi-VDADtransfer|8365") in new stack
-- AGI Script agi://127.0.0.1:4577/agi-VDADtransfer completed, returning 0
-- Executing [8365@default:4] AGI("Local/900393404516236@default-bd99,1", "agi://127.0.0.1:4577/agi-VDADtransfer|8365") in new stack
-- AGI Script agi://127.0.0.1:4577/agi-VDADtransfer completed, returning 0
-- Executing [8365@default:5] Hangup("Local/900393404516236@default-bd99,1", "") in new stack
== Spawn extension (default, 8365, 5) exited non-zero on 'Local/900393404516236@default-bd99,1'
-- Executing [h@default:1] DeadAGI("Local/900393404516236@default-bd99,1", "agi://127.0.0.1:4577/call_log|h") in new stack
-- AGI Script agi://127.0.0.1:4577/call_log completed, returning 0
-- Executing [h@default:2] DeadAGI("Local/900393404516236@default-bd99,1", "agi://127.0.0.1:4577/VD_hangup|PRI-----NODEBUG-----16---------------") in new stack
-- AGI Script agi://127.0.0.1:4577/VD_hangup completed, returning 0
-- Hungup 'Zap/1-1'
== Spawn extension (default, 900393404516236, 2) exited non-zero on 'Local/900393404516236@default-bd99,2'
-- Executing [h@default:1] DeadAGI("Local/900393404516236@default-bd99,2", "agi://127.0.0.1:4577/call_log|h") in new stack
-- AGI Script agi://127.0.0.1:4577/call_log completed, returning 0
-- Executing [h@default:2] DeadAGI("Local/900393404516236@default-bd99,2", "agi://127.0.0.1:4577/VD_hangup|PRI-----NODEBUG-----16-----ANSWER-----14-----0") in new stack
Freddy_rixcom
 
Posts: 36
Joined: Fri Feb 15, 2008 7:16 am

Postby mflorell » Sat Feb 16, 2008 7:40 pm

Have you tried using the sip-silence Playback before the 8365 extens in your extensions.conf?
mflorell
Site Admin
 
Posts: 18387
Joined: Wed Jun 07, 2006 2:45 pm
Location: Florida

Postby Freddy_rixcom » Mon Feb 18, 2008 2:29 am

No I don't. I will try immediately.
Then if it doesn't work, i will tri to play extension by saying numbers of it.
So if asterisk doesn't have it in the actual dialplan i should know where is the problem. About agents any suggestion?
Thanks a lot.
See yuo later
Freddy_rixcom
 
Posts: 36
Joined: Fri Feb 15, 2008 7:16 am

Make sure U are not manually setting CID in extensions.conf

Postby TroyD » Mon Apr 14, 2008 11:58 pm

I had added a line to my extensions.conf so that on an outbound call I would set the CID to send, and this was causing me not to be able to have a HUMAN answered call transferred to the Agent.. Not sure if thats your issue, but If you made ay changes then that may be the culprit..

Vicidial is very sensitive to ANY manual CID changes.
TroyD
 
Posts: 96
Joined: Fri Nov 02, 2007 4:03 pm

Postby mflorell » Tue Apr 15, 2008 8:33 am

Yes, VICIDIAL is not happy when you try to change callerID information anywhere in the dialing process. It needs control of CallerID information to track calls.
mflorell
Site Admin
 
Posts: 18387
Joined: Wed Jun 07, 2006 2:45 pm
Location: Florida


Return to Support

Who is online

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