res_pjsip_outbound_registration: SIP resource for outbound registrations¶

This configuration documentation is for functionality provided by res_pjsip_outbound_registration.

Overview¶

Outbound Registration

This module allows 'res_pjsip' to register to other SIP servers.

Configuration File: pjsip.conf¶

[registration]: The configuration for outbound registration¶

Registration is COMPLETELY separate from the rest of 'pjsip.conf'. A minimal configuration consists of setting a 'server_uri'and a 'client_uri'.

Configuration Option Reference¶

Configuration Option Descriptions¶

auth_rejection_permanent¶

If this option is enabled and an authentication challenge fails, registration will not be attempted again until the configuration is reloaded.

client_uri¶

This is the address-of-record for the outbound registration (i.e. the URI in the To header of the REGISTER).

For registration with an ITSP, the client SIP URI may need to consist of an account name or number and the provider's hostname for their registrar, e.g. client_uri=1234567890@example.com. This may differ between providers.

For registration to generic registrars, the client SIP URI will depend on networking specifics and configuration of the registrar.

endpoint¶

When line support is enabled this configured endpoint name is used for incoming calls that are related to the outbound registration.

fatal_retry_interval¶

If a fatal response is received, chan_pjsip will wait fatal_retry_interval seconds before attempting registration again. If 0 is specified, chan_pjsip will not retry after receiving a fatal (non-temporary 4xx, 5xx, 6xx) response. Setting this to a non-zero value may go against a "SHOULD NOT" in RFC3261, but can be used to work around buggy registrars.

forbidden_retry_interval¶

If a 403 Forbidden is received, chan_pjsip will wait forbidden_retry_interval seconds before attempting registration again. If 0 is specified, chan_pjsip will not retry after receiving a 403 Forbidden response. Setting this to a non-zero value goes against a "SHOULD NOT" in RFC3261, but can be used to work around buggy registrars.

line¶

When enabled this option will cause a 'line' parameter to be added to the Contact header placed into the outgoing registration request. If the remote server sends a call this line parameter will be used to establish a relationship to the outbound registration, ultimately causing the configured endpoint to be used.

max_random_initial_delay¶

By default, registrations are randomly delayed by a small amount to prevent too many registrations from being made simultaneously.

Depending on your system usage, it may be desirable to set this to a smaller or larger value to have fine grained control over the size of this random delay.

max_retries¶

This sets the maximum number of registration attempts that are made before stopping any further attempts. If set to 0 then upon failure no further attempts are made.

outbound_auth¶

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

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.

security_negotiation¶

• no

• mediasec

server_uri¶

This is the URI at which to find the registrar to send the outbound REGISTER. This URI is used as the request URI of the outbound REGISTER request from Asterisk.

For registration with an ITSP, the setting may often be just the domain of the registrar, e.g. sip:sip.example.com.

support_path¶

When this option is enabled, outbound REGISTER requests will advertise support for Path headers so that intervening proxies can add to the Path header as necessary.

transport¶

Generated Version¶

This documentation was generated from Asterisk branch certified/20.7 using version GIT