Skip to content

'CallScenario' should have a property changed callback. #28288

Open

Description

Since there is no property changed callback for the CallScenario property, In the case described below, we are unable to detect changes to the CallScenario property and update it.

Repro Steps

  1. Call from A to B -> CallScenario = P2P

  2. Remote user B adds third participant 'C' to the call

  3. C rejects the incoming call

    • CallScenario does not get updated on User A (it is still set to 'P2P' on User A), even though it is different for User B (it is set to 'MultiParty' because we update it as part of handling the remoteParticipants changed event). Having a callback to subscribe to would help keep track of the value for all participants."
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Labels

ClientThis issue points to a problem in the data-plane of the library.Communicationcustomer-reportedIssues that are reported by GitHub users external to the Azure organization.questionThe 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