mirror of
https://github.com/asterisk/asterisk.git
synced 2025-09-06 12:36:58 +00:00
properly document this morning's changes to 'ignoreregexpire'
git-svn-id: https://origsvn.digium.com/svn/asterisk/trunk@6871 65c4cc65-6c06-0410-ace0-fbb531ad65f3
This commit is contained in:
@@ -204,9 +204,18 @@ srvlookup=yes ; Enable DNS SRV lookups on outbound calls
|
|||||||
; friends expire within this number of seconds instead of the
|
; friends expire within this number of seconds instead of the
|
||||||
; registration interval.
|
; registration interval.
|
||||||
|
|
||||||
;ignoreexpire=yes ; When reading a peer from Realtime, if the peer's registration
|
;ignoreregexpire=yes ; Enabling this setting has two functions:
|
||||||
; has expired based on its registration interval, used the stored
|
;
|
||||||
; address information regardless. (yes|no)
|
; For non-realtime peers, when their registration expires, the information
|
||||||
|
; will _not_ be removed from memory or the Asterisk database; if you attempt
|
||||||
|
; to place a call to the peer, the existing information will be used in spite
|
||||||
|
; of it having expired
|
||||||
|
;
|
||||||
|
; For realtime peers, when the peer is retrieved from realtime storage,
|
||||||
|
; the registration information will be used regardless of whether
|
||||||
|
; it has expired or not; if it expires while the realtime peer is still in
|
||||||
|
; memory (due to caching or other reasons), the information will not be
|
||||||
|
; removed from realtime storage
|
||||||
|
|
||||||
; Incoming INVITE and REFER messages can be matched against a list of 'allowed'
|
; Incoming INVITE and REFER messages can be matched against a list of 'allowed'
|
||||||
; domains, each of which can direct the call to a specific context if desired.
|
; domains, each of which can direct the call to a specific context if desired.
|
||||||
|
Reference in New Issue
Block a user