Cisco Virtualization Experience Media Engine

Cisco Virtualization Experience Media Engine
Cisco Virtualization Experience Media Engine
• Virtual Deployments, page 1
• Differences in the Virtual Environment, page 3
• Considerations for Virtual Environments, page 4
• Supported Codecs, page 5
Virtual Deployments
Note
In this deployment guide, the term thin client refers to repurposed PCs, or other supported client devices
set up to provide access to hosted virtual desktops (HVD).
With the Cisco Virtualization Experience Media Engine (VXME) for Windows software, users can place and
receive calls with their Cisco Unified Communications clients in a virtual environment. The Cisco Virtualization
Experience Media Engine software runs on the thin client, and the Cisco Unified Communications client and
Cisco VXME Utilities runs on the Microsoft Windows hosted virtual desktop (HVD), in the data center. To
reduce latency and to enhance media quality, Cisco Virtualization Experience Media Engine streams media
between the thin clients without going through the hosted virtual desktops.
Deployment Guide for Cisco Virtualization Experience Media Engine for Windows Release 10.5
1
Cisco Virtualization Experience Media Engine
Virtual Deployments
Use the following flowchart to determine whether you require VXME for your virtual environment.
Figure 1: Determine Whether You Need Cisco Virtualization Experience Media Engine for Windows
A Cisco Virtualization Experience Media Engine for Windows virtual deployment comprises the following
components:
• Supported desktop virtualization platforms (thin clients).
For more information about the minimum requirements for supported thin clients, see the Release Notes
for Cisco Virtualization Experience Media Engine for Windows for your release.
• Cisco Virtualization Experience Media Engine software, which is required to support audio and video
calls in the virtual environment.
Cisco Virtualization Experience Media Engine also provides support for some accessories. For more
information about supported accessories, see the Release Notes for Cisco Virtualization Experience
Media Engine for Windows for your release.
• Microsoft Windows hosted virtual desktops (HVD), in a data center.
For more information about supported Windows operating systems, see Release Notes for Cisco
Virtualization Experience Media Engine for Windows for your release.
• Supported Cisco Unified Communications clients with Cisco VXME Utilities, such as Cisco Jabber and
Cisco UC Integration for Microsoft Lync.
Note
For Cisco Jabber, you must install Cisco VXME Utilities, on the HVD, separately.
Cisco UC Integration for Microsoft Lync includes Cisco VXME Utilities, which is
installed automatically if the installer detects a virtual environment.
Deployment Guide for Cisco Virtualization Experience Media Engine for Windows Release 10.5
2
Cisco Virtualization Experience Media Engine
Differences in the Virtual Environment
The following image depicts an example deployment and illustrates traffic and protocol usage.
Figure 2: Example Cisco Virtualization Experience Media Engine for Windows Deployment
Differences in the Virtual Environment
The user experience with Cisco Virtualization Experience Media Engine and a supported Cisco Unified
Communications client in a virtual environment is very similar to the experience provided by a standard Cisco
Unified Communications client installation, with some differences:
• The Cisco Unified Communications client detects the virtual environment at run time and starts in
virtualization mode.
• Users can choose to control their Cisco IP Phone or to use their computer to make and receive calls. The
default phone selection is Use my computer for calls. After device selection, the Cisco Virtualization
Experience Media Engine application starts the transfer of the phone configuration data for that user.
For more information, see Configuration Files.
• Users manage their camera and audio devices by using the Device Selector, which is located in the
Windows notification area. Users can also use the following tabs to manage their camera and audio
devices from within their Cisco Unified Communications client:
◦File > Options > Audio
◦File > Options > Video
Note
With Cisco Jabber for Windows Release 10.5(1), the Advanced button that appears on
the Video tab is not present in the virtual environment. With Cisco Jabber for Windows
10.5(2) the Advanced button does appear on the Video tab in the virtual environment.
• If a connection failure between the thin client and the HVD occurs, the user is prompted to log back on
to the HVD. If the user has an active call, it is preserved. The user can end the call by using one of the
accessories, such as the keyboard. If the user does not have an accessory with which to end the call, the
Deployment Guide for Cisco Virtualization Experience Media Engine for Windows Release 10.5
3
Cisco Virtualization Experience Media Engine
Considerations for Virtual Environments
user can ask the other party to end the call. If there are held calls when the connection failure occurs,
the parties on hold receive no notification of the connection failure. After logging back on to the HVD,
the user can send an instant message (IM) to the parties that were left on hold.
• If the thin client loses the connection to the network, the user is prompted to log back on to the HVD.
If the connection failure occurs during a call, the call is lost. After reconnecting, the user can try to call
the other party or send an IM. For the other party on the call, silence is the only indication that the call
has dropped.
• By default, all calls send and receive video if both parties have video capability. Users can select their
preference from the following options:
◦Always start calls with video: Starts all calls as video calls, which send local video
◦Never start calls with video: Starts all calls as audio-only calls
This setting applies to all calls that the user places and receives. The default setting is Always start calls
with video. Users can change this setting in File > Options > Calls.
Note
You can disable video globally or on a per-device basis on the Cisco Unified
Communications Manager. Navigate to System > Enterprise Phone Configuration
and set Video Calling to Disabled.
• Some menus and options for the supported Cisco Unified Communications clients are different. For
example, users cannot initiate Video Desktop Share from the call window. Video Desktop Share is
supported only from the chat window.
Important
If Cisco Jabber or Cisco UC Integration for Microsoft Lync is also installed on the thin client, ensure that
users exit the software client before they sign in to their HVDs. If Cisco Jabber or Cisco UC Integration
for Microsoft Lync is running on the local desktop, and the user subsequently tries to sign in to another
instance of the software client on their HVD, Cisco VXME cannot register and problems with accessories
can occur.
Considerations for Virtual Environments
In a virtual environment, you install Cisco Virtualization Experience Media Engine for Windows on a supported
desktop virtualization platform. You install a supported Cisco Unified Communications client on the hosted
virtual desktops (HVD), rather than on client computers (PCs). If your Cisco Unified Communications client
does not include Cisco VXME Utilities, you must install that first. Otherwise, the installation is the same as
the installation of the Cisco Unified Communications client in a nonvirtual environment.
When you add devices for virtual users to the Cisco Unified Communications Manager, the device type is
Cisco Unified Client Services Framework (CSF). Each user should have only one CSF device. If multiple
CSF devices exist for a user, Cisco Virtualization Experience Media Engine selects the first device in the
alphabetical list. To prevent issues caused by multiple registrations for the same user on the Cisco Unified
Communications Manager, advise users to sign in to only one HVD or client at a time. A CSF device user
can register with the Unified Communications Manager from only one client at a time. Multiple registrations
from multiple clients with the same CSF device are not supported.
Deployment Guide for Cisco Virtualization Experience Media Engine for Windows Release 10.5
4
Cisco Virtualization Experience Media Engine
Supported Codecs
You must also enable the computer-telephony integration (CTI) protocol for all virtual Cisco Unified
Communications client users.
Tip
Before you begin to install the Cisco Unified Communications client on the HVD, see the Release Notes
for Cisco Virtualization Experience Media Engine for Windows for your release and for the Cisco Unified
Communications client.
Supported Codecs
Supported Audio Codecs
• G.722
• G.722.1
• G.722.1 32k
• G.722.1 24k
Note
G.722.1 is supported on Cisco Unified Communications Manager 8.6.1 or later.
• G.711
• G.711 A-law
• G.711 u-law
• G.729a
Supported Video Codecs
• H.264/AVC
Deployment Guide for Cisco Virtualization Experience Media Engine for Windows Release 10.5
5
Cisco Virtualization Experience Media Engine
Supported Codecs
Deployment Guide for Cisco Virtualization Experience Media Engine for Windows Release 10.5
6
Was this manual useful for you? yes no
Thank you for your participation!

* Your assessment is very important for improving the work of artificial intelligence, which forms the content of this project

Download PDF

advertising