Cisco Virtualization Experience Media Engine Overview
Purpose of This Guide
The Cisco Virtualization Experience Media Engine for SUSE Linux Deployment and Installation Guide
includes the following task-based information required to deploy
Cisco Virtualization Experience Media Engine for SUSE Linux (VXME for SUSE Linux).
Installation and configuration workflows and procedures that outline the processes
and configure Cisco VXME for SUSE Linux
Installation and configuration information for Cisco AnyConnect Secure Mobility Client in a Cisco VXME for SUSE Linux deployment
Upgrade information for Cisco VXME for SUSE Linux
About Cisco Virtualization Experience Media Engine
Cisco Virtualization Experience Media Engine (VXME) extends the Cisco collaboration experience to virtual deployments. With a supported version of Cisco Jabber for Windows, users can send and receive phone calls on their hosted virtual desktops (HVD). The VXME software detects the virtual environment and routes all audio and video streams directly from one endpoint to another, without going through the HVD.
The applications in the
family of products are:
Cisco Virtualization Experience Media Engine for SUSE Linux
Cisco Virtualization Experience Media Engine for Windows
With Cisco Virtualization Experience Media Engine (VXME), thin client users can place
and receive calls with their Cisco Unified Communications application (Cisco Jabber).
Cisco Virtualization Experience Media Engine consists of the Cisco VXME Agent and the Cisco VXME Client. To reduce latency and to enhance media quality, VXME streams media between the endpoints
without going through the hosted virtual desktops.
Figure 1. Determine Whether You Need Cisco Virtualization Experience Media Engine for SUSE Linux. Use the following flowchart to determine whether you require VXME for your virtual environment.
Cisco VXME virtual deployment consists of the following components:
Supported SUSE Linux thin clients
information about supported thin clients, see
Notes for Cisco Virtualization Experience Media Engine for SUSE Linux.
Cisco VXME Client installed on the thin client
virtual desktops (HVD), in a data center
Cisco Jabber installed on the HVD
Cisco VXME Agent installed on the HVD
Cisco Unified Communications Manager
Differences in the Virtual Environment
The user experience with Cisco Virtualization Experience Media Engine and a supported Cisco Unified Communications client is similar to the experience provided by a standard Cisco Unified Communications client installation. However, in a virtual environment there are 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 Phones or to use their computers 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 can 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
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.
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 start Video Desktop Share (Binary Floor Control Protocol) from the call window. Video Desktop Share is supported only from the IM-chat window (Remote Desktop Protocol).
The following table lists the file types and names for this release.
Cisco Virtualization Experience Media Engine Client for SUSE Linux SP2 (downloadable .zip file)
SP2 VXME.rpm file (extracted from zip file)
SP2 VXME Prerequisites.rpm file (extracted from zip file)
Cisco Virtualization Experience Media Engine Client for SUSE Linux SP3 (downloadable .zip file)
SP3 VXME Client.rpm file (extracted from zip file)
SP3 VXME Prerequisites.rpm file (extracted from zip file)
Cisco Virtualization Experience Media Engine Agent for SUSE Linux Release 11.0 (downloadable zip file)
Cisco VXME Agent installer file (extracted from zip file)
Cisco AnyConnect for SUSE Linux SP2 (downloadable zip file)
SP2 Cisco AnyConnect.rpm file (extracted from zip file)
Cisco AnyConnect for SUSE Linux SP3 (downloadable zip file)
SP3 Cisco AnyConnect.rpm file (extracted from zip file)
Cisco AnyConnect Feature Support
Cisco Virtualization Experience Media Engine supports Cisco AnyConnect Secure Mobility Client, Release 3.1. The Cisco AnyConnect Secure Mobility client provides remote users with secure VPN connections to the Cisco 5500 Series Adaptive Security Appliance (ASA). Cisco AnyConnect Secure Mobility client supports Cisco ASA version 8.0(4) or later and the Adaptive Security Device Manager (ASDM) 6.4(1) or later.
Cisco AnyConnect is available as a separate add-on that you can push to your devices using the standard add-on procedure.
upgrades of Cisco AnyConnect 3.1 from the ASA are
table shows the AnyConnect features supported on the thin clients.
Table 1 AnyConnect
Supported on SUSE Linux-based Thin Clients
Datagram Transport Layer
Security (DTLS) with SSL access to VPN
Compression -Increases the
communications performance between the security appliance and the client
Fallback from DTLS to TLS
if DTLS fails
authentication for standalone mode
RSA SecurID integration
Download certificate from ASA with Get Certificate
Simple Certificate Enrollment Protocol (SCEP) to set up and renew a certificate used for client authentication
Minimize on connect
IPv6 VPN access-Allows
access to IPv6 resources over a public IPv4 connection
Local LAN access
Local printer access through client firewall rules
Trusted network detection
Captive portal (hotspot)
Start Before Logon (SBL)
Autoconnect on start
Resume session after loss
Auto update AnyConnect
N/A (update using Dell Wyse Device Manager)
Auto update AnyConnect
Reporting Tool (DART)
Processing Standard (FIPS) security
acceptable use policies to protect endpoints from websites found to be unsafe