Cisco Support Community
cancel
Showing results for 
Search instead for 
Did you mean: 
New Member

Jabber for Windows 9.7.1 UDS Integration and EMail as UserID results in wrong IM Address

Hello everyone-

I am experiencing a Problem with the following configuration on CUCM 10.0.1, IM&P 10.0.1 and J4W 9.7.1.

I imported all Users via LDAP into CUCM with their mail Address as UserID. In Presence i set the address scheme to directory-uri.

Now the Im Address in Presence seems correct to me as "user@domain.zz"

When i open Jabber, which is UDS integrated, and view a Profile for a contact i can see that the IM Address changed to "user@domain.zz@domain.zz".

I believe the mandatory directory parameter <PresenceDomain>Domain address of your Presence server</PresenceDomain> in the jabber-config is responsible for this.

Is there any way to prohibit the append of the Presence Domain ?

Thanks a lot in advance

Björn Engel

 

4 REPLIES
Cisco Employee

No, that's a known issue, JID

No, that's a known issue, JID is composed of whatever you are syncing for userID+Jabber domain, so you end up with two @s if you choose the mail as field to sync.

HTH

java

if this helps, please rate

www.cisco.com/go/pdi
New Member

Hi Jaime, thank you for your

Hi Jaime, thank you for your answer-

Referring to the admin guide (page 18ff), i interpreted that when i am using the directory-uri it should be possible to use the Email Adress as UserID. Inside the IM&P database the correct IM Address is shown. It looks like a problem of the client. The deletion of the working directories and restart of Jabber didnt change the behavior. It seems to me that the client adds the second @domain.zz by itself. I didnt find any compatibility matrix for this new introduced feature...

http://www.cisco.com/c/en/us/td/docs/voice_ip_comm/cucm/im_presence/configAdminGuide/10_0_1/CUP0_BK_C318987B_00_config-admin-guide-imp-100.pdf

 

Thanks again

What is the bug id?

What is the bug id?

New Member

I found the following:https:/

I found the following:

https://tools.cisco.com/bugsearch/bug/CSCuo95266

 

374
Views
0
Helpful
4
Replies
CreatePlease to create content