Cisco Jabber in Deskphone Mode

This topic describes how to configure desk phone control for Cisco Jabber.

Enable End Users and Devices for CTI

The Standard CTI Enabled group or a customized group must be added for every Cisco Unified IP phone type.

  • Choose the Standard CTI Allow Control of Phones supporting Rollover Mode group for the Cisco Unified IP Phone 6900 Series.
  • Choose the Standard CTI Allow Control of Phones supporting Connected Xfer and conf group for the Cisco Unified IP Phone 8900 and 9900 Series.

CTI must be enabled for end users to use Cisco Jabber to control the desk phone. In the end-user configuration window, go to the Permissions Information configuration. To allow CTI control in deskphone mode, add the user to the appropriate groups:

  • For all IP phone types, add the user to the Standard CTI Enabled group.
  • For the Cisco Unified IP Phone 6900 Series, also add the user to the Standard CTI Allow Control of Phones Supporting Rollover Mode group.
  • For the Cisco Unified IP Phone 8900 and 9900 Series, add the user to the Standard CTI Allow Control of Phones Supporting Connected Xfer and Conf group.

Verify that the box Allow Control of Device from CTI is checked on the user configuration page. This setting is the default. The device and directory number must be enabled for CTI as well. In Cisco Unified Communications Manager Administration, go to the phone of the end user. Verify that the Allow Control of Device from CTIcheck box is checked. Then, go to the directory number configuration and verify that the same box is checked.

A UC Service for CTI is required. Add a new UC Service for CTI, and enter the IP address of the Cisco Unified Communications Manager where you enabled the Cisco CTIManager service. The port is set to 2748 by default. Then, go to the service profile, where you can set a maximum of three servers for CTI service.

Cisco Jabber in Deskphone Mode

 This topic explains how Cisco Jabber functions in deskphone mode.
  • Dial the number in Cisco Jabber to start the call on your selected phone.
  • Forwarding a call, even to voicemail, requires configured CSSs.

After setting up the CTI configuration, switch Cisco Jabber from softphone mode to deskphone mode. This mode can also be used with virtualized desktops, because Cisco Jabber uses the phone to initiate the call and the call is done using the phone.

The Cisco Unified Communications Manager IP Phone (CCMCIP) profile acquires the associated device list information from Cisco Unified Communications Manager when going into deskphone mode. (Choose the option Use my phone for calls.) When a phone can be controlled with Cisco Jabber, the CTI gateway profile is used. To dial a number, type the digits into the Search or call field. The phone of Jane White will start the call and go into loudspeaker mode.

Advertisements

LDAP and Voicemail Profile Test

This topic describes how to test the LDAP server and add contacts in Cisco Jabber.

Test the LDAP profile:

  • In Cisco Jabber, enter a name in the Search field to search for a user that is located on the LDAP server.
  • In this example, search with the letter “j.”
    1. Three users are found starting with “j.”
    2. Mouse over a user and add the user to the contact list.

In Cisco Jabber, you can search for a user that is located on the LDAP server, but is not located in Cisco Unified Communications Manager, to test the LDAP profile. In this example, the search string is only one character, “j.” The search result displays three users.

Note

The search tool of the Jabber Client searches for contacts in the locally entered repository (Jabber) or in the repository of the directory service that is configured. The results indicate in which repository the user was found—for instance, Contact and recent, or Directory

Note

When you enter the search string, be aware that for the new LDAP queries, at least three characters are required. This means that the results to search strings one character long can include only locally defined contacts or results from previously performed queries. This can be easily verified, by adding new users either locally or at the directory. Check what the search results indicate as the source of information when entering less than three and subsequently when entering at least three characters..

Displaying these results shows you that the LDAP profile is correctly applied. Mouse over the search results and click the plus sign (+) to add the user to the contact list. When adding the first user, you must create a group—for example, Cisco. Then, you can add the user to the contact list for that group. When you add the first user, make sure that offline users are also shown in the contact list to avoid having to troubleshoot a situation where the issue does not really exist.

Note

Cisco Jabber for Windows requires a jabber-config.xml file that includes the information that is necessary to reach the LDAP server. If you configure only the UC Service in the service profile without the jabber-config.xml file, you will not be able to search for contacts in the Microsoft Active Directory server.

Voicemail Profile Test

This topic describes how to test the voicemail profile in Cisco Jabber using the visual interface to access voice messages.

Test the voicemail profile:

  • Leave a message.
  • Receive the message with Cisco Jabber.
  • Call voicemail from Cisco Jabber.

In Cisco Jabber, the Voicemail button indicates new voice messages. In this example, there is one new voice message. Click the Voicemail button to use visual voicemail. The voice message list is shown. One new message from Jane White (2002) is shown in the figure.

Click the play message icon to listen to the voice message. If you right-click the voice message entry as shown in the figure, then you can choose to perform the following actions:

  • Place a call to 2002.
  • Chat with John.
  • Mark as read or unread; this action synchronizes the MWI.
  • Delete the message.

Connection Status

This topic presents the Cisco Jabber connection status tool.

  • In Cisco Jabber, go to Help > Show Connection Status.
  • In this example, the client has connected to:
    1. Cisco Unified Communications Manager in softphone mode
    2. Cisco Unity Connection for visual voicemail
    3. Cisco Unified Communications IM and Presence Service for presence information
    4. LDAP for directory search

In Cisco Jabber, you can use the connection status tool to see a status overview of the configured and assigned Cisco Unified Communications Services. As shown in the figure, you can easily spot issues, where an incorrect hostname, IP, or port is configured. If there is an error, an error code describes the issue that is occurring with that specific UC Service.

Choose Help > Show Connection Status in Cisco Jabber. The tool shows the status for LDAP, Presence, Deskphone, and others. The green check marks indicate that the modules are correctly set up. A blue circle with an exclamation mark is informational, describing, for example, that deskphone video is not available in softphone mode. An orange triangle with an exclamation mark (not shown in the figure) shows an error. The Reason field provides additional information when an error occurs. In the example in the figure, the reason is “Deskphone video is not available in softphone mode.”

Cisco Jabber Account Options

This topic describes the phone account options that Cisco Jabber presents if the service profile is configured.

Configure the Cisco Jabber options:

  • The phone accounts appear only if the user has certain Cisco Unified Communications Services configured—for example, a voicemail UC Service in the configured service profile.
  • Voicemail and conferencing profiles can share the user credentials.
  • Calendar integration can also be configured.

A Cisco Jabber option Account—for example, for voice messaging—appears only if the corresponding UC Service is configured. The Cisco Jabber menus are dynamic and show only account options for which a UC service is configured.

End users must provide the credentials in Cisco Jabber for the account that they are configuring—for example, voicemail or conferencing. In the example in the figure, a voicemail service was configured. The user must enter the Cisco Unity Connection local password if the voicemail service is imported from Cisco Unified Communications Manager and the LDAP credentials if the voicemail service is imported from the LDAP server.

For voicemail and conferencing, you can set the Credentials Source parameter so that the voicemail service can share user credentials with other services. If you want to share the voicemail service user credentials with another service, select the appropriate service from the Credentials Source list. The user credentials are automatically synchronized with the services that you select. The credentials can be entered for voicemail, conferencing, and LDAP. Other profiles are transparent to end users. In addition, the user can configure calendar integration.

Cisco Jabber in Softphone Mode

This topic describes Cisco Jabber in softphone mode.

  • Set the Network Connection parameters to Automatic.
  • Log in with user domain credentials.
  • Make test calls.

Start Cisco Jabber, enter the UserPrincipalName (UPN), and set the account type to Automatic. The service domain is discovered first, followed by the network services. Enter your mail address to receive the IP address of the Cisco Unified Communications Manager. When Cisco Jabber tries to connect to Cisco Unified Communications Manager, you must authenticate with user credentials, which in most cases are the domain username and password when LDAP integration and authentication is set up.

The figure shows the Cisco Jabber client trying to call the phone 2002 in softphone mode. You can simply enter a phone number in the search field. However, CoS applies here as well. If you did not configure a CSS for the client, you cannot make any calls. Starting a video might not be shown as an option if the client PC does not have a camera.

Visual Voicemail Interface for Cisco Jabber

This topic describes how Cisco Jabber can access voice messages and present them in Cisco Jabber in a visual interface.

In Cisco Unity Connection, choose Class of Service > Class of Service.

  • Enable Cisco Jabber to access voice messages.
  • Only LDAP-imported users can use LDAP credentials in Cisco Jabber for authentication.

In Cisco Unity Connection, choose Class of Service > Class of Service. Select, for example, the default class of service Voice Mail User CoS, which is used by all end users. Enable Cisco Jabber to access voice messages, and check the following boxes:

  • Allow Users to Access Voice Mail Using an IMAP Client: Check this check box to give users who are assigned to this CoS access to voice messages by using an IMAP client. The check box is not checked by default. When this check box is checked, you must also check one of the following options:
    1. Allow Users to Access Message Bodies: Users have access to the entire voicemail.
    2. Allow Users to Access Message Bodies Except on Private Messages: Users have access to the entire voicemail, unless the message is marked private, in which case they have access only to the message header.
    3. Allow Users to Access Message Headers Only: Users have access only to message headers.
Note

Encrypted message bodies cannot be accessed from an IMAP client.

  • Allow Users to Use Unified Client to Access Voice Mail: Check this check box to give users who are assigned to this CoS access to voice messages via Cisco Jabber.

Upload Jabber Config File to TFTP Server

Use the Jabber Config File Generator to generate the correct XML file. The generator can be found at: https://supportforums.cisco.com/docs/DOC-25778.

For the directory search to work, upload the XML file jabber-config.xml.

  • Download the Jabber Config File Generator.
  • Additional features such as URI dialing and others are enabled with this file generator as well.
<?xml version="1.0" encoding="utf-8"?>
<config version="1.0">
 <Options>
   <Set_Status_Away_On_Inactive>false</Set_Status_Away_On_Inactive>
 </Options>
 <Directory>
   <ConnectionType>1</ConnectionType>
   <PrimaryServerName>10.1.5.14</PrimaryServerName>
   <BDIPrimaryServerName>10.1.5.14</BDIPrimaryServerName>
   <ServerPort1>389</ServerPort1>
   <BDIServerPort1>389</BDIServerPort1>
   <UseWindowsCredentials>0</UseWindowsCredentials>
   <ConnectionUsername>Administrator@collab10x.cisco.com</ConnectionUsername>
   <BDIConnectionUsername>Administrator@collab10x.cisco.com</BDIConnectionUsername>
   <ConnectionPassword>Cisco1234</ConnectionPassword>
   <BDIConnectionPassword>Cisco1234</BDIConnectionPassword>
</Directory>
</config>

The generator renders the proper jabber-config.xml file for you after you answer a few questions in an easy-to-use form. Then, you can simply copy and paste the result into an XML file. The generator has built-in logic, which verifies that you are entering the correct information for the deployment selected, as well as valid XML characters.

The figure shows an example XML file with the Jabber Config File Generator-generated content. The example XML file connects to a Microsoft Active Directory server with the IP address 10.1.5.14 and the port 389. The user name is Administrator@collab10x.cisco.com, and the password is Cisco1234. Because the network services are discovered, you do no need to specify a Cisco Unified Communications Manager IP address. In previous Cisco Unified Communications IM and Presence Service versions, the Cisco Unified Communications IM and Presence Service node was contacted first. With Cisco Unified Communications IM and Presence Service Release 10.x, the Cisco Jabber client contacts Cisco Unified Communications Manager first and receives the necessary information from the device-specific configuration file and the jabber-config.xml file.

The XML file structure is rendered in JavaScript, so you still need to paste the contents into a text file (saved as an XML file) and upload the file to the Cisco Unified Communications Manager TFTP server, using exactly the same name jabber-config.xml. Without this XML file, the Cisco Jabber for Windows client will not support the directory search for end users. Other features, such as URI dialing, are also enabled in the Jabber Config File Generator.