I’m deploying a k8s(docker based) jitsi environment, when configuring jvb, since I could not export 4443/10000 port of jvb outside, I used sip-communicator.properties to enable NAT like below:
When I check through chrome://webrtc-internals/, I found the nat does not work as my design, it reads like:
a=candidate:2 1 udp 1694498815 126.96.36.199 10000 typ srflx raddr 10.244.1.33 rport 10000 generation 0
what’s more strange is that 188.8.131.52 appeared in all my docker based environment as the outside endpoint in request, and this ip should belongs to an aws machine.
So I want to make clear that:
- does 184.108.40.206 work as jvb outside point for all docker-based jvb service?
- how could I make my own NAT setting work?