Jitsi Meet Google Analytics

  1. Jitsi Meet Google Analytics Download
  2. Jitsi Meet Online

So I want to add my google analytics tracking id to my project. First I want to test if it works so I decided to add it to a local dev deployment. I did the following changes to my config.json: // A list of scripts to load as lib-jitsi-meet 'analytics handlers'. AnalyticsScriptUrls: 'libs/analytics-ga.js' // google-analytics , // The Google Analytics Tracking ID googleAnalyticsTrackingId. Experience advanced meeting moderation and analytics. Get Organized.Sync with all the popular Google, Microsoft and Apple calendars. No commitments, cancel at any time. Connect your calendar to view all your meetings in Jitsi Meet. Plus, add Jitsi meetings to.

Jitsi Meet is an open source video conferencing solution that can be hosted on-premises or in the cloud. Compared to hosted services like Google Meet, WebEx, or Zoom, Jitsi calls are encrypted through your own server(s), providing enhanced privacy & security and peace of mind.

Online meeting applications such as Zoom require both moderators and guest attendees to install browser plugins, desktop or mobile clients to access their meetings. Security researchers & zero-day attackers have discovered security flaws in Zoom which allow attackers to remotely spy on your computer’s webcam and microphone. Some releases of Zoom also allowed attackers to elevate to root access on client machines, posing a critical security risk.

Although Zoom has patched the vulnerabilities that have been discovered so far, its sudden rise from 10 million to 200 million daily active users have made Zoom a prime target for cybercriminals who want to break into corporate and government networks. The situation is so severe that IT departments including at the Australian Defense Forces, Google, NASA, NYC Department of Education, SpaceX, and the Taiwan government have all forbidden their employees from using Zoom at work.

As Zoom struggled to keep up with the explosion in demand when “social distancing” and “work from home” policies came into place around the world, some Zoom calls outside of China were routed through Zoom’s Chinese servers. This is an enormous privacy concern for corporations and government organizations that are sensitive to cyber-espionage risks.

Normally Zoom calls are routed through the closest server to one’s geographic region. For example, a call between two attendees in Europe should normally stay within Europe. But when you entrust your privacy to a third-party such as Zoom, you can never know whether that is the case.

Jitsi is a more secure alternative to Zoom for video conferencing, because the traffic is routed through servers that you control. All connections are encrypted with your own SSL certificates, which means you don’t have to trust a third-party provider (unless you want to). These servers can reside in your office, a co-location datacenter, or a cloud provider.

Furthermore, Jitsi leverages the WebRTC protocol for streaming video, a standard that is widely maintained by major browser vendors – particularly the Chromium project. WebRTC has been found to adapt better to low-bandwidth connections with equal or better performance to proprietary codecs used by applications like Zoom.

Although Jitsi Meet can be used as a standalone voice & video conferencing server, it is commonly integrated with a chat app such RocketChat – an open source alternative to Slack. With the RocketChat integration, users can create 1-to-1 or channel calls with a single click from the RocketChat interface. Users can also join calls using the Jitsi Meet mobile app available for Android and iOS. Screen sharing without additional plugins (and if configured, call recording) is supported.

Jitsi Meet can be branded with your organization’s URL and logo so your customers have confidence that they are meeting with your employees on a trusted platform.

For 1-to-1 meetings, Jitsi can often establish a peer-to-peer link between the two attendees. For meetings with 3 or more people, the Jitsi Video Bridge (JVB) relays the audio and video streams between the attendees. Therefore, it’s important for the Jitsi Meet server to have a high bandwidth network connection, especially if you plan to host video conferences with a large number of attendees.

Setting up Jitsi Meet can be challenging for end user organizations, especially since most likely, their users will be behind a NAT. The Jitsi server may also be behind a NAT itself, whether it is a network gateway or a virtual network in Docker.

Ports 4443 (TCP) and 10000 (UDP) need to be open and forwarded to the server. With some network architectures, a STUN server is also needed to traverse NAT and discover the public IP addresses of the WebRTC peers. Otherwise, users will experience call failures or a “black screen” when turning on their audio and video.

Integrating Jitsi Meet with RocketChat can also be a challenge. If you only want internal users authenticated to RocketChat to be able to set up Jitsi calls using your Jitsi server, you need to set up a JSON Web Token (JWT). When a new meeting is set up, Jitsi will challenge the RocketChat server to provide the JWT. If the JWT matches the value that Jitsi Meet is expecting based on its configuration, then the room will be created.

Moderators can easily secure their Jitsi meetings by adding a password to their Jitsi meeting, which will prevent further attendees from joining unless they have the password. There is no limit to the number of Jitsi meeting rooms you can create, and the number of simultaneous calls is only limited by the bandwidth and processing power that your Jitsi deployment supports.

If you are concerned about the confidentiality of the voice and video calls that your users hold over Google Meet, Webex, or Zoom, you should consider deploying Jitsi Meet as a secure alternative. Browser vendors have security response teams that work around the clock to patch any vulnerabilities that are discovered in their browsers. As long as your end users practice good security hygiene and keep their browsers up-to-date, using WebRTC in Chrome or Chromium-based browsers is a more secure solution compared to installing additional third-party applications such as WebEx or Zoom.

Contact us about how Jitsi Meet and RocketChat can enable your remote workforce to stay productive even if they are not physically together in the same office. There are no per-seat license fees with Jitsi Meet or RocketChat, making them a cost-effective solution compared to Slack Premium or Microsoft Teams.

You can use Jitsi Meet API to create Jitsi Meet video conferences with a custom GUI.


Jitsi Meet Google Analytics Download

To embed Jitsi Meet API in your application you need to add Jitsi Meet API library

Now you can access Jitsi Meet API trough the JitsiMeetJS global object.

Getting Started

  1. The first thing you must do in order to use Jitsi Meet API is to initialize JitsiMeetJS object:
  1. Then you must create the connection object:
  1. Now we can attach some listeners to the connection object and establish the server connection:
  1. After you receive the CONNECTION_ESTABLISHED event you are to create the JitsiConference object andalso you may want to attach listeners for conference events (we are going to add handlers for remote track, conference joined, etc. ):
  1. You also may want to get your local tracks from the camera and microphone:

NOTE: Adding listeners and creating local streams are not mandatory steps.

  1. Then you are ready to create / join a conference :

After that step you are in the conference. Now you can continue with adding some code that will handle the events and manage the conference.


Jitsi Meet API has the following components:

  • JitsiMeetJS

  • JitsiConnection

  • JitsiConference

  • JitsiTrack

  • JitsiTrackError


JaaS customers, please checkout this example: https://github.com/saghul/sandbox-html/tree/main/jaas-ljm. Live: https://bettercallsaghul.com/sandbox-html/jaas-ljm/


You can access the following methods and objects trough JitsiMeetJS object.

  • JitsiMeetJS.init(options) - this method initialized Jitsi Meet API.The options parameter is JS object with the following properties:

    • useIPv6 - boolean property
    • disableAudioLevels - boolean property. Enables/disables audio levels.
    • disableSimulcast - boolean property. Enables/disables simulcast.
    • enableWindowOnErrorHandler - boolean property (default false). Enables/disables attaching global onerror handler (window.onerror).
    • disableThirdPartyRequests - if true - callstats will be disabled and the callstats API won't be included.
    • enableAnalyticsLogging - boolean property (default false). Enables/disables analytics logging.
    • externalStorage - Object that implements the Storage interface. If specified this object will be used for storing data instead of localStorage.
    • callStatsCustomScriptUrl - (optional) custom url to access callstats client script
    • disableRtx - (optional) boolean property (default to false). Enables/disable the use of RTX.
    • disabledCodec - the mime type of the code that should not be negotiated on the peerconnection.
    • preferredCodec - the mime type of the codec that needs to be made the preferred codec for the connection.
    • useTurnUdp - boolean property (default false). Enables use of turn over udp for jvb. It is disabled because not very useful (if the client can use udp, it likely can connect to jvb directly over udp too; but it can be useful to still enable udp turn when an udp turn is known to be whitelisted on a network)
    • disableH264 - DEPRECATED. Use disabledCodec instead.
    • preferH264 - DEPRECATED. Use preferredCodec instead.
  • JitsiMeetJS.JitsiConnection - the JitsiConnection constructor. You can use that to create new server connection.

  • JitsiMeetJS.setLogLevel - changes the log level for the library. For example to have only error messages you should do:

  • JitsiMeetJS.createLocalTracks(options) - Creates the media tracks and returns them trough Promise object. If rejected, passes JitsiTrackError instance to catch block.

    • options - JS object with configuration options for the local media tracks. You can change the following properties there:
      1. devices - array with the devices - 'desktop', 'video' and 'audio' that will be passed to GUM. If that property is not set GUM will try to get all available devices.
      2. resolution - the prefered resolution for the local video.
      3. constraints - the prefered encoding properties for the created track (replaces 'resolution' in newer releases of browsers)
      4. cameraDeviceId - the deviceID for the video device that is going to be used
      5. micDeviceId - the deviceID for the audio device that is going to be used
      6. minFps - the minimum frame rate for the video stream (passed to GUM)
      7. maxFps - the maximum frame rate for the video stream (passed to GUM)
      8. desktopSharingFrameRate
        • min - Minimum fps
        • max - Maximum fps
      9. desktopSharingSourceDevice - The device id or label for a video input source that should be used for screensharing.
      10. facingMode - facing mode for a camera (possible values - 'user', 'environment')
      11. firePermissionPromptIsShownEvent - optional boolean parameter. If set to true, JitsiMediaDevicesEvents.PERMISSION_PROMPT_IS_SHOWN will be fired when browser shows gUM permission prompt.
      12. fireSlowPromiseEvent - optional boolean parameter. If set to true, JitsiMediaDevicesEvents.USER_MEDIA_SLOW_PROMISE_TIMEOUT will be fired when browser takes too long to resolve the gUM promise. This event is mutual exclusive with the above JitsiMediaDevicesEvents.PERMISSION_PROMPT_IS_SHOWN event
    • firePermissionPromptIsShownEvent - DEPRECATED. Use options.firePermissionPromptIsShownEvent instead
  • JitsiMeetJS.createTrackVADEmitter(localAudioDeviceId, sampleRate, vadProcessor) - Creates a TrackVADEmitter service that connects an audio track to a VAD (voice activity detection) processor in order to obtain VAD scores for individual PCM audio samples.

    • localAudioDeviceId - The target local audio device.
    • sampleRate - Sample rate at which the emitter will operate. Possible values 256, 512, 1024, 4096, 8192, 16384. Passing other values will default to closes neighbor, i.e. Providing a value of 4096 means that the emitter will process bundles of 4096 PCM samples at a time, higher values mean longer calls, lowers values mean more calls but shorter.
    • vadProcessor - VAD Processors that does the actual compute on a PCM sample.The processor needs to implement the following functions:
      • getSampleLength() - Returns the sample size accepted by calculateAudioFrameVAD.
      • getRequiredPCMFrequency() - Returns the PCM frequency at which the processor operates .i.e. (16KHz, 44.1 KHz etc.)
      • calculateAudioFrameVAD(pcmSample) - Process a 32 float pcm sample of getSampleLength size.
  • JitsiMeetJS.enumerateDevices(callback) - DEPRECATED. Use JitsiMeetJS.mediaDevices.enumerateDevices(callback) instead.

  • JitsiMeetJS.isDeviceChangeAvailable(deviceType) - DEPRECATED. Use JitsiMeetJS.mediaDevices.isDeviceChangeAvailable(deviceType) instead.

  • JitsiMeetJS.isDesktopSharingEnabled() - returns true if desktop sharing is supported and false otherwise. NOTE: that method can be used after JitsiMeetJS.init(options) is completed otherwise the result will be always null.

  • JitsiMeetJS.getActiveAudioDevice() - goes through all audio devices on the system and returns information about one that is active, i.e. has audio signal. Returns a Promise resolving to an Object with the following structure:

    • deviceId - string containing the device ID of the audio track found as active.
    • deviceLabel - string containing the label of the audio device.
  • JitsiMeetJS.getGlobalOnErrorHandler() - returns function that can be used to be attached to window.onerror and if options.enableWindowOnErrorHandler is enabled returns the function used by the lib. (function(message, source, lineno, colno, error)).

  • JitsiMeetJS.mediaDevices - JS object that contains methods for interaction with media devices. Following methods are available:

    • isDeviceListAvailable() - returns true if retrieving the device list is supported and false - otherwise
    • isDeviceChangeAvailable(deviceType) - returns true if changing the input (camera / microphone) or output (audio) device is supported and false if not. deviceType is a type of device to change. Undefined or 'input' stands for input devices, 'output' - for audio output devices.
    • enumerateDevices(callback) - returns list of the available devices as a parameter to the callback function. Every device is a MediaDeviceInfo object with the following properties:
      • label - the name of the device
      • kind - 'audioinput', 'videoinput' or 'audiooutput'
      • deviceId - the id of the device
      • groupId - group identifier, two devices have the same group identifier if they belong to the same physical device; for example a monitor with both a built-in camera and microphone
    • setAudioOutputDevice(deviceId) - sets current audio output device. deviceId - id of 'audiooutput' device from JitsiMeetJS.enumerateDevices(), ' is for default device.
    • getAudioOutputDevice() - returns currently used audio output device id, ' stands for default device.
    • isDevicePermissionGranted(type) - returns a Promise which resolves to true if user granted permission to media devices. type - 'audio', 'video' or undefined. In case of undefined will check if both audio and video permissions were granted.
    • addEventListener(event, handler) - attaches an event handler.
    • removeEventListener(event, handler) - removes an event handler.
  • JitsiMeetJS.events - JS object that contains all events used by the API. You will need that JS object when you try to subscribe for connection or conference events.We have two event types - connection and conference. You can access the events with the following code JitsiMeetJS.events.<event_type>.<event_name>.For example if you want to use the conference event that is fired when somebody leave conference you can use the following code - JitsiMeetJS.events.conference.USER_LEFT.We support the following events:

    1. conference

      • TRACK_ADDED - stream received. (parameters - JitsiTrack)
      • TRACK_REMOVED - stream removed. (parameters - JitsiTrack)
      • TRACK_MUTE_CHANGED - JitsiTrack was muted or unmuted. (parameters - JitsiTrack)
      • TRACK_AUDIO_LEVEL_CHANGED - audio level of JitsiTrack has changed. (parameters - participantId(string), audioLevel(number))
      • DOMINANT_SPEAKER_CHANGED - the dominant speaker is changed. (parameters - id(string))
      • USER_JOINED - new user joined a conference. (parameters - id(string), user(JitsiParticipant))
      • USER_LEFT - a participant left conference. (parameters - id(string), user(JitsiParticipant))
      • MESSAGE_RECEIVED - new text message received. (parameters - id(string), text(string), ts(number))
      • DISPLAY_NAME_CHANGED - user has changed his display name. (parameters - id(string), displayName(string))
      • SUBJECT_CHANGED - notifies that subject of the conference has changed (parameters - subject(string))
      • LAST_N_ENDPOINTS_CHANGED - last n set was changed (parameters - leavingEndpointIds(array) ids of users leaving lastN, enteringEndpointIds(array) ids of users entering lastN)
      • CONFERENCE_JOINED - notifies the local user that he joined the conference successfully. (no parameters)
      • CONFERENCE_LEFT - notifies the local user that he left the conference successfully. (no parameters)
      • CONFERENCE_UNIQUE_ID_SET - notifies the local user that the unique id for a meeting has been set. (parameters - meetingId(string))
      • DTMF_SUPPORT_CHANGED - notifies if at least one user supports DTMF. (parameters - supports(boolean))
      • USER_ROLE_CHANGED - notifies that role of some user changed. (parameters - id(string), role(string))
      • USER_STATUS_CHANGED - notifies that status of some user changed. (parameters - id(string), status(string))
      • CONFERENCE_FAILED - notifies that user failed to join the conference. (parameters - errorCode(JitsiMeetJS.errors.conference))
      • CONFERENCE_ERROR - notifies that error occurred. (parameters - errorCode(JitsiMeetJS.errors.conference))
      • KICKED - notifies that user has been kicked from the conference. (parameters - actorParticipant(JitsiParticipant), reason(string))
      • PARTICIPANT_KICKED - notifies that participant has been kicked from the conference by another participant. (parameters - actorParticipant(JitsiParticipant), kickedParticipant(JitsiParticipant), reason(string))
      • START_MUTED_POLICY_CHANGED - notifies that all new participants will join with muted audio/video stream (parameters - JS object with 2 properties - audio(boolean), video(boolean))
      • STARTED_MUTED - notifies that the local user has started muted
      • CONNECTION_STATS - DEPRECATED. Use JitsiMeetJS.events.connectionQuality.LOCAL_STATS_UPDATED instead.
      • BEFORE_STATISTICS_DISPOSED - fired just before the statistics module is disposed and it's the last chance to submit some logs to the statistics service, before it gets disconnected
      • AUTH_STATUS_CHANGED - notifies that authentication is enabled or disabled, or local user authenticated (logged in). (parameters - isAuthEnabled(boolean), authIdentity(string))
      • ENDPOINT_MESSAGE_RECEIVED - notifies that a new messagefrom another participant is received on a data channel.
      • TALK_WHILE_MUTED - notifies that a local user is talking while having the microphone muted.
      • NO_AUDIO_INPUT - notifies that the current selected input device has no signal.
      • AUDIO_INPUT_STATE_CHANGE - notifies that the current conference audio input switched between audio input states i.e. with or without audio input.
      • NOISY_MIC - notifies that the current microphone used by the conference is noisy.
      • PARTICIPANT_PROPERTY_CHANGED - notifies that user has changed his custom participant property. (parameters - user(JitsiParticipant), propertyKey(string), oldPropertyValue(string), propertyValue(string))
    2. connection

      • CONNECTION_FAILED - indicates that the server connection failed.
      • CONNECTION_ESTABLISHED - indicates that we have successfully established server connection.
      • CONNECTION_DISCONNECTED - indicates that we are disconnected.
      • WRONG_STATE - indicates that the user has performed action that can't be executed because the connection is in wrong state.
    3. detection

      • VAD_SCORE_PUBLISHED - event generated by a TackVADEmitter when it computed a VAD score for an audio PCM sample.
    4. track

      • LOCAL_TRACK_STOPPED - indicates that a local track was stopped. Thisevent can be fired when dispose() method is called or for other reasons.
      • TRACK_AUDIO_OUTPUT_CHANGED - indicates that audio output device for track was changed (parameters - deviceId (string) - new audio output device ID).
    5. mediaDevices

      • DEVICE_LIST_CHANGED - indicates that list of currently connected devices has changed (parameters - devices(MediaDeviceInfo[])).
      • PERMISSION_PROMPT_IS_SHOWN - Indicates that the environment is currently showing permission prompt to access camera and/or microphone (parameters - environmentType ('chrome' 'opera' 'firefox' 'safari' 'nwjs' 'react-native' 'android').
    6. connectionQuality

      • LOCAL_STATS_UPDATED - New local connection statistics are received. (parameters - stats(object))
      • REMOTE_STATS_UPDATED - New remote connection statistics are received. (parameters - id(string), stats(object))
  • JitsiMeetJS.errors - JS object that contains all errors used by the API. You can use that object to check the reported errors from the APIWe have three error types - connection, conference and track. You can access the events with the following code JitsiMeetJS.errors.<error_type>.<error_name>.For example if you want to use the conference event that is fired when somebody leave conference you can use the following code - JitsiMeetJS.errors.conference.PASSWORD_REQUIRED.We support the following errors:

    1. conference
      • CONNECTION_ERROR - the connection with the conference is lost.
      • SETUP_FAILED - conference setup failed
      • AUTHENTICATION_REQUIRED - user must be authenticated to create this conference
      • PASSWORD_REQUIRED - that error can be passed when the connection to the conference failed. You should try to join the conference with password.
      • PASSWORD_NOT_SUPPORTED - indicates that conference cannot be locked
      • VIDEOBRIDGE_NOT_AVAILABLE - video bridge issues.
      • RESERVATION_ERROR - error in reservation system
      • GRACEFUL_SHUTDOWN - graceful shutdown
      • JINGLE_FATAL_ERROR - error in jingle (the orriginal error is attached as parameter.)
      • CONFERENCE_DESTROYED - conference has been destroyed
      • CHAT_ERROR - chat error happened
      • FOCUS_DISCONNECTED - focus error happened
      • FOCUS_DISCONNECTED - focus left the conference
      • CONFERENCE_MAX_USERS - The maximum users limit has been reached
    2. connection
      • CONNECTION_DROPPED_ERROR - indicates that the connection was dropped with an error which was most likely caused by some networking issues.
      • PASSWORD_REQUIRED - passed when the connection to the server failed. You should try to authenticate with password.
      • SERVER_ERROR - indicates too many 5XX errors were received from the server.
      • OTHER_ERROR - all other errors
    3. track
      • GENERAL - generic getUserMedia-related error.
      • UNSUPPORTED_RESOLUTION - getUserMedia-related error, indicates that requested video resolution is not supported by camera.
      • PERMISSION_DENIED - getUserMedia-related error, indicates that user denied permission to share requested device.
      • NOT_FOUND - getUserMedia-related error, indicates that requested device was not found.
      • CONSTRAINT_FAILED - getUserMedia-related error, indicates that some of requested constraints in getUserMedia call were not satisfied.
      • TRACK_IS_DISPOSED - an error which indicates that track has been already disposed and cannot be longer used.
      • TRACK_NO_STREAM_FOUND - an error which indicates that track has no MediaStream associated.
      • SCREENSHARING_GENERIC_ERROR - generic error for screensharing.
      • SCREENSHARING_USER_CANCELED - an error which indicates that user canceled screen sharing window selection dialog.
  • JitsiMeetJS.errorTypes - constructors for Error instances that can be produced by library. Are useful for checks like error instanceof JitsiMeetJS.errorTypes.JitsiTrackError. Following Errors are available:

    1. JitsiTrackError - Error that happened to a JitsiTrack.
  • JitsiMeetJS.logLevels - object with the log levels:

    1. TRACE
    2. DEBUG
    3. INFO
    4. LOG
    5. WARN
    6. ERROR


This objects represents the server connection. You can create new JitsiConnection object with the constructor JitsiMeetJS.JitsiConnection. JitsiConnection has the following methods:

  1. JitsiConnection(appID, token, options) - constructor. Creates the conference object.

    • appID - identification for the provider of Jitsi Meet video conferencing services. NOTE: not implemented yet. You can safely pass null
    • token - secret generated by the provider of Jitsi Meet video conferencing services. The token will be send to the provider from the Jitsi Meet server deployment for authorization of the current client.
    • options - JS object with configuration options for the server connection. You can change the following properties there:
      1. serviceUrl - XMPP service URL. For example 'wss://server.com/xmpp-websocket' for Websocket or '//server.com/http-bind' for BOSH.
      2. bosh - DEPRECATED, use serviceUrl to specify either BOSH or Websocket URL.
      3. hosts - JS Object
        • domain
        • muc
        • anonymousdomain
      4. enableLipSync - (optional) boolean property which enables the lipsync feature. Currently works only in Chrome and is disabled by default.
      5. clientNode - The name of client node advertised in XEP-0115 'c' stanza
      6. xmppPing - (optional) JS Object - xmpp ping options
        • interval - how often to send ping requests, default: 10000 (10 seconds)
        • timeout - the time to wait for ping responses, default: 5000 (5 seconds)
        • threshold - how many ping failures will be tolerated before the connection is killed, default: 2
      7. websocketKeepAlive - (optional) Setting the interval of websocket keepalive GET requests. By default, the value is 1 minute(which means a minute + a minute of jitter).Used for certain deployments where a stick table entry needs to be kept alive we use those GET requests.
      8. websocketKeepAliveUrl - (optional) Specific Url to use for the websocket keepalive GET requests.
  2. connect(options) - establish server connection

    • options - JS Object with id and password properties.
  3. disconnect() - destroys the server connection

  4. initJitsiConference(name, options) - creates new JitsiConference object.

    • name - the name of the conference

    • options - JS object with configuration options for the conference. You can change the following properties there:

      • openBridgeChannel - Enables/disables bridge channel. Values can be 'datachannel', 'websocket', true (treat it as 'datachannel'), undefined (treat it as 'datachannel') and false (don't open any channel). NOTE: we recommend to set that option to true
      • recordingType - the type of recording to be used
      • callStatsID - callstats credentials
      • callStatsSecret - callstats credentials
      • enableTalkWhileMuted - boolean property. Enables/disables talk while muted detection, by default the value is false/disabled.
      • ignoreStartMuted - ignores start muted events coming from jicofo.
      • startSilent - enables silent mode, will mark audio as inactive will not send/receive audio
      • confID - Used for statistics to identify conference, if tenants are supported will contain tenant and the non lower case variant for the room name.
      • siteID - (optional) Used for statistics to identify the site where the user is coming from, if tenants are supported it will contain a unique identifier for that tenant. If not provided, the value will be infered from confID
      • statisticsId - The id to be used as stats instead of default callStatsUsername.
      • statisticsDisplayName - The display name to be used for stats, used for callstats.
      • focusUserJid - The real JID of focus participant - can be overridden here
      • enableNoAudioDetection
      • enableNoisyMicDetection
      • enableRemb
      • enableTcc
      • useRoomAsSharedDocumentName
      • channelLastN
      • startBitrate
      • stereo
      • forceJVB121Ratio - 'Math.random() < forceJVB121Ratio' will determine whether a 2 people conference should be moved to the JVB instead of P2P. The decision is made on the responder side, after ICE succeeds on the P2P connection.
      • hiddenDomain
      • startAudioMuted
      • startVideoMuted
      • enableLayerSuspension - if set to 'true', we will cap the video send bitrate when we are told we have not been selected by any endpoints (and therefore the non-thumbnail streams are not in use).
      • deploymentInfo
        • shard
        • userRegion
      • p2p - Peer to peer related options
        • enabled - enables or disable peer-to-peer connection, if disabled all media will be routed through the Jitsi Videobridge.
        • stunServers - list of STUN servers e.g. { urls: 'stun:meet-jit-si-turnrelay.jitsi.net:443' }
        • backToP2PDelay - a delay given in seconds, before the conference switches back to P2P, after the 3rd participant has left the room.
        • disabledCodec - the mime type of the code that should not be negotiated on the peerconnection.
        • preferredCodec the mime type of the codec that needs to be made the preferred codec for the connection.
        • disableH264 - DEPRECATED. Use disabledCodec instead.
        • preferH264 - DEPRECATED. Use preferredCodec instead.
      • rttMonitor
        • enabled
        • initialDelay
        • getStatsInterval
        • analyticsInterval
        • stunServers
      • e2eping
        • pingInterval
      • abTesting - A/B testing related options
        • enableSuspendVideoTest
      • testing
        • capScreenshareBitrate
        • p2pTestMode
        • octo
          • probability

      NOTE: if 4 and 5 are set the library is going to send events to callstats. Otherwise the callstats integration will be disabled.

  5. addEventListener(event, listener) - Subscribes the passed listener to the event.

    • event - one of the events from JitsiMeetJS.events.connection object.
    • listener - handler for the event.
  6. removeEventListener(event, listener) - Removes event listener.

    • event - the event
    • listener - the listener that will be removed.
  7. addFeature - Adds new feature to the list of supported features for the local participant

    • feature - string, the name of the feature
    • submit - boolean, default false, if true - the new list of features will be immediately submitted to the others.
  8. removeFeature - Removes a feature from the list of supported features for the local participant

    • feature - string, the name of the feature
    • submit - boolean, default false, if true - the new list of features will be immediately submitted to the others.



The object represents a conference. We have the following methods to control the conference:

  1. join(password) - Joins the conference

    • password - string of the password. This parameter is not mandatory.
  2. leave() - leaves the conference. Returns Promise.

  3. myUserId() - get local user ID.

  4. getLocalTracks() - Returns array with JitsiTrack objects for the local streams.

  5. addEventListener(event, listener) - Subscribes the passed listener to the event.

    • event - one of the events from JitsiMeetJS.events.conference object.
    • listener - handler for the event.
  6. removeEventListener(event, listener) - Removes event listener.

    • event - the event
    • listener - the listener that will be removed.
  7. on(event, listener) - alias for addEventListener

  8. off(event, listener) - alias for removeEventListener

  9. sendTextMessage(text) - sends the given string to other participants in the conference.

  10. setDisplayName(name) - changes the display name of the local participant.

    • name - the new display name
  11. selectParticipant(participantId) - Elects the participant with the given id to be the selected participant in order to receive higher video quality (if simulcast is enabled).

    • participantId - the identifier of the participant

Throws NetworkError or InvalidStateError or Error if the operation fails.

  1. sendCommand(name, values) - sends user defined system command to the other participants
    • name - the name of the command.
    • values - JS object. The object has the following structure:

Jitsi Meet Online

  1. sendCommandOnce(name, values) - Sends only one time a user defined system command to the other participants
  1. removeCommand(name) - removes a command for the list of the commands that are sent to the ther participants

    • name - the name of the command
  2. addCommandListener(command, handler) - adds listener

    • command - string for the name of the command
    • handler(values) - the listener that will be called when a command is received from another participant.
  3. removeCommandListener(command) - removes the listeners for the specified command

    • command - the name of the command
  4. addTrack(track) - Adds JitsiLocalTrack object to the conference. Throws an error if adding second video stream. Returns Promise.

    • track - the JitsiLocalTrack
  5. removeTrack(track) - Removes JitsiLocalTrack object to the conference. Returns Promise.

    • track - the JitsiLocalTrack
  6. isDTMFSupported() - Check if at least one user supports DTMF.

  7. getRole() - returns string with the local user role ('moderator' or 'none')

  8. isModerator() - checks if local user has 'moderator' role

  9. lock(password) - set password for the conference; returns Promise

    • password - string password

    Note: available only for moderator

  10. unlock() - unset conference password; returns Promise

    Note: available only for moderator

  11. kickParticipant(id, reason) - Kick participant from the conference

    • id - string participant id
    • reason - (optional) string, default 'You have been kicked.' - reason of the participant to kick
  12. setStartMutedPolicy(policy) - make all new participants join with muted audio/video

    • policy - JS object with following properties
      • audio - boolean if audio stream should be muted
      • video - boolean if video stream should be muted

    Note: available only for moderator

  13. getStartMutedPolicy() - returns the current policy with JS object:

    • policy - JS object with following properties
      • audio - boolean if audio stream should be muted
      • video - boolean if video stream should be muted
  14. isStartAudioMuted() - check if audio is muted on join

  15. isStartVideoMuted() - check if video is muted on join

  16. sendFeedback(overallFeedback, detailedFeedback) - Sends the given feedback through CallStats if enabled.

    • overallFeedback - an integer between 1 and 5 indicating the user feedback
    • detailedFeedback - detailed feedback from the user. Not yet used
  17. setSubject(subject) - change subject of the conference

    • subject - string new subject

    Note: available only for moderator

  18. sendEndpointMessage(to, payload) - Sends message via the data channels.

    • to - the id of the endpoint that should receive the message. If ' the message will be sent to all participants.
    • payload - JSON object - the payload of the message.

Throws NetworkError or InvalidStateError or Error if the operation fails.

  1. sendEndpointStatsMessage(payload) - Sends a EndpointStats Colibri message on the bridge channel. This should be used instead of broadcastEndpointMessage for relaying local stats to all the remote endpoints.
    • payload - JSON object - the payload of the message.

Throws NetworkError, InvalidStateError or Error if the operation fails.

  1. broadcastEndpointMessage(payload) - Sends broadcast message via the datachannels.
    • payload - JSON object - the payload of the message.

Throws NetworkError or InvalidStateError or Error if the operation fails.

  1. replaceTrack - replaces the track currently being used as the sender's source with a new MediaStreamTrack. The new track must be of the same media kind (audio, video, etc) and switching the track should not require negotiation. replaceTrack(oldTrack, newTrack)

Throws NetworkError or InvalidStateError or Error if the operation fails.

  1. setReceiverConstraints - set the constraints for the video that is requested from the bridge. This single message should be used in lieu of setLastN, setReceiverVideoConstraint and selectParticipants methods. These constraints are applicable to bridge connection only. More information about the signaling message format and how the Jitsi Videobridge allocates bandwidth can be found here.

    • videoConstraints - Object that specifies the constraints in the following format.
  2. setReceiverVideoConstraint(resolution) - set the desired resolution to get from JVB (180, 360, 720, 1080, etc).You should use that method if you are using simulcast.

  3. setSenderVideoConstraint(resolution) - set the desired resolution to send to JVB or the peer (180, 360, 720).

  4. isHidden - checks if local user has joined as a 'hidden' user. This is a specialized role used for integrations.

  5. setLocalParticipantProperty(propertyKey, propertyValue) - used to set a custom propery to the local participant('fullName': 'Full Name', favoriteColor: 'red', 'userId': 234). Also this can be used to modify an already set custom property.

    • propertyKey - string - custom property name
    • propertyValue - string - custom property value
  6. getParticipants() - Retrieves an array of all participants in this conference.

  7. revokeOwner(participantId) - Revokes owner's rights to the participant. The particiapnt that invokes the function should have same or more rights than the targeted participant. This rights check is done at the XMPP server level.


The object represents single track - video or audio. They can be remote tracks ( from the other participants in the call) or local tracks (from the devices of the local participant).We have the following methods for controling the tracks:

  1. getType() - returns string with the type of the track( 'video' for the video tracks and 'audio' for the audio tracks)

  2. mute() - mutes the track. Returns Promise.

    Note: This method is implemented only for the local tracks.

  3. unmute() - unmutes the track. Returns Promise.

    Note: This method is implemented only for the local tracks.

  4. isMuted() - check if track is muted

  5. attach(container) - attaches the track to the given container.

  6. detach(container) - removes the track from the container.

  7. dispose() - disposes the track. If the track is added to a conference the track will be removed. Returns Promise.

    Note: This method is implemented only for the local tracks.

  8. getId() - returns unique string for the track.

  9. getParticipantId() - returns id(string) of the track owner

    Note: This method is implemented only for the remote tracks.

  10. setAudioOutput(audioOutputDeviceId) - sets new audio output device for track's DOM elements. Video tracks are ignored.

  11. getDeviceId() - returns device ID associated with track (for local tracks only)

  12. isEnded() - returns true if track is ended

  13. setEffect(effect) - Applies the effect by swapping out the existing MediaStream on the JitsiTrack with the new

    MediaStream which has the desired effect. 'undefined' is passed to this function for removing the effect and for

    restoring the original MediaStream on the JitsiTrack.

    The following methods have to be defined for the effect instance.

    startEffect() - Starts the effect and returns a new MediaStream that is to be swapped with the existing one.

    stopEffect() - Stops the effect.

    isEnabled() - Checks if the local track supports the effect.

    Note: This method is implemented only for the local tracks.


The object represents error that happened to a JitsiTrack. Is inherited from JavaScript base Error object,so 'name', 'message' and 'stack' properties are available. For GUM-related errors,exposes additional 'gum' property, which is an object with following properties:

  • error - original GUM error
  • constraints - GUM constraints object used for the call
  • devices - array of devices requested in GUM call (possible values - 'audio', 'video', 'screen', 'desktop', 'audiooutput')