Deploying a Conferencing Node in Azure

After deploying the Management Node you can deploy one or more Conferencing Nodes in Azure to provide conferencing capacity.

To deploy a Conferencing Node in Azure:

  1. Create a VM instance using the prepared Conferencing Node disk image. For more information on this, see:

    Each Conferencing Node VM instance must be deployed in its own storage container and its own resource group.

  2. After the instance has booted, perform a configuration-only deployment on the Management Node to inform it of the new Conferencing Node:

    1. Log in to the Pexip Infinity Administrator interface on the Management Node.
    2. Go to Platform configuration > Conferencing Nodes.
    3. Select Add Conferencing Node.
    4. For deployment type, choose Generic (configuration-only) and select Next.
    5. Enter the details of the new Conferencing Node, including:

      IPv4 address

      Enter the Private IP address that you assigned to the VM instance (the ipAddress ARM template parameter).

      Network mask

      Ensure that the mask matches the one defined for the subnet selected for the instance (the networkSubnetName ARM template parameter). For example a subnet with a /20 prefix size has a network mask of 255.255.240.0.

      Gateway IP address

      The gateway address is the first usable address in the subnet selected for the instance (e.g. 172.31.0.1 for a 172.31.0.0/20 subnet).

      IPv4 static NAT address

      Configure the Conferencing Node's static NAT address, if you have a assigned a public/external IP address to the instance.

      Enter the public address dynamically allocated by Azure.

      You must also specify other fields such as the Name, Role, Hostname, Domain, System location and assign a TLS certificate. These fields are listed below.

    6. Select Finish.
    7. Select Download Conferencing Node Configuration and save the XML configuration file.

      A zip file with the name pexip-<hostname>.<domain>.xml will be downloaded.

  3. You must now upload the XML configuration file to the new Conferencing Node:

    1. Browse to https://<conferencing-node-ip-address>:8443/ and use the form provided to upload the XML configuration file to the Conferencing Node VM.

      If you cannot access the Conferencing Node, check that you have allowed the appropriate source addresses in your security group inbound rules for management traffic. In public deployments and where there is no virtual private network, you need to use the public address of the node.

      1. Select Choose File and select the XML configuration file.
      2. Select Upload.
    2. The Conferencing Node will apply the configuration and then reboot. When it has rebooted, it will connect to the Management Node.

      You can close the browser window used to upload the file.

After deploying a new Conferencing Node, it takes approximately 5 minutes before the node is available for conference hosting and for its status to be updated on the Management Node. Until it is available, the Management Node will report the status of the Conferencing Node as having a last contacted and last updated date of "Never". "Connectivity lost between nodes" alarms relating to that node may appear temporarily.