Welcome to the #dominoforever Product Ideas Forum! The place where you can submit product ideas and enhancement request. We encourage you to participate by voting on, commenting on, and creating new ideas. All new ideas will be evaluated by HCL Product Management & Engineering teams, and the next steps will be communicated. While not all submitted ideas will be executed upon, community feedback will play a key role in influencing which ideas are and when they will be implemented.
For more information and upcoming events around #dominoforever, please visit our Destination Domino Page
Sametime Meetings 11.5+: Use only HTTPS instead of 10000/30000 UDP for Audio/Video/Screencast Streams
We love Sametime Meetings 11.5 and we would love to use it more often, but 2 out of 3 Customers (Guests) we invited to join our Meeting Session did not see or hear anything because of their Firewall blocking the outbound Port 10000/30000 UDP that ...
Please remove Websphere for Sametime. If not possible,
Remove Websphere Network deployment ---> WebSphere Liberty Profile on a docker container
Remove DB2 --> Free SQL solution on a docker container or move to mongodb
Load the chat client in the background, not blocking the user's work
It's great that the chat client loads the open conversions on startup, but not, it's blocking the user to work. Move this process to the background, allowing the user to continue, while the chat clients start and load the open conversations.
Reduce the needed hardware for Sametime on-premises
Currently the environment needs to run on multiple servers in a complex environment, which is heavy to install, maintain and operate - Best would be if IBM Sametime could be set up and run on one server.
Our thoughts go into the direction to user...
The Sametime Web Chat client looks like a decade old web chat client. It does a real disservice to IBM Verse to bundle it with Web Chat's antiquated interface. Rocket.Chat would be an example of a web interface that is more widely acceptable.
Support to run multiple recorder pods per worker node for Sametime Meeting on premise
In ST v11.5 and v11.6, Sametime Meeting on premise could support to run only one recorder pod per worker node, and one recorder pod could support only one meeting recording, it costs too much resources to support the recording function, need to ru...
Implement Lobby function into Sametime V11.5 Meetings
Jitsi offers the possibility of a "Lobby function": https://community.jitsi.org/t/how-to-how-do-i-use-the-new-lobby-feature/73100 This is a nice feature customers would like to see implemented in ST V11.5 Meetings.
Sametime is expected to have the ability to send PUSH notifications for Mobile Client users, even if users are simultaneously logged in anywhere (Web, rich, standalone clients).
Sametime is expected to have the ability to send PUSH notifications for Mobile Client users, even if users are simultaneously logged in anywhere (Web, rich, standalone clients). Currently, APNS PUSH notification about new chat messages is not bein...