if a request is forwarded to another destination in failure route by appending a new branch to it like in this example from the manual:
failure_route[1] { # forwarding failed -- try again at another destination append_branch("sip:nonsense@iptel.org"); log(1,"first redirection\n"); # if this alternative destination fails too, proceed to reply_route[2] t_on_failure("2"); t_relay(); }
then translated request-uri (format o) of accounting record does not contain this appended new uri, since the appended branch is not checked, when o-value is selected:
case 'o': if (rq->new_uri.len) val_arr[cnt]=&rq->new_uri; else val_arr[cnt]=&rq->first_line.u.request.uri; ATR(OURI); break;
is there an existing solution to this problem or should the above code be fixed?
-- juha
This should be fixed, thanks for the report, I have put it on my todo list.
Jan.
On 16-12 22:13, Juha Heinanen wrote:
if a request is forwarded to another destination in failure route by appending a new branch to it like in this example from the manual:
failure_route[1] { # forwarding failed -- try again at another destination append_branch("sip:nonsense@iptel.org"); log(1,"first redirection\n"); # if this alternative destination fails too, proceed to reply_route[2] t_on_failure("2"); t_relay(); }
then translated request-uri (format o) of accounting record does not contain this appended new uri, since the appended branch is not checked, when o-value is selected:
case 'o': if (rq->new_uri.len) val_arr[cnt]=&rq->new_uri; else val_arr[cnt]=&rq->first_line.u.request.uri; ATR(OURI); break;is there an existing solution to this problem or should the above code be fixed?
-- juha
Serusers mailing list serusers@lists.iptel.org http://lists.iptel.org/mailman/listinfo/serusers
-
Jan Janak -
Juha Heinanen