o Juha Heinanen on 05/06/2011 05:33 PM:
Juha Heinanen writes:
i'm pretty sure that rfc3261 says that in in-dialog requests, route
header must contain in reverse order the entries learned from 200 ok
that established the dialog.
rfc 3261 section 12.1 Creation of a Dialog, 12.1.1 UAS behavior:
The route set MUST be set to the list of URIs in the Record-Route header
field from the request, taken in order and preserving all URI
parameters.
section 2.2 Requests within a Dialog, 12.2.1 UAC Behavior:
If the route set is not empty, and the first URI in the route set
contains the lr parameter (see Section 19.1.1),
the UAC MUST place the remote target URI into the Request-URI and MUST
include a Route header field containing the route set values in order,
including all parameters.
to me this means that there cannot be any extra entries in the route
header of bye.
indeed, then the force_outbound_proxy config options makes SEMS not
RFC compliant in that matter.
Just set that one to no in the sbc profile. Probably this should be
mentioned in the doc.
Stefan
-- juha
_______________________________________________
Sems mailing list
[email protected]
http://lists.iptel.org/mailman/listinfo/sems
--
Stefan Sayer
VoIP Services Consulting and Development
Warschauer Str. 24
10243 Berlin
tel:+491621366449
sip:[email protected]
email/xmpp:[email protected]
_______________________________________________
Sems mailing list
[email protected]
http://lists.iptel.org/mailman/listinfo/sems
