Page 393 - Asterisk™: The Future of Telephony

qualify=yes|no|seconds
regcontext (peer)
By specifying the context that contains the actions to perform, you can configure
Asterisk to perform a number of actions when a peer registers to your server. This
option works in conjunction with regexten by specifying the extension to execute.
If no regexten is configured, the peer name is used as the extension. Asterisk will
dynamically create and destroy a NoOp at priority 1 for the extension. All actions to
be performed upon registration should start at priority 2. More than one
regexten may be supplied, if separated by an &. regcontext can be set on a per-peer
basis or globally:
regcontext=peer_registrations
regexten (peer)
The regexten option is used in conjunction with regcontext to specify the extension
that is executed within the configured context. If regexten is not explicitly config-
ured, the peer name is used as the extension to match:
regexten=1000
rtpholdtimeout (peer)
This takes as its argument an integer, specified in seconds. It terminates a call if no
RTP data is received while on hold within the time specified. The value of rtphold
timeout must be greater than that of rtptimeout (see also rtptimeout):
rtpholdtimeout=120
rtpkeepalive (peer)
Specifies how often Asterisk should send keepalives in the RTP stream, in seconds.
Defaults to zero, which means Asterisk won’t send any RTP keepalives:
rtpkeepalive=45
rtptimeout (peer)
This takes as its argument an integer, specified in seconds. It terminates a call if no
RTP data is received within the time specified:

rtptimeout=60
secret (both)
This sets the password to use for authentication:
secret=welcome
setvar (both)
This sets a channel variable, which will be available when a channel to the peer or
user is created and will be destroyed when the call is hung up. For example, to set
the channel variable foo with a value of bar, use:
setvar=foo=bar

SIP | 365