Chapter 1. Planning

- Cisco Jabber Softphone for VDI

- Cisco Jabber and VDI

- The User Experience

- General Requirements

- Requirements—HP Thin Pro Thin Clients

- Requirements—Ubuntu Thin Clients

- Requirements—Unicon eLux Thin Clients

- Requirements—Windows Thin Clients

Cisco Jabber Softphone for VDI

The applications in the Cisco Jabber Softphone for VDI family of products are:

- Cisco Jabber Softphone for VDI—HP Thin Pro and Ubuntu

- Cisco Jabber Softphone for VDI—Unicon eLux

- Cisco Jabber Softphone for VDI—Windows

- Cisco Jabber Softphone for VDI—Dell Wyse Thin OS (Available from, and supported by Dell Wyse)

Cisco Jabber and VDI

Cisco Jabber chat and presence are supported in Virtual Desktop Infrastructure deployments. However, because of a limitation known as the hairpin effect, calling and video capability are not supported. The additional bandwidth required for calls and video creates a bottleneck at the data center.

Cisco Jabber Softphone for VDI 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 Cisco Jabber Softphone for VDI software automatically detects the virtual environment. To reduce latency and to enhance media quality, Cisco Jabber Softphone for VDI streams media between the endpoints without going through the hosted virtual desktops.

Cisco Jabber Softphone for VDI—Data Flow

Use the following flowchart to determine whether you require Cisco Jabber Softphone for VDI.

Do You Need Cisco Jabber Softphone for VDI?

The User Experience

Cisco Jabber Softphone for VDI detects the virtual environment at run time and Cisco Jabber starts in virtualization mode. The user experience with Cisco Jabber for Windows and Cisco Jabber Softphone for VDI is similar to the non-VDI experience. However, in a virtual environment there are some minor differences:

- Device Selector, which is located in the Windows notification area, allows users to quickly switch their active camera and audio devices. Device management is also available from within Cisco Jabber.

- Headset Priority—By default, Cisco Jabber adds a newly connected device to the top of the priority list, and makes the new device active. You can set the HeadsetPreference parameter so that Cisco Jabber adds new devices to the bottom of the priority list. For more information, see Parameters Reference Guide for Cisco Jabber.

Note

Users can override this setting in their Audio preferences.

- Feature Support—Cisco Jabber Softphone for VDI supports most Cisco Jabber for Windows features, with some exceptions. For more information, see the release notes for your platform:

- Release Notes for Cisco Jabber Softphone for VDI—HP Thin Pro and Ubuntu

- Release Notes for Cisco Jabber Softphone for VDI—Unicon eLux

- Release Notes for Cisco Jabber Softphone for VDI—Windows

Release Notes for Cisco Jabber Softphone for VDI

General Requirements

General requirements apply to all Cisco Jabber Softphone for VDI platforms.

Important

Only the components, versions, and minimum hardware requirements listed in this guide are supported. Use of unsupported components can result in a nonfunctional deployment.

Accessories

For a complete listing of recommended 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.

Cisco Jabber for Windows

Cisco Jabber for Windows 12.7 running on the hosted virtual desktop (HVD).

For complete information about virtual environment compatibility, see the Cisco Jabber documentation for your release.

Cisco Unified Communications Manager

Recommended: CUCM Release 11.5(1)SU3 or later

Minimum: CUCM Release 10.5

Connection Broker—Installed on the Hosted Virtual Desktops

- Citrix Virtual Apps and Desktops (formerly XenApp and XenDesktop) versions 7.x–7.1909, and 7.15 LTSR up to CU4

Shared Desktop is supported only in full-screen mode. Published Application is supported in full-screen mode for Cisco Jabber Softphone for VDI—Windows.

- VMware Horizon 6 versions 6.x–7.10

A connection broker is software that creates connections to hosted virtual desktops. A connection broker performs a number of tasks including the following:

- Validating the username and providing a connection for the user.

- Allowing the user to connect to a specific virtual desktop.

Operating Systems—Installed on the Hosted Virtual Desktops

- Microsoft Windows 7 32–bit

- Microsoft Windows 7 64–bit

- Microsoft Windows 8 32–bit

- Microsoft Windows 8 64–bit

- Microsoft Windows 8.1 32–bit

- Microsoft Windows 8.1 64 64–bit

- Microsoft Windows 10 32–bit

- Microsoft Windows 10 64–bit

Server Operating Systems—Installed on the Hosted Virtual Desktops

- Microsoft Windows Server 2012 R2

- Microsoft Windows Server 2016 R2

Port Requirements

Cisco Jabber Softphone for VDI requires the same ports as Cisco Jabber does, and the following additional port range:

Port Usage

Port Range

Description

16384–32767

UDP Inbound and outbound traffic for RTP (audio and video streams)

You can configure the Cisco Unified Communications Manager to reduce this port range. Change the Start/Stop Media Port setting in the SIP Profile, which is associated with the CSF device.

Supported Codecs

Audio Codecs:

- G.722

- 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.

Video Codec: H.264/AVC

Requirements—HP Thin Pro Thin Clients

Important

Only the components, versions, and minimum hardware requirements listed in this guide are supported. Use of unsupported components can result in a nonfunctional deployment.

HP ThinPro Platform Image

32–bit: HP ThinPro 6.2

64–bit: HP ThinPro 7.1 SP3.3 and 7.x versions

HP Thin Pro Thin Clients—Hardware

We recommend the following client hardware, which was tested with HP Thin Pro 6.2:

- HP t520

- HP t530

- HP t620

- HP t630

- HP t730

- HP mt21

We recommend the following client hardware, which was tested with HP Thin Pro 7.1 SP3.3:

- HP t430

- HP t520

- HP t530

- HP t630

- HP t730

- HP mt21

Connection Broker—Installed on the HVD

- Citrix Virtual Apps and Desktops (formerly XenApp and XenDesktop) versions 6.x, 7.x–7 1811, and 7.15 LTSR

Published Application and Shared Desktop are supported only in full-screen mode.

- VMware Horizon 6 versions 6.x–7.7

A connection broker is software that creates connections to hosted virtual desktops. A connection broker performs a number of tasks including the following:

- Validating the username and providing a connection for the user.

- Allowing the user to connect to a specific virtual desktop.

Citrix Workspace app or VMware Horizon Client—Installed on the Thin Clients

The HP Thin Pro image includes the required Citrix and VMware versions.

The Citrix Workspace app or VMware Horizon Client provides a user interface for the corresponding connection broker.

Requirements—Ubuntu Thin Clients

Important

Only the components, versions, and minimum hardware requirements listed in this guide are supported. Use of unsupported components can result in a nonfunctional deployment.

Ubuntu Desktop Image

- Ubuntu 14.04 32b LTS (i386)

- Ubuntu 16.04 64b LTS (AMD64)

Ubuntu Thin Clients—Hardware

The minimum hardware requirements for thin clients are as follows:

- Installed RAM 2 GB

- Free Physical Memory 1 GB

- Free Disk Space 256 MB

- CPU: AMD G-T56N 1.65Ghz, or Intel Core2Duo T7500 2.2 GHz

- USB 2.0 for USB camera and audio devices

Citrix Workspace app or VMware Horizon Client—Installed on the Thin Clients

- Citrix Receiver 13.0 and later

- Citrix Workspace app 1808 and later

- VMware Horizon View Client versions 4.x and 5.x

The Citrix Workspace app or VMware Horizon Client provides a user interface for the corresponding connection broker.

Requirements—Unicon eLux Thin Clients

Important

Only the components, versions, and minimum hardware requirements listed in this guide are supported. Use of unsupported components can result in a nonfunctional deployment.

Unicon eLux Platform Image

- 32–bit: Unicon eLux 5.7

- 64–bit: Unicon eLux 6.5

The eLux packages are available from Unicon eLux. For assistance locating a download, contact eLux support.

Unicon eLux Thin Clients—Hardware

The minimum hardware requirements for thin clients are:

- 1.6 GHz dual-core processor

- 2 GB RAM

We recommend the following client hardware, which was tested with eLux RP 5.7.0:

- HP T620 Dual Core / Quad Core

- HP T630 Dual Core / Quad Core

- HP T730

- Cisco VXC 6215

- Dell Wyse Z50D

Citrix Workspace App or VMware Horizon Client—Installed on the Thin Clients

Unicon eLux includes the required Citrix and VMware versions.

The Citrix Workspace app or VMware Horizon Client provides a user interface for the corresponding connection broker.

Cisco Anyconnect (Optional)

vpnsystem V4.5-1

Requirements—Windows Thin Clients

Important

Only the components, versions, and minimum hardware requirements listed in this guide are supported. Use of unsupported components can result in a nonfunctional deployment.

Microsoft Windows Thin Clients—Hardware

The minimum system requirements for thin clients are as follows:

- Installed RAM 2 GB

- Free Physical Memory 1 GB

- Free Disk Space 256 MB

- CPU Mobile AMD Sempron Processor 3600+, 2-GHz Intel Core 2 CPU, or T7400 2.16 GHz

- DirectX 11 compatible GPU

- USB 2.0 for USB camera and audio devices

Microsoft Windows—Installed on the Thin Clients

- Microsoft Windows 7 32–bit

Requires Update for Windows 7 (KB4019990)

- Microsoft Windows 7 64–bit

Requires Update for Windows 7 for x64–based Systems (KB4019990)

- Microsoft Windows 8 32–bit

- Microsoft Windows 8 64–bit

- Microsoft Windows 8.1 32–bit

- Microsoft Windows 8.1 64–bit

- Microsoft Windows 10 32–bit

- Microsoft Windows 10 64–bit

- Windows Thin PC 32–bit

Note

Cisco Jabber Softphone for VDI for Windows does not require the Microsoft .NET Framework or any Java modules.

Windows Embedded Standard Thin Clients—Hardware

The minimum system requirements for thin clients are as follows:

- Installed RAM 2 GB

- Free Physical Memory 1 GB

- Free Disk Space 256 MB

- CPU performance affects the maximum video resolution. With Windows Embedded Standard thin clients, the expected resolution depends on the CPU:

- Up to 720p with quad-core AMD GX-420CA SOC 2 GHz or similar

- Up to 240p with dual-core AMD G-T56N 1.65 GHz or similar

- Audio-only support with dual-core VIA Eden X2 U4200 1 GHz or similar CPU

Note

These hardware specifications are only guidelines for the expected resolutions. Other factors can affect video resolution.

- DirectX 11 compatible GPU

- USB 2.0 for USB camera and audio devices

Windows Embedded Standard—Installed on the Thin Clients

- Windows Embedded Standard 7 32–bit

Requires Update for Windows Embedded Standard 7 (KB4019990)

- Windows Embedded Standard 7 64–bit

Requires Update for Windows Embedded Standard 7 for 64–bit Systems (KB4019990)

- Windows Embedded Standard 8 64–bit

Requires Update for Windows Embedded Standard 8 for 64–bit Systems (KB4019990)

- Windows 10 IoT Enterprise

Citrix Workspace App or VMware Horizon Client—Installed on the Thin Clients

- Citrix Receiver (ICA) for Windows 4.4, and up to 4.12

- Citrix Workspace App (ICA) for Windows 1808, and up to 1907

Important

Cisco Jabber Softphone for VDI does not support Citrix Workspace App downloaded from the Microsoft Store.

- VMware Horizon Client for Windows 4.1.0, 4 and up to 5.0

(Versions 4.3 and 4.4 are not supported.)

The Citrix Workspace app or VMware Horizon Client provides a user interface for the corresponding connection broker.

Important

Before you install the Cisco JVDI Client, install the Citrix Receiver or VMware Horizon Client on the thin client.

If you change from a Citrix environment to a VMware environment (or from VMware to Citrix), reinstall the Cisco JVDI Client.

Part I. Deployment

- Deployment Overview

- Downloads

- Installation

- Upgrade

Chapter 2. Deployment Overview

- Deployment Overview Workflow

Deployment Overview Workflow

We recommend that you read the release notes document for your platform. Review the requirements to confirm that all hardware and software meet them. Failure to meet all requirements can result in a nonfunctional deployment.

Important

The Cisco Jabber for Windows and Cisco JVDI Agent versions must always match. However, the Cisco JVDI Client version can be the same, or the previous version. The earlier software version determines the available feature set.

You must install both Cisco JVDI Agent and Cisco JVDI Client; otherwise, the softphone fails to register.

Procedure

Step 1

Follow the instructions to deploy Cisco Jabber for Windows, up to the installation of the Jabber client.

Important

You must create CSF devices for Cisco Jabber Softphone for VDI users, and add each user to the following Access Control Groups:

- Standard CCM End Users

- Standard CTI Enabled

See On-Premises Deployment for Cisco Jabber for your release.

For hybrid deployments, see Cloud and Hybrid Deployments for Cisco Jabber for your release.

Cisco Jabber deployment guides are available from: https://www.cisco.com/c/en/us/support/unified-communications/jabber-windows/products-installation-guides-list.html.

Step 2

Create and set up the hosted virtual desktops in the data center.

Ensure that the hosted virtual desktops (HVD) are ready for you to install the Cisco JVDI Agent. See Set up the Hosted Virtual Desktops Workflow.

Step 3

Set up and configure the thin clients.

See the documentation for the thin clients.

Step 4

Install the Cisco Jabber Softphone for VDI components on the thin clients and the HVDs.

- Install the Components Workflow—HP Thin Pro

- Install the Components Workflow—Ubuntu

- Install the Components Workflow—Unicon eLux

- Install the Components Workflow—Windows

Chapter 3. Downloads

- Download the Cisco JVDI Agent

- Download the Cisco JVDI Client

- Download Cisco AnyConnect—Unicon eLux

Download the Cisco JVDI Agent

Procedure

Step 1

Visit the following URL:

http://www.cisco.com/cisco/software/navigator.html

Step 2

Navigate to Products > Unified Communications > Unified Communications Applications > Messaging, and then select your Cisco Jabber Softphone for VDI platform:

- Cisco Jabber Softphone for VDI—HP Thin Pro and Ubuntu

- Cisco Jabber Softphone for VDI—Unicon eLux

- Cisco Jabber Softphone for VDI—Windows

Step 3

From the list, choose the Cisco JVDI Agent file for your release.

Step 4

Click Download or Add to cart and follow the prompts.

Download the Cisco JVDI Client

This procedure applies to the HP Thin Pro 7.1 SP3, Unicon eLux, and Windows platforms. For HP Thin Pro 6.2, the Cisco Jabber Softphone for VDI Debian (.deb) package and cisco-jvdi<xx.x.x>-pre-reqs.xar file are available from HP. For Ubuntu, the Debian package is available from the Ubuntu Software Center.

Procedure

Step 1

Visit the following URL:

http://www.cisco.com/cisco/software/navigator.html

Step 2

Navigate to Products > Unified Communications > Unified Communications Applications > Messaging, and then select your Cisco Jabber Softphone for VDI platform:

- Cisco Jabber Softphone for VDI—HP Thin Pro and Ubuntu

- Cisco Jabber Softphone for VDI—Unicon eLux

- Cisco Jabber Softphone for VDI—Windows

Step 3

From the list, choose the Cisco JVDI Client file for your release.

Step 4

Click Download or Add to cart and follow the prompts.

Download Cisco AnyConnect—Unicon eLux

The supported vpnsystem package is available from Unicon.

Procedure

Step 1

Visit the Unicon web site.

Step 2

Locate and download the file: vpnsystem.

For assistance locating the file, contact Unicon support.

Chapter 4. Installation

- Set up the Hosted Virtual Desktops Workflow

- Install the Components Workflow—HP Thin Pro

- Install the Components Workflow—Ubuntu

- Install the Components Workflow—Unicon eLux

- Install the Components Workflow—Windows

Set up the Hosted Virtual Desktops Workflow

The Virtual Machines for the HVDs can be either Citrix-, or VMware-provisioned. Citrix-provisioned virtual machines can be dedicated, or have multiple users connected over multiple remote sessions. To support multiple remote sessions, the virtual machine must be running a supported Microsoft Windows Server operating system.

Procedure

Step 1

Log in to the Microsoft Windows HVD as the new user, with administration rights.

Step 2

Join the HVD to the corporate domain.

You must have domain administration rights.

Step 3

Set up Citrix or VMware access to the HVDs.

What to do next

- Install the Components Workflow—HP Thin Pro

- Install the Components Workflow—Ubuntu

- Install the Components Workflow—Unicon eLux

- Install the Components Workflow—Windows

Install the Components Workflow—HP Thin Pro

Before you begin

Ensure that you have all of the required files on hand. If you plan to manually install Cisco JVDI Client on the thin clients, copy the files to a USB stick.

- Download the Cisco JVDI Agent

- Download the Cisco JVDI Client

Note

Starting with Thin Pro7.1 SP3, the prerequisites file is pre-installed with Thin Pro. For Thin Pro 6.2, you can obtain the prerequisites file directly from HP.

Important

The Cisco Jabber for Windows and Cisco JVDI Agent versions must always match. However, the Cisco JVDI Client version can be the same, or the previous version. The earlier software version determines the available feature set.

Procedure

Step 1

On the thin client, install the Cisco Jabber Softphone for VDI files in the following order, either manually from a USB stick, or use HP Device Manager for mass deployments.

Order of installation:

1. Prerequisites

2. Cisco Jabber Softphone for VDI .deb package.

For more information about mass deployment, see the documentation for HP Device Manager 4.7, available from HP.

Step 2

On the HVD, install Cisco JVDI Agent.

Double-click the .msi file, and then follow the installation wizard steps.

Step 3

On the HVD, install Cisco Jabber for Windows.

Double-click CiscoJabberSetup.msi and follow the installation wizard steps. For detailed information about how to install Cisco Jabber for Windows, see On-Premises Deployment for Cisco Jabber for your release.

For hybrid deployments, see Cloud and Hybrid Deployments for Cisco Jabber for your release.

Cisco Jabber deployment guides are available from: https://www.cisco.com/c/en/us/support/unified-communications/jabber-windows/products-installation-guides-list.html.

What to do next

Clone the HVD. For best practices for cloning Microsoft Windows HVD images, consult the documentation for your Citrix or VMware product.

Create an image for the thin clients. See the documentation for HP Device Manager 4.7, available from HP.

Install the Components Workflow—Ubuntu

Important

The Cisco Jabber for Windows and Cisco JVDI Agent versions must always match. However, the Cisco JVDI Client version can be the same, or the previous version. The earlier software version determines the available feature set.

Before you begin

Ensure that you have all of the required files on hand. If you plan to manually install Cisco JVDI Client on the thin clients, copy the files to a USB stick.

- Download the Cisco JVDI Agent

- Obtain the Cisco Jabber Softphone for VDI deb package from the Ubuntu software center repository.

On the thin client, use the terminal emulator to run the following command: sudo apt-get update, and then enter your password at the prompt. The list of repositories for the Ubuntu Software Center updates. After the command finishes reading the package lists, you can close the terminal emulator. You can place the file on a network share accessible from the thin clients, or copy it to a USB stick.

Procedure

Step 1

On the HVD, install Cisco JVDI Agent.

Double-click the Cisco JVDI Agent .msi and follow the installation wizard steps.

Step 2

On the HVD, install Cisco Jabber; double-click CiscoJabberSetup.msi and follow the installation wizard steps.

For detailed information about how to install Cisco Jabber for Windows, see On-Premises Deployment for Cisco Jabber for your release.

For hybrid deployments, see Cloud and Hybrid Deployments for Cisco Jabber for your release.

Cisco Jabber deployment guides are available from: https://www.cisco.com/c/en/us/support/unified-communications/jabber-windows/products-installation-guides-list.html.

Step 3

On the thin client, install the Cisco JVDI Client; enter your password at the authentication prompt.

When you double-click the Cisco Jabber Softphone for VDI deb package, the Ubuntu Software Center opens. After you click Install, the Ubuntu Software Center locates and installs the dependency libraries, and then installs the Cisco JVDI Client.

What to do next

Clone the HVD image. For best practices for cloning Microsoft Windows HVD images, consult the documentation for your Citrix or VMware product.

Create an image for the thin clients.

Install the Components Workflow—Unicon eLux

Important

The Cisco Jabber for Windows and Cisco JVDI Agent versions must always match. However, the Cisco JVDI Client version can be the same, or the previous version. The earlier software version determines the available feature set.

Before you begin

- Download the Cisco JVDI Agent

- Download the Cisco JVDI Client

- Download Cisco AnyConnect—Unicon eLux (Optional, required only if users need VPN connectivity.)

Procedure

Step 1

On the HVD, install Cisco Jabber for Windows.

Double-click CiscoJabberSetup.msi and follow the installation wizard steps. For detailed information about how to install Cisco Jabber for Windows, see On-Premises Deployment for Cisco Jabber for your release.

For hybrid deployments, see Cloud and Hybrid Deployments for Cisco Jabber for your release.

Cisco Jabber deployment guides are available from: https://www.cisco.com/c/en/us/support/unified-communications/jabber-windows/products-installation-guides-list.html.

Step 2

On the HVD, install Cisco JVDI Agent.

Double-click the MSI file and follow the installation wizard steps.

Step 3

On the thin client, install the Cisco JVDI Client and if required, deploy Cisco AnyConnect at the same time.

What to do next

Clone the HVD image. For best practices for cloning Microsoft Windows HVD images, consult the documentation for your Citrix or VMware product.

Use the Elias tool to create an image that contains Cisco JVDI Client. Deploy the image to the thin clients. For more information about how to create an image or how to update the thin client, see the Elias documentation available from the Unicon website.

Install the Components Workflow—Windows

Important

The Cisco Jabber for Windows and Cisco JVDI Agent versions must always match. However, the Cisco JVDI Client version can be the same, or the previous version. The earlier software version determines the available feature set.

Before you begin

- Download the Cisco JVDI Agent

- Download the Cisco JVDI Client

Procedure

Step 1

On the HVD, install Cisco JVDI Agent.

Step 2

On the HVD, install Cisco Jabber.

Double-click CiscoJabberSetup.msi and follow the installation wizard steps. For detailed information about how to install Cisco Jabber for Windows, see On-Premises Deployment for Cisco Jabber for your release.

For hybrid deployments, see Cloud and Hybrid Deployments for Cisco Jabber for your release.

Cisco Jabber deployment guides are available from: https://www.cisco.com/c/en/us/support/unified-communications/jabber-windows/products-installation-guides-list.html.

Step 3

On the thin client, install the Cisco JVDI Client.

See Cisco JVDI Client Installation.

- Cisco JVDI Client Installation

- Run the Microsoft Installer

- Use the Command Line

- Use the Group Policy Editor

Cisco JVDI Client Installation

Prerequisites

Before you install Cisco JVDI Client on the thin clients, complete the following tasks:

- Install and set up the Citrix Receiver or VMware Horizon View Client.

Note

The JVDI Client is available as a 32– or 64–bit application.

- Obtain the Cisco JVDI Client zip file, and extract the contents.

Use one of the following methods to install Cisco JVDI Client:

- Run the Microsoft Installer

- Use the Command Line

- Use the Group Policy Editor

Run the Microsoft Installer

Run the Microsoft Installer (MSI) to install Cisco JVDI Client.

Procedure

Step 1

Double-click the CiscoJVDIClientSetup.msi file.

Step 2

To open the executable file, click OK.

Step 3

If the Open File - Security Warning appears, click Run.

Step 4

Read the EULA and, if you agree, click Accept and Install.

http://www.cisco.com/go/eula.

Step 5

To complete the installation, click Finish.

Use the Command Line

Procedure

Step 1

Open a command window.

Step 2

Enter the following command: start /wait msiexec.exe /i <path to MSI>\CiscoJVDIClientSetup.msi /quiet.

The /quiet switch specifies a silent installation.

Use the Group Policy Editor

Use the Group Policy Management console to deploy Cisco JVDI Client to supported thin clients that are running a supported Microsoft Windows operating system.

Before you begin

- Use Microsoft Orca to set the language code to 1033.

- Copy the modified Microsoft Installer (MSI) to a software distribution point for deployment. All computers to which you plan to deploy Cisco JVDI Client must be able to access the MSI on the distribution point.

Procedure

Step 1

Select Start > Run.

Step 2

At the prompt, enter the following command: GPMC.msc.

Step 3

Right-click on the appropriate domain in the left section.

Step 4

Select Create a GPO in this Domain, and Link it here.

Step 5

In the New GPO window, Name field, enter a name for the group policy object.

Step 6

Leave the default value or select an option from the Source Starter GPO list, and then select OK.

The new group policy appears in the list of group policies for the domain.

Step 7

Select the group policy object under the domain in the left section.

Step 8

From the Security Filtering section of the Scope tab, select Add.

Step 9

Specify the computers and users to which you want to deploy Cisco JVDI Client.

Step 10

Specify the MSI file.

Step 11

Right-click the group policy object in the left section and then select Edit.

The Group Policy Management Editor opens.

Step 12

Select Computer Configuration and then select Policies > Software Settings.

Step 13

Right-click Software Installation and then select New > Package.

Step 14

Next to File Name, enter the location of the MSI file.

Example:

\\server\software_distribution

Important

Enter the Uniform Naming Convention (UNC) path for the location of the MSI file. If you do not enter the UNC path, Group Policy cannot deploy Cisco JVDI Client.

Step 15

Select the MSI file, and then select Open.

Step 16

In the Deploy Software dialog box, select Assigned, and then select OK.

Chapter 5. Upgrade

- Upgrade Notes

- Upgrade Workflow

Upgrade Notes

To get the new Cisco Jabber Softphone for VDI Release 12.7 features, you must upgrade all of the following components to Release 12.7:

- Cisco Jabber for Windows

- Cisco JVDI Agent

- Cisco JVDI Client

Both the Cisco JVDI Agent and Cisco JVDI Client are required for softphone registration to succeed. The Cisco Jabber for Windows and Cisco JVDI Agent versions must always match. However, the Cisco JVDI Client version can be the same, or the previous version. The earlier software version determines the available feature set.

- Cisco Jabber for Windows Release 12.7, Cisco JVDI Agent Release 12.7, and Cisco JVDI Client Release 12.7

- Cisco Jabber for Windows Release 12.7, Cisco JVDI Agent Release 12.7, and Cisco JVDI Client Release 12.6

Important

The limitations and restrictions for the earlier JVDI Client release apply. The available features are limited to those available for the earlier release. For more information, see the release notes for the earlier release. For example, if your JVDI Client Release is 12.6, see the release notes document for Release 12.6.

Upgrade Workflow

We recommend that you read the release notes document for your platform. Review the requirements to confirm that all hardware and software meet them. Failure to meet all requirements can result in a nonfunctional deployment.

Before you begin

Ensure that you have all of the required files on hand. If you plan to manually install Cisco JVDI Client on the thin clients, copy the files to a USB stick.

Procedure

Follow the steps to install the Cisco Jabber Softphone for VDI components on the thin clients and the HVDs.

- Install the Components Workflow—HP Thin Pro

- Install the Components Workflow—Ubuntu

- Install the Components Workflow—Unicon eLux

- Install the Components Workflow—Windows

Important

Both the Cisco JVDI Agent and Cisco JVDI Client are required for softphone registration to succeed. The Cisco Jabber for Windows and Cisco JVDI Agent versions must always match. However, the Cisco JVDI Client version can be the same, or the previous version. The earlier software version determines the available feature set.

If you're not upgrading the Cisco JVDI Client, you can skip the steps to install it.

Part II. Troubleshooting

- Troubleshooting—Windows

- Troubleshooting—Unicon eLux

- Troubleshooting—HP Thin Pro and Ubuntu

- General Troubleshooting

Chapter 6. Troubleshooting—Windows

- Configuration Files

- Registry Keys

- Verify the Connection Status in Cisco Jabber

- Verify That Cisco JVDI Agent Is Installed

- Confirm the Version of Cisco JVDI Client

- Call Control Is Lost After a Network Failure

- Call Is Lost After HVD Disconnection

- Enable Log Collection

- Enable Memory Dump Collection

Configuration Files

For each Cisco Unified Client Services Framework (CSF) device that you add to the system, Cisco Unified Communications Manager creates a configuration (CNF.xml) file. The CNF file contains the device specifications for the associated user.

When users sign in to Cisco Jabber, Cisco Jabber Softphone for VDI starts the download of the associated CNF file to the thin client. To ensure the successful transfer of the file, open the relevant ports in all firewall applications to allow the thin client to access the ports. For more information about how to open ports, see the documentation for the firewall software.

Important

Download of the CNF.xml file follows the system setting for HTTP proxy. Ensure that the proxy does not route the HTTP request from the thin client outside of the corporate network.

Registry Keys

The Cisco JVDI Client installation program checks to ensure that either the Citrix Receiver or the VMware Horizon Client is already installed on the reused PC. In one of the following registry locations, the InstallFolder string-type registry key must be present:

- For Citrix, the installer searches in HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Citrix\Install\ICA Client for the path to the Citrix installation.

Example (from an x86 PC): [HKEY_LOCAL_MACHINE\SOFTWARE\Citrix\Install\ICA Client] "InstallFolder"="C:\\Program Files\\Citrix\\ICA Client\\"

- For VMware Horizon, the installer searches in HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\VMware, Inc.\VMware VDM for the path to the VMware installation.

Example (from an x64 PC): [HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\VMware, Inc.\VMware VDM] "ClientInstallPath"="C:\\Program Files\\VMware\\VMware View\\Client\\"

Verify the Connection Status in Cisco Jabber

After you sign in to Cisco Jabber for Windows, you can check the connection status for Jabber and for Cisco Softphone for VDI. You can also confirm the versions for the JVDI Agent and the JVDI Client.

Procedure

Step 1

Click to open the Settings Menu.

Step 2

Go to Help > Show connection status

Step 3

In the Connection Status window, click JVDI Details.

You can see the following information:

- JVDI Client version

Tip

If the JVDI Client version is 12.5 or 12.1, the client version doesn't appear until after the softphone connects.

- JVDI Agent version

- Virtual Channel status indicates whether communication between the JVDI Client andCisco Jabber is successful.

- SIP status indicates whether SIP communication with Cisco Unified Communications Manager is successful.

- Softphone CTI status indicates whether CTI communication is successful.

Tip

If the SIP status is Connected, but the Softphone CTI status is Not connected, check the CTI configuration in CUCM.

Step 4

To see detailed diagnostic information for Cisco Jabber, press Ctrl +Shift +D.

Verify That Cisco JVDI Client Is Running

Use Windows Task Manager to verify that Cisco JVDI Client is running.

In a Citrix environment, the Cisco Jabber Softphone for VDI processes start when the user signs in to their hosted virtual desktop (HVD). The processes stop when the session ends.

In a VMware environment, the Cisco Jabber Softphone for VDI processes start after the user signs in to their HVD and in to Cisco Jabber. The processes stop when the session ends.

Procedure

Step 1

On the thin client desktop, right-click the taskbar and then select Task Manager.

Step 2

On the Processes tab, scroll down and look for the vxc.exe process.

Verify That Cisco JVDI Agent Is Installed

You can use the Windows Control Panel to verify that Cisco JVDI Agent is installed. You can also verify the version.

Procedure

Step 1

From Control Panel, open Programs and Features (Windows 7) or Programs (Windows 8 and later).

Step 2

Scroll through the list of installed programs to locate Cisco JVDI Agent.

The Cisco JVDI Agent version appears in the Versions column.

Confirm the Version of Cisco JVDI Client

Cisco JVDI Client appears in the list of installed programs and features.

Procedure

Step 1

Step 2

On the thin client, open Control Panel > Programs and Features.

Step 3

Scroll down the list and locate Cisco JVDI Client.

Step 4

To confirm the version for Cisco JVDI Client, see the Version column.

Call Control Is Lost After a Network Failure

Users see a prompt to reconnect to their hosted virtual desktops (HVDs). After the users reconnect, Cisco Jabber call control features do not work.

This problem can occur if the thin client loses network connectivity.

To resolve this issue, have the users exit Cisco Jabber and disconnect from their HVDs. Next they can log back in to their HVDs and sign back in to Cisco Jabber to restore call control.

Call Is Lost After HVD Disconnection

Users receive a prompt to log back in to their hosted virtual desktops (HVD) during an active call, and the call drops. The other party to the call has no indication that the call has ended, except the line is silent.

This issue can occur if the connection between the thin client and the HVD drops, causing a temporary loss of registration and call control.

To work around this issue, users can call the other party back. If the other party is not available, users can send an instant message (IM).

Enable Log Collection

You can modify the Cisco configuration file (cisco.conf) to enable the collection of logs from the thin client.

The cisco.conf file is located in: C:\Program Files (x86)\Cisco Systems\Cisco VXME\cisco.conf

Procedure

Step 1

Open the cisco.conf file and add the following lines:

[logger]

log_level = Debug

You can set the log level to one of the following values: Fatal, Error, Warning, Info, Debug or Trace. The default level is Debug.

Step 2

Save the file.

Step 3

Restart the vxc process by logging out and back in to the HVD.

Enable Memory Dump Collection

You can modify the Cisco configuration file (cisco.conf) to enable the Problem Reporting Tool (PRT) to collect a memory dump.

For Windows 32-bit, the cisco.conf file is located in C:\Program Files (x86)\Cisco Systems\Cisco VXME\cisco.conf.

For Windows 64-bit, the cisco.conf file is located in C:\Program Files\Cisco Systems\Cisco VXME\cisco.conf.

Procedure

Step 1

Open the cisco.conf file and add the following lines:

[logger]

dump_type = Minidump
dump_when_collect_log = True

You can set the dump_type to Fulldump or Minidump. The default is Minidump. If dump_when_collect_log is set to False, the PRT doesn't collect the memory dump.

Step 2

Save the file.

Step 3

Restart the vxc process by logging out and back in to the HVD.

Chapter 7. Troubleshooting—Unicon eLux

- Verify the Platform Base Image Version

- Verify the Connection Status in Cisco Jabber

- Verify That Cisco JVDI Client Is Installed

- Verify That Cisco JVDI Agent Is Installed

- Verify That VXC Is Running on the Thin Client

- Call Control Is Lost After a Network Failure

- Call Is Lost After HVD Disconnection

Verify the Platform Base Image Version

Procedure

Step 1

On the Start menu, select Control Panel.

Step 2

Select the Setup tab.

Step 3

Select the General tab and look for the OS line.

Verify the Connection Status in Cisco Jabber

After you sign in to Cisco Jabber for Windows, you can check the connection status for Jabber and for Cisco Softphone for VDI. You can also confirm the versions for the JVDI Agent and the JVDI Client.

Procedure

Step 1

Click to open the Settings Menu.

Step 2

Go to Help > Show connection status

Step 3

In the Connection Status window, click JVDI Details.

You can see the following information:

- JVDI Client version

Tip

If the JVDI Client version is 12.5 or 12.1, the client version doesn't appear until after the softphone connects.

- JVDI Agent version

- Virtual Channel status indicates whether communication between the JVDI Client andCisco Jabber is successful.

- SIP status indicates whether SIP communication with Cisco Unified Communications Manager is successful.

- Softphone CTI status indicates whether CTI communication is successful.

Tip

If the SIP status is Connected, but the Softphone CTI status is Not connected, check the CTI configuration in CUCM.

Step 4

To see detailed diagnostic information for Cisco Jabber, press Ctrl +Shift +D.

Verify That Cisco JVDI Client Is Installed

Use this procedure to verify that Cisco JVDI Client is installed, and to confirm the Cisco JVDI Client version.

Procedure

Step 1

On the Start menu, select Control Panel.

Step 2

Select the Setup tab.

Step 3

Select the General tab.

Step 4

Scroll down the list of packages and look for Cisco JVDI Client.

The add-on versions appear in the same line.

Verify That Cisco JVDI Agent Is Installed

You can use the Windows Control Panel to verify that Cisco JVDI Agent is installed. You can also verify the version.

Procedure

Step 1

From Control Panel, open Programs and Features (Windows 7) or Programs (Windows 8 and later).

Step 2

Scroll through the list of installed programs to locate Cisco JVDI Agent.

The Cisco JVDI Agent version appears in the Versions column.

Verify That VXC Is Running on the Thin Client

Cisco Jabber Softphone for VDI requires that the vxc process be running.

Procedure

Step 1

Use Secure Shell (SSH) to connect to the thin client.

Step 2

Search the running programs for vxc.

ps -ef | grep -r vxc

You should see the following lines:

admin@LWT44d3ca76ba19:~> ps -ef |grep -r vxc

thinuser 6536 1 0 Mar14 ? 00:07:43 /bin/bash /usr/bin/pidrun.sh -c run_vxc.sh -a -m -o /var/log/cisco/vxcConsole.log -e /var/log/cisco/vxcError.log

thinuser 6538 6536 0 Mar14 ? 00:00:00 /bin/bash /usr/bin/run_vxc.sh -m

thinuser 6547 6538 8 Mar14 ? 13:02:16 vxc -m

admin 31576 31303 0 11:05 pts/0 00:00:00 grep -r vxc

admin@LWT44d3ca76ba19:~>

Call Control Is Lost After a Network Failure

Users see a prompt to reconnect to their hosted virtual desktops (HVDs). After the users reconnect, Cisco Jabber call control features do not work.

This problem can occur if the thin client loses network connectivity.

To resolve this issue, have the users exit Cisco Jabber and disconnect from their HVDs. Next they can log back in to their HVDs and sign back in to Cisco Jabber to restore call control.

Call Is Lost After HVD Disconnection

Users receive a prompt to log back in to their hosted virtual desktops (HVD) during an active call, and the call drops. The other party to the call has no indication that the call has ended, except the line is silent.

This issue can occur if the connection between the thin client and the HVD drops, causing a temporary loss of registration and call control.

To work around this issue, users can call the other party back. If the other party is not available, users can send an instant message (IM).

Chapter 8. Troubleshooting—HP Thin Pro and Ubuntu

- Verify the Platform Version—HP Thin Pro

- Verify the Platform Version—Ubuntu

- Verify the Connection Status in Cisco Jabber

- Verify That the Cisco JVDI Client Is Installed

- Verify That Cisco JVDI Agent Is Installed

- Verify That VXC Is Running on the Thin Client

- Call Control Is Lost After a Network Failure

- Call Is Lost After HVD Disconnection

Verify the Platform Version—HP Thin Pro

Procedure

Step 1

On the thin client, open the terminal console.

Step 2

Enter the following command: lsb_release -a .

Step 3

Look in the output for the HP Thin Pro version.

Example:

HP Thin Pro 5.2

Verify the Platform Version—Ubuntu

Procedure

Step 1

On the thin client, open System Settings.

Step 2

Select Details.

The version appears under the Ubuntu logo.

Example:

Ubuntu 14.04.x 32b LTS

Verify the Connection Status in Cisco Jabber

After you sign in to Cisco Jabber for Windows, you can check the connection status for Jabber and for Cisco Softphone for VDI. You can also confirm the versions for the JVDI Agent and the JVDI Client.

Procedure

Step 1

Click to open the Settings Menu.

Step 2

Go to Help > Show connection status

Step 3

In the Connection Status window, click JVDI Details.

You can see the following information:

- JVDI Client version

Tip

If the JVDI Client version is 12.5 or 12.1, the client version doesn't appear until after the softphone connects.

- JVDI Agent version

- Virtual Channel status indicates whether communication between the JVDI Client andCisco Jabber is successful.

- SIP status indicates whether SIP communication with Cisco Unified Communications Manager is successful.

- Softphone CTI status indicates whether CTI communication is successful.

Tip

If the SIP status is Connected, but the Softphone CTI status is Not connected, check the CTI configuration in CUCM.

Step 4

To see detailed diagnostic information for Cisco Jabber, press Ctrl +Shift +D.

Verify That the Cisco JVDI Client Is Installed

Use this procedure to verify that Cisco JVDI Client is installed, and to confirm the version.

Procedure

Step 1

On the thin client, open the terminal console.

Step 2

Enter the following command: dpkg -l | grep jvdi .

Step 3

In the output, look for ii cisco-jvdi-client.

Example:

ii cisco-jvdi-client <xx.x.x.xxx> i386 Cisco JVDI Client

Verify That Cisco JVDI Agent Is Installed

You can use the Windows Control Panel to verify that Cisco JVDI Agent is installed. You can also verify the version.

Procedure

Step 1

From Control Panel, open Programs and Features (Windows 7) or Programs (Windows 8 and later).

Step 2

Scroll through the list of installed programs to locate Cisco JVDI Agent.

The Cisco JVDI Agent version appears in the Versions column.

Verify That VXC Is Running on the Thin Client

Cisco Jabber Softphone for VDI requires that the vxc process be running.

Procedure

Step 1

Use Secure Shell (SSH) to connect to the thin client.

Step 2

Search the running programs for vxc.

ps -ef | grep -r vxc

You should see the following lines:

admin@LWT44d3ca76ba19:~> ps -ef |grep -r vxc

thinuser 6536 1 0 Mar14 ? 00:07:43 /bin/bash /usr/bin/pidrun.sh -c run_vxc.sh -a -m -o /var/log/cisco/vxcConsole.log -e /var/log/cisco/vxcError.log

thinuser 6538 6536 0 Mar14 ? 00:00:00 /bin/bash /usr/bin/run_vxc.sh -m

thinuser 6547 6538 8 Mar14 ? 13:02:16 vxc -m

admin 31576 31303 0 11:05 pts/0 00:00:00 grep -r vxc

admin@LWT44d3ca76ba19:~>

Call Control Is Lost After a Network Failure

Users see a prompt to reconnect to their hosted virtual desktops (HVDs). After the users reconnect, Cisco Jabber call control features do not work.

This problem can occur if the thin client loses network connectivity.

To resolve this issue, have the users exit Cisco Jabber and disconnect from their HVDs. Next they can log back in to their HVDs and sign back in to Cisco Jabber to restore call control.

Call Is Lost After HVD Disconnection

Users receive a prompt to log back in to their hosted virtual desktops (HVD) during an active call, and the call drops. The other party to the call has no indication that the call has ended, except the line is silent.

This issue can occur if the connection between the thin client and the HVD drops, causing a temporary loss of registration and call control.

To work around this issue, users can call the other party back. If the other party is not available, users can send an instant message (IM).

Chapter 9. General Troubleshooting

- Problem Reporting Tool

- Verify Device Registration with Cisco Unified Communications Manager

Problem Reporting Tool

The Problem Reporting Tool (PRT) is a small program that automatically runs if Cisco Jabber encounters an unrecoverable error, unhandled exception, or crash. The tool collects logs from the thin client and hosted virtual desktop and then creates a problem report. The report is a zip file that you can send to the Cisco Technical Assistance Center (TAC), to provide the necessary information to solve the problem. The tool saves the file to the user's desktop. Users must accept the privacy agreement to run the PRT.

Tip

Advise users to include a memory dump with the problem report if Cisco Jabber crashes. We also recommend that users provide a description of the circumstances that lead up to the error.

If a user experiences an error that does not crash the software, the user can run the PRT from the Cisco Jabber menu: Help > Report a problem.

If Cisco Jabber is not running, users can generate a problem report from the Windows Start menu . To access the tool from outside the application, choose Start > All Programs > Cisco Jabber > Cisco Jabber Problem Report.

Important

Problem reports include logs from the thin client, the hosted virtual desktop, and any detailed information that users enter. You can use this information to help troubleshoot the issue.

If there is a problem with the virtual channel, or if Cisco Jabber is not running, the problem report does not include logs from the thin client. For more information, see Virtual Channel Problem.

- Virtual Channel Problem

Virtual Channel Problem

If a problem exists with the virtual channel, the problem-reporting tool cannot collect the logs from the thin client. A problem with the virtual channel can cause the Device Selector to not start or to not populate with devices.

Cisco Technical Assistance Center (TAC) personnel may ask you to gather the logs manually by running one of the following executables:

- Windows OS 32-bit: C:\Program Files (x86)\Cisco Systems\Cisco JVDI\CollectCiscoJVDIClientLogs.exe

- Windows OS 64-bit: C:\Program Files\Cisco Systems\Cisco JVDI\CollectCiscoJVDIClientLogs.exe

- Linux-based OS: /usr/bin/collect-files

The executable gathers the logs from the thin client and saves them to the desktop as a CiscoJVDIClient-logs[timestamp].7z file. You can still use the PRT to gather the logs from the hosted virtual desktop. Submit all logs gathered to TAC.

Configuration Files

For each Cisco Unified Client Services Framework (CSF) device that you add to the system, Cisco Unified Communications Manager creates a configuration (CNF.xml) file. The CNF file contains the device specifications for the associated user.

When users sign in to Cisco Jabber, Cisco Jabber Softphone for VDI starts the download of the associated CNF file to the thin client. To ensure the successful transfer of the file, open the relevant ports in all firewall applications to allow the thin client to access the ports. For more information about how to open ports, see the documentation for the firewall software.

Important

Download of the CNF.xml file follows the system setting for HTTP proxy. Ensure that the proxy does not route the HTTP request from the thin client outside of the corporate network.

Verify Device Registration with Cisco Unified Communications Manager

After device registration, verify that the CSF device registered to the Cisco Unified Communications Manager from the thin client IP address. For more information, see the documentation for your version of Cisco Unified Communications Manager.

New and Changed Information

- New and Changed Information

New and Changed Information

Date

Status

Description

Location

January, 2020

Changed

Removed the requirement to reinstall the Cisco JVDI Client for Windows, after upgrading your Citrix or VMware product. (CSCvs73031)

Requirements—Windows Thin Clients

Changed

Updated Citrix Virtual Apps and Desktops support to address CSCvs67124.

General Requirements

November, 2019

Changed

Added a data flow illustration to address CSCvr99526.

Cisco Jabber Softphone for VDI

October, 2019

New

Added a new topic to address CSCvr84303.

Verify Device Registration with Cisco Unified Communications Manager

September, 2019

Changed

Updated parameter name: HeadsetPreferenceOnVDI.

The User Experience

New

Initial publication. This restructured guide covers all Cisco Jabber Softphone for VDI platforms.

Full Cisco Trademarks with Software License

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.

All printed copies and duplicate soft copies of this document are considered uncontrolled. See the current online version for the latest version.

Cisco has more than 200 offices worldwide. Addresses and phone numbers are listed on the Cisco website at www.cisco.com/go/offices.

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. (1721R)