Hello Leonardo,
Few questions for you, does it work for Jabber for Windows users?
Where are the pictures stored? AD or a web server?
Is this client connecting to the directory at all? if you look for someone do you see reults in "directory"? or just "contacts and recents?
Non domain computers don't connect automatically to your AD for directory search, adding an XML can help, here's one that worked for a customer(Mac users):
<?xml version="1.0" encoding="UTF-8"?>
<config version="1.0">
<Directory>
<BDILDAPServerType>AD</BDILDAPServerType>
<BDIPrimaryServerName>AD_IPADDRESS</BDIPrimaryServerName>
<BDIEnableTLS>False</BDIEnableTLS>
<BDIServerPort1>3268</BDIServerPort1>
<BDIConnectionUsername>admin@jabbermac7.net</BDIConnectionUsername>
<BDIConnectionPassword>xxxxxx</BDIConnectionPassword>
<BDISearchBase1>OU=User Accounts,DC=US,DC=example,DC=com</BDISearchBase1>
<BDIBusinessPhone>telephoneNumber</BDIBusinessPhone>
<BDIPhotoSource>thumbnailPhoto</BDIPhotoSource>
<BDIPresenceDomain>jabbermac75.net</BDIPresenceDomain>
</Directory>
</config>
You can save this as an xml and test if a browser can open it, if so make it global by uploading it to CUCM and restarting TFTP, do make sure there's not an xml already in there, you can check by putting in a browser your TFTP's IP :6970/jabber-config.xml so the url would be: http://X.X.X.X:6970/jabber-config.xml
The connection username and password should be from a user that has at least read access on the OU where the users are located.
And the BDIPresenceDomain should be AD's domain.
Cheers,
Oscar
