Quoting Andrew Pam (andrew@sericyb.com.au):
Hmm. It mostly fails with Firefox and mostly succeeds with Chrome, so maybe that was the problem. Even with Chrome the "Reflexive connectivity" and "Video bandwidth" tests fail. Are there any ports I have to open on my firewall for Jitsi?
Checking my rushed notes for server setup of jitsi.conzealand.nz : 80/tcp for Web UI HTTP to redirect 443/tcp for Web UI HTTPS 4443/tcp for RTP media over TCP (transport for WebRTC A/V) 10000/udp for RTP media over UDP optional: 20000-20050/udp for jigasi (SIP access) (That's for a fairly generic setup, which ended up not including SIP.) ISTR that the two you say fail don't necesarily matter much. -- Cheers, "My hot flight attendant asked how I like my coffee. Rick Moen And that's when she told me: 'That's cute, honey, but rick@linuxmafia.com the coffee's free. You don't have to pay for it, here." McQ! (4x80) (seen on Twitter)
On 15/8/20 6:51 pm, Rick Moen wrote:
Quoting Andrew Pam (andrew@sericyb.com.au):
Hmm. It mostly fails with Firefox and mostly succeeds with Chrome, so maybe that was the problem. Even with Chrome the "Reflexive connectivity" and "Video bandwidth" tests fail. Are there any ports I have to open on my firewall for Jitsi? Checking my rushed notes for server setup of jitsi.conzealand.nz :
80/tcp for Web UI HTTP to redirect 443/tcp for Web UI HTTPS 4443/tcp for RTP media over TCP (transport for WebRTC A/V) 10000/udp for RTP media over UDP optional: 20000-20050/udp for jigasi (SIP access)
(That's for a fairly generic setup, which ended up not including SIP.)
ISTR that the two you say fail don't necesarily matter much.
There are desktop and phone apps. I've found these to be much better than the web interface, particularly much lower cpu load. Mike
participants (2)
-
Mike O'Connor -
Rick Moen