o Juha Heinanen on 05/06/2011 07:37 PM:
Stefan Sayer writes:
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,
force_outbound_proxy should mean that for in-dialog requests the request
is always sent to outbound proxy no matter what the route set it. if
I may be confusing things, but isn't this what next_hop is for?
must have no effect on contents of route header. for initial requests
it should mean that request it sent to outbound proxy possibly with
pre-loaded route header of outbound proxy.
that's what outbound_proxy is for. its just the force_outbound_proxy
option which makes SEMS non-RFC compliant.
In summary:
next_hop - set IP:port where message is sent to, without any effect on
the message
outbound_proxy - set R-URI and first Route on out-of-dialog messages
force_outbound_proxy=yes - use outbound_proxy value also as R-URI and
first Route in-dialog; non- RFC compliant.
and:
Destination priority:
1. next_hop_ip
2. outbound_proxy (if 1st req or force_outbound_proxy)
3. first route
4. remote URI
please fix, since i want to use outbound_proxy profile option.
just don't set force_outbound_proxy.
Stefan
-- juha
--
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
