Repeatedly calling mute/unmute will update the muted state of the call locally, but other participants on the call do not see the same muted state of the remote participant

[christopher-tobin-pwc]

• Package Name: @azure/communication-calling
• Package Version: 1.23.2-beta.1
• Operating system: MacOS
• nodejs
  • version:
• browser
  • name/version: chrome/124.0.6367.62
• typescript
  • version:
• Is the bug related to documentation in
  • README.md
  • source code documentation
  • SDK API docs on https://docs.microsoft.com

Describe the bug
When the mute/unmute SDK operations are repeatedly invoked enough to trigger throttling, the isMuted field on the call is still updated. The other participant(s) on the call no longer see the correct muted state of the user. This can result in a situation where the local user believes they are muted but the other participant(s) on the call can still hear them.

To Reproduce

1. Start a call (either 1:1 or 1:N)
2. Repeatedly mute/unmute the local user (more than 15 times in a 30 second window) to trigger a 429 - Too Many Requests error

Expected behavior
The isMuted state of the call matches the isMuted state of the user seen by the other participant(s) on the call. The isMutedChanged event is only raised when the local user is actually muted or unmuted for the other participant(s) on the call (meaning other participants on the call can either no longer hear them or hear them).

Screenshots
If applicable, add screenshots to help explain your problem.

Additional context

• There is a 429 (Too Many Requests) error seen in the console, but this error is not thrown by the mute/unmute functions. There is no way for consumers to capture this error and decision on it
• The isMutedChanged event is raised even though the call to mute/unmute was throttled
• This call id had the out of sync muted state when the call ended
  • 0c16b95f-62ad-4c56-9c52-c844a6fdd9b7