[OpenSIPS-Devel] [ opensips-Bugs-2634285 ] Nat_traversal: opensipsctl ul rm doesn't clean up keepalives

[SourceForge.net]

Bugs item #2634285, was opened at 2009-02-24 19:11
Message generated for change (Settings changed) made by bogdan_iancu
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=1086410&aid=2634285&group_id=232389

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: modules
Group: trunk
>Status: Closed
Resolution: Invalid
Priority: 5
Private: No
Submitted By: Thomas Gelf (thomas_gelf)
Assigned to: Dan (dan_pascu)
Summary: Nat_traversal: opensipsctl ul rm doesn't clean up keepalives

Initial Comment:
Running

> opensipsctl ul rm user at domain.tld

doesn't seem to affect nat_traversal's keep-alive state.

Steps I followed to reproduce this issue:
* removed all registrations
* stopped OpenSIPS
* removed keep-alive state file
* started OpenSIPS
* booted some test device
* let devices (all of them behind NAT) REGISTER themselves
* stopped OpenSIPS, manually compared usrloc entries and keep-alive state file
* everything seemed to be fine
* restarted OpenSIPS, "ul rm" for one user, stopped OpenSIPS
* old entry is still to be found in keep-alive state file

OpenSIPS version: SVN trunk, updated this morning. If you need more tests please let me know!

Best regards,
Thomas Gelf


----------------------------------------------------------------------

Comment By: Thomas Gelf (thomas_gelf)
Date: 2009-02-26 14:10

Message:
Silly me, should have known that - sorry! Got confused as there have been
LOTS of keepalives because of a braindead ALG in my test environment ;-)

----------------------------------------------------------------------

Comment By: Dan (dan_pascu)
Date: 2009-02-25 13:20

Message:
The nat_traversal module doesn't use the ul module contacts, instead it
keeps track itself of the nat entry points (ip:port). These do not have a
1:1 relationship, as a nat entry point can be used by multiple contacts. So
when a contact is removed you can say nothing about the nat entry point not
being used anymore. The nat_traversal module will remove a nat entry point
from the keepalive list only when all the reasons to keep that address
alive expire. For a registration, that means when it expires. Read the
nat_traversal documentation for a detailed explanation of its operation.


----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=1086410&aid=2634285&group_id=232389