|
Version 6.3 |
|
| ||||||||||||||||||||||
Configuring the STUN ModuleUse the WebAdmin Interface to configure the STUN module. Open the Services pages in the Settings realm, and open the STUN page:
Note: the "old" STUN protocol (RFC 3489) requires 4 UDP sockets to be configured, using 2 different ports and 2 different IP Addresses, in all combinations. To support the RFC 3489 protocol, the STUN server should have at least 2 different Local IP Addresses available to its clients. Protocol MultiplexingThe 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:
To support ICE clients, the STUN module supports STUN packet multiplexing with the RTP protocol: the Media Proxy and Media Server legs detect STUN packets and send them the the STUN module for processing. |