Bugs item #1930055, was opened at 2008-03-31 13:47 Message generated for change (Comment added) made by mzabaluev You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=756076&aid=1930055&group_id=143636
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: None Group: None >Status: Closed Resolution: Works For Me Priority: 1 Private: No Submitted By: Mikhail Zabaluev (mzabaluev) Assigned to: Nobody/Anonymous (nobody) Summary: Unregister when a new public binding is detected Initial Comment: When outbound detects a new address binding, any successful registration by the same NUA handle should be explicitly unregistered. This may be needed in two cases: 1) weird configurations with NAT and no authentication; 2) when the binding changes on a NAT middle box. See also the discussion on a maemo bug: https://bugs.maemo.org/show_bug.cgi?id=3056 ---------------------------------------------------------------------- >Comment By: Mikhail Zabaluev (mzabaluev) Date: 2008-04-04 17:01 Message: Logged In: YES user_id=313104 Originator: YES It's been working as described, the bug is invalid. ---------------------------------------------------------------------- Comment By: Mikhail Zabaluev (mzabaluev) Date: 2008-04-04 15:43 Message: Logged In: YES user_id=313104 Originator: YES > The previous contact is added to the new REGISTER request with expires=0 parameter. Was it implemented in Sofia-SIP for a long time? ---------------------------------------------------------------------- Comment By: Pekka Pessi (ppessi) Date: 2008-04-04 15:37 Message: Logged In: YES user_id=52043 Originator: NO The previous contact is added to the new REGISTER request with expires=0 parameter. In other words, the REGISTER request is used to both unregister the old contact and register the newly discovered contact. While this is very basic REGISTER functionality from pre-RFC-2543 era, it may confuse some proxies. Please confirm if that is so. ---------------------------------------------------------------------- Comment By: Mikhail Zabaluev (mzabaluev) Date: 2008-04-02 11:59 Message: Logged In: YES user_id=313104 Originator: YES Maybe it's not a good idea to unregister _before_ the contact is updated. But it could be done afterwards (after the whole update transaction, or perhaps just firing an un-REGISTER request right after the REGISTER with a contact update is sent?). OTOH, it can bring more issues with saner proxies, than it solves with a few not-so-sane examples. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=756076&aid=1930055&group_id=143636 ------------------------------------------------------------------------- Check out the new SourceForge.net Marketplace. It's the best place to buy or sell services for just about anything Open Source. http://ad.doubleclick.net/clk;164216239;13503038;w?http://sf.net/marketplace _______________________________________________ Sofia-sip-devel mailing list Sofia-sip-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/sofia-sip-devel