[OpenSER-Devel] [ openser-Feature Requests-1666126 ] tm module should support automatic usage of maddr parameter

SourceForge.net noreply at sourceforge.net
Fri Jul 4 18:53:48 CEST 2008


Feature Requests item #1666126, was opened at 2007-02-22 13:39
Message generated for change (Comment added) made by henningw
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=743023&aid=1666126&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: modules
>Group: None
Status: Open
Resolution: None
Priority: 2
Private: No
Submitted By: Brad Watkins (marquis42)
Assigned to: Nobody/Anonymous (nobody)
Summary: tm module should support automatic usage of maddr parameter

Initial Comment:
According to RFC 3261 (section 16.5):

If the Request-URI of the request contains an maddr parameter, theRequest-URI MUST be placed into the target set as the only target URI, and the proxy MUST proceed to Section 16.6.

And 3263 (Section 4):

We define TARGET as the value of the maddr parameter of the URI, if present, otherwise, the host value of the hostport component of the URI.


It therefore stands to reason that for RFC-compliance reasons (and to help users :) ), the tm module should be modified to use the maddr parameter if present as the destination of a request.

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

>Comment By: Henning Westerholt (henningw)
Date: 2008-07-04 16:53

Message:
Logged In: YES 
user_id=337916
Originator: NO

As this can be achieved with transformations in the script, as Daniel
pointed out, i move this to the feature request section.

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

Comment By: Daniel-Constantin Mierla (miconda)
Date: 2007-03-07 10:11

Message:
Logged In: YES 
user_id=1246013
Originator: NO



More information about the Devel mailing list