We are testing the jabber for ipad now and the contact photos do not show up, this really have confused me for several days, here's the information:
IM & Presence version:9.1
Jabber for IPAD version: 9.6
Everything works fine (contact phone number, call, etc) except for the contact photo. We've already mapped the LDAP attributes at IM & Presence: Application > Legecy Clients > Settings, we fill in the attribute of photo with the URL http://192.168.1.120/%%sAMAccountName%%.jpg. And we can open the picture with that URL in the browser , however, the photo does not display at our Jabber clients. Can anybody help me with this? We use IIS for the web service.
The same situlation exists on my windows client. I use the xml file to show the photo and disallow the file type which cannot be transferred. however, only the contact photo does not show up. Someone please help me.... Thanks so much
For just now, i deleted the contact cache at my windows PC and re-login the Jabber, then the photos show up successfully, however, the Jabber for IPAD&Iphone still refuse to show me the photos even though i re-installed them for several times.
The J4W works fine now and the photos show up successfully, the problem now is all about the jabber for ipad. I think the jabber-config.xml is just related to the J4W and what affects the Jabber for ipad is the LDAP attributes map at IM & Presence, isn't it :)?
The above paragraph needs to be adjusted in your file.
Jabber for ipad in 9.6 should be able to get thumbnail photo source by default provided this information is successfully replicated across all the global catalogues.
"BDIPresenceDomain" is the value of the sip proxy domain name of cups. In order to find out what is the sip proxy domain name in your case here is what you can do;
go to cups admin page\ click system\ cluster topology \ click settings\ on the rt. hand side check what is the value specified under Domain Name; and then ensure that is implemented under "BDIPresenceDomain" in the jabber-config.xml
"BDIPrimaryServerName" needs to be the address of preferably a global catalogue if you are using a Microsoft AD server.
"BDIConnectionUsername" Expecting your AD ldap domain name is test.com the format in which you would like the "BDIConnectionUsername" is email@example.com
where alias is the userid/alias of the user which has read access for AD.
Are you getting this error “Installer User Interface Mode Not Supported. The installer cannot run in this UI mode. To specify the interface mode, use the -i command-line option, followed by the UI mode identifier. The value UI mode identifiers...
The below trick might come handy when you have to add a new node to a cluster but you don't have or is unsure of the security password for the publisher. This procedure has been around for ages.
1) Login into the CLI of the Publisher.