Solved: Jabber 12 client lost pictures

Doug · ‎04-09-2018

Just downloaded Jabber 12. All was working on 11. We are on the latest Cisco telephony infrastructure.

After restarting Jabber with new version 12. Lost all contact pictures. Can clear all cache and restart and pictures appear. Little later they are gone again.

Any suggestions?

Adam Pawlowski · ‎06-12-2018

If you look at the end user profile under User Management -> End User you can see a UC Service Profile there. Those are in total listed under User Management -> User Settings -> Service Profile . Clicking on view details will show you the parameters, and that checkbox is present under Directories. Similarly if you press Shift - Control - D within Jabber you'll see a diagnostic screen, you can scroll down and click to see the XML of the service profile (not really needed here) or further down under where it says "Active Directory" for whatever reason, directory source is listed.

If it is UDS then you must host the JPEG files somewhere. If it is LDAP then you need to make sure that the data is (I believe - someone else would have to correct me if I'm wrong) stored in the thumbnailPhoto attribute I believe. If that attribute moved, or changed formats, that may have also broken it.

View solution in original post

Jaime Valencia · ‎04-09-2018

Where do you have your pictures and what configuration do you have in place?

HTH

java

if this helps, please rate

Doug · ‎04-09-2018

Getting pictures from LDAP. The only difference is the client version 12. Version 11 of any sub-version works perfectly, or any lower version.

Jaime Valencia · ‎04-09-2018

What do you use as LDAP?

I have MS AD 2012 in my lab and it worked fine after the upgrade.

HTH

java

if this helps, please rate

Doug · ‎04-10-2018

Our domain is at 2008 R2 functional level. LDAP sync is through CUCM configuration.

Jaime Valencia · ‎04-10-2018

That shows as a supported release, you'd probably need to review a PRT to confirm all the config Jabber is receiving is correct and it's trying to get the images.

You could also try to login with other credentials to reset Jabber and see if you get the same behavior, or reset, delete all the cache, and try again.

HTH

java

if this helps, please rate

Doug · ‎04-11-2018

Reset did not help. Also attempting to clear: \AppData\Local\Cisco\Unified Communications\

\AppData\Local\Cisco\Unified Communications\Jabber\CSF\Photo CachePhoto does not re-populate. Everything else under CSF does. Does that help? I don't know, (guessing),. would it have anything to do with DHCP settings for TFTP?

Jaime Valencia · ‎04-11-2018

No, DHCP and TFTP have nothing to do, you want to review a PRT for this.

HTH

java

if this helps, please rate

Doug · ‎04-11-2018

Help me out please. PRT? Just recently digging into Jabber.

Jabber.log has photoUrlTemplate=, again I assume this is important, maybe not.

Doug · ‎04-11-2018

Need to change something. Appears the client does not matter. Could be our new CUCM which is now version 12. Removed version 12 Jabber client, removed all files on c: drive. Installed a v11 client. Same issue, no photo cache. So, maybe it is actually in the CUCM config.

Jaime Valencia · ‎04-11-2018

That, or there is some problem with the connection to LDAP, but given that, you want to review your config and your .xml in case you have photo configuration there, and something is wrong.

I have Jabber 12.0 in my lab with CUCM 11.5(1)SU4 and CUCM 12.0 with MS AD 2012 R2 for pictures and they both work fine.

HTH

java

if this helps, please rate

Doug · ‎04-18-2018

Just an update: still have not found setting to correct this.

Adam Pawlowski · ‎04-22-2018

If it pulls from LDAP/AD directly , then you should make sure they attribute is on all servers (iirc they do SRV based server lookup now). Similarly, the log and maybe a sniffer trace would show you what contact is resolving to ensure you’re looking at the right record.

Works fine for me with UDS and photo URL in 12

Doug · ‎06-12-2018

Finally got the LDAP - LDAP Search -> UDS config implemented in CUCM. No change. Still no pictures, ran LDAP Sync. Nothing. Cleared all caches, no pictures. Nothing at all in the photo cache directory as before.

Adam Pawlowski · ‎06-12-2018

Right, all that does is cause the UCM to search for contacts via LDAP and present them in UDS results.

You still need to use the photo URL and an external server to host the data if you are not using LDAP.

If you look at the active service profile, there's a checkbox of "Use UDS for contact resolution" which drives this when you are not using the Collaboration Edge. If you are, then it is ALWAYS UDS regardless of the service profile and LDAP server configurations.