Web User Interface

Identities → NAT → STUN Server

Phone User Interface

n/a

Initial Firmware Version

V6

XML Configuration

<stun_server idx="INDEX" perm="PERMISSIONFLAG">VALIDVALUE</stun_server>

Description

We reintroduced a STUN keep-alive mechanism for SIP, which can be turned on manually by specifying the address of the STUN server followed by the port number. However, we strongly discourage you from using it, because it can not work properly in symmetrical NAT environments (i.e., linux-based router/firewall). The only general SIP NAT solution is a session border controller (SBC) on the service provider’s side.

The address received from the STUN server is used in Contacts headers for transport UDP.

If tcp_listen is on, this is also done for transports TCP and TLS, otherwise the address used for these transports is the internal local address (No longer applies starting with version 10.1.64.15).

For an alternative to STUN see unsaf_via_received_rport.

Valid Values

e.g. <217.115.141.99:5062>

Default Value

blank