Features added in previous versions

This section summarizes the features and enhancements that were added in previous releases of Pexip Infinity software.

Features added in version 20

Pexip Infinity version 20 added the following features and enhancements:

Feature Description More information
Video interoperability with Microsoft Teams

Pexip Infinity provides any-to-any video interoperability with Microsoft Teams.

It enables any video conferencing system to join Microsoft Teams meetings and allows authenticated systems to join as trusted participants without additional user interaction (i.e. lobby by-pass), including:

  • H.323 & SIP room-based videoconferencing systems, including Cisco, Polycom, LifeSize, and others
  • Browser-based video (WebRTC / RTMP)

Third-party systems can connect to Teams meetings via the Pexip Distributed Gateway either via a Virtual Reception (IVR) or by dialing the conference directly.

Integrating Microsoft Teams with Pexip Infinity

Conference participant avatars

Conference participants and directory contacts within Pexip Infinity can be represented by an avatar or image.

You can configure user records to represent those participants/contacts and associate each user with an avatar URL that points to an external service (such as Gravatar) which can be used to retrieve that user's avatar/image. Then, when that user is participating in a conference, their avatar can be shown to any of the other conference participants who are using an Infinity Connect client.

User records can be created manually (Users & Devices > Users), or they can generated from directory information contained in an AD/LDAP server via the existing VMR and device provisioning mechanism (Utilities > LDAP Sync Templates).

Users and participant avatars
Administrative improvements

This release contains the following administrative improvements:

  • New brandingURL Infinity Connect provisioning parameter that can be used to instruct the Infinity Connect client to use the same branding that has been uploaded to Pexip Infinity (and which is being used automatically by the web app).
  • You can specify the maximum number of days of logs and call history to retain on Pexip nodes (Platform > Global settings > Maximum log age).
  • Improved diagnostics, including the ability to create custom graphs, to make it easier to identify system dynamics such as call rate and participant creation times.
  • The Enable distributed database setting for a Conferencing Node can be modified via the Administrator interface after a node has been deployed.
  • New pex_md5 and pex_to_uuid filters that can be used in LDAP sync templates.
  • New conference participant status attributes that indicate if mute, disconnect and transfer actions are supported for that participant.

Registering and provisioning the Infinity Connect clients

Creating and viewing diagnostic graphs

 

 

Changes in functionality in version 20

Feature Description More information
Updated base theme

The base theme built into Pexip Infinity has been updated:

  • The background image is now a fjord (previously clouds).

  • The +n participant indicator overlay is now white on dark gray (previously orange on dark gray).
  • The default conference avatar, which is used in the contact list in Microsoft Skype for Business and Lync clients and in the legacy Infinity Connect clients, is now (previously an orange Pexip logo).

When customizing your own themes:

  • There are three new splash screens: no_main_video, no_incoming_video and no_presentation which are used when there is no video or presentation stream.
  • All of the in-conference indicators now use SVG files (previously PNG files).
  • There are new settings, audio files and indicators for Google Hangouts Meet interoperability as described below.
Base theme and other preconfigured themes
Updated themes and trusted device rules for Google Hangouts Meet integration

This contains important information for administrators who have configured Google Hangouts Meet interoperability in v19 and are upgrading v20.

Updated themes

There are new and updated theme settings, audio files and indicators that are used by default for callers who are gatewayed via Pexip Infinity into a Hangouts Meet conference:

  • New "conference recording stopped/started" audio files and new content for the existing "conference streaming stopped/started" audio files.
  • New icon_recording.svg visual indicator.
  • New recording_indicator_text setting in the themeconfig.json file, which is set to "Recording".

Previously in v19 we recommended that you use a customized theme (hangouts-theme.zip) supplied by Pexip for your Call Routing Rules used to route callers into Hangouts Meet conferences. In v20 the audio file and indicator customizations contained in that theme are now included by default in the base theme that is supplied automatically with Pexip Infinity. Therefore if you have used the Pexip-supplied hangouts-theme.zip in your deployment, to ensure that it does not conflict with the new base theme built into v20, we recommend that you delete that custom theme:

  1. In Pexip Infinity, go to Services > Themes.
  2. Select your existing "Hangouts theme" you created previously.
  3. Select Delete and confirm.

    Any services that were using that theme will now revert to using the default theme instead. If that theme was the default theme, then the default theme will revert to the base theme.

Note that if you had applied further personalized customizations to the "Hangouts theme", you should create and use a new theme that only contains those extra customizations.

Call Routing Rules into Hangouts Meet conferences

When integrating with Google Hangouts Meet you must explicitly set a new Treat as trusted flag on your Call Routing Rules if you want the devices routed via that rule to be trusted in Hangouts Meet.

Previously in v19 the devices were automatically treated as trusted from Pexip Infinity's perspective if they were registered to Pexip Infinity. You must still also associate the rule with a trusted access token.

On upgrade to version 20, any existing rules with a Call target of Google Hangouts Meet meeting will automatically have the new Treat as trusted flag enabled if that rule has Match incoming calls from registered devices only selected.

Configuring Pexip Infinity as a Google Hangouts Meet gateway

Base theme and other preconfigured themes

Administrative modifications

This release contains the following administrative modifications:

  • The Users top-level menu is now called Users & Devices. The Device aliases option has moved from Service Configuration to Users & Devices.
  • Policy profiles include a new Use local avatar configuration option.
  • "Connectivity lost between nodes" alarms are now only raised once per node which has been lost, and the alarm contains details of all of the other nodes that have reported it as lost.

 

Grayscale removed Video participants who are on hold, or who are experiencing connectivity issues, are still represented by a frozen image, but this is no longer converted to grayscale.  

Features added in version 19

Pexip Infinity version 19 added the following features and enhancements:

Feature Description More information
Video interoperability with Google Hangouts Meet

The Pexip Distributed Gateway provides any-to-any video interoperability with Google Hangouts Meet.

Third-party systems can connect to Hangouts Meet conferences via the Pexip Distributed Gateway either by dialing the conference directly or via a Virtual Reception (IVR).

Integrating Google Hangouts Meet with Pexip Infinity
Skype for Business Video-based Screen Sharing (VbSS)

Pexip Infinity supports sending and receiving content via VbSS to and from Skype for Business meetings, and to and from Skype for Business clients that are either calling another endpoint via the Pexip Distributed Gateway, or calling into a Virtual Meeting Room.

Note that VbSS is disabled by default on Pexip Infinity. It can be enabled via Platform > Global settings.

(VbSS was previously available as technology preview in earlier versions.)

Enable VbSS for Skype for Business
Improved video quality in low bandwidth scenarios

Participants now experience improved video quality in low bandwidth network scenarios, and when endpoints can only support low resolutions.

Pexip Infinity prioritizes image sharpness over high frame rates, and now sends video at lower frame rates if 30 fps is not achievable.

 
Enhancements to Live View

The Live View summary contains the following enhancements when showing active conferences:

  • Highlights any issues with backplane links between nodes when viewing a conference.
  • Displays links to an externally-hosted conference, such as a Microsoft Teams or Skype for Business meeting, or Google Hangouts Meet.
Viewing live and historical platform status

Changes in functionality in version 19

Feature Description More information
Consistent display of participant names in overlays The way in which participant names are shown as text overlays within a conference has been standardized. Any protocol or trailing IP address and port information is stripped from the displayed name/alias. For example, alice@example.com is now shown instead of sip:alice@example.com. Selecting the layout seen by participants
Administrative modifications

This release contains the following administrative modifications:

  • Two new audio files are included in the Base theme: conf-streaming_started_48kHz_mono.wav and conf-streaming_stopped_48kHz_mono.wav. These audio files are only played to callers who are gatewayed via Pexip Infinity into a Google Hangouts Meet conference.
  • The Administrator interface uses color coding when reporting media statistics, such as perceived call quality, packet loss and jitter. In general, statistics that are shown in green represent good quality, orange represents intermediate quality, and red is used for bad quality.

Base theme and other preconfigured themes

Reporting of media statistics and perceived call quality

Features added in version 18

Pexip Infinity version 18 added the following features and enhancements:

Feature Description More information
Simplified network routing requirements for Proxying Edge Nodes

As of version 18, Proxying Edge Nodes may no longer need full mesh connectivity to all other Conferencing Nodes.

If a location only contains Proxying Edge Nodes, then those proxying nodes in that location only require IPsec connectivity with:

  • any other proxying nodes in that location
  • all nodes in the transcoding location, and the primary and secondary overflow locations that are associated with that location
  • the Management Node.

This means that the proxying nodes in one location do not need to have a direct network connection to other proxying nodes in other locations.

Deployment guidelines for Proxying Edge Nodes

Network deployment options

New style themes with more flexible customization options

Version 18 of Pexip Infinity introduced a new way to specify the contents and layout of your own customized themes. The new style themes are more efficient than the previous style themes, and offer more flexibility when customizing them for your own requirements. Any previous legacy-style themes that you have customized in earlier versions of Pexip Infinity can still be used and changed, and continue to work exactly as before if you have set them as the default theme or applied them to specific services.

The new style base theme, which is used by default if you have not applied any customized themes to your services, behaves in exactly the same manner as the previous legacy-style base theme, and looks almost the same (some of the PIN-entry splash screen graphics used when joining a conference have been updated). The audio prompts are the same in new and legacy style themes.

Creating and applying themes to conferences
Microsoft Skype for Business and Lync integration improvements Pexip Infinity now supports send and receive video FEC (X-ULPFECUC) with Lync 2013 / Skype for Business clients and Skype for Business meetings. Pexip Infinity and Skype for Business / Lync integration features
Conference and participant status improvements

This release contains the following administrative improvements when viewing conference and participant status:

  • The participant status "perceived call quality" calculation now takes jitter into account for the time window being assessed.
  • Call protocol and, when applicable, the media proxying node and proxy location are displayed on the current and historic participant status summary pages.
  • The conference graph now displays current and total packet loss when viewing a backplane connection.
  • You can search by disconnect reason when viewing participant history.

Viewing current conference status

Viewing participant status

Administrative improvements

This release contains the following administrative improvements:

  • There is a new Log summary option that generates a condensed view of the messages in the support log, showing a summary of the call signaling for the current search/filtered log messages, such as a filter on a specific call ID.
  • You can upload the automatic daily backup file to an external FTP server.
  • A "Hardware IO (input/output) instability detected" alarm is raised if a high level of hard disk read/write latency is detected.
  • Ability to perform a packet capture to and from Conferencing Nodes in one or more locations, and the Management Node.
  • If you are using LDAP authentication, there are two new sets of permissions: "May create/delete packet capture" and "May download packet capture", and "May create/delete system backup" and "May download system backup" that must be assigned to the account role to enable the administrator to run and download a packet capture, and to perform backup and restore tasks respectively.

About the support log

Backing up and restoring configuration

Viewing alarms

Performing a network packet capture

Changes in functionality in version 18

Feature Description More information
Routing for calls from registered next-generation Infinity Connect desktop client Administrators can specify whether calls made from registered next-generation Infinity Connect desktop clients are placed via the registrar or via DNS. The default setting is to route via the registrar. Route calls via registrar
Administrative modifications

This release contains the following administrative modifications:

  • When configuring a Virtual Reception, you now explicitly specify the type of Virtual Reception: either Regular (the default) or Lync / Skype for Business (when using Pexip Infinity as a gateway into SfB/Lync meetings). This has also introduced a new two_stage_dial_type field to the set of Virtual Reception service type response fields when using external or local policy.
  • The "Call capacity limit reached" alarm now clears either when an existing call is disconnected or the next time a new call is successfully placed (previously it would only clear when a new call is successfully placed).
  • When viewing LDAP sync template results, more information is included in any "Last sync error" messages for conference or alias clashes, such as the names of the VMRs or aliases causing the clash.
  • When using jinja2 scripts, you can now use the new pex_now custom Pexip filter to obtain the current date and time, and the jinja2 range filter. There is also a new pex_url_encode filter that creates URL parameters that are safely URL-encoded.
  • Two new parameters/variables are available when using external or local policy to assign the media location: proxy_node_address and proxy_node_location.
  • "Participant has disconnected" messages in the administrator log now include a License-type parameter.
  • "Configuration changed" messages in the administrator log now include a Fields parameter which lists the fields that have been modified.
  • When using the management API you can filter on a participant ID when using the participant status and participant history resources.

Configuring Virtual Reception IVRs

Using patterns, variables and filters when provisioning VMRs, devices and users

Security improvements: only TLS1.2 is enabled by default for inbound HTTPS connections and ability to enable HTTP Content Security Policy on Conferencing Nodes

On upgrade to v18, the only version of TLS enabled by default for HTTPS inbound connections is TLS1.2.

This means that client API and management API users can no longer connect with TLS1.0 or TLS1.1; they must use a higher TLS protocol version. Support for old TLS versions may be re-enabled by running the security wizard and answering the TLS prompts appropriately.

Administrators also have the ability to enable HTTP Content Security Policy on Conferencing Nodes by running the security wizard.

The Management Node security wizard contains two new settings:

  • Permit TLS <1.2 for inbound HTTPS (default is No)
  • Enable HTTP Content-Security-Policy for Conferencing Nodes (default is No)

If you are using version 3 of the Pexip Reverse Proxy you will not be able to connect to Conferencing Nodes. You should either:

  • Upgrade to v5 of the Pexip Reverse Proxy, or
  • If continuing to use v3, connect over SSH to the reverse proxy and run the following command:

    sudo apt-get update && sudo apt-get -y dist-upgrade

In either case we recommend you first take a VM snapshot of the reverse proxy.

Deploying Pexip Infinity in a secure mode of operation

Features added in version 17

Pexip Infinity version 17 added the following features and enhancements:

Feature Description More information
Microsoft Skype for Business and Lync integration improvements

There are several interoperability improvements when integrating Pexip Infinity with Microsoft Skype for Business and Lync:

  • Improved recording indicator support: when a SfB/Lync client records a conference, an indicator is shown on the video conferencing systems, and if recording via Pexip Infinity, an indicator is shown to SfB/Lync clients.
  • Improved call quality in SfB/Lync meetings: SfB/Lync clients that are connected to a SfB/Lync meeting now receive smoother video streams from gatewayed VTC endpoints.
  • Improved audio and video FEC (Forward Error Correction): Pexip Infinity now supports audio FEC (RED) for audio content sent to and received from Skype for Business / Lync 2013 clients. Video FEC now supports Reed-Solomon encoding, which enables the recovery of lost video packets received by Pexip from Skype for Business / Lync 2013 clients.
Pexip Infinity and Skype for Business / Lync integration features
Improved platform status dashboard

The live view of the status of the Pexip Infinity platform has been substantially enhanced:

  • More participant and conference information: new charts and graphs showing participant information by location, protocol, license type and conference type.
  • Errors and warnings: any current errors or warnings are listed and the administrator can view further details about individual issues and view associated documentation for possible causes and suggested resolutions.
  • Call quality issues: identification of individual participants or conferences that are experiencing call quality issues.
  • Historic data for troubleshooting and platform analysis: when reviewing historic platform, conference and participant status information you now have access to historic call quality information and improved analysis tools and interactive charts where you can filter out or select specific elements such as participants using selected protocols or those accessing a conference from certain locations.

Note that some dashboard features (platform and issues summary statistics and the "Live" indicator) do not work in Internet Explorer browsers. We recommend using Chrome, Firefox or Edge browsers for the best experience.

Viewing live and historical platform status
Large-scale deployments improvements

Version 17 of Pexip Infinity includes several enhancements to support large-scale deployments:

  • Parallel upgrades of Conferencing Nodes: when upgrading to version 17 or later, the system will now upgrade up to 5 Conferencing Nodes simultaneously.
  • Reduced network traffic between nodes: optimized communication processes within the Pexip Infinity platform to decrease the amount of network traffic between Conferencing Nodes.
Upgrading the Pexip Infinity platform
Improved user experience in conferences
  • High-resolution content sharing: improved high-resolution content sharing at lower bandwidths (1080p low framerate):

    • 1080p is automatically used for sharing high-resolution content with HD-capable endpoints if there is sufficient available bandwidth.
    • When sending presentation content to a conference participant, the resolution and framerate that is used adapts dynamically to match the presented content.
  • Sharper text in participant names overlays: when the showing of participants' names is enabled on a VMR, the size of the text overlay varies automatically according to the type of layout and the resolution being received by the endpoint or SfB/Lync client. Participant names are also shown on the thumbnails (PiPs). In low resolutions the text overlays are not shown.
Selecting the layout seen by participants
Certificate management improvements

This release contains several improvements to the certificate management processes:

  • Modify CSR content when updating existing certificates: when generating a certificate signing request (CSR) for an existing certificate you can now change the certificate data to be included in the new request, such as adding extra subject alternative names (SANs) to those already present in the existing certificate.
  • Multiple certificates with the same subject name: you can now upload TLS certificates and trusted CA certificates with duplicate subject names. This provides increased flexibility when uploading and managing updates to existing certificates.

Managing TLS and trusted CA certificates

Certificate signing requests (CSRs)

Administrative improvements

This release contains the following administrative improvements:

  • Enable/disable chat per VMR: conference chat messages support can now be configured on a per VMR basis.
  • Enable/disable break-in resistance per location: PIN brute force resistance and VOIP scanner resistance can now be configured on a per location basis.
  • VMR provisioning enhancements: the LDAP sync templates that are used to provision Virtual Meeting Rooms now let you specify/override the Guests can present, enable chat, and conference capabilities settings for the VMR.
  • RTMP streaming support in Call Routing Rules: you can now specify RTMP (streaming) as the outgoing protocol to use in a Call Routing Rule.
  • Virtual Machine information: configuration information about the Virtual Machine hosting a Conferencing Node is reported via Status > Conferencing Nodes. This includes system memory, the number of vCPUs, CPU model, instruction set and hypervisor.
  • Change participant role via API: there is a new management API command of participant/role that can change the role of a conference participant.

Enabling and disabling chat

Break-in resistance settings to mitigate rogue calls

Provisioning VMRs, devices and users from Active Directory via LDAP

Configuring Call Routing Rules

Using the Pexip Infinity management API

Client authentication via AD FS and Google *Technology preview only

Support to allow client applications (such as the next-generation Infinity Connect clients) to authenticate against Microsoft Active Directory Federation Services (AD FS) and Google has been added to Pexip Infinity.

This will enable "single sign-on" capabilities for those clients, allowing users to register using their AD or Google credentials, and complements the existing Pexip Infinity capability to provision users from Active Directory.

This feature is "technology preview" until Infinity Connect clients that support this feature are released.

Using AD FS for client authentication

Using Google for client authentication

* Technology preview only

Changes in functionality in version 17

Feature Description More information
Administrative modifications

This release contains the following administrative modifications:

  • Replication of any configuration changes to Conferencing Nodes typically occurs after approximately one minute. Now, 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 (note that the administrator log shows when each node has been updated).
  • The History & Logs > Conferencing Node history page now shows when nodes were added or removed, and when a node was placed into or out of maintenance mode.
  • A new "CPU instruction set is deprecated" alarm is raised when a Conferencing Node restarts, if it is deployed on a server that is not using the AVX/AVX2 CPU instruction set (e.g. if it uses SSE4.2).
  • When using the management API, the bucketed_call_quality and historic_call_quality participant status fields are now a list of integers (previously a string). As of version 17.2 these fields are no longer reported in the response to management API requests for all participants for a conference instance (current and historic), but this data is reported when requesting a specific participant.
  • Conference status information reported via the management API includes an "is_started" field which indicates whether or not the conference has started due to a Host being present.
  • On the Administrator interface, Exchange Servers have been renamed Pexip Exchange Integrations.
  • On the Administrator interface, under the Users menu, User Authentication is now Administrator Authentication, Account Roles is now Administrator Roles, and LDAP Roles is now LDAP Role Mappings.
  • Participant call quality information is now shown on the current and historic participants summary page on the Administrator interface.
  • Registration alias requests sent to external policy now include the registration protocol.
  • System location information (Location="...") has been added to administrator log messages for "Participant attempting to join conference" and for "Registration added" / "Registration deleted" messages.
  • VMR and device sync administrator log messages are now logged to the administrator.ldap.sync module (previously administrator.vmrsync).
  • The Conference-ID is now included in administrator log messages for conference created/stopped and participant joined/disconnected events.

Using the Pexip Infinity management API

Viewing alarms

Features added in version 16

Pexip Infinity version 16 added the following features and enhancements:

Feature Description More information
Full support for Distributed Proxying Edge Nodes

You can deploy your Pexip Infinity system as either a mix of Proxying Edge Nodes and Transcoding Conferencing Nodes, or as a system that only contains Transcoding Conferencing Nodes.

A typical deployment scenario is to use Proxying Edge Nodes as a front for many privately-addressed Transcoding Conferencing Nodes. Those outward-facing proxying nodes would receive all the signaling and media from endpoints and other external systems, and then forward that media onto other internally-located transcoding nodes to perform the standard Pexip Infinity transcoding, gatewaying and conferencing hosting functions.

(Proxying Edge Nodes were previously available as technology preview in version 15.)

Distributed Proxying Edge Nodes
Google Cloud Platform support Pexip Infinity can now be deployed on the Google Cloud Platform. Using a cloud service provides scalable computing capacity and eliminates your need to invest in hardware up front, so you can deploy Pexip Infinity even faster. (Note that Pexip Infinity can also be deployed on Amazon Web Services and Microsoft Azure cloud platforms.)

Deploying Pexip Infinity on Google Cloud Platform (GCP)

Break-in resistance security protection

Two new security features provide resistance to malicious attempts to break in to your Pexip Infinity system:

  • PIN brute force resistance: this temporarily blocks all access to a VMR that receives a significant number of incorrect PIN entry attempts.
  • VOIP scanner resistance: this temporarily blocks service access attempts from any source IP address that dials a significant number of incorrect aliases in a short period.

These two options (Platform > Global settings) are enabled by default on upgrade to version 16.

Break-in resistance

Security best practices

Rewind and replay the status graph for live view and historic conferences

The interactive live view graph showing the status of the Pexip Infinity platform can be rewound and replayed to show historical status for the last 7 days.

Graphs for any current or historic conference can also be viewed and replayed. This allows you, for example, to see when participants and Conferencing Nodes joined or disconnected from the conference.

Rewinding and replaying status

Viewing current conference status

VMR Scheduling for Exchange maintenance and recovery The VMR Scheduling for Exchange feature now includes two scripts that can be run from the Management Node to allow you to restore meetings and delete old calendar and mail items from the room resource's mailbox. Maintenance and recovery procedures for VMR Scheduling for Exchange
Support for multiple Exchange servers

The VMR Scheduling for Exchange feature now supports environments with more than one Exchange server. To do this, a new Exchange domain configuration option has been added; one Exchange domain must be configured for each Exchange server in your deployment.

For customers upgrading to v16, the FQDN used in the EWS URL will automatically be added as the first Exchange domain.

Exchange domains
Ability to prevent Guest participants from presenting content An administrator can configure individual Virtual Meeting Rooms and Virtual Auditoriums so that Guest participants are not allowed to present into the conference (they can still receive presentation content from other Host participants). By default, Guests are allowed to present content.

About PINs, Hosts and Guests

Configuring Virtual Meeting Rooms (VMRs)

Configurable timeouts for participants

You can now configure the length of time that:

  • participants can remain at the PIN entry stage
  • Guest participants can remain in the waiting room.

Participants will be disconnected automatically after the configured time.

Limiting the time a participant can spend at the PIN entry screen

Limiting how long Guests can wait for a Host

VMR and device provisioning enhancements

The following improvements and modifications have been made to VMR and device provisioning:

  • When performing an LDAP sync of devices, you can now optionally sync any disabled AD items. This allows you to create device aliases for conference rooms/resources which typically have disabled AD accounts/mailboxes in Microsoft Exchange.
  • There is more flexible alias handling when provisioning VMRs via LDAP:
    • VMR aliases can now be tagged as overridable. This allows you to manually add further aliases to a provisioned VMR.
    • You can now provision up to 8 aliases per VMR (previously 4).
Provisioning VMRs, devices and users from Active Directory via LDAP
Enable maintenance mode simultaneously You can now simultaneously enable or disable maintenance mode for multiple Conferencing Nodes. Manually placing a Conferencing Node into maintenance mode
Enable and disable SSH on individual nodes You can now override the global SSH setting in order to enable or disable SSH access on the Management Node and individual Conferencing Nodes.  
Select which logs are sent to syslog

In previous versions, syslog servers received both support log and Linux audit log entries. In version 16, you can control which of the following logs are sent to a particular syslog server:

  • support log
  • audit log
  • web server log.
Using a syslog server
TLS certificate management enhancements

There are new TLS certificate management features:

  • Ability to download individual TLS certificates. Note that if you are using LDAP authentication, there is a new permission "May download TLS private key" that must be assigned to the account role to enable the administrator to download a certificate's private key.
  • You can create a certificate signing request (CSR) for existing installed certificates, for example if you need to replace a certificate that is due to expire.
Managing TLS and trusted CA certificates

Changes in functionality in version 16

Feature Description More information
Selecting a Conferencing Node's role (transcoding or proxying) When deploying a new Conferencing Node you must now assign it a Role of either Transcoding Conferencing Node or Proxying Edge Node. Previously an Enable transcoding checkbox was used to determine a node's role. Distributed Proxying Edge Nodes
Calls (signaling) received in one location can have their media transcoded by a Conferencing Node in a different location

When configuring a system location you can now specify a Transcoding location. This lets you define the system location to handle media transcoding for calls (signaling) received in, or sent from, that location.

On upgrade to version 16, the Transcoding location defaults to This location for any existing locations — this default means that transcoding is performed by a Transcoding Conferencing Node in the same location as where the call signaling is being handled, as per previous behavior. This new setting is intended for use in locations that contain Proxying Edge Nodes so that you can specify the location (and thus the Transcoding Conferencing Nodes) to where media will be proxied for transcoding purposes.

About system locations
New Scheduled Conferences page Scheduled conferences are now listed on a separate page, rather than on the Virtual Meeting Room page. Managing scheduled conferences
Additional customizations for VMR Scheduling for Exchange For meetings and VMRs created using the VMR Scheduling for Exchange feature, you can now use jinja2 templates to configure the Conference name, Conference description, and Conference subject. You can also customize the date-time format to be used. Configuring a Pexip Exchange Integration
Conference "comfort noise" Low-level, almost imperceptible background noise has been added to the audio mix in conferences. This creates a similar effect to an open mic and gives reassurance that the conference is alive, even if all participants are muted.  
Administrative improvements and modifications

This release contains the following administrative improvements and modifications:

  • The ability to mute all Guests in a VMR (via Status > Conferences).
  • New History & Logs > Alarm history page shows all historic alarms including the severity level, and the time the alarm was raised and lowered. This information is also available via the management history API.
  • New Status > Conferencing Node History page shows all events (stop, start or running) that have been applied to overflow Conferencing Nodes. This information is also available via the management history API.
  • The ability to disable the management web interface session timeout for inactive users (Platform > Global settings > Enable management web interface session timeout).
  • When configuring a Virtual Reception, the Skype for Business / Lync fields used for configuring IVR gateway routing to SfB/Lync meetings are now in the main settings (previously they were in the Advanced options).
  • When configuring a Call Routing Rule's Call target, the Skype for Business / Lync meeting direct (not via Virtual Reception) option is now called Skype for Business / Lync meeting direct (Conference ID in dialed alias).
  • Searching / filtering is now supported on the Conferencing Node status and Conferencing Node configuration pages.
  • The service count on the Themes page now includes any Call Routing Rules that use that theme (in addition to VMRs).
  • When using the management API, configured services and Call Routing Rules can be filtered by theme (using a filter criteria of ivr_theme).
 
External and local policy improvements and modifications

The following improvements and modifications have been made to external and local policy:

  • The response for service configuration policy for Virtual Meeting Rooms and Virtual Auditoriums supports new guests_can_present and primary_owner_email_address elements.
  • There is a new request parameter / call_info variable of trigger which indicates the trigger for the policy request, for example "invite", "options" and so on.
  • Local policy scripts can use a new pex_in_subnet filter to test whether a participant's address is within one or more subnets.
  • The call_direction request parameter / call_info variable now reports a value of "non_dial" instead of "None" (when policy is triggered by requests that are not related to incoming or outgoing call setup).
  • External policy requests now support Basic Authentication and basic ASCII-encoded username and password credentials. Previously Pexip Infinity encoded the credentials to UTF-8. There should be no impact on any existing policy server configuration after upgrading to version 16 providing basic ASCII characters were used for the credentials.
Using external and local policy to control Pexip Infinity behavior

Features added in version 15

Pexip Infinity version 15 added the following features and enhancements:

Feature Description More information
VMR Scheduling for Exchange

The VMR Scheduling for Exchange feature allows you to create an add-in that enables Microsoft Outlook desktop and Web App users in Office 365 or Exchange environments to schedule meetings using Pexip VMRs as a meeting resource.

This feature is available as a separately licensed feature within the Pexip Infinity platform.

Integrating with Microsoft Exchange
VMR licenses

A new licensing model has been introduced that requires a VMR license for each Virtual Meeting Room and Virtual Auditorium configured on the platform.

This change does not affect customers on existing licenses who are upgrading to v15 or later — additional licenses are not required for these customers. If you have any further questions, please contact your Pexip authorized representative.

Pexip Infinity license installation and usage
Proxying Edge Nodes *Technology preview only

You can deploy your Pexip Infinity system as either a mix of Proxying Edge Nodes and Transcoding Conferencing Nodes, or as a system that only contains Transcoding Conferencing Nodes. Prior to version 15 of Pexip Infinity, all Conferencing Nodes were, in effect, Transcoding Conferencing Nodes.

A typical deployment scenario is to use Proxying Edge Nodes as a front for many privately-addressed Transcoding Conferencing Nodes. Those outward-facing proxying nodes would receive all the signaling and media from endpoints and other external systems, and then forward that media onto other internally-located transcoding nodes to perform the standard Pexip Infinity transcoding, gatewaying and conferencing hosting functions.

Distributed Proxying Edge Nodes
Dynamic bursting to Microsoft Azure You can now utilize dynamic bursting to Conferencing Nodes hosted in a Microsoft Azure cloud service. (Pexip Infinity already previously supported dynamic bursting to Amazon Web Services.) Dynamic bursting to a cloud service
Improved resilience in Fusion links to Microsoft Skype for Business and Lync

Pexip Infinity now supports XOR-based Forward Error Correction (FEC) resulting in improved packet loss resilience in gateway calls from Pexip Infinity to Skype for Business / Lync meetings.

There is better resilience when Pexip Infinity is acting as a gateway between Skype for Business / Lync and standards-based endpoints. If the connection to the Skype for Business / Lync meeting is lost, Pexip Infinity now attempts to re-establish the connection. Note that this does not apply to Pexip-hosted VMRs that have been merged into a SfB/Lync meeting.

 
Regex testing tool The Pexip Infinity Administrator interface contains an inbuilt regex testing tool (Utilities > Regular Expression Tester). Regular expression (regex) reference
New visual indicators for a locked conference

All Host participants on all endpoints now see visual indicators when a conference is locked or unlocked, and when other Guest participants are waiting to join a locked conference.

The style and use of the indicators can be fully customized via themes.

Locking a conference and allowing participants to join a locked conference

Base theme and other preconfigured themes

* Technology preview only

Changes in functionality in version 15

Feature Description More information
Multiple changes to the base Pexip theme

The following changes have been made to the base Pexip theme:

  • The base Pexip theme contains a new connecting.jpg file. This new "Connecting call" image is shown (instead of the "Welcome" image) when placing a person-to-person call via the Pexip Distributed Gateway, and when gatewaying individual participants into a Skype for Business / Lync meeting.
  • Themes no longer use a JPEG image file to specify the background color of the thumbnail that shows how many additional participants are in the conference. The plus_n_indicator.jpg file has been removed from the set of image files used in themes. Now, the background color of the thumbnail that shows how many additional participants are in the conference is controlled by a new plus_n_indicator_bg_color setting in the themeconfig.json file. The default thumbnail background color itself has not changed.

    If you have customized your own themes and have used a custom plus_n_indicator.jpg file, you must update those themes to specify your required background color. You do this by adding the new plus_n_indicator_bg_color setting to your custom themeconfig.json file. You should also remove your custom plus_n_indicator.jpg file as this file is now ignored. If you do not update your themes, the default background color (dark gray) will be used instead.
    If you have customized your own themes but have not used a custom plus_n_indicator.jpg file, but the default plus_n_indicator.jpg file exists in your custom theme, then we recommend that you delete it to maintain consistency with the base theme.

  • New conference_locked_indicator.png and conference_unlocked_indicator.png files have been added; the default for both are solid white images against a fully transparent background. Accompanying text, and the ability to enable and disable the indicator, is configurable via the themeconfig.json file.

  • The default audio_indicator.png and streaming_indicator.png files have been changed and are now solid white images against a fully transparent background.
  • Previously, for indicators showing the number of additional audio participants, customers could specify both the color of the text and the color of the background against which the text and icons would appear. Now, the color of the background against which the text and icons appear is fixed to be semi-transparent (0x7f323232), and the text is fixed to be solid white. For this reason, indicator_num_color and indicator_num_bg_color are no longer used and have been removed from the themeconfig.json file.
  • no_presentation_video_bg has been removed from the themeconfig.json file.
Rules and requirements for customized themes
Change in behavior of audio-only indicators

When there are five or more audio-only participants, a single indicator will be present on the left-hand side of the video window that will display:

  • (when minimized) the audio-only icon followed by the total number of audio-only participants , or
  • (when expanded) the name of the current speaker, followed by the audio-only icon and the number of other audio-only participants.
Features common to all layouts
Increased repeat interval for the "Waiting for the conference host to join" message The repeat interval for the "Waiting for the conference host to join" message has been increased. It is now repeated every 30 seconds for video participants, and every 15 seconds for audio-only participants. Previously it was repeated every 10 seconds for all participant types.  
Clashes detected during an LDAP synchronization process no longer override existing settings Prior to version 15, any clashes that occurred when provisioning VMRs and devices from Active Directory via LDAP would result in the existing VMR or device alias properties being overwritten with the data generated from the template synchronization currently in progress. Now, any existing VMR properties, VMR-to-alias assignments, and device aliases are not overwritten. Viewing LDAP sync template results
Control-only Infinity Connect participants never consume a license Prior to version 15, Infinity Connect presentation and control-only participants consumed a port license when sharing their screen, or sending or receiving full-motion HD presentations. From version 15, presentation and control-only participants will never consume a license. Pexip Infinity license installation and usage
Administrative improvements and modifications

This release contains the following administrative improvements and modifications:

  • New call quality analysis to assist administrative troubleshooting: the system now analyzes packet loss statistics so that when viewing the status of call participants you can see the current call quality and a graph showing the fluctuations in quality over the duration of the call. The call quality graph is also available when looking at historic call participant information.
  • Ability to specify the minimum time for which a dynamic bursting Conferencing Node is kept powered on.
  • TURN server addresses can be specified as an FQDN and can also be resolved through an SRV lookup.
  • Improved robustness during the upgrade process. For example, if an individual Conferencing Node does not restart successfully after upgrading, the upgrade process will continue with upgrading any remaining nodes.
  • Snapshots can be taken via the management API.
  • In the support log, support.sip log messages for UPDATE requests now generate verbose output (rather than summary output).
 
Stricter syntactic validation of HTTP requests The HTTP server performs strict validation of HTTP requests. Correctly written clients (such as web browsers and the Infinity Connect desktop client) are unaffected by this change. Some reverse proxy configurations and badly-implemented clients may receive 400 Bad Request responses when accessing the Pexip Infinity APIs and web interface.

Apache HTTP Protocol Options Directive

Apache HTTP Request Parsing Whitespace Defects

Support for VMware ESXi 6.5 Pexip Infinity now supports VMware ESXi 6.5. Supported ESXi versions

Planned changes in future releases

Feature Description More information
Make Automatic routing the default option within Infinity Connect when dialing out from a conference

Currently when dialing out from a conference via Infinity Connect, the default routing is Manual, which means that the caller has to select the protocol to use to reach the callee. Most typical participants are not familiar with call protocols and may only know the alias of the person they want to invite into the conference and do not know the type of device or system that person is using.

In future releases of Pexip Infinity, we intend to make Automatic routing the default option within Infinity Connect, with a longer-term goal of removing the automatic / protocol selection option altogether so that automatic routing is always used. With this in mind, we recommend that you start considering how you want outbound calls to be handled and plan your Call Routing Rules accordingly.

Recommendations for handling outgoing calls from a conference

Features added in version 14

Pexip Infinity version 14 added the following features and enhancements:

Feature Description More information
Layout improvements
  • We have increased the relative size of video images and reduced the amount of black space.
  • Thumbnails of participants entering the stage will now fade into place (previously they slid in from the side).
Selecting the layout seen by participants
Show main speakers' names

You can now configure Virtual Meeting Rooms and Virtual Auditoriums to show the name(s) of the participant(s) who are being shown in the main video. Names will be displayed at the bottom of the participant's video.

Showing the names of participants as a text overlay

Live platform status overview

Pexip Live View (Status > Live View) is a new interactive graphical report that shows the current status of your deployment, including load on Conferencing Nodes and conferences taking place.

Minor changes have been made to the conference graph to align it with the new Live View.

Viewing live and historical platform status

Viewing current conference status

Test call service

Pexip Infinity now includes a new Test Call Service. This provides a test loop that allows users to check the quality of their video and audio, and verifies that they can connect to the Conferencing Node.

On upgrade to version 14, a single default test service with the name "Test Call Service" and the alias "test_call" is automatically added to your system configuration. (If an existing conference or alias exists with those names, they will not be reassigned to the new service.) You can add further test services and aliases as necessary, and configure them via themes if required.

Configuring the Test Call Service
Certificate Signing Requests (CSRs) You can generate a Certificate Signing Request (CSR) from within Pexip Infinity, and then upload the returned certificate associated with that request. Certificate signing requests (CSRs)
Allow only registered devices to make Pexip Distributed Gateway calls

You can configure Call Routing Rules to only allow devices that are registered to Pexip Infinity to be able to make calls via the Pexip Distributed Gateway. This provides greater security and control over the devices that can use gateway resources.

Configuring Call Routing Rules
Local policy scripts

Local policy allows you to manipulate service configuration and media location data (that has been provided either via the external policy API, or has been retrieved from Pexip Infinity's own database) by running a jinja2 script against that data.

Local policy and external policy are configured via policy profiles (Call control > Policy profiles) and a policy profile is than assigned to a system location.

On upgrade to version 14, any existing external policy servers are converted into policy profiles.

Using external and local policy to control Pexip Infinity behavior
Dual network interfaces (NICs) for Conferencing Nodes You can configure a secondary network address on a Conferencing Node. If configured, this secondary address is used for signaling and media, and the primary address is used for inter-node communication. Conferencing Nodes with dual network interfaces (NICs)
Improved CSV import/export The existing CSV import/export utility for Virtual Meeting Rooms has been expanded to include all configuration options. Additional CSV import/export is now available for Virtual Auditoriums, Virtual Receptions, Automatically Dialed Participants, and device aliases. Bulk import/export of service configuration data
H.264 High Profile codec support

Pexip Infinity now supports the H.264 High Profile codec. The H.264 High Profile codec can provide HD video quality with reduced bandwidth requirements on H.264 connections.

This codec is disabled by default. To enable the codec, go to Platform > Global settings and, in the Codecs section, 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.

About global settings
RTMP dual stream support for Automatically Dialed Participants (ADPs) Automatically Dialed Participants (ADPs) can be configured with RTMP dual streams. Automatically dialing out to a participant from a conference
Skype for Business Video-based Screen Sharing (VbSS) *Technology preview only Pexip Infinity now supports sending and receiving content to and from Skype for Business clients using VbSS.  
New alarm Pexip Infinity will raise an alarm if it detects that the underlying hardware appears to be over-committed. Viewing alarms

* Technology preview only

Changes in functionality in version 14

Feature Description More information
Less verbose support.sip messages in the support log Some support.sip messages in the support log are less verbose than previously. Log messages for SUBSCRIBE, NOTIFY, OPTIONS and INFO requests now generate summary output.  
Keep alive pings from SIP proxies no longer trigger external policy requests Pexip Infinity now immediately responds with 200 OK to OPTIONS keep alive pings from remote SIP proxies, and does not perform any additional processing — such as sending outbound external policy requests — on receipt of such messages.  
Lync and Skype for Business terminology updates

References to "Lync" on the Pexip Infinity Administrator interface have been updated to also refer to "Skype for Business", specifically:

  • "Lync servers" are now called "Lync / Skype for Business servers".
  • The "Lync (MS-SIP)" protocol (used in Call Routing Rules and when dialing out) is now called "Lync / Skype for Business (MS-SIP)".
  • In Call Routing Rules the "Lync AVMCU conference direct (not via Virtual Reception)" call target is now called "Lync / Skype for Business meeting direct (not via Virtual Reception)", and the "Lync clients or Lync AVMCU conferences via a Virtual Reception" call target is now called "Lync / Skype for Business clients, or meetings via a Virtual Reception".
  • The "Lync MSSIP domain" (used in global settings and system location configuration) is now called "Pexip Infinity domain (for Lync / Skype for Business integration)".
  • Global setting "Enable Lync auto-escalation" is now called "Enable Lync / Skype for Business auto-escalation".
  • "Lync conference lookup location" on a Virtual Reception is now called "Lync / Skype for Business meeting lookup location".

(Note that all API parameter/field names are unchanged.)

 
Management API improvements

There have been minor updates to the management API:

  • It now allows filtering of devices ('device' resource) by the owner email address ('primary_owner_email_address' field).
Retrieving, paginating, filtering and ordering resource details
Improvements to the conference status graph There have been minor updates to the conference status graph, including changes to the icons representing Conferencing Nodes, and the inclusion of presentation and control-only participants in the graph. Viewing current conference status
More historical media load data The Conferencing Node media load graph now shows 4 weeks of history (rather than one week as previously). Viewing Conferencing Nodes
Relationship between services and themes

You can now:

  • from each of the Services pages, view which themes are associated with the services, and sort the list by theme
  • view the number of services to which a particular theme has been applied.
Viewing the themes currently in use
Service creation time

You can now view the time at which a particular service was created. This information is shown via the Administrator interface on the edit page for each service. This applies to:

  • Virtual Meeting Rooms
  • Virtual Auditoriums
  • Virtual Reception
  • Automatically Dialed Participants
  • Device aliases
 
Maintenance mode status The Conferencing Node status page now includes a sortable column regarding whether each node is in maintenance mode.  
Conference history The maximum number of conferences show in the Conference History page has increased from 5,000 to 10,000. Viewing historical information about conferences
Security-related updates

This release includes several security-related modifications:

  • TLS connections no longer use Triple DES or MD5.
  • The security wizard (used when deploying Pexip Infinity in secure mode):
    • allows you to disable TLS 1.0
    • allows you to disable Anonymous Diffie Hellmann key exchange for outbound SIP/TLS
    • no longer allows you to enable SSL 3.0.

Deploying Pexip Infinity in a secure mode of operation

Infinity Connect web app support for Microsoft Internet Explorer on Windows 10 has been deprecated. Support for the Infinity Connect web app via Microsoft Internet Explorer on Windows 10 systems has been deprecated. Windows 10 users should use Microsoft Edge (or another browser such as Chrome, Firefox or Opera) instead.  
API participants and backplane reservation If an API participant is the first participant to join a conference, it will now reserve a backplane for the conference. Previously an API participant would not have reserved a backplane. Hardware resource allocation rules

Features added in version 13

Pexip Infinity version 13 added the following features and enhancements:

Feature Description More information
Dynamic bursting to the AWS cloud

Pexip Infinity deployments have the ability to burst into the Amazon Web Services (AWS) cloud when primary conferencing capabilities are reaching their capacity limits, thus providing additional temporary Conferencing Node resources.

This provides the ability to dynamically expand conferencing capacity whenever scheduled or unplanned usage requires it. The AWS cloud Conferencing Nodes instances are only started up when required and are automatically stopped again when capacity demand normalizes, ensuring that AWS costs are minimized.

Configuring dynamic bursting to the AWS cloud

Video watermarking via themes

Video watermarking overlays a small transparent image onto the main speaker video during a conference. This enables you to add your own imagery, logos or information to the video stream.

Video watermarking is enabled by default, and applies a Pexip logo to all conferences (VMRs and Virtual Auditoriums) running on new installations and on upgrades of existing installations. Watermarks are not added to calls placed via the Pexip Distributed Gateway.

The watermark image can be disabled or customized via the theme applied to the conference, allowing you to have a different watermark per VMR, if required.

Rules and requirements for customized themes
Device provisioning via LDAP Pexip Infinity can bulk provision devices from directory information contained in an AD/LDAP server. This complements existing functionality to provision VMRs via LDAP. As a consequence, "VMR sync templates" are now referred to more generically as "LDAP sync templates". Provisioning VMRs, devices and users from Active Directory via LDAP
Ability to send a provisioning email to a VMR or device owner When bulk-provisioning VMRs or device aliases from Active Directory via LDAP, an email can be sent out to the VMR owner telling them the properties of their VMR, such as its aliases and security PINs, or to the device owner telling them the device alias properties, such as its associated username and password for registration purposes. Sending provisioning emails to VMR and device owners
Directory (phone book) of devices and VMRs for registered Infinity Connect clients Pexip Infinity now provides a search facility to its registered Infinity Connect clients that enables them to look up the contact details of other devices and VMRs, making it easier for the Infinity Connect client to call those devices or VMRs. Directory (phone book) of devices and VMRs for registered Infinity Connect clients
External policy API enhancements including directory and registration requests

The external policy API has been enhanced to include:

  • New directory information request to obtain a list of phonebook aliases. The directory information can be used by Infinity Connect desktop clients and Infinity Connect mobile clients that are registered to a Pexip Infinity Conferencing Node.
  • New registration alias request to enquire if an alias is allowed to register to a Pexip Infinity Conferencing Node.
  • Ability to administratively enable or disable support for individual API request types.
Using external and local policy to control Pexip Infinity behavior
Audio-only call licenses

Pexip Infinity's call licensing model can support audio-only call licenses, port (video call) licenses, or a combination of the two.

On upgrade to version 13, all existing call licenses are treated as port (video call) licenses.

Pexip Infinity license installation and usage
Ability to disable individual codecs You can choose, on a global basis, which codecs to offer in audio/video negotiation. About global settings
Support for presenting PowerPoint files from Skype for Business / Lync clients Participants connected to the Pexip VMR in a Skype for Business / Lync Fusion or gateway call can now see shared content if a Skype for Business / Lync user presents PowerPoint files. Supported codecs, protocols and resilience
New alarms

New alarms have been added on the Management Node for when nodes are not correctly synchronized for NTP, and when there are connectivity or configuration synchronization issues between nodes.

The alarm icon displayed on the Pexip Infinity Administrator interface is now a red triangle.

Viewing alarms
Historical backplane statistics Historical conference backplane data, including media streams, is available via the Pexip Infinity Administrator interface and the management API. Viewing historical information about conferences
Improved resilience and retransmission for Chrome-based clients

Significantly improved media transport robustness for Chrome-based WebRTC clients (Infinity Connect desktop client and Infinity Connect web app on Chrome browsers).

Negative acknowledgements and RTP retransmission have been implemented for video sent between Chrome-based clients and Pexip Infinity.

 
Administrative usability improvements

The following administrative usability improvements have been made:

  • You can use the Pexip Infinity Administrator interface to transfer a participant to another conference.
  • Improved conference media graph — when viewing the status of an ongoing conference the media graph now highlights the nodes and endpoints within each system location. You can also view the current media load for each Conferencing Node, see real-time packet loss data for each connection, and use your mouse to pan and zoom the graph.
  • You can view the current and historical (last 7 days) capacity and media load of a system location.
  • You can view the historical (last 7 days) media load of a Conferencing Node.
  • The Pexip Infinity Administrator interface now uses drop-down menus and has a lighter color scheme. (The submenu groupings and order are unchanged.)
  • Tables now allow multi-level sorting.
  • The status of a self-signed TLS certificate on the Management Node or on a Conferencing Node is shown as Temporary.
  • You can specify a free-format description when configuring NTP, DNS and syslog servers.

Transferring a participant to another conference

Viewing current conference status

Viewing system location status

Additional layout A new 2 + 21 layout is now available. Selecting the layout seen by participants

Changes in functionality in version 13

Feature Description More information
Video watermarking is enabled by default in the base theme and in all preconfigured themes

Video watermarking, which overlays a small transparent image onto the main speaker video during a conference, is enabled by default in version 13 in the base theme and in all preconfigured themes.

After upgrading to version 13, the default Pexip watermark will be applied to all conferences, even if an existing custom theme has been applied to that VMR.

If you want to remove watermarking or use a different watermark image, you need to create a customized theme with either watermarking disabled (by changing the themeconfig.json file to state "disable_watermark_icon" : true,) or with a different image (by replacing the watermark_icon.png file), and then apply that customized theme as either the new default theme for your system, or apply it to individual services (VMRs, Call Routing Rules etc).

If you have an existing custom theme, you can update that theme either to disable watermarking (by adding "disable_watermark_icon" : true, to the themeconfig.json file) or to use a different watermark image (by adding your own watermark_icon.png file).

Note that you cannot modify the base theme — you must upload your own customized theme and set it as the new default theme, or apply your custom theme to individual services.

Video watermarking

Creating and applying themes to conferences

Changed images in the Base Pexip theme The Base Pexip theme contains different images for the PIN entry screens and other information screens such as "Capacity exceeded", "Insufficient licenses", "Connecting", and so on. You can change any of these images, if required, by uploading your own customized theme.

Base theme and other preconfigured themes

Creating and applying themes to conferences

HSTS (HTTP Strict Transport Security) has been enabled Pexip Infinity nodes now enable HSTS to ensure greater security. This means that if your deployment moves from using a valid TLS certificate to using an invalid certificate (e.g. you redeploy a Conferencing Node, or your certificate expires or is invalidated for some reason) then certain web browsers will stop you from accessing that node via the web when using the DNS name of that node, until you correct the certificate issue. You may browse directly to the IP address of the node in the meantime. This applies to the Management Node and Conferencing Nodes. Managing TLS and trusted CA certificates
Registered aliases returned in status queries are lower case All registered aliases in status information shown on the Pexip Infinity Administrator interface or returned via the management API are always in lower case, regardless of the capitalization of the alias that was actually registered.  

Features added in version 12

Pexip Infinity version 12 added the following features and enhancements:

Feature Description More information
Microsoft Azure cloud service support

Pexip Infinity can now be deployed on the Microsoft Azure cloud service. Using a cloud service provides scalable computing capacity and eliminates your need to invest in hardware up front, so you can deploy Pexip Infinity even faster. (Note that Pexip Infinity can also be deployed on Amazon Web Services.)

You can use a cloud service to launch as many or as few virtual servers as you need, and use those virtual servers to host a Pexip Infinity Management Node and as many Conferencing Nodes as required for your Pexip Infinity platform.

You can scale up or down to handle changes in requirements or spikes in conferencing requirements. This means that you can also use the cloud service provider's APIs and the Pexip Infinity management API to monitor usage and bring up / tear down Conferencing Nodes as required to meet conferencing demand.

Pexip publishes disk images for the Pexip Infinity Management Node and Conferencing Nodes. These images may be used to launch instances of each node type as required.

Deploying Pexip Infinity on Microsoft Azure

1080p (Full HD) support You can now enable 1080p (Full HD) across your deployment. Enabling Full HD (1080p) for main video in calls
Routing rules for outbound calling

Routing rules can now optionally be applied to outbound calls made from within a conferencing service, such as when dialing out to add a participant to a Virtual Meeting Room or when configuring an Automatically Dialed Participant.

Within the Pexip Infinity Administrator interface, the Service configuration > Distributed Gateway menu path is now Service configuration > Call routing and "Gateway Routing Rules" are now generally referred to as "Call Routing Rules".

When configuring routing rules you can decide whether the rule applies only to incoming Pexip Distributed Gateway calls (the default, and as per behavior in previous releases), or only to outgoing calls placed from within a Pexip Infinity conference, or to both incoming gateway calls and outgoing calls from conferences.

Routing rules can also be temporarily disabled, allowing you to more easily test configuration changes.

Configuring Call Routing Rules
Ability to route calls to registered devices only

When configuring Call Routing Rules you can specify whether the call is to be routed to registered devices only, or — as per previous behavior — to route the call to a matching registered device if it is currently registered, otherwise attempt to route the call via an external system such as a SIP proxy, Skype for Business / Lync server, H.323 gatekeeper or other gateway/ITSP.

Note that on upgrading to version 12, any existing rules that have a SIP proxy of "nowhere.invalid" will be automatically changed to a "registered devices only" rule (as any rule with a proxy of "nowhere.invalid" could never result in a call to an external system).

Configuring Call Routing Rules
Simplified routing of Pexip Distributed Gateway calls into Skype for Business / Lync meetings

Pexip Distributed Gateway routing rules can be explicitly configured to route calls into an ad hoc or scheduled Skype for Business / Lync meeting, based on the Conference ID.

This allows end users direct entry into a Skype for Business / Lync meeting without requiring them to go via a Virtual Reception (IVR) first.

Configuring Pexip Infinity as a Skype for Business / Lync gateway
Holding screens when there is only one video participant in a conference

When a participant is the only device in a Pexip Infinity conference or Pexip Distributed Gateway call that is sending video, that participant now sees a holding screen until other video participants join the conference.

The holding screen indicates either that the participant is the only participant in the conference, or that all of the other participants are audio-only (and they are shown via their audio-only indicators as usual).

The holding images are fully customizable via the theme associated with the service (Virtual Meeting Room, Call Routing Rule etc).

Selecting the layout seen by participants and Customizing conference images and voice prompts using themes
Guest-only conferences with control-only Host A Host can join a conference as a presentation and control-only participant and start the conference, allowing Guest participants to join. This means that the presentation and control-only Host can manage the conference without being a participant. (Previously the Host would have had to join as a video or audio participant in order for Guests to join.) Using Infinity Connect in-call controls
Participant transfer You can use the management and client APIs to transfer a participant to another conference.

Management command API

Using the Pexip client APIs

Improved TLS certificate management

You can more easily upload and view individual TLS server certificates, and configure the node(s) to which each certificate is assigned.

You can also import multiple certificates in one step, for example a TLS certificate and its associated CA bundle.

An alarm is raised if the Management Node or a Conferencing Node has no associated TLS certificate, or if a TLS certificate has an incomplete chain of trust to the root CA certificate.

Managing TLS and trusted CA certificates
SIP TLS FQDN and TLS certificates specified during deployment You can now specify the SIP TLS FQDN and TLS certificate to be used by a Conferencing Node at the time you deploy it (rather than after it is deployed). Deploying new Conferencing Nodes
web app participants can view presentations in a separate window

Infinity Connect web app participants can elect to view the current presentation in a separate pop-out window. This applies to the presenter as well as those viewing the presentation.

Introduction to Infinity Connect
Audio notification when participants waiting to join a locked conference A new audio file has been added to the base theme that plays a notification to all participants in a locked conference to indicate that there is a participant waiting to be let in. Locking a conference and allowing participants to join a locked conference
WebRTC support for Infinity Connect web app clients using Microsoft Edge Infinity Connect web app clients using Microsoft Edge version 20.10532 or later will now connect to Pexip Infinity conferences over WebRTC. Earlier versions of Microsoft Edge will continue to connect over RTMP and use Flash video. About the Infinity Connect web app
DTMF conference controls Host participants using telephones or SIP/H.323 endpoints that support DTMF can now lock and unlock a conference, mute and unmute all guests, and terminate a conference, using DTMF controls. The controls are customizable on a per-theme basis via the themeconfig.json file. Using DTMF to control a conference
Including the PIN in VMR dial strings SIP and H.323 endpoints and Skype for Business / Lync clients that dial into PIN-protected conferences can bypass the PIN entry screen by including the PIN in the dialed alias. Including the PIN in the dial string to bypass the PIN entry screen
Virtual Reception support for Skype for Business / Lync clients

Lync/Skype for Business clients can now use the Virtual Reception service to either join a VMR or to route calls via the Pexip Distributed Gateway.

Virtual Receptions and Skype for Business / Lync clients
Ability to restrict or transform the aliases entered into a Virtual Reception

New Virtual Reception configuration options allow you to restrict the aliases or alias patterns that can be entered into a Virtual Reception and optionally transform the entered alias before the Virtual Reception attempts to route the call to that new destination.

Restricting or transforming the aliases entered into a Virtual Reception
Including the VMR alias / Conference ID in Virtual Reception dial strings

SIP and H.323 endpoints can optionally bypass having to enter the VMR destination alias or a Skype for Business / Lync Conference ID via DTMF tones.

Instead they can include the numeric alias of the VMR or the Skype for Business / Lync Conference ID in the Virtual Reception dial string.

About the Virtual Reception IVR service

Using Pexip Infinity as a Skype for Business / Lync gateway

Automatic daily backups

You can choose to automatically backup the Management Node configuration data on a daily basis.

Also, when restoring a backup there is a new confirmation step where you can see the Management Node IP address that will be restored.

Backing up and restoring configuration
Global bandwidth limits You can now set the maximum inbound and outbound call bandwidth on a system-wide basis, as well as per service. Managing and restricting call bandwidth
Additional Conferencing Node status information Information regarding a Conferencing Node's current media load and total estimated capacity in terms of HD connections is now available via the main Conferencing Node status page of the Administrator interface. Viewing Conferencing Nodes
Adaptive strategy for registration refresh intervals

When calculating the registration refresh interval for registered SIP and H.323 devices, Pexip Infinity now uses an adaptive strategy by default. It will automatically adjust the refresh interval depending on the number of current registrations on the Conferencing Node handling the registration request, in order to spread the load of registration refreshes.

You can also configure separate registration refresh intervals for SIP endpoints that are registering from behind a NAT.

Registering devices to Pexip Infinity
Improved theme management When adding or modifying a theme you can now assign the Call Routing Rules that will use that theme. Creating and applying themes to conferences
Dual streaming RTMP participants can be added via the Pexip Infinity Administrator interface When using the Pexip Infinity Administrator interface to add an RTMP streaming participant to a conference you can now optionally enter the RTMP URL for a second (presentation) stream. Manually dialing out to a participant from a conference
"Keep conference alive" option for manually dialed participants You can now determine whether participants who have been added to a conference by an administrator (either from the Administrator interface or using the Management API) have the ability to keep a conference alive. Automatically ending a conference
Display name for dialed participants You can specify a display name for participants that are added to a conference either manually via the Pexip Infinity Administrator interface, as an automatically dialed participant, or via the management API. Manually dialing out to a participant from a conference
Audio output device selection From Chrome 50, Infinity Connect clients will offer the option to select the device used for audio output. Configuring Infinity Connect clients

Changes in functionality in version 12

Feature Description More information
Maximum PIN length of 20 digits

The maximum PIN length for Host and Guest PINs has been extended from 10 to 20 digits.

If you use customized themes you should regenerate your PIN entry screen images to ensure that you have customized versions of the new screens (for the entry of 11–20 digits). This is particularly important if you use PINs with a trailing #.

 
Support for VMware vSphere ESXi 4.1 has been deprecated

ESXi 4.1 support has been deprecated in Pexip Infinity v12 because ESXi 4.1 does not support AVX or AVX2, and these are required in Pexip Infinity v12 (see below).

If you have upgraded to Pexip Infinity from a version prior to v12, you can still deploy Conferencing Nodes to servers running ESXi 4.1; however if you have a new deployment using v12 or later and attempt to deploy a Conferencing Node to a server running ESXi 4.1, that node will go straight into maintenance mode.

 
AVX or AVX2 required

From version 12, new deployments of Pexip Infinity require AVX or AVX2 processor instruction sets. Conferencing Nodes deployed onto a server with older instruction sets will go straight into maintenance mode.

Upgrades from previous versions to version 12 are not affected. Your existing Conferencing Nodes, and any newly deployed Conferencing Nodes, will run on SSE4.1.

 
Management configuration API now always allocates new resource object IDs.

The management configuration API now always allocates a new object ID when creating a new resource. Previously, if a resource was deleted, its ID would have been reused when creating a new resource of the same type.

Management configuration API

Features added in version 11

Pexip Infinity version 11 added the following features and enhancements:

Feature Description More information
Multistreaming support from Skype for Business / Lync AVMCU to Pexip Infinity

Pexip Infinity can receive multiple video streams from a Skype for Business / Lync AVMCU multi-party conference.

This means, for example, that all endpoints connected to a Skype for Business / Lync meeting via the Pexip Distributed Gateway now see a full combined set of both Skype for Business / Lync meeting and any other Pexip gateway participants in the conference. Previously Skype for Business / Lync participants would see all Skype for Business / Lync meeting participants, but gateway participants would only see the currently active Skype for Business / Lync meeting participant.

Pexip Infinity and Skype for Business / Lync integration features
Merge a Skype for Business / Lync meeting with a Pexip Infinity VMR conference

A Skype for Business / Lync meeting can be merged with a conference being hosted on the Pexip Infinity platform. This means that, for example:

  • a Skype for Business / Lync user dialed into a Pexip VMR can use drag-and-drop to add a contact (such as a Microsoft Surface Hub system, or an external SIP/H.323 device) into the meeting. This will create an adhoc Skype for Business / Lync meeting and merge it with the Pexip VMR.
  • a Skype for Business / Lync user in a Skype for Business / Lync meeting can drag and drop a Pexip VMR contact into the Skype for Business / Lync meeting to manually merge the conferences together.

When a conference is merged, participants in the Pexip VMR see a combined set of Pexip VMR and Skype for Business / Lync meeting participants, and the Skype for Business / Lync meeting participants see the Pexip VMR stage alongside the other Skype for Business / Lync meeting participants.

Pexip Infinity and Skype for Business / Lync integration features
H.264 simulcast from Pexip Infinity to Skype for Business / Lync AVMCU

Pexip Infinity can now send the video streams of gateway participants at multiple resolutions to an AVMCU multi-party conference.

This means that if Skype for Business / Lync clients request different video resolutions from the AVMCU, Pexip Infinity can now support the equivalent request from the AVMCU. This optimizes the user experience for all conference participants, and for all device sizes from a mobile client to the Microsoft Surface Hub.

Pexip Infinity and Skype for Business / Lync integration features
Optimized Skype for Business / Lync gateway functionality Pexip's Skype for Business / Lync gateway functionality has been improved to reduce the bandwidth and quantity of streams sent to the AVMCU based on what is requested. (This improvement has no detrimental impact to the user experience.) Pexip Infinity and Skype for Business / Lync integration features
Amazon Web Services (AWS) support

The Amazon Elastic Compute Cloud (Amazon EC2) service provides scalable computing capacity in the Amazon Web Services (AWS) cloud. Using Amazon EC2 eliminates your need to invest in hardware up front, so you can deploy Pexip Infinity even faster.

You can use Amazon EC2 to launch as many or as few virtual servers as you need, and use those virtual servers to host a Pexip Infinity Management Node and as many Conferencing Nodes as required for your Pexip Infinity platform.

Amazon EC2 enables you to scale up or down to handle changes in requirements or spikes in conferencing requirements. This means that you can also use the AWS APIs and the Pexip Infinity management API to monitor usage and bring up / tear down Conferencing Nodes as required to meet conferencing demand.

Pexip publishes Amazon Machine Images (AMIs) for the Pexip Infinity Management Node and Conferencing Nodes. These AMIs may be used to launch instances of each node type as required.

Deploying Pexip Infinity on Amazon Web Services (AWS)

KVM, Xen and ESXi 6.0 hypervisor support

The Pexip Infinity platform can be deployed on KVM and Xen hypervisors.

The Management Node and Conferencing Nodes can now be deployed on KVM and Xen hosts as well as VMware vSphere and Microsoft Hyper‑V hosts.

Support for VMware ESXi 6.0 has also been added.

Configuring KVM for Pexip Infinity

Configuring Xen for Pexip Infinity

Intel AVX2 processor instruction set support

Pexip Infinity can make full use of the AVX2 instruction set provided by modern Intel processors. This increases the performance of video encoding and decoding.

For VMware platforms, ESXi 6 is required to enable this optimization.

Detailed server hardware requirements
web app branding upload

Infinity Connect web app branding packages can be uploaded to the Management Node and automatically pushed out to all Conferencing Nodes.

You can upload the branding packages that are generated by the Pexip branding portal, as well as any manually created customizations.

Customizing the Infinity Connect clients
Additions to theme feature
  • Additional indicators, icons, background colors and text can now be customized using themes.
  • You can now apply themes to Gateway Rules, meaning that you can customize the presence avatar.
Customizing conference images and voice prompts using themes
H.323 gatekeeper functionality

H.323 endpoints can now register to Pexip Infinity.

This means that Pexip Infinity now acts as a SIP registrar and as an H.323 gatekeeper. Note that the Infinity Connect desktop client and the Android mobile client can also register to Pexip Infinity.

Registering devices to Pexip Infinity
View registered aliases You can see a list of all device aliases that are currently registered to the Pexip Infinity platform. Viewing registrations
Ability to change a Conferencing Node's location You can change the system location of an existing Conferencing Node via the Administrator interface (which then automatically reboots the Conferencing Node). Configuring existing Conferencing Nodes

VMR provisioning via LDAP enhanced with daily sync, customizable fields and string length filter

The facility to bulk-provision VMRs from directory information contained in an AD/LDAP server has been enhanced:

  • Automatic daily sync: each VMR sync template can be configured to run automatically on a daily basis. Note that on upgrade, your existing templates will not be set to run automatically.
  • Customizable LDAP fields: to complement the standard LDAP fields that can be used as variables, administrators can add their own fields to support additional attributes in their LDAP/AD schemas.
  • New pex_strlen filter which returns the length of string.
Provisioning VMRs, devices and users from Active Directory via LDAP
Improved trusted CA certificate management

You can now upload, view and delete individual trusted CA certificates, in addition to being able to import a file of one or more certificates.

An alarm is raised when a certificate is due to expire within the next 30 days.

Managing TLS and trusted CA certificates
Ability to limit the media capability

You can now specify the maximum media capability of certain calls. Options are audio-only, main video only, or main video plus presentation. This feature allows better resource management and smaller SDPs when calling out to known audio-only devices.

You can place restrictions on a per-conference basis (for Virtual Meeting Rooms and Virtual Auditoriums) or a per-call basis (for outbound and Distributed Gateway calls). You can also limit the capability of a Virtual Reception.

Controlling media capability

Configurable auto-escalation of Skype for Business / Lync audio calls

You can configure whether a Skype for Business / Lync audio call is automatically escalated so that it receives video from a conference.

Previously, such audio calls were always escalated to receive video. From v11 this behavior is configurable and is disabled by default.

Automatically escalating Skype for Business / Lync audio calls
Changes to Host and Guest PIN behavior

Conference PINs can now optionally end with #. This means that:

  • Host PINs and Guest PINs for the same conference can now be different lengths.
  • Users who have accidentally entered too many or too few digits can enter # to return to the start of the PIN entry process.
Using # at the end of a PIN
Skype for Business / Lync Response Group support

SIP Replaces support (RFC 3891 - "Replaces" Header) has been implemented.

This enables support within Pexip Infinity for Skype for Business / Lync Response Group call management.

 
Skype for Business / Lync IVR gateway conference lookup location

When configuring the Skype for Business / Lync IVR gateway functionality, you can specify the system location that will perform the Skype for Business / Lync Conference ID lookup on the Skype for Business / Lync server.

This can assist in scenarios where an external device connects to a Virtual Reception via a Conferencing Node in the DMZ and that node is not trusted by the Skype for Business / Lync FEP.

Configuring Pexip Infinity as a Skype for Business / Lync gateway
Option to mute all guests in a Virtual Auditorium Virtual Auditoriums have a new option to automatically mute all Guests when they first join a conference. After the conference has started, Hosts can use the Infinity Connect client to unmute Guests, either individually or as a group. Configuring Virtual Auditoriums
Send DTMF to manually dialed participants

DTMF sequences can be configured when manually dialing out to participants from a conference via the Administrator interface. The DTMF is transmitted 3 seconds after the call connects to the participant.

Manually dialing out to a participant from a conference
Last conference participant timeout

You can configure at the platform level 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.

By default the Last participant backstop timeout setting is configured to never eject the last participant.

About global settings
Additional options to determine whether an ADP can keep a conference alive

In addition to the existing behavior (where a conference would be terminated if the only remaining participant was an Automatically Dialed Participant, unless there were two or more ADPs and at least one was a Host), there are now two other options:

  • a Host ADP can be configured to always keep a conference alive even if they are the only remaining participant
  • an ADP can be configured to never keep a conference alive.
Keeping a conference alive
Infinity Connect one-click join The process of joining conferences via Infinity Connect has been streamlined. Users now elect, prior to joining the conference, whether they will join a conference with full video and audio, with audio only, or as presentation and control-only.  
Infinity Connect supported in Microsoft Edge The Infinity Connect web app is now supported in Microsoft Edge. Using the Infinity Connect web app
Infinity Connect users can change the role of other participants Infinity Connect users who have a role of Host can change the role of other users in the conference. This is useful, for example, if a Host needs to leave the conference; they can promote one of the Guests to a role of Host so that the conference will continue after they disconnect. Changing a participant's role from Guest to Host (and vice versa)
Infinity Connect users can automatically mute microphone on joining Many videoconference users mute their microphones unless they are actually speaking, to reduce the level of background noise. This option allows users to join with their microphone muted by default.  
New parameters supported in preconfigured URLs

Additional parameters are now supported in URLs that can be provided to Infinity Connect web app users to preconfigure conference joining information:

  • <escalate> offers users the camera and microphone selection options immediately upon joining
  • <extension> provides the Virtual Reception extension, or the Skype for Business / Lync Conference ID.
Creating preconfigured links to conferences via Infinity Connect
Alarm raised when Management Node limit is reached An alarm is raised if the Management Node does not have sufficient resources for the current deployment size (number of Conferencing Nodes). Viewing alarms

Features added in version 10

Pexip Infinity version 10 added the following features and enhancements:

Feature Description More information
VMR provisioning from Active Directory / LDAP

Pexip Infinity Virtual Meeting Rooms can be bulk-provisioned from directory information contained in a Windows Active Directory LDAP server, or any other LDAP-accessible database.

This means, for example, that you can automatically provide a personal VMR for every employee in an organization. Data such as employee names can be imported from the directory and used to generate a unique name and alias for each VMR, following a pattern such as meet.<username>@example.com. Other VMR attributes such as PIN numbers can also be generated, depending upon how you configure your VMR template.

After the VMRs have been generated you can periodically re-run the provisioning process to resynchronize your VMRs to cater for additions and removals to the directory.

Provisioning VMRs, devices and users from Active Directory via LDAP
Lync IVR gateway

Within on-prem Lync deployments a Virtual Reception can act as a "Lync IVR lobby" to route calls based on the Lync Conference ID into any ad hoc or scheduled Lync multi-party conference.

This means that Lync users can schedule and use Lync conferences in the normal way. A Lync conference ID is generated when an on-prem Lync deployment is configured with a dial-in access number. Non-Lync users (H.323, SIP, Infinity Connect endpoints etc) can then dial a URI or IP address of the "Lync IVR lobby" and enter that Lync conference ID to join the Lync conference from the video endpoint. Lync users and video endpoint users can then see each other and present to each other.

Configuring Pexip Infinity as a Lync gateway
Pexip StudioSound™

Pexip’s new StudioSound™ audio feature brings recording studio technology and quality to video, audio, and web conferencing. It greatly improves the overall experience by making conferences and meetings sound better, with improved intelligibility.

StudioSound™ is part of the standard Pexip Infinity feature set and is utilized automatically in all conferences.

Infinity Connect clients can register and receive calls

Infinity Connect desktop clients for Windows, Mac OS X and Linux, and Infinity Connect mobile clients for Android can register to Pexip Infinity Conferencing Nodes.

This means that users who have registered their Infinity Connect client can be dialed in to a Pexip conference, and can receiving incoming calls placed via the Pexip Distributed Gateway.

Registering devices to Pexip Infinity
Infinity Connect enhancements

Further enhancements have been made to Infinity Connect clients. These include:

  • Ability to preview your own video (self view) and check camera and microphone settings before joining a call.
  • New toolbar icons to start video, or to start audio-only when joining a call.
  • Ability to send DTMF tones (via the keypad) to another participant.
  • Host or Guest indication in the participant list.
  • "Currently speaking" badge in the participant list.
  • Each participant is shown as a single entry in the participant list, even if they are sending multiple media streams.
  • Information about each participant is now available by clicking on their name in the participant list.
  • Ability to stop sending a presentation to a participant is now available in all clients.
  • Ability to send anonymous usage statistics to Pexip. (This helps us improve the operation of the Pexip Infinity platform based on real-life customer usage data.)
Introduction to Infinity Connect
New audio-only indicator

Audio-only participants are now represented by an avatar on the left side of the video window. Whenever an audio-only participant is speaking, their avatar slides out to show their name; the most recent video participant to speak will remain in the main video window. You can use an external policy server to personalize the avatar for individual participants, otherwise the avatar will be an icon of a telephone handset.

Note: As a consequence of this change, the audio_avatar.jpg theme file was deprecated in v10 and has been removed completely in v11.

Selecting the layout seen by participants
Separate RTMP streams for video and presentation content

Pexip Infinity can stream the main video and presentation content channels separately over RTMP.

This means that when streaming a conference over RTMP — to streaming and recording services such as YouTube — viewers can simultaneously access the main video stream of the participants and a separate presentation content stream.

Streaming a conference to YouTube
Active speaker shown when receiving single-stream presentation When sending presentation content to a single-stream endpoint such as Skype or broadcasting via an RTMP stream (when not dialed out with dual streaming), Pexip Infinity sends the video stream of the active speaker in a small window in the upper right corner of the presentation. Selecting the layout seen by participants
Send content with a video thumbnail to Lync Room Systems Pexip Infinity can now send presentation content to Lync Room Systems (SMART and Crestron) in main video with the active speaker as a thumbnail. This allows both content and main video to be seen whenever an LRS system connects directly to a Pexip VMR.  
Improved status reporting for Infinity Connect and Lync clients

When viewing the status of conference participants, Infinity Connect and Microsoft Lync clients are now shown as a single participant instance, regardless of whether they have active media streams or if they are presenting content.

Each participant's status shows the individual media streams, and for completed conferences it may show multiple instances of each stream type (for example if the participant had started presenting, stopped and then started presenting again).

Viewing participant status
Reject calls via external policy

When responding to a service configuration request, an external policy server can instruct Pexip Infinity to reject the call associated with that service request.

If the policy server does not return the service configuration data and it does not instruct Pexip Infinity to reject the call, then Pexip Infinity will continue with its standard processing behavior (it will attempt to obtain the relevant information from its own internal database).

 
Improved scalability for WebRTC calls Scalability improvements for WebRTC video handling in distributed conferences.  
Login history You can view the 100 most recent attempts to log in to the Pexip Infinity Administrator interface. Viewing login history
Limited duration snapshot As an alternative to generating a full diagnostic snapshot, you can specify the number of hours to include in a limited duration snapshot. Downloading a diagnostic snapshot
Customizable Lync contact list avatar for gateway contacts The Lync contact list avatar that is displayed for contacts reached via the Pexip Distributed Gateway can be customized. You can do this by modifying the presence_avatar_image.jpg file contained in the default theme. Presence and contact lists in Skype for Business / Lync environments

Features added in version 9

Pexip Infinity version 9 added the following features and enhancements:

Feature Description More information
Infinity Connect web app and desktop client enhancements

Instant Messaging and chat

Conference participants using a variety of clients can chat and share links with other participants. Supported clients include Microsoft Lync, Skype, and Skype for Business. Chat is also natively supported in Pexip's own Infinity Connect suite (Web App and desktop client). Microsoft Lync and Infinity Connect clients can also chat when calling each other directly via the Pexip Distributed Gateway.

Content sharing

All users can now share images and PDF content from any browser.

Notifications and selective unlocking for a locked conference

When a new participant attempts to connect to a locked conference using a Guest PIN (or without a PIN if it is an open conference), the Hosts are notified that the participant is waiting to join. Hosts can then selectively either allow the participant to join the conference, or reject the request and disconnect the participant. While waiting, the participant is held in the conference lobby, where they will see and hear the waiting for conference host message (these items are customizable via themes).

Conference control

Host participants now have the options to mute all Guest participants simultaneously, and to disconnect all participants simultaneously.

Role selection when adding participants

You can select the role (Host or Guest) when adding a participant to a conference.

New and improved design

The Infinity Connect web app and desktop clients have been redesigned with a new look and workflow to support the chat, content sharing and conference control features. This allows, for example, conference participants who are using a video conferencing endpoint, or a Microsoft Lync client, to use Infinity Connect to connect to the conference without audio and video, but have access to all of the advanced features.

Simplified rebranding

It is now easier to rebrand the styles and images used in the Infinity Connect clients. You can add a logo, a background image and set the colors to match your own corporate branding. Existing customers who have rebranded the Infinity Connect web app have to reapply their branding in version 9. Any textual changes to labels and messages also has to be reapplied. As any existing branding on the Conferencing Nodes will be removed when upgrading, customers may want to prepare their updated branding prior to upgrading.

Enabling and disabling chat

Locking a conference and allowing participants to join a locked conference

Introduction to Infinity Connect

Outbound video streaming to Content Delivery Networks and public services Pexip Infinity can output a dedicated multimedia stream to enterprise CDN (Content Delivery Network) streaming and recording services such as Wowza, Adobe, VBrick, and Microsoft Azure, and to public streaming services such as YouTube. Any Pexip conference can be streamed as a live event to an unlimited number of viewers, and can be recorded and stored for later consumption. Streaming and recording a conference
Device registration Endpoint devices can register to Pexip Infinity Conferencing Nodes. This allows Pexip Infinity to route outbound calls to those registered devices without having to go via a SIP proxy or rely on DNS. Registering devices to Pexip Infinity
External policy

Pexip Infinity's external policy feature allows call policy decisions to be taken by an external system, based on the data sources that are available to that system. This allows Pexip Infinity administrators to implement routing decisions based on their specific requirements. The external system can, for example, return VMR configuration data and JPEG avatars to represent participants in a conference, and decide the location for the placement of media on a per call basis.

Using the external policy server API with Pexip Infinity
Backup and restore Administrators can backup and restore configuration data via the Pexip Infinity Administrator interface. Backing up and restoring configuration
Location-based call control enhancements

Pexip Distributed Gateway

You can optionally configure Call Routing Rules to place the outgoing call from a Conferencing Node in a specific location (rather than from the node that received the call). This means that internal LAN-facing nodes and NATted DMZ-facing nodes can act as a gateway between internal and external traffic.

Automatically dialed participants

You can optionally configure an Automatically Dialed Participant to be called from a Conferencing Node in a specific location (rather than from the node being used by the participant who initiated the conference).

About the Pexip Distributed Gateway service
and
Automatically dialing out to a participant from a conference
Microsoft Lync integration enhancements

Per-location Lync MSSIP domain

You can specify the Lync MSSIP domain per location. If configured, it is used instead of the global Lync MSSIP domain in outbound calls to Lync from Conferencing Nodes in that location. This makes it easier for service providers, for example, to support multiple Lync domains.

Direct gateway calls into the AVMCU

Calls received via the Pexip Distributed Gateway can now be configured to call directly into an AVMCU multi-party conference (both ad-hoc and scheduled calls hosted on AVMCU).

Audio-only calls

When making audio-only calls from Lync to a Pexip Virtual Meeting Room, the participants in the VMR will only receive your audio. However, the Lync user will receive video and audio from the VMR. The Lync call can be escalated to video in the normal way by starting video, if required.

Resizing shared application content

When a Lync user shares an application (rather than their screen), additional black borders are now removed and the shared content is resized to cover the full dual video stream for receiving endpoints/clients.

Integrating Microsoft Skype for Business / Lync with Pexip Infinity
STUN servers

Conferencing Node STUN servers

You can configure the STUN servers used by Conferencing Nodes on a per location and per gateway rule basis. This enables a Conferencing Node to discover its public NAT address in deployment scenarios where the TURN server is not located outside of the enterprise firewall.

Infinity Connect WebRTC client STUN servers

You can configure the STUN servers to be used by Infinity Connect WebRTC clients when they connect to a Conferencing Node in a specific system location.

In previous releases, Infinity Connect WebRTC clients always used stun.l.google.com. This STUN server address is included by default in v9. Customers upgrading from previous releases will have the stun.l.google.com server address added automatically to all existing system locations, resulting in no change to previous behavior.

Using STUN servers with Pexip Infinity
Join/leave notifications Themes now include the option to play audio tones to notify when participants join or leave a conference. Playing notification tones when participants join or leave a conference
Additional audio notifications

New audio files have been added so that:

  • when the last Host leaves a conference, the remaining Guest participants are played a notification that their call will be disconnected shortly
  • when there is just one participant in a conference, they are notified that they are the only participant.
Audio (sound) files
Preconfigured themes Pexip Infinity now ships with 4 preconfigured themes that are either with or without entry and exit tones, and that refer to the "#" key as either "the hash key" or "the pound key". Base theme and other preconfigured themes
Layouts

The following enhancements have been made to layouts:

  • Different layouts can be applied to a Virtual Meeting Room as well as a Virtual Auditorium.
  • There is now an additional layout option that allows you to show the main speaker only, in full screen (with no thumbnails).
  • For Virtual Auditoriums, you can elect to pin the presenter to the main video when they are sharing a presentation, regardless of who is speaking.
Selecting the layout seen by participants
Disconnect all participants from a conference You can disconnect all of the participants from a conference via the Status > Conferences page on the Administrator interface. Disconnecting participants from a conference
Conference participant status Conference participant status information indicates if the participant is currently on hold or if the participant is a streaming or recording device. Viewing current conference status
Syslog server connection protocol You can choose the IP transport protocol to use — UDP, TCP or TLS — when configuring a remote syslog server. Using a syslog server
Ability to disable SIP UDP You can enable or disable incoming calls on SIP UDP separately from those over SIP TCP/TLS. Disabling SIP UDP can help reduce SIP spam. On new installations of version 9, SIP UDP is disabled by default. Upgrades from existing versions will have SIP UDP enabled (assuming SIP was enabled previously), and can be disabled in Global Settings. Enabling and disabling SIP, H.323, WebRTC and RTMP
Pexip Infinity Administrator interface improvements

Local timezone

The Pexip Infinity Administrator interface now displays times using the administrator's local timezone. (Log timestamps continue to use UTC.)

New Call control and Users navigation menu options

There are now separate menu options for Call control configuration (H.323 gatekeepers, SIP credentials, SIP proxies, Lync servers, TURN servers, STUN servers and Policy servers) and for User configuration (User authentication, Account roles and LDAP roles).

Timezones
Alarm enhancements

You will now receive a warning when:

  • your license is due to expire within the next 60 days
  • the syslog server is inaccessible

Also, you can view all alarm activity by searching the Administrator log for administrator.alarm. This will show a list of all Alarm raised and Alarm lowered events.

Viewing alarms
Alarm raised and lowered events You can view alarms that have since been resolved by searching the Administrator log for administrator.alarm. This will show a list of all Alarm raised and Alarm lowered events. Viewing alarms
Automatic Conferencing Node deployment improvements

Verify VM manager certificate

When automatically deploying a new Conferencing Node on a VMware host, you can control whether the certificate presented by the VM manager is verified before the connection is allowed.

Faster resource path selection

There is an extra step in the automatic deployment wizard to select a datacenter. The resource path selection is then filtered by the selected datacenter.

Deploying new Conferencing Nodes
Support for G.719 Support has been added for the G.719 audio codec. Audio and video specifications
Endpoint IP addresses removed from analytics events Endpoint IP addresses are no longer included in the information sent when usage reporting has been enabled. Information sent when usage reporting is enabled

Features added in version 8

Pexip Infinity version 8 added the following features and enhancements:

Pexip Infinity platform features

Feature Description More information
Additional codecs

Support has been added for the following codecs:

Audio

  • Siren7™ (licensed from Polycom®)
  • Speex
  • AAC-LC

Video

  • H.261
Audio and video specifications
Guest-only timeout You can now specify the length of time a conference will continue with only Guest participants, after all Host participants have left. Using PINs to differentiate between Hosts and Guests
Optional reporting of usage statistics We have added the option for administrators to provide us with anonymized deployment and usage information. This setting is disabled by default on upgrade from previous versions. Automatically sending usage statistics
Architectural improvements As well as adding new features, this release includes a number of behind-the-scenes improvements, continuing our focus on further enhancing the stability, quality and capacity of the Pexip Infinity platform.  
CDR improvements All Conference Detail Records accessible via the Management Node now include the call video and audio details.  

Microsoft Lync interoperability features

Feature Description More information
Support for outbound RDP to Microsoft Lync Pexip Infinity supports bi-directional RDP. Microsoft Lync users can now send and receive dual streams (previously Lync could send two streams but only receive a single stream). This means Lync users can now view presentation content and the presenter at the same time. To use this feature you must ensure that Pexip Infinity is configured to enable outbound calls to Lync clients. Integrating Microsoft Skype for Business / Lync with Pexip Infinity
Support for bi-directional content sharing for Lync AVMCU conferences When an endpoint is brought into a Microsoft Lync AVMCU conference via the Pexip Distributed Gateway, the endpoint can send and receive dual stream presentation to/from the AVMCU. The Lync AVMCU participants will receive the endpoint presentation as a secondary RDP stream. When Lync clients are sharing desktop or applications in the AVMCU, the content can be viewed on the endpoint as H239/BFCP dual stream.  
Support for Skype*Technology preview only Skype users can connect a full audio and video call into a Pexip Infinity VMR or distributed gateway, either through direct federation to a Pexip Conferencing Node or through an on-premises Lync deployment.  

* Technology preview only

Web and mobile client features

Feature Description More information
New versions of Infinity Connect mobile client An update of the Infinity Connect mobile client for iOS is now available, and includes a version for the SECTOR network.  
Full support for RTMP RTMP is now fully supported (previously available as technology preview in version 7). RTMP is the protocol used by Infinity Connect via Internet Explorer and Safari browsers. Enabling and disabling SIP, H.323, WebRTC and RTMP

Features added in version 7

Pexip Infinity version 7 added the following features and enhancements:

Pexip Infinity platform features

Feature Description More information
Firewall traversal support

New firewall traversal features enable Conferencing Nodes to be deployed in a public DMZ:

  • Privately-addressed Conferencing Nodes can be deployed behind a NAT firewall, allowing external parties to connect directly to them via a public address.
  • Conferencing Nodes can be deployed in the local network and in a DMZ (with a non-NAT firewall in between).
  • Conferencing Nodes support media latching, providing better connectivity for remote SIP endpoints that are behind remote NAT devices.
  • Conferencing Nodes support media over TCP. This improves connectivity through strict firewalls with ICE clients such as Lync and Infinity Connect. TCP media uses the same ports as those used for RDP and RTP content.
  • Static routes can be configured via the Administrator interface and assigned to an existing Management Node, and to new and existing Conferencing Nodes.
Network deployment options
Location overflow when media capacity is reached If a location reaches its capacity for a conference instance, additional "overflow" locations can be utilized to handle the media for new conference participants that are connected (for signaling purposes) to nodes within that location. Overflow locations
DNS and NTP servers per location DNS servers and NTP servers are now configured per location, and apply to all of the Conferencing Nodes in that location. You can also configure specific DNS servers and NTP servers for the Management Node.  
Send DTMF to Automatically Dialed Participants DTMF sequences can be configured for Automatically Dialed Participants. The DTMF is transmitted 3 seconds after the call connects to the participant. Automatically dialing out to a participant from a conference
Pexip Distributed Gateway support for bandwidth restrictions and DTMF

Bandwidth restrictions can be applied to calls made via the Pexip Distributed Gateway. They can be applied to each Call Routing Rule.

If the Pexip Distributed Gateway receives DTMF signaling from an inbound call, it will generate similar DTMF on the outbound call.

 
Service tags Administrators have the option to assign a unique identifier to a Pexip Infinity service (Virtual Meeting Room, Virtual Auditorium, Virtual Reception or Call Routing Rule) and then use this to track usage of the service. Tracking usage with a service tag
Customizable audio avatar The image used in place of an audio participant's video stream is now customizable as part of a theme. Customizing conference images and voice prompts using themes
Default theme You can now nominate a theme to be used by default for any services that do not have a theme selected. Setting the default theme
Conference locking You can now lock a conference after it has started to prevent any further participants from joining. Locking a conference and allowing participants to join a locked conference
Improved media resilience FEC support for VP8.  
Support for 1080p*Technology preview only All resolutions up to and including 1080p (1920 x 1080) at a full 30 frames per second are now supported.  

* Technology preview only

Microsoft Lync interoperability features

Feature Description More information
Improved Microsoft Lync interoperability
  • Pexip Infinity acts as a gateway between Lync and standards-based endpoints.
  • Pexip Infinity supports bi-directional RDP*Technology preview only. Lync users can now send and receive dual streams (previously Lync could send two streams but only receive a single stream). This means Lync users can now view presentation content and the presenter at the same time.
  • CCCP support providing improved features and usability:
    • Initiation of point-to-point calls from Lync to standards-based devices.
    • Drag-and-drop to add H.323/SIP endpoints into a Lync conference.
Integrating Microsoft Skype for Business / Lync with Pexip Infinity

* Technology preview only

Web and mobile client features

Feature Description More information
Infinity Connect suite This release includes Infinity Connect, a suite of software clients that allows end users to connect to Pexip Infinity services from a web browser, an installable desktop client, or a mobile client (supported on Windows, OS X and Linux). This incorporates design and usability updates to what was previously the Pexip Web App. Introduction to Infinity Connect
Browser-based client support extended Access to the browser-based video client has been extended to Opera, IE*Technology preview only and Safari*Technology preview only (in addition to Chrome and Firefox).
Infinity Connect mobile client for SECTOR Network An additional Android version of the Infinity Connect mobile client is available for use in enterprises that require mobile apps to work with management solutions based on OpenPeak's ADAM platform.

 

* Technology preview only

Usability features

Feature Description More information
Support for Russian language The Pexip Infinity Administrator interface can now be displayed in Russian, in addition to Simplified Chinese and English. Changing the display language

Features added in version 6

Pexip Infinity version 6 added the following features and enhancements:

Pexip Infinity platform features

Feature Description More information
Alarms Notifications will appear on the new Alarms page (Status > Alarms) whenever a participant cannot join a conference because of lack of resources or lack of licenses. Viewing alarms
Global settings page Configuration of settings that apply to all Conferencing Nodes, or to the entire platform, have been incorporated on a new Global settings page (Platform > Global settings). About global settings
Limiting participant numbers You can now specify the maximum number of participants that will be allowed to use a Virtual Meeting Room or Virtual Auditorium at any one time. Limiting the number of participants
Enabling or disabling SIP, H.323 and WebRTC You now have the option to select which call protocols (SIP, H.323 or WebRTC) your deployment will support. Enabling and disabling SIP, H.323, WebRTC and RTMP
Lync MSSIP domain You can now specify the name of the Lync domain to which this Pexip deployment belongs.  
Lync presence In a Lync environment, Pexip Infinity will publish presence information for Virtual Meeting Rooms and Virtual Auditoriums.  
Customizable avatars for Lync You can customize the avatar that is displayed in Lync users' contact lists to represent a Virtual Meeting Room or a Virtual Auditorium. Customizing conference images and voice prompts using themes

Security features

Feature Description More information
Integration with external systems You can now configure a username and password to be used by external systems (for example, CUCM) that are integrating with Pexip Infinity. Integrating with external systems
SIP authentication credentials You can now configure the SIP credentials that Pexip Infinity will use if it is challenged for authentication credentials after making a SIP request. Integrating with external systems
AD/LDAP integration You can now enable administrators to use their Active Directory or other LDAP server credentials to log in to the Pexip Infinity web-based Administrator interface or management API. Managing administrator access via LDAP
Role-based authorization If you are using AD/LDAP integration, you can create roles with different access rights for administrators accessing the Pexip Infinity web-based Administrator interface or management API. Managing administrator access via LDAP
OCSP support You now have the option to use OCSP when checking the validity of TLS certificates. Using OCSP to check the status of certificates
SIP TLS verification For SIP connections over TLS, you now have the option to require that peer certificates are verified. Verifying SIP TLS connections with peer systems
SNMPv3 support Pexip Infinity now supports SNMPv3, in addition to SNMPv2c. Enabling SNMP
Secure NTP Pexip Infinity now supports synchronization of time over an encrypted channel. Syncing with NTP servers
AS-SIP Pexip Infinity now supports interoperability with Assured Services SIP (AS-SIP) compliant devices.  
Configurable SSH access You can now disable access over SSH to the Management Node and Conferencing Nodes. About global settings
Management web interface session timeout You can now configure the number of minutes a browser session may remain idle before the user is logged out of the Pexip Infinity Administrator interface. About global settings
Login banner text You can now specify informational text to display in a message box on the Administrator interface login page. About global settings

Pexip Web App features

Feature Description More information
Improved screen sharing for Pexip Web App users Screen sharing from within the Pexip Web App is now enabled via a Chrome extension, and users now have the option to select whether they share their entire screen or a single application.

Introduction to Infinity Connect

Usability features

Feature Description More information
Logs have paginated view and support searching

The entire contents of the administrator log and the support log can now be displayed in the Administrator interface via a paginated view.

You can also search the logs using the new search box at the top left of the page.

About the support log

About the administrator log

Localization The Pexip Infinity Administrator interface can now be displayed in Simplified Chinese, in addition to English. Changing the display language