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
`allow_overlap`	`Boolean`	`yes`	`false`	Enable RFC3578 overlap dialing support.
`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_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
`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 user 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_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.
`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
`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

Configuration Option Descriptions

100rel

no
required
yes

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.

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.

Note

Icon

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

allowed_not_screened
allowed_passed_screen
allowed_failed_screen
allowed
prohib_not_screened
prohib_passed_screen
prohib_failed_screen
prohib
unavailable

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

none
outgoing
incoming

direct_media_method

Method for setting up Direct Media between endpoints.

invite
reinvite - Alias for the invite value.
update

connected_line_method

Method used when updating connected line information.

invite - When set to invite, check the remote's Allow header and if UPDATE is allowed, send UPDATE instead of INVITE to avoid SDP renegotiation. If UPDATE is not Allowed, send INVITE.
reinvite - Alias for the invite value.
update - If set to update, send UPDATE regardless of what the remote Allows.

dtmf_mode

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

rfc4733 - DTMF is sent out of band of the main audio stream. This supercedes the older RFC-2833 used within the older chan_sip.
inband - DTMF is sent as part of audio stream.
info - DTMF is sent as SIP INFO packets.
auto - DTMF is sent as RFC 4733 if the other side supports it or as INBAND if not.
auto_info - DTMF is sent as RFC 4733 if the other side supports it or as SIP INFO if not.

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.

Note

Icon

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.

Note

Icon

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.

username - Matches the endpoint or AOR ID based on the username and domain in the From header (or To header for AORs). If an exact match on both username and domain/realm fails, the match is retried with just the username.
auth_username - Matches the endpoint or AOR ID based on the username and realm in the Authentication header. If an exact match on both username and domain/realm fails, the match is retried with just the username.

Note
Icon

This method of identification 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 this method 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 in the "global" configuration object.
ip - Matches the endpoint based on the source IP address.
This method of identification is not configured here but simply allowed by this configuration option. See the documentation for the identify configuration section for more details on this method of endpoint identification.
header - Matches the endpoint based on a configured SIP header value.
This method of identification is not configured here but simply allowed by this configuration option. See the documentation for the identify configuration section for more details on this method of endpoint identification.

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.

user
uri_core
uri_pjsip

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.

Note

Icon

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

no
yes
required
always
forced - Alias of always

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.

Note

Icon

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

no - res_pjsip will offer no encryption and allow no encryption to be setup.
sdes - res_pjsip will offer standard SRTP setup via in-SDP keys. Encrypted SIP transport should be used in conjunction with this option to prevent exposure of media encryption keys.
dtls - res_pjsip will offer DTLS-SRTP setup.

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

none - No error correction should be used.
fec - Forward error correction should be used.
redundancy - Redundancy error correction should be used.

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.

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.

Note

Icon

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.

Note

Icon

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