Cisco Jabber UC Services

This topic describes the Cisco Unified Communications Services applications and protocols.

You may select up to three servers for each Cisco Unified Communications Services in the service profile.

  • You cannot mix different applications for one Cisco Unified Communications Services.
Cisco Unified Communications Services Application Protocol
Mailstore Exchange TCP, SSL, TLS, or UDP
Voicemail Unity or Unity Connection HTTP, HTTPS
Conferencing WebEx HTTP, HTTPS
Directory Directory, Enhanced Directory TCP, UDP, TLS
IM and Presence Unified CM (IM and Presence), WebEx (IM and Presence) XMPP
CTI TCP
Video Conference Scheduling Portal TelePresence Management System HTTP, HTTPS

Presence is enabled per user in the user configuration. In addition, you must specify a service profile. Via this service profile and the Cisco Unified Communications Services selected in the profile, you can add feature access to Cisco Jabber.

To allow Cisco Jabber to present voice messages in a graphical form, you must configure the voicemail service for Cisco Unity Connection using HTTP or HTTPS. In addition, you need to specify the mailstore, which enables visual access to voice messages. Cisco Unity creates subscriber mailboxes for message storage on the Microsoft Exchange server. Cisco Unity Connection provides a mailstore service and hosts the mailstore service on the same server.

When integrating Cisco MeetingPlace Express, Cisco MeetingPlace Classic, or Cisco WebEx, create a conferencing service using HTTP or HTTPS. In addition, you can add a conference scheduling portal as a service.

When adding a directory service, Cisco Jabber can connect to the Microsoft Active Directory server for contact search and number-to-name resolution. However, not all clients can use this service. For Cisco Jabber for Windows, you need to deploy an additional jabber-config.xml file. If you select UDS–Enhanced Directory for directory integration, then you can use Cisco User Data Service (UDS) for directory searches without selecting any primary, secondary, or tertiary servers. Clients connect to Cisco UDS using DNS SRVs.

The IM and Presence service specifies the Cisco Unified Communications IM and Presence server addresses (using XMPP), and the CTI service specifies Cisco Unified Communications Manager with CTIManager service activated.

Advertisements

Legacy Client Settings

This topic describes the TFTP and Cisco Unified Communications Manager IP Phone (CCMCIP) profiles that are configured on Cisco Unified Communications IM and Presence Service node.

On Cisco Unified Communications IM and Presence Service node, choose Applications > Legacy Client > Settings.

  • Choose the Proxy Listener.
  • Set the primary TFTP server to the Cisco Unified Communications Manager TFTP server IP address.

On Cisco Unified Communications IM and Presence Service node, choose Applications > Legacy Client > CCMCIP Profile.

  • Set the primary and secondary CCMCIP Host.
  • Make the profile the default.

In Cisco Unified Communications IM and Presence Service node, choose Applications > Legacy Client > Settings, and set the primary TFTP server to the IP address of the Cisco Unified Communications Manager that is hosting the TFTP server. If available, configure a backup TFTP server address. Cisco Jabber connects to the primary TFTP server. When the connection is established, Cisco Jabber downloads the configuration file from Cisco Unified Communications Manager.

The configuration file contains the list of Cisco Unified Communications Manager primary and failover server addresses. The configuration file also contains the transport protocol for Cisco Jabber to use in softphone mode to connect to Cisco Unified Communications Manager. After Cisco Jabber downloads the file successfully, the configuration information is made available to other Cisco Jabber subsystems.

Each time Cisco Jabber tries to download the configuration file, the application attempts to contact the primary TFTP server. If the primary TFTP server does not respond, Cisco Jabber fails over to the backup TFTP servers, if any exist. Cisco Jabber fails over to the backup TFTP servers in the order that is specified in Cisco Unified Communications IM and Presence Administration. If all TFTP server connections fail, Cisco Jabber tries to load the last valid downloaded configuration from the local hard disk.

Choose Application > CCMCIP Profile, and add a new profile. Enter a name for the CCMCIP Profile, and define the primary CCMCIP and backup CCMCIP hosts. Both fields are mandatory. This profile offers a list of associated devices to Cisco Jabber when it is used in deskphone mode. However, this profile must be created, even if you only use softphone mode in Cisco Jabber; otherwise, the client does not successfully register.

Cisco Jabber in Phone-Only and Softphone Modes

This topic describes how to set up Cisco Jabber for phone-only mode without a Cisco Unified Communications IM and Presence Service node.

  • Configure Cisco Jabber in phone-only mode:
    1. Cisco Unified Communications IM and Presence Service node is not required.
    2. Presence and IM features are not available.
  • Checklist for phone-only mode configuration:
    1. Add a new end user, and do not enable presence.
    2. Add a new Cisco Unified CSF device; set the mandatory parameters and the owner ID.
    3. Add the DN, the route partition, and other mandatory settings.
  • Install Cisco Jabber:
    1. Set the account type to Automatic.
    2. Log in with the UserPrincipalName to discover the service domain.
  • The following are not available in phone-only mode:
    1. Desk phone control is not available.
    2. There is no LDAP server connection available for contact search.
    Note

    CSF = Client Services Framework

The figure lists the steps that are required to set up Cisco Jabber in phone-only mode. Cisco Jabber registers with Cisco Unified Communications Manager using SIP. In phone-only mode, features like IM, presence, and directory access are not available.

Follow the configuration checklist to set up Cisco Jabber in phone-only mode.

Note

Do not enable presence for users or devices in phone-only mode.

Configure Cisco Jabber in Softphone Mode

This topic describes how to configure Cisco Jabber to run in softphone mode.

Cisco Jabber in softphone mode must be configured on Cisco Unified Communications Manager:

  • Configure the end user.
    1. Create and associate the new Cisco Unified CSF device.
    2. Set the primary extension.
    3. Enable User for Unified CM IM and Presence.
  • Add a new device.
    1. Add a Cisco Unified CSF device.
    2. Name has no restrictions, so you do not have to use CSFNAME.
    3. Add the user as owner of the device, and set the primary phone.
    4. Add the DN, and associate a user with the line.
    5. Device will register with Cisco Unified Communications Manager using SIP.
  • Add Legacy Client Configuration (TFTP and CCMCIP profile).
  • Configure UC Profiles and Service Profile for presence functionality.

In Cisco Unified Communications Manager Administration, create a Cisco Unified Client Services Framework (CSF) device. This device is used by Cisco Jabber in softphone and deskphone mode. For deskphone mode, additional CTI configuration is required. The main difference is the registration. In softphone mode, Cisco Jabber registers with Cisco Unified Communications Manager using SIP. In deskphone mode, Cisco Jabber registers with Cisco Unified Communications IM and Presence using XMPP and controls the desk phone via CTIQBE.

Follow the checklist that is presented in the figure to set up a Cisco Unified CSF device for Cisco Jabber in softphone mode.

When the Cisco Unified CSF device is created, add the DN of the phone or device profile of the user to the new device. The DN is a shared line, and the devices that are sharing this number are listed under associated devices. After saving, associate the end user with the line by clicking the Associate End Users button. This action is important, because the presence status is shown per line, not per device status.

Next, associate the Cisco Unified CSF device with the end user. When the Cisco Unified CSF device is successfully created, associate the device to the end user configuration. Choose User Management > End User, and select the user. Click Device Association, search for the previously created Cisco Unified CSF device, and click Add Selected. The device is now displayed in the Controlled Devices list. After the association is done, the primary line can be selected.