Bugs item #1816647, was opened at 2007-10-19 09:02 Message generated for change (Comment added) made by sf-robot You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=756076&aid=1816647&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: Fixed Priority: 5 Private: No Submitted By: Mikhail Zabaluev (mzabaluev) Assigned to: Nobody/Anonymous (nobody) Summary: Outbound contact does not make it to dialogs Initial Comment: Somehow, the Contact with the external binding discovered by the outbound code is not used in subsequent dialogs. See the attached application log. ---------------------------------------------------------------------- >Comment By: SourceForge Robot (sf-robot) Date: 2007-11-30 19:20 Message: Logged In: YES user_id=1312539 Originator: NO This Tracker item was closed automatically by the system. It was previously set to a Pending status, and the original submitter did not respond within 14 days (the time period specified by the administrator of this Tracker). ---------------------------------------------------------------------- Comment By: Pekka Pessi (ppessi) Date: 2007-11-16 09:35 Message: Logged In: YES user_id=52043 Originator: NO I have updated the registration selection code in darcs. If it does not find a matching AoR from registrations, it uses the first registered Contact. ---------------------------------------------------------------------- Comment By: Pekka Pessi (ppessi) Date: 2007-11-16 02:40 Message: Logged In: YES user_id=52043 Originator: NO Looks like the code selecting the Contact use the AoR (From/To header) to do so. Perhaps a saner approach is to use the contact from the first real registration. ---------------------------------------------------------------------- Comment By: Mikhail Zabaluev (mzabaluev) Date: 2007-11-14 06:58 Message: Logged In: YES user_id=313104 Originator: YES While researching this, I've split nua_registration_by_aor() into two functions which cover the two use cases with different sets of parameters and are simpler to comprehend. I'm attaching the patch here. As to the problem at hand, my idea is, it occurs because the contact created by outbound doesn't make it into the registration list with nr_public flag set to nonzero. Hence, nua_registration_by_aor(), when supplied with a "wrong" AOR taken out of To:, picks up the first registration in the list which turns out to be the transport default. File Added: sofia-sip-registration-by-refactor.dpatch ---------------------------------------------------------------------- Comment By: Mikhail Zabaluev (mzabaluev) Date: 2007-11-07 05:10 Message: Logged In: YES user_id=313104 Originator: YES The problem only occurs when the To: handle in an incoming INVITE has a URI that does not match our AOR. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=756076&aid=1816647&group_id=143636 ------------------------------------------------------------------------- SF.Net email is sponsored by: The Future of Linux Business White Paper from Novell. From the desktop to the data center, Linux is going mainstream. Let it simplify your IT future. http://altfarm.mediaplex.com/ad/ck/8857-50307-18918-4 _______________________________________________ Sofia-sip-devel mailing list Sofia-sip-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/sofia-sip-devel
