SIP Resource using PJProject

This configuration documentation is for functionality provided by res_pjsip.

pjsip.conf

endpoint

Endpoint

Configuration Option Reference

Option Name

Type

Default Value

Regular Expression

Description

100rel

Custom

yes

false

Allow support for RFC3262 provisional ACK tags

aggregate_mwi

Boolean

yes

false

Condense MWI notifications into a single NOTIFY.

allow

Codec

 

false

Media Codec(s) to allow

codec_prefs_incoming_offer

Custom

prefer: pending, operation: intersect, keep: all, transcode: allow

false

Codec negotiation prefs for incoming offers.

codec_prefs_outgoing_offer

Custom

prefer: pending, operation: union, keep: all, transcode: allow

false

Codec negotiation prefs for outgoing offers.

codec_prefs_incoming_answer

Custom

prefer: pending, operation: intersect, keep: all

false

Codec negotiation prefs for incoming answers.

codec_prefs_outgoing_answer

Custom

prefer: pending, operation: intersect, keep: all

false

Codec negotiation prefs for outgoing answers.

allow_overlap

Boolean

yes

false

Enable RFC3578 overlap dialing support.

overlap_context

String

 

false

Dialplan context to use for RFC3578 overlap dialing.

aors

String

 

false

AoR(s) to be used with the endpoint

auth

Custom

 

false

Authentication Object(s) associated with the endpoint

callerid

Custom

 

false

CallerID information for the endpoint

callerid_privacy

Custom

allowed_not_screened

false

Default privacy level

callerid_tag

Custom

 

false

Internal id_tag for the endpoint

context

String

default

false

Dialplan context for inbound sessions

direct_media_glare_mitigation

Custom

none

false

Mitigation of direct media (re)INVITE glare

direct_media_method

Custom

invite

false

Direct Media method type

trust_connected_line

Boolean

yes

false

Accept Connected Line updates from this endpoint

send_connected_line

Boolean

yes

false

Send Connected Line updates to this endpoint

connected_line_method

Custom

invite

false

Connected line method type

direct_media

Boolean

yes

false

Determines whether media may flow directly between endpoints.

disable_direct_media_on_nat

Boolean

no

false

Disable direct media session refreshes when NAT obstructs the media session

disallow

 

 

 

Media Codec(s) to disallow

dtmf_mode

Custom

rfc4733

false

DTMF mode

media_address

String

 

false

IP address used in SDP for media handling

bind_rtp_to_media_address

Boolean

no

false

Bind the RTP instance to the media_address

force_rport

Boolean

yes

false

Force use of return port

ice_support

Boolean

no

false

Enable the ICE mechanism to help traverse NAT

identify_by

Custom

username,ip

false

Way(s) for the endpoint to be identified

redirect_method

Custom

user

false

How redirects received from an endpoint are handled

mailboxes

String

 

false

NOTIFY the endpoint when state changes for any of the specified mailboxes

mwi_subscribe_replaces_unsolicited

Boolean

no

false

An MWI subscribe will replace sending unsolicited NOTIFYs

voicemail_extension

Custom

 

false

The voicemail extension to send in the NOTIFY Message-Account header

moh_suggest

String

default

false

Default Music On Hold class

outbound_auth

Custom

 

false

Authentication object(s) used for outbound requests

outbound_proxy

String

 

false

Full SIP URI of the outbound proxy used to send requests

rewrite_contact

Boolean

no

false

Allow Contact header to be rewritten with the source IP address-port

rtp_ipv6

Boolean

no

false

Allow use of IPv6 for RTP traffic

rtp_symmetric

Boolean

no

false

Enforce that RTP must be symmetric

send_diversion

Boolean

yes

false

Send the Diversion header, conveying the diversion information to the called user agent

send_history_info

Boolean

no

false

Send the History-Info header, conveying the diversion information to the called and calling user agents

send_pai

Boolean

no

false

Send the P-Asserted-Identity header

send_rpid

Boolean

no

false

Send the Remote-Party-ID header

rpid_immediate

Boolean

no

false

Immediately send connected line updates on unanswered incoming calls.

timers_min_se

Unsigned Integer

90

false

Minimum session timers expiration period

timers

Custom

yes

false

Session timers for SIP packets

timers_sess_expires

Unsigned Integer

1800

false

Maximum session timer expiration period

transport

String

 

false

Explicit transport configuration to use

trust_id_inbound

Boolean

no

false

Accept identification information received from this endpoint

trust_id_outbound

Boolean

no

false

Send private identification details to the endpoint.

type

None

 

false

Must be of type 'endpoint'.

use_ptime

Boolean

no

false

Use Endpoint's requested packetization interval

use_avpf

Boolean

no

false

Determines whether res_pjsip will use and enforce usage of AVPF for this endpoint.

force_avp

Boolean

no

false

Determines whether res_pjsip will use and enforce usage of AVP, regardless of the RTP profile in use for this endpoint.

media_use_received_transport

Boolean

no

false

Determines whether res_pjsip will use the media transport received in the offer SDP in the corresponding answer SDP.

media_encryption

Custom

no

false

Determines whether res_pjsip will use and enforce usage of media encryption for this endpoint.

media_encryption_optimistic

Boolean

no

false

Determines whether encryption should be used if possible but does not terminate the session if not achieved.

g726_non_standard

Boolean

no

false

Force g.726 to use AAL2 packing order when negotiating g.726 audio

inband_progress

Boolean

no

false

Determines whether chan_pjsip will indicate ringing using inband progress.

call_group

Custom

 

false

The numeric pickup groups for a channel.

pickup_group

Custom

 

false

The numeric pickup groups that a channel can pickup.

named_call_group

Custom

 

false

The named pickup groups for a channel.

named_pickup_group

Custom

 

false

The named pickup groups that a channel can pickup.

device_state_busy_at

Unsigned Integer

0

false

The number of in-use channels which will cause busy to be returned as device state

t38_udptl

Boolean

no

false

Whether T.38 UDPTL support is enabled or not

t38_udptl_ec

Custom

none

false

T.38 UDPTL error correction method

t38_udptl_maxdatagram

Unsigned Integer

0

false

T.38 UDPTL maximum datagram size

fax_detect

Boolean

no

false

Whether CNG tone detection is enabled

fax_detect_timeout

Unsigned Integer

0

false

How long into a call before fax_detect is disabled for the call

t38_udptl_nat

Boolean

no

false

Whether NAT support is enabled on UDPTL sessions

t38_udptl_ipv6

Boolean

no

false

Whether IPv6 is used for UDPTL Sessions

t38_bind_udptl_to_media_address

Boolean

no

false

Bind the UDPTL instance to the media_adress

tone_zone

String

 

false

Set which country's indications to use for channels created for this endpoint.

language

String

 

false

Set the default language to use for channels created for this endpoint.

one_touch_recording

Boolean

no

false

Determines whether one-touch recording is allowed for this endpoint.

record_on_feature

String

automixmon

false

The feature to enact when one-touch recording is turned on.

record_off_feature

String

automixmon

false

The feature to enact when one-touch recording is turned off.

rtp_engine

String

asterisk

false

Name of the RTP engine to use for channels created for this endpoint

allow_transfer

Boolean

yes

false

Determines whether SIP REFER transfers are allowed for this endpoint

user_eq_phone

Boolean

no

false

Determines whether a user=phone parameter is placed into the request URI if the user is determined to be a phone number

moh_passthrough

Boolean

no

false

Determines whether hold and unhold will be passed through using re-INVITEs with recvonly and sendrecv to the remote side

sdp_owner

String

-

false

String placed as the username portion of an SDP origin (o=) line.

sdp_session

String

Asterisk

false

String used for the SDP session (s=) line.

tos_audio

Custom

0

false

DSCP TOS bits for audio streams

tos_video

Custom

0

false

DSCP TOS bits for video streams

cos_audio

Unsigned Integer

0

false

Priority for audio streams

cos_video

Unsigned Integer

0

false

Priority for video streams

allow_subscribe

Boolean

yes

false

Determines if endpoint is allowed to initiate subscriptions with Asterisk.

sub_min_expiry

Unsigned Integer

0

false

The minimum allowed expiry time for subscriptions initiated by the endpoint.

from_user

Custom

 

false

Username to use in From header for requests to this endpoint.

mwi_from_user

String

 

false

Username to use in From header for unsolicited MWI NOTIFYs to this endpoint.

from_domain

String

 

false

Domain to use in From header for requests to this endpoint.

dtls_verify

Custom

no

false

Verify that the provided peer certificate is valid

dtls_rekey

Custom

0

false

Interval at which to renegotiate the TLS session and rekey the SRTP session

dtls_auto_generate_cert

Custom

no

false

Whether or not to automatically generate an ephemeral X.509 certificate

dtls_cert_file

Custom

 

false

Path to certificate file to present to peer

dtls_private_key

Custom

 

false

Path to private key for certificate file

dtls_cipher

Custom

 

false

Cipher to use for DTLS negotiation

dtls_ca_file

Custom

 

false

Path to certificate authority certificate

dtls_ca_path

Custom

 

false

Path to a directory containing certificate authority certificates

dtls_setup

Custom

 

false

Whether we are willing to accept connections, connect to the other party, or both.

dtls_fingerprint

Custom

 

false

Type of hash to use for the DTLS fingerprint in the SDP.

srtp_tag_32

Boolean

no

false

Determines whether 32 byte tags should be used instead of 80 byte tags.

set_var

Custom

 

false

Variable set on a channel involving the endpoint.

message_context

String

 

false

Context to route incoming MESSAGE requests to.

accountcode

String

 

false

An accountcode to set automatically on any channels created for this endpoint.

preferred_codec_only

Boolean

no

false

Respond to a SIP invite with the single most preferred codec (DEPRECATED)

incoming_call_offer_pref

Custom

local

false

Preferences for selecting codecs for an incoming call.

outgoing_call_offer_pref

Custom

remote_merge

false

Preferences for selecting codecs for an outgoing call.

rtp_keepalive

Unsigned Integer

0

false

Number of seconds between RTP comfort noise keepalive packets.

rtp_timeout

Unsigned Integer

0

false

Maximum number of seconds without receiving RTP (while off hold) before terminating call.

rtp_timeout_hold

Unsigned Integer

0

false

Maximum number of seconds without receiving RTP (while on hold) before terminating call.

acl

Custom

 

false

List of IP ACL section names in acl.conf

deny

Custom

 

false

List of IP addresses to deny access from

permit

Custom

 

false

List of IP addresses to permit access from

contact_acl

Custom

 

false

List of Contact ACL section names in acl.conf

contact_deny

Custom

 

false

List of Contact header addresses to deny

contact_permit

Custom

 

false

List of Contact header addresses to permit

subscribe_context

String

 

false

Context for incoming MESSAGE requests.

contact_user

Custom

 

false

Force the user on the outgoing Contact header to this value.

asymmetric_rtp_codec

Boolean

no

false

Allow the sending and receiving RTP codec to differ

rtcp_mux

Boolean

no

false

Enable RFC 5761 RTCP multiplexing on the RTP port

refer_blind_progress

Boolean

yes

false

Whether to notifies all the progress details on blind transfer

notify_early_inuse_ringing

Boolean

no

false

Whether to notifies dialog-info 'early' on InUse&Ringing state

max_audio_streams

Unsigned Integer

1

false

The maximum number of allowed audio streams for the endpoint

max_video_streams

Unsigned Integer

1

false

The maximum number of allowed video streams for the endpoint

bundle

Boolean

no

false

Enable RTP bundling

webrtc

Boolean

no

false

Defaults and enables some options that are relevant to WebRTC

incoming_mwi_mailbox

String

 

false

Mailbox name to use when incoming MWI NOTIFYs are received

follow_early_media_fork

Boolean

yes

false

Follow SDP forked media when To tag is different

accept_multiple_sdp_answers

Boolean

no

false

Accept multiple SDP answers on non-100rel responses

suppress_q850_reason_headers

Boolean

no

false

Suppress Q.850 Reason headers for this endpoint

ignore_183_without_sdp

Boolean

no

false

Do not forward 183 when it doesn't contain SDP

stir_shaken

Custom

off

false

Enable STIR/SHAKEN support on this endpoint

stir_shaken_profile

String

 

false

STIR/SHAKEN profile containing additional configuration options

allow_unauthenticated_options

Boolean

no

false

Skip authentication when receiving OPTIONS requests

security_negotiation

Custom

no

false

The kind of security agreement negotiation to use. Currently, only mediasec is supported.

security_mechanisms

Custom

 

false

List of security mechanisms supported.

geoloc_incoming_call_profile

String

 

false

Geolocation profile to apply to incoming calls

geoloc_outgoing_call_profile

String

 

false

Geolocation profile to apply to outgoing calls

send_aoc

Boolean

no

false

Send Advice-of-Charge messages

Configuration Option Descriptions

100rel

aggregate_mwi

When enabled, aggregate_mwi condenses message waiting notifications from multiple mailboxes into a single NOTIFY. If it is disabled, individual NOTIFYs are sent for each mailbox.

codec_prefs_incoming_offer

This is a string that describes how the codecs specified on an incoming SDP offer (pending) are reconciled with the codecs specified on an endpoint (configured) before being sent to the Asterisk core. The string actually specifies 4 name:value pair parameters separated by commas. Whitespace is ignored and they may be specified in any order. Note that this option is reserved for future functionality.

Parameters:

Prefer the codecs coming from the caller. Use only the ones that are common. keeping the order of the preferred list. Keep all codecs in the result. Allow transcoding.

codec_prefs_outgoing_offer

This is a string that describes how the codecs specified in the topology that comes from the Asterisk core (pending) are reconciled with the codecs specified on an endpoint (configured) when sending an SDP offer. The string actually specifies 4 name:value pair parameters separated by commas. Whitespace is ignored and they may be specified in any order. Note that this option is reserved for future functionality.

Parameters:

Prefer the codecs coming from the endpoint. Merge them with the codecs from the core keeping the order of the preferred list. Keep only the first one. No transcoding allowed.

codec_prefs_incoming_answer

This is a string that describes how the codecs specified in an incoming SDP answer (pending) are reconciled with the codecs specified on an endpoint (configured) when receiving an SDP answer. The string actually specifies 4 name:value pair parameters separated by commas. Whitespace is ignored and they may be specified in any order. Note that this option is reserved for future functionality.

Parameters:

Use the defaults but keep oinly the first codec.

codec_prefs_outgoing_answer

This is a string that describes how the codecs that come from the core (pending) are reconciled with the codecs specified on an endpoint (configured) when sending an SDP answer. The string actually specifies 4 name:value pair parameters separated by commas. Whitespace is ignored and they may be specified in any order. Note that this option is reserved for future functionality.

Parameters:

Use the defaults but keep oinly the first codec.

overlap_context

Dialplan context to use for overlap dialing extension matching. If not specified, the context configured for the endpoint will be used. If specified, the extensions/patterns in the specified context will be used for determining if a full number has been received from the endpoint.

aors

List of comma separated AoRs that the endpoint should be associated with.

auth

This is a comma-delimited list of auth sections defined in pjsip.conf to be used to verify inbound connection attempts.

Endpoints without an authentication object configured will allow connections without verification.

Using the same auth section for inbound and outbound authentication is not recommended. There is a difference in meaning for an empty realm setting between inbound and outbound authentication uses. See the auth realm description for details.

callerid

Must be in the format Name <Number>, or only <Number>.

callerid_privacy

direct_media_glare_mitigation

This setting attempts to avoid creating INVITE glare scenarios by disabling direct media reINVITEs in one direction thereby allowing designated servers (according to this option) to initiate direct media reINVITEs without contention and significantly reducing call setup time.

A more detailed description of how this option functions can be found on the Asterisk wiki https://wiki.asterisk.org/wiki/display/AST/SIP+Direct+Media+Reinvite+Glare+Avoidance

direct_media_method

Method for setting up Direct Media between endpoints.

connected_line_method

Method used when updating connected line information.

dtmf_mode

This setting allows to choose the DTMF mode for endpoint communication.

media_address

At the time of SDP creation, the IP address defined here will be used as the media address for individual streams in the SDP.

Be aware that the external_media_address option, set in Transport configuration, can also affect the final media address used in the SDP.

bind_rtp_to_media_address

If media_address is specified, this option causes the RTP instance to be bound to the specified ip address which causes the packets to be sent from that address.

identify_by

Endpoints and AORs can be identified in multiple ways. This option is a comma separated list of methods the endpoint can be identified.

This option controls both how an endpoint is matched for incoming traffic and also how an AOR is determined if a registration occurs. You must list at least one method that also matches for AORs or the registration will fail.

redirect_method

When a redirect is received from an endpoint there are multiple ways it can be handled. If this option is set to user the user portion of the redirect target is treated as an extension within the dialplan and dialed using a Local channel. If this option is set to uri_core the target URI is returned to the dialing application which dials it using the PJSIP channel driver and endpoint originally used. If this option is set to uri_pjsip the redirect occurs within chan_pjsip itself and is not exposed to the core at all. The uri_pjsip option has the benefit of being more efficient and also supporting multiple potential redirect targets. The con is that since redirection occurs within chan_pjsip redirecting information is not forwarded and redirection can not be prevented.

mailboxes

Asterisk will send unsolicited MWI NOTIFY messages to the endpoint when state changes happen for any of the specified mailboxes. More than one mailbox can be specified with a comma-delimited string. app_voicemail mailboxes must be specified as [email protected]; for example: [email protected] For mailboxes provided by external sources, such as through the res_mwi_external module, you must specify strings supported by the external system.

For endpoints that SUBSCRIBE for MWI, use the mailboxes option in your AOR configuration.

outbound_auth

This is a comma-delimited list of auth sections defined in pjsip.conf used to respond to outbound connection authentication challenges.

Using the same auth section for inbound and outbound authentication is not recommended. There is a difference in meaning for an empty realm setting between inbound and outbound authentication uses. See the auth realm description for details.

rewrite_contact

On inbound SIP messages from this endpoint, the Contact header or an appropriate Record-Route header will be changed to have the source IP address and port. This option does not affect outbound messages sent to this endpoint. This option helps servers communicate with endpoints that are behind NATs. This option also helps reuse reliable transport connections such as TCP and TLS.

rpid_immediate

When enabled, immediately send 180 Ringing or 183 Progress response messages to the caller if the connected line information is updated before the call is answered. This can send a 180 Ringing response before the call has even reached the far end. The caller can start hearing ringback before the far end even gets the call. Many phones tend to grab the first connected line information and refuse to update the display if it changes. The first information is not likely to be correct if the call goes to an endpoint not under the control of this Asterisk box.

When disabled, a connected line update must wait for another reason to send a message with the connected line information to the caller before the call is answered. You can trigger the sending of the information by using an appropriate dialplan application such as Ringing.

timers_min_se

Minimum session timer expiration period. Time in seconds.

timers

timers_sess_expires

Maximum session timer expiration period. Time in seconds.

transport

This will force the endpoint to use the specified transport configuration to send SIP messages. You need to already know what kind of transport (UDP/TCP/IPv4/etc) the endpoint device will use.

Not specifying a transport will select the first configured transport in pjsip.conf which is compatible with the URI we are trying to contact.

Warning

Icon

Transport configuration is not affected by reloads. In order to change transports, a full Asterisk restart is required

trust_id_inbound

This option determines whether Asterisk will accept identification from the endpoint from headers such as P-Asserted-Identity or Remote-Party-ID header. This option applies both to calls originating from the endpoint and calls originating from Asterisk. If no, the configured Caller-ID from pjsip.conf will always be used as the identity for the endpoint.

trust_id_outbound

This option determines whether res_pjsip will send private identification information to the endpoint. If no, private Caller-ID information will not be forwarded to the endpoint. "Private" in this case refers to any method of restricting identification. Example: setting callerid_privacy to any prohib variation. Example: If trust_id_inbound is set to yes, the presence of a Privacy: id header in a SIP request or response would indicate the identification provided in the request is private.

use_avpf

If set to yes, res_pjsip will use the AVPF or SAVPF RTP profile for all media offers on outbound calls and media updates and will decline media offers not using the AVPF or SAVPF profile.

If set to no, res_pjsip will use the AVP or SAVP RTP profile for all media offers on outbound calls and media updates, and will decline media offers not using the AVP or SAVP profile.

force_avp

If set to yes, res_pjsip will use the AVP, AVPF, SAVP, or SAVPF RTP profile for all media offers on outbound calls and media updates including those for DTLS-SRTP streams.

If set to no, res_pjsip will use the respective RTP profile depending on configuration.

media_use_received_transport

If set to yes, res_pjsip will use the received media transport.

If set to no, res_pjsip will use the respective RTP profile depending on configuration.

media_encryption

media_encryption_optimistic

This option only applies if media_encryption is set to sdes or dtls.

g726_non_standard

When set to "yes" and an endpoint negotiates g.726 audio then use g.726 for AAL2 packing order instead of what is recommended by RFC3551. Since this essentially replaces the underlying 'g726' codec with 'g726aal2' then 'g726aal2' needs to be specified in the endpoint's allowed codec list.

inband_progress

If set to yes, chan_pjsip will send a 183 Session Progress when told to indicate ringing and will immediately start sending ringing as audio.

If set to no, chan_pjsip will send a 180 Ringing when told to indicate ringing and will NOT send it as audio.

call_group

Can be set to a comma separated list of numbers or ranges between the values of 0-63 (maximum of 64 groups).

pickup_group

Can be set to a comma separated list of numbers or ranges between the values of 0-63 (maximum of 64 groups).

named_call_group

Can be set to a comma separated list of case sensitive strings limited by supported line length.

named_pickup_group

Can be set to a comma separated list of case sensitive strings limited by supported line length.

device_state_busy_at

When the number of in-use channels for the endpoint matches the devicestate_busy_at setting the PJSIP channel driver will return busy as the device state instead of in use.

t38_udptl

If set to yes T.38 UDPTL support will be enabled, and T.38 negotiation requests will be accepted and relayed.

t38_udptl_ec

t38_udptl_maxdatagram

This option can be set to override the maximum datagram of a remote endpoint for broken endpoints.

fax_detect

This option can be set to send the session to the fax extension when a CNG tone is detected.

fax_detect_timeout

The option determines how many seconds into a call before the fax_detect option is disabled for the call. Setting the value to zero disables the timeout.

t38_udptl_nat

When enabled the UDPTL stack will send UDPTL packets to the source address of received packets.

t38_udptl_ipv6

When enabled the UDPTL stack will use IPv6.

t38_bind_udptl_to_media_address

If media_address is specified, this option causes the UDPTL instance to be bound to the specified ip address which causes the packets to be sent from that address.

record_on_feature

When an INFO request for one-touch recording arrives with a Record header set to "on", this feature will be enabled for the channel. The feature designated here can be any built-in or dynamic feature defined in features.conf.

This setting has no effect if the endpoint's one_touch_recording option is disabled

record_off_feature

When an INFO request for one-touch recording arrives with a Record header set to "off", this feature will be enabled for the channel. The feature designated here can be any built-in or dynamic feature defined in features.conf.

This setting has no effect if the endpoint's one_touch_recording option is disabled

tos_audio

See https://wiki.asterisk.org/wiki/display/AST/IP+Quality+of+Service for more information about QoS settings

tos_video

See https://wiki.asterisk.org/wiki/display/AST/IP+Quality+of+Service for more information about QoS settings

cos_audio

See https://wiki.asterisk.org/wiki/display/AST/IP+Quality+of+Service for more information about QoS settings

cos_video

See https://wiki.asterisk.org/wiki/display/AST/IP+Quality+of+Service for more information about QoS settings

dtls_verify

This option only applies if media_encryption is set to dtls.

It can be one of the following values:

dtls_rekey

This option only applies if media_encryption is set to dtls.

If this is not set or the value provided is 0 rekeying will be disabled.

dtls_auto_generate_cert

If enabled, Asterisk will generate an X.509 certificate for each DTLS session. This option only applies if media_encryption is set to dtls. This option will be automatically enabled if webrtc is enabled and dtls_cert_file is not specified.

dtls_cert_file

This option only applies if media_encryption is set to dtls.

dtls_private_key

This option only applies if media_encryption is set to dtls.

dtls_cipher

This option only applies if media_encryption is set to dtls.

Many options for acceptable ciphers. See link for more:

http://www.openssl.org/docs/apps/ciphers.html#CIPHER\_STRINGS

dtls_ca_file

This option only applies if media_encryption is set to dtls.

dtls_ca_path

This option only applies if media_encryption is set to dtls.

dtls_setup

This option only applies if media_encryption is set to dtls.

dtls_fingerprint

This option only applies if media_encryption is set to dtls.

srtp_tag_32

This option only applies if media_encryption is set to sdes or dtls.

set_var

When a new channel is created using the endpoint set the specified variable(s) on that channel. For multiple channel variables specify multiple 'set_var'(s).

message_context

If specified, incoming MESSAGE requests will be routed to the indicated dialplan context. If no message_context is specified, then the context setting is used.

accountcode

If specified, any channel created for this endpoint will automatically have this accountcode set on it.

preferred_codec_only

Respond to a SIP invite with the single most preferred codec rather than advertising all joint codec capabilities. This limits the other side's codec choice to exactly what we prefer.

Warning

Icon

This option has been deprecated in favor of incoming_call_offer_pref. Setting both options is unsupported.

incoming_call_offer_pref

Based on this setting, a joint list of preferred codecs between those received in an incoming SDP offer (remote), and those specified in the endpoint's "allow" parameter (local) es created and is passed to the Asterisk core.

This list will consist of only those codecs found in both lists.

outgoing_call_offer_pref

Based on this setting, a joint list of preferred codecs between those received from the Asterisk core (remote), and those specified in the endpoint's "allow" parameter (local) is created and is used to create the outgoing SDP offer.

rtp_keepalive

At the specified interval, Asterisk will send an RTP comfort noise frame. This may be useful for situations where Asterisk is behind a NAT or firewall and must keep a hole open in order to allow for media to arrive at Asterisk.

rtp_timeout

This option configures the number of seconds without RTP (while off hold) before considering a channel as dead. When the number of seconds is reached the underlying channel is hung up. By default this option is set to 0, which means do not check.

rtp_timeout_hold

This option configures the number of seconds without RTP (while on hold) before considering a channel as dead. When the number of seconds is reached the underlying channel is hung up. By default this option is set to 0, which means do not check.

acl

This matches sections configured in acl.conf. The value is defined as a list of comma-delimited section names.

deny

The value is a comma-delimited list of IP addresses. IP addresses may have a subnet mask appended. The subnet mask may be written in either CIDR or dotted-decimal notation. Separate the IP address and subnet mask with a slash ('/')

permit

The value is a comma-delimited list of IP addresses. IP addresses may have a subnet mask appended. The subnet mask may be written in either CIDR or dotted-decimal notation. Separate the IP address and subnet mask with a slash ('/')

contact_acl

This matches sections configured in acl.conf. The value is defined as a list of comma-delimited section names.

contact_deny

The value is a comma-delimited list of IP addresses. IP addresses may have a subnet mask appended. The subnet mask may be written in either CIDR or dotted-decimal notation. Separate the IP address and subnet mask with a slash ('/')

contact_permit

The value is a comma-delimited list of IP addresses. IP addresses may have a subnet mask appended. The subnet mask may be written in either CIDR or dotted-decimal notation. Separate the IP address and subnet mask with a slash ('/')

subscribe_context

If specified, incoming SUBSCRIBE requests will be searched for the matching extension in the indicated context. If no subscribe_context is specified, then the context setting is used.

contact_user

On outbound requests, force the user portion of the Contact header to this value.

asymmetric_rtp_codec

When set to "yes" the codec in use for sending will be allowed to differ from that of the received one. PJSIP will not automatically switch the sending one to the receiving one.

rtcp_mux

With this option enabled, Asterisk will attempt to negotiate the use of the "rtcp-mux" attribute on all media streams. This will result in RTP and RTCP being sent and received on the same port. This shifts the demultiplexing logic to the application rather than the transport layer. This option is useful when interoperating with WebRTC endpoints since they mandate this option's use.

refer_blind_progress

Some SIP phones (Mitel/Aastra, Snom) expect a sip/frag "200 OK" after REFER has been accepted. If set to no then asterisk will not send the progress details, but immediately will send "200 OK".

notify_early_inuse_ringing

Control whether dialog-info subscriptions get 'early' state on Ringing when already INUSE.

max_audio_streams

This option enforces a limit on the maximum simultaneous negotiated audio streams allowed for the endpoint.

max_video_streams

This option enforces a limit on the maximum simultaneous negotiated video streams allowed for the endpoint.

bundle

With this option enabled, Asterisk will attempt to negotiate the use of bundle. If negotiated this will result in multiple RTP streams being carried over the same underlying transport. Note that enabling bundle will also enable the rtcp_mux option.

webrtc

When set to "yes" this also enables the following values that are needed in order for basic WebRTC support to work: rtcp_mux, use_avpf, ice_support, and use_received_transport. The following configuration settings also get defaulted as follows:

media_encryption=dtls

dtls_auto_generate_cert=yes (if dtls_cert_file is not set)

dtls_verify=fingerprint

dtls_setup=actpass

incoming_mwi_mailbox

If an MWI NOTIFY is received from this endpoint, this mailbox will be used when notifying other modules of MWI status changes. If not set, incoming MWI NOTIFYs are ignored.

follow_early_media_fork

On outgoing calls, if the UAS responds with different SDP attributes on subsequent 18X or 2XX responses (such as a port update) AND the To tag on the subsequent response is different than that on the previous one, follow it. This usually happens when the INVITE is forked to multiple UASs and more than one sends an SDP answer.

This option must also be enabled in the system section for it to take effect here.

accept_multiple_sdp_answers

On outgoing calls, if the UAS responds with different SDP attributes on non-100rel 18X or 2XX responses (such as a port update) AND the To tag on the subsequent response is the same as that on the previous one, process the updated SDP. This can happen when the UAS needs to change ports for some reason such as using a separate port for custom ringback.

This option must also be enabled in the system section for it to take effect here.

suppress_q850_reason_headers

Some devices can't accept multiple Reason headers and get confused when both 'SIP' and 'Q.850' Reason headers are received. This option allows the 'Q.850' Reason header to be suppressed.

ignore_183_without_sdp

Certain SS7 internetworking scenarios can result in a 183 to be generated for reasons other than early media. Forwarding this 183 can cause loss of ringback tone. This flag emulates the behavior of chan_sip and prevents these 183 responses from being forwarded.

stir_shaken

Enable STIR/SHAKEN support on this endpoint. On incoming INVITEs, the Identity header will be checked for validity. On outgoing INVITEs, an Identity header will be added.

stir_shaken_profile

A STIR/SHAKEN profile that is defined in stir_shaken.conf. Contains several options and rules used for STIR/SHAKEN.

allow_unauthenticated_options

RFC 3261 says that the response to an OPTIONS request MUST be the same had the request been an INVITE. Some UAs use OPTIONS requests like a 'ping' and the expectation is that they will return a 200 OK.

Enabling allow_unauthenticated_options will skip authentication of OPTIONS requests for the given endpoint.

There are security implications to enabling this setting as it can allow information disclosure to occur - specifically, if enabled, an external party could enumerate and find the endpoint name by sending OPTIONS requests and examining the responses.

security_negotiation

security_mechanisms

This is a comma-delimited list of security mechanisms to use. Each security mechanism must be in the form defined by RFC 3329 section 2.2.

geoloc_incoming_call_profile

This geolocation profile will be applied to all calls received by the channel driver from the remote endpoint before they're forwarded to the dialplan.

geoloc_outgoing_call_profile

This geolocation profile will be applied to all calls received by the channel driver from the dialplan before they're forwarded the remote endpoint.

auth

Authentication type

Configuration Option Reference

Option Name

Type

Default Value

Regular Expression

Description

auth_type

Custom

userpass

false

Authentication type

nonce_lifetime

Unsigned Integer

32

false

Lifetime of a nonce associated with this authentication config.

md5_cred

String

 

false

MD5 Hash used for authentication.

password

String

 

false

Plain text password used for authentication.

refresh_token

String

 

false

OAuth 2.0 refresh token

oauth_clientid

String

 

false

OAuth 2.0 application's client id

oauth_secret

String

 

false

OAuth 2.0 application's secret

realm

String

 

false

SIP realm for endpoint

type

None

 

false

Must be 'auth'

username

String

 

false

Username to use for account

Configuration Option Descriptions

auth_type

This option specifies which of the password style config options should be read when trying to authenticate an endpoint inbound request. If set to userpass then we'll read from the 'password' option. For md5 we'll read from 'md5_cred'. If set to google_oauth then we'll read from the refresh_token/oauth_clientid/oauth_secret fields. The following values are valid:

This setting only describes whether the password is in plain text or has been pre-hashed with MD5. It doesn't describe the acceptable digest algorithms we'll accept in a received challenge.

md5_cred

Only used when auth_type is md5. As an alternative to specifying a plain text password, you can hash the username, realm and password together one time and place the hash value here. The input to the hash function must be in the following format:

<username>:<realm>:<password>

For incoming authentication (asterisk is the server), the realm must match either the realm set in this object or the default_realm set in in the global object.

For outgoing authentication (asterisk is the UAC), the realm must match what the server will be sending in their WWW-Authenticate header. It can't be blank unless you expect the server to be sending a blank realm in the header. You can't use pre-hashed passwords with a wildcard auth object. You can generate the hash with the following shell command:

$ echo -n "myname:myrealm:mypassword" | md5sum

Note the '-n'. You don't want a newline to be part of the hash.

password

Only used when auth_type is userpass.

realm

For incoming authentication (asterisk is the UAS), this is the realm to be sent on WWW-Authenticate headers. If not specified, the global object's default_realm will be used.

For outgoing authentication (asterisk is the UAC), this must either be the realm the server is expected to send, or left blank or contain a single '*' to automatically use the realm sent by the server. If you have multiple auth objects for an endpoint, the realm is also used to match the auth object to the realm the server sent.

Using the same auth section for inbound and outbound authentication is not recommended. There is a difference in meaning for an empty realm setting between inbound and outbound authentication uses.

If more than one auth object with the same realm or more than one wildcard auth object associated to an endpoint, we can only use the first one of each defined on the endpoint.

domain_alias

Domain Alias

Configuration Option Reference

Option Name

Type

Default Value

Regular Expression

Description

type

None

 

false

Must be of type 'domain_alias'.

domain

String

 

false

Domain to be aliased

transport

SIP Transport

Configuration Option Reference

Option Name

Type

Default Value

Regular Expression

Description

async_operations

Unsigned Integer

1

false

Number of simultaneous Asynchronous Operations, can no longer be set, always set to 1

bind

Custom

 

false

IP Address and optional port to bind to for this transport

ca_list_file

Custom

 

false

File containing a list of certificates to read (TLS ONLY, not WSS)

ca_list_path

Custom

 

false

Path to directory containing a list of certificates to read (TLS ONLY, not WSS)

cert_file

Custom

 

false

Certificate file for endpoint (TLS ONLY, not WSS)

cipher

Custom

 

false

Preferred cryptography cipher names (TLS ONLY, not WSS)

domain

String

 

false

Domain the transport comes from

external_media_address

String

 

false

External IP address to use in RTP handling

external_signaling_address

String

 

false

External address for SIP signalling

external_signaling_port

Unsigned Integer

0

false

External port for SIP signalling

method

Custom

 

false

Method of SSL transport (TLS ONLY, not WSS)

local_net

Custom

 

false

Network to consider local (used for NAT purposes).

password

String

 

false

Password required for transport

priv_key_file

Custom

 

false

Private key file (TLS ONLY, not WSS)

protocol

Custom

udp

false

Protocol to use for SIP traffic

require_client_cert

Custom

 

false

Require client certificate (TLS ONLY, not WSS)

type

Custom

 

false

Must be of type 'transport'.

verify_client

Custom

 

false

Require verification of client certificate (TLS ONLY, not WSS)

verify_server

Custom

 

false

Require verification of server certificate (TLS ONLY, not WSS)

tos

Custom

0

false

Enable TOS for the signalling sent over this transport

cos

Unsigned Integer

0

false

Enable COS for the signalling sent over this transport

websocket_write_timeout

Integer

100

false

The timeout (in milliseconds) to set on WebSocket connections.

allow_reload

Boolean

no

false

Allow this transport to be reloaded.

allow_wildcard_certs

Custom

 

false

Allow use of wildcards in certificates (TLS ONLY)

symmetric_transport

Boolean

no

false

Use the same transport for outgoing requests as incoming ones.

Configuration Option Descriptions

cert_file

A path to a .crt or .pem file can be provided. However, only the certificate is read from the file, not the private key. The priv_key_file option must supply a matching key file. The certificate file can be reloaded if the filename in configuration remains unchanged.

cipher

Comma separated list of cipher names or numeric equivalents. Numeric equivalents can be either decimal or hexadecimal (0xX).

There are many cipher names. Use the CLI command pjsip list ciphers to see a list of cipher names available for your installation. See link for more:

http://www.openssl.org/docs/apps/ciphers.html#CIPHER\_SUITE\_NAMES

external_media_address

When a request or response is sent out, if the destination of the message is outside the IP network defined in the option localnet, and the media address in the SDP is within the localnet network, then the media address in the SDP will be rewritten to the value defined for external_media_address.

method

local_net

This must be in CIDR or dotted decimal format with the IP and mask separated with a slash ('/').

priv_key_file

A path to a key file can be provided. The private key file can be reloaded if the filename in configuration remains unchanged.

protocol

tos

See https://wiki.asterisk.org/wiki/display/AST/IP+Quality+of+Service for more information on this parameter.

This option does not apply to the ws or the wss protocols.

cos

See https://wiki.asterisk.org/wiki/display/AST/IP+Quality+of+Service for more information on this parameter.

This option does not apply to the ws or the wss protocols.

websocket_write_timeout

If a websocket connection accepts input slowly, the timeout for writes to it can be increased to keep it from being disconnected. Value is in milliseconds.

allow_reload

Allow this transport to be reloaded when res_pjsip is reloaded. This option defaults to "no" because reloading a transport may disrupt in-progress calls.

allow_wildcard_certs

In combination with verify_server, when enabled allow use of wildcards, i.e. '.' in certs for common,and subject alt names of type DNS for TLS transport types. Names must start with the wildcard. Partial wildcards, e.g. 'f.example.com' and 'foo..com' are not allowed. As well, names only match against a single level meaning '.example.com' matches 'foo.example.com', but not 'foo.bar.example.com'.

symmetric_transport

When a request from a dynamic contact comes in on a transport with this option set to 'yes', the transport name will be saved and used for subsequent outgoing requests like OPTIONS, NOTIFY and INVITE. It's saved as a contact uri parameter named 'x-ast-txp' and will display with the contact uri in CLI, AMI, and ARI output. On the outgoing request, if a transport wasn't explicitly set on the endpoint AND the request URI is not a hostname, the saved transport will be used and the 'x-ast-txp' parameter stripped from the outgoing packet.

contact

A way of creating an aliased name to a SIP URI

Configuration Option Reference

Option Name

Type

Default Value

Regular Expression

Description

type

None

 

false

Must be of type 'contact'.

uri

String

 

false

SIP URI to contact peer

expiration_time

Custom

 

false

Time to keep alive a contact

qualify_frequency

Unsigned Integer

0

false

Interval at which to qualify a contact

qualify_timeout

Double

3.0

false

Timeout for qualify

authenticate_qualify

Boolean

no

false

Authenticates a qualify challenge response if needed

outbound_proxy

String

 

false

Outbound proxy used when sending OPTIONS request

path

String

 

false

Stored Path vector for use in Route headers on outgoing requests.

user_agent

String

 

false

User-Agent header from registration.

endpoint

String

 

false

Endpoint name

reg_server

String

 

false

Asterisk Server name

via_addr

String

 

false

IP-address of the last Via header from registration.

via_port

Unsigned Integer

0

false

IP-port of the last Via header from registration.

call_id

String

 

false

Call-ID header from registration.

prune_on_boot

Boolean

no

false

A contact that cannot survive a restart/boot.

Configuration Option Descriptions

expiration_time

Time to keep alive a contact. String style specification.

qualify_frequency

Interval between attempts to qualify the contact for reachability. If 0 never qualify. Time in seconds.

qualify_timeout

If the contact doesn't respond to the OPTIONS request before the timeout, the contact is marked unavailable. If 0 no timeout. Time in fractional seconds.

authenticate_qualify

If true and a qualify request receives a challenge response then authentication is attempted before declaring the contact available.

This option does nothing as we will always complete the challenge response authentication if the qualify request is challenged.

outbound_proxy

If set the provided URI will be used as the outbound proxy when an OPTIONS request is sent to a contact for qualify purposes.

user_agent

The User-Agent is automatically stored based on data present in incoming SIP REGISTER requests and is not intended to be configured manually.

endpoint

The name of the endpoint this contact belongs to

reg_server

Asterisk Server name on which SIP endpoint registered.

via_addr

The last Via header should contain the address of UA which sent the request. The IP-address of the last Via header is automatically stored based on data present in incoming SIP REGISTER requests and is not intended to be configured manually.

via_port

The IP-port of the last Via header is automatically stored based on data present in incoming SIP REGISTER requests and is not intended to be configured manually.

call_id

The Call-ID header is automatically stored based on data present in incoming SIP REGISTER requests and is not intended to be configured manually.

prune_on_boot

The option is set if the incoming SIP REGISTER contact is rewritten on a reliable transport and is not intended to be configured manually.

aor

The configuration for a location of an endpoint

Configuration Option Reference

Option Name

Type

Default Value

Regular Expression

Description

contact

Custom

 

false

Permanent contacts assigned to AoR

default_expiration

Unsigned Integer

3600

false

Default expiration time in seconds for contacts that are dynamically bound to an AoR.

mailboxes

String

 

false

Allow subscriptions for the specified mailbox(es)

voicemail_extension

Custom

 

false

The voicemail extension to send in the NOTIFY Message-Account header

maximum_expiration

Unsigned Integer

7200

false

Maximum time to keep an AoR

max_contacts

Unsigned Integer

0

false

Maximum number of contacts that can bind to an AoR

minimum_expiration

Unsigned Integer

60

false

Minimum keep alive time for an AoR

remove_existing

Boolean

no

false

Determines whether new contacts replace existing ones.

remove_unavailable

Boolean

no

false

Determines whether new contacts should replace unavailable ones.

type

None

 

false

Must be of type 'aor'.

qualify_frequency

Unsigned Integer

0

false

Interval at which to qualify an AoR

qualify_timeout

Double

3.0

false

Timeout for qualify

authenticate_qualify

Boolean

no

false

Authenticates a qualify challenge response if needed

outbound_proxy

String

 

false

Outbound proxy used when sending OPTIONS request

support_path

Boolean

no

false

Enables Path support for REGISTER requests and Route support for other requests.

Configuration Option Descriptions

contact

Contacts specified will be called whenever referenced by chan_pjsip.

Use a separate "contact=" entry for each contact required. Contacts are specified using a SIP URI.

mailboxes

This option applies when an external entity subscribes to an AoR for Message Waiting Indications. The mailboxes specified will be subscribed to. More than one mailbox can be specified with a comma-delimited string. app_voicemail mailboxes must be specified as [email protected]; for example: [email protected] For mailboxes provided by external sources, such as through the res_mwi_external module, you must specify strings supported by the external system.

For endpoints that cannot SUBSCRIBE for MWI, you can set the mailboxes option in your endpoint configuration section to enable unsolicited MWI NOTIFYs to the endpoint.

maximum_expiration

Maximum time to keep a peer with explicit expiration. Time in seconds.

max_contacts

Maximum number of contacts that can associate with this AoR. This value does not affect the number of contacts that can be added with the "contact" option. It only limits contacts added through external interaction, such as registration.

The rewrite_contact option registers the source address as the contact address to help with NAT and reusing connection oriented transports such as TCP and TLS. Unfortunately, refreshing a registration may register a different contact address and exceed max_contacts. The remove_existing and remove_unavailable options can help by removing either the soonest to expire or unavailable contact(s) over max_contacts which is likely the old rewrite_contact contact source address being refreshed.

This should be set to 1 and remove_existing set to yes if you wish to stick with the older chan_sip behaviour.

minimum_expiration

Minimum time to keep a peer with an explicit expiration. Time in seconds.

remove_existing

On receiving a new registration to the AoR should it remove enough existing contacts not added or updated by the registration to satisfy max_contacts? Any removed contacts will expire the soonest.

The rewrite_contact option registers the source address as the contact address to help with NAT and reusing connection oriented transports such as TCP and TLS. Unfortunately, refreshing a registration may register a different contact address and exceed max_contacts. The remove_existing option can help by removing the soonest to expire contact(s) over max_contacts which is likely the old rewrite_contact contact source address being refreshed.

This should be set to yes and max_contacts set to 1 if you wish to stick with the older chan_sip behaviour.

remove_unavailable

The effect of this setting depends on the setting of remove_existing.

If remove_existing is set to no (default), setting remove_unavailable to yes will remove only unavailable contacts that exceed _max_contacts_to allow an incoming REGISTER to complete sucessfully.

If remove_existing is set to yes, setting remove_unavailable to yes will prioritize unavailable contacts for removal instead of just removing the contact that expires the soonest.

See remove_existing and max_contacts for further information about how these 3 settings interact.

qualify_frequency

Interval between attempts to qualify the AoR for reachability. If 0 never qualify. Time in seconds.

qualify_timeout

If the contact doesn't respond to the OPTIONS request before the timeout, the contact is marked unavailable. If 0 no timeout. Time in fractional seconds.

authenticate_qualify

If true and a qualify request receives a challenge response then authentication is attempted before declaring the contact available.

This option does nothing as we will always complete the challenge response authentication if the qualify request is challenged.

outbound_proxy

If set the provided URI will be used as the outbound proxy when an OPTIONS request is sent to a contact for qualify purposes.

support_path

When this option is enabled, the Path headers in register requests will be saved and its contents will be used in Route headers for outbound out-of-dialog requests and in Path headers for outbound 200 responses. Path support will also be indicated in the Supported header.

system

Options that apply to the SIP stack as well as other system-wide settings

Configuration Option Reference

Option Name

Type

Default Value

Regular Expression

Description

timer_t1

Unsigned Integer

500

false

Set transaction timer T1 value (milliseconds).

timer_b

Unsigned Integer

32000

false

Set transaction timer B value (milliseconds).

compact_headers

Boolean

no

false

Use the short forms of common SIP header names.

threadpool_initial_size

Unsigned Integer

0

false

Initial number of threads in the res_pjsip threadpool.

threadpool_auto_increment

Unsigned Integer

5

false

The amount by which the number of threads is incremented when necessary.

threadpool_idle_timeout

Unsigned Integer

60

false

Number of seconds before an idle thread should be disposed of.

threadpool_max_size

Unsigned Integer

50

false

Maximum number of threads in the res_pjsip threadpool. A value of 0 indicates no maximum.

disable_tcp_switch

Boolean

yes

false

Disable automatic switching from UDP to TCP transports.

follow_early_media_fork

Boolean

yes

false

Follow SDP forked media when To tag is different

accept_multiple_sdp_answers

Boolean

no

false

Follow SDP forked media when To tag is the same

disable_rport

Boolean

no

false

Disable the use of rport in outgoing requests.

type

None

 

false

Must be of type 'system' UNLESS the object name is 'system'.

Configuration Option Descriptions

timer_t1

Timer T1 is the base for determining how long to wait before retransmitting requests that receive no response when using an unreliable transport (e.g. UDP). For more information on this timer, see RFC 3261, Section 17.1.1.1.

timer_b

Timer B determines the maximum amount of time to wait after sending an INVITE request before terminating the transaction. It is recommended that this be set to 64 * Timer T1, but it may be set higher if desired. For more information on this timer, see RFC 3261, Section 17.1.1.1.

disable_tcp_switch

Disable automatic switching from UDP to TCP transports if outgoing request is too large. See RFC 3261 section 18.1.1.

follow_early_media_fork

On outgoing calls, if the UAS responds with different SDP attributes on subsequent 18X or 2XX responses (such as a port update) AND the To tag on the subsequent response is different than that on the previous one, follow it.

This option must also be enabled on endpoints that require this functionality.

accept_multiple_sdp_answers

On outgoing calls, if the UAS responds with different SDP attributes on non-100rel 18X or 2XX responses (such as a port update) AND the To tag on the subsequent response is the same as that on the previous one, process the updated SDP.

This option must also be enabled on endpoints that require this functionality.

disable_rport

Remove "rport" parameter from the outgoing requests.

global

Options that apply globally to all SIP communications

Configuration Option Reference

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

90

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' UNLESS the object name is 'global'.

user_agent

String

Asterisk PBX GIT-20-96d9ad5

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 a challenge, the digest realm 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.

ignore_uri_user_options

Boolean

no

false

Enable/Disable ignoring SIP URI user field options.

use_callerid_contact

Boolean

no

false

Place caller-id information into Contact header

send_contact_status_on_update_registration

Boolean

no

false

Enable sending AMI ContactStatus event when a device refreshes its registration.

taskprocessor_overload_trigger

Custom

global

false

Trigger scope for taskprocessor overloads

norefersub

Boolean

yes

false

Advertise support for RFC4488 REFER subscription suppression

allow_sending_180_after_183

Boolean

no

false

Allow 180 after 183

all_codecs_on_empty_reinvite

Boolean

no

false

If we should return all codecs on re-INVITE without SDP

Configuration Option Descriptions

disable_multi_domain

If disabled it can improve realtime performance by reducing the number of database requests.

unidentified_request_period

If unidentified_request_count unidentified requests are received during unidentified_request_period, a security event will be generated.

unidentified_request_count

If unidentified_request_count unidentified requests are received during unidentified_request_period, a security event will be generated.

endpoint_identifier_order

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.

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.

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.

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

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.

ignore_uri_user_options

If you have this option enabled and there are semicolons in the user field of a SIP URI then the field is truncated at the first semicolon. This effectively makes the semicolon a non-usable character for PJSIP endpoint names, extensions, and AORs. This can be useful for improving compatibility with an ITSP that likes to use user options for whatever reason.

Example: Sample SIP URI
Example: Sample SIP URI user field
Example: Sample SIP URI user field truncated

The caller-id and redirecting number strings obtained from incoming SIP URI user fields are always truncated at the first semicolon.

use_callerid_contact

This option will cause Asterisk to place caller-id information into generated Contact headers.

taskprocessor_overload_trigger

This option specifies the trigger the distributor will use for detecting taskprocessor overloads. When it detects an overload condition, the distrubutor will stop accepting new requests until the overload is cleared.

allow_sending_180_after_183

Allow Asterisk to send 180 Ringing to an endpoint after 183 Session Progress has been send. If disabled Asterisk will instead send only a 183 Session Progress to the endpoint. (default: "no")

all_codecs_on_empty_reinvite

On reception of a re-INVITE without SDP Asterisk will send an SDP offer in the 200 OK response containing all configured codecs on the endpoint, instead of simply those that have already been negotiated. RFC 3261 specifies this as a SHOULD requirement.

Import Version

This documentation was imported from Asterisk Version GIT-20-96d9ad5