§2024-09-04

Jitsi Meet uses several ports for its various components to function properly. Here’s a breakdown of the main ones:

HTTP/HTTPS Ports:

Port 80 (HTTP): Used for web traffic, but usually redirected to HTTPS. Port 443 (HTTPS): Used for secure web traffic. This is the main port for accessing the Jitsi Meet web interface. Media Ports:

Port 10000 (UDP): Used by Jitsi Videobridge for WebRTC media streaming. This port is crucial for video and audio communication. XMPP Ports:

Port 5222 (TCP): Used by the XMPP server for client-to-server communication. Port 5269 (TCP): Used for server-to-server communication in XMPP. TURN Server Ports (if using TURN server for NAT traversal):

Port 3478 (UDP/TCP): Default port for TURN server, used for relaying media through NATs. Jicofo (Jitsi Conference Focus) Ports:

Port 5347 (TCP): Used for communication between Jicofo and the XMPP server.

Jitsi Meet and XMPP:

TCP 443: HTTPS (secure web traffic, often used for Jitsi Meet) TCP 80: HTTP (web traffic, typically for initial connections and redirecting to HTTPS) TCP 5222: XMPP client connections (XMPP is the protocol Jitsi uses for signaling) TCP 5269: XMPP server-to-server communication TCP 5280: BOSH (Bidirectional-streams Over Synchronous HTTP, used for XMPP) TCP 5281: XMPP for other services (e.g., SIP) TCP 8080: (Common for web applications, might be used for Jitsi components or other applications) TCP 8888: (Additional port used by Jitsi or other services) TCP 9090: (Another additional port used by Jitsi or other services) TURN Server:

TCP 5349: TURN over TLS (secure TURN connections) TCP 5350: TURN over UDP (TURN with additional UDP support) UDP Ports TURN Server: UDP 5349: TURN over TLS (though primarily TURN uses TCP for secure connections, it can use UDP in certain configurations) UDP 5350: TURN for non-secure UDP (common for real-time media traffic)