Medias Mediatrix 1204, Reference Manual

Page: 264 / 390

Chapter 19 - STUN Configuration STUN Client Configuration
238 Mediatrix 1204
STUN Client Configuration
The following describes how to configure the Mediatrix 1204 STUN client via SNMP. You can also use the web
interface to configure the STUN parameters. See
“STUN Configuration” on page 98 for more details.
X
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 1204 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 1204 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 1204 sends blank keepalive messages to
keep a firewall hole opened in the
stunKeepAliveInterval variable.
Keepalive messages are used by both the signalling protocol socket and the RTP socket to keep
those connections 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.
7. Set the frequency, in seconds, at which a unit should do NAT binding discovery for its signalling
protocol socket in the
stunNatBindingQueryInterval variable.
This is only used with units that do not register their ports. Units that register their ports do their NAT
binding discovery just before registering.
8. Enable the STUN client by setting the stunEnable variable to enable .
This enables the STUN client for all sockets (VoIP signalling, RTP and T.38) altogether.
The following behaviour also applies:
• If a unit is unable to re-register and there are no ongoing calls, it tries to rediscover its
NAT binding for the signalling protocol socket.
• If a STUN server is unresponsive, it is put in a “penalty box” for 60 seconds. See “SIP
Penalty Box” on page 226 for more details.
9. Restart the Mediatrix 1204 so that the changes may take effect.
Note:
Keepalive messages are not supported on the T.38 socket.