It requires of HAProxy fronting the web service with the stick tables feature configured. At least two stack replicas (shards) continuously active across different availability zones. We wanted not only a scalable solution, but also to benefit from a high availability setup. Jitsi Meet as the web client to gather all the functionality under a single webappĪside from the above, it offers the possibility of adding plug-ins and enabling additional external components to add capabilities like transcription, mail integration and file sharing.Īt the time this solution was built, Jitsi was advertised as scalable, however that’s not out of the box, there’s some additional setup that needs to happen for that to be the case:. Jitsi Videobridge (JVB) as the video relay backend. Jicofo, a service to manage the mapping between users and conferences. Prosody, a well known Extensible Messaging and Presence Protocol (XMPP) server. Jitsi Meet is a conferencing solution that combines multiple components, a bare-bones setup of the solution includes the following: Although deploying a solution on Azure is nowadays a piece of cake, there’s still some caveats to a truly scalable solution, follow along to see how we built it. It turns out the tool that ticked all those boxes was Jitsi Meet. At Airwalk we needed to build a self-hosted, scalable, customisable and secure solution to meet the strict needs of our highly-regulated environments while maintaining control over cost. Alongside the well-known paid players, some open source underdogs emerged as victors. If you don’t know why you need this API then don’t allow it.As many businesses during the pandemic decentralised their operations, conferencing tools exploded in popularity. This port is required to access the Jibri HTTP API. No specific port, it depends on your choice. This is not needed by JVB itself but most probably you need it to connect your server via SSH and to manage itĬheck external-api-port in your /etc/jitsi/jibri/nf file to learn the port number. Required for JMS to transport the websocket traffic to JVB Required for clients and coturn to send/receive the audio/video packets to JVB This is not needed by Jitsi itself but most probably you need it to connect your server via SSH and to manage itĬoturn should be able to access the local UDP/10000 (which is used by JVB) through the public IP address. If you don’t know why you need this API then don’t allow it. Required if you need to access the Jicofo REST API through the public IP. If you don’t know what colibri is then don’t allow it. Required if you need to access the Colibri REST API through the public IP. 
Required for coturn if you set this port for “ turn” on /etc/prosody/conf.d/ As an alternative you may use TCP/443 for “ turns” if you configured correctly your Nginx service.
Required for coturn if you set this port for “ turns” on /etc/prosody/conf.d/. If there is no additional JVB or Jibri, don’t allow it This is only needed if you have an additional JVB or an additional Jibri on a seperate machine. Required for clients to send/receive the audio/video packets to JVB Required for clients to access to Nginx and coturn Required for Let’s Encrypt to create/update TLS certificates The following ports should be accessible through the public IP address
0 kommentar(er)
