Install and Configure Sametime Meetings Pre-Release 11.5

Hello,

We are in the process of evaluating Sametime Meetings 11.5 Pre-Release. We have successfully upgraded Sametime Community/Proxy to FP2. We have also upgraded underlying Domino to latest fix pack.

We have followed every instruction in the following documentation
https://help.hcltechsw.com/sametime/11.0.2/admin/enable_sametime_meeting.html

Domino/Sametime Community/Proxy have been installed and configured on a single CentOS VM. Sametime Community server is up and running without any issues. tested with both web and mobile clients and no issues encountered.

We are now trying to install and configure Sametime Meetings 11.5. the issue we are facing now is that the meetings login page doesn't have login button at all. It has only JOIN button. After entering the credentials the page successfully authenticates and navigates to the next page. But the subsequent page will have option only to join a meeting with a message stating that to start a meeting login to sametime. But i am already successfully authenticated and the display name on the meetings page indicates that i have been authenticated.

SSO between community and meetings server also works. In a single browser window if i am already logged on to Sametime web client and navigating to Sametime meetings will allow me to meetings home page without authenticating.

Actually before this we were ahead of this where we were successfully logged in and started a meeting. But even then we had issue where after someone joins loading meeting page starts loading again and again. But now after several restarts we actually went back where even the login is not working...to say login is working but only JOIN.

Please find attached the files required for debugging. Do let us know if you require any additional info.

Domino
notes.ini

Sametime Community
sametime.ini
sametime.log
ststart

Sametime Proxy
stproxyconfig.xml
dbconfig.properties
zipped logs folder

and on Sametime Meetings server on docker we are seeing following exceptions
jicofo_1 | Jicofo 2020-09-02 07:57:25.421 WARNING: [58] org.jitsi.jicofo.JvbDoctor.log() Health check failed on: jvb@auth.sametime.test/tH_s0cmd error: <error type='cancel'><internal-server-error xmlns='urn:ietf:params:xml:ns:xmpp-stanzas'/><text xmlns='urn:ietf:params:xml:ns:xmpp-stanzas' xml:lang='en'>java.lang.Exception: Address discovery through STUN failed</text></error>
jicofo_1 | Jicofo 2020-09-02 07:57:25.423 INFO: [46] org.jitsi.jicofo.BridgeSelector.log() Removing JVB: jvb@auth.sametime.test/tH_s0cmd
jicofo_1 | Jicofo 2020-09-02 07:57:25.424 INFO: [46] org.jitsi.jicofo.JvbDoctor.log() Stopping health-check task for: jvb@auth.sametime.test/tH_s0cmd

jvb_1 | JVB 2020-09-02 07:57:55.401 INFO: [15] org.jitsi.xmpp.mucclient.MucClientManager.log() Setting a presence extension: org.jitsi.xmpp.extensions.colibri.ColibriStatsExtension@12c792bd
jvb_1 | java.lang.Exception: java.lang.Exception: Address discovery through STUN failed

jicofo_1 | Jicofo 2020-08-31 04:09:43.017 WARNING: [76] org.jitsi.jicofo.JvbDoctor.log() Health check failed on: jvb@auth.sametime.test/sq9rH3ye error: <error type='cancel'><internal-server-error xmlns='urn:ietf:params:xml:ns:xmpp-stanzas'/><text xmlns='urn:ietf:params:xml:ns:xmpp-stanzas' xml:lang='en'>java.lang.Exception: Address discovery through STUN failed</text></error>
jicofo_1 | Jicofo 2020-08-31 04:09:43.022 INFO: [46] org.jitsi.jicofo.BridgeSelector.log() Removing JVB: jvb@auth.sametime.test/sq9rH3ye
jicofo_1 | Jicofo 2020-08-31 04:09:43.023 INFO: [46] org.jitsi.jicofo.JvbDoctor.log() Stopping health-check task for: jvb@auth.sametime.test/sq9rH3ye
jicofo_1 | Jicofo 2020-08-31 04:09:48.005 INFO: [38] org.jitsi.jicofo.BridgeSelector.log() Added videobridge: jvb@auth.sametime.test/sq9rH3ye v: null
jicofo_1 | Jicofo 2020-08-31 04:09:48.005 WARNING: [38] org.jitsi.jicofo.BridgeSelector.log() No pub-sub node mapped for jvb@auth.sametime.test/sq9rH3ye
jicofo_1 | Jicofo 2020-08-31 04:09:48.010 INFO: [46] org.jitsi.jicofo.JvbDoctor.log() Scheduled health-check task for: jvb@auth.sametime.test/sq9rH3ye

Thanks & Regards,
Prashanth

SettingsLogs.zip

This print -

java.lang.Exception: java.lang.Exception: Address discovery through STUN failed

Would suggest the server is unable to reach the Google Public STUN server(s) which are configured by default.

stun.l.google.com:19302,stun1.l.google.com:19302,stun2.l.google.com:19302

Please open a case and we can look further if that does not resolve your issue.

Hey Anthony,

Thanks for the reply. Yes i have created a case along with the logs and waiting for a reply. Will share HCL's reply as soon as i have an answer.

Thanks & Regards,

Prashanth

Hello Anthony,

Just wanted to update you that we were able to get the Sametime Meetings up and running. Yes connectivity to the Google STUN might be an issue but the main issue was the DOCKER_HOST_ADDRESS in custom.env. We had set the hostname instead of ip address. Based on the following reply for my case from HCL we performed and all set now.

set/validate the DOCKER_HOST_ADDRESS
in custom.env - ensure it is to the rout-able/expected IP of the MeetingServer
steps -
a) update custom.env
b) docker-compose down
c) delete the 'jitsi-config' directory
d) docker-compose up -d

But actually when we tried for the first time we did set the ip address itself. For several reasons we discarded that installation and started fresh. During second attempt we tried by setting the hostname for DOCKER_HOST_ADDRESS but later changed it based on HCL's suggestion.

Hope the suggestion from HCL might be useful for anyone facing the issue with Sametime Meetings.

Thanks & Regards,

Prashanth