About global settings

The length of time (in seconds) for which a conference will continue with only Guest participants, after all Host participants have left.

Default: 60 seconds

The length of time (in seconds) for which a conference will continue with only one participant remaining. The type of participant (Host, Guest, automatically dialed, streaming etc) is irrelevant.

The time can be configured to values between 60 seconds and 86400 (1 day), or to 0 (never eject).

Default: 0 (never eject)

The length of time (in seconds) for which a participant is allowed to remain at the PIN entry screen before being disconnected.

Default: 120 seconds

The length of time (in seconds) for which a Guest participant can remain at the waiting screen if a Host does not join, before being disconnected.

Default: 900 seconds

Controls the maximum call quality for participants connecting to Pexip Infinity services.

You can override this global setting for each individual service (VMR, Call Routing Rule etc). For example, you could use the default option of "HD" for most of your services by default, but enable Full HD on some specific services. The options are:

• SD: each participant is limited to SD quality.
• HD: each participant is limited to HD (720p) quality.
• Full HD (1080p): allows any endpoint capable of Full HD to send and receive its main video at 1080p.

Default: HD

See Setting and limiting call quality for more information.

When sending main video and presentation to a standards-based (SIP or H.323) endpoint, this defines the maximum percentage of the call bandwidth to allocate to the presentation content (with the remainder allocated to main video). It must be in the range 25% to 75%.

Default: 75%

Controls support for the SIP protocol over TCP and TLS across all Conferencing Nodes in your Pexip Infinity deployment.

Note that disabling SIP will disable support for Skype for Business / Lync (MS-SIP).

Default: enabled.

Allows or prevents incoming calls over SIP UDP.

Default: disabled.

Enable H.323 *If you change this setting, all existing calls will be disconnected and all Conferencing Nodes will be automatically restarted.

Enable WebRTC

Enable RTMP *If you change this setting, all existing calls will be disconnected and all Conferencing Nodes will be automatically restarted.

These boxes control support for the selected protocols across all Conferencing Nodes in your Pexip Infinity deployment.

Default: all of these settings are enabled by default.

Enables support for the Pexip Infinity client API. This is required for integration with the Infinity Connect browser-based, desktop and mobile clients, and any other third-party applications that use the client API, as well as for integration with Microsoft Teams.

This setting must be enabled if you want to Enable WebRTC or Enable RTMP.

Default: enabled.

Allows endpoints that support FECC to be controlled by a Host participant using an Infinity Connect client.

Default: enabled.

Control another participant's camera

Enables relay of chat messages between conference participants using Skype for Business / Lync and Infinity Connect clients.

You can override this setting on a per conference basis (for a Virtual Meeting Room or Virtual Auditorium).

Default: enabled.

Enables calls via the Pexip Distributed Gateway, and allows dial-out from Pexip Infinity conference (via the Infinity Connect clients and the Pexip Infinity Administrator interface).

Default: enabled.

About the Pexip Distributed Gateway service

Manually dialing out to a participant from a conference

When selected, Pexip Infinity does not default to the legacy version of the Infinity Connect web app. However, unsupported browsers will be redirected to the legacy web app.

Default: enabled.

The name of the SIP domain that is routed from Skype for Business / Lync to Pexip Infinity, either as a static route or via federation.

You can also configure the Pexip Infinity domain on a per-location basis, which would override this global setting for Conferencing Nodes in that location.

Microsoft Skype for Business / Lync with Pexip Infinity

When selected, this automatically escalates a Skype for Business / Lync audio call so that it receives video from a conference.

Default: disabled.

Controls support for Skype for Business Video-based Screen Sharing (VbSS).

Note that VbSS is always enabled for Microsoft Teams calls, regardless of this setting.

Default: disabled.

For information about enabling VbSS on your Skype for Business infrastructure see https://technet.microsoft.com/en-us/library/mt756736.aspx.

Allows an administrator to log in to the Management Node and all Conferencing Nodes over SSH.

This setting can be overridden on individual nodes.

Default: enabled.

When disabled, Infinity Connect clients display aliases from their own call history only.

When enabled, registered Infinity Connect clients additionally display the aliases of Virtual Meeting Rooms, Virtual Auditoriums, Virtual Receptions, and devices registered to the Pexip Infinity platform.

Default: enabled.

When enabled, if a location only contains Proxying Edge Nodes, then those nodes only require IPsec connectivity with other nodes in that location, the transcoding location, the primary and secondary overflow locations, and with the Management Node. When disabled a full connectivity mesh is required between all nodes in the deployment.

Default: enabled.

Controls the media encryption requirements for participants connecting to Pexip Infinity services.

You can override this global setting for each individual service (VMR, Call Routing Rule etc). For example, you could use the default option of "best effort" for most of your services, but enforce encryption on some specific services.

• Best effort: each participant will use media encryption if their device supports it, otherwise the connection will be unencrypted.
• Required: all participants (including RTMP participants) must use media encryption.
• No encryption: all H.323, SIP and MS-SIP participants must use unencrypted media. (RTMP participants will use encryption if their device supports it, otherwise the connection will be unencrypted.)

Default: Best effort

The start and end values for the range of ports (UDP and TCP) that all Conferencing Nodes use to send signaling (for H.323, H.245 and SIP).

Default: 33000–39999.

The start and end values for the range of ports (UDP and TCP) that all Conferencing Nodes use to send media for H.323, SIP, Skype for Business / Lync, WebRTC and RTMP (note that RTMP uses TCP only).

Default: 40000–49999.

Controls which codecs to offer in audio/video negotiation (SDPs).

Some third-party systems can experience issues if they are sent a large SDP from Pexip Infinity. You can reduce the size of the SDP by disabling specific, unwanted codecs.

Default: all codecs are selected except AAC-LD128, H.264 High (mode 0) and H.264 High (mode 1).

To enable the H.264 High Profile codec, move H.264 High (mode 1) into the list of Chosen Codecs. For optimal interoperability results, only enable H.264 High (mode 1) — leave H.264 High (mode 0) in the Available Codecs list.

Determines whether OCSP is used to check the status of TLS certificates.

Off: OCSP is not used.

On: OCSP is used, and the request is sent to the URL specified in the TLS certificate. If no URL is specified in the TLS certificate, the OCSP responder URL configured below is used.

Override: OCSP is used, and the request is sent to the OCSP responder URL specified in the OCSP responder URL field, regardless of any URL encoded in the TLS certificate.

Default: Off.

The URL to which OCSP requests are sent if either:

• the OCSP state is set to On but no URL is present in the TLS certificate, or
• the OCSP state is set to Override (in which case any URL present in the certificate is ignored).

Determines whether to verify the peer certificate for connections over SIP TLS.

Off: the peer certificate is not verified; all connections are allowed.

On: the peer certificate is verified, and the peer's remote identities (according to RFC5922) are compared against the Application Unique String (AUS) identified by Pexip Infinity — the SIP URI — before the connection is allowed.

Default: Off.

The maximum number of days of logs and call history to retain on Pexip nodes. On busy systems, logs may still be rotated before this time due to limited disk space.

Enter 0 to have no set limit.

Default: 0.

Select this option to instruct Pexip Infinity to temporarily block all access to a VMR that receives a significant number of incorrect PIN entry attempts

You can override this setting on a per location basis.

Default: enabled.

Select this option to instruct Pexip Infinity to temporarily block service access attempts from any source IP address that dials a significant number of incorrect aliases in a short period

You can override this setting on a per location basis.

Default: enabled.

Access for external systems is over HTTPS by default. If this box is selected, access over HTTP is also permitted.

Default: disabled.

Controls whether inactive users are automatically logged out of the Administrator interface after a period of time.

If enabled, users are logged out after a number of minutes of inactivity as specified in the Management web interface session timeout setting.

If disabled, users of the Administrator interface are never timed out. You may want to use this option if, for example, you have an administrator session that permanently monitors the system live view.

Default: enabled.

The number of minutes a browser session may remain idle before the user is logged out of the Management Node Administrator interface, if Enable management web interface session timeout is selected.

Default: 30 minutes.

Enable incident reporting

Incident reporting URL

If incident reporting is enabled, reports are sent to the specified URL.

This setting is configured during initial installation of the Management Node (when running the installation wizard).

Select this option to allow submission of deployment and usage statistics to Pexip. This will help us improve the product.

This setting is configured during initial installation of the Management Node (when running the installation wizard).

These options enable and configure the Pexip Infinity platform for dynamic cloud bursting to either Microsoft Azure, Amazon Web Services (AWS) or Google Cloud Platform (GCP).

The bursting threshold controls when your dynamic overflow nodes in your cloud service are automatically started up so that they can provide additional conferencing capacity. When the number of additional HD calls that can still be hosted in a location reaches or drops below the threshold, it triggers Pexip Infinity into starting up an overflow node in the overflow location.

An overflow cloud bursting node is automatically stopped when it becomes idle (no longer hosting any conferences). However, you can configure the Minimum lifetime for which the bursting node is kept powered on. By default this is set to 50 minutes, which means that a node is never stopped until it has been running for at least 50 minutes. If your service provider charges by the hour, it is more efficient to leave a node running for 50 minutes — even if it is never used — as that capacity can remain on immediate standby for no extra cost. If your service provider charges by the minute you may want to reduce the Minimum lifetime.

Choose which Cloud provider you want to host your bursting nodes and then complete the relevant additional fields that configure the access credentials to that service.

Configuring dynamic bursting to the AWS cloud

Configuring dynamic bursting to the Microsoft Azure cloud

Configuring dynamic bursting to the Google Cloud Platform (GCP)

This setting enables media relay on TCP port 443 on all Conferencing Nodes. This is intended as a fallback mechanism for use by WebRTC clients that are behind strict firewalls that block RTP media to Pexip's standard ports. This setting should only be enabled when it is impossible to amend the firewall's rules to allow UDP media, as sending media over TCP can result in increased latency and jitter.

Enabling this setting may cause disruption to ongoing WebRTC sessions.