Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Updated to GIT-13-5a5b949

...

Option Name

Type

Default Value

Regular Expression

Description

max_forwards

Unsigned Integer

70

false

Value used in Max-Forwards header for SIP requests.

keep_alive_interval

Unsigned Integer

0

false

The interval (in seconds) to send keepalives to active connection-oriented transports.

contact_expiration_check_interval

Unsigned Integer

30

false

The interval (in seconds) to check for expired contacts.

disable_multi_domain

Boolean

no

false

Disable Multi Domain support

max_initial_qualify_time

Unsigned Integer

0

false

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.

unidentified_request_period

Unsigned Integer

5

false

The number of seconds over which to accumulate unidentified requests.

unidentified_request_count

Unsigned Integer

5

false

The number of unidentified requests from a single IP to allow.

unidentified_request_prune_interval

Unsigned Integer

30

false

The interval at which unidentified requests are older than twice the unidentified_request_period are pruned.

type

None

 

false

Must be of type 'global'.

user_agent

String

Asterisk PBX GIT-13-bf213595a5b949

false

Value used in User-Agent header for SIP requests and Server header for SIP responses.

regcontext

String

 

false

When set, Asterisk will dynamically create and destroy a NoOp priority 1 extension for a given peer who registers or unregisters with us.

default_outbound_endpoint

String

default_outbound_endpoint

false

Endpoint to use when sending an outbound request to a URI without a specified endpoint.

default_voicemail_extension

String

 

false

The voicemail extension to send in the NOTIFY Message-Account header if not specified on endpoint or aor

debug

String

no

false

Enable/Disable SIP debug logging. Valid options include yes

no or a host address

endpoint_identifier_order

String

ip,username,anonymous

false

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.

default_from_user

String

asterisk

false

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.

default_realm

String

asterisk

false

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.

mwi_tps_queue_high

Unsigned Integer

500

false

MWI taskprocessor high water alert trigger level.

mwi_tps_queue_low

Integer

-1

false

MWI taskprocessor low water clear alert level.

mwi_disable_initial_unsolicited

Boolean

no

false

Enable/Disable sending unsolicited MWI to all endpoints on startup.

Configuration Option Descriptions

...

Info
titleNote

One of the identifiers is "auth_username" which matches on the username in an Authentication header. This method has some security considerations because an Authentication header is not present on the first message of a dialog when digest authentication is used. The client can't generate it until the server sends the challenge in a 401 response. Since Asterisk normally sends a security event when an incoming request can't be matched to an endpoint, using auth_username requires that the security event be deferred until a request is received with the Authentication header and only generated if the username doesn't result in a match. This may result in a delay before an attack is recognized. You can control how many unmatched requests are received from a single ip address before a security event is generated using the unidentified_request parameters.

Anchor
global_mwi_tps_queue_high
global_mwi_tps_queue_high

mwi_tps_queue_high

On a heavily loaded system you may need to adjust the taskprocessor queue limits. If any taskprocessor queue size reaches its high water level then pjsip will stop processing new requests until the alert is cleared. The alert clears when all alerting taskprocessor queues have dropped to their low water clear level.

Anchor
global_mwi_tps_queue_low
global_mwi_tps_queue_low

mwi_tps_queue_low

On a heavily loaded system you may need to adjust the taskprocessor queue limits. If any taskprocessor queue size reaches its high water level then pjsip will stop processing new requests until the alert is cleared. The alert clears when all alerting taskprocessor queues have dropped to their low water clear level.

Info
titleNote

Set to -1 for the low water level to be 90% of the high water level.

Anchor
global_mwi_disable_initial_unsolicited
global_mwi_disable_initial_unsolicited

mwi_disable_initial_unsolicited

When the initial unsolicited MWI notification are enabled on startup then the initial notifications get sent at startup. If you have a lot of endpoints (thousands) that use unsolicited MWI then you may want to consider disabling the initial startup notifications.

When the initial unsolicited MWI notifications are disabled on startup then the notifications will start on the endpoint's next contact update.

Import Version

This documentation was imported from Asterisk Version GIT-13-bf213595a5b949