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