Cisco Jabber client on CME 10.x

[Muthurani Lavanya Paneerselvam]

• Introduction
• Cisco Jabber Client on CME 10.x
• Example: Configuring Cisco Jabber CSF Client
• Related Information

Introduction

This document covers the Cisco Jabber clients support on Cisco Unified CME 10.5 release.

Cisco Jabber Client on CME 10.x 

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 can configure the username and password under voice register pool to identify the user logging into Cisco Unified CME through Cisco Jabber client. 

A new phone type, 'Jabber-CSF-Client' has been added to configure the Cisco Jabber client under voice register pool. 

Cisco Jabber CSF client can be provisioned in 2 modes:

• Full UC mode (with integrated IM and Presence services)
• Phone only mode. 
• From CME-10.5 onwards 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.
• Prerequisite - Cisco Unified CME 10.0 and later

Configuration

Configuring phone-only mode global level
router#conf  t
router(config)#voice register global
router(config-register-global)#phone-mode phone-only

Configuring phone-only mode in voice register template
router(config)#voice register template 1
router(config-register-temp)#phone-mode phone-only

Configuring phone-only mode in voice register pool
router(config)#voice register pool 1
router(config-register-pool)#phone-mode phone-only

Example: Configuring Cisco Jabber CSF Client

Cisco Jabber CSF client installed in full UC mode: ! voice register dn 1 number 991001 name Jabber-CSF-Client-1 label Jabber-CSF-Client-1 ! voice register pool 1 id device-id-name jabber_csf_1 type Jabber-CSF-Client number 1 dn 1 username john password john123 codec g711ulaw camera video ! ip http secure-server ip http secure-port 8443 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 1111022 password 1111022 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 1111023 password 1111023  template 1 ! !

Note
• The Cisco Jabber CSF client (full UC mode) should register with a presence server such as
cloud-based Webex server, or a Cisco Unified Presence server to enable the telephony features on the Jabber client.
• Desk phone mode is not supported.

• The following Cisco Jabber CSF type of devices are not supported:
– Cisco Jabber for MAC (phone-only mode)
– 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)

Related Information

• Cisco Unified Communication Manager Express System Administration Guide

[Aman Soi]

[+5]

regds,

aman

[Muthurani Lavanya Paneerselvam]

Thank you Aman.

Regards

Lavanya

[sailyachta]

So, with CME 10.5 and only a Cisco 29XX router you can't use Jabber on an iPhone?

[kashif2401]

Hi lavanya,

I am having some issue here with htttp authentication, here is the output for debug ip http all

Please help me with this.

Jan 4 08:08:47.828: cme_uds_urlhook: http request url /cucm-uds/version
Jan 4 08:08:47.828: Mon, 04 Jan 2016 08:08:47 GMT 192.168.20.142 /cucm-uds/version auth_required
Protocol = HTTP/1.1 Method = GET
Jan 4 08:08:47.828:
Jan 4 08:08:48.032: cme_uds_urlhook: http request url /cucm-uds/user/kashif/devices
Jan 4 08:08:48.032: cme_uds_realm_authenticate username kashif password 12345678
Jan 4 08:08:48.032: validate_cme_user_credential auth user is kashif and auth pwd Wmxg.|
Jan 4 08:08:48.032: cme_uds_realm_authenticate username/password authorization failed
Jan 4 08:08:48.032: HTTP: Authentication failed for realm cme_uds_access
Jan 4 08:08:48.032: HTTP: Authentication failed for level 15
Jan 4 08:08:50.032: Mon, 04 Jan 2016 08:08:50 GMT 192.168.20.142 /cucm-uds/user/kashif/devices auth_failed
Protocol = HTTP/1.1 Method = GET Query = max=100
Jan 4 08:08:50.032: Content-Type = text/xml

Jan 4 08:08:50.320: cme_uds_urlhook: http request url /cucm-uds/user/kashif@ns-arabia.com/devices
Jan 4 08:08:50.320: cme_uds_realm_authenticate username kashif@ns-arabia.com password 12345678
Jan 4 08:08:50.320: validate_cme_user_credential auth user is kashif@ns-arabia.com and auth pwd Wmxg.|
Jan 4 08:08:50.320: cme_uds_realm_authenticate username/password authorization failed
Jan 4 08:08:50.320: HTTP: Authentication failed for realm cme_uds_access
Jan 4 08:08:50.320: HTTP: Authentication failed for level 15
Jan 4 08:08:52.320: Mon, 04 Jan 2016 08:08:52 GMT 192.168.20.142 /cucm-uds/user/kashif@ns-arabia.com/devices auth_failed
Protocol = HTTP/1.1 Method = GET Query = max=100
Jan 4 08:08:52.320: Content-Type = text/xml

[Salvador Antonio Quintanilla Mendoza]

Hi,

Im having the same issue.

CME_SUPER_REPUESTOS#
*Aug 9 15:54:00.439: cme_uds_urlhook: http request url /cucm-uds/user/android/devices
*Aug 9 15:54:00.439: cme_uds_realm_authenticate username android password android123
*Aug 9 15:54:00.439: HTTP: Authentication failed for realm cme_uds_access
*Aug 9 15:54:00.439: HTTP: Authentication failed for level 15
*Aug 9 15:54:02.439: Tue, 09 Aug 2016 15:54:02 GMT 172.18.7.28 /cucm-uds/user/android/devices auth_failed
Protocol = HTTP/1.1 Method = GET Query = max=100
*Aug 9 15:54:02.439: Content-Type = text/xml

Did you solve this???