In exchange I'll make a contribution to the README to clarify this. If you choose to, 2 ports per active SIP call will be necessary. As for the 20000-20050 that's the range for jigasi, in case you choose to deploy that to facilitate SIP access, but that's not necessary. Required 10000 UDP > For General Network Audio/Video Meetings. Required 443 TCP > For general access to Jitsi Meet. Also, if UDP doesn't work the experience will be quite bad. The following ports need to be open in your firewall, to allow traffic to the Jitsi Meet server: 80 TCP > For SSL certificate verification / renewal with Let's Encrypt. plus there is 20000-20050 there, does that range need to be open? And does it mean only 50 clients can connect? □Ĥ443 is not there for simplicity. I've tried to figure this out staring at, but I don't see the 4443 there. ![]() Those are for RTP media over TCP and UDP.īut not those 5222/tcp, 5269/tcp, 5280/tcp, 5347/tcp on "prosody" - are those just internal among the containers, but not externally needed? ![]() I'm guessing that ports 8000 & 8443 (which I'm about to change to 80 and 443.)Ĭorrect. □ If this is already explained on some other doc in the Jitsi project, I'd love to read it, and link it from the README. plus there is 20000-20050 there, does that range need to be open? And does it mean only 50 clients can connect? would you know and be willing to confirm above or correct me? In exchange I'll make a contribution to the README to clarify this. ![]() I'm guessing that ports 8000 & 8443 (which I'm about to change to 80 and 443.) and also 440 must be open, but not those 5222/tcp, 5269/tcp, 5280/tcp, 5347/tcp on "prosody" - are those just internal among the containers, but not externally needed?
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |