About global settings

Global settings are system-wide configuration options that affect the entire Pexip Infinity platform. Some of the settings may be overridden at the location, Conferencing Node or VMR level — this is indicated in the table below where applicable.

To configure the global settings, go to Platform configuration > Global settings. The settings are grouped into categories:

Setting Description More information
Service configuration
Guests-only timeout

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

Using PINs to differentiate between Hosts and Guests
Last participant backstop timeout

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)

Automatically ending a conference
PIN entry timeout

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

Default: 120 seconds

Limiting the time a participant can spend at the PIN entry screen
Waiting for Host timeout

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

Default: 900 seconds

Limiting how long Guests can wait for a Host
Default theme The theme to use for services that have no specific theme selected. Customizing conference images and voice prompts using themes
Maximum inbound call bandwidth (kbps) Limits the bandwidth of media being received by Pexip Infinity from individual participants, for calls where bandwidth limits have not otherwise been specified. Restricting call bandwidth
Maximum outbound call bandwidth (kbps) Limits the bandwidth of media being sent by Pexip Infinity to individual participants, for calls where bandwidth limits have not otherwise been specified. Restricting call bandwidth
Connectivity
Enable SIP *

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.

Enabling and disabling SIP, H.323, WebRTC and RTMP
Enable SIP UDP *

Allows or prevents incoming calls over SIP UDP.

Default: disabled.

Enable H.323 *

Enable WebRTC *

Enable RTMP *

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.

Enable 1080p (Full HD)

Enables the use of 1080p (Full HD) for main video in calls.

Default: disabled.

Enabling Full HD (1080p) for main video in calls
Enable chat

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.

Enabling and disabling chat
Enable outbound calls

Enables calls via the Pexip Distributed Gateway, and allows dial-out from Pexip Infinity using Pexip Infinity Connect clients, the Infinity Connect mobile clients for iOS and Android, and the Pexip Infinity Administrator interface.

Default: enabled.

About the Pexip Distributed Gateway service

Manually dialing out to a participant from a conference

Enable support for Pexip Infinity Connect and Mobile App

Controls support for Pexip Infinity clients. These include the Infinity Connect web app, Infinity Connect desktop client, the Infinity Connect mobile client for iOS or Android, and any other third-party applications that use the client APIs.

Default: enabled.

Introduction to Infinity Connect
Default to next-generation Web App Default to the next-generation version of the Infinity Connect web app. Unsupported browsers will be redirected to the legacy web app. Enabling the next-generation Infinity Connect web app
Pexip Infinity domain (for Lync / Skype for Business integration)

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

Enable Skype for Business / Lync auto-escalation

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

Default: disabled.

Automatically escalating Skype for Business / Lync audio calls
Enable VbSS for Skype for Business

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.

DSCP value for management traffic The DSCP value for SSH, HTTPS and SNMP management traffic sent from the Management Node and from Conferencing Nodes. This is an optional Quality of Service (QoS) setting used to prioritize different types of traffic in large, complex networks. Also see Configuring system locations.  
Enable SSH

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

Note that this setting can be overridden on individual nodes.

Default: enabled.

 
Enable directory

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 deployment.

Default: enabled.

Directory (phone book) of devices and VMRs for registered Infinity Connect clients
Enable restricted routing for Proxying Edge Nodes

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.

Deployment guidelines for Proxying Edge Nodes
Port ranges
Signaling port range start and end *

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.

 
Media port range start and end *

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.

 
Codecs
Codecs

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.

 
Security
OCSP state

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.

Using OCSP to check the status of certificates
OCSP responder URL

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).
Using OCSP to check the status of certificates
SIP TLS certificate verification mode

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.

Verifying SIP TLS connections with peer systems
Maximum log age (days)

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.

 
Break-in resistance
Enable PIN brute force resistance

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.

Break-in resistance settings to mitigate rogue calls
Enable VOIP scanner resistance

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.

Break-in resistance settings to mitigate rogue calls
External system integration
Enable HTTP access for external systems

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

Default: disabled.

Integrating with external systems
External system username and password The username and password used by external systems (such as CUCM) when authenticating with Pexip Infinity. Integrating with external systems
Management web interface configuration
Login banner text Any text entered here is displayed in a message box on the login page. This field supports plain text only.  
Enable management web interface session timeout

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.

 
Management web interface session timeout

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.

 
Reporting

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).

Automatically reporting errors
Automatically send deployment and usage statistics to Pexip

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).

Automatically sending usage statistics
Cloud bursting
Enable bursting to the cloud

Bursting threshold

Tag name and value

Minimum lifetime

Cloud provider

These options enable and configure the Pexip Infinity platform for dynamic cloud bursting to either AWS or Microsoft Azure.

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

Tech preview features
Enable push notifications This setting will support future feature updates to Infinity Connect mobile clients. If enabled, push notifications are sent to the external policy server whenever a registered mobile client receives a call, needs to refresh its session token, or becomes unregistered.  
* If you change any of these values, each Conferencing Node must be rebooted before the changes will take effect.