Skip to content

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

Open

Description

  • Package Name: @azure/communication-calling
  • Package Version: 1.28.4
  • Operating system: Windows
  • browser
  • name/version: Chrome 122.0.6261.95

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

  • isRecordingActive property is false as expected.
  • But the recordings property is empty, it does not contain accurate recordingInfo of the current recording which is in Paused state
    Image

Related to: #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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Assignees

Labels

ClientThis issue points to a problem in the data-plane of the library.Network - DNSService AttentionWorkflow: This issue is responsible by Azure service team.customer-reportedIssues that are reported by GitHub users external to the Azure organization.needs-team-attentionWorkflow: This issue needs attention from Azure service team or SDK teamquestionThe issue doesn't require a change to the product in order to be resolved. Most issues start as that

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions