[Devel] Re: [Users] strict to loose - Route Header not removed
bogdan at voice-system.ro
Thu May 11 19:15:29 CEST 2006
maybe I do not fully understand your scenario, but do not see how the IP
of the last proxy may appear both in RURI and a Route hdr - it means
either the ACK is bogus, either the ACK indeed passed twice via that proxy.
if you can get an ngrep trace of the INVITE + 200OK + ACK, I will be
able to better understand the situation.
Walter Schober wrote:
>Consider, one has targeted the last proxy by IP
>address, e.g. the proxy is responsible for 111.222.333.129.
>Then e.g. some ACK might be sent to ACK sip:user at 111.222.333.129 + Route
>Header pointing to itself.
>This is not handled by after_strict().
More information about the Devel