Configuring Virtual Meeting Rooms
Virtual Meeting Rooms are used to hold Pexip Infinity conferences. Each Virtual Meeting Room has one or more aliases associated with it, and participants access the conference by dialing one of these aliases.
When creating a new Virtual Meeting Room, you must provide at least one alias that will be used to access it. You can also optionally configure PINs for the conference.
To create a new Virtual Meeting Room, go to and click .
To edit an existing Virtual Meeting Room, or to view its details (including all the aliases associated with it), go to and select the name of the Virtual Meeting Room.
As an alternative to manually configuring your Virtual Meeting Rooms:
-
You can import Virtual Meeting Rooms from directory information contained in a Windows Active Directory LDAP server, or any other LDAP-accessible database. For more information, see Provisioning VMRs and devices from Active Directory via LDAP.
- You can bulk import basic Virtual Meeting Rooms configuration from a CSV file. See Bulk import / export of basic Virtual Meeting Room or Virtual Auditorium configuration.
- You can also manage Virtual Meeting Rooms using the Pexip Infinity API.
Any configuration changes made to Virtual Meeting Rooms are replicated to all Conferencing Nodes within 60 seconds and applied to any subsequent conferences in that Virtual Meeting Room. If there are any conferences already in place that use the Virtual Meeting Room, any attempts to join it after the configuration has been replicated may be affected by the new configuration settings. For this reason, we do not recommend changing Virtual Meeting Room configuration while a conference is in progress as this may lead to an inconsistent user experience.
When adding or editing Virtual Meeting Rooms, the options are:
Option | Description |
---|---|
Name | The name used to refer to this Virtual Meeting Room. |
Description | A description of the Virtual Meeting Room. |
Host PIN |
This optional field allows you to set a secure access code that must be entered by Virtual Meeting Room participants before they can join the conference. If Allow Guests is set to Yes, then the Host PIN will apply to the conference Host(s) only. For more information, see About PINs, Hosts and Guests.
|
Allow Guests |
Yes: the conference will have two types of participants, Hosts and Guests. You must configure a Host PIN to be used by the Hosts. You can optionally configure a Guest PIN; if you do not configure a Guest PIN, Guests can join without a PIN, but the meeting will not start until the first Host has joined. No: all participants will have Host privileges. Default: No. |
Guest PIN |
This optional field allows you to set a secure access code that must be entered by Virtual Meeting Room Guests before they can join the conference. For more information, see About PINs, Hosts and Guests.
|
View |
The maximum number of other participants that each participant will see, and the layout used to show them. For more information, see Selecting the layout seen by participants. Default: Large main speaker and up to 7 other participants (1+7 layout). |
Theme |
The theme for use with this Virtual Meeting Room. For more information, see Customizing images and voice prompts using themes. Default: <use Default theme> (the global default theme will be used). |
Advanced options | |
Automatically Dialed Participants |
When a conference begins in this Virtual Meeting Room, a call will be placed automatically to any participants selected here. To add an Automatically Dialed Participant that is not already on the list, select the icon to the right of the selection fields. For more information, see Automatically dialing out to a participant from a conference. |
Maximum inbound call bandwidth (kbps) |
Enter a value in this field to limit the bandwidth of media being received by Pexip Infinity from each individual participant dialed in to this Virtual Meeting Room. For more information see Restricting call bandwidth. |
Maximum outbound call bandwidth (kbps) |
Enter a value in this field to limit the bandwidth of media being sent from Pexip Infinity to each individual participant dialed in to this Virtual Meeting Room. For more information see Restricting call bandwidth. |
Conference capabilities |
Allows you to limit the media content of the conference. For more information, see Controlling media capability. Default: Main video + presentation. |
Participant limit |
This optional field allows you to limit the number of participants allowed to join this Virtual Meeting Room. For more information see Limiting the number of participants. |
Service tag |
This optional field allows you to assign a unique identifier to this service, which you can then use to track use of the service. |
VMR origin |
The name of the LDAP sync template used to create this VMR; if the VMR was created by manual input, CSV import, or via the API this will be blank. This field is read-only. |
Owner's email address | The email address of the owner of the VMR. VMR provisioning messages associated with this VMR will be sent to this address. |
Aliases | |
Alias: #1 | |
Alias |
The alias that, when received by Pexip Infinity, will cause it to route the call to this service (Virtual Meeting Room, Virtual Auditorium or Virtual Reception). The alias entered here must match exactly the alias as it is received by Pexip Infinity. Wildcards and regular expressions are not supported. In most cases, the alias received by Pexip Infinity will be the same as the alias that the conference participant dialed from their endpoint, but there are some exceptions, described in About aliases. You may also want to define multiple aliases for the same service to ensure that it can be accessed by devices and protocols that enforce specific alias formats — for more information, see Using multiple aliases to access the same service. |
Description | An optional description of the alias. This is useful if you have more than one alias for a service. |
Add another Alias | Select this option if you want the Virtual Meeting Room to be accessible by more than one alias. For more information, see Using multiple aliases to access the same service. |