Deploying a Conferencing Node in Google Cloud Platform
After deploying the Management Node and completing the initial platform configuration you can deploy one or more Conferencing Nodes in GCP to provide conferencing capacity.
To deploy a Conferencing Node on a Google Compute Engine VM:
- If you have not already done so, prepare a Conferencing Node disk image. For more information on this, see Obtaining and preparing disk images for GCE Virtual Machines.
- From the GCP project console, go to .
- Select .
Complete the following fields (leave all other settings as default):
Name Enter a unique name for the instance, for example "pexipnode-europe-1". Zone Select an appropriate Zone. Typically you should choose a zone that is geographically close to the location from where users will connect to it. Machine type
Select 8 vCPUs (n1-highcpu-8).
We recommend selecting a minimum CPU platform. Select Intel Broadwell or later.and then select the most modern platform available that does not incur a surcharge, typically
For more information see Recommended instance types and call capacity guidelines.
Select the Conferencing Node custom disk image:
- Select .
- Select .
- Select the Conferencing Node custom disk image, e.g. "pexip-node-v24-1".
- Select .
Westrongly recommend SSDs for Conferencing Nodes. General VM processes (such as snapshots and backups) and platform upgrades will be faster with SSDs.
Expand the Management, disk, networking, SSH keys section and select the tab.
Assign Network tags to the instance, for example "pexip-provisioning pexip-conferencing".
These are the tags that should be applied to your Conferencing Node firewall rules (see Controlling access to Conferencing Nodes for installation/provisioning and Controlling access to Conferencing Nodes for conference participants).
You must decide whether or not to assign an external IP address to the instance.
You must assign a static public/external IP address to the Conferencing Node if you want that node to be able to host conferences that are accessible from devices in the public internet.
- Expand the Management, disk, networking, SSH keys section and select the tab.
- In the Network interfaces field, select the default interface to open the Network interface dialog.
- Select a Subnetwork if appropriate (e.g. if it is a private/hybrid deployment and you have created new subnets to avoid overlapping addresses in your corporate network).
Select an appropriate External IP:
- None: no external IP address will be assigned. Use this where the node does not need to have a publicly-accessible IP address.
- Create IP address: select this option to create a static external address. You can enter a Name for the address and GCP will allocate a static IP address.
- <external address>: you can select a specific static external address if you have already created one in advance.
Do not select Ephemeral — if you stop and restart the instance a new address will be assigned.
We recommend applying an SSH key to the Conferencing Node instance if you are not already using a project-wide key for all of the instances in your project.
The username element of the SSH key must be "admin" or "admin@<domain>". To apply an instance-level key:
- Select the tab and select .
- Select . This produces a text box. Copy the contents of your public SSH key file and paste them into the text box.
- Modify the username element to "admin" or "admin@<domain>" if necessary.
- Select .
See Security and SSH keys for more information.
- Select to create the instance.
- On the Internal IP" address, and the "External IP" address (if appropriate) that have been assigned to the new instance / Conferencing Node. page, make a note of the "
After the instance has booted, perform a configuration-only deployment on the Management Node to inform it of the new Conferencing Node:
- Log in to the Pexip Infinity Administrator interface on the Management Node.
- Go to .
- Select .
- For deployment type, choose Generic (configuration-only) and select .
Enter the details of the new Conferencing Node, including:
Enter the GCE Internal IP address of the new VM instance.
Gateway IP address
Enter the default gateway address for the region in which the node is deployed. See https://cloud.google.com/compute/docs/vpc/#subnet-ranges for a table of regions and default gateway addresses.
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 External IP address allocated by GCE for the VM instance.
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.Full list of configuration fields (click to expand/contract) Option Description Name Enter the name that will be used to refer to this Conferencing Node in the Pexip Infinity Administrator interface. Description An optional field where you can provide more information about the Conferencing Node. Role
This determines the Conferencing Node's role:
- Proxying Edge Node: a Proxying Edge Node handles all media and signaling connections with an endpoint or external device, but does not host any conferences — instead it forwards the media on to a Transcoding Conferencing Node for processing.
- Transcoding Conferencing Node: a Transcoding Conferencing Node handles all the media processing, protocol interworking, mixing and so on that is required in hosting Pexip Infinity calls and conferences. When combined with Proxying Edge Nodes, a transcoding node typically only processes the media forwarded on to it by those proxying nodes and has no direct connection with endpoints or external devices. However, a transcoding node can still receive and process the signaling and media directly from an endpoint or external device if required.
See Distributed Proxying Edge Nodes for more information. Hostname
Enter the hostname and domain to be assigned to this Conferencing Node. Each Conferencing Node and Management Node must have a unique hostname.
The Hostname and Domain together make up the Conferencing Node's DNS name or FQDN. We recommend that you assign valid DNS names to all your Conferencing Nodes. For more information, see Assigning hostnames and FQDNs.
IPv4 address Enter the IP address to be assigned to this Conferencing Node when it is created. Network mask Enter the IP network mask to be assigned to this Conferencing Node. Gateway IPv4 address Enter the IP address of the default gateway to be assigned to this Conferencing Node. Secondary interface IPv4 address The optional secondary interface IPv4 address for this Conferencing Node. If configured, this interface is used for signaling and media communications to clients, and the primary interface is used for communication with the Management Node and other Conferencing Nodes. For more information, see Conferencing Nodes with dual network interfaces (NICs). Secondary interface network mask The optional secondary interface network mask for this Conferencing Node. System location
Select the physical location of this Conferencing Node. A system location should not contain a mixture of proxying nodes and transcoding nodes.
If the system location does not already exist, you can create a new one here by clicking to the right of the field. This will open up a new window showing the For further information see About system locations.page.
SIP TLS FQDN A unique identity for this Conferencing Node, used in signaling SIP TLS Contact addresses. For more information, see SIP TLS FQDN. TLS certificate The TLS certificate to use on this node. This must be a certificate that contains the above SIP TLS FQDN. Each certificate is shown in the format <subject name> (<issuer>). IPv6 address The IPv6 address for this Conferencing Node. Each Conferencing Node must have a unique IPv6 address. Gateway IPv6 address
The IPv6 address of the default gateway.
If this is left blank, the Conferencing Node listens for IPv6 Router Advertisements to obtain a gateway address.
IPv4 static NAT address
The public IPv4 address used by this Conferencing Node when it is located behind a NAT device. Note that if you are using NAT, you must also configure your NAT device to route the Conferencing Node's IPv4 static NAT address to its IPv4 address.
For more information, see Configuring Pexip Infinity nodes to work behind a static NAT device.
Static routes From the list of Available Static routes, select the routes to assign to the node, and then use the right arrow to move the selected routes into the Chosen Static routes list. For more information, see Managing static routes. Enable distributed database
This should usually be enabled (checked) for all Conferencing Nodes that are expected to be "always on", and disabled (unchecked) for nodes that are expected to only be powered on some of the time (e.g. cloud bursting nodes that are likely to only be operational during peak times).
Determines whether this node can be accessed over SSH.
Use Global SSH setting: SSH access to this node is determined by the global Enable SSH setting ( ).
Off: this node cannot be accessed over SSH, regardless of the global Enable SSH setting.
On: this node can be accessed over SSH, regardless of the global Enable SSH setting.
Default: Use Global SSH setting.
Enter the password to be used when logging in to this Conferencing Node's Linux operating system over SSH. The username will always be admin.
Logging in to the operating system is required when changing passwords or for diagnostic purposes only, and should generally be done under the guidance of your Pexip authorized support representative. In particular, do not change any configuration using SSH — all changes should be made using the Pexip Infinity Administrator interface.
- Select .
Selectand save the XML configuration file.
A zip file with the name pexip-<hostname>.<domain>.xml will be downloaded.
You must now upload the XML configuration file to the new Conferencing Node:
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
ingress firewall rulesfor management traffic. In public deployments and where there is no virtual private network, you need to use the public address of the node.
- Select and select the XML configuration file.
- Select .
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.
When the node is up and running you can optionally remove the "pexip-provisioning" Network tag from the instance (or whichever tag you have associated with your provisioning firewall rule as described in Controlling access to Conferencing Nodes for installation/provisioning ) as it is no longer required. Note, do not delete the firewall rule or remove the "pexip-conferencing" tag.