Cisco Jabber for Windows on CallManager Express

Cisco Jabber

Unified CME Releases 12.5 and later support Cisco Jabber (The Jabber version supported on Unified CME Releases 8.6 to 10.5 is now End-of-Life). The SIP softphone client is capable of supporting VoIP over WLAN. Unified CME supports supplementary services such as Hold, Resume, Transfer, Call Park, and Call Pickup for the softphone SIP client. 

From Unified CME 12.5 onwards, Cisco Jabber CSF 12.1.0 client for MAC and Windows (phone-only mode) is supported. Jabber versions 9.0.x is End of Life and Unified CME 12.5 is the minimum version required for Cisco Jabber client support on Unified CME. 

Feature Support for Cisco Jabber

The following features are support for Cisco Jabber on Unified CME 12.5 and later releases: 

  • Hold or Resume
  • Transfer
  • Shared Line
  • Mixed Shared Line
  • Call forward—All, Busy, No Answer, Unregistered 
  • Directed Call Park Pickup
  • Single Number Reach (SNR)
  • Voice Hunt Group (Sequential, Parallel)
  • Hardware Conference
  • Music On Hold
  • Video
Restrictions

The following Unified CME features are not supported with Cisco Jabber:

  • Barge
  • cBarge
  • Built-in Bridge (BIB) Conference
  • Do Not Disturb
  • KPML Dialing

Cisco Jabber Client is a SIP-based soft client with integrated Instant Messaging and presence functionality, and uses the new Client Services Framework 2nd Generation (CSF2G) architecture. 

CSF is a unified communications engine that is reused by multiple Cisco PC-based clients and mobile clients. The client is identified by a device ID name that can be configured under the voice register pool in Cisco Unified CME. You should configure the username and password under voice register pool to identify the user logging into Cisco Unified CME through Cisco Jabber client. The device discovery process uses HTTPS connection. Therefore, you should configure the secure HTTP on Cisco Unified CME. 

A new phone type, ‘Jabber-CSF-Client’ has been added to configure the Cisco Jabber client under voice register pool. This can be used to configure any CSF based Cisco Jabber client. In CME-10.0 we used the type ‘Jabber-Win’ to configure Cisco Jabber client. In CME-10.5 this type is deprecated and the new ‘Jabber-CSF-Client’ should be used to configure Cisco Jabber client as well. 

Cisco Jabber CSF client can be provisioned in 2 modes: Full UC mode (with integrated IM and Presence services) and Phone only mode. The phone-only mode of Cisco Jabber CSF devices is also supported. This can be configured with the option ‘phone-mode phone-only’ under ‘voice register global’ or ‘voice register pool’ or ‘voice register template’ config. 

If the Jabber client is installed in phone only mode then no extra configuration is required on CME. The normal Jabber configuration should be sufficient. 

Cisco Jabber Client Support Versions

Restrictions

  • The Cisco Jabber CSF client supports only the softphone mode with Cisco Unified CME. 
  • Desk phone mode is not supported. 
  • The following Cisco Jabber CSF type of devices are not supported: 
    • Cisco Jabber for iPhone (both full UC mode and phone-only mode) 
    • Cisco Jabber for Android (both full UC mode and phone-only mode) 
    • Cisco Jabber for iPad (both full UC mode and phone-only mode)

Configuring Cisco Jabber

The following example shows phone type Cisco Jabber configured under voice register pool 20:


!  
voice register dn  20
number 1000
call-forward b2bua busy 1500
call-forward b2bua mailbox 1500  
call-forward b2bua noan 1500 timeout 20
pickup-call any-group
pickup-group 1
name Test iPhone
!         
!
voice register pool  8
registration-timer max 720 min 660
session-transport tcp
type CiscoMobile-iOS 
number 1 dn 20
dtmf-relay rtp-nte
!         
!

Configuring Cisco Jabber CSF Client

The following example shows how to configure the Cisco Jabber CSF client installed in full UC mode:


!
voice register dn 1
number 1200
name Test-CSF-1
label   Test-CSF-1
!
voice register pool 1
id device-id-name jabber_csf_1
type Jabber-CSF-Client
number 1 dn 1
username user1 password yahoo
codec g711ulaw
camera
video
!
ip http secure-server
ip http secure-port 8443

The following example shows how to configure the Cisco Jabber CSF client in phone-only mode from CME under voice register global: 


voice register global
 phone-mode phone-only
!
voice register pool  1
 id device-id-name winJabber 
 number 1 dn 1
 type Jabber-CSF-Client
 username 1234 password 1234
!

The following example shows how to configure the Cisco Jabber CSF client in phone-only mode from CME under voice register pool: 

voice register pool 1
id device-id-name winJabber
number 1 dn 1
type Jabber-CSF-Client
username 1234 password 1234
phone-mode phone-only
!

The following example shows how to configure the Cisco Jabber CSF client in phone-only mode from CME under voice register template: 


voice register template  1
 phone-mode phone-only
!
voice register pool  2
 id device-id-name winJabber
 type Jabber-CSF-Client
 number 1 dn 2
 username 1234 password 1234
 template 1
!

For Cisco Jabber CSF client (version 12.1.0 and onwards) support, Unified CME 12.5 is configured as the DNS Server. The host machine of the Jabber client is configured to point to Unified CME that is configured as the DNS server. The following example shows how to configure Unified CME 12.5 and later versions as DNS Server to support the Cisco Jabber CSF client, Version 12.1.0 for Mac and Windows (Phone-only Mode): 


enable
configure terminal
ip dns server
ip host _sip_tcp.cisco.com srv 0 1 5060 cme.cisco.com
ip host _sip_udp.cisco.com srv 0 1 5060 cme.cisco.com
ip host _sips_tcp.cisco.com srv 0 1 5060 cme.cisco.com
ip host _cisco-uds._tcp.cisco.com srv 0 1 8443 cme.cisco.com
ip host uds._tcp.cisco.com srv 0 1 8443 cme.cisco.com
ip host _collab-edge._tls.cisco.com srv 0 1 8443 cme.cisco.com
ip host cme.cisco.com 10.64.86.106 (Note: IP Address of Unified CME 12.5)
ip host _cisco-phone-http.tcp.cisco.com srv 0 1 8443 cme.cisco.com

Install Jabber for Windows

Complete these instructions in order to install Jabber:

  • Download the installer from the Cisco web site and start the installation process with the installation wizard.
  • Click Accept and Install.
  • Wait for the installation to complete.
  • Click Finish.

Log Into Jabber

  1. Once Jabber is installed and launched, enter your username and password in order to log in. 
  • Set up the TFTP and CME server. 
  • Enter the username and password that were configured under the voice register pool and click Sign In.
  • An alert pop ups up in regards to the self-signed certificate from the CME. Click Accept in order to accept the certificate and allow Jabber to authenticate and log in.
  • Jabber for Windows is now ready to make and receive calls.

Known Issue: Certificate Error

When you try to log in to Jabber, there is a message in regards to a certificate error:

Enter the debug ip http all command in order to get this output:

019193: *Jul  1 08:59:02.561: %HTTPS: http ssl get context fail (-41104)
019194: *Jul 1 08:59:02.561: HTTP: ssl get context failed (-40407)

Solution

As seen in the ouput above, it is a problem with the HTTPS certificate.

In order to solve this, log into the CLI and remove the HTTPS configuration commands. Also remove the self-signed certificate generated by the CME for HTTPS.

CMEconfig)#no ip http secure-server
CME(config)#no ip http secure-port 8443
CME(config)#no crypto pki certificate chain TP-self-signed-3120869618
This will remove all certificates for trustpoint TP-self-signed-3120869618
Are you sure you want to do this? [yes/no]: yes

Then, reconfigure the HTTPS configuration and confirm a new self-signed certificate has been created.

CME(config)#ip http secure-server
CME(config)#ip http secure-port 8443
!
crypto pki trustpoint TP-self-signed-3120869618
enrollment selfsigned
subject-name cn=IOS-Self-Signed-Certificate-3120869618
revocation-check none
rsakeypair TP-self-signed-3120869618
!

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out /  Change )

Google photo

You are commenting using your Google account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s