Hi Klaus,
I had a similar issue with the following scenario:
Client -> Openser -> Other Softswitch
The problem was that not only that the Softswitch was removing the
Record-Route header, but also rewriting it with it's own.
Bellow is a quote from RFC 3261:
"""
12.1.1 UAS behavior
When a UAS responds to a request with a response that establishes a
dialog (such as a 2xx to INVITE), the UAS MUST copy all Record-Route
header field values from the request into the response (including the
URIs, URI parameters, and any Record-Route header field parameters,
whether they are known or unknown to the UAS) and MUST maintain the
order of those values.
"""
So, it is obvious that this was a broken implementation. The only way
I could fix that was using another SBC in front of Openser.
Cheers,
DanB
On Nov 16, 2007 9:25 AM, Klaus Darilion <klaus.mailinglists(a)pernau.at> wrote:
Hi!
I just was thinking about the follwing scenario_
client a--->proxy--->client b
the proxy does record routing
a calls b
b send back 200 OK, but does NOT mirror the Record-route headers.
in-dialog requests sent from a to b will bypass the proxy, thus bypass
proxy security features (e.g. removing the credentials).
Thus IMO we should have some settings which allow the proxy to add RR
header also for relayed response if during request processing
record-route was called and the proxy misses itself as the top RR
header. what do you think?
regards
klaus
_______________________________________________
Users mailing list
Users(a)lists.openser.org
http://lists.openser.org/cgi-bin/mailman/listinfo/users