From demo testing: @anthonyrowe @hi-liang
Low priority.
When we use a device or network which has strict port filtering, jitsi fails to connect, but mqtt connects fine. So we see other users moving, and it takes the jitsi signaling system several seconds/minutes to fail retries propagating the error up to the user.
It would be great to know almost immediately that Jitsi would never work on this network/device. Super confusing to users from corporate laptops.
Can we add a quick port check in jitsi's random range, when !Jitsi.isReady on startup.
From demo testing: @anthonyrowe @hi-liang
Low priority.
When we use a device or network which has strict port filtering, jitsi fails to connect, but mqtt connects fine. So we see other users moving, and it takes the jitsi signaling system several seconds/minutes to fail retries propagating the error up to the user.
It would be great to know almost immediately that Jitsi would never work on this network/device. Super confusing to users from corporate laptops.
Can we add a quick port check in jitsi's random range, when
!Jitsi.isReadyon startup.