Page 1 of 1

Recordings duration doesn't match on the actual file

PostPosted: Thu May 16, 2019 9:08 am
by jessiekidfernando
Hello Everyone,

Any idea why the duration of the recordings doesn't match on the actual file?

See example below.

https://snag.gy/Jn6c5G.jpg

Regards,

Jessie Kid Fernando

Re: Recordings duration doesn't match on the actual file

PostPosted: Thu May 16, 2019 10:56 am
by williamconley
Do you have a recording delay configured?

Re: Recordings duration doesn't match on the actual file

PostPosted: Thu May 16, 2019 11:28 am
by jessiekidfernando
Hello Williamconley,

Where can I see that?

Re: Recordings duration doesn't match on the actual file

PostPosted: Thu May 16, 2019 11:28 am
by jessiekidfernando
Never mind. I am now double checking it.

Re: Recordings duration doesn't match on the actual file

PostPosted: Thu May 16, 2019 11:29 am
by jessiekidfernando
It is set to 0.

Re: Recordings duration doesn't match on the actual file

PostPosted: Thu May 16, 2019 12:19 pm
by williamconley
was the call inbound or outbound and did you get that setting from Ingroup or Campaign?

Is recording also set for the agent? I can only think that there's a conflict/overlap in recording for DID/User/Ingroup/Campaign and that the log shows the call length instead of the recording length when the recording was initiated only during one stage of the call.

Or the agent pushed the "stop recording" button.

Technically none of those should create a wrong value in that field, but there are a lot of factors involved.

Also, of course, it's possible there's a flaw in the system somewhere. A dialplan context without a "hangup()" would be expected to leave the field blank instead of wrong, but this is linux where anything can magically happen. lol. 8-)