We have configured an external webserver to store our contact photos. But I couldn't get it working on Jabber windows clients. It works for CUPC8.5. I run the wireshark on webserver and can't see any request from Jabber client. xml file is -
<?xml version="1.0" encoding="utf-8"?>
Can someone please advise what's the issue.
The file content seems ok. What would help troubleshoot this better would be a sniffer from the local workstation to see if at all being is sending out the request.
Also just to test, from the workstation, try manually going to the browser using the Web Server link.
Let me know what you see in the local packet capture.
Sent from Cisco Technical Support Android App
Thanks for the reply. I can access the photos by manually typing the address on to a webpage. Also, CUPC on the same pc can fetch photos successfully.
Seems like we would need to add the following attributes to the jabber file itself:
Please add that and test again.
Tried that but it didn't work. The problem is that our webserver is not getting any request from the jabber client but get request from the cupc client from the same pc.
Ok, so post me the content of the exact jabber file and also if you can take a packet capture :
1) Start Packet Caputure
2) Start Cisco Jabber
3) Wait till the presence status shows correctly
4) Stop Packet Capture.
Filter on the WebServer IP address and then see if there are any responses sent to the server
First I was thinking perhaps we may have the incorrect Parameter to pull the contact images and that maybe its not sAMAccountName and perhaps uid, however, even if was incorrect, we should see some info be requested from the Web Server, its as if, Cisco Jabber is not reading the Config File.
Can you tell me where the config file is located on the workstation.
Also let me know what the parameter is for the Photos under LDAP Attributes on CUPS Admin -> Application -> CUPC -> Settings
We may have to pull a clean detailed PRT to see exactly what is going on. Please refer to this Post for the details on deleting the old logs and then recreating the problem:
So let me know the location of the file, also provide the PRT and I'll take a look.
Parameter sAMAccountName is correct as this is working with CUPC client. But I did try to use uid as well but still no response.
Config file is located at - c:\Documents and Settings\Username\Application Data\Cisco\Unified Communications\Jabber\CSF\Config.
Parameter for the photos in CUPS - http://webserver/people/%%sAMAccountName%%.jpg
I tried following the link but there is no log folder under CSF in my workstation. But I have attached the fresh PRT logs, please have a look and let me know for any question.
I noticed that your jabber-config xml file is slightly wrong. In there you have the line:
The correct line is:
Please make the appropriate change in Jabber Config XML file and try again.
I did use
In the PRT, I see the following:
2012-05-28 09:02:16,733 DEBUG [0x00001654] [s\feature-libs\config\src\Config.cpp(74)] [csf.unified.config] [Config::getValue] - result [true] key [PhotoUriWithToken] value [http://
I understand that you changed the parameter to see if we can even pull a single image for anyone, however, what I see next is:
2012-05-28 09:02:16,733 DEBUG [0x00001654] [rdsource\ADPersonRecordSourceLog.cpp(50)] [csf.person.adsource] [WriteLogMessage] - Configuration::SetConfigurationParameter - setting configuration parameter [PhotoSource] to [adack] //This needs to be AD Parameter which I see you used earlier
2012-05-28 09:02:16,733 DEBUG [0x00001654] [rdsource\ADPersonRecordSourceLog.cpp(50)] [csf.person.adsource] [WriteLogMessage] - Configuration::SetConfigurationParameter - setting configuration parameter [PhotoUriWithToken] to [http://pho/people/adack.jpg]
Do you know where this url is coming from?
I suggest that based on Jason's input and as well as changing the parameter back to the one we want, lets follow this action plan:
1) Exit out of Jabber and delete the files from the following location:
C:\Documents and Settings\
2 ) Modify the Jabber-Config.xml
Change the Directory Section of the Jabber-Config.xml to the following
3) Re-login and then Generate the PRT by Help -> Report Error
Keep in mind if the jabber-config.xml is uploaded on Call Manager, it'll replace any local modification, so we have to update the file on Call Manager .
Once we have the new PRT with the Config provided above, I can work on that.
Thanks for providing the new file.
In the logs I do see the config file being implemented,
2012-05-28 10:24:50,952 DEBUG [0x000012b8] [rdsource\ADPersonRecordSourceLog.cpp(50)] [csf.person.adsource] [WriteLogMessage] - Configuration::SetConfigurationParameter - setting configuration parameter [PhotoUriSubstitutionToken] to [sAMAccountName]
2012-05-28 10:24:50,952 DEBUG [0x000012b8] [rdsource\ADPersonRecordSourceLog.cpp(50)] [csf.person.adsource] [WriteLogMessage] - Configuration::SetConfigurationParameter - setting configuration parameter [PhotoUriWithToken] to [http://
I'll research more to see if we are missing any additional configs and will update you then.
Glad I found this thread. I have exactly the same issue with Abhi at the moment with my Jabber client. Photos are stored and retrieved on a standalone HTTP server, works perfectly with CUPC (8.5.1) but not Jabber (9.0.1). I'll be watching this thread with interest for potential resolution.
Please keep the discussions coming.
I have the exact same problem too.
Hosting my jpg on and http server and all is well with CUPC 8.5. As soon as I delete CUPC on PC and install Jabber for Windows 9.0.4 then no photos.
Funny thing is I have upgraded the iPads to Jabber for iPad and photos work there and also work on Jabber IM for iPhone. Come on Cisco! Don't make us re-invent the wheel again...
I'm watching this thread too. This is our Verizon UCCaaS demo that we deliver demos to for customers. Kind of embarrasing that Lync has Photos and we don't. This should be simple and you should be able to upgrade a client on a PC and not have things not work.
Judging by the number of views on this thread, there are quite a number of people having the same issues. Just like share that the problem still persists with Jabber for Windows 9.1.1. This issue has now become a showstopper for us to upgrade from CUPC to Jabber. Any help on this would be much appreciated.
anyone was able to solve this issue? We seem to be hitting the same problem.
We managed to resolve the issue ourselves. In contrast with CUPC8.5, which does not necessarily need a manually configured client configuration file for it to work, Jabber mandates it. So for those guys who had contact photos working with CUPC8.5 using HTTP server and not working whilst using Jabber 9.1 for Windows, try this:-
- Manually create a jabber-config.xml using the following guide:-
or you can create it using the "config file generator" posted here
https://supportforums.cisco.com/docs/DOC-25778. The bare minimum for contact pics using HTTP server ONLY to work is:-
- Upload this file onto a TFTP server (CUCM recommended as per
- Test whether you can access this config file from where the Jabber client is installed by browsing
After doing the above, contact photo using HTTP server on Jabber for Windows should work providing that there's no other connectivity issues.