[Asterisk-cvs] asterisk/configs sip.conf.sample,1.65,1.66

[kpfleming]

Update of /usr/cvsroot/asterisk/configs
In directory mongoose.digium.com:/tmp/cvs-serv27411/configs

Modified Files:
	sip.conf.sample 
Log Message:
clean up rtcaching config options (issue #4075)


Index: sip.conf.sample
===================================================================
RCS file: /usr/cvsroot/asterisk/configs/sip.conf.sample,v
retrieving revision 1.65
retrieving revision 1.66
diff -u -d -r1.65 -r1.66
--- sip.conf.sample	23 Aug 2005 00:50:38 -0000	1.65
+++ sip.conf.sample	25 Aug 2005 02:25:30 -0000	1.66
@@ -169,20 +169,25 @@
 				; 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|<seconds>)
+				; 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