If you want to enable photos in the Sametime client, there is documentation available, unfortunately it all refers to versions 9 or 10, where it was told to use the Sametime Console. Now in version 11 the Sametime Console does not exist, so how do you do that ? The Sametime Console wrote the settings selected in a series of XML configuration files, so the only way now to work is manually edit those files, see for example my previous post on enabling file transfer. With the help (again) of the excellent Trevor Tallackson from HCL I was able to set up the pictures in Sametime, here is how to do it
First add the picture URL in the person document in the Domino directory
Now edit the file UserInfoConfig.xml located in the Domino program directory and add those lines <Detail FieldName="PhotoURL" Id="PhotoURL" Type="text/plain"/> <Detail FieldName="PhotoURL" Id="ImagePath" Type="text/plain" /> in the section <Details> Add these two Detail Ids to the <ParamsSets> section <Set SetId="0" params="MailAddress,Name,Title,Location,Telephone,PhotoURL,ImagePath,Company"/> <Set SetId="1" params="MailAddress,Name,Title,Location,Telephone,PhotoURL,ImagePath,Company"/> These are needed because in the UserInfoConfig.xml file on the Sametime Community server, the Standalone Connect client and Embedded require ImagePath string detail, Mobile and Web clients require the PhotoURL detail
Note: do not copy/paste from above. I had reports it does not work well. Just add PhotoURL and ImagePath to the params= line.
For me it was not working initially, then Trevor wrote me this: Looks like the stconfig.nsf “UserInfo” document is getting in the way here. Add the following to your UserInfoConfig.xml file between <UserInformation> and <Resources> <ReadStConfigUpdates value= “false”/> This tells the UserInfoServlet to only use the UserInfoConfig.xml configuration.
Restart the server and now you have pictures in Sametime client
I stumbled into a problem at one of my customers. In the client, the icon for file transfer was greyed out and the one for sending a screenshot was missing,
I opened a case with HCL and the suggestion was to enable the setting im.3000 in the file policies.user.xml. to do so you have to edit the line <p:policy-attribute id=“im.3000” type=“boolean” current-value=“1” default-value=“1" master-attribute-link=“null” possibl ..... By default the current-value is 0, you have to set it to 1 I did that but the file transfer was not available the same.
After checking the file I found that there were 2 occurrences of im.3000, one for the im.default.policy and the other for the im.anonymous.policy, the problem is that this setting is written only in the section “imserver.policygroup.chat”. I copied the lines from that section and added them in the “imserver.policygroup.filetransfer” section. <p:policy-attribute id="im.3000" type="boolean" current-value="1" default-value="1" master-attribute-link="null" possible-value-labels="null" possible-values="null" label="im.3000.label" description="im.3000.desc" visible="true"/>
Restarted the server and now in the client I had this
I checked with HCL, file transfer and screen capture are not allowed with Sametime limited use license. You should use the content of this blog post only to fix issues if you have a standard license and file transfer is not working. If you enable file transfer, you should upgrade your license to be compliant.
I installed a Sametime 11 server for a customer, everything was working, but the mobile clients could not access the server. Upon trying to login they saw this on their phones
I was not the only one with this problem, other 2 persons I know had the same issue with their installation.
I talked to my friend Andreas Ponte, from Belsoft who told me that they could use mobile clients, so we crosschecked our configurations. and it turned out that my customer sametime.ini had this line ST_BRANDING_INFO=entry while his had ST_BRANDING_INFO=standard As soon as I changed the sametime.ini and restarted, the access from mobile devices was working.
I had installed Sametime withe the option “limited” because this is the license my customer has
So, the solution is simple but I have asked HCL to clarify. As far as I know since V10 the limited license allows the use of mobile clients, and I do not think this has changed in V11
I received a mail from HCL stating this: For now, the workaround is to add the stanza to the stproxyconfig.xml and NOT change the ST_BRANDING_INFO in sametime.ini, since that setting controls other features/UI of the clients if you are only licensed for ENTRY.
I struggled a bit in setting up integration of Sametime 11 with Domino web mail, both iNotes and VoP, but eventually with the help from the great Trevor Tallackson of HCL Sametime Support I succeeded.
There are some things not obvious to do to set this up, and the one for VoP made me almost drop my jaw when Trevor suggested it 🙂
iNotes Web Access I have installed both Community Server and Proxy Server on the same machine, so in the Domino Configuration document for my server, in the tab iNotes, in the Sametime section I have put the hostname of my server as “Location of the Sametime proxy server to use when using https:” which is https://domino.eld.it:8443
We could not understand why though in the notes.ini of the server the parameters were correct, the server tried to access domino.eld.it and not proxy.eld.it In my notes.in i I had this iNotes_WA_SametimeProxy=1 iNotes_WA_SametimeProxyServer=http://proxy.eld.it:8080 iNotes_WA-SametimeProxyServerSSL=https://proxy.eld.it:8443 VOP_GK_sametime=1 VOP_GK_sametime_rich_client=0
Trevor checked his notes.ini on the server where the integration was working and saw that those lines were all caps and wrote me:
This may seem silly, but try the notes.ini parameters all in caps. Here is our production server’s notes.ini (that is working fine). INOTES_WA_SAMETIMEPROXYSERVERSSL=https://<Our_hostname>; VOP_GK_SAMETIME=1 VOP_GK_SAMETIME_RICH_CLIENT=1
I tried his suggestion and guess what ? It worked! Honestly I have no idea why with V11 the lines have to be all caps, I told Trevor that I leave up to him to find the reason, but as silly as it may seem this is the solution. I would never have guessed it in a million years…..