Initial platform configuration
After you have run the installation wizard, you must perform some preliminary configuration of the Pexip Infinity platform before you can then deploy a Conferencing Node.
This section lists the configuration required, and provides a summary of each step with a link to further information.
All configuration should be done using the Pexip Infinity Administrator interface.
The Pexip Infinity Administrator interface is hosted on the Management Node. To access this:
- Open a web browser and type in the IP address or DNS name that you assigned to the Management Node using the installation wizard (you may need to wait a minute or so after installation is complete before you can access the Administrator interface).
- Until you have uploaded appropriate TLS certificates to the Management Node, your browser may present you with a warning that the website's security certificate is not trusted. You should proceed, but upload appropriate TLS certificates to the Management Node (and Conferencing Nodes, when they have been created) as soon as possible.
Thelogin page will appear.
- Log in using the web administration username and password you set using the installation wizard.
You are now ready to begin configuring the Pexip Infinity service and deploying Conferencing Nodes.
As a first step, we strongly recommend that you configure at least 2 additional NTP servers or NTP server pools to ensure that log entries from all nodes are properly synchronized. For details, see Enabling NTP on the Management Node.
Brief details of how to perform the initial configuration are given below.
At least one DNS server must be added to your system. DNS is required when using hostnames instead of IP addresses when setting up NTP servers, syslog servers and VM managers. It is also used for call routing that depends on FQDNs.
You will already have configured at least one DNS server when running the install wizard, but you can now change it or add more DNS servers.
See Enabling DNS for more information.
Pexip Infinity uses NTP servers to obtain accurate system time. This is necessary to ensure correct operation, including configuration replication and log timestamps.
We strongly recommend that you configure at least 3 distinct NTP servers or NTP server pools to ensure that log entries from all nodes are properly synchronized.
You will already have configured at least one NTP server when running the install wizard, but you can now change it or add more NTP servers.
See Enabling NTP on the Management Node for more information.
You must install a system license with sufficient concurrent call capacity for your environment before you can place calls to Pexip Infinity services.
See Pexip Infinity license installation and usage for more information.
Adding a system location
These are labels that allow you to group together Conferencing Nodes that are in the same datacenter. You must have at least one location configured before you can deploy a Conferencing Node.
See About system locations for more information.
Uploading TLS certificates
You must install TLS certificates on the Management Node and each Conferencing Node. TLS certificates are used by these systems to verify their identity to clients connecting to them.
All nodes are deployed with self-signed certificates, but we strongly recommend they are replaced with ones signed by either an external CA or a trusted internal CA.
See Managing TLS and trusted CA certificates for more information.
Adding a Virtual Meeting Room
Conferences take place in Virtual Meeting Rooms and Virtual Auditoriums. Configuration includes any PINs required to access the conference.
See Configuring Virtual Meeting Rooms for more information.
Adding an alias for the Virtual Meeting Room
(done while adding the Virtual Meeting Room)
A Virtual Meeting Room or Virtual Auditorium can have more than one alias. Conference participants can access a Virtual Meeting Room or Virtual Auditorium by dialing any one of its aliases directly.
See About aliases for more information.
You are now ready to deploy a Conferencing Node. See Manually deploying a Conferencing Node on a KVM host for more information.