Mic icon is not toggled when being muted by a moderator in a federated call

[nickvergessen]

How to use GitHub

• Please use the 👍 reaction to show that you are affected by the same issue.
• Please don't comment if you have no relevant information to add. It's just extra noise for everyone subscribed to this issue.
• Subscribe to receive notifications on status change and new comments.

---

Steps to reproduce

1. UserA on ServerA creates a conversation and invites UserB on ServerB
2. UserA starts a call
3. UserB joins the call
4. UserA presses the "mute icon" for UserB

Expected behaviour

UserB should see that they are muted

Actual behaviour

Also every now and then UserB got unmuted for me when toggling the camera as UserB or other things

[danxuliu]

To force mute another participant a control message is sent to every participant in the call; the client of the target participant should mute itself when the message is received, but the clients of other participants will also locally mute the target participant. This ensures that even if the client of the target participant does not mute itself for some reason in practice it will be muted for the rest of participants (or, at least, for those currently in the call).

Due to all that the forceMute control message includes the session ID of the target participant in its payload:

{
    type: 'control',
    control: {
        sender: ...,
        receiver: ...,
        data: {
            action: 'forceMute',
            peerId: SIGNALING-SESSION-ID-OF-THE-TARGET-PARTICIPANT,
        }
    }
}

For a federated user, its own signaling session ID and the ID seen by other participants is different, so the peerId needs to be converted. The signaling server takes care of that in other cases, but for control messages currently only the receiver and sender fields are converted.

@fancycode Could control->data->peerId be converted as well? :-) Thanks!