[Devel] [ openser-Patches-1413083 ] Path support for save() and lookup()

[Klaus Darilion]

Great! :-)

thanks
klaus

SourceForge.net wrote:
> Patches item #1413083, was opened at 2006-01-23 19:06
> Message generated for change (Tracker Item Submitted) made by Item Submitter
> You can respond by visiting: 
> https://sourceforge.net/tracker/?func=detail&atid=743022&aid=1413083&group_id=139143
> 
> 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: Open
> Resolution: None
> Priority: 5
> Submitted By: Andreas Granig (agranig)
> Assigned to: Nobody/Anonymous (nobody)
> Summary: Path support for save() and lookup()
> 
> Initial Comment:
> Hello,
> 
> Attached you can find a Patch for Path support
> according to RFC 3327 for usage in registrars and
> home-proxies:
> 
> A call to save(...) stores, if path-support is enabled
> in the registrar-module, the values of the Path
> Header(s) along with the contact into usrloc. There are
> three modes regarding the reply to a REGISTER including
> one or more Path HFs:
> 
> - off: stores the value of the Path headers into usrloc
> without passing it back to the UAC in the reply.
> - lazy: stores the Path header and passes it back to
> the UAC if Path-support is indicated by the "path"
> param in the Supported HF.
> - strict: rejects the registration with "420 Bad
> Extension" if there's a Path header but no support for
> it is indicated by the UAC. Otherwise it's stored and
> passed back to the UAC.
> 
> A call to lookup(...) always uses the path header if
> found, and inserts it as Route HF either in front of
> the first Route HF, or after the last Via HF if no
> Route is present. It also sets the destination uri to
> the first Path uri, thus overwriting the received-uri,
> because NAT has to be handled at the outbound-proxy of
> the UAC (the first hop after client's NAT).
> 
> The whole process is transparent to the user, so no
> config changes are required beside setting the
> registrar-parameters "use_path" and "path_mode".
> 
> Another patch for handling Path at intermediate proxies
> is in progress. This will also solve the NAT-issue by
> handing over a received-param to a registrar in the
> Path uri and by rewriting the dst-uri for subsequent
> requests towards the UAC based on this param.
> 
> ----------------------------------------------------------------------
> 
> You can respond by visiting: 
> https://sourceforge.net/tracker/?func=detail&atid=743022&aid=1413083&group_id=139143
> 
> _______________________________________________
> Devel mailing list
> Devel at openser.org
> http://openser.org/cgi-bin/mailman/listinfo/devel
> 
>