Recodings do not stop after call hang up
Posted: Wed Jan 24, 2007 4:29 am
I have installed VICIDIAL for a call center that has the policy that all calls MUST be recorded. In order to achieve this I had set the "Campaign Recordings" field to ALLFORCE.
Now, when an agent login to a campaign the a SIP/c001-XXXXXX (for example) channel spawns that connects the agent to VICIDIAL. When the agent dials a lead a second channel is spawned: Local/86000XX@vicidial-XXXXX that connects the customer and also a third channel Local/786000XX@vicidial-XXXXX is spawned which is the recording channel.
When this same agent is done with the call and presses the "HANGUP CUSTOMER" button, the customer's Local/86000XX@vicidial-XXXXX channel is hung up automatically, but the recording Local/786000XX@vicidial-XXXXX stay active!
If one would go and monitor the disk activity at the /var/spool/asterisk/monitor directory, one would see that the wav file is still growing even after the agent has logged out of VICIDIAL. This has a huge impact on the server's performance and disk space!
The only way to stop the recording is for the administrator to login to astguiclient and force a hangup on the recording channel.
I also noticed a "Stop Rec after each call" field in the phone setting in VICIDIAL ADMIN and I double checked and made sure that all phone were set to 1.
The extensions.conf file contains the following:
[vicidial]
...
; 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)
exten => 8309,1,Answer
exten => 8309,2,Monitor(wav,${CALLERIDNAME})
exten => 8309,3,Wait,3600
exten => 8309,4,Hangup
...
I also made sure that the recording extension in VICIDIAL ADMIN is set to 8309.
Asterisk does not display any debugging errors.
I am using Asterisk version 1.2.13 and VICIDIAL version 2.0.2
If anybody know what else I could check or do, please let me know.
Now, when an agent login to a campaign the a SIP/c001-XXXXXX (for example) channel spawns that connects the agent to VICIDIAL. When the agent dials a lead a second channel is spawned: Local/86000XX@vicidial-XXXXX that connects the customer and also a third channel Local/786000XX@vicidial-XXXXX is spawned which is the recording channel.
When this same agent is done with the call and presses the "HANGUP CUSTOMER" button, the customer's Local/86000XX@vicidial-XXXXX channel is hung up automatically, but the recording Local/786000XX@vicidial-XXXXX stay active!
If one would go and monitor the disk activity at the /var/spool/asterisk/monitor directory, one would see that the wav file is still growing even after the agent has logged out of VICIDIAL. This has a huge impact on the server's performance and disk space!
The only way to stop the recording is for the administrator to login to astguiclient and force a hangup on the recording channel.
I also noticed a "Stop Rec after each call" field in the phone setting in VICIDIAL ADMIN and I double checked and made sure that all phone were set to 1.
The extensions.conf file contains the following:
[vicidial]
...
; 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)
exten => 8309,1,Answer
exten => 8309,2,Monitor(wav,${CALLERIDNAME})
exten => 8309,3,Wait,3600
exten => 8309,4,Hangup
...
I also made sure that the recording extension in VICIDIAL ADMIN is set to 8309.
Asterisk does not display any debugging errors.
I am using Asterisk version 1.2.13 and VICIDIAL version 2.0.2
If anybody know what else I could check or do, please let me know.