Pexip Infinity v10.2 Release Notes

Pexip Infinity v10.2 Release Notes Contents Introduction 1 Upgrading to version 10.2 2 New features and improvements in this release 3 Issues fixed in v10.2 5 Issues fixed in v10.1 5 Issues fixed in v10 6 Known limitations 8 Introduction This document contains the release notes for Pexip Infinity version 10.2, released on 30 September 2015. 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. 2015 Pexip AS Version 10.2.a November 2015 Page 1 of 10

Upgrading to version 10.2 Upgrading to version 10.2 Upgrading from version 4 or later to version 10.2 To upgrade Pexip Infinity software from v4 or later to v10.2: 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 v10.2 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 10.2 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 v10.2 upgrade file. 5. Follow the steps outlined above, and when asked to Choose File browse to the location of the v10.2 upgrade file. For more information For full details on upgrading Pexip Infinity, see the Upgrading the Pexip Infinity platform. 2015 Pexip AS Version 10.2.a November 2015 Page 2 of 10

New features and improvements in this release New features and improvements in this release Version 10.2 This is a maintenance release. This release resolves the audio issues around background noise amplification seen in version 10.1. Version 10.1 This is a maintenance release. Version 10 Feature VMR provisioning from Active Directory / LDAP Description 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. 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. 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. 2015 Pexip AS Version 10.2.a November 2015 Page 3 of 10

New features and improvements in this release Feature Infinity Connect enhancements Description 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.) 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: You can no longer use themes to customize the audio avatar (although the audio_avatar.jpg file is still included in a theme, it is not currently used). This functionality will be included in a future release. Separate RTMP streams for video and presentation content Active speaker shown when receiving singlestream presentation Send content with a video thumbnail to Lync Room Systems Improved status reporting for Infinity Connect and Lync clients 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. 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. 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. 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). 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 Login history Limited duration snapshot Scalability improvements for WebRTC video handling in distributed conferences. You can view the 100 most recent attempts to log in to the Pexip Infinity Administrator interface. As an alternative to generating a full diagnostic snapshot, you can specify the number of hours to include in a limited duration snapshot. 2015 Pexip AS Version 10.2.a November 2015 Page 4 of 10

Issues fixed in v10.2 Feature Customizable Lync contact list avatar for gateway contacts Description 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. Issues fixed in v10.2 Pexip 5354 The audio issues around background noise amplification seen in version 10.1 have been resolved. Issues fixed in v10.1 Pexip 5117 An RTMP participant can no longer be left as the only participant in a conference if an invalid URI is used as the RTMP dual stream address when adding an RTMP participant. 5113 Occasional issues with jpeg or PDF slide presentations being slow to start have been resolved. This used to occur if the slides were high resolution, or when using a policy server to supply personalized audio avatars. 5110 Pexip Infinity can now initiate an audio/video WebRTC call with Chrome 46 (currently in beta). 5109 A VMR synchronization template pattern that contains unicode no longer causes the sync of that template to fail. 5085 Output recorded in the support and administrator logs has been improved when reporting connectivity failures to LDAP / Active Directory when used for VMR synchronization. 5061 If an Infinity Connect client is presenting a slide, and then another Infinity Connect client starts presenting a slide (stealing the presentation), the Infinity Connect client that is now presenting now sees their own slide being presented in their own presentation control thumbnail. 5046 If an Infinity Connect Web App user calls a Virtual Reception and then enters the same Virtual Reception alias into the Extension field, rather than the alias of the required VMR, the Web App now presents a "Conference extension not found" message. 4980 The conference and participant history detail records now store the "Streaming or recording device" indicator. 4899 The Pexip outbound RDP encoder no longer experiences occasional transmission failures when sending consecutive slides of a presentation that contains very detailed visual images or graphs. 4840 All incoming unicode URIs are now properly matched against configured Pexip Distributed Gateway rules. 4793 If a VMR synchronization template pattern contains an incorrectly formatted filter expression, when the template is synced it now raises an appropriate administrator log error message and does not create the VMR. 2015 Pexip AS Version 10.2.a November 2015 Page 5 of 10

Issues fixed in v10 Microsoft 3744 Skype version 7.7.64.102 clients now send DTMF tones to federated environments, therefore they can now connect to PINprotected Pexip Infinity conferences. Radvision 5104 The H.245 TCS sent by Pexip to a Radvision MCU now signals the correct protocolidentifier for H.245 version 15 instead of version 14. Issues fixed in v10 Pexip 4621 When automatically deploying a new Conferencing Node, the progress bar on the Deploying Conferencing Node page will no longer stop at 96% for successful deployments. 4619 When dialing out to an RTMP URL, if the target of that RTMP URL is a CNAME record in lower case, and the target A records are in upper case (or vice versa), the lookup will now succeed. 4578 You can now restore a backup taken via the Pexip Infinity Administrator interface even if, since the backup file was produced, any Conferencing Nodes have been added or removed, or the Management Node has been redeployed. 4402 Conference Status no longer incorrectly reports the instant messaging count as 0, even when messages are exchanged in a conference. 4173 You can now change the name of a system location without any risk of a loss of service, and without having to reboot any Conferencing Nodes. 3665 The participant list displayed on both the Management Node and the Pexip Infinity Connect client now only shows a single participant instance for any Lync client connected when content is being shared. 2004 In very rare circumstances, a presentation that has been sent for a long period of time from a standards-based video endpoint may, at times, stall and thus prevent forwarding from one slide to another. If this happens the presentation image will now convert to grayscale. The presenter can then resolve this by disconnecting and re-connecting to the conference. Microsoft 4303 Plain text messages sent to Lync 2013 ios and Android clients will no longer trigger a 415 error code in response. 4018 Lync presence indications are now properly presented on Lync for ipad clients. (Note that avatars may not be presented correctly; this cannot be controlled.) 3689 If a RADVISION H.323 endpoint joins an AV-MCU conference through the Pexip Distributed Gateway, video will no longer be lost after a prolonged period of time. 2015 Pexip AS Version 10.2.a November 2015 Page 6 of 10

Issues fixed in v10 3374 Locking and unlocking spotlight of endpoints connected into the Microsoft AV-MCU via the Pexip Distributed Gateway no longer intermittently results in participants seeing the audio indicator instead of video. 3157 Participant status of an AV-MCU no longer improperly reflects an old call ID within the Administrator and Support logs on the Pexip Management Node. Cisco 4565 In a VMR conference, a presentation to a DX80 is no longer susceptible to failing after a few seconds. 4413 If an outbound call is initiated from Pexip to a VCS Expressway that does not inherently trust the remote Pexip node, and where the SIP TLS FQDN is configured on the Pexip Conferencing Node, the protocol is SIP TLS, and the endpoint registered to the VCS Expressway starts sharing content before someone else shares first, content will not be properly received by the Pexip Conferencing Node. This issue has been resolved in v10. Polycom 4620 When using older Polycom CMA or RealPresence Desktop clients, G.719 audio no longer causes audio issues with low bandwidths (512k and lower). 2015 Pexip AS Version 10.2.a November 2015 Page 7 of 10

Known limitations Known limitations Pexip 5078 The Management Node may not properly create a backup file if the system includes themes that are in excess of 2.5 GB of hard disk storage. To resolve the issue you must delete the oversized themes via the Administrator interface. 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. 4945 If an Infinity Connect participant is presenting, and another Infinity Connect participant starts and then quickly stops presenting, this can cause the initial presenter's screen to look like it is still presenting, but presentation is stopped on all participants. 4914 In some cases, in-band DTMF tones may not be detected if they are input too quickly. This is resolved through using out-of-band DTMF tones. 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. 4721 Gateway Routing Rules that are intended to route calls to devices registered to Pexip Infinity (e.g. Infinity Connect clients) could, depending upon DNS configuration, result in call looping if the destination device alias is not currently registered. For more information and to ensure proper routing of calls, see Avoiding call looping at http://docs.pexip.com/admin/registering_ devices.htm#looping. 4665 Incoming audio is not properly recognized on an incoming SIP call from SPIRENT ios clients. 4399 If a Lync client is receiving w448p main video resolution and participant names are enabled, the participant name for one of the participants connected into the conference will display unnecessarily small. 4312 Occasionally, group chat messages may not be displayed to Infinity Connect Web App participants who are using Internet Explorer. 2010 If during a single conference a new presentation stream is started but fails to connect, the last frame from the previous presenter may be visible to the participants of the conference. Cisco 4761 After upgrading to version 10, some MXPs may no longer be able to connect over TLS to Pexip Infinity, if the endpoint connects directly to a Conferencing Node (e.g. because it is registered to Infinity, or it using IP dialing). Please contact support@pexip.com if you experience this issue. 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. 2015 Pexip AS Version 10.2.a November 2015 Page 8 of 10

Known limitations 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. 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. 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. 4694 A presence subscription message from consumer Skype is not properly recognized as a Microsoft-specific 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. 4373 Outbound video calls made from the Lync 2010 client for ios may only connect using audio rather than automatically escalating to video as expected. 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 can be resolved by stopping and starting video again. 4262 If a Lync participant in an AV-MCU multi-party conference is presenting while another device joins the AV-MCU conference via the Pexip Distributed Gateway, the Lync presenter will see a "Someone has joined and can't see what's being presented or shared" notification. However, the gateway participant will be able to see the presentation. The notification will disappear after approximately 15 seconds. 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. 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. 3719 If a standards-based endpoint transmits a dual stream presentation at a very low resolution, the transcoded presentation will be sent in native resolution to any connected Lync clients. This may create a sub-optimal experience depending on the PC screen resolution of the Lync end-user PC. 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. The Lync 2013 client always uses VSR packets to negotiate the video mode even for RTVideo calls. However, Pexip Infinity assumes that Lync clients will always use video preference RTCP extensions to negotiate the RTVideo resolution and only looks for X-H264UC when processing VSRs. 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. 3798 Starting and stopping a presentation many times may stop a Polycom HDX endpoint from sending the presentation stream. 2015 Pexip AS Version 10.2.a November 2015 Page 9 of 10

Known limitations VMWare --- Disk access on ESXi 4.1 is typically considerably slower than on ESXi 5 and above. Tasks that require significant disk access, such as importing large conference configurations or writing many frequent log entries, may take over 5 times as long on ESXi 4.1 as compared to ESXi 5.1. 2015 Pexip AS Version 10.2.a November 2015 Page 10 of 10