Cisco Jabber Video for TelePresence 4.7 Release Notes

Transcription

1 First Published: October 29, 2013 Americas Headquarters Cisco Systems, Inc. 170 West Tasman Drive San Jose, CA USA Tel: NETS (6387) Fax:

2 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: 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) 2013 Cisco Systems, Inc. All rights reserved.

3 CONTENTS CHAPTER 1 Cisco Jabber Video for TelePresence 1 CHAPTER 2 Release and general information 3 CHAPTER 3 Important considerations 7 CHAPTER 4 Defects 11 Bug toolkit 11 Resolved defects 12 iii

4 Contents iv

5 CHAPTER 1 Cisco Jabber Video for TelePresence Cisco Jabber Video for TelePresence 4.7 is a maintenance release. These release notes describe feature and capability changes as well as issues resolved in Cisco Jabber Video for TelePresence since version 4.6. The following documents provide guidance on installation, initial configuration, and operation of the product: Cisco Jabber Video for TelePresence Administrator Guide Cisco Jabber Video for TelePresence User Guide for Windows Cisco Jabber Video for TelePresence User Guide for Mac OS X All Cisco Jabber Video for TelePresence documentation can be found at the following location: Changed in Release 4.7 Cisco Jabber Video for TelePresence 4.7 contains fixes to existing functionality. See Resolved defects for information on the fixes included in this release. Cisco Jabber Video for TelePresence 4.7 contains the following features: An updated audio sub-system. Stability and reliability improvements under heavy system loads. Support added for PCI-E cameras on Mac OS X. Important Cisco Jabber Video for TelePresence 4.7 supports Microsoft Windows 8 in classic desktop mode only. The Metro interface and Microsoft Windows 8 tablets are not supported. System Requirement Changes in Release 4.7 Cisco Jabber Video for TelePresence 4.7 makes the following changes to system requirements: Mac OS X 10.6 is no longer supported. The minimum required version is now Mac OS X 10.7 Mac OS X 10.9 is now supported. 1

6 Cisco Jabber Video for TelePresence The Mac OS X version of Cisco Jabber Video for TelePresence now requires a system with a 2GHz Core 2 Duo or better CPU. This was previously the recommended minimum. It is now the required minimum. Cisco Jabber Video for TelePresence 4.7 will be the last release to support Microsoft Windows XP and Microsoft Windows Vista. 2

7 CHAPTER 2 Release and general 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.7 from versions earlier than 4.3 The Cisco Jabber Video for TelePresence 4.7 installer will make some changes to previous installations due to changes in product name and brand in version 4.3. Users must manually remove the old application after installing and launching Cisco Jabber Video for TelePresence 4.7 on Mac OS X. Windows During installation: 3

8 Release and general information Cisco Jabber Video for TelePresence 4.7 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: If upgrading from version 4.1 or later, the existing profile folders and registry settings are renamed from ~\Cisco\Movi\2.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\2.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. Default file locations Files Program file Microsoft Windows location Microsoft Windows Vista and 7 (64 bit): %Program Files(x86)%\Cisco\ Microsoft Windows Vista and 7 (32 bit) : %Program Files%\Cisco\ Microsoft Windows XP: ~\Program Files\Cisco\ Mac OS X location /Applications/Jabber Video Favorites and History %APPDATA%\Cisco\JabberVideo\ ~/Library/Application Support/Jabber Video/ 4

9 Release and general information Files Log files for debugging purposes Microsoft Windows location <CSIDL_LOCAL_APPDATA>\Cisco\ JabberVideo\Logs\ The <CSIDL_LOCAL_APPDATA> directory is hidden by default and can be found at: Microsoft Windows XP: %USERPROFILE%\Local Settings\Application Data\ Micorsoft Windows Vista and Windows 7: %LOCALAPPDATA % (typically %USERPROFILE%\AppData\) Mac OS X location ~/Library/Logs/Jabber Video/ The Favorites and History are individual to each user logging on to Jabber Video on a Microsoft Windows computer. The Favorites and History are specific to the Mac OS X user account, regardless of which Jabber Video user is logged in on a Mac OS X computer. 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.3 is not possible. 5

10 Release and general information 6

11 CHAPTER 3 Important considerations Review the following important considerations when using Cisco Jabber Video for TelePresence. Description Workaround Users experience black incoming video connected to a This is due to the MXP VNC source being MXP system with a movable camera through H323 when selected when in a SIP-H323 call with the MXP attempting to use Far End Camera Control (FECC). using FECC control. Do not use FECC on a SIP-H323 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. Due to application-specific support for Windows APIs, Sharing the entire screen rather than the not all applications can be shared with Jabber Video at this application window works for most time. Platforms known to cause presentation sharing issues applications. in Jabber Video include Adobe AIR and GTK+. 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 3ivx codec(s). Uninstall the 3ivx 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. Create a new REG_DWORD registry key called MediaEnable in \HKLM\System\currentcontrolset\ services\csahook and set it to the value 0. 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 CSCtu24103). Mac OS X only: It is not possible to share full-screen PowerPoint presentations. 7

12 Important considerations Description Cisco Jabber Video for TelePresence cannot share full screen applications on Mac OS X. Cisco Jabber Video for TelePresence 4.2 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.2 and older. Some flicker may be present in the presentation view using Microsoft Internet Explorer 6 and 8 using Cisco Jabber Video for TelePresence 4.2 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. Cisco Jabber Video for TelePresence 4.2, 4.1, 4.0, and 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 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. Workaround 8

13 Important considerations Description 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. (CSCtz20509) Workaround Minimize all background applications before starting presentation sharing. Change Windows 7 performance settings to Adjust for best performance. 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 135W power supply with their computer if possible. Using the 90W power supply may cause performance degradation. Users upgrading from Cisco Jabber Video for TelePresence 4.2 to 4.3 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.2. (CSCue03995) Refer to thread/ for information on this issue. Generating DTMF tones using the keyboard in Cisco Jabber Video for TelePresence on Mac OS X duplicates the tones. Use the mouse. Cisco Jabber Video for TelePresence displays the error message: JabberVideo.exe: Entry Point not Found when placing or receiving calls. The message is caused by the Samsung Kies software. Samsung Kies installs the file avrt.dll in the folder %WINDIR%\System32. Renaming this file stops the message from appearing. 9

14 Important considerations Description 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. 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. Workaround 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. There are two workarounds to this issue: Disable encryption when placing a call. Initiate secure calls from the other endpoint. Performing either workaround will resolve the issue. 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. Disable TLS globally on the VCS where the endpoint is registered. 10

15 CHAPTER 4 Defects This section contains information on the defects for Cisco Jabber Video for TelePresence. Bug toolkit, page 11 Resolved defects, page 12 Bug toolkit Known problems (bugs) are graded according to severity level. These release notes contain descriptions of the following: All severity level 1 or 2 bugs Significant severity level 3 bugs All customer-found bugs except severity level 6 enhancement requests You can search for problems by using the Cisco Software Bug Toolkit. Before You Begin To access Bug Toolkit, you need the following items: Internet connection Web browser Cisco.com user ID and password Procedure Step 1 Step 2 Step 3 To access the Bug Toolkit, go to Log 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 Bug ID field, then click Go. 11

16 Resolved defects Defects What to Do Next For information about how to search for bugs, create saved searches, and create bug groups, click Help on the Bug Toolkit page. Resolved defects This section contains information on the defects resolved in this release. Identifier CSCuh57500 CSCue83678 CSCuh73158 CSCuf34508 CSCuh52513 CSCuh81078 CSCuj71312 CSCuj59974 CSCuj50047 CSCuj88210 Description Screen saver is activated during the call (Mac) Jabber Video not registering to VCS with lower priority in SRV record Documentation for support for Atom processors is inconsistent Jabber Video fails to send video from integrated Lenovo camera in a call No camera detected on OS X 10.9 No camera detected on Mid 2013 MacBook Air (shipped with OS X ) Wrong text string for built-in microphone on OS X No audio, neither incoming nor outgoing, after microphone mute on Windows 7 and later Low frame rate from Cisco cameras CSEQ out of order for multiway 12