STUN Module

Use the WebAdmin Interface to configure the STUN module. Open the Services pages in the Settings realm, and open the STUN page:

Log

Use this setting to specify which records the STUN module should put in the Server Log.

The STUN module Log records are marked with the STUN tag.

Listener

Use this link to open the UDP Listener and TCP Listener pages and specify the port numbers and local network addresses for the STUN service, and access restrictions for these port.
By default STUN clients send "Bind" requests to the UDP port 3478, and they send "Shared Secret" requests to the secured TCP (TLS) port 5349.

Channels

Use this setting to specify the maximum concurrent number of STUN TCP requests.

Note: the STUN protocol requires 4 UDP sockets to be configured, using 2 different ports and 2 different IP Addresses, in all combinations. Thus, the STUN server should have at least 2 different Local IP Addresses available to its clients.

The SIP module supports STUN packet multiplexing with the SIP protocol. When a STUN packet is received on any of the SIP UDP Listener sockets, the packet is passed to the STUN module for processing.

Note: the STUN module must know the exact Network IP Address the request was received on. To support STUN protocol, the SIP Module UDP Listener sockets must be configured using explicitly specified IP Addresses, and not use the "all addresses" settings.

Note: the SIP module UDP Listener sockets can be used as "alternative" STUN address and port. I.e. you can create only 2 UDP Listener sockets for the network address IP1, port 3478, and for the network address IP2, port 3478 - if there are at least 2 SIP UDP Listener sockets, for:

• network address IP1, port 5060 (or any port other than 3478)
• network address IP2, port 5060 (or any port other than 3478)