Mute all Functionality

Sarita_Kumari_Singh · May 11, 2023, 12:36pm

“When a moderator clicks on ‘Mute All’ in Jitsi, a dialog box opens. I would like to understand the flow of events from the frontend to the backend regarding toggling the option for attendees to unmute themselves. Could the Jitsi community provide insights into how this functionality is implemented and how the frontend and backend components interact in this process?”

damencho · May 11, 2023, 2:37pm

All interactions are xmpp stanzas sending to the server. You can open the developer console before loading the page and look at the network communication bosh requests or websockets messages.
Or you can do APP.conference.saveLogs() in the console while in the conference and you will get all the xmpp messages exchanged between the client and the prosody server.

Sarita_Kumari_Singh · May 19, 2023, 5:29am

From my finding In Jitsi Meet, the communication flow from the frontend code to the backend components involves multiple steps for muteall functioallity. is it right flow ?:

Frontend Code: The frontend code captures user actions, such as participant can’t mute themselves.

Communication with Jicofo: To interact with the backend, the frontend code utilizes lib-jitsi-meet. It sends XMPP stanzas containing jid and mediatype to Jicofo, the signaling component.

Processing by Jicofo: Jicofo receives the XMPP stanzas from lib-jitsi-meet and processes them based on the msg then it blaclist the jid .

Instruction to JVB: Jicofo communicates with the JVB instances, responsible for media routing and conferencing capabilities. It instructs the JVB to perform operations such as forwarding or blocking media streams for specific participants. For example, when a participant’s audio is reject for unmuting, Jicofo sends an instruction to the JVB to block the audio stream to other participants.

Media Routing: The JVB acts as a bridge component, handling media routing between conference participants. It receives instructions from Jicofo regarding media blocking. Based on these instructions, the JVB adjusts its media routing logic to block the media streams to participants .

Feedback to Jicofo: Once the JVB performs the necessary operations, it provides feedback or updates to Jicofo. This feedback includes information about successfully applied changes, encountered errors, or other relevant details related to media routing.

Feedback to Frontend: Jicofo, upon receiving feedback from the JVB, sends XMPP stanzas or other messages to the frontend code through lib-jitsi-meet. This feedback informs the frontend code about the outcome of the user actions and provides updates to the user interface or conference state as required.
-----please correct me if i am wrong

damencho · May 19, 2023, 11:36am

I don’t agree with this one, the rest seems fine.

Local muting does not involve jicofo. Participants when mute locally are sending silence which is filtered automatically by jvb.

Remote muting though, when a moderator is muting someone goes through jicofo as described. To prevent the remote muted part of unmuting and continue sending, even if that happens jvb will not route that media to the rest of the participants.

Sarita_Kumari_Singh · May 22, 2023, 10:13am

Thank you sir for correcting me.In the React frontend codebase . I’m trying to identify the file responsible for handling the communication with lib-jitsi-meet when a moderator clicks on the ‘mute all’ functionality and toggling to participant cant unmute themselves. Could you please point me to the specific file or component where this communication takes place? I’m interested in understanding the flow of data and actions between the React frontend and the lib-jitsi-meet library during the ‘mute all’ toggling operation. The codebase is extensive, and despite my efforts, I haven’t been able to pinpoint the specific file or component. Could u please provide guidance or insights on where I should look in order to comprehend the code flow from react frontend code base to libjitsi meet during the ‘mute all’ toggling operation? Your assistance would be greatly appreciated. Thank you Sir!"

Sarita_Kumari_Singh · May 26, 2023, 12:27pm

hii sir,Could you please help me understand how the “Mute All” functionality is implemented in Jitsi? I’ve been trying to figure out how the frontend (React codebase) communicates with the backend services (lib-jitsi-meet, jicofo, jvb) and how backedn service communicate with eachother. Specifically, I’m looking for information on which frontend react code base component are involved in communicating with lib-jitsi-meet for “mute all” and which components or modules in lib-jitsi-meet are involved in the communication with jicofo and which component are involved in jicofo to communicate with jvb . please Help me I would greatly appreciate any guidance or explanations you can provide. Thank you!

damencho · May 30, 2023, 2:28pm

Here is your flow from UI to the xmpp IQ that is sent to the backend.

github.com

jitsi/jitsi-meet/blob/5077a33fcb6ab4ad39505e7475679b4c3b4e9188/react/features/video-menu/actions.any.ts#L89


      
              };
          }
          
          
/**
           * Mutes all participants.
           *
           * @param {Array<string>} exclude - Array of participant IDs to not mute.
           * @param {MEDIA_TYPE} mediaType - The media type to mute.
           * @returns {Function}
           */
          export function muteAllParticipants(exclude: Array<string>, mediaType: MediaType) {
              return (dispatch: IStore['dispatch'], getState: IStore['getState']) => {
                  const state = getState();
                  const localId = getLocalParticipant(state)?.id ?? '';
          
          
        if (!exclude.includes(localId)) {
                      dispatch(muteLocal(true, mediaType, mediaType !== MEDIA_TYPE.AUDIO));
                  }
          
          
        getRemoteParticipants(state).forEach((p, id) => {
                      if (exclude.includes(id)) {

github.com

jitsi/jitsi-meet/blob/06b67dcf4480e307c2313499a76bd7d88fac480e/react/features/base/participants/middleware.ts#L233


      
                      localRecording: recording
                  }));
              }
          
          
    break;
          }
          
          
case MUTE_REMOTE_PARTICIPANT: {
              const { conference } = store.getState()['features/base/conference'];
          
          
    conference?.muteParticipant(action.id, action.mediaType);
              break;
          }
          
          
// TODO Remove this middleware when the local display name update flow is
          // fully brought into redux.
          case PARTICIPANT_DISPLAY_NAME_CHANGED: {
              if (typeof APP !== 'undefined') {
                  const participant = getLocalParticipant(store.getState());
          
          
        if (participant && participant.id === action.id) {

github.com

jitsi/lib-jitsi-meet/blob/d2179f31508f82fe51279ebe490740c3351d239f/JitsiConference.js#L1769


      
                              value: JINGLE_SI_TIMEOUT
                          }));
                  }, JINGLE_SI_TIMEOUT);
              }
          };
          
          
/**
           * Mutes a participant.
           * @param {string} id The id of the participant to mute.
           */
          JitsiConference.prototype.muteParticipant = function(id, mediaType) {
              const muteMediaType = mediaType ? mediaType : MediaType.AUDIO;
          
          
    if (muteMediaType !== MediaType.AUDIO && muteMediaType !== MediaType.VIDEO) {
                  logger.error(`Unsupported media type: ${muteMediaType}`);
          
          
        return;
              }
          
          
    const participant = this.getParticipantById(id);

github.com

jitsi/lib-jitsi-meet/blob/6b71d39b216be5154003bdd3de2acf5a48db7065/modules/xmpp/ChatRoom.js#L1759


      
              const iqToFocus = $iq(
                  { to: this.focusMucJid,
                      type: 'set' })
                  .c('mute', {
                      xmlns: `http://jitsi.org/jitmeet/${mediaType}`,
                      jid
                  })
                  .t(mute.toString())
                  .up();
          
          
    this.connection.sendIQ(
                  iqToFocus,
                  result => logger.log('set mute', result),
                  error => logger.log('set mute error', error));
          }
          
          
/**
           * TODO: Document
           * @param iq
           */
          onMute(iq) {

Sarita_Kumari_Singh · May 31, 2023, 5:46am

thank you so much sir