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

Welcome to Cisco Support Community. We would love to have your feedback.

For an introduction to the new site, click here. If you'd prefer to explore, try our test area to get started. And see here for current known issues.

New Member

Jabber ID as Directory URI fail when searching for contacts, Jabber still returns userID@domain as IM address

I've got a problem with JID set to Directory URI in CUCM/IMP 10.5. We've set up IMP node to Directory URI as IM Address Scheme in IMP Admin > Presence > Settings > Advanced Configuration. Directory URI is synced from email address in LDAP integration, every user has correct Directory URI value.

Despite this setup client (JfW 10.5) always returns userID@domain as IM address for every LDAP user I try to search. If I add user manually with JID=Directory URI address, user is identified correctly and communication is working. 

IMP Documentation says EDI must be used to get this working. UDS is not supported at this time. Unfortunatelly I can't get contact search working even with EDI and desktop in MS AD domain.

 

For example:

My JID = email = Directory URI = jiri.solc@domain.cz

My userID = solc

When I search for contacts, Jabber returns solc@domain.cz as IM address every time.

 

Only workaround is to add a contact manually without searching for one.

 

Any ideas? Thank you...

Everyone's tags (3)
1 ACCEPTED SOLUTION

Accepted Solutions
New Member

Hello.We were able to solve

Hello.

We were able to solve this as well. We are using UDS only.

We have the following:

CUCM 10.5.1

IM&P 10.5.1

Jabber 10.6 - We had to reset all instances of this to get the proper jabber-config.xml to download. Then remove contacts and re-add.


On our CUCM service profile for Jabber we have Directory / LDAP set to none, however, we have Use UDS checked.
 

Here is our jabber-config.xml. Also make sure your tftp is reachable, and also that you have saved the xml file in utf-8 text format.

 

<?xml version="1.0" encoding="utf-8"?>
<config version="1.0">
 <Policies>
   <EnableSIPURIDialling>false</EnableSIPURIDialling>
   <DirectoryURI>mail</DirectoryURI>
 </Policies>
 <Presence>
  <PresenceServerAddress>presence-server-address-here</PresenceServerAddress>
  <PresenceServerDomain>presence-server-domain.com-here</PresenceServerDomain>
 </Presence>
 <Directory>
   <IMAddresses use-default="false">
      <IMAddress>mail</IMAddress>
   </IMAddresses>
   <UseSIPURIToResolveContacts>true</UseSIPURIToResolveContacts>
   <SipUri>mail</SipUri>
   <DirectoryServerType>UDS</DirectoryServerType>
   <PresenceServer>presence-server-address-here</PresenceServer>
   <UdsServer>callmanager-server-address-here</UdsServer>
 </Directory>
</config>

 

30 REPLIES
New Member

Nah, I've found answer for my

I'm also looking forward UDS/BDI supports Directory URI or support for EDI/BDI when using MRA. :-(

New Member

Hi, were you able to get it

Hi,

 

were you able to get it work with Directory URI?

New Member

No I didn't. I think it's not

No I wasn't. I think it's not possible with current Jabber 10.5. Directory URI is only supported when using EDI and only inside corporate network.

I'm actually looking forward this new Jabber 10.6 feature that might solve this problem with "Flexible JID Structure".

 

Cisco Employee

Hi,If I understand the issue

Hi,

If I understand the issue correctly.

  • Issue is that when you search new users in Jabber search bar, new user is added into Jabber with "Chat (IM address)" in the format of domain_user_id@domain and not in format of "Directory URI (=email)".
  • In CUCM directory synchronization, e-mail is set up such as "Directory URI" attribute
  • You have set IM Schema as "Directory URI" on IM&P.
  • You have got Jabber 10.5, CUCM 10.5 and CUCM IMP 10.5
  • You tried using EDI integration for testing.

If you are planing to test with the EDI directory integration again.

You can try the below xml tags in the jabber-config.xml file to enable Jabber client to retrieve the IM address from Mail field in Active Directory client.

<Directory>

<IMAddressesuse-default=”false”>

        <IMAddress>mail</IMAddress>

    </IMAddresses>

</Directory>

 

or

 

<Directory>

 <IMAddressesuse-default=”false”>

        <IMAddressprefix=”sip:”>msRTCSIP-PrimaryUserAddress</IMAddress>

    </IMAddresses>

</Directory

 

Regards,

Ankoor

New Member

Hi, any news? I have the same

Hi,

 

any news? I have the same problem but the xml part above doesn't resolve my problem!

 

i see always  domain_user_id@domain and not only the mail, that correspond to the URI

 

Let me know please.

 

Thanks

Cisco Employee

What I have been told about

What I have been told about this is that in Jabber 10.6 the Jabber client will be able to support the Directory URI for search.

New Member

Anyone have 10.6 resolve this

Anyone have 10.6 resolve this issue? I have installed it, but issue remains.

New Member

I'm having the same issue,

I'm having the same issue, but according to the 10.5.2 imp documentation, this is still not supported with UDS as someone else pointed out a few months ago with a previous version.

thanks,

 

New Member

I have this working in a

I have this working in a multi-cluster/multi-forest environment..  jabber-config file is below, one thing to note as I just recently discovered, the sip: that prefixes the msRTCSIP-primaryuseraddress in ad is case sensitive, in this environment, two of the forests used lowercase sip: and the other two used uppercase SIP:.  I would get scenarios where when you perform a contact search, it would resolve the name but would not strip the prefix from the IM address.  Also the Service profile in UC has the "Use UDS for contact resolution" box checked.

 

<?xml version="1.0" encoding="utf-8"?>
<config version="1.0">
 <Options>
     <Start_Client_On_Start_OS>true</Start_Client_On_Start_OS>
     <AllowUserCustomTabs>true</AllowUserCustomTabs>
     <DockedWindowVisible>true</DockedWindowVisible>
 </Options>
 <Phone>
   <EnableDSCPPacketMarking>true</EnableDSCPPacketMarking>
 </Phone>
 <Policies>
    <enableLocalAddressBookSearch>false</enableLocalAddressBookSearch>
    <File_Transfer_Enabled>false</File_Transfer_Enabled>
    <EnableSIPURIDialling>true</EnableSIPURIDialling>
    <DirectoryURI>msRTCSIP-PrimaryUserAddress</DirectoryURI>
    <ServicesDomainSsoEmailPrompt>OFF</ServicesDomainSsoEmailPrompt>
    <disable_im_history>true</disable_im_history>
 </Policies>
 <Directory>
 <UseSIPURIToResolveContacts>true</UseSIPURIToResolveContacts>
 <UriPrefix>sip:</UriPrefix>
 <SipUri>msRTCSIP-PrimaryUserAddress</SipUri>
 <PhotoUriSubstitutionToken>sAMAccountName</PhotoUriSubstitutionToken>
 <PhotoUriWithToken>http://YOURCOMPANYWEBSERVER.COM/adphotos/%%uid%%.jpg</PhotoUriWithToken>
 <UdsPhotoUriWithToken>http://YOURCOMPANYWEBSERVER.COM/adphotos/%%uid%%.jpg</UdsPhotoUriWithToken>
 </Directory>
</config> 

New Member

The xml configurations you

The xml configurations you are referring to are supposed to be used with EDI directory integrations and not with UDS, like when you are connected via Expway. Were you able to verify your setup Flexible JID setup works with clients connected through Expway (doing things like adding new contacts)?

If I'm not mistaken, documentation for IMP 10.5.2 clearly states that URI based JID is not supported with UDS, which makes me think that multidomain environments are still not supported  with UDS integrations.

thanks!

New Member

You are correct, it is

You are correct, it is supposed to be in Beta still on the producion release of jabber 10.6, however this configuration does work when using only UDS for both on premise and off premise deployments.  The issue was still in place on the 10.5 train of jabber where it would append the incorrect domain to the IM address if you click the contact that is resolved during a predictive search while adding contacts.  

 

Unless I am mistaken, the Flexible JID feature is still in beta on 10.6, but does work with this config.

Bronze

Hi, Looking through all this

Hi, 

Looking through all this as im getting the same thing.

 

If I login as me@mydomain.com then when do a lookup for personA the chatIM address appears as personA@mydomain.com but is really personA@otherdomain.com, also appears on the presence cluster correctly. So appears it just gets the userId and adds my what ever domain my own account logged into.

 

Is there a clear fix on this as appears to be different sources stating different things? Running recent presence 10.5x and getting customer to update the Jabber 10.6 client to full release as was running beta.

 

Brian, i am interested what directory your jabber client connects to EDI or UDS?

New Member

I am having to force UDS for

I am having to force UDS for both on site and mobile access.  Also in this scenario I had to sync all four AD forests to All four UC clusters...  1 of the forest on each cluster sets the User for home cluster, the other 3 I just apply a feature group template that does not enable any services, nor does it set the home cluster option.  Supposedly if you have a single AD forest with multiple subdomains, EDI or BDI is supported for Flexible JID.  I am running 10.5.2 im&p and 10.6 on jabber.  One side not on this one though, I am having to fight with presence issues being shared between exchange, etc..  so it is not the ideal way to implement this solution, but the name resolution portion will work as advertised.

Cisco Employee

Using:

Using:

   <IMAddresses use-default="false">
      <IMAddress>mail</IMAddress>
   </IMAddresses>
is unsupported. If you are using this configuration you are in an unsupported configuration and will not be supported by Cisco.
The only correct config is:
<Directory>
  <SipUri>mail</SipUri>
  <UseSIPURIToResolveContacts>true</UseSIPURIToResolveContacts>

  <BDISipUri>mail</BDISipUri>
  <BDISipUriToResolveContacts>true</BDISipUriToResolveContacts>
</Directory>
New Member

Jabber 10.6 will have the

Jabber 10.6 will have the ability for Flexible URI. The expected date to be released is 27 Jan 2015.

Its bad that Cisco is releasing IM & P that has the URI option and Jabber is not.

This confused alot of people and they have created a defect for that:

CSCuo95266    Jabber Windows and directory URI address scheme in IMP 10.x -doc defect

New Member

Hello.We were able to solve

Hello.

We were able to solve this as well. We are using UDS only.

We have the following:

CUCM 10.5.1

IM&P 10.5.1

Jabber 10.6 - We had to reset all instances of this to get the proper jabber-config.xml to download. Then remove contacts and re-add.


On our CUCM service profile for Jabber we have Directory / LDAP set to none, however, we have Use UDS checked.
 

Here is our jabber-config.xml. Also make sure your tftp is reachable, and also that you have saved the xml file in utf-8 text format.

 

<?xml version="1.0" encoding="utf-8"?>
<config version="1.0">
 <Policies>
   <EnableSIPURIDialling>false</EnableSIPURIDialling>
   <DirectoryURI>mail</DirectoryURI>
 </Policies>
 <Presence>
  <PresenceServerAddress>presence-server-address-here</PresenceServerAddress>
  <PresenceServerDomain>presence-server-domain.com-here</PresenceServerDomain>
 </Presence>
 <Directory>
   <IMAddresses use-default="false">
      <IMAddress>mail</IMAddress>
   </IMAddresses>
   <UseSIPURIToResolveContacts>true</UseSIPURIToResolveContacts>
   <SipUri>mail</SipUri>
   <DirectoryServerType>UDS</DirectoryServerType>
   <PresenceServer>presence-server-address-here</PresenceServer>
   <UdsServer>callmanager-server-address-here</UdsServer>
 </Directory>
</config>

 

Bronze

Hi, That config has given me

Hi,

 

That config has given me some progress thanks. The thing is up the top of the jabber application it displays the URI of the logged in user and not FirstName LastName, did you have this issue? If so were you able to resolve it?

 

 

Thanks

New Member

Hi,I think this problem is

Hi,

I think this problem is discussed in this thread:

https://supportforums.cisco.com/discussion/11512806/jabber-windows-name-displayed-userdomain

best regards

New Member

Hi,solved the problem, a

Hi,

solved the problem, a space is missing in the XML script:

from your post

<IMAddressesuse-default=”false”>

correct:

<IMAddresses use-default=”false”>

Philipp

Bronze

Hi,I cannot find any

Hi,

I cannot find any documentation (Jabber 10.6 deployment guide, directory sources section) on the parameter <IMAddresses use-default="false"> or generate that output using the tool. Is there anything you can link?

 

I do have my jabber 10.6 clients being able to display the ChatIM address as desired but the top of the client displays the URI format of the user and not FirstName LastName. People in the jabber directory and contact list are displayed as the FirstName LastName along with the correct URI.

 

My Jabber clients are using UDS, which again is confusing as some presence doco states need to use AD but Jabber 10.6 slide decks states you can have UDS. I would like to use UDS.

New Member

Hi,this was also my intention

Hi,

this was also my intention to search through the jabber deployment guides and I did not find them either.

but as the message was from a cisco contact I gave it a try and it was working.

the problem seems to be that jabber, by default, does not support the Directory URI option which is already available within the server configuration. it was suposed to be implemented with version 10.6 but it seems it wasn't.

the problem was that, when displaying the profile of a user that is in your address book (not an already added contact) the userid@defaultdomain was displayed as IM address.

when you go to New => Company Contact and you add the full mail address (do not press TAB) the IM chat field is updated for the contact.

the IMAddress option did update this with the mail adress which is also our IM chat address.

Philipp

Bronze

Hi,  Are you using EDI or UDS

Hi, 

 

Are you using EDI or UDS?

 

Are you able to attach your jabber-config.xml file obviously remove/replace any details. I ended up using the generator tool and replaced anything that resembled a lookup to use 'mail'. Trying to cut it back to just the IMAddress or generating the file without default values didn't work. I'm really just trying to resolve the display name of the logged in user to change it to Firstname Lastname and not display the URI

New Member

Hi,we are on EDI and using

Hi,

we are on EDI and using Active Directory in the background.

Philipp

Bronze

Thanks, will test it out

Thanks, will test it out tomrrow

Cisco Employee

Not supported yet, targeting

Not supported yet, targeting 10.6  version jabber. 

Tapan

New Member

Hi,we solved the problem, we

Hi,

we solved the problem, we are using:

- jabber 10.5.4

- cucm 10.5.2

- presence server 10.5.2

 

in the jabber-config.xml on the CuCM we added the following values:

 <Directory>
   <IMAddresses use-default="false">
      <IMAddress>mail</IMAddress>
   </IMAddresses>
   <UriPrefix>sip:</UriPrefix>
 </Directory>
 
also check in Presence => Domains that prints "The IM Address scheme is set to Directory URI"
 
best regards
 
Philipp
New Member

Using one of your config file

Using one of your config file lines fixed a similar problem I was having. Instead of the Jabber IM address resolving to username@domain it was resolving to sip:username@domain for directory look ups only (searches).

 

Adding in this line seemed to fix the problem:

<UriPrefix>SIP:</UriPrefix>

or

<UriPrefix>sip:</UriPrefix>

 

The UriPrefix parameter is case sensitive, FYI.

 

Thanks

- Stephen

New Member

I have the same issue, the IM

I have the same issue, the IM address is correct in CUPs, but not in Jabber. LDAP is working properly in Jabber, no errors.

 

Tom

Hi,we solved the problemin

Hi,

we solved the problem

in the jabber-config.xml on the CuCM we added the following values

 

<?xml version="1.0" encoding="utf-8"?>
<config version="1.0">
 
 <Presence>
  <PresenceServerAddress>172.1.1.3</PresenceServerAddress>
  <PresenceServerDomain>domain.com</PresenceServerDomain>
 </Presence>
 <Directory>
  <ConnectionType>1</ConnectionType>
  <PrimaryServerName>172.1.1.15</PrimaryServerName>
  <ServerPort1>389</ServerPort1>
  <UseWindowsCredentials>0</UseWindowsCredentials>
  <ConnectionUsername>admin@domain.com</ConnectionUsername>
  <ConnectionPassword>password</ConnectionPassword>
 </Directory>
</config>

5075
Views
20
Helpful
30
Replies