Pexip Infinity v11.1 Release Notes

Pexip Infinity v11.1 Release Notes Contents Introduction 1 Upgrading to version 11.1 2 New features and improvements in this release 3 Changes in functionality in this release 6 Issues fixed in v11.1 6 Issues fixed in v11 7 Known limitations 9 Introduction This document contains the release notes for Pexip Infinity version 11.1. Complete information about how to install and operate Pexip Infinity is available from the Pexip technical documentation website at docs.pexip.com. The website also contains comprehensive documentation on all aspects of deploying the Pexip Infinity platform. This includes how to use the Infinity Connect client suite, and how to integrate Pexip Infinity with other third-party systems and call control solutions including Microsoft Lync, Cisco Unified Communications Manager, Cisco VCS and Polycom DMA. Management Node host server sizing information You must increase the size of the Management Node host server to 2 cores and 4 GB of RAM for any deployments with more than 10 Conferencing Nodes. We recommend increasing to 4 cores and 6 GB of RAM for any deployments with more than 30 Conferencing Nodes. 2016 Pexip AS Version 11.1.a March 2016 Page 1 of 10

Upgrading to version 11.1 Upgrading to version 11.1 Upgrading from version 4 or later to version 11.1 To upgrade Pexip Infinity software from v4 or later to v11.1: 1. Before upgrading, we recommend that you use your hypervisor's snapshot functionality to take a full VMware/Hyper-V snapshot of the Management Node. If upgrading from v8, due to incompatibilities resolved in v8.1, ensure that you take a non-quiescing snapshot. This snapshot will be required should you later need to downgrade, or if the upgrade fails. You may also want to take a snapshot of each Conferencing Node, although depending on the size and complexity of your deployment it may be easier to simply redeploy these from the Management Node in the unlikely event that this is required. 2. Reboot all Conferencing Nodes. There are two ways of doing this: o o Log in to the virtual hypervisor and reboot the machine using its processes. Connect to the Conferencing Node via SSH, login as admin, and issue the command sudo reboot. 3. Download the Pexip Infinity upgrade package for v11.1 from www.pexip.com/software-download. 4. From the Pexip Infinity Administrator interface, go to Utilities > Upgrade. 5. Select Choose File and browse to the location of the upgrade package. 6. Select Upgrade. There will be a short delay while the upgrade package is uploaded. After the upgrade package has been uploaded, you are presented with a confirmation page showing details of the existing software version and the upgrade version. 7. To proceed, select Upgrade. You are taken to the Upgrade status page, showing the current upgrade status of the Management Node and all Conferencing Nodes. This page automatically refreshes every 5 seconds. 8. When the upgrade completes, all systems will show a status of No upgrade in progress and have the new Installed version. If a Conferencing Node fails to upgrade, for example if it remains on a Waiting for calls to clear status, it should be rebooted. The upgrade process will then continue as expected. If you are using VMware snapshots for backup purposes, we recommend that you delete those snapshots after approximately two weeks, providing your upgraded system is operating as expected. This is because Virtual Machines, in general, should not run with snapshots over time. Upgrading from version 3 to version 11.1 To upgrade Pexip Infinity version 3 software to the latest version, you must first upgrade to version 6. To do this: 1. Download the Pexip Infinity v6 upgrade file (contact your authorized Pexip representative for the link to this file). 2. Follow the steps outlined above, but when asked to Choose File browse to the location of the v6 upgrade file. 3. Verify that the upgrade has completed successfully. 4. Download the Pexip Infinity v11.1 upgrade file. 5. Follow the steps outlined above, and when asked to Choose File browse to the location of the v11.1 upgrade file. For more information For full details on upgrading Pexip Infinity, see the Upgrading the Pexip Infinity platform. 2016 Pexip AS Version 11.1.a March 2016 Page 2 of 10

New features and improvements in this release New features and improvements in this release You can go to https://docs.pexip.com/admin/whats_new.htm and follow the relevant links for more information about all of these features. Version 11.1 This is a maintenance release. This release contains several important security updates. For full information see https://www.pexip.com/security-bulletins. Version 11 Feature Multistreaming support from Lync / Skype for Business AVMCU to Pexip Infinity Merge a Lync / Skype for Business AVMCU conference with a Pexip Infinity VMR conference Description Pexip Infinity can receive multiple video streams from an AVMCU multi-party conference. This means, for example, that all endpoints connected to an AVMCU conference via the Pexip Distributed Gateway now see a full combined set of both AVMCU and any other Pexip gateway participants in the conference. Previously Lync / Skype for Business participants would see all AVMCU participants, but gateway participants would only see the currently active AVMCU participant. A Lync / Skype for Business AVMCU hosted multi-party conference can be merged with a conference being hosted on the Pexip Infinity platform. This means that, for example: a Lync / Skype for Business 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 AVMCU conference and merge it with the Pexip VMR. a Lync / Skype for Business user in an AVMCU conference can drag and drop a Pexip VMR contact into the AVMCU conference to manually merge the conferences together. When a conference is merged, participants in the Pexip VMR see a combined set of Pexip VMR and Lync / Skype for Business AVMCU participants, and the Lync / Skype for Business AVMCU participants see the Pexip VMR stage alongside the other AVMCU participants. H.264 simulcast from Pexip Infinity to Lync / Skype for Business AVMCU Optimized Lync / Skype for Business gateway functionality Amazon Web Services (AWS) support Pexip Infinity can now send the video streams of gateway participants at multiple resolutions to an AVMCU multi-party conference. This means that if Lync / Skype for Business 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's Lync / Skype for Business 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.) 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. 2016 Pexip AS Version 11.1.a March 2016 Page 3 of 10

New features and improvements in this release Feature KVM, Xen and ESXi 6.0 hypervisor support Description 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. 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. 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. 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. 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. View registered aliases Ability to change a Conferencing Node's location VMR provisioning via LDAP enhanced with daily sync, customizable fields and string length filter Improved trusted CA certificate management You can see a list of all device aliases that are currently registered to the Pexip Infinity platform. You can change the system location of an existing Conferencing Node via the Administrator interface (which then automatically reboots the Conferencing Node). 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. 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. 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. Note that in the latter case, SIP endpoints will retain any limits placed on the Virtual Reception when they reach their destination Virtual Meeting Room or Virtual Auditorium; all other endpoints will use the limits of the destination service. Configurable auto-escalation of Lync / Skype for Business audio calls You can configure whether a Lync / Skype for Business 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. 2016 Pexip AS Version 11.1.a March 2016 Page 4 of 10

New features and improvements in this release Feature Changes to Host and Guest PIN behavior Description 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. Lync / Skype for Business Response Group support Lync / Skype for Business IVR gateway conference lookup location SIP Replaces support (RFC 3891 - "Replaces" Header) has been implemented. This enables support within Pexip Infinity for Lync / Skype for Business Response Group call management. When configuring the Lync / Skype for Business IVR gateway functionality, you can specify the system location that will perform the Lync / Skype for Business Conference ID lookup on the Lync / Skype for Business 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 Lync / Skype for Business FEP. Option to mute all guests in a Virtual Auditorium Send DTMF to manually dialed participants Last conference participant timeout 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. 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. 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. 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. Infinity Connect one-click join Infinity Connect supported in Microsoft Edge Infinity Connect users can change the role of other participants Infinity Connect users can automatically mute microphone on joining New parameters supported in preconfigured URLs 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. The Infinity Connect Web App is now supported in Microsoft Edge. 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. 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. 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 Lync / Skype for Business Conference ID. 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). 2016 Pexip AS Version 11.1.a March 2016 Page 5 of 10

Changes in functionality in this release Changes in functionality in this release Feature Starting media when using the Infinity Connect Web App Description Creating preconfigured links to conferences via Infinity Connect The Infinity Connect Web App in version 10 did not automatically start media, so you needed to add &media=1 to any preconfi gured links to conferences to automatically start the camera and mic. In version 11 the assumption is that media will start automatically so you no longer explicitly need to add &media=1. However, if you do not want media to start automatically you must add &media= to any preconfi gured links to conferences. Infinity Connect Web App branding There has been a change to the user-configurable settings in the Infinity Connect Web App. In version 10 the "Always start media immediately when connecting" setting (which was Off by default) is now in version 11 called "Show camera / microphone options when connecting" and is On by default. This is the setting that determines whether users are presented with the camera and mic selection screen prior to joining a conference. Note that if you want to customize the default value for this setting, in the settings.js file a new startmedia setting has replaced the previous promptmedia setting. For more information see Advanced Infinity Connect Web App customization. Issues fixed in v11.1 Pexip 6136 This resolves an issue where Pexip Infinity would not use high-resolution WXGA or 720p presentation streams with Tandberg MXP endpoints. 6127 This resolves a compatibility issue with Chrome v50 where calls could fail. 6101 Pexip Infinity now supports the ability to modify the 'Allowed SIP' methods in the middle of a call. This improves third-party interoperability with gateways and SBCs that may require method modification to keep calls alive. 5938 This resolves an issue where dial-out occasionally fails when initiated from a Conferencing Node that is no longer involved in a call. 5903 The Infinity Connect client can now successfully initiate dual-stream RTMP dial-out. 5889 This resolves an issue where the "you are the only participant in the conference" audio prompt was occasionally played multiple times. 5882 Changes to themes are now correctly synchronized with Conferencing Nodes after approximately 1 minute. 5563 This resolves an issue in Pexip Infinity calls where volume levels are quieter than expected, and where audio may also briefly cut out. 5306 Call history processing on the Management Node no longer uses excessive memory. Microsoft 6117 This resolves an occasional issue where Lync calls would not receive presentation content if the RDP call was routed to a different Conferencing Node than the audio/video call. 2016 Pexip AS Version 11.1.a March 2016 Page 6 of 10

Issues fixed in v11 6057 This resolves an issue where Lync presentation content (RDP) is seen to have high latency from Pexip Infinity towards the Lync client. 5683 This resolves an issue where an unexpected system fault could occur when connecting to an AV-MCU conference if the call signaling and media were split between Conferencing Nodes in different system locations. Cisco 5998 This resolves an issue with receiving DTMF tones from Cisco CTS release 1.10.13. Polycom 5898 This resolves an issue with Polycom endpoints behind NATs not receiving presentation video. Issues fixed in v11 Pexip 5461 Audio from quiet participants would occasionally fade out in version 10.2. This has now been resolved. 5409 Registrations with the sips: URI scheme, as used by Avaya and some other vendors, can now be called from Pexip Infinity. 5303 Static NAT addresses are now correctly used for outbound H.323 calls. 5284 Calls are now correctly placed from the requested outgoing location if one has been configured for an Automatically Dialed Participant or a Gateway Routing Rule. 5276 All ICE calls now allocate 4 ports per media line/stream from the configured media port range. Previously, ICE calls reserved 2 ports from the media port range and 1 port from the ephemeral range. 5249 Conference hosts using Infinity Connect can now allow participants to enter a locked, PIN-protected conference. 5219 STUN servers used with Lync/Skype for Business can now be specified with an FQDN. 5213 You can now use the management API or the Pexip Infinity Administrator interface to dial out from a VMR that was created through external policy. 5078 The Management Node now properly creates a backup file if the system includes themes that are in excess of 2.5 GB of hard disk storage. 4945 An Infinity Connect client that stops presenting shortly after it starts will now properly release presentation to prevent future issues with sharing from other clients. 2010 If during a single conference a new presentation stream is started but fails to connect, the last frame from the previous presenter can no longer be occasionally visible to the participants of the conference. 2016 Pexip AS Version 11.1.a March 2016 Page 7 of 10

Issues fixed in v11 Microsoft 5573 A compatibility issue with content sharing between Pexip Infinity and Skype for Business 2016 has been resolved. 5040 If an Infinity Connect participant makes an audio-only call through the Pexip Distributed Gateway to a Lync client, the call connects as audio-only as expected. If that Lync client then escalates the call and connects to another Lync client as audio only, then escalates to video, the Infinity Connect participant may disconnect unexpectedly. This issue is resolved in version 11. 5020 Microsoft Lync or Skype for Business clients that connect into a Pexip VMR as audio-only may not be properly considered an audioonly call, but rather a video call that does not support video. There is now a global setting that allows the administrator to configure whether or not Lync audio calls are automatically escalated to video. 4694 A presence subscription message from consumer Skype is now recognized as a Microsoft-specific message. 4358 If a Lync 2013 for Windows client joins a VMR as a video participant, pauses video, ends video, then resumes video, the main camera stream will not properly resume. This issue is resolved in version 11. 4210 Intermittent Distributed Gateway calls to the Lync AV-MCU will experience loss of video from AV-MCU when the remote client resumes a call previously placed on hold. This issue is resolved in version 11. 2016 Pexip AS Version 11.1.a March 2016 Page 8 of 10

Known limitations Known limitations Pexip 5832 An audio-only conference participant who is using the Infinity Connect Web App via Internet Explorer, Microsoft Edge or Apple Safari browsers cannot present content (share images or PDFs) to the conference. To resolve this the user can connect and present successfully by using a WebRTC-enabled browser instead such as Chrome, Firefox or Opera, or by using the Infinity Connect desktop client or an Infinity Connect Mobile client. 4971 A dual-streamed RTMP participant can only be added via the Infinity Connect clients. You cannot add a dual-streamed RTMP participant via the Administrator interface or management API. 4836 If an Infinity Connect participant joins as a control/presentation only participant, and then escalates to full audio and video capabilities on a Conferencing Node that is out of resources, the participant will be disconnected. 4665 Incoming audio is not properly recognized on an incoming SIP call from SPIRENT ios clients. 4312 Occasionally, group chat messages may not be displayed to Infinity Connect Web App participants who are using Internet Explorer. Cisco 4142 If the presentation channel already active from an MXP is taken by another connected participant, the MXP may not properly receive presentation content. Microsoft 5100 If a Conferencing Node being used as a gateway into a Lync AV-MCU conference is near processor capacity and another endpoint in the AV-MCU conference starts sending content, a participant may be inadvertently disconnected from the conference. To resolve this, the endpoint can dial back into the conference. 4926 Participants calling into Lync/Skype for Business through the Pexip Distributed Gateway may experience inconsistent call rejection messages if a Conferencing Node is placed into maintenance mode. 4812 In some instances, one of two messages sent to a VMR from two Lync clients not previously connected may not be properly retained by the VMR. To resolve, re-send the message. 4465 Audio may fail to resume if a Skype client behind a NAT mutes its microphone for a prolonged period of time while connected to a Pexip VMR. 4382 Rarely, outbound calls made from Infinity to Lync clients registered to a Lync Edge server will fail. Re-attempting that same call should succeed without issue. 4195 Participants connected via the Pexip Distributed Gateway into the AV-MCU may not receive presentation content from Lync participants. This occurs if the Lync user has a screen resolution where the width is an odd number of pixels, such as a resolution of 1437x758. If this occurs, one workaround is for the user to share an application rather than their full desktop. 2497 If a Cisco VCS is used as call control between a Conferencing Node and a Lync 2013 FEP, only audio calls are possible. Lync FEP and Conferencing Nodes should be neighbored directly then audio and video calls will work as expected. 2016 Pexip AS Version 11.1.a March 2016 Page 9 of 10

Known limitations Polycom 4684 An incoming H.239 presentation from an H.323 Polycom RealPresence endpoint may not be properly recognized if that call flows through a Sonus SBC. 2016 Pexip AS Version 11.1.a March 2016 Page 10 of 10