nathelper

nathelper

greger on 26 November, 2006 - 09:40
Keywords: 2.0.x | Module | nathelper

Standard

This is a module to help with NATi traversal. In particular, it helps symmetric UAs that don't advertise they are symmetric and are not able to determine their public address. fix_nated_contact rewrites Contact header field with request's source address:port pair. fix_nated_sdp adds the active direction indication to SDPi (flag 0x01) and updates source IP address too (flag 0x02).


Maxim Sobolev

Running rtpproxy on a different machine than SER

lakmal on 8 November, 2006 - 19:06
Keywords: nathelper

Optimizing the use of RTP proxy

ladaan on 18 September, 2006 - 07:51
Keywords: 2.0.x | Book | nathelper
NATi traversal with RTPi proxy deals with all kinds of NAT but should be used when is really needed. This document describes how to optimize the use of RTP proxy. The full configuration file is available in attachments.

NAThelper SIP message/OPTIONS ping functionality

greger on 13 August, 2006 - 08:02
Keywords: 0.9.x | nathelper

0.9.7-pre4 (probably all 0.9.x)

NAThelper patch from Portaone that enables the ping functionality in nathelper to send SIP message (i.e. OPTIONS) instead of 4-byte UDP packets. This is useful for NATs that ignore ping keepalives from the outside as the user agent will answer the OPTIONS packet with OK (or 404 Not found etc dependent on support for OPTIONS).


Save the patchfile to modules/nathelper directory, then (having that directory as current) use the command 'patch -p1 < nathelper_ping.patch'

OBS! You also need to edit the parser/parse_hostport.c file and remove the #ifdef _OBSOLETED and #endif around the parse_hostport() function.

Add this to your seri.cfg to enable OPTIONS messages to the UAs as keepalives:
modparam("nathelper", "natping_method", "OPTIONS")

You will see a lot 'No UACi support' warning messages in your log. These are harmless and are caused by replies to the OPTIONS message and SERi detects (correctly) these messages as originated from SER (as UAC). You can remove the warnings by commenting out in modules/tm/t_reply.c in run_failure_handler():

        /* failure_route for a local UAC? */
        if (!shmem_msg) {
          /* GVT: Commented out as nathelper sends UAC messages to UAs for keepalives. The replies
             should just be ignored... */
          /* LOG(L_WARN,"Warning: run_failure_handlers: no UAC support (%d, %d) \n",
                                        t->on_negative, t->tmcb_hl.reg_types); */
          return 0;
        }

This is the page where YOU add your most wanted SERi features or modules! Please feel free to edit this page.

See a more detailed list of wishlist items on the tracker (items on this wishlist will end up in the tracker when they are detailed enough to do actual coding).

New groups can also be added. This wishlist is used for evaluating what to focus on for future releases.

In order to know the general interest of a feature, you can also vote for features. Just add an * in parenthesis behind the feature, and please only add one...

ping_nated_only

janakj on 9 March, 2006 - 23:41
Keywords: nathelper

If this variable is set then only contacts that have "behind_NATi" flag in user location database set set will get ping.

Default value is 0.

...
modparam("nathelper", "ping_nated_only", 1)
...

natping_interval

janakj on 9 March, 2006 - 23:33
Keywords: nathelper | parameter

Period of time in seconds between sending short UDP packets to all currently registered UAs to keep their NATi bindings alive. Value of 0 disables this functionality.

Default value is 0.

...
modparam("nathelper", "natping_interval", 10)
...

XML feed
Home |  Recent changes |  Search |  Glossary |  Sitemap |  Login