Page 1 of 1

Campaign Recording Filenames not matching DB entries

PostPosted: Tue Jun 15, 2010 1:41 pm
by shm267
I just upgraded the base VicidialNOW base build to vicidial 2.2.1-237, build 100510-2015 and Asterisk 1.4.21.2

I did not really test prior to the upgrade, but noticed I can not seem to access the call recording for the campaign, the filename in the report does not seem to match the filename in the recording directories and the location is blank.



Agent Detail Report...

# LEAD DATE/TIME SECONDS RECID FILENAME LOCATION
1 56 2010-06-15 13:56:57 4 3 20100615-135656_2142543870
2 55 2010-06-15 13:56:20 23 2 20100615-135619_2142543870
3 55 2010-06-15 13:53:29 23 1 20100615-135328_2142543870


/var/spool/asterisk directory on the vicidial server

|-- monitorDONE
| |-- FTP
| |-- FTP2
| |-- GSM
| | |-- 1276624409-Local-58600051@default-ae12,1-all.gsm
| | |-- 1276624580-Local-58600051@default-9794,1-all.gsm
| | `-- 1276624617-Local-58600051@default-663a,1-all.gsm

PostPosted: Tue Jun 15, 2010 7:56 pm
by shm267
Soved.

This issues turned out to be old lingering code in extensions.conf

Make sure these sections of code are commented out. It appears the variable CALLERIDNAME was replaced with CALLERID(name), the old reference is blank and creates the wrong file name for the recordings.

====================
OLD VERSION
; this is used for recording conference calls, the client app sends the filename
; value as a callerID recordings go to /var/spool/asterisk/monitor (WAV)
; Recording is limited to 1 hour, to make longer, just change the Wait,3600
;exten => 8309,1,Answer
;exten => 8309,2,Monitor(wav,${CALLERIDNAME})
;exten => 8309,3,Wait,3600
;exten => 8309,4,Hangup

; this is used for recording conference calls, the client app sends the filename
; value as a callerID recordings go to /var/spool/asterisk/monitor (GSM)
; Recording is limited to 1 hour, to make longer, just change the Wait,3600
;exten => 8310,1,Answer
;exten => 8310,2,Monitor(gsm,${CALLERIDNAME})
;exten => 8310,3,Wait,3600
;exten => 8310,4,Hangup
OLD VERSION
====================

====================
NEW VERSION - auto generated in extensions-vicidial.conf
; this is used for recording conference calls, the client app sends the filename
; value as a callerID recordings go to /var/spool/asterisk/monitor (WAV)
; Recording is limited to 1 hour, to make longer, just change the server
; setting ViciDial Recording Limit
; this is the WAV verison, default
exten => 8309,1,Answer
exten => 8309,n,Noop(CALLERIDNAME=${CALLERIDNAME})
exten => 8309,n,Noop(CALLERID(name)=${CALLERID(name)})
exten => 8309,n,Monitor(wav,${CALLERID(name)})
exten => 8309,n,Wait,3600
exten => 8309,n,Hangup
; this is the GSM verison
exten => 8310,1,Answer
exten => 8310,n,Noop(CALLERIDNAME=${CALLERIDNAME})
exten => 8310,n,Noop(CALLERID(name)=${CALLERID(name)})
exten => 8310,n,Monitor(gsm,${CALLERID(name)})
exten => 8310,n,Wait,3600
exten => 8310,n,Hangup
==========================================

PostPosted: Wed Jun 16, 2010 12:00 am
by mflorell
That is mentioned in the UPGRADE doc, as well as being set properly in the default extensions.conf.

PostPosted: Wed Jun 16, 2010 10:23 am
by shm267
See that now (item 13), but I would suggest a note on the VicidialNOW upgrade page just as a reminder. In case someone else is like me and does not read every line.

PostPosted: Thu Jun 17, 2010 3:30 pm
by gardo
From the UPGRADE doc:

13. Removed the ViciDial recording extensions from the general dialplan since
they are now auto-generated and placed in the extensions-vicidial.conf
file(8309 and 8310). Also, phone dial-out contexts are definable now
allowing you to lock out agent phone in a call center from dialing out.


You don't need to manually edit your extensions.conf file if you follow the upgrade procedure here: http://vicidialnow.org.

PostPosted: Thu Jun 17, 2010 4:08 pm
by shm267
Actually, that is the process I followed twice on two different servers.

I did miss the instruction...
Don't forget to answer "Y" when asked "Copy sample configuration files to /etc/asterisk/?"

I'm I correct in assuming this is where it would have blown away my modified version of extension.conf with a sample/corrected version?

PostPosted: Sat Jun 19, 2010 2:59 pm
by gardo
Yes you are right. This would have overwritten your .conf files.