02-06-2016 03:04 PM - edited 03-17-2019 05:51 PM
02-06-2016 04:29 PM
The default behavior for a Jabber client using EDI is the binary object and the thumbnailPhoto attribute so the XML file you have shown isn't really accomplishing anything. The most likely reason this failed was because the Global Catalog database (which Jabber connects to when using EDI by default) doesn't have the thumbnailPhoto attribute. You need to enable this and, while you're at it, verify that you have the required parameters indexed so you don't adversely impact the performance of AD.
http://www.cisco.com/c/en/us/td/docs/voice_ip_comm/jabber/11_5/CJAB_BK_J06BEF2D_00_jabber-parameters-reference-guide-115/CJAB_BK_J06BEF2D_00_jabber-parameters-reference-guide-115_chapter_01001.html#CJAB_RF_AE445EC6_00
In the case of the PhotoUriWithToken the most immediate mistake is that you incorrectly capitalized the A in NAme. If that doesn't fix it you may want to run a packet capture and see if Jabber attempts to make the HTTP GET and if it does, whether it runs into problems (e.g. maybe the IIS server is incorrectly requiring authentication).
02-06-2016 05:34 PM
I forgot to mention that i added the thumbnailPhoto in global catalog by using following procedure. when i added the thumbnail photo in global catalog and press ok, it tells me to save it. i saved it with the name of Console.
can you please elaborate regarding the parameter indexing. this is a test environment so i have couple of users configured in AD for testing.
Regarding PotoUriwithToken i will update the jabber-config file and update on this forum.
02-07-2016 03:49 AM
Hi,
I did packet capture for Scenario 2 but it seems like Jabber is not even sending "GET HTTP" request to the web server. do we need to enter the IP address of webserver in "jabber-config.xml" file or we have to define somewhere in CUCM. i have attached packet capture of wireshark having the following ip address of devices.
CUCM: 10.172.192.1
DC/WebServer: 10.172.192.8
End user: 10.172.192.110
03-10-2016 10:54 AM
Hi Naray,
I am having the exact same problem. Jabber contact photo's are not being displayed for J4W using PhotoURI from an IIS server. After spending a considerable amount of time with TAC, they mentioned that the AD attribute needs to be in a Unicode String Syntax. In the current AD environment we are testing in, the thumbnailPhoto is not in this syntax and we are testing using alternative AD attributes for the URI Token.
Let me know if this issue has been resolved for you.
Regards,
Ray
04-26-2016 02:49 PM
Late update, we found the issue. We had these parameters in the jabber-config.xml;
<DomainName>mail</DomainName>
<BDIDomainName>mail</BDIDomainName>
It was causing problems and once removed, contact photos from PhotoURI using tokens started working. Unfortunately now, we have an ever growing number of users saying that the photos of a particular contact is incorrect. Checking the file on the Web Server, it is correct however it appears Jabber is saving the photo incorrectly into the local Photo Cache. A 'Reset Jabber' fixes the issue for that local user but is the problem occurs for other users.
J4W 11.5.0
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide