Module: sems Branch: master Commit: 3d6356197f685771c62821cc8106ea46b22fce9c URL: http://git.sip-router.org/cgi-bin/gitweb.cgi/sems/?a=commit;h=3d6356197f685771c62821cc8106ea46b22fce9c
Author: Stefan Sayer <[email protected]> Committer: Stefan Sayer <[email protected]> Date: Fri Feb 21 00:40:48 2014 +0100 doc:sbc:enable_reg_caching option documented --- apps/sbc/etc/transparent.sbcprofile.conf | 7 +++++++ doc/Readme.sbc.txt | 24 ++++++++++++++++++++++++ 2 files changed, 31 insertions(+), 0 deletions(-) diff --git a/apps/sbc/etc/transparent.sbcprofile.conf b/apps/sbc/etc/transparent.sbcprofile.conf index a6082e2..385fb08 100644 --- a/apps/sbc/etc/transparent.sbcprofile.conf +++ b/apps/sbc/etc/transparent.sbcprofile.conf @@ -26,6 +26,13 @@ # outbound interface to use (interface ID) #outbound_interface=extern +# registration cache: use local registration cache +# enable_reg_caching=yes +# register upstream every 3600 sec +# min_reg_expires=3600 +# and make UA re-register every 60 sec +# max_ua_expires=60 + ## RTP relay # enable RTP relaying (bridging): #enable_rtprelay=yes diff --git a/doc/Readme.sbc.txt b/doc/Readme.sbc.txt index e2d7285..7316620 100644 --- a/doc/Readme.sbc.txt +++ b/doc/Readme.sbc.txt @@ -296,6 +296,30 @@ next_hop or determined otherwise). These settings apply only for the UAC side, i.e. the outgoing side of the initial INVITE. +Registration caching +-------------------- +If registration caching is activated, SEMS SBC saves the contact of REGISTER +messages in a local registration cache (in-memory) along with information of +where the registration was received from and over which transport, interface +etc. SEMS SBC then replaces the contact with a locally generated alias that +points to itself, and sends it to the upstream registrar. When a message comes +from the registrar, SEMS SBC looks up the alias, retargets it from the +registration cache (sets RURI), and sends it over the saved transport to the +proper remote address where the client is (e.g. behind NAT) by setting next_hop +etc properly. + +To activate the registration cache, use the option + enable_reg_caching=yes +(for both REGISTER and other messages). With the parameters + min_reg_expires and max_ua_expires +it can be controlled how long the registration to the upstream registrar should +persist and how short it should be to the UA. E.g. if the UA should periodicly +re-REGISTER every 60 seconds, but to the upstream registrar the registration should +persist 1h, min_reg_expires=3600 and max_ua_expires=60 should be set. + +For a local registrar (i.e. operation without an upstream registrar), see the 'registrar' +call control module. + Filters ------- Headers and messages may be filtered. A filter can be set to _______________________________________________ Semsdev mailing list [email protected] http://lists.iptel.org/mailman/listinfo/semsdev
