From bf6bc6d4fd293447be123a2ae6fb9e89b7b775be Mon Sep 17 00:00:00 2001 From: "Kevin P. Fleming" Date: Thu, 25 Aug 2005 02:25:30 +0000 Subject: clean up rtcaching config options (issue #4075) git-svn-id: https://origsvn.digium.com/svn/asterisk/trunk@6401 65c4cc65-6c06-0410-ace0-fbb531ad65f3 --- configs/sip.conf.sample | 31 ++++++++++++++++++------------- 1 file changed, 18 insertions(+), 13 deletions(-) (limited to 'configs') diff --git a/configs/sip.conf.sample b/configs/sip.conf.sample index a348b52bc..2eaba6c3f 100755 --- a/configs/sip.conf.sample +++ b/configs/sip.conf.sample @@ -169,20 +169,25 @@ srvlookup=yes ; Enable DNS SRV lookups on outbound calls ; route = Assume NAT, don't send rport ; (work around more UNIDEN bugs) -;rtcachefriends=yes ; Cache realtime friends by adding them to the internal list - ; just like friends added from the config file only on a - ; as-needed basis. -;rtnoupdate=yes ; do not send the update request over realtime. -;rtautoclear=yes ; Auto-Expire friends created on the fly on the same schedule - ; as if it had just registered when the registration expires - ; the friend will vanish from the configuration until requested - ; again. If set to an integer, friends expire - ; within this number of seconds instead of the - ; same as the registration interval -;rtignoreexpire=yes ; when reading a peer from Realtime, if the peer's registration - ; has expired based on its registration interval, used the stored - ; address information regardless +;rtcachefriends=yes ; Cache realtime friends by adding them to the internal list + ; just like friends added from the config file only on a + ; as-needed basis? (yes|no) + +;rtupdate=yes ; Send registry updates to database using realtime? (yes|no) + ; If set to yes, when a SIP UA registers successfully, the ip address, + ; the origination port, the registration period, and the username of + ; the UA will be set to database via realtime. If not present, defaults to 'yes'. +;rtautoclear=yes ; Auto-Expire friends created on the fly on the same schedule + ; as if it had just registered? (yes|no|) + ; If set to yes, when the registration expires, the friend will vanish from + ; the configuration until requested again. If set to an integer, + ; friends expire within this number of seconds instead of the + ; registration interval. + +;rtignoreexpire=yes ; When reading a peer from Realtime, if the peer's registration + ; has expired based on its registration interval, used the stored + ; address information regardless. (yes|no) [authentication] ; Global credentials for outbound calls, i.e. when a proxy challenges your -- cgit v1.2.3