Module: sems
Branch: 1.4
Commit: b34e028f1405bd5ec3aa3b5911ecce500fd2792e
URL:    
http://git.sip-router.org/cgi-bin/gitweb.cgi/sems/?a=commit;h=b34e028f1405bd5ec3aa3b5911ecce500fd2792e

Author: Stefan Sayer <[email protected]>
Committer: Stefan Sayer <[email protected]>
Date:   Fri May  6 19:34:08 2011 +0200

doc: added note about force_outbound_proxy non-rfc-compliance

thanks to Juha Heinanen for reporting

---

 doc/Readme.sbc.txt |    7 +++++--
 1 files changed, 5 insertions(+), 2 deletions(-)

diff --git a/doc/Readme.sbc.txt b/doc/Readme.sbc.txt
index 4ae8100..4b03751 100644
--- a/doc/Readme.sbc.txt
+++ b/doc/Readme.sbc.txt
@@ -248,8 +248,11 @@ Outbound proxy and next hop
 
 An outbound proxy may be set with the outbound_proxy option. If this is
 not set, the outbound_proxy option of sems.conf is used, if that one is set.
-Setting an outbound proxy will add a route header. force_outbound_proxy forces
-the outbound proxy route also for in-dialog requests.
+Setting an outbound proxy will add a route header.
+
+force_outbound_proxy forces the outbound proxy as first route and request URI
+also for in-dialog requests. Note that this is NOT RFC3261 compliant (section
+2.2 Requests within a Dialog, 12.2.1 UAC Behavior).
 
 The next hop (destination IP[:port] of outgoing requests) can be set with
 the next_hop_ip and next_hop_port options. next_hop_port defaults to 5060

_______________________________________________
Semsdev mailing list
[email protected]
http://lists.iptel.org/mailman/listinfo/semsdev

Reply via email to