Specifications

Chapter 13 - STUN Configuration STUN Client Configuration
156
Mediatrix 4100
STUN Client Configuration
The following describes how to configure the Mediatrix 4100 STUN client via SNMP.
To configure the STUN client:
1. In the ipAddressConfig folder, locate the ipAddressConfigStunStatic group.
No DHCP value is available, you can only define STUN server information with static values.
2. Set the static STUN server IP address or Fully Qualified Domain Name (FQDN) in the
stunStaticHost variable.
The default value is 192.168.0.10.
3. Set the static STUN server IP port number in the stunStaticPort variable.
The default value is 3478.
4. In the stunMIB, set the amount of time, in seconds, the Mediatrix 4100 should keep a STUN query
result in its internal cache in the stunQueryCacheDuration variable.
Keeping a query in a cache helps to reduce the amount of unnecessary STUN queries when an RTP
or T.38 socket is re-used within a short period of time. Available values range from 0 s to 3600 s.
When set to 0, the cache is disabled and the unit performs a STUN query each time a socket needs
to be used.
5. Set the maximum amount of time, in milliseconds, the Mediatrix 4100 should wait for an answer to
a STUN query sent to a STUN server in the stunQueryTimeout variable.
Available values range from 500 ms to 10000 ms. The default value is 1000 ms.
Caution is advised in setting long timeouts. In the advent of an unresponsive STUN server, the unit
may end up waiting a long time before it determines that a call cannot be made due to the STUN
server failure.
6. Define the interval, in seconds, at which the Mediatrix 4100 sends blank keepalive messages to
keep a firewall hole opened in the stunKeepAliveInterval variable.
Keepalive messages are used by the RTP socket to keep the connection opened through a firewall.
Available values range from 0 s to 120 s. The default value is 30 s.
When set to 0, no keepalive packet is sent.
See
Firewall Traversal” on page 78 for information on the keepalive parameter for the signalling
MGCP.
7. Enable the STUN client by setting the stunEnable variable to enable.
This enables the STUN client for all sockets (RTP and T.38) altogether.
8. Restart the Mediatrix 4100 so that the changes may take effect.
Note: Keepalive messages are not supported on the T.38 socket.