 Feedback
|
Contents
- Release Notes for Cisco Virtualization Experience Media Engine Release 9.2(1)
- Release and general information
- Virtualization Experience Media Engine 9.2(1)
- System requirements
- Finding documentation
- New in this release
- Cisco Virtualization Experience Client 6215 copyright
- Virtualization Experience Media Engine copyright
- Installation and upgrade notes
- Important considerations
- Multiple Registrations
- Echo Cancellation
- Jabra Bluetooth audio devices
- Video resolution
- Camera hot swap
- Cameras and other applications
- USB 3.0 ports
- Caveats
- Using the Bug Toolkit
- Open caveats
- Resolved caveats
- Closed caveats
- Troubleshooting
- Problem report
- Create problem report
- Create problem report from Help menu
- Create problem report from Windows Start menu
- Lost call control after network failure
- Lost call after HVD disconnection
- No authentication prompt for registration
Release Notes for Cisco Virtualization Experience Media Engine Release 9.2(1)
Release and general information
These release notes describe new features, requirements, restrictions, and caveats for Cisco Virtualization Experience Media Engine Release 9.2(1). These release notes are updated for every maintenance release but not for patches or hot fixes.
Before you install Cisco Virtualization Experience Media Engine, we recommend that you review this document for information about issues that may affect your system.
Cisco Virtualization Experience Media Engine Release is an add-on for Cisco Virtualization Experience Client 6215.
Virtualization Experience Media Engine 9.2(1)
Cisco Virtualization Experience Media Engine (VXME) extends the Cisco Jabber collaboration experience to virtual deployments. With Cisco Jabber for Windows 9.1(1) or later, or Cisco UC Integration for Microsoft Lync 9.2(1) or later, users can send and receive phone calls on hosted virtual desktops (HVD). The VXME software detects the virtual environment and routes all audio and video streams directly from one thin client to another thin client or a telephone, without going through the HVD.
For more information about Cisco Jabber, see Release Notes for Cisco Jabber for Windows :
http://www.cisco.com/en/US/products/ps12511/prod_release_notes_list.html
For more information about Cisco UC Integration for Microsoft Lync, see Release Notes for Cisco UC Integration for Microsoft Lync :
http://www.cisco.com/en/US/products/ps11390/prod_release_notes_list.html
System requirements
Table 1 Requirements Component
Requirements
Virtual desktop thin client
Cisco VXC 6215 with Firmware Version 9.2(1)
Unified communications client on virtual environment
Cisco Jabber for Windows 9.1(4) or later; or Cisco UC Integration for Microsoft Lync 9.2(1) or later running on a Windows XP or Windows 7 hosted virtual desktop with
- Citrix XenDesktop 5.0, 5.5, or 5.6
- Citrix Xenapp 6.0, and 6.5 published desktops
- VMware View (PCoIP) 5.0, 5.1, or 5.2
Note Cisco Jabber desktop share, Jabber desk phone video (display of video on desktop when the thin client is tethered to the user's desk phone), recording and silent monitoring (contact center), and Cisco Unified Survivable Remote Site Telephony (SRST) are not supported with Cisco Virtualization Experience Media Engine.
Cisco Unified Communications Manager
Cisco Unified Communications Manager 7.1.5, 8.0, 8.5, 8.6, 9.0, or 9.1.
Accessories
High-definition video (720p at 30 fps) requires Logitech Webcam C920-C designed for Cisco.
Note High-definition video (720p at 30 fps) requires the Logitech Webcam C920-C designed for Cisco, which has built-in video processing capabilities. With a different camera, video output is limited to 360p maximum.
For a complete list of supported accessories, see : Cisco Virtualization Experience Client 6215 with VXME: Cisco Approved Audio and Video Accessories data sheet.
Finding documentation
Provide the following URL to your users:
http://www.cisco.com/go/6215_guide
You can place a shortcut on the Cisco Virtualization Experience Client 6215 desktop. You can also add the link to the Citrix landing page or to the VMware Horizon View pre-login banner. For more information, see Deployment Guide for Cisco Virtualization Experience Media Engine, located here:
http://www.cisco.com/en/US/products/ps12862/prod_installation_guides_list.html
For a complete list of related documents, see the Documentation Guide for Cisco Virtualization Experience Client 6215 located here:
http://www.cisco.com/en/US/products/ps11976/products_documentation_roadmaps_list.html
New in this release
Release 9.2(1)
- Supports Cisco Jabber for Windows Release 9.2(1).
- Supports Cisco UC Integration for Microsoft Lync Release 9.2(1). Cisco UC Integration for Microsoft Lync Release 9.2(2) features an integrated installer, which includes VXME Utilities.
- Supports Secure Real-time Transport Protocol (SRTP).
Attention:SRTP requires Cisco Jabber for Windows Release 9.2(2), or Cisco UC Integration for Microsoft Lync 9.2(2).
Installation and upgrade notes
Important:If you are upgrading from a prior release, first uninstall earlier versions of Cisco Jabber or Cisco UC Integration for Microsoft Lync from the hosted virtual desktop (HVD).
Supported upgrade paths include:
- Cisco Voice and Video Firmware Release 8.6 to Cisco Virtualization Experience Media Engine Release 9.2(1)
- Cisco Voice and Video Firmware Release 8.7 to Cisco Virtualization Experience Media Engine Release 9.2(1)
- Cisco Virtualization Experience Media Engine Release 9.0 to Cisco Virtualization Experience Media Engine Release 9.2(1)
Table 2 Overview of installation and deployment tasks Step Details 1
Build the Microsoft Windows desktop image.
- Log into the HVD as the new user with domain administration rights.
- Join the HVD to the corporate domain.
- Set up Citrix or VMWare.
- Install VXME Utilities on the Microsoft Windows desktop image.
- Install Cisco Jabber or Cisco UC Integration for Microsoft Lync on the Microsoft Windows desktop image. See the documentation for your release of Cisco Jabber for Windows: http://www.cisco.com/en/US/products/ps12511/prod_installation_guides_list.html Cisco UC Integration for Microsoft Lync: http://www.cisco.com/en/US/products/ps11390/tsd_products_support_series_home.html
- Create a snapshot of the image and clone it (for backup purposes).
2
Add users and devices on the Cisco Unified Communications Manager.
3
Cisco Jabber: Set up users on the Cisco Unified Communications Manager for Cisco Jabber Unified Communications features, such as Cisco Unified CM IM and Presence and WebEx integration.
Cisco UC Integration for Microsoft Lync: Microsoft Lync handles instant messages (IM) and Presence.
See the Server Setup Guide for your release of Cisco Jabber for Windows:
http://www.cisco.com/en/US/products/ps12511/prod_installation_guides_list.html
For more information about how to set up Microsoft Lync, see the product documentation. For information about Cisco UC Integration for Microsoft Lync, see the documentation for your release: http://www.cisco.com/en/US/products/ps11390/tsd_products_support_series_home.html
4
Ensure that users know how to access the user guides.
For information about how to set up links to the documentation, see Deployment Guide for Cisco Virtualization Experience Media Engine Release 9.0.
http://www.cisco.com/en/US/products/ps12862/prod_installation_guides_list.html
5
Set up the Cisco Virtualization Experience Client hardware and configure the device.
For links to software downloads, documentation roadmap, licensing information, and release notes, see:
http://www.cisco.com/en/US/products/ps11976/tsd_products_support_general_information.html
Quick Start Guide, VESA mount instructions, and regulatory information:
http://www.cisco.com/en/US/products/ps11976/prod_installation_guides_list.html
6
Install the Cisco Virtualization Experience Media Engine upgrade on the Cisco Virtualization Experience Client 6215.
See the Administration Guide for your release:
http://www.cisco.com/en/US/products/ps11976/prod_maintenance_guides_list.html
Note All software downloads include a Checksum folder, which contains SHA-1 checksums that you can use for verification.
7
Open the required ports in all firewalls.
See Ports Reference Guide for Cisco Virtualization Experience Media Engine Release 9.0.
http://www.cisco.com/en/US/products/ps12862/prod_installation_guides_list.html
Important considerations
Multiple Registrations
A CSF device user can register with the Communications Manager from only one client at a time. Multiple registrations from multiple clients with the same CSF device are not supported.
NoteWe recommend that you create only one CSF device for each user. If multiple devices exist for a virtual user, virtual Jabber automatically selects the first device in the list.
Jabra Bluetooth audio devices
All Jabra Bluetooth devices introduce a short delay in bringing up the audio path (about 1-3 seconds). With the latest firmware, the Jabra Speak 450 for Cisco does not have this issue. For other supported Jabra Bluetooth devices, such as Jabra Pro, you can eliminate the delay by changing the device settings in the Jabra PC Suite.
For more information, see User Guide for Cisco Virtualization Experience Client 6215 Release 9.0.
For more information about the Jabra PC Suite, visit: http://www.jabra.com/Support/jabra-PC-suite.
Video resolution
The following table lists the resolutions sent and received between end-points, depending on whether you use a high definition (HD) camera, or a standard definition (SD) camera.
Table 3 Video resolutions End-points
VXC to
Send/receive HD
Logitech Webcam C920-C
Send/receive SD
Cisco PHD camera
EX90
send 720p / receive 576p
send 360p / receive 512×288
CTS500-32 / TX9000 (Lago HW)
send 720p / receive 360p
send 360p / receive 352×240
CTS500-37 / CTS1300 (TenBears HW) Mode 0
send 576p / receive 360p
send 360p / receive 352×240
CTS500-37 / CTS1300 (TenBears HW) Mode 1
send 720p / receive 360p
send 360p / receive 352×240
JabberWin
send 720p / receive 1088×612
send 360p / receive 360p
VXC
send 576p / receive 576p
send / receive 360p
TP bridge
send / receive 720p
send 360p / receive 512×288
9971
send 360p / receive 640×480
send 360p / receive 352×288
894X
send 360p / receive 640×480
send 360p / receive 352×288 (15fps)
Cameras and other applications
To support use of the camera by other applications, such as Skype and Adobe Connect, Citrix 5.5 is required. With Citrix 4.0 or 5.0, only Cisco Virtualization Experience Client 6215 can use the camera.
VMWare does not support cameras on the hosted virtual desktop (HVD). Some cameras do work with VMware USB redirection, but VMware does not provide support for those that do not work.
USB 3.0 ports
The USB 3.0 ports on the Cisco Virtualization Experience Client do not support cameras, USB drives, or headsets. If a user plugs one of these devices into one of the USB 3.0 ports, a message appears to indicate that they must use one of the non-USB 3.0 ports. For the best user experience, advise users not to use USB 3.0 ports for cameras, USB drives, or headsets.Caveats
Using the Bug Toolkit
Known problems (bugs) are graded according to severity level. These release notes contain descriptions of the following:
Before you begin
You can search for problems by using the Cisco Software Bug Toolkit. To access the Toolkit, you need these items:
Procedure
- To access the Bug Toolkit, go to http://tools.cisco.com/Support/BugToolKit/action.do?hdnAction=searchBugs.
- Sign in with your Cisco.com user ID and password.
- Enter the ID number in the Search for Bug ID field, and click Go to look for information about a specific problem.
For more information about how to search for bugs, create saved searches, and create bug groups, click Help on the Bug Toolkit page.
Open caveats
The caveats in the following table describe possible unexpected behavior in the latest Cisco Virtualization Experience Media Engine release. These caveats may also be open in previous releases. This document includes only severity 1, 2, 3, and select severity 4 and 5 open caveats, as well as all customer-found defects. The table is sorted by severity, and then by identifier in alphanumeric order. Defect status is subject to change. For up-to-date information about a defect, search the Bug Toolkit for the bug Identifier or click the corresponding link for the bug in the following table.
Table 4 Open caveats for Cisco Virtualization Experience Media Engine Identifier Severity Component Headline CSCug58760 2 vxc CTI control not gained after first attempt at signing into CUCI. CSCuh06813 2 cpve [INT] Call drop on answer, Lost Call caps untill reboot of TC CSCuh30410 2 vxc [INT] HVD disconnecting with CUCILync in VMView 5.1 Only CSCuf21097 3 vmware VMWare View logging Virtual Channel Events, using up disk space CSCuf21832 3 vxc VXME doesnt always re-register after the HVD has lost/re-gained network CSCuf31518 3 device_switcher USB3 webcam does not work after switching from a USB2 webcam CSCuf32082 3 device_manager LifeCam, Precision HD & LogiC920 on USB 3.0 stop working after two calls CSCug46050 3 vxc Video stops when Hold on 9971, Resume in VXME Shared Line CSF device CSCug56943 3 cucilync SD Cameras - Video resolution changed after Hold/Resume the call CSCuh00984 3 vxc Picture in Picture missing on VXC to VXC Call (Intermittant 1:3) CSCuh05955 3 vxc No self view at VXME Jabber (non SRTP) calling 9971 CSCuh06605 3 integration_win [INT] Device Switcher not launching at times CSCuh06982 3 vxc Video res is only 288p when using a SD (MS LifeCam) camera on VMware CSCuh09414 3 vxc [INT] No self view on Jabber vxme to Jabber vxme call Resolved caveats
This section lists caveats that are resolved but that may have been open in previous releases.
The table lists bugs in order by severity, and then by identifier in alphanumeric order. Defect status is subject to change. For up-to-date information about a defect, search the Bug Toolkit for the bug Identifier.
Identifier Severity Component Headline CSCuf50318 2 cpve Localisation Of UC Keyboard Display Not Translating Text Closed caveats
The following table lists closed caveats. For more information about a defect, search the Bug Toolkit for the bug Identifier.
Identifier Severity Component Headline CSCuf51675 3 vxc SD/HD mode - Full screen video, audio at VXC is poor to a CTS500-37 CSCuf51708 3 vxc VXC Audio quality maybe impacted by high CPU in full screen video. Troubleshooting
Problem report
Problem reports include logs from the Cisco Virtualization Experience Client, hosted virtual desktop, and any detailed information that users enter. You can use this information to help troubleshoot the issue.
If users encounter a problem with Cisco Jabber or Cisco UC Integration for Microsoft Lync, they can create a problem report. If Cisco Jabber or Cisco UC Integration for Microsoft Lync encounters a problem and needs to close, the Client Error dialog starts automatically, so that the user can create a problem report. Users can also generate a problem report from the Windows Start menu, if Cisco Jabber or Cisco UC Integration for Microsoft Lync is not running.
TipAdvise users to include a memory dump if Cisco Jabber or Cisco UC Integration for Microsoft Lync crashes.
Create problem report
ProcedureIf Cisco Jabber or Cisco UC Integration for Microsoft Lync encounters a problem and needs to close, the problem reporting tool starts automatically.
Create problem report from Help menu
ProcedureIf you experience an issue with Cisco Jabber or Cisco UC Integration for Microsoft Lync, you can manually create a problem report from the Help menu.
Step 1 Click . Step 2 Choose a problem area, and then click Next. Step 3 Enter a short description of the problem, and then click Next. Step 4 (Optional) To include a memory dump file, check Include memory dump, and then click Attach File. Include a memory dump if Cisco Jabber, Cisco UC Integration for Microsoft Lync, or Device Selector crashes.
Step 5 In the Open dialog, select the memory dump file, and then click Open. Step 6 Click Save Report.
Note If your system administrator set up the feature, you can click Send Report to upload the problem report to a server. You do not need to save the file locally with this feature.
Step 7 In the Save As dialog, choose the location to which you want to save the problem report. Step 8 Send the file to your system administrator.
Create problem report from Windows Start menu
ProcedureIf you are not signed in to Cisco Jabber or Cisco UC Integration for Microsoft Lync, you can create a problem report from the Microsoft Windows Start menu.
Step 1 Click . For Cisco UC Integration for Microsoft Lync, click .
Step 2 Choose a problem area, and then click Next. Step 3 Enter a short description of the problem, and then click Next. Step 4 (Optional) To include a memory dump file, check Include memory dump, and then click Attach File. Include a memory dump if Cisco Jabber, Cisco UC Integration for Microsoft Lync, or Device Selector crashes.
Step 5 In the Open dialog, select the memory dump file, and then click Open. Step 6 Click Save Report.
Note If your system administrator set up the feature, you can click Send Report to upload the problem report to a server. You do not need to save the file locally with this feature.
Step 7 In the Save As dialog, choose the location to which you want to save the problem report. Step 8 Send the file to your system administrator.
Lost call control after network failure
Problem You see a prompt to reconnect to your hosted virtual desktop (HVD). After you reconnect, Cisco Jabber cannot control calls and your phone does not show as registered on the Logitech UC Keyboard.Lost call after HVD disconnection
Problem You receive a prompt to log back in to your hosted virtual desktop (HVD) during an active call, and the call drops. The other party to the call will have no indication that the call has ended, except the line will be silent.
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)
Copyright © 2013, Cisco Systems, Inc. All rights reserved.
