Not able to get agiout log files

[perhub]

Hi,

We are using the vicidial and got it working nicely for predictive dialing.
When I created an inbound group it didn't work though and the problem is that agiout files are not created so I can't debug the application.

in /etc/astguiclient.conf

PATHlogs => /var/log/astguiclient

in directory
/var/log/astguiclient
I have logfiles for adapt, hopper, listen (with ext YYYY-MM-DD) but not agiout.

In the webpage for the server I have AGI Output: BOTH

What am I failing to configure to get the log going?

regards
Per

[mflorell]

That's odd, I haven't seen that as a problem before. If you attach to the Real Asterisk CLI do you see output from the AGI scripts?

[perhub]

Yes I am getting some AGI debugging in the Asterisk logfile but not enough to know whats failing.

I am running version 2.0.4 on FreeBSD 6.2.

Below you will se an output from the asterisk log

a=silenceSupp:off - - - -
a=ptime:20[Feb 20 06:51:38] VERBOSE[40900] logger.c: -- Executing [46855801961@default:4] AGI("SIP/46855801963-086c5000", "agi-VDAD_ALL_inbound.agi|CIDLO
OKUPRC-----LB-----PASSNING-----46855801961-----Closer-----park----------999-----1-----PASS_IN") in new stack
[Feb 20 06:51:38] VERBOSE[40900] logger.c: -- Launched AGI Script /usr/local/share/asterisk/agi-bin/agi-VDAD_ALL_inbound.agi
[Feb 20 06:51:38] VERBOSE[40900] logger.c:
<--- SIP read from 62.80.200.53:5060 --->
ACK sip:46855801961@62.80.200.44 SIP/2.0
Via: SIP/2.0/UDP 62.80.200.53;branch=z9hG4bKf831.2f7defeec339e37757584a2856ff66d5.0
Via: SIP/2.0/UDP 62.80.200.53:5061;rport=5061;branch=z9hG4bKa1c2a87c35da3b127440f1de63c9a090
Max-Forwards: 16
From: <sip:0732511383@62.80.200.53>;tag=2efc1a028ec6d915d8c89788431b43d7
To: <sip:46855801961@62.80.200.53>;tag=as33440bed
Call-ID: BBECD55C-DEAE11DC-A0B0ED7D-E0488183@62.80.200.58
CSeq: 200 ACK
Expires: 300
User-Agent: Sippy


<------------->
[Feb 20 06:51:38] VERBOSE[40900] logger.c: AGI Tx >> agi_request: agi-VDAD_ALL_inbound.agi
[Feb 20 06:51:38] VERBOSE[40900] logger.c: --- (10 headers 0 lines) ---
[Feb 20 06:51:38] VERBOSE[40900] logger.c: AGI Tx >> agi_channel: SIP/46855801963-086c5000
[Feb 20 06:51:38] VERBOSE[40900] logger.c: AGI Tx >> agi_language: en
[Feb 20 06:51:38] VERBOSE[40900] logger.c: AGI Tx >> agi_type: SIP
[Feb 20 06:51:38] VERBOSE[40900] logger.c: AGI Tx >> agi_uniqueid: 1203486697.1
[Feb 20 06:51:38] VERBOSE[40900] logger.c: AGI Tx >> agi_callerid: 0732511383
[Feb 20 06:51:38] VERBOSE[40900] logger.c: AGI Tx >> agi_calleridname: unknown
[Feb 20 06:51:38] VERBOSE[40900] logger.c: AGI Tx >> agi_callingpres: 0
[Feb 20 06:51:38] VERBOSE[40900] logger.c: AGI Tx >> agi_callingani2: 0
[Feb 20 06:51:38] VERBOSE[40900] logger.c: AGI Tx >> agi_callington: 0
[Feb 20 06:51:38] VERBOSE[40900] logger.c: AGI Tx >> agi_callingtns: 0
[Feb 20 06:51:38] VERBOSE[40900] logger.c: AGI Tx >> agi_dnid: 46855801961
[Feb 20 06:51:38] VERBOSE[40900] logger.c: AGI Tx >> agi_rdnis: unknown
[Feb 20 06:51:38] VERBOSE[40900] logger.c: AGI Tx >> agi_context: default
[Feb 20 06:51:38] VERBOSE[40900] logger.c: AGI Tx >> agi_extension: 46855801961
[Feb 20 06:51:38] VERBOSE[40900] logger.c: AGI Tx >> agi_priority: 4
[Feb 20 06:51:38] VERBOSE[40900] logger.c: AGI Tx >> agi_enhanced: 0.0
[Feb 20 06:51:38] VERBOSE[40900] logger.c: AGI Tx >> agi_accountcode:
[Feb 20 06:51:38] VERBOSE[40900] logger.c: AGI Tx >>
[Feb 20 06:51:38] VERBOSE[40900] logger.c: -- AGI Script agi-VDAD_ALL_inbound.agi completed, returning 0
[Feb 20 06:51:38] VERBOSE[40900] logger.c: -- Executing [46855801961@default:5] Hangup("SIP/46855801963-086c5000", "") in new stack
[Feb 20 06:51:38] VERBOSE[40900] logger.c: == Spawn extension (default, 46855801961, 5) exited non-zero on 'SIP/46855801963-086c5000'
[Feb 20 06:51:38] VERBOSE[40900] logger.c: Scheduling destruction of SIP dialog 'BBECD55C-DEAE11DC-A0B0ED7D-E0488183@62.80.200.58' in 32000 ms (Method: ACK)
[Feb 20 06:51:38] VERBOSE[40900] logger.c: set_destination: Parsing <sip:62.80.200.53;ftag=2efc1a028ec6d915d8c89788431b43d7;lr> for address/port to send to

[mflorell]

That's not the Real Asterisk CLI, that looks like a remote connection(asterisk -r) to the Asterisk CLI.

How are you starting Asterisk?

I have not done any testing of VICIDIAL on FreeBSD and cannot troubleshoot that platform for you.

[perhub]

I am starting Asterisk with the perl script that existed in the astgui packet.
astgui/bin/start_asterisk_boot.pl

You are correct that I am using the remote connection -r to connect to asterisk.

How should one start Asterisk for vicidial to work optimal and get the most logging?

As long as I get enough logging I can troubleshoot the vicidial on freeBSD and hopefully give someone else good hints on how to set it up on FreeBSD.

regards
Per

[mflorell]

If you are starting asterisk that way then you should be able to attach to the screen running it to get full output:

screen -r asterisk

- to detach

'Ctrl+a' then type 'd'