Bulk import/export of service configuration data

If you want to configure your Pexip Infinity platform with a large number of Virtual Meeting Rooms, Virtual Auditoriums, Virtual Receptions, Automatically Dialed Participants (APDs) or device aliases, you can import the configuration for each of these items from a CSV file.

You can also export all of your existing service configuration data to a CSV file. You may want to do this for backup purposes or to transfer configuration between, for example, a test system and a production system.

You can also use a CSV file to import multiple endpoints for One-Touch Join (see Adding OTJ endpoints in bulk for more information).

You can import Virtual Meeting Rooms and device aliases from directory information contained in a Windows Active Directory LDAP server, or any other LDAP-accessible database. For more information, see Provisioning VMRs, devices and users from Active Directory via LDAP.

Preparing the CSV file for import

When formatting your import file:

  • A header row in the CSV file is optional. If included, it must use the same field names as shown in the following sections, but you may change the order of the fields. If a header row is not used, fields must be in the same order as shown for each import file type.
  • All non-blank fields must contain valid data, for example the pin field must only contain digits and the dtmf_sequence field must only contain digits or commas.
  • If non-ASCII characters are used, the file must be encoded as UTF-8 text.
  • Fields with values of true or false are not case-sensitive. All other fields are case-sensitive.
  • Values may optionally be enclosed in double quotation marks; any strings containing commas must be enclosed in double quotation marks e.g. "description for x, y and z".

Note that you can perform an export of existing data to produce an example file in the correct format.

The sections below contain the specific field requirements for your service, device alias or ADP import file.