Jabber 9.7 problem with Presence outlouk and with photos

[chrysostomos1980]

Hi Community

First issue:

When we had jabber version 9.6 the photos appearing correctly into the jabber

Now with the 9.7 the photos not working

we are using UDS

Below is the config from the jabber-config.xml file

 <Directory>
  <DirectoryServerType>UDS</DirectoryServerType>
  <UdsPhotoUriWithToken>http://Active directory name.domain/%%uid%%.jpg</UdsPhotoUriWithToken>
 </Directory>
 

Second issue:

Either with 9.6 or 9.7 the presence status into the outlook is not working

Could you pls help with the above's issues?

Regards

cc

[Emmanuel Valdez]

Hi,

Your issue is only with jabber for windows?

Can you post your jabber-config.xml? you can obtain it with the following url.

http://ccm-ip-address:6970/jabber-config.xml

Did you tried to integrate with EDI?

Regards.

[chrysostomos1980]

Hi Emmanuel

First thank you very much for the help

Some questions about EDI:

1)

If i use EDI instead of UDS then i have to modify ONLY the xml file?Nothing else into CUCM?

2)

<ConnectionUsername>LDAP_Jabber_Username@domain.com</ConnectionUsername>

<ConnectionPassword>LDAP_Jabber_Password</ConnectionPassword>

What credentials are the above?

3) Y.Y.Y.Y is the webserver where photos are store.: We have stored the photos into the LDAP and not to any external web server.

[chrysostomos1980]

Hi

We have also a full collaboration edge deployment here ( Expressway C and E)

We cant change it to EDI , because may other issues coming after that

what do you believe?

[chrysostomos1980]

Hi

i didnt check with other devices , only with windows

I prefer UDS either of EDI

<?xml version="1.0" encoding="utf-8"?>
<config version="1.0">
 <Presence>
  <PresenceServerAddress>10.10.10.10</PresenceServerAddress>
 </Presence>
 <Presence>
   <PresenceServerAddress>10.10.10.11</PresenceServerAddress>
 </Presence>
 <Directory>
  <DirectoryServerType>UDS</DirectoryServerType>
  <UdsPhotoUriWithToken>http://Active directory name.domain/%%uid%%.jpg</UdsPhotoUriWithToken>
 </Directory>
 <Policies>
<EnableSIPURIDialling>true</EnableSIPURIDialling>
</Policies>
<Policies>
<EnableSIPURIDialling>true</EnableSIPURIDialling>
<VoiceServicesDomain>dfg.com</VoiceServicesDomain>
<RemoteAccess>ON</RemoteAccess>
</Policies>
</config>

[Emmanuel Valdez]

Hi,

Try using EDI instead UDS, if you don´t use encryption use this configuration,

<config version="1.0">

<Presence>

<PresenceServerAddress>10.10.10.10</PresenceServerAddress>

</Presence>

<Directory>

<DirectoryServerType>EDI</DirectoryServerType>

<PrimaryServerName>X.X.X.X</PrimaryServerName>

<ServerPort1>389</ServerPort1>

<UseWindowsCredentials>0</UseWindowsCredentials>

<ConnectionUsername>LDAP_Jabber_Username@domain.com</ConnectionUsername>

<ConnectionPassword>LDAP_Jabber_Password</ConnectionPassword>

<BusinessPhone>ipPhone</BusinessPhone>

<SearchBase1>OU=Users,DC=domain,DC=com</SearchBase1>

<PhotoUriSubstitutionEnabled>true</PhotoUriSubstitutionEnabled>

<PhotoUriSubstitutionToken>sAMAccountName</PhotoUriSubstitutionToken>

<PhotoUriWithToken>http://Y.Y.Y.Y/photos/sAMAccountName.jpg</PhotoUriWithToken>

</Directory>

</config>

X.X.X.X is your LDAP and Y.Y.Y.Y is the webserver where photos are store.

Let me know if you have any question.

Please rate if it was useful.

Regards.

[Emmanuel Valdez]

Can you post the status connection for your jabber client? under help menu it´s the third option.

Regards.

[Emmanuel Valdez]

Hi,

1)

When you use EDI the first step is to synchronize your CUCM with your LDAP, for his example I integrate Microsoft AD and I chose sAMAccountName for the User ID Attribute (Image 1).

Then you have to create your UC service under User Management>User Settings>UC Service (Image 2)

Then create your Service Profile and associate the UC Service (Image 3) that created before.

Then apply the Service Profile to the users that were syncronized from LDAP.

Finally upload your jabber-config.xml and restart the TFTP Service.

Probably you already have these parameters, so you only need to upload the new jabber-config.xml

2)<ConnectionUsername>*LDAP_Jabber_Username@domain.com></ConnectionUsername>

This parameter is the user that can access the LDAP Scheme to obtain the users on the correct OU. For example cisco_jabber@myenterprise.net if you don´t know this user name you can use the administrator user but I don´t recommend it if you don´t use Secure LDAP

<ConnectionPassword>*LDAP_Jabber_Password*</ConnectionPassword>

This is the password for the user that access your LDAP Scheme.

3)

If your LDAP is the web server you only need to repeat the IP address on the jabber-config.xml file.

If you need anything else please let me know and if it was useful plese rate.

Regards.