About -> News -> Stun Server

Built-in STUN server for OpenSIPS

Thanks to Razvan Pistolea, there is a new STUN server(rfc 3489) module integrated in OpenSIPS.

Why an integrated STUN server module?

• A STUN server uses 2 ips and 2 ports to create 4 sockets on which to listen or respond.
• This integrated STUN module uses the SIPS sockets created by the OpenSIPS core:
  • one (or two) of the sockets will overlap with the SIP signaling socket
  • the rest will be created by this module for STUN only purposes.
• In the case of a bad behaving NATs (such as symmetric NAT) only this integrated STUN server will increase the likelihood of STUN to solve the NAT traversal for a wider range of NAT implementations. This translates into less need of media relaying (for NAT traversal purposes).

Notes:

• It is important to set the primary_ip:primary_port to match the OpenSIPS signaling ip and ports.
• If OpenSIPS binds one more interface this module will use that too; so make sure you set the correct alternate_ip:primary_port.
• STUN requires 2 routable ip addresses; if in shortage create a virtual interface (i don't recommend because it destroys the purpose for some usages).

Example:

    Opensips listening for signaling traffic:
        89.89.89.12:5060
    for stun module we configure :
        primary_ip = 89.89.89.12; primary_port = 5060 - overlapping with signaling socket
        primary_ip = 89.89.89.12; alternate_port = 3478 - dedicated stun socket
        alternate_ip = 34.34.34.12; primary_port = 5060 - dedicated stun socket
        alternate_ip = 34.34.34.12; alternate_port = 3478 - dedicated stun socket

Documentation can be found here: http://www.opensips.org/html/docs/modules/devel/stun.html