vicidial.org

Hello Everyone,

Anyone knows why the file is being created using a different date? See sample logs below. The call was the initiated on August 30 but hte file name is August 31.



[Aug 30 15:22:23] VERBOSE[30849][C-00006d4f] pbx.c: Executing [8309@default:2] Monitor("Local/58600063@default-000044a1;1", "wav,20190831-032222_2534682163_OUTSOURC_CSP5661_V8301522090033678544_") in new stack
[Aug 30 15:22:35] VERBOSE[30914][C-00006d55] pbx.c: Executing [8309@default:2] Monitor("Local/58600058@default-000044a3;1", "wav,20190831-032234_3093358504_OUTSOURC_CSP5685_V8301522130036763615_") in new stack
[Aug 30 15:22:55] VERBOSE[31106][C-00006d6e] pbx.c: Executing [8309@default:2] Monitor("Local/58600051@default-000044b9;1", "wav,20190831-032253_9735736710_OUTSOURC_CSP5658_V8301522340036764318_") in new stack
[Aug 30 15:23:01] VERBOSE[31169][C-00006d71] pbx.c: Executing [8309@default:2] Monitor("Local/58600055@default-000044ba;1", "wav,20190831-032300_8594756792_OUTSOURC_CSP5697_V8301522480036764317_") in new stack
[Aug 30 15:23:29] VERBOSE[31296][C-00006d7e] pbx.c: Executing [8309@default:2] Monitor("Local/58600064@default-000044c0;1", "wav,20190831-032328_2093128259_OUTSOURC_CSP5672_V8301522440033976011_") in new stack
[Aug 30 15:23:46] VERBOSE[31466][C-00006d94] pbx.c: Executing [8309@default:2] Monitor("Local/58600066@default-000044d4;1", "wav,20190831-032345_5309256041_OUTSOURC_CSP5717_V8301523370034588546_") in new stack
[Aug 30 15:23:52] VERBOSE[31512][C-00006d9b] pbx.c: Executing [8309@default:2] Monitor("Local/58600053@default-000044d6;1", "wav,20190831-032350_5595564715_OUTSOURC_CSP5686_V8301523410036763488_") in new stack
[Aug 30 15:24:13] VERBOSE[31712][C-00006da7] pbx.c: Executing [8309@default:2] Monitor("Local/58600061@default-000044de;1", "wav,20190831-032412_5024479967_OUTSOURC_CSP5665_V8301523440036764247_") in new stack
[Aug 30 15:24:29] VERBOSE[31833][C-00006db4] pbx.c: Executing [8309@default:2] Monitor("Local/58600063@default-000044e8;1", "wav,20190831-032428_6413441620_OUTSOURC_CSP5661_V8301524080036762607_") in new stack

Is the server's time correct?

What time zone is involved? (Server time, Agent time, Prospect/Lead time ...)

If the recording filename is using GMT (which is also UTC), then your time zone offset could cause the GMT date to actually be tomorrow if the call is late enough in the day.

Hello william,

I resolved this issue. We were able to adjust the recording based on the server time instead on the workstation time.