Is anyone else seeing this issue? I have a script running that flags call logs that have recordings, and then I hit the call recording api, /restapi/v1.0/account/accountId/recording/recordingId, with the recoding ID that I get from the call log, and every time it returns a duration of 3 seconds, even though every single call is much longer.
I've opened a ticket with support and have been met with crickets. This is in our production environment and causing significant issues.
Any advice?
I'm having the same issue as well. Any update?
Checking the workaround now.
I'm already implementing the workaround, taking the duration from the call-log, but looks like the call.duration and recording.duration are in some case really distant. For example, I have a call duration returning 43 seconds but when I download the recording file its duration is only 23 seconds.
At least this is better than showing 3 seconds for every call.
Do you mean that the value of the duration field is just 3 instead of the actual duration of the recording?
Yes. Here's what I see no matter the what record ID I check:
And here it is in the admin call log report:
Hi Daniel,
Did you receive any resolution to this issue? We are facing the same problem.
That's weird. I just check and it returns the correct value
{
id: '197253472xxxx',
contentUri: 'https://media.ringcentral.com/restapi/v1.0/account/80964xxxx/recording/197253472xxxx/content',
contentType: 'audio/mpeg',
duration: 87
}
I suggest you open a dev support ticket so some one can have a closer look at your account. I am sure that it's not the platform issue.
Hi @Phong Vu ,
Do you know whether there has been any progress with getting this bug fixed?
I have had no response to my support ticket.
Thank you.
I thought it was fixed a long time ago. But I just checked and it wasn't.
Let me check with the platform team to get the latest status.
UPDATED: Unfortunately, the issue is not fixed and I have no ETA.
10 People are following this question.
