14 Mar
2008
14 Mar
'08
2:28 p.m.
Correcting two mails in this thread....
Miklos Tirpak píše v Pá 14. 03. 2008 v 12:03 +0100:
...
assign_hf_value("Contact",
"<%(a)contact.uri;param=value>")value>");
But you loose the header parameters this way :(
I don't think so... @(select_any_header.nameaddr).uri was intended to
return the whole uri INCLUDING all parameters. Anyway the construction
above will work, you just might end with two occurences of param
parameter.
----
Jiri Kuthan píše v Pá 14. 03. 2008 v 08:35 -0400:
# here you can formulate complex URIs
xlset_attr("$rpidheader",
"<sip:%$asserted_id@%@ruri.host>;screen=yes");
correct, shows how you can combine the request's parts using xlog formatting.
# here you initiate redirection based on a URI in an
AVP (statefuly here)
attr_destination("$tu.fwd_busy_target");
t_reply("302", "Redirect On Busy");
These two are completely unrelated.... attr_destination sets the target
for the request being forwarded regardless what request_uri/loose_route
has set (e.g. should be followed by append_branch, t_relay) whilst
t_reply just sends reply. So if you use just these two lines you won't
get Contact holding $tu.fwd_busy_target in the 302 reply.
Michal