RTCMultiConnection Docs

RTCMultiConnection API Reference / "sessionid"

By default, channel is used as sessionid. It means that a channel can contain only one session. You can override this behaviour by setting sessionid object.

A "sessionid" can be set like this:

initiator.sessionid = 'unique-session-id';

// or
initiator.open('sessionid');

// or
participant.connect('sessionid');

// since v1.7, you can invoke "join" method directly
participant.join('sessionid', optional_joinAs);

Now, this channel can contain multiple sessions; each session can be uniquely identified using sessionid. Each session will act as a unique conference room.

var common_channelid = 'channel-id';

var room1 = new RTCMultiConnection(common_channelid);
var room2 = new RTCMultiConnection(common_channelid);
var room3 = new RTCMultiConnection(common_channelid);
var room4 = new RTCMultiConnection(common_channelid);

room1.open('room1');
room2.open('room2');
room3.open('room3');
room4.open('room4');

All rooms are part of single channel. onNewSession event will be fired for each room.

var common_channelid = 'channel-id';

var room1 = new RTCMultiConnection(common_channelid);
var room2 = new RTCMultiConnection(common_channelid);
var room3 = new RTCMultiConnection(common_channelid);
var room4 = new RTCMultiConnection(common_channelid);

room1.join('room1');
room2.join('room2');
room3.join('room3');
room4.join('room4');


Want to ask a Question?

You can include your email for private conversation!

Latest Updates