Viewing Conferencing Nodes

You can view details of all of your current Conferencing Nodes, including an interactive Conferencing Node status chart showing the load history for that node. You can also review a list of historic events (such as starting or stopping cloud bursting nodes) that have occurred on your Conferencing Nodes.

Viewing current Conferencing Nodes

To see a list of all Conferencing Nodes, go to Status > Conferencing Nodes.

Each Conferencing Node has the following information available:

Field Description
Name The name of the Conferencing Node. Click on the name to view detailed status information.
System location The physical location of the Conferencing Node.
Role Indicates the node's role — either a Transcoding Conferencing Node or a Proxying Edge Node.
IPv4 Address The primary IP address of the Conferencing Node.
Secondary address * The optional secondary interface IPv4 address of the Conferencing Node.
Static NAT address * The optional static NAT address of the Conferencing Node.
Version The version number of the Pexip Infinity software that is currently installed on this Conferencing Node.
Number of vCPUs The configured number of virtual CPUs.
System memory The amount of RAM configured on this Virtual Machine.
Maintenance mode Indicates whether the node is currently in maintenance mode.
Config sync status

The configuration synchronization status:

  • Synchronized: the node's configuration is synchronized (as at the Last updated date/time).
  • Suspended: synchronization is paused — this applies to nodes that are configured for dynamic bursting but are not currently active.
  • Not synchronized: the node can be reached and is responding, however it is not currently synchronized. If this situation persists (for more than an hour) then you should contact your Pexip authorized support representative. When the Management Node is restarted, it is expected that Conferencing Nodes will show as not synchronized for several minutes.
  • Unreachable: the node cannot be reached (does not respond) — this could be due to network issues or it may be powered off.

A "Configuration not synchronized" alarm is raised if the status is "Not synchronized" or "Unreachable".

Last contacted

The date and time that the Conferencing Node last responded to the Management Node. In typical deployments, configuration replication is performed approximately once per minute. However, in very large deployments (more than 60 Conferencing Nodes), configuration replication intervals are extended, and it may take longer for configuration changes to be applied to all Conferencing Nodes (the administrator log shows when each node has been updated).

  • Green text indicates that there are no issues.
  • Orange text indicates that no responses have been received within the last 2 expected replication intervals (typically within the last 3–5 minutes) and the node is not synchronized.
  • Red text indicates that no contact has been made for some time — typically none within the last 5 minutes, but note that this replication interval is extended in very large deployments.
  • Light gray text indicates that the node is suspended (a dynamic bursting node that is not currently active).
Last updated The last time that the Conferencing Node's configuration was successfully updated.

Maximum connections
Maximum direct media connections

Audio connections *
SD connections *
HD connections *
Full HD connections *

Proxy audio connections *
Proxy video connections *

For a Transcoding Conferencing Node, the initial table shows an estimate of the total number of simultaneous high-definition (HD) 720p video calls this node can handle.

After you have selected an individual transcoding node to view, you can also review the estimated SD, HD, Full HD and audio call capacity.

For a Proxying Edge Node, the initial table shows an estimate of the total number of proxied video calls this node can handle. After you have selected an individual proxying node to view, you can also review the estimated proxying capacity for audio calls.

Media load

An estimate of how much of its total capacity the Conferencing Node is currently using.

Note that when a Conferencing Node is in maintenance mode, it reports a media load of 100%. This is to indicate that there is no current capacity available.

Call count * The number of signaling connections that the node is currently handling.

CPU model *

CPU instruction set *

Hypervisor *

Extra information about the Virtual Machine hosting this Conferencing Node, including:

  • The underlying CPU model.
  • The highest CPU instruction set supported by this Virtual Machine.
  • The hypervisor on which this Virtual Machine is running.
Usage graph *

Shows media usage % statistics for this Conferencing Node for the last 4 weeks.

You can click on the graph and then scroll to zoom in and out, and you can drag the timebox to the left or right to move forwards or backwards in time.

* Only displayed when you have selected an individual Conferencing Node to view.

† Capacity estimates assume that only calls of that media type are being handled. For more information on server capacity, see Capacity planning.

Viewing historic Conferencing Node events

Go to History & logs > Conferencing Node History to see all of the events that have occurred on your Conferencing Nodes. These events include:

  • Adding or removing a node.
  • Placing a node into or out of maintenance mode.
  • Starting up or stopping a cloud bursting node.