12 Aug
2008
12 Aug
'08
9:54 a.m.
Hi Alex,
Let me double check this. In our setup, this works properly (or at least
no problem known); and the from headers in the reply is right as well.
One difference may be, that we use uac_replace_from purely in
branch_route() and not in the request route itself.
I can double check your problem tomorrow (i'm not at the office today)
and, if i find something, update the patch.
Carsten
Alex Hermann wrote:
On Tuesday 12 August 2008, Iñaki Baz Castillo wrote:
El Tuesday 12 August 2008 14:17:39 Alex Hermann
escribió:
No. I really need to modify the From.
I tried Carstens patch to use uac_replace_from in branch route. This hack does
the 'right thing' for requests, but still puts multiple From headers in
replies.
REQUEST_ROUTE:
uac_replace_from(a)
t_relay();
FAILURE_ROUTE:
append_branch()
uac_replace_from(b)
t_relay()
the second uac_replace_from always produces garbage in the From
Yes, it occurred the same to me. uac_replace_from has a very buggy
behaviour.
Is not valid for you using P-Asserted-Identity or RPID?