Today I noticed that Sametime awareness was not working in Verse. Since it did until a few days ago I started to look what could be wrong. I tried to log in to Sametime and could not. Alas, time to look at the logs on the server; doing so I noticed a strange error in the community container log. A timeout when connecting to my LDAP server. I checked my Domino server, which is my LDAP and everything was fine. So I started a remote session with my Linux box where I have installed Sametime and all of a sudden weird errors appeared when I tried to change directory from / to /sametime. A look at the filesystem left me horrified. I had the disk full!!!

Sametime 12.0.1 introduced a new feature, a monitoring dashboard based on Grafana. But on Docker it was not working, in various panels, for example those related to meetings it showed “no data”. Some of us reported this to HCL and they told that a fix would be provided for FP1.

I set up the monitoring dashboard in Sametime, using the provided JSON files; in case you don’t know how to do that, you enable it running this command docker-compose -f docker-compose.yml -f docker-compose-monitoring.yml up -d https://help.hcltechsw.com/sametime/1201/admin/Managing_dashboard.html Today I discovered that my Prometheus container kept crashing, and in the logs I found lines like these

Upon suggestion from my friend Erik Schwalb of HCL, I upgraded to FP1 a Sametime12 server where I made some branding customization. Contrary to what I wrote in my previous post not ALL customizations are kept.

I updated the Sametime Proxy server 11.5 to IF1 for a customer, and the integration with iNotes broke. When a user tried to start a chat with another user he received an error

Since in my test environment I do not have a proper domain name I had to tweak a bit some configuration settings in order to make the installation work; this can be useful if you want to setup a Meeting server inside your network using a domain like .local instead of your company real domain and hosts file instead of DNS.

In my previous post here I described how to set up a Jitsi server using the Domino directory as LDAP. That setup required all the users to authenticate before joining a room.

I have worked with my friend and fellow HCL Master Detlev Poettgen in setting up a solution to allow customers to use video-conferencing now, while we wait for Sametime Meetings to ship. We have used Jitsi, the same technology used by Sametime meeting, and set up a raw integration. Is obviously not a fully integrated solution, but it works pretty well.

Sametime 11 FP1 has shipped, so me and my fellow Master and friend Matteo Bisi started upgrading our test servers immediately. We found a couple of thing you may want to be aware of in order to upgrade successfully.