[Asterisk-cvs] asterisk/configs iax.conf.sample,1.52,1.53

kpfleming kpfleming
Fri Sep 2 10:18:41 CDT 2005


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

Modified Files:
	iax.conf.sample 
Log Message:
make chan_iax2 rtupdate behave the same as chan_sip


Index: iax.conf.sample
===================================================================
RCS file: /usr/cvsroot/asterisk/configs/iax.conf.sample,v
retrieving revision 1.52
retrieving revision 1.53
diff -u -d -r1.52 -r1.53
--- iax.conf.sample	25 Aug 2005 02:22:04 -0000	1.52
+++ iax.conf.sample	2 Sep 2005 14:19:36 -0000	1.53
@@ -251,29 +251,25 @@
 ;
 ;codecpriority=host
 
-;
-; Cache realtime friends by adding them to the internal list
-; just like friends added from the config file only on a
-; as-needed basis.
-;
-;rtcachefriends=yes 
-;
-; do not send the update request over realtime.
-;
-;rtnoupdate=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
-;
-;rtautoclear=yes 
-;
-;rtignoreexpire=yes		; when reading a peer from Realtime, if the peer's registration
+;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
+				; address information regardless. (yes|no)
 
 ; Guest sections for unauthenticated connection attempts.  Just
 ; specify an empty secret, or provide no secret section.




More information about the svn-commits mailing list