The documentation set for this product strives to use bias-free language. For the purposes of this documentation set, bias-free is defined as language that does not imply discrimination based on age, disability, gender, racial identity, ethnic identity, sexual orientation, socioeconomic status, and intersectionality. Exceptions may be present in the documentation due to language that is hardcoded in the user interfaces of the product software, language used based on RFP documentation, or language that is used by a referenced third-party product. Learn more about how Cisco is using Inclusive Language.
Each of the components listed in the following table must meet the requirements. Use of unsupported components can result in a nonfunctional deployment.
Component |
Requirements |
||
---|---|---|---|
SUSE Linux thin clients—Hardware |
SP2-supported hardware: Dell Wyse Z50D or D50D SP3-supported hardware: Dell Wyse D50Q, Z50Q, or Z50QQ
|
||
SUSE Linux Platform SP2 Image |
11.2.092 |
||
SUSE Linux Platform SP3 Image |
11.3.092 |
||
Hosted virtual desktop OS (server-side) |
|||
Connection broker for the hosted virtual desktop |
|||
Receiver or client (on the thin client) |
The platform SP2 or SP3 image includes the required receiver or client. |
||
Cisco Unified Communications client on the hosted virtual desktop |
Cisco Jabber for Windows 11.0 running on the hosted virtual desktop (HVD). Cisco VXME is compatible with all future 11.0(X) Cisco Jabber for Windows versions. All Jabber features that are supported for the current release of VXME are supported for future 11.0(X) Jabber releases. For complete information about virtual environment compatibility, see the Virtual Environments section in Installation and Configuration Guide for Cisco Jabber for Windows for your release. |
||
Windows Server (Required for Citrix XenApp) |
(Standard, Enterprise, Datacenter, and Foundation) |
||
Cisco Unified Communications Manager User Data Service (UDS) |
|||
Cisco AnyConnect (Optional) |
3.1.08009-71 (available for SP2 and SP3) |
||
Accessories |
For a complete listing of supported audio and video accessories, see Unified Communications Endpoint and Client Accessories, at http://www.cisco.com/c/en/us/products/unified-communications/uc_endpoints_accessories.html. Ensure that all Jabra devices are running the latest firmware. You can use Jabra Direct to update the firmware. For more information visit: http://www.jabra.com. |
Video resolution and performance depend on various factors including the thin client and camera used. The following table lists the maximum expected resolutions for each thin client.
Thin Client Model |
Standard Resolution |
Resolution With Encoding Camera (Logitech C920-C) |
---|---|---|
Dell Wyse D50D |
240p |
480p |
Dell Wyse D50Q |
480p |
720p and higher |
Dell Wyse Z50D |
360p |
720p |
Dell Wyse Z50Q |
720p and higher |
720p and higher |
Dell Wyse Z50QQ |
720p and higher |
720p and higher |
SUSE Linux thin clients must meet all system requirements including a compatible base image version. For more information, see Release Notes for Cisco Virtualization Experience Media Engine for SUSE Linux for your release.
Wyse Device Manager 5.0 is the recommended deployment tool to deploy VXME to Dell Wyse thin clients.
Cisco does not support any management administrative method to deploy VXME to Dell Wyse thin clients. Support for adding and enabling add-ons is provided by Dell Wyse, using Wyse Device Manager or other methods supported by Dell Wyse.
The following table lists the ports or port ranges used by Cisco Virtualization Experience Media Engine for SUSE Linux.
Cisco Virtualization Experience Media Engine uses the computer-telephony integration (CTI) protocol. Cisco Jabber for Windows on a hosted virtual desktop uses outbound TCP port 2748 to connect to the CTI gateway. The CTI gateway is the CTI Manager component of Cisco Unified Communications Manager.
For a complete listing of ports required by Cisco Jabber for Windows, see the planning guide for your release of Cisco Jabber.
Audio Codec |
Video Codec |
---|---|
G.722 |
H.264/AVC |
G.722.1 (24 and 32k) G.722.1 is supported on Cisco Unified Communications Manager 8.6.1 or later. |
|
G.711 A-law |
|
G.711 u-law |
|
G.729a |
|
Opus Opus is supported on Cisco Unified Communications Manager 11.0 or later. |
To enable Cisco AnyConnect connections, set up Cisco AnyConnect profiles on the Cisco Adaptive Security Appliance (ASA). Next, specify the required VPN INI connection parameters on the thin client. After you set up the required profiles and push the INI parameters to the client, users can then establish secure connections.
Before you provide the devices to your remote employees, push the required configuration to the devices on your local network first. You can then provide the preconfigured devices to remote users to operate behind the Cisco AnyConnect VPN.
On the Cisco Adaptive Security Appliance (ASA), AnyConnect profiles provide basic information about connection setup, and users cannot manage or modify them. The profile is an XML file that lets you identify the secure gateway (Cisco ASA) hosts that you want to make accessible. In addition, the profile specifies extra connection attributes and constraints for a user. Usually, a user has a single profile file. This profile contains all the hosts needed by a user, and extra settings as needed.
By creating and assigning different profiles to group policies configured on the Cisco ASA, you can differentiate access to Cisco ASA features. The Cisco ASA automatically pushes the profile assigned to the user upon connection setup.
You can configure a profile using the AnyConnect profile editor, a GUI-based configuration tool launched from the Adaptive Security Device Manager (ASDM). The AnyConnect software package, version 3.0 and later, includes the editor. The editor starts when you load the AnyConnect package on the Cisco ASA as an SSL VPN client image.
For detailed configuration information, see the Cisco AnyConnect Secure Mobility Client Administrator Guide for your release.
To set up Cisco AnyConnect on the device, configure the Custom Connect INI parameter to create Cisco AnyConnect connections. Use the INI parameters to specify the Cisco Adaptive Security Appliance (ASA) address and settings.
To create the Cisco AnyConnect connection, configure the Custom Connect parameter in your INI file. The Custom Connect parameter includes a Command option to enable Cisco AnyConnect at startup and to include a Cisco AnyConnect icon on the desktop.
CONNECT=Custom \ Description="ASA Connection" \ AutoConnect=Yes \ Reconnect=Yes \ ReconnectSeconds=100 \ Command=/opt/cisco/anyconnect/bin/vpnui
Note | In the INI file, include the INIFileSource=cache parameter. This parameter ensures that devices use the local cached version of the INI file if they cannot access the INI files from Cisco VXC Manager. This parameter is important for devices running the Cisco AnyConnect VPN. These devices require a configuration to reference at bootup before connecting to the network over VPN. |
Parameter | Description | ||
---|---|---|---|
AutoConnect={no, yes} | Default is no. Yes or no option to start a connection automatically at sign-on. |
||
Command=<command or application to be executed from the client> | Mandatory Option Specifies a command or application to be executed from the client. For Cisco AnyConnect: Command=/opt/cisco/anyconnect/bin/vpnui |
||
Description=<string description> | Mandatory Option Connection description. Provides a connection name for the Desktop icon and the Connection Manager.
|
||
Reconnect={no, yes} | Default is no. Yes or no option to automatically reconnect to an application server after a disconnection. |
||
ReconnectSeconds=<value in seconds> | Default is 30. Specifies the amount of time in seconds (default is 30) to wait before automatic reconnection to an application server after a disconnection. Requires Reconnect=yes or 1. |
Caution | Do not insert any additional spaces at the end of lines in the INI file. Extra spaces may cause the device to parse the INI file incorrectly. |
To complete the Cisco AnyConnect setup, specify the Cisco ASA address and settings using the following INI parameters. After you configure these settings and the Custom Connect parameter, push the updated INI file to your devices to enable VPN connections.
Parameter | Description |
---|---|
VPNGroup=<Group name>,... (optional) | Use this parameter if you configure groups on the Cisco ASA. This parameter specifies the name or names (separated by commas) that the Cisco AnyConnect Client can use for the VPN connection. |
VPNHeadendAddress= <FQDN or IP address> (required) |
Specifies the VPN headend FQDN or IP Address to autoconfigure the Cisco AnyConnect Client. For example, VPN.Cisco.com or 192.168.0.1. |
The following shows an example configuration:
VPNGroup= profilename VPNHeadendAddress=192.168.0.1