This guide provides information about the following topics:

• Installing and configuring Cisco Jabber Softphone for VDI for Windows

• Installing and configuring Cisco AnyConnect Secure Mobility Client in a Cisco Jabber Softphone for VDI for Windows deployment

• Upgrading Cisco Jabber Softphone for VDI for Windows

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

With Cisco Jabber Softphone for VDI, thin client users can place and receive calls with their Cisco Unified Communications application (Cisco Jabber). Cisco Jabber Softphone for VDI consists of the Cisco JVDI Agent and the Cisco JVDI Client. 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 supports some audio and video 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.

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

A Cisco Jabber Softphone for VDI deployment consists of the following components:

• Supported Windows thin clients.

  For more information about supported thin clients, see Release Notes for Cisco Jabber Softphone for VDI for Windows.

• Cisco JVDI Client installed on the thin client.

• Windows hosted virtual desktops (HVD), in a data center.

  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.

• Cisco Jabber installed on the HVD.

• Cisco JVDI Agent installed on the HVD.

• Cisco Unified Communications Manager.

The user experience, with Cisco Jabber Softphone for VDI and a supported Cisco Unified Communications client, is similar to the experience provided by a standard 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.

• Cisco Jabber can control a Cisco IP Phone or use the computer to make and receive calls. The default phone selection is Use my computer for calls. After device selection, the Cisco Jabber Softphone for VDI application starts the transfer of the phone configuration data for that user. For more information, see Configuration Files.

• Use the Device Selector, which is located in the Windows notification area, to manage camera and audio devices. Device management is also available from within the Cisco Unified Communications client.

• By default, all calls send and receive video if both parties have video capability. The available options are:

  • 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 placed and received. The default setting is Always start calls with video.

  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 are different in a virtual deployment. For example, Video Desktop Share (Binary Floor Control Protocol) is not available from the call window. Video Desktop Share is supported only from the IM-chat window (Remote Desktop Protocol).