VPN Blocking Jitsi

I have a corporate client that uses a VPN for it’s employees and the employees are unable participate in Jitsi meetings even though TURN is working and the server has been tested to be working with port 10000 blocked. Has anyone experienced something similar? Any ideas on a solution?

hi, Have you found any solution ?

Regards

Here is a possible solution.

hi,

I am using a turn server with a separate, IP with 443 & 80, still people in corporate VPN cant access to JVB.

please refer log below.

Thank you.

14043: IPv4. tcp or tls connected to: :22397
14043: IPv4. tcp or tls connected to: :22396
14044: IPv4. tcp or tls connected to: :22393
14044: IPv4. tcp or tls connected to: :22392
14051: IPv4. tcp or tls connected to: :22382
14051: IPv4. tcp or tls connected to: :22381
14088: session 001000000000000166: TLS/TCP socket disconnected: :22392
14088: session 001000000000000166: closed (2nd stage), user <1618388019> realm <myturn.com.sg> origin <>, local 192.168.10.209:443, remote :22392, reason: TLS/TCP socket buffer operation error (callback)
14088: session 004000000000000218: TLS/TCP socket disconnected: :22393
14088: session 004000000000000218: closed (2nd stage), user <1618388019> realm <myturn.com.sg> origin <>, local 192.168.10.209:443, remote :22393, reason: TLS/TCP socket buffer operation error (callback)
14095: session 001000000000000167: TLS/TCP socket disconnected: :22382
14095: session 001000000000000167: closed (2nd stage), user <1618388027> realm <myturn.com.sg> origin <>, local 192.168.10.209:443, remote :22382, reason: TLS/TCP socket buffer operation error (callback)
14095: session 000000000000000197: TLS/TCP socket disconnected: :22381
14095: session 000000000000000197: closed (2nd stage), user <1618388027> realm <myturn.com.sg> origin <>, local 192.168.10.209:443, remote :22381, reason: TLS/TCP socket buffer operation error (callback)
14103: session 001000000000000165: closed (2nd stage), user <> realm <myturn.com.sg> origin <>, local 192.168.10.209:443, remote :22397, reason: allocation watchdog determined stale session state
14103: session 001000000000000165: SSL shutdown received, socket to be closed (local 192.168.10.209:443, remote :22397)
14103: session 003000000000000109: closed (2nd stage), user <> realm <myturn.com.sg> origin <>, local 192.168.10.209:443, remote :22396, reason: allocation watchdog determined stale session state
14103: session 003000000000000109: SSL shutdown received, socket to be closed (local 192.168.10.209:443, remote :22396)

Regards.