Questions regarding using the Jitsi installation’s own local stun server, for STUN_MAPPING_HARVESTER_ADDRESSES
In the file
There is a setting:
Why is the address “meet-jit-si-turnrelay.jitsi.net” used?
Can I change to my own Jitsi instance since the current Jitsi installation installs a local stun server?
What are the pros and cons of doing so?
As Australia is a long distance from where “meet-jit-si-turnrelay.jitsi.net” is hosted, it seems possible to reduce latency and international network traffic by using a local stun server. If anyone who understands Jitsi well, can you please comment on my ideas of preferring to use the local stun server verses a sun server which is based on the other side of the world, transversing the pacific ocean via a submarine communications cable which is already saturated by network traffic.
The name “STUN_MAPPING_HARVESTER_ADDRESSES” indicates to me that the Jitsi installation will determine which stun server to used based on this setting, but is it possible to reduce CPU resources by directly defining the stun server so that the process of determining which server can be bypassed. Though I guess that this is not something that would take up a lot of CPU resources, is determined at the start of a call, and is then never called again during the meeting’s life.
Would this be away to bypass the determination of which stun server to use (when the public IP address is the same as the Jitsi server’s internal IP address)?
org.ice4j.ice.harvest.DISABLE_AWS_HARVESTER=true #org.ice4j.ice.harvest.STUN_MAPPING_HARVESTER_ADDRESSES=meet-jit-si-turnrelay.jitsi.net:443 org.ice4j.ice.harvest.NAT_HARVESTER_LOCAL_ADDRESS=<publicIPaddress> org.ice4j.ice.harvest.NAT_HARVESTER_PUBLIC_ADDRESS=<publicIPaddress>
Despite my ideas and questions above, if my understanding of the STUN server’s purpose it is only used in the initial setup of a participant to a meeting, to help the participant’s side determine its internet facing IP address? And if this is true, there will be very little internet traffic, which only occurs once per participant (joining a meeting), hence any savings are only small.
The STUN server allows clients to find out their public address, the type of NAT they are behind and the Internet side port associated by the NAT with a particular local port. This information is used to set up UDP communication between the client and the VoIP provider to establish a call.
How does it work? The client, usually inside a private network, sends a binding request to a STUN server on the public Internet. The STUN server responds with a success response that contains the IP address and port number of the client, as observed from the server’s perspective.