[SIP Beyond VoIP] STUN keep-alive

Luci Stanescu luci at cnix.ro
Mon Jan 16 12:41:06 CET 2012


On 16 Jan 2012, at 11:03, 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.


You can try it out to see if this makes it work, but keep in mind there are some important preconditions:
  * the client must a single port for all SIP messages (both sending and receiving).
  * there must be a single entry point IP address, protocol and port to the provider network (i.e. if the provider has multiple proxies, this will work for receiving incoming calls but other transactions might use another proxy => those binding will likely expire)

As for the load put on the server, it's true, it's a horrible waste just for NAT traversal. You can technically send anything, which should make all NAT boxes keep the binding alive. But if you use OpenSIPS, give the nat_traversal module a try. It's the best point capable of detecting whether there's a NAT box in between the user and the proxy. Can't really think of a simple way a client could reliably do it.

Kind Regards,

--
Luci Stanescu

-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 5417 bytes
Desc: not available
URL: <http://lists.ag-projects.com/pipermail/sipbeyondvoip/attachments/20120116/888ecba8/attachment.bin>


More information about the SIPBeyondVoIP mailing list