So for the UDS integration which is what it sounds like you’re doing; the userid field is what you have.
If your user’s have an Active Directory, and the sAMAccountName and domain name of the user’s AD profile match the user’s email address convention, the fix would be to simply integrate CUCM with LDAP. Another solution would be to enable the Flexible Jabber ID (FJID) and map it to the “Mail” field of the user’s CUCM End User account. Beware though ... FJID may not work well over MRA, though on-perm it should be fine. Sent from my iPhone > On Sep 5, 2018, at 07:11, GR <grc...@gmail.com> wrote: > > Hi Team, > > We have a customer using Jabber in Phone mode no presence. > Currently using userID@Domain for login.Cucm version is 11.5. Jabber version > is 12. CUCM is sso enabled with AD integration. Directory URI etc is set at > end user level in CUCM. > > How can we get it to use - email as Jabber login instead of the userid field. > > Sent from my iPhone > _______________________________________________ > cisco-voip mailing list > cisco-voip@puck.nether.net > https://eur01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fpuck.nether.net%2Fmailman%2Flistinfo%2Fcisco-voip&data=02%7C01%7C%7C87b2c19e858940a8268208d6132052b1%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C636717426874199693&sdata=kGc0iQvGpKIOP18dZthkoBp2o6WJBl2EDjzS24%2BmWjo%3D&reserved=0 _______________________________________________ cisco-voip mailing list cisco-voip@puck.nether.net https://puck.nether.net/mailman/listinfo/cisco-voip
