I see that there was some discussion back in March 2006 (http://www.openser.org/pipermail/users/2006-March/003339.html) regarding this parameter, but nothing since. Daniel mentioned that perhaps it might be put on the to-do list, but I see no mention of it anywhere else. Was this implemented in 1.2? I see that maddr is available using pseudo-var transformations as {uri.maddr} in 1.2, but not mention of any automatic behavior if the parameter exists. I realize that I can work around it by using subst and subst_uri, but I really shouldn't have to. A simple t_relay should send it on its merry way to the value of maddr. My reading of both RFC3261 and 3263 seem to imply that the existence of this parameter in the request URI mandates forwarding the request to this address. I see in the code (for 1.1.1, I haven't looked at 1.2 yet) that the parameter is parsed, but then it appears (correct me if I'm wrong) as though nothing further is done with it. Is there some relatively simple way to modify the code to so that the maddr is used directly? As you can probably tell, I have a gateway with which I have to interoperate which uses this parameter extensively, hence my interest. :) Any advice (even if it's "use subst and subst_uri you whiner" ;) ) is appreciated. Thanks in advance, - Brad The contents of this e-mail are intended for the named addressee only. It contains information that may be confidential. Unless you are the named addressee or an authorized designee, you may not copy or use it, or disclose it to anyone else. If you received it in error please notify us immediately and then destroy it. _______________________________________________ Users mailing list Users(a)openser.org http://openser.org/cgi-bin/mailman/listinfo/users