Upgrade CUPS 8.6 to IM&P 11.0 - Jabber for Windows client 10.6

[Carl Ratcliffe]

Hi Support Community

We are upgrading our voice environment from 8.6 to 11.0 including CUCM, CUPS, CUC and UCCX including moving from MCS servers to Cisco UCS. In regards to CUCM, UCCX and CUC I have completed these many times in the past and we have a detailed plan. In regards to CUPS/Jabber we are still trying to finalise the upgrade design and after reading many documents and a few good videos by Jaime Valencia our particular upgrade scenario is still unclear.

We were using Microsoft OCS and decided to migrate to CUPS/Jabber, we have 3 CUCM clusters so we created 3 single server CUPS clusters ( we are going to put HA in when we go to Cisco UCS but at the time we only had 3 spare MCS servers ) and these have intercluster peers.

• We are using a single domain across all 3 clusters.
• 100% of our users use IM&P with voicemail and calendar integration and call control
• 10% of our users also have softphones
• We don't use SRV yet for service discovery due to having 3 clusters on 8.6 so we have Jabber for Windows 10.6 packaged with Microsoft SCCM specifying the Account Type as Cisco IM & Presence and Login Server "use the following server" which points to the CUPS Publisher.
• First time users have to specify username@domain.com at which point it discovers the domain then we have to use just the username and password to login after which its cached and all subsequent logins are automatic.

My  questions are :

• When we upgrade CUPS 8.6 to IM&P 11.0 will ourJabber for Windows 10.6 client configuration continue to work without any changes ?
• We currently point to the Account Type "Cisco IM & Presence", this allows us to use IM&P and voice ie call control and softphones, in what scenario would you select Account Type Cisco Unified Communications Manager ?
• We want to use SRV for Service Discovery but as we have 3 clusters which are being upgraded in a phased approach are we better waiting until we have upgraded all 3 clusters then we can use a single SRV for multi clusters with ILS ?
• When you first login to Jabber you have to enter username@domain.com then it discovers the domain then we just enter username and password ( minus the domain ) , will the SRV service discovery mean we only need to enter username and password once without the domain specified ?
• Does this SRV for service discovery also provide the HA for login if the primary server is down or is that done some other way ?

Thanks, Carl Ratcliffe

Preston Lancashire England

[Jaime Valencia · Accepted solution]

Yes, the config will remain the same

As to the second question, read here:

http://www.cisco.com/c/en/us/td/docs/voice_ip_comm/jabber/10_6/planning-guide/CJAB_BK_CD3376A0_00_cisco-jabber-106-planning-guide/CJAB_BK_CD3376A0_00_cisco-jabber-planning-guide_chapter_01000.html

http://www.cisco.com/c/en/us/td/docs/voice_ip_comm/jabber/10_6/CJAB_BK_C56DE1AB_00_cisco-jabber-106-deployment-and-installation-guide/CJAB_BK_C56DE1AB_00_cisco-jabber-106-deployment-and_chapter_010000.html

As now CUCM is the one that handles the services profiles, that define everything, you want to use _cisco-uds

#3 Yes, you probably want to wait to get them all into the same release, then make sure ILS is working fine, then configure the SRVs

#4 yes, the first time it will ask for user@domain, once it finds the SRVs it will cache the user and you'll only need the password.

#5 yes, you can configure the SRVs for all the servers in the cluster.

[Carl Ratcliffe]

Hi Jaime

Thanks for your time and response and thanks for the excellent videos you have posted on various topics.

Just to be clear, I understand the IM&P server is essentially part of the CUCM cluster however when it mentions that CUCM handles service profiles and the _cisco-uds provides the location of the Cisco Unified Communications Manager and the client can retrieve service profiles from Cisco Unified Communications Manager to determine the authenticator is this actually specifying a traditional CUCM call processing node or a IM&P node that it just refers to as CUCM ?

My configuration at the moment specifies the CUPS server directly so im just trying to understand if when I go to v11 and eventually use SRV's am I going to point to CUCM instead of IM&P ?

Thanks, Carl Ratcliffe

Preston Lancashire England

[Jaime Valencia]

Yes, you will point to CUCM and use _cisco-uds, whether you want phone only, IM only, or full UC, if you want it to have CUC, TMS, etc. It will all be handled by the service profiles in CUCM.

[Carl Ratcliffe]

Thanks Jaime,

so when I upgrade CUPS 8.6 to IM&P 11.0 and leave the Jabber for windows 10.6 configuration unchanged with manual config of the Service Type = Cisco IM & Presence and specify the FQDN of the CUPS 8.6 Publisher( which will now be IM&P Publisher ) will this have any negative impact seen as the documents are advising that it should be CUCM that you point to and not CUPS/IM&P ?

Once we have all clusters on 11.0 the plan is to remove Jabber For Windows 10.6 via SCCM then deploy an upgraded version also using SRV records we just wanted to make sure we can do this after the upgrade and not before.

Thanks, Carl Ratcliffe

Preston Lancashire England

[Carl Ratcliffe]

Hi Jaime

I have just read the Cisco Jabber 11 Planning Guide in preparation for when we do upgrade Jabber for Windows clients and what im confused about is why the non DNS SRV Record method states the authenticator =CUP with a presence server address when the SRV _cisco-uds is to be configured as CUCM for the authenticator ?

Recommended Connection Methods

The method that you should use to provide the client with the information it needs to connect to services depends on your deployment type, server versions, and product modes. The following tables highlight various deployment methods and how to provide the client with the necessary information.

Table 1 On-Premises Deployments for Cisco Jabber for Windows

Product Mode	Server Versions	Discovery Method	Non DNS SRV Record Method
Full UC (default mode)	Release 9.1.2 and later: Cisco Unified Communications Manager Cisco Unified Communications Manager IM and Presence Service	A DNS SRV request against _cisco-uds .<domain>	Use the following installer switches and values: AUTHENTICATOR=CUP CUP_ADDRESS= <presence_server_address>
Full UC (default mode)	Release 8.x: Cisco Unified Communications Manager Cisco Unified Presence	A DNS SRV request against _cuplogin.<domain>	Use the following installer switches and values: AUTHENTICATOR=CUP CUP_ADDRESS= <presence_server_address>
IM Only (default mode)	Release 9 and later: Cisco Unified Communications Manager IM and Presence Service	A DNS SRV request against _cisco-uds .<domain>	Use the following installer switches and values: AUTHENTICATOR=CUP CUP_ADDRESS= <presence_server_address>
IM Only (default mode)	Release 8.x: Cisco Unified Presence	A DNS SRV request against _cuplogin .<domain>	Use the following installer switches and values: AUTHENTICATOR=CUP CUP_ADDRESS= <presence_server_address>
Phone Mode	Release 9 and later: Cisco Unified Communications Manager	A DNS SRV request against _cisco-uds.<domain>	Use the following installer switches and values: AUTHENTICATOR=CUCM TFTP=<CUCM_address> CCMCIP=<CUCM_address> PRODUCT_MODE=phone_mode High availability is not supported using this method of deployment.
Phone Mode	Release 8.x: Cisco Unified Communications Manager	Manual connection settings	Use the following installer switches and values: AUTHENTICATOR=CUCM TFTP=<CUCM_address> CCMCIP=<CUCM_address> PRODUCT_MODE=phone_mode High availability is not supported using this method of deployment.

Cisco Unified Communications Manager release 9.x and earlier—If you enable Cisco Extension Mobility, the Cisco Extension Mobility service must be activated on the Cisco Unified Communications Manager nodes that are used for CCMCIP. For information about Cisco Extension Mobility, see the Feature and Services guide for your Cisco Unified Communications Manager release.

Note	Cisco Jabber release 9.6 and later can still discover full Unified Communications and IM-only services using the _cuplogin DNS SRV request but a _cisco-uds request will take precedence if it is present.

[Carl Ratcliffe]

I have tested upgrading CUCM and CUPS from v8.6 to v11 whilst leaving the Jabber clients untouched. These Jabber clients use bootstrap files using CUPS as the authenticator and they continue to work with full UC functionality.

Although doing this doesn't use service profiles from CUCM it is obviously still pulling the same information through from Presence even though its no longer included in presence so its obviously pulling this through from CUCM.

If you select either Cisco IM & Presence or Cisco Communications Manager 8.xoptions, the client retrieves

UC services from Cisco Unified Presence or Cisco Unified Communications Manager IM and Presence

Service. The client does not use service profiles or SSO discovery.

Note : We will certainly be using service profiles and DNS SRV in the future however as we have 3 Presence Clusters at v8.6 and we will be completing a phased migration we cannot use a single SRV until we are on v11 as we wont have ILS between the clusters to look for the home location of users.