search

Azure / azure-sdk-for-js

This repository is for active development of the Azure SDK for JavaScript (NodeJS & Browser). For consumers of the SDK we recommend visiting our public developer docs at https://docs.microsoft.com/javascript/azure/ or our versioned developer docs at https://azure.github.io/azure-sdk-for-js.
MIT License
2.07k stars 1.19k forks source link

[Communication - Calling] recordings property of callRecordingApi is not accurate for participants who join a call when recording is 'Paused' #31511

Open antojose1 opened 3 days ago

antojose1 commented 3 days ago

Describe the bug Participants are not able to retrieve accurate cloud 'recordings' if they join a call after a cloud recording has already been started and paused.

To Reproduce Use the add-1-on-1-voice-calling sample, and do the bare minimum to add "manage call recording on the client" and "add a participant to a call" functionality.

Steps to reproduce the behavior:

  1. Establish a 1:1 call
  2. Get the recording feature API object
    • inspect isRecordingActive and recordings properties -> isRecordingActive is false and recordings array is empty as expected.
  3. Determine the Server Call ID and start a cloud recording using call automation.
    • Inspect isRecordingActive properties -> isRecordingActive is true and recordings array has recordingInfo as expected.
  4. Pause the recording
  5. Add a new participant to the call.
  6. For the new participant, get the recording feature API object and inspect isRecordingActive and recordings properties.

Expected behavior isRecordingActive property is false and recordings array has correct recordingInfo.

Actual behavior

Related to: https://github.com/Azure/azure-sdk-for-js/issues/28964 - isRecordingActive and recordings properties are correctly updating now as fixed here, but if the recording is in paused state when new participant joins, issue is still there as described above

github-actions[bot] commented 3 days ago

Thanks for the feedback! We are routing this to the appropriate team for follow-up. cc @dnssuppgithub.