Cisco Jabber for Windows 9.2.1 Release Notes
Release Information
Downloads: This chapterpdf (PDF - 1.15MB) The complete bookPDF (PDF - 1.97MB) | The complete bookePub (ePub - 117.0KB) | Feedback

Release Information

Release Information

Documentation Resources

Installation and Configuration Guide

The Installation and Configuration Guide contains the following information:
  • System and network requirements
  • Hardware requirements
  • Supported software and devices
  • Information to help you plan your deployment
  • Installation procedures
  • Client configuration requirements and information

Find the Installation and Configuration Guide for each release at http:/​/​www.cisco.com/​en/​US/​products/​ps12511/​prod_​installation_​guides_​list.html

Server Setup Guide

The Server Setup Guide provides task-based information to help you configure services for the client. This guide is available at http:/​/​www.cisco.com/​en/​US/​products/​ps12511/​prod_​installation_​guides_​list.html

Licensing Information

Find out what open source libraries and other licensing information at http:/​/​www.cisco.com/​en/​US/​products/​ps12511/​products_​licensing_​information_​listing.html

New in this Release

Find out what's new in the latest release.

Phone Mode

You can deploy the client in phone mode so that the primary authentication for users is to Cisco Unified Communications Manager. In phone mode deployments, you provision users with audio and video capabilities as base functionality without instant messaging and presence capabilities.

To deploy the client in phone mode, specify the PRODUCT_MODE argument during installation. You can also specify additional server addresses during installation or in the client configuration file with the following:
Installation argument Configuration parameter
TFTP TftpServer1
CTI CtiServer1
CCMCIP CcmcipServer1
If you plan to provision users with voicemail capabilities, specify the following configuration parameters:
  • VVM_Mailstore_Server_0
  • VVM_Mailstore_PollingInterval

See the Cisco Jabber for Windows Installation and Configuration Guide for more information about deploying the client in phone mode.

Known Issues with Phone Mode

  • Cisco Jabber for Windows does not currently support changing product mode from a Full UC or Cisco Jabber for Everyone (IM Only) deployment to a phone mode deployment. This issue is resolved in a future version with CSCug54512.
  • Contact resolution with UDS is not available in this release. This issue is resolved in version 9.2.2 with CSCug71071.

Meetings Integration

Cisco Jabber for Windows does not currently support meetings integration in phone mode deployments. You cannot provision users with conferencing functionality if you deploy the client in phone mode.

Ability to Save Chats to File

As of this release, users can save chat transcripts to HTML files. Users can save transcripts from individual and group chats.

To save a chat transcript, users right-click in the Conversations window and select Save chat.

The Microsoft Windows Save As dialog then prompts users to select a location on the file system to save the chat transcript. The client saves chat transcripts to the My Documents folder by default.

Per Session Chat History

As of this release, the client saves chat history for each login session if you disable chat history.

If you enable chat history, the client persists chat history to the local client disk. When users restart the client or sign out, chat history is available on subsequent logins.

If you disable chat history, the client saves chat history for each login session. When users restart the client or sign out, no chat history is available from previous sessions. An example of chat history across sessions is as follows:
  1. User A signs in.
  2. User A starts a chat with user B.
  3. User A closes the Conversations window.
  4. User A starts a new chat with user B. The chat history from the previous session is available in the Conversations window.
  5. User A signs out. When user A signs in again no chat history is available.

Icons for Instant Messaging Encryption

The client displays different icons to indicate when instant messages are encrypted.

Lock Icon

In both on-premises and cloud-based deployments, the client displays a lock icon when it establishes a secure connection to the presence server.


Note


In on-premises deployments, you can disable XMPP security. In this case, the client does not display a lock icon because the connection to the presence server is not secure.

The setting to disable XMPP security is as follows:
Cisco Unified Presence

System > Security > Settings > Enable XMPP Client to CUP Secure Mode

Cisco Unified Communications IM and Presence

System > Security > Settings > Enable XMPP Client to IM/P Service Secure Mode


Padlock Icon

In cloud-based deployments, the client displays a padlock icon if:
  1. You enable client to client encryption.
  2. The client successfully establishes a secure connection with another client.

Installation Arguments

The following are the new installation arguments in this release:
  • PRODUCT_MODE
  • LOG_DIRECTORY

Configuration Parameters

Review all new configuration parameters for this release.

See the Cisco Jabber for Windows Installation and Configuration Guide for complete details about all configuration parameters.

Parameter Value Description
ProductMode

Default

Phone_Mode

Specifies the Cisco Jabber for Windows product mode. Set one of the following values:
Default

Set this value if Cisco Jabber for Windows users authenticate to a presence server as the primary login.

You should choose this value if you want to provision users with instant messaging and presence as base functionality.

Phone_Mode

Set this value if Cisco Jabber for Windows users authenticate to Cisco Unified Communications Manager as the primary login.

You should choose this value if you plan to provision users with audio devices as base functionality.

TftpServer1

IP address

Hostname

FQDN

Specifies the address of the primary Cisco Unified Communications Manager TFTP service where device configuration files reside. Set one of the following as the value:
  • Hostname (hostname)
  • IP address (123.45.254.1)
  • FQDN (hostname.domain.com)
You should set this parameter in the client configuration only if:
  • You deploy the client in phone mode.
  • The TFTP server address for the device configuration is different to the TFTP server address for the client configuration. During installation, you should set the address of the TFTP server where the client configuration file resides with the following argument: TFTP.
TftpServer2

IP address

Hostname

FQDN

Specifies the address of the secondary Cisco Unified Communications Manager TFTP service.

CtiServer1

IP address

Hostname

FQDN

Specifies the address of the primary CTI server.

You should specify a CTI server address in the client configuration if users have desk phone devices.

CtiServer2

IP address

Hostname

FQDN

Specifies the address of the secondary CTI server.

CcmcipServer1

IP address

Hostname

FQDN

Specifies the address of the primary CCMCIP server.

This parameter is required only if the address of your CCMCIP server is not the same as the TFTP server address. If the address of the CCMCIP server is the same as the TFTP server address, the client can use the TFTP server address to connect to the CCMCIP server.

CcmcipServer2

IP address

Hostname

FQDN

Specifies the address of the secondary CCMCIP server.

PresenceServerType

CUP

WebEx

Defines the type of presence server. Set one of the following values:
CUP
Cisco Unified Presence or Cisco Unified Communications IM and Presence
WebEx
Cisco WebEx Messenger
PresenceServerAddress

IP address

Hostname

FQDN

Specifies the address of your presence server. Set one of the following as the value:
  • Hostname (hostname)
  • IP address (123.45.254.1)
  • FQDN (hostname.domain.com)

You must specify a value for this argument if your presence server does not support domain name system service records (DNS SRV). For example, Cisco Unified Presence 8.5.2 does not support DNS SRV.

PresenceServerDomain Domain name

Identifies the domain name of the presence server. Specify the domain name as the value of this argument; for example, domain.com.

You must specify this argument if the domain of the presence server is not the same as the domain of the workstations on which the client is installed.

VVM_Mailstore_Server_0

IP address

Hostname

FQDN

Specifies the address of your mailstore server. Set one of the following as the value:
  • Hostname (hostname)
  • IP address (123.45.254.1)
  • FQDN (hostname.domain.com)
VVM_Mailstore_PollingInterval Number of seconds
Specifies the number of seconds between which the client polls the mailstore server for deleted messages.
0

The client does not poll the mailstore server.

The mailstore server does not notify the client when users delete voicemail messages. If you set 0 as the value, the client cannot detect when users delete voicemail messages. As a result, the client does not remove voicemail messages that users delete until the next time the users sign in.

1 or higher

The client polls the mailstore server at the interval you specify.

The default value is 60.