29 Feb
2012
29 Feb
'12
7:35 p.m.
On 02/29/2012 06:23 PM, Klaus Darilion wrote:
That's really weird. It should not rewrite $ru.
Maybe there is some
special handling for ACK.
Yeah, I'm going to check the source.
Anyway, if the Route header is consumed and pushed
into $du it means
that the "special behavior" which was done for the INVITE
(loose-route==0) is not used here. IIRC these special behavior is only
triggered if the request does not contain a to-tag.
Right, and this is explicitely stated in the docs.
If tm is used, it will take care of this by consuming
the ACK and
generating a new one. It seems that we need some fixes for stateless
routing.
I already switched back to transaction stateful routing for now until I
get a better idea about what's going on on my test machine.
Andreas