Skip to content

Video Conferencing

ConnectyCube Multiparty Video Conferencing API is built on top of WebRTC protocol and based on top of WebRTC SFU architecture.

Max people per Conference call is 12.

Video Conferencing is available starting from Advanced plan.

To get a difference between P2P calling and Conference calling please read our ConnectyCube Calling API comparison blog page.

Features supported

  • Video/Audio Conference with up to 12 people
  • Join-Rejoin video room functionality (like Skype)
  • Guest rooms
  • Mute/Unmute audio/video streams
  • Display bitrate
  • Switch video input device (camera)
  • Switch audio input device (microphone)

Get started with SDK

Follow the Getting Started guide on how to connect ConnectyCube SDK and start building your first app.

Code samples

There are ready-to-go FREE code samples to help you better understand how to integrate multiparty video conferencing capabilities in your apps:

Conference Calling code sample for Web (React)

Conference Calling code sample for Web (Angular)

Conference Calling code sample for Web (vanilla JS)


Connect adapter.js

Make sure you connected the latest version of adapter.js

Set up config

In order to start working with Multiparty Video Conferencing API you need to initialize a client:

const credentials = {
appId: ...,
authKey: "...",
authSecret: "..."
const MULTIPARTY_SERVER_ENDPOINT = 'wss://...:8989';
const appConfig = {
debug: { mode: 1 },
conference: { server: MULTIPARTY_SERVER_ENDPOINT },
ConnectyCube.init(credentials, appConfig)

Default multiparty server endpoint is wss:// (see).

Create meeting

In order to have a conference call, a meeting object has to be created.

const params = {
name: "My meeting",
start_date: timestamp,
end_date: timestamp
attendees: [
{id: 123, email: "..."},
{id: 124, email: "..."}
record: false,
chat: false
.then(meeting => {
const confRoomId = meeting._id;
.catch(error => { });

Once meeting is created, you can use meeting._id as a conf room identifier in the below requests when join a call.

Create call session

Once a meeting is created/retrieved, you can create a conf call session. Normally, each browser tab will need a single session with the server:

const session = ConnectyCube.videochatconference.createNewSession();

Once a session is created, you can interact with a Video Conferencing API.

Access local media stream

In order to have a video chat session you need to get an access to the user’s devices (webcam / microphone):

const mediaParams = {
audio: true,
video: true,
.then((localStream) => {})
.catch((error) => {});

This method lets the browser ask the user for permission to use devices. You should allow this dialog to access the stream. Otherwise, the browser can’t obtain access and will throw an error for getUserMedia callback function.

For more information about possible audio/video constraints, here is a good code sample from WebRTC team how to work with getUserMedia constraints:

HD video quality

If HD video quality is required - the following audio/video constraints are required to pass:

{video: { width: 1280, height: 720 }, audio: true}

More info about all possible is are available here

Attach local media stream

Then you should attach your local media stream to HTML video element.

For Web-like environments, including Cordova - use the following method:

session.attachMediaStream("myVideoElementId", localStream, {
muted: true,
mirror: true,

For ReactNative environment - use the following method:

import {RTCView} from 'react-native-connectycube';
// pass a local or remote stream to the RTCView component
<RTCView objectFit="cover" style={styles.rtcView} key={userId} streamURL={localStream.toURL()} />

Join room

To jump into video chat with users you should join it:

.join(confRoomId, userId, userDisplayName)
.then(() => {})
.catch((error) => {});

To check current joined video room use the following property:

const confRoomId = session.currentRoomId;

Join as listener

It can be a requirement where it needs to join a room as listener only, w/o publishing own media stream. It can be useful for a case with a teacher and many students where normally students join a call as listeners and only a teacher publishes own media stream:

.joinAsListener(confRoomId, userId, userDisplayName)
.then(() => {})
.catch((error) => {});

List online participants

To list online users in a room:

.then((participants) => {})
.catch((error) => {});


There are 6 events you can listen for:

ConnectyCube.videochatconference.onParticipantJoinedListener = (
) => {};
ConnectyCube.videochatconference.onParticipantLeftListener = (session, userId) => {};
ConnectyCube.videochatconference.onRemoteStreamListener = (session, userId, stream) => {};
ConnectyCube.videochatconference.onSlowLinkListener = (session, userId, uplink, nacks) => {};
ConnectyCube.videochatconference.onRemoteConnectionStateChangedListener = (session, userId, iceState) => {};
ConnectyCube.videochatconference.onSessionConnectionStateChangedListener = (session, iceState) => {};
ConnectyCube.videochatconference.onErrorListener = (session, error) => {};

Mute/Unmute audio

You can mute/unmute your own audio:

// mute
// unmute
//check mute state
session.isAudioMuted(); // true/false

Mute/Unmute video

You can mute/unmute your own video:

// mute
// unmute
//check mute state
session.isVideoMuted(); // true/false

List of devices

// get all devices
.then((allDevices) => {})
.catch((error) => {});
// only video devices
.then((videoDevices) => {})
.catch((error) => {});
// only audio devices
.then((audioDevices) => {})
.catch((error) => {});

Switch video(camera)/audio(microphone) input device

const deviceId = "...";
// switch video
.switchMediaTracks({ video: deviceId })
.then((updatedLocaStream) => {}) // you can reattach local stream
.catch((error) => {});
// switch audio
.switchMediaTracks({ audio: deviceId })
.then((updatedLocaStream) => {}) // you can reattach local stream
.catch((error) => {});

Screen Sharing

Request a desktop stream by calling getDisplayMedia:

const constraints = {
video: {
width: 1280,
height: 720,
frameRate: { ideal: 10, max: 15 },
audio: true,
.then((localDesktopStream) => {})
.catch((error) => {});

More info about what else options can be passed can be found here

If the local stream already exists, the next call to getUserMedia or getDisplayMedia will update the tracks in the stream and preserve the track’s enabled state for the audio track.

Get remote user bitrate

const bitrate = session.getRemoteUserBitrate(userId);

Get remote user mic level

const micLevel = session.getRemoteUserVolume(userId);

Leave room and destroy conf session

To leave current joined video room:

.then(() => {})
.catch((error) => {});

Retrieve meetings

Retrieve a meeting by id:

const params = {
_id: meetingId,
.then((meeting) => {})
.catch((error) => {});

Retrieve a list of meetings:

const params = { limit: 5, offset: 0 };
.then((meetings) => {})
.catch((error) => {});

Edit meeting

A meeting creator can edit a meeting:

const params = { name, start_date, end_date };
.update(meetingId, params)
.then((meeting) => {})
.catch((error) => {});

Delete meeting

A meeting creator can delete a meeting:

.then(() => {})
.catch((error) => {});


Server-side recording is available. Read more about Recording feature

Retrieve recordings with download url

.then(() => {})
.catch((error) => {});

Continue calling in background

If you are developing dedicated apps for iOS and Android - it’s required to apply additional configure for the app to continue playing calling audio when it goes into the background.

On iOS: there is no way to continue a video call in background because of some OS restrictions. What is supported there is to continue with voice calling while an app is in background. Basically, the recommended to achieve this is to switch off device camera when an app goes to background and then switch camera on back when an app goes to foreground.

Furthermore, even voice background call are blocked by default on iOS. To unblock - you need to setup proper background mode capabilities in your project. Please find the Enabling Background Audio link with more information how to do it properly. Generally speaking, you need to enable Voice over IP and Remote notifications capabilities:

Setup Xcode VOIP capabilities

For Android, we also recommend to implement the same camera switch flow when go to background and then return to foreground.