Must be of type 'contact'.
SIP URI to contact peer
Time to keep alive a contact
Interval at which to qualify a contact
Timeout for qualify
Outbound proxy used when sending OPTIONS request
Stored Path vector for use in Route headers on outgoing requests.
User-Agent header from registration.
Asterisk Server name
Configuration Option Descriptions
The User-Agent is automatically stored based on data present in incoming SIP REGISTER requests and is not intended to be configured manually.
Asterisk Server name on which SIP endpoint registered.
The configuration for a location of an endpoint
Value used in Max-Forwards header for SIP requests.
The interval (in seconds) to send keepalives to active connection-oriented transports.
The interval (in seconds) to check for expired contacts.
Disable Multi Domain support
The maximum amount of time from startup that qualifies should be attempted on all contacts. If greater than the qualify_frequency for an aor, qualify_frequency will be used instead.
The number of seconds over which to accumulate unidentified requests.
The number of unidentified requests from a single IP to allow.
The interval at which unidentified requests are older than twice the unidentified_request_period are pruned.
Must be of type 'global'.
Value used in User-Agent header for SIP requests and Server header for SIP responses.
When set, Asterisk will dynamically create and destroy a NoOp priority 1 extension for a given peer who registers or unregisters with us.
Endpoint to use when sending an outbound request to a URI without a specified endpoint.
The voicemail extension to send in the NOTIFY Message-Account header if not specified on endpoint or aor
Enable/Disable SIP debug logging. Valid options include yes
no or a host address
The order by which endpoint identifiers are processed and checked. Identifier names are usually derived from and can be found in the endpoint identifier module itself (res_pjsip_endpoint_identifier_*). You can use the CLI command "pjsip show identifiers" to see the identifiers currently available.
When Asterisk generates an outgoing SIP request, the From header username will be set to this value if there is no better option (such as CallerID) to be used.
When Asterisk generates an challenge, the digest will be set to this value if there is no better option (such as auth/realm) to be used.
This documentation was imported from Asterisk Version GIT-13-69ced868aef2c4