Customizing lib-jitsi-meet API (low level)

ERSIN_COL · May 8, 2023, 8:58am

I created custom web ui using lib-jitsi-meet low level api. I want to customize the sendTextMessage(text) method : lib-jitsi-meet/JitsiConference.js at master · jitsi/lib-jitsi-meet · GitHub

MESSAGE_RECEIVED - new text message received I want my method to be like this so

room.on(JitsiMeetJS.events.conference.MESSAGE_RECEIVED , (id, text, ts, extraParams) => {

        console.log('messageReceived', id, text, ts);
        console.log('messages', mainRoomMessages)
        console.log('extraParams', extraParams));

How can I customize it to send an extra parameter to the sendTextMessage method to do this?

min.js codes in my server are on this path : /usr/share/jitsi-meet/libs/lib-jitsi-meet.min.js

and the sendTextMessage codes here are like this:

Zu.prototype.sendTextMessage=function(e){let t=arguments.length>1&&void 0!==arguments[1]?arguments[1]:"body";this.room&&this.room.sendMessage(e,t)}

Do I need to make a change here, if so, can I use this method in a customized way on the distribution I use?

In summary, can you guide me how to customize and use the methods in lib-jitsi-meet low level API?

damencho · May 8, 2023, 10:46am

For modifying the message you need changes in ljm.
But there is an option to send custom messages in ljm, why don’t you use that.

github.com

jitsi/lib-jitsi-meet/blob/f0dd403951dd5d417aca301f0b8b4e2d31751713/JitsiConference.js#L2861


      
          */
          JitsiConference.prototype.sendEndpointMessage = function(to, payload) {
             this.rtc.sendChannelMessage(to, payload);
          };
          
          
/**
          * Sends local stats via the bridge channel which then forwards to other endpoints selectively.
          * @param {Object} payload The payload of the message.
          * @throws NetworkError/InvalidStateError/Error if the operation fails or if there is no data channel created.
          */
          JitsiConference.prototype.sendEndpointStatsMessage = function(payload) {
             this.rtc.sendEndpointStatsMessage(payload);
          };
          
          
/**
          * Sends a broadcast message via the data channel.
          * @param payload {object} the payload of the message.
          * @throws NetworkError or InvalidStateError or Error if the operation fails.
          * @deprecated Use 'sendMessage' instead. TODO: this should be private.
          */
          JitsiConference.prototype.broadcastEndpointMessage = function(payload) {

github.com

jitsi/lib-jitsi-meet/blob/f0dd403951dd5d417aca301f0b8b4e2d31751713/JitsiConference.js#L2871


      
          JitsiConference.prototype.sendEndpointStatsMessage = function(payload) {
              this.rtc.sendEndpointStatsMessage(payload);
          };
          
          
/**
           * Sends a broadcast message via the data channel.
           * @param payload {object} the payload of the message.
           * @throws NetworkError or InvalidStateError or Error if the operation fails.
           * @deprecated Use 'sendMessage' instead. TODO: this should be private.
           */
          JitsiConference.prototype.broadcastEndpointMessage = function(payload) {
              this.sendEndpointMessage('', payload);
          };
          
          
/**
           * Sends a message to a given endpoint (if 'to' is a non-empty string), or
           * broadcasts it to all endpoints in the conference.
           * @param {string} to The ID of the endpoint/participant which is to receive
           * the message, or '' to broadcast the message to all endpoints in the
           * conference.
           * @param {string|object} message the message to send. If this is of type

github.com

jitsi/lib-jitsi-meet/blob/f0dd403951dd5d417aca301f0b8b4e2d31751713/JitsiConference.js#L2889


      
          * the message, or '' to broadcast the message to all endpoints in the
          * conference.
          * @param {string|object} message the message to send. If this is of type
          * 'string' it will be sent as a chat message. If it is of type 'object', it
          * will be encapsulated in a format recognized by jitsi-meet and converted to
          * JSON before being sent.
          * @param {boolean} sendThroughVideobridge Whether to send the message through
          * jitsi-videobridge (via the COLIBRI data channel or web socket), or through
          * the XMPP MUC. Currently only objects can be sent through jitsi-videobridge.
          */
          JitsiConference.prototype.sendMessage = function(message, to = '', sendThroughVideobridge = false) {
             const messageType = typeof message;
          
          
   // Through videobridge we support only objects. Through XMPP we support
             // objects (encapsulated in a specific JSON format) and strings (i.e.
             // regular chat messages).
             if (messageType !== 'object'
                     && (sendThroughVideobridge || messageType !== 'string')) {
                 logger.error(`Can not send a message of type ${messageType}`);
          
          
       return;

saghul · May 8, 2023, 4:54pm

I’d recommend sending an object with the text and metadata. It will be JSON encoded.