#dominoforever | Product Ideas Portal


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 Sametime Meetings uses for Audio/Video/Screencast Streams.

From a Network Security Point of View, it is understandable to block all outbound Traffic by default and allow only neccessary outbound Ports to be open for Traffic.

This makes it very difficult to advocate for Sametime Meetings because we can not force our Customers to open Port 10000/3000 UDP just to be able to join our Sametime Meetings - they would rather propose to use MS Teams.

If you love Sametime Meetings, please upvote this Idea so we can have a better User Experience and a true "Browser-only" Meetings Client that runs Out-of-the-Box without having to modify any Environment besides the one it is installed on.

  • Guest
  • Nov 17 2020
  • Planning to implement
  • Attach files
  • Guest commented
    28 Apr 07:07pm

    It should not only have a fallback to HTTPS, it should also be viable over a HTTPS proxy. Consideration should also be given to proper and configurable handling of MITM aka SSL Inspection. This is very important with large accounts.

  • Guest commented
    9 Feb 07:00pm

    Hello, HCL has published an article that explains how to enable TCP on the Meeting Server video bridge. https://support.hcltechsw.com/csm?id=kb_article&sysparm_article=KB0087176

  • Guest commented
    9 Feb 01:50pm

    Update February 2021: According to HCL Support it is now possible to enable a fallback mechanism to support TCP instead of UDP. Please open a support ticket to receive the instructions as this is not yet part of the product documentation.

  • Guest commented
    31 Jan 02:34pm

    I second this. Having full support for TURN (the technical solution) would allow wider adoption and customer satisfaction. Having the UDP dependency is a stopper for customers

  • Admin
    Gaganpreet Saini commented
    17 Nov, 2020 09:20pm

    Hi Patrick, Henning - thanks for submititng thsi idea and your comments. We are looking into it. We currently do not officially support relays or over TCP connection. It hasn't been formally tested yet. We need to do our due diligence on performance testing before claiming this support. I have now added it to our list.

  • Guest commented
    17 Nov, 2020 04:15pm

    There seems to be a Solution for Jitse (Sametime Meetings Open Source Base): https://community.jitsi.org/t/udp-port-10000-blocked-behind-corporate-firewall-possible-approaches/28681

  • Guest commented
    17 Nov, 2020 12:58pm

    Afaik Teams also uses UDP Ports (3478-3481), they just seem to have a fallback solution (to 443 TCP) if those ports are blocked.