Discovery 19: Deploy an On-Premise Cisco Jabber Client for Windows

Introduction
In this lab, you will configure the pre-requisite services to deploy an on-premise Cisco Jabber client on a Windows
machine. These services include the UC Services, service profile, device association, permissions, and CSF
(Client Services Framework) Device.

This lab will take approximately 60 minutes to complete.

Topology

Task 1: Create UC Services and Service Profile

Activity
Jabber clients need to be able to reach several different applications to provide access to services such as
voicemail, meetings, directories, and other functions. Jabber determines the location of these services from the
service profile assigned to the Jabber client’s user. A service profile contains one or more UC services which are
configured with the parameters for a specific service such as voicemail or the LDAP directory.

You will only be using two UC Services in this discovery but a production deployment of Jabber would use more
depending on the feature available to the Jabber clients.

Step 1
From PC-1, open Chrome and navigate to https://10.1.5.5/ccmadmin and log in with username Administrator
and password C0ll@B.

Step 2
Select User Management > User Settings > UC Service.
Step 3
Click Add New.

Step 4
From the drop-down menu, select CTI then click Next. The CTI (Computer Telephony Integration) service you
are creating here notifies the Cisco Jabber client how to connect to the publisher for CTI functions. This CTI is
the only service required for Phone-only mode.

Notice that the drop-down menu has the other potential services that can be configured in order for Jabber to
offer more features for the user:
CTI: Allows end users to control devices from the Cisco Jabber interface (desktop mode).
Mailstore: Provides Cisco Jabber users with Visual Voicemail capabilities.

Cisco Unity Connection creates subscriber mailboxes on a Microsoft Exchange Server, so you should
point the mailstore service to the Exchange Server.
Cisco Unity Connection typically provides a mailstore service and hosts the mailstore service on the same
server. When using Cisco Unity Connection, you should point the mailstore service to this server.

Voicemail: Enables users to retrieve voicemails.

IM and Presence: Enables users to have instant messaging and presence capabilities.
Directory: Enables Cisco Jabber to integrate with LDAP servers for directory lookup purposes.
Video Conference Scheduling Portal: Allows integration with Cisco TMS.
Conferencing: Allows Cisco Jabber to integrate with Cisco Webex Meeting or Cisco Webex Meetings Server.
Step 5
Fill in the form using the following information and click Save.

Name: HQ CUCM Publisher CTI

Description: HQ CUCM Publisher CTI Services for Cisco Jabber
Host Name / IP Address: cucm-pub.cll-collab.internal (Use the FQDN (Fully Qualified Domain Name) for
the Publisher. It is possible to enter the IP address in this field instead.)
Port: 2748 (Default)

Step 6
Click Save. Then click Add New. Choose IM and Presence from the drop-down and click Next.

Step 7
Fill in the form using the following information:

Name: IMP
 Description: HQ IMP Services for Cisco Jabber
Host Name / IP Address: 10.1.5.7

Step 8
Select User Management > User Settings > Service Profile.

Step 9
Click Add New.

Step 10
Enter Jabber_SP in the Name field and Jabber Service Profile in the description.
Step 11
Check the box titled “Make this default service profile for the system.”

Step 12
Scroll down to the IM and Presence Profile section and select the IMP service you created earlier from the
primary drop-down menu.

Step 13
In the CTI Profile section, select the HQ CUCM Publisher CTI service you created earlier from the primary drop-
down menu.

Step 14
Click Save.

The profile has now been configured to use the CTI service. This profile will need to be associated to the end
user, but there are a few more things that need to be configured first. The association will be done later in this
lab.

Task 2: Configure a SIP Trunk to Cisco IMP

In this task, you will configure the Cisco Unified Communications Manager integration with Cisco Unified
Communications IM and Presence.

Activity
SIP Trunk Configuration from Cisco Unified Communications Manager to Cisco Unified Communications
IM and Presence
The first step in creating a link between Cisco Unified Communications Manager and IM&P is to configure the SIP
trunk security profile and the SIP trunk pointing to the Cisco Unified Communications IM and Cisco Unified
Presence.

Step 1
 In Cisco Unified CallManager Administration, select System > Security > SIP Trunk Security Profile.

Step 2
Click Add New and configure a new profile with the following settings:

Name: IMP
Description: IMP Trunk Security Profile
Check the box: Check the Accept Presence Subscription check box to allow Cisco Unified
Communications Manager to accept presence subscription requests that come via the SIP trunk.
Check the box: Check the Accept Out-of-Dialog Refer check box to allow Cisco Unified Communications
Manager to accept incoming non-INVITE, out-of-dialog REFER requests that come via the SIP trunk.
Check the box: Check the Accept Unsolicited Notification check box to allow Cisco Unified
Communications Manager to accept incoming non-INVITE, unsolicited notification messages that come via
the SIP trunk.
Check the box: Check the Accept Replaces Header check box to allow Cisco Unified Communications
Manager to accept new SIP dialogs that have replaced existing SIP dialogs.
Step 3
Go to Device > Device Settings > SIP Profile.

Step 4
Click Find and select HQ SIP Profile.
Step 5
Scroll to the bottom of the screen and verify that the check box next to Enable OPTIONS Ping to monitor
destination status for Trunks with Service Type “None (Default)” is selected. The remaining options in the
SIP OPTIONS Ping section are left at their default values but they can be adjusted to suit the needs of the site or
connection.

Step 6
The next step is to configure a SIP trunk that points to the Cisco Unified Communications IM and Cisco Unified
Presence. The previously configured SIP Trunk Security Profile and the HQ SIP Profile will be used for the new
SIP trunk. Choose Device > Trunk and click Add New. Use the following settings to configure the new Trunk:

Trunk Type: SIP Trunk

Device Protocol: SIP
Trunk Service Type: None(Default)
Device Name: IMP_Trunk
Device Pool: HQ
SIP Destination Address: 10.1.5.7
SIP Trunk Security Profile: IMP
SIP Profile: HQ SIP Profile
Step 7
Go to System > Service Parameters.

Step 8
Select the Publisher CUCM-PUB.CLL_COLLAB.INTERNAL and the service Cisco CallManager.
Step 9
Set the parameter for IM and Presence Publish Trunk to IMP_Trunk.

Task 3: Add Cisco Services Framework Device

Activity
The Cisco Jabber software registers to the Cisco UCM as a CSF Device. As such, you need to add the new device
to the configuration. Much like a regular IP Phone, you need to define parameters such as Device Pool, Location,
calling search space, and a directory number. This CSF device must also be associated to a user account since it
won’t be identifiable via MAC address, the linkage between the CSF and the user is through the login with
username.

Step 1
Select Device > Phone.

Step 2
Click Add New.
Step 3
Select Cisco Unified Client Services Framework from the Phone Type drop-down menu.

Step 4
Click Next and use the following information to complete the Device Information section of the form:

Device Name: CSFJDoe

Description: John Doe CSF Cisco Jabber Softphone
Device Pool: HQ
Phone Button Template: Standard Client Services Framework
Calling Search Space: Internal_CSS
Location: HQ
Owner User ID: jdoe
Primary Phone: HQ-CIPC-1
Device Security Profile: Cisco Unified Client Services Framework – Standard SIP Non-Secure Profile
SIP Profile: HQ SIP Profile
Step 5
Click Save, then click Line [1] – Add a new DN.

Step 6
Enter 11001 in the Directory Number field.
Step 7
Select HQ_Lobby_PT from the Route Partition drop-down menu.

Step 8
Click the description field to make sure that the rest of the information has been updated. Verify the directory
number of HQ-CIPC-1. Also verify that “Allow Control of Device from CTI” is checked--a default setting, but worth
noting it is a requirement for this lab.
Step 9
Scroll Down to "Line 1 on Device CSFJDoe" and enter the following information:

Display (Caller ID): John Doe

External Phone Number Mask: 408555XXXX

Step 10
In the "Forwarded Call Information Display on Device CSFJDoe" section, select the Caller Name and Caller
Number checkboxes.

Step 11
In order to use Jabber for phone presence, the Cisco UCM end user needs to be associated to the directory
number. Scroll to the bottom of the page to the "Users Associated with Line" section and click Associate End
Users.

Step 12
 Click Find, then check the box next to jdoe and click Add Selected.

Step 13
Click Save and click Apply Config.

Step 14
Repeat the previous steps to create a CSF device for Jane White using the following information:

Device Name: CSFJWhite

Description: Jane White CSF Cisco Jabber Softphone
Device Pool: HQ
Phone Button Template: Standard Client Services Framework
Calling Search Space: Internal_CSS
Location: HQ
Owner User ID: jwhite
Primary Phone: HQ-CIPC-2
Device Security Profile: Cisco Unified Client Services Framework – Standard SIP Non-Secure Profile
SIP Profile: HQ SIP Profile
Line 1:

Directory Number: 11002

Route Partition: HQ_Managers_PT
Associated Devices: HQ-CIPC-2
Display (Caller ID): Jane White
External Phone Number Mask: 408555XXXX
Caller Name: Checked
Caller Number: Checked
Associated End User: jwhite

Task 4: Configure End-User Settings

Activity
The user account requires a few additional permissions. It is also a requirement to select the Service Profile that
the Cisco Jabber client will use when the user logs in. The user account also needs to be associated to the CSF
device, and in the case of Deskphone mode, the user also needs to be associated to the physical phone. This lab
will take you through the steps needed to configure the user account that will be used to log in to the Cisco Jabber
client.

Step 1
Select User Management > End User.

Step 2
Click jdoe from the list of end users.

Step 3
In the Services Settings section, select the check box for Enable User for Unified CM IM and Presence. Then
select the Jabber_SP profile from the UC Service profile drop-down menu and click Save.

Step 4
In the Device Information section, click Device Association. Device association creates the link between the
user account and the devices they will use. In this lab, John Doe has access to the HQ-CIPC-1 and CSFJdoe
devices. In order for the Cisco Jabber client to know which phone it can control (Deskphone), these links must
exist.
Step 5
Click Find, then check the boxes next to CSFJDoe and HQ-CIPC-1.

Step 6
Click Save Selected / Changes.

Step 7
Click Go next to the "Related Links: Back to User" and click Save.

Step 8
Scroll down to the "Permissions Information" section, click Add to Access Control Group.
Step 9
Click Find, then select the following groups:

Standard CCM End Users

Standard CTI Allow Control of Phones supporting Connected Xfer and conf
Standard CTI Allow Control of Phones supporting Rollover Mode
Standard CTI Enabled

At a minimum, the end user needs to belong to the Standard CCM End Users (already configured for jdoe), and
the Standard CTI Enabled group.

Certain phone models require additional groups, as follows:

For Cisco Unified IP Phone 6900 Series, choose Standard CTI Allow Control of Phones supporting Rollover
Mode.

For Cisco Unified IP Phone 8900 or 9900 Series, choose Standard CTI Allow Control of Phones supporting
Connected Xfer and conf.

Step 10
Click Add Selected.

Step 11
Confirm that the new Groups have been added, then click Save.
Step 12
Scroll down to the "Permissions Information" section and notice that the associated Roles have updated
according to the new groups the user has been associated with.

Step 13
Repeat the previous steps on the user account jwhite. All settings are the same, but the device association
needs to be to her phones (HQ-CIPC-2 and CSFJWhite).

Step 14
Reset the password for jwhite to C0ll@B.

Task 5: Configure Cisco Jabber Client for Windows

Activity
Once the configuration is completed in Cisco Unified Communications Manager, the Jabber clients can be
activated and registered. The Jabber clients have been preinstalled on PC-1 and PC-2.

Step 1
On the PC-1 desktop, open the Cisco Jabber application.

Step 2
Enter jdoe@cll-collab.internal and click Continue.
Step 3
The Jabber client will perform a DNS lookup for Cisco Unified Communications Manager at _cisco-uds._tcp.cll-
collab.internal. If the lookup is successful, you may be presented with a certificate warning if the PC does not
trust the certificate of the Communication Manager. After verifying the identity of the server (cucm-pub.cll-
collab.internal in this case), click Accept to continue.

Step 4
When prompted for the password, enter C0ll@B and click Sign In.
Step 5
Once the Jabber client registers, you will see the main screen. You will see that John Doe is in the available
state and, since this is a new installation, you are prompted to start adding contacts.
Step 6
Repeat the previous steps and activate the Jabber client on PC-2 for user jwhite@cll-collab.internal with
password C0ll@B.

Step 7
Once both Jabber clients are registered, call from John Doe to Jane White by entering 11002 and clicking the
green call icon.

Step 8
Answer the call on PC-2 (Jane White).

Step 9
The PCs are video enabled, so the screen will change, and you will see a simulated video stream which is
provided by a video file that is streamed from one PC to the other in both directions. Your own video output is
shown as a smaller window in the right-hand corner of the screen.
Step 10
If you look at John Doe’s PC, you will see the opposite screen arrangement. You will also see that both John and
Jane’s status has automatically been changed to On a call.

Step 11
On PC-1, add a contact for Jane on John’s Jabber client. Click Add Contact.

Step 12
In the search area, type Jane. Double-click on Jane White with the green status indicator.

Step 13
It is useful to organize your contacts by groups. Since no groups exist, click the New Group button.
Step 14
Enter the name Sales and click Create.

Step 15
You will be returned the Add Contacts window. The new group name will be selected. Finish adding the contact
by clicking Add.

Step 16
On PC-1, on John Doe’s Jabber client, click the small down arrow to the left of his name. Change the state to Do
Not Disturb.

You can manually change your status to Do Not Disturb, Away or Available. You can also change the
text that is displayed to other users by click on the text and adding your own custom message.
Step 17
On PC-1, click the green “IM” icon next to Jane White’s name.

Step 18
This will open a separate window for instant messaging. Send a message to Jane White.

Task 6: Troubleshoot Cisco Jabber

Activity
Cisco Jabber has some useful troubleshooting tools built directly into the application. This lab will step you through
these tools in the event you need to troubleshoot the client.

The first and most useful tool to help with troubleshooting is the Problem Reporter. It will create a zip file that
contains the log file and many other files useful for troubleshooting. It’s important to know how to generate this file,
as it’s the first thing Cisco TAC will request when logging a Cisco Jabber TAC case.

Step 1
Click the gear icon in Cisco Jabber and select Help > Report a problem

Step 2
Notice that the drop-down menu allows you to select the area for which your problem is based.

Step 3
The next step is to define a summary of the problem, then give a detailed step by step procedure on how to
 replicate the problem. You are also able to attach additional files or screenshots to this problem report. Since this
lab is working without fault, feel free to choose any area from the drop-down menu.

Step 4
Click Save to save this report with all attachments and screenshots (if any). The default save location is the
desktop.
Step 5
On the desktop, notice that the filename contains the time stamp of when the file dump is created. If a Cisco TAC
engineer had requested the problem report, this file is the file you would email to the engineer. Right-click on the
newly created file on the desktop and click Extract All…

Step 6
Leave the default extraction location on the desktop and click Extract.
Step 7
Notice the new folder and many files that can be used to help troubleshoot, including the file named “user-
comment” which contains all the information you typed when generating this report.
Step 8
To view the log file, right-click on the file named jabber.log and click Edit with Notepad++.

Step 9
Note that there are no errors in this lab causing the Cisco Jabber client to fail. These steps are to illustrate the
method that can be used when trying to troubleshoot problems you may face in your environments.

Step 10
To view your connection status, from Cisco Jabber, click the gear icon and select Help > Show Connection
Status. The connection status window shows an overview of the health of Cisco Jabber and is a quick way to
identify if any services are not working.
Step 11
Notice that the Softphone has a green tick with the details of Cisco UCM that Jabber is registered with. You will
also notice the Directory information which is also using Cisco UCM. The Deskphone is showing a status of “Not
Connected” as the phone is not on and not connected.

Step 12
To view Jabber errors, close the Connection Status window, then click the gear icon and select Help > Show
error notifications.
Step 13
Note that the Error Notifications window highlights any errors and their severity, and the date and time the event
occurred. You will not notice any error messages currently because Cisco Jabber is working without any faults,
but it’s useful to know how to access these help tools if you run into trouble at any stage.