Page 1 of 1

RECORDINGS DIFFERENT FROM TALK TIME

PostPosted: Tue Mar 31, 2015 4:23 pm
by snocetti
Hello, I am experiencing problems with recordings, a lot of these says for example 3 or 4 seconds, but length of call is more than 100 seconds.

I checked all config, campaign recording is all force, inbound recording too, and agent recording is enabled too.

I upgrade to latest version but problem persist.

This is version.

VERSION: 2.12-479a
BUILD: 150313-0912

This is an example:

CLOSER RECORDS FOR THIS LEAD:
# DATE/TIME LENGTH STATUS TSR CAMPAIGN LIST LEAD WAIT HANGUP REASON
1 2015-03-26 15:24:09 165 BTC 6003 ATBOGOTA 998 134090 0.00 AGENT


AGENT LOG RECORDS FOR THIS LEAD:
# DATE/TIME CAMPAIGN TSR PAUSE WAIT TALK DISPO STATUS GROUP SUB
1 2015-03-26 15:22:05 ATCLIENT 6003 0 137 152 0 BTC AGENTES_BOGOTA LAGGED


IVR LOGS FOR THIS LEAD:
# CAMPAIGN DATE/TIME CALL MENU ACTION


RECORDINGS FOR THIS LEAD:
# LEAD DATE/TIME SECONDS RECID FILENAME LOCATION TSR
1 134090 2015-03-26 15:26:54 0 156977 IN_20150326-152421_ATCLIENT_6003_17440769 http://10.57.1.242/RECORDIN... 6003


As you see recording length says 0 seconds.

I investigated and I found that some times RECORDING does not go out from meetme and continues recording some calls in same recording file..

Some help for this?

Re: RECORDINGS DIFFERENT FROM TALK TIME

PostPosted: Tue Mar 31, 2015 4:56 pm
by DomeDan
Maybe a load issue, what is the system load when there is many agents active?
is it a cluster setup or all on one server? if its a cluster then check the load on every server (and how many physical cores does the server cpu have?)

Re: RECORDINGS DIFFERENT FROM TALK TIME

PostPosted: Tue Mar 31, 2015 10:03 pm
by snocetti
Server load is 0,6 (Load average), it is a 8 core xeon server with 8 gb ram memory.

Total server agents are 20 - 24

This is an ALL IN ONE setup, no more servers. This was installed from VICIBOX.