[SR-Users] nathelpler module path support

Ovidiu Sas osas at voipembedded.com
Fri May 13 18:08:52 CEST 2011


On Fri, May 13, 2011 at 12:03 PM, Asgaroth <00asgaroth00 at gmail.com> wrote:
> Hi Ovidiu,
>
> I have just tried this nat_traversal module, and it looks like I
> cannot run it from the registrars, as it appears that the
> "nat_keepalive()" parameter will only send the keepalive to the source
> address the message was sent from, which, if I run it from my
> registrar, will be the address of the proxy server.

It is stated in the doc that you need to run the nat_traversal on the proxy.


> I also tried running this from the proxy server. It seems to work from
> there, however, the issue have have now, is that even if I unregister
> a device, the nat_keepalive() application is still sending notify
> messages. I dont see an exported function anywhere for that module to
> stop it from sending keepalives when a device unregisters. Is that the
> expected behaviour?

I'm not sure about this ... IIRC, in the past, that was the expected behavior.
Not sure if this was fixed.


> On 13/05/2011, Ovidiu Sas <osas at voipembedded.com> wrote:
>> Try the nat_traversal module:
>> http://www.kamailio.org/docs/modules/3.1.x/modules_k/nat_traversal.html
>> It should handle this kind of scenarios.
>>
>>
>> Regards,
>> Ovidiu Sas
>>
>> On Fri, May 13, 2011 at 6:49 AM, Asgaroth <00asgaroth00 at gmail.com> wrote:
>>> Hi All,
>>>
>>> I have a scenario where our registrar's are sitting behind our sip
>>> proxy. The sip proxy is the only system that has access to the outside
>>> world. Our registrar's are all on internal private addresses.
>>>
>>> I am trying to configure our registrar's to perform nat pinging.
>>> However, because the registrar's are on an internal address there is
>>> no way for the nat ping to get out. I enabled the path option so that
>>> the registrar stores the path that the registration comes in on.
>>> However it doesnt seem like the nathelper module uses the path
>>> parameter to send the outgoing nat ping. I tried the nat ping using
>>> sip method INFO, but the same applies, it does not appear to be able
>>> to send out via the outbound proxy.
>>>
>>> I tried to enable the natping option on the sip proxy, but it appears
>>> that only registrations with a socket address of the local host will
>>> get pinged, or else it is ignored.
>>>
>>> Is there an option that I am missing for the nat helper module that
>>> will enable me to set an outbound proxy for the nat ping messages?
>>>
>>> Any insight would be appreciated.
>>>
>>> Thanks
>>>
>>> _______________________________________________
>>> SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list
>>> sr-users at lists.sip-router.org
>>> http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
>>>
>>
>> _______________________________________________
>> SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list
>> sr-users at lists.sip-router.org
>> http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
>>
>
> _______________________________________________
> SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list
> sr-users at lists.sip-router.org
> http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
>



More information about the sr-users mailing list