Cisco Jabber Video for TelePresence 4.8 Release Notes

Cisco Jabber Video for TelePresence 4.8 Release Notes Introduction New and Changed Features Requirements Upgrade Information 5 Limitations and Restrictions 6 Caveats 10

Revised: May 7, 015, Introduction These release notes describe feature and capability changes as well as issues resolved in Cisco Jabber Video for TelePresence. The current version of the application is Release 4.8(11). Product Overview Cisco Jabber Video for TelePresence (Jabber Video) is an application that extends the reach of telepresence. Jabber Video works with a compatible PC or Mac and a webcam or Cisco TelePresence PrecisionHD camera to provide high-definition video communications to more people, on more devices, from more places. Jabber Video can connect to telepresence systems, resulting in a wider community of colleagues, partners, and business customers. Product Documentation The following documents are available for Cisco Jabber Video for TelePresence 4.8: Administrator Guide The Administrator Guide provides information on installation, initial configuration, and operation of the client. User Guide for Windows The User Guide provides task-based information about end user operation of the client on the Windows operating system. User Guide for Mac OS X The User Guide provides task-based information about end user operation of the client on the Mac operating system. To view documentation, see the Cisco Jabber Video for TelePresence documentation home page. New and Changed Features Release 4.8(11) Cisco Jabber Video for TelePresence 4.8(11) contains fixes to existing functionality. For information about the fixes included in this release, see: Resolved Caveats, on page 11. Release 4.8(8) Cisco Jabber Video for TelePresence 4.8(8) contains fixes to existing functionality. For information about the fixes included in this release, see: Resolved Caveats, on page 11. This release updates CiscoSSL from 4. to CiscoSSL 4.4 to address vulnerabilities in the OpenSSL library. Release 4.8(6) Cisco Jabber Video for TelePresence 4.8(6) contains fixes to existing functionality. For information about the fixes included in this release, see: Resolved Caveats, on page 11. This release updates CiscoSSL from 4. with FOM 4.1 to CiscoSSL 4. with FOM 4.1 to address the HeartBleed vulnerability in the OpenSSL library.

Release 4.8 Cisco Jabber Video for TelePresence 4.8 contains fixes to existing functionality. For information about the fixes included in this release, see: Resolved Caveats, on page 11. Cisco Jabber Video for TelePresence 4.8 contains the following features: A new provisioning setting (Support AES-56 in SRTP) to specify whether Jabber Video supports AES-56 in SRTP The protocol handler setting once again supports the "movi:" protocol as an alternative to "sip:". Specify "movi:" to ensure that Jabber Video is always used even if another SIP client is the system default. Important Cisco Jabber Video for TelePresence 4.8 supports Microsoft Windows 8.x in classic desktop mode only. The Metro interface and Microsoft Windows 8.x tablets are not supported. Requirements Infrastructure requirements Jabber Video requires the Provisioning option on the Cisco VCS and in Cisco TMS to be enabled. Product Cisco TelePresence Management Suite (Cisco TMS) Cisco Video Communication Server (Cisco VCS) Version required 1.6 or later X5. or later X6.0 or later for ICE support X6.1 or later for NTLM support NTLM authentication client requirements Jabber Video supports authentication with Active Directory and NTLM. For instructions on deploying NTLM authentication with Jabber Video and Cisco VCS, refer to Cisco TelePresence Video Communication Server Authenticating Devices Deployment Guide (http://www.cisco.com/en/us/products/ps117/products_installation_and_configuration_guides_list.html). Note that to use NTLM authentication with Jabber Video and Cisco VCS, NTLMv must be supported by the client computer. It is especially important to be aware of this requirement if there are older computers in your network. On the client computer: 1 Go to My Computer\HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Lsa. If the LmCompatibilityLevel setting (REG_DWORD) is 1, set to or higher. Save your changes.

Caution With a setting of 1, authentication will fail for the client, and no warnings or error messages will be received from Cisco VCS, which passes the request on to the Active Directory server. PC requirements Operating System Windows 7 Windows 8.x Processor Memory GHz Intel Core Duo or equivalent. Windows 8.x or Windows 7 -bit: 1 GB RAM or more. Windows 8.x or Windows 7 64-bit: GB RAM or more Graphics card Sound card OpenGL version 1., or OpenGL version 1. with the multitexturing extension. Any standard sound card (full-duplex, 16-bit or better). Note On computers with limited processing power and/or memory, Jabber Video will use a lot of system resources, and reduced performance can be expected. On Windows 8.x, only the classic Desktop user interface is supported. Mac OS X requirements Operating System Mac OS X 10.9 Mac OS X 10.8 Mac OS X 10.7 Processor GHz Intel Core Duo or equivalent. Multimedia device requirements Microphone All microphones work well with Jabber Video. Note that some cameras have built-in microphones. 4

Camera Jabber Video works with most common web cameras. See the Cisco Knowledge Base for updated information on Jabber Video and cameras (http://www.cisco.com/en/us/docs/telepresence/endpoint/articles/cisco_telepresence_movi_tested_cameras_kb_77.shtml). Note Cisco recommends using the Cisco PrecisionHD USB camera for business-quality HD video. Upgrade Information Upgrading The process of upgrading Cisco Jabber Video for TelePresence is controlled by the IT administrator through four provisioning options in Cisco TelePresence Management Suite: Windows Software URL OS X Software URL Windows Software Version OS X Software Version The provisioned URL must be an open (non-authenticated) http address. Automatic upgrade over ftp or https is not supported. Cisco recommends that the administrator immediately test and verify that the provisioned URLs work and are available to all provisioned users on the network. When these two options are correctly configured, users will receive a prompt when they sign in asking them whether they want to upgrade immediately: If the user accepts, the new installer will be downloaded and started automatically. Restarting the computer after installation is not necessary. If the user accepts, but the download is not available for example because the user is connecting from outside the company network, the user will be notified of the failure and the prompt will return the next time the user signs in. If the user clicks Ask Later, the prompt will return the next time the user signs in Use the deployment tools to force the upgrade to ensure the client is upgraded even without user intervention. If you want to make absolutely sure that all clients are upgraded, you can instead opt to use your deployment Upgrading to Cisco Jabber Video for TelePresence 4.8 from versions earlier than 4. The Cisco Jabber Video for TelePresence 4.8 installer will make some changes to previous installations due to changes in product name and brand in version 4.. Users must manually remove the old application after installing and launching Cisco Jabber Video for TelePresence 4.8 on Mac OS X. Windows During installation: Cisco Jabber Video for TelePresence 4.8 installs itself to the program file paths described below. Cisco Jabber Video for TelePresence registers itself as the default SIP protocol handler. When Cisco Jabber Video for TelePresence is launched: 5

If upgrading from version 4.1 or later, the existing profile folders and registry settings are renamed from ~\Cisco\Movi\.0\~ to ~\Cisco\JabberVideo\~. If upgrading from a version older than 4.1, the existing profile folders and registry settings are renamed from ~\TANDBERG\Movi\.0\~ to ~\Cisco\JabberVideo\~. Mac OS X Install and start up Cisco Jabber Video for TelePresence before removing Movi. Settings are imported on first startup. During installation: Cisco Jabber Video for TelePresence installs itself as a new application alongside Cisco TelePresence Movi. Cisco Jabber Video for TelePresence registers itself as the default SIP protocol handler. The program bundle identifier is now com.cisco.jabbervideo. When Cisco Jabber Video for TelePresence is launched: Preferences, Favorites, and History are imported from Movi. Stored passwords are not imported and must be re-entered. Downgrading The provisioning options for software URL and version also make it possible to provision a downgrade, taking users to an earlier version of Cisco Jabber Video for TelePresence. The downgrade process is similar to the upgrade process. When downgrading to an earlier version, the user's Favorites, History, and settings are kept intact. Logs and log settings are deleted. Note A complete downgrade to versions earlier than 4. is not possible. Limitations and Restrictions Review the following important considerations when using Cisco Jabber Video for TelePresence. Description Users upgrading from Release 4.7 or older to Release 4.8 or newer must enter their password even if the Remember me option is selected and the password is automatically filled in when the new version is first run. Users who have selected the Sign in automatically option will fail on their first login attempt. Users must enter their password and login manually. Workaround Users experience black incoming video connected to a MXP system with a movable camera through H when attempting to use Far End Camera Control (FECC). This is due to the MXP VNC source being selected when in a SIP-H call with the MXP using FECC control. Do not use FECC on a SIP-H call if you experience black video. The MXP side must manually select the main camera to be able to transmit video. Dial the MXP using SIP. 6

Description Due to application-specific support for Windows APIs, not all applications can be shared with Jabber Video at this time. Platforms known to cause presentation sharing issues in Jabber Video include Adobe AIR and GTK+. Workaround Sharing the entire screen rather than the application window works for most applications. Cisco Jabber Video for TelePresence may not function properly after upgrading to a new Mac OS X version. Problem reports indicate a QuickTime failure and lists ivx codec(s). Uninstall the ivx codec(s) or upgrade to a version that supports the new Mac OS X version. Users of the Cisco Security Agent (CSA) may encounter an issue where Cisco Jabber Video for TelePresence freezes during camera selection or call setup. No applications will then be able access audio devices, and the computer must be restarted for audio functionality to resume. The issue only affects users with a USB microphone or USB camera that includes a microphone. The issue is also most likely to arise under low battery conditions (Cisco Security Agent issue identifier CSCtu410). Create a new REG_DWORD registry key called MediaEnable in \HKLM\System\currentcontrolset\services\csahook and set it to the value 0. Mac OS X only: It is not possible to share full-screen PowerPoint presentations. Cisco Jabber Video for TelePresence cannot share full screen applications on Mac OS X. Cisco Jabber Video for TelePresence 4. and earlier cannot use the Mac OS X Command-tab (application switcher) or Command-Q (close application) with the presentation sharing feature. It is not possible to share an application from a different Mac OS X Space. It is only possible to share applications that are in the same Space as Cisco Jabber Video for TelePresence. It is not possible to move an application to another Space while sharing it during a call. This can cause Cisco Jabber Video for TelePresence to stop sharing of the application. If another application partially covers the Citrix window shared on a Microsoft Windows computer, Cisco Jabber Video for TelePresence being shared, will share that part of the application as well. This affects Release 4. and later. 7

Description Some flicker may be present in the presentation view using Microsoft Internet Explorer 6 and 8 using Cisco Jabber Video for TelePresence 4. and older. This flicker is seen on the receiving end and the PiP (picture-in-picture) on the sending end as well. This flicker may also be experienced occasionally in other applications such as Microsoft Excel and Notepad. The cause cannot be reproduced on all computers. It may be experienced on some computers and not others. Workaround Cisco Jabber Video for TelePresence 4., 4.1, 4.0, and.1.1 cannot shared a Microsoft PowerPoint presentation with embedded video. Customers may experience a loss of embedded pictures when sharing from Microsoft Word or Microsoft PowerPoint 00. This affects Cisco Jabber Video for TelePresence 4.1 and 4.0. The presentation sharing feature may not function correctly due to packet loss when using WiFi networks. This affects all versions of Cisco Jabber Video for TelePresence. Users may experience an issue where the last used application is brought to the front when the user clicks on the shared presentation. This does not cause Cisco Jabber Video for TelePresence to functional incorrectly, it only forces the user to move back to the application they were using previously. This issue is encountered on Microsoft Windows 7. (CSCtz0509) Users may experience an issue in Cisco Jabber Video for TelePresence to Cisco Jabber Video for TelePresence calls using desktop sharing where some text in a shared presentation using small fonts may be difficult to read due to lack of clarity. Lenovo W510 owners who use Cisco Jabber Video for TelePresence should use the larger 15W power supply with their computer if possible. Using the 90W power supply may cause performance degradation. Minimize all background applications before starting presentation sharing. Change Windows 7 performance settings to Adjust for best performance. Users upgrading from Cisco Jabber Video for TelePresence 4. to 4. or later may receive an error message asking them to restart their computer or reinstall the application. This error message is related to the graphics drivers on the user's computer. This error message indicates the user should upgrade their graphics drivers or downgrade to Release 4.. (CSCue0995) Refer to https://supportforums.cisco.com/discussion/114596/ jabber-fails-start for information on this issue. 8

Description Generating DTMF tones using the keyboard in Cisco Jabber Video for TelePresence on Mac OS X duplicates the tones. Cisco Jabber Video for TelePresence displays the error message: JabberVideo.exe: Entry Point not Found when placing or receiving calls. Workaround Use the mouse. The message is caused by the Samsung Kies software. Samsung Kies installs the file avrt.dll in the folder %WINDIR%\System. Renaming this file stops the message from appearing. Cisco Jabber Video for TelePresence users on Microsoft Windows may experience unclear audio or audio with static noise. This happens even under favorable network conditions. Some sound drivers have their own set of audio enhancements that can conflict with the built-in functionality of Cisco Jabber Video for TelePresence. The most notable of these features is the Acoustic Echo Canceller. This does not apply to all driver-based enhancements. It is only in combination with certain hardware that these enhancements causes issues. If you experience this problem, disable the driver's enhancements. Select Control Panel > Hardware and Sound > Manage audio devices > Recording. Select the microphone and select Properties. Go to the Enhancement tab and check Disable all sound effects. Note that for some driver and hardware combinations, it may be enough to only disable the Acoustic Echo Canceller by unchecking it in the list of individual enhancements. An issue has been discovered during enhancements to the secure calling capabilities of Cisco Jabber Video for TelePresence. The application may not properly decrypt calls sent to some endpoints. Cisco suggests opening a technical support case with the endpoint vendor if you encounter this issue. There are three workarounds to this issue: Provision users with Support AES-56 in SRTP set to Off. Disable encryption when placing a call. Initiate secure calls from the other endpoint. Cisco Jabber Video for TelePresence may have issues sharing BFCP content when dialing into a Polycom RMX bridge with TLS enabled on the VCS. This issue is not present when TLS is disabled. Performing any of the above workarounds will resolve the issue. Disable TLS globally on the VCS where the endpoint is registered. Cisco Jabber Video for TelePresence may stop functioning when switching from one graphics card to another. The following error message is displayed: Graphics card not supported! New features in this version of Jabber Video are not supported by your computer's graphic driver. Update to the newest graphics driver available and run Jabber Video for TelePresence again. If the upgrade fails, disable the second graphics card and run Jabber Video for TelePresence again. 9

Caveats This section contains information on the caveats for Cisco Jabber Video for TelePresence. Bug Search Tool, on page 10 Open Caveats, on page 10 Resolved Caveats, on page 11 Bug Search Tool Known problems (bugs) are graded according to severity level. These release notes contain descriptions of the following: All severity level 1 or bugs Significant severity level bugs All customer-found bugs except severity level 6 enhancement requests You can search for problems by using the Cisco Software Bug Search Tool. Before You Begin To access Bug Search Tool, you need the following items: Internet connection Web browser Cisco.com user ID and password Procedure Step 1 Step Step To access the Bug Search Tool, go to https://tools.cisco.com/bugsearch/search. Sign in with your Cisco.com user ID and password. To look for information about a specific problem, enter the bug ID number in the Search for field, then press Enter. What to Do Next For information about how to use the Bug Search Tool, select Help on the Bug Search Tool screen. Open Caveats The following caveats were open at time of shipping. Table 1: Open Caveats in Cisco Jabber Video for TelePresence 4.8(11) Identifier CSCut549 Movi 4.8 client disconnects after 40-50 mins 10

Identifier CSCus875 CSCut00 CSCut6940 CSCuu0454 No audio or destroyed for the 1st call after system reboot using MOVI Movi 4.8.8 not compatible with AMD FirePro W4170M Jabber Video delegated credential checking fails with local users More than 50 contact in favorites show wrong status The following caveats were open at time of shipping. Table : Open Caveats in Cisco Jabber Video for TelePresence 4.8 Identifier CSCtu71670 CSCuj08784 CSCul507 CSCul7088 CSCum40474 CSCum76860 CSCum78889 CSCun6775 CSCue558 CSCug64596 CSCty8980 4 4 6 Application sharing issues VCS<->CUCM interworking: Video starts after 1 minute Multiway: Fails on refer after challenges from VCS ICE functions improperly when any m= line is zero in SIP SDP OS X 10.7.5: Not sending any video, crashing when loading Video preferences Jabber Video 4.7 minimum media port range seems to be 11, not 10. PrecisionHD USB Camera LED issue Calls from Movi hangs after a few seconds Called device still rings even if caller hung up, SIP 481 Black screen when calling MPS with at least participants SIP display name not used Resolved Caveats Table : Resolved Caveats in Cisco Jabber Video for TelePresence 4.8(11) Identifier CSCus55191 CSCup04761 CSCup416 CSCuq5656 CSCus1419 CSCus4871 Echo cancellation not working Movi can't stop sharing main video presentation Multiple Vulnerabilities in OpenSSL - June 014 August 6, 014 OpenSSL Vulnerabilities Oct 014 OpenSSL Vulnerabilities JANUARY 015 OpenSSL Vulnerabilities 11

Identifier CSCut45966 CSCus08199 CSCup154 CSCur984 CSCuo94065 CSCus98615 CSCup1857 4 MARCH 015 OpenSSL Vulnerabilities Movi 4. & 4.8 video frozen after desktop share No media until ICE fails Jabber accepting blank password after one use of password Jabber for TP does not allow TCP registration Crash while Quick Setup window is opened and web cam is connected Jabber Video 4.8 lets Windows apply Power settings during active call Table 4: Resolved Caveats in Cisco Jabber Video for TelePresence 4.8(8) Identifier CSCup416 CSCuo76479 Multiple Vulnerabilities in OpenSSL - June 014 Jabber 4.8 Crashes on Launch with UseWindowsUsername=1 The following severity 1,, and caveats were present in at least one previous release and are resolved in this release. Resolved minor caveats are not listed here. Table 5: Resolved Caveats in Cisco Jabber Video for TelePresence 4.8(6) Identifier CSCuo8855 CSCuo11104 Cisco Jabber Video for TelePresence (Movi) vulnerable to CVE-014-0160 May only respond to first PLI/FIR and ignore subsequent requests The following severity 1,, and caveats were present in at least one previous release and are resolved in this release. Resolved minor caveats are not listed here. Table 6: Resolved Caveats in Cisco Jabber Video for TelePresence 4.8 Identifier CSCuh08911 CSCul1667 CSCum55 CSCum4556/CSCul5911 CSCud1795 CSCuh5761 Encrypt login password in memory Unencrypted SIP registration fails Multiple rtpmap lines per dynamic payload type Crash on startup or after hibernation Call drops during re-registration across traversal zone Wireless headsets don't work on Windows 8 (Jabra and Plantronics) 1

Identifier CSCuj99914 CSCul161 CSCul058 CSCul4746 CSCul47476 CSCum0406 CSCum70564 CSCum8087 CSCun47996 CSCug1650 6 SIP message Call-Info decode failure Allow leading and trailing spaces in passwords (Windows) Flux crash Vulnerability fixes for PNG Development Group libpng Vulnerability fixes for XMLSoft libxml Crash when bringing up or tearing down an AnyConnect VPN link Do not launch the application on startup by default Make AES-56 usage in SRTP provisionable. Vulnerability fixes for OpenSSL Reinstate the "movi:" protocol handler Closed Caveats This section contains information on the caveats closed in this release. Table 7: Closed Caveats in Cisco Jabber Video for TelePresence 4.8(11) Identifier CSCtu71670 CSCuj08784 CSCul507 CSCul7088 CSCum40474 CSCum76860 CSCum78889 CSCun6775 CSCue558 CSCug64596 CSCty8980 4 4 6 Application sharing issues VCS<->CUCM interworking: Video starts after 1 minute Multiway: Fails on refer after challenges from VCS ICE functions improperly when any m= line is zero in SIP SDP OS X 10.7.5: Not sending any video, crashing when loading Video preferences Jabber Video 4.7 minimum media port range seems to be 11, not 10. PrecisionHD USB Camera LED issue Calls from Movi hangs after a few seconds Called device still rings even if caller hung up, SIP 481 Black screen when calling MPS with at least participants SIP display name not used 1

THE SPECIFICATIONS AND INFORMATION REGARDING THE PRODUCTS IN THIS MANUAL ARE SUBJECT TO CHANGE WITHOUT NOTICE. ALL STATEMENTS, INFORMATION, AND RECOMMENDATIONS IN THIS MANUAL ARE BELIEVED TO BE ACCURATE BUT ARE PRESENTED WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED. USERS MUST TAKE FULL RESPONSIBILITY FOR THEIR APPLICATION OF ANY PRODUCTS. THE SOFTWARE LICENSE AND LIMITED WARRANTY FOR THE ACCOMPANYING PRODUCT ARE SET FORTH IN THE INFORMATION PACKET THAT SHIPPED WITH THE PRODUCT AND ARE INCORPORATED HEREIN BY THIS REFERENCE. IF YOU ARE UNABLE TO LOCATE THE SOFTWARE LICENSE OR LIMITED WARRANTY, CONTACT YOUR CISCO REPRESENTATIVE FOR A COPY. The Cisco implementation of TCP header compression is an adaptation of a program developed by the University of California, Berkeley (UCB) as part of UCB's public domain version of the UNIX operating system. All rights reserved. Copyright 1981, Regents of the University of California. NOTWITHSTANDING ANY OTHER WARRANTY HEREIN, ALL DOCUMENT FILES AND SOFTWARE OF THESE SUPPLIERS ARE PROVIDED AS IS" WITH ALL FAULTS. CISCO AND THE ABOVE-NAMED SUPPLIERS DISCLAIM ALL WARRANTIES, EXPRESSED OR IMPLIED, INCLUDING, WITHOUT LIMITATION, THOSE OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT OR ARISING FROM A COURSE OF DEALING, USAGE, OR TRADE PRACTICE. IN NO EVENT SHALL CISCO OR ITS SUPPLIERS BE LIABLE FOR ANY INDIRECT, SPECIAL, CONSEQUENTIAL, OR INCIDENTAL DAMAGES, INCLUDING, WITHOUT LIMITATION, LOST PROFITS OR LOSS OR DAMAGE TO DATA ARISING OUT OF THE USE OR INABILITY TO USE THIS MANUAL, EVEN IF CISCO OR ITS SUPPLIERS HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. Any Internet Protocol (IP) addresses and phone numbers used in this document are not intended to be actual addresses and phone numbers. Any examples, command display output, network topology diagrams, and other figures included in the document are shown for illustrative purposes only. Any use of actual IP addresses or phone numbers in illustrative content is unintentional and coincidental. Cisco and the Cisco logo are trademarks or registered trademarks of Cisco and/or its affiliates in the U.S. and other countries. To view a list of Cisco trademarks, go to this URL: http:// www.cisco.com/go/trademarks. Third-party trademarks mentioned are the property of their respective owners. The use of the word partner does not imply a partnership relationship between Cisco and any other company. (1110R) 015 Cisco Systems, Inc. All rights reserved.

Americas Headquarters Cisco Systems, Inc. San Jose, CA 9514-1706 USA Asia Pacific Headquarters Cisco Systems (USA) Pte. Ltd. Singapore Europe Headquarters Cisco Systems International BV Amsterdam, The Netherlands Cisco has more than 00 offices worldwide. Addresses, phone numbers, and fax numbers are listed on the Cisco Website at www.cisco.com/go/offices.