[SIP Beyond VoIP] STUN keep-alive

[Adrian Georgescu]

Your are taking the wrong approach to solve NAT traversal. 

You must use nat_traversal module that takes care of the keep alives for all transactions not just Register. Lowering the Register is creating more load on the server as it involves authentication, several round trip times and database queries and does not solve the keep alive of your live dialogs.

Adrian


On Jan 16, 2012, at 12:03 PM, Mihai Richard wrote:

> This might work. Now I'm just asking if there are some other messages that I
> can send to the server to keep the NAT binding and still not require much
> processing from the server. If not, I'm going ahead and lowering the
> registration interval.
> 
> Thanks,
> 
> --
> Mihai Richard
> 
> On 1/16/12 12:49 PM, "Luci Stanescu" <luci at cnix.ro> wrote:
> 
>> Hi Mihai,
>> 
>> On 16 Jan 2012, at 10:44, Mihai Richard wrote:
>>> Both clients are indeed behind the same NAT router, but problems appear only
>>> after one of them has a long period of inactivity(no messages sent to the
>>> server). If one client has a long period of inactivity, it cannot be
>>> contacted by other client but in turn it can contact clients that recently
>>> had activity.
>> 
>> 
>> If the server doesn't do anything to keep the NAT binding alive, you can lower
>> the registration interval to something like 60 seconds. Of course, only if the
>> server doesn't complain that the interval is too brief.
>> 
>> Kind Regards,
>> 
>> --
>> Luci Stanescu
>> 
> 
> 
> _______________________________________________
> SIPBeyondVoIP mailing list
> SIPBeyondVoIP at lists.ag-projects.com
> http://lists.ag-projects.com/mailman/listinfo/sipbeyondvoip
>