Module: sems Branch: master Commit: 9f26c92b46317551103ae33aead2c3c27b0fba13 URL: http://git.sip-router.org/cgi-bin/gitweb.cgi/sems/?a=commit;h=9f26c92b46317551103ae33aead2c3c27b0fba13
Author: Stefan Sayer <[email protected]> Committer: Stefan Sayer <[email protected]> Date: Fri Feb 21 18:23:20 2014 +0100 doc:sbc:documented next_hop options with various alternatives/transports --- doc/Readme.sbc.txt | 6 +++++- 1 files changed, 5 insertions(+), 1 deletions(-) diff --git a/doc/Readme.sbc.txt b/doc/Readme.sbc.txt index b1262b2..30a5b42 100644 --- a/doc/Readme.sbc.txt +++ b/doc/Readme.sbc.txt @@ -289,7 +289,11 @@ also for in-dialog requests. Note that this is NOT RFC3261 compliant (section The next hop (destination IP[:port] of outgoing requests) can be set with the next_hop option. next_hop port defaults to 5060 if not set or -empty. Usually, replies are sent back to where the request came from +empty. Multiple alternatives for the next hop can be set, also with their +respective transports, e.g. + next_hop=1.2.3.4/TCP,1.2.3.4:5060/UDP + +Usually, replies are sent back to where the request came from (honoring rport), but if next_hop should be used nevertheless, next_hop_for_replies profile option can be set to "yes". _______________________________________________ Semsdev mailing list [email protected] http://lists.iptel.org/mailman/listinfo/semsdev
