Resource allocation examples

The examples below are designed to give you an idea of how the Hardware resource allocation rules apply as the capabilities of the Pexip Infinity platform are extended in the various scenarios:

In each of these cases, the hardware capacity requirements are described in terms of the HD resources required for a connection. A connection can be a call or presentation from an endpoint to a Virtual Meeting Room or Virtual Auditorium, a backplane between Transcoding Conferencing Nodes, or a call into or out of the Pexip Distributed Gateway. In this context, a connection is analogous to a port.

All of these examples are based around using the default Maximum call quality of HD. A Full HD connection would use twice the resource of a HD connection and a standard definition SD connection would use half the resource. WebRTC connections are assumed to be using the VP9 codec. VP9 calls consume around 1.5 times the resource for calls for main video (i.e. 1.5 HD resources for 720p, and 3 HD for 1080p).

All of the examples assume that the endpoints are connecting directly to Transcoding Conferencing Nodes. However, the Teams examples also show the effect of routing those calls via a Proxying Edge Node to the Teams Connector. (When a connection is proxied via a Proxying Edge Node, the proxying node also consumes connection resources in order to forward the media streams on to a Transcoding Conferencing Node. A transcoding node always consumes the same amount of connection resources regardless of whether it has a direct connection to an endpoint, or it is receiving the media streams via a proxying node.)

Virtual Meeting Rooms

Single non-distributed VMR

Pexip Infinity requires 4.5 HD resources. 3.5 HD resources are required by the endpoints (the two standards-based endpoints each use 1 HD resource and the WebRTC VP9 client uses 1.5 HD), and 1 HD resource is reserved by the backplane.

  • A presentation is then sent from a standards-based endpoint (see diagram).

Pexip Infinity requires no additional resources (assuming the WebRTC client has not elected to receive full motion presentation).

The conference uses 3 concurrent call licenses.

Single distributed VMR (standards-based, WebRTC and SfB/Lync endpoints)

Pexip Infinity requires 3.5 HD resources on Node 1 (2.5 for the connected participants, and 1 for the backplane), and 2 HD resources on Node 2, (1 for the connected participant, and 1 for the backplane).

  • A presentation is then sent from the standards-based endpoint (see diagram).

Pexip Infinity requires no additional resources on Node 1 (assuming the WebRTC client has not elected to receive full motion presentation). But it requires 1 additional HD resource on Node 2 for the SfB/Lync client to receive presentation, so the total resources used on Node 2 is now 3 HD. The same is true if the SfB/Lync client were to send presentation.

The conference uses 3 concurrent call licenses.

Single distributed VMR — 3 nodes

Pexip Infinity requires 2.5 HD resources on node 1 (1.5 for the WebRTC participant, and 1 for the backplane) and 2 HD resources on nodes 2 and 3 (1 for the connected participants, and 1 for the backplane).

  • The WebRTC participant then shares their screen (see diagram).

Pexip Infinity requires an additional 0.5 HD resources on Node 1 for the WebRTC endpoint to send presentation, and 1 additional HD resource on Node 2 for the Lync / Skype for Business client to receive presentation, so the total resources used on Node 1 is now 3 HD and Node 2 is also 3 HD.

The conference uses 3 concurrent call licenses.

Multiple distributed VMRs

Pexip Infinity requires 5.5 HD resources on node 1, 4 HD resources on node 2, and 3.5 HD resources on node 3.

  • The WebRTC participant in VMR 2 then shares their screen (see diagram).

Pexip Infinity requires an additional 0.5 HD resources on node 1 (for the WebRTC participant to send presentation) and 1 additional HD resource on node 2 (for the Lync / Skype for Business participant to receive presentation), so the total resources used on node 1 is now 6 HD and the total resources on node 2 is now 5 HD.

The conferences use 7 concurrent call licenses.

Gateway calls — all clients

Non-distributed gateway call (standards-based endpoint to SfB/Lync client)

  • There are multiple Conferencing Nodes in a single system location, but the gateway call is located on a single node.
  • There is one standards-based endpoint connecting via the node to a SfB/Lync client.
  • Each endpoint uses HD video and audio.

Pexip Infinity requires 2 HD resources: 1 for the inbound leg (endpoint to Pexip Infinity) and 1 for the outbound leg (Pexip Infinity to recipient). It also reserves 1 HD resource for a presentation backplane (in case either participant starts sending presentation and it is handled on a different node), so a total of 3 HD resources are used (see diagram).

  • If a presentation is sent from the standards-based endpoint, Pexip Infinity will use the 1 reserved HD resource for the SfB/Lync client to receive presentation.
  • If a presentation is sent from the SfB/Lync client, Pexip Infinity will use the 1 reserved HD resource for the SfB/Lync client to send presentation.

    However, if the RDP or VBSS presentation call from the SfB/Lync client lands on a different Conferencing Node to the video call, then the call will require an additional 2 HD resources (as a backplane is required in each direction between the node handling the video call and the node handling the presentation call, making 5 HD resources in total — 2 video + 2 backplane + 1 presentation).

The conference uses 2 concurrent call licenses in both cases.

Distributed gateway call (WebRTC to SfB/Lync client)

Pexip Infinity requires 4.5 HD resources: 2.5 HD on node 1 (1.5 for the connected participant and 1 for the backplane), and 2 HD on node 2 (1 for the connected participant and 1 for the backplane).

  • A presentation (screensharing) is then sent from the Infinity Connect desktop client to the SfB/Lync client.

Pexip Infinity requires 0.5 additional HD resources for node 1 for the Infinity Connect client to share its screen (a total of 3 HD resources on node 1). Likewise, 1 additional HD resource is used on node 2 for the SfB/Lync client to receive presentation (a total of 3 HD resources on node 2).

If the SfB/Lync client was to send presentation rather than receive, we would still require the same 3 HD resources on node 2, but as the Infinity Connect client does not consume a HD resource to receive content (as still images), we still only use 2.5 HD resources on node 1.

In both cases, the conference uses 2 concurrent call licenses.

Gateway calls to Skype for Business meetings

Single non-distributed gateway call to SfB/Lync meeting

  • There are multiple Conferencing Nodes in a single system location, but the gateway call is located on a single node.
  • We have one standards-based endpoint connecting to a SfB/Lync meeting via the node.
  • Two SfB clients are also connected directly to the SfB/Lync meeting.
  • Each endpoint uses HD video and audio.

Pexip Infinity requires 2 HD resources. The standards-based endpoint uses 1 HD resource, and the connection to the SfB/Lync meeting uses 1 HD resource.

  • A presentation is then sent from the standards-based endpoint (see diagram).

Pexip Infinity requires 1 additional HD resource for the SfB/Lync meeting to receive presentation, so a total of 3 HD resources are used. The same is true if a SfB/Lync user were to send a presentation within the SfB/Lync meeting.

The call uses 2 concurrent call licenses in both cases.

Gateway calls to Hangouts Meet

Single non-distributed gateway call (standards-based endpoint to Hangouts)

  • We have one standards-based endpoint connecting via a single node in a single location to a Google Hangouts Meet meeting.
  • Two Hangouts Meet clients are also connected to the meeting.
  • Each endpoint uses HD video and audio.

Pexip Infinity requires 2.2 HD resources. The standards-based endpoint uses 1 HD resource. The connection to Hangouts Meet uses 1.2 HD resources (it uses VP8).

  • A presentation is then sent from the standards-based endpoint (see diagram).

Pexip Infinity requires an additional 1.2 HD resources for Hangouts Meet to receive presentation. However, no additional resources are required if presentation content is sent from Hangouts Meet.

The call uses 2 concurrent call licenses in both cases.

Single distributed gateway call (standards-based endpoint to Hangouts)

  • There are two Conferencing Nodes in two different system locations.
  • A gateway call is placed from a standards-based endpoint connected via node 2 to a Google Hangouts Meet meeting connected via node 1.
  • Two Hangouts Meet clients are also connected to the meeting.
  • Each endpoint uses HD video and audio.

Pexip Infinity requires 2.2 HD resources on node 1 (1.2 for the connection to Hangouts Meet and 1 for the backplane), and 2 HD resources on node 2 (1 for the standards-based endpoint and 1 for the backplane), so 4.2 HD resources in total.

  • A presentation is then sent from the standards-based endpoint (see diagram).

Pexip Infinity requires an additional 1.2 HD resources for Hangouts Meet to receive presentation. However, no additional resources are required if presentation content is sent from Hangouts Meet.

The call uses 2 concurrent call licenses in both cases.

Multiple distributed gateway calls (mixed endpoints to Hangouts)

  • There are two Conferencing Nodes in two different system locations.
  • Two gateway calls are placed to the same Google Hangouts Meet meeting connected via node 1: one from a standards-based endpoint connected via node 2, and one from a Skype for Business client also connected via node 2.
  • Two Hangouts Meet clients are also connected to the meeting.
  • Each endpoint uses HD video and audio.

Pexip Infinity requires 4.4 HD resources on node 1 (each of the 2 gateway calls requires 1.2 for the connection to Hangouts Meet and 1 for the backplane). It also requires 4 HD resources on node 2 (the standards-based endpoint requires 1 for its connection to the gateway, and 1 for the gateway's backplane; the Skype for Business client requires 1 for its connection to the gateway, and 1 for the gateway's backplane), so 8.4 HD resources in total (see diagram above).

  • A presentation is then sent from the standards-based endpoint (see diagram below).

Pexip Infinity requires an additional 1.2 HD resources on node 1 to send the presentation to Hangouts Meet, but does not require additional resources on the other connection that is receiving the presentation from Hangouts Meet. The Skype for Business client requires 1 additional HD resource on node 2 to receive presentation, so 10.6 HD resources in total across the two nodes.

Gateway calls to Microsoft Teams

Single non-distributed gateway call (standards-based endpoint to Teams)

  • We have one standards-based endpoint connecting via a single transcoding node to a Microsoft Teams meeting via the Teams Connector.
  • Two Teams clients are also connected to the meeting.
  • Each endpoint uses HD video and audio.

Pexip Infinity requires 2.5 HD resources. The standards-based endpoint uses 1 HD resource, and the backplane connection to the Teams Connector uses 1.5 HD resources.

  • A presentation is then sent from the standards-based endpoint (see diagram).

Pexip Infinity requires no additional resources for the Microsoft Teams meeting to receive presentation. The same would be true if one of the Teams clients sent presentation content.

The call uses 2 concurrent call licenses in both cases.

Single gateway call via Proxying Edge Node (standards-based endpoint to Teams)

  • There is a proxying node in location A and a transcoding node in location B.
  • A gateway call is placed from a standards-based endpoint connected to the transcoding node to a Microsoft Teams meeting. The call is routed via the proxying node and the Teams Connector.
  • Two Teams clients are also connected to the meeting.
  • Each endpoint uses HD video and audio.

Pexip Infinity requires 0.2 HD resources on the proxying node, and 2.5 HD resources on the transcoding node (1 for the standards-based endpoint and 1.5 for the backplane connection).

  • A presentation is then sent from the standards-based endpoint (see diagram).

Pexip Infinity requires no additional resources for the Microsoft Teams meeting to receive presentation. The same would be true if one of the Teams clients sent presentation content.

The call uses 2 concurrent call licenses in both cases.

Multiple distributed gateway calls via Proxying Edge Node (mixed endpoints to same Teams meeting)

  • There is a proxying node in location A and a transcoding node in location B.
  • Two gateway calls are placed from endpoints connected to the transcoding node to a Microsoft Teams meeting. One endpoint is a standards-based endpoint and the other is a Skype for Business client. Both calls are routed via the proxying node and the Teams Connector.
  • Two Teams clients are also connected to the Microsoft Teams meeting.
  • Each endpoint uses HD video and audio.

Pexip Infinity requires 0.4 HD resources on the proxying node and 4 HD resources on the transcoding node (the standards-based endpoint requires 1 for its connection to the gateway, and 1 for the backplane; the Skype for Business client requires 1 for its connection to the gateway, and 1 for the backplane) (see diagram above).

  • A presentation is then sent from the standards-based endpoint (see diagram below).

Pexip Infinity requires no additional resources on the proxying node. The Skype for Business client requires 1 additional HD resource on the transcoding node to receive presentation.

* WebRTC connections are assumed to be using the VP9 codec. VP9 calls consume around 1.5 times the resource for calls for main video (i.e. 1.5 HD resources for 720p, and 3 HD for 1080p).