Jabber login behavior after domain change

[mbrown-revitycu]

We recently went through a rebranding at our organization which not surprisingly led to a new domain name and corresponding new email addresses for all users.

Since then, we have seen some really strange behavior with Jabber that we have been unable to explain. We use LDAP to sync users into CUCM from AD, after which we enable the user for IM and Presence to give them Jabber access. Users then login to Jabber using their email address and Windows credentials.

Users who were with the organization prior to the rebrand have an email of "user@newdomain.com" along with an alias of "user@olddomain.com."

Users who were hired after the rebrand only have an address of "user@newdomain.com." They don't have an alias for "olddomain.com" because they never had an email with that address.

Here's the strangeness. Users hired after the rebrand - who only have "newdomain.com" emails - have to login to Jabber with "user@olddomain.com" even though have never ever had an email with that address. If they attempt to login with "newdomain.com" they are unable to login at all.

What in the world would cause this? Please let me know if there's any more information I can provide to help troubleshoot.

Thanks!

[b.winter]

Probably because the IM&P is set to use the "default domain" configured and not set to "flexible JID", which uses the Directory URI (email) as IM address.
So it doesn't care which email the users have, because it is not used all.

You always need to login with "user@imp-domain".

Check the setting in IMP --> Presence --> Settings --> Advanced Configuration --> IM Address Scheme

If you want to use the Directory URI (email) as the IM address, then you have to "reconfigure" the IM Address Scheme, the corresponding Jabber xml file and DNS records to support "flexible JID"

[mbrown-revitycu]

This is what we currently have there, which seems to be what it should be. Is there a corresponding value in the Jabber .xml file that we need to update?

[b.winter · Accepted solution]

And what about the SRV records?
Per default, Jabber uses the domain, which you enter during the login, to look for the SRV record (which in the end tells Jabber the CUCM DNS / IP).
Do you have the cisco-uds SRV record in the new domain too?

[Carlo Poggiarelli]

Hi

Under System --> Server Please select the IM&P server and look at which domain is specified in "IM and Presence Domain" field.

Please let us know.

Regards

Carlo

[mbrown-revitycu]

We were completely missing the SRV records! After adding all those records to DNS, all users can now log into Jabber with newdomain.com successfully.

Thank you!!