Migrating Jabber to new CUCM environment

[alexmacaronis]

Hello,

We're moving from on-premises, self managed call manager to Telstra TCCCP (partner hosted solution).

I've been tasked with trying to figure out how to manage the seamless switch-over of the Jabber client as we migrate on a site-by-site basis.

We're currently using DNS discovery to point to our internal call manager servers and users are getting the full jabber experience. The new service will only be providing phone services, IM&P to be disabled.

We're trying to cut over users on a site by site basis, not all at once. Can anyone suggest a strategy to automatically re-direct users to the new call manager (and enable Phone_Only) without breaking the existing experience for all of the other users?

Thanks,

Alex

[Mohammed al Baqari]

How do you manage DNS per site. ? If you have local DNS per-site then you
can create CNAME record to point your old domain name (existing one) to new
domain name. The new domain name should have an A record to point to new
environment which provide PhoneOnly. This way when your site users try to
discover jabber using DNS, it will point them to the new environment.

This is just an idea but you need to test and validate.

[alexmacaronis]

Unfortunately our DNS is not per site.

[pqueued]

Push a local host file with specific DNS/SRV records for service discovery out via a GPO? Assuming you have your sites broke up into different OU's?

[Jonathan Schulenberg]

I’m surprised the HCS provider doesn’t have guidance to offer here.

Ask them if you can configure ILS between the two CUCM clusters during the transition. This will let you untick Home Cluster from your on-premises cluster and tick it on the HCS cluster instead. The next time Jabber does service discovery, resolving to either cluster, the user will be pointed to whichever cluster they are provisioned on. HCS CUCM is normal CUCM with provisioning tools wrapped around it. If they tell you it can’t be done that’s a limitation on their part, not the product.