Rate this page:

How to build a conference

Voximplant comprises the Conference module to create Local and Standalone conference calls. Learn the architecture basics of both approaches below.

Local conference

There is only one JS scenario needed for this type of conference. To start the scenario, you have to make a phone call (initiation call) or an HTTP request to it. After that, the scenario will call other participants via PSTN/SIP and add them to the conference (up to 49 calls per session). All the endpoints will hear each other and won't hear themselves.

no incoming calls

Note that Local conferences don't accept any incoming calls except for the initial one.

Look at the skeleton of a Local conference that should be started via an incoming call:

local conference

local conference

Standalone Conference

Standalone conference takes up to 100 endpoints (incoming and outgoing) and requires one or two scenarios, depending on a usage case.

Standalone: One Scenario

If your users will be joining a conference only via SDK-based clients, you need only one scenario (see the code in the next section).

Standalone: Two Scenarios

If you want incoming PSTN/SIP calls, the conference will require an additional gateway scenario to accept incoming calls and forward them to a conference:

gateway scenario

gateway scenario

The code is quite simple, but pay attention to line 5:

gateway scenario – line 5

gateway scenario – line 5

When you create a rule for the second scenario, its Pattern filed should contain the same value as was passed to the callConference call in the previous scenario. In our case, it's "conferenceId".

Next, you have to create a conference scenario which process inbound calls from the gateway and can initiate outbound calls; all the calls are eventually connected to the conference.

conference scenario

conference scenario

These are the basics of creating conferences in Voximplant. For more details, you can check this tutorial revealing all the nuances of the topic.