res_pjsip_outbound_registration

Outbound Registration

This module allows res_pjsip to register to other SIP servers.

pjsip.conf

[registration]

The configuration for outbound registration

• auth_rejection_permanent - Determines whether failed authentication challenges are treated as permanent failures.
• client_uri - Client SIP URI used when attemping outbound registration
• contact_user - Contact User to use in request. If this value is not set, this defaults to 's'
• contact_header_params - Header parameters to place in the Contact header
• expiration - Expiration time for registrations in seconds
• max_retries - Maximum number of registration attempts.
• security_negotiation - The kind of security agreement negotiation to use. Currently, only mediasec is supported.
• security_mechanisms - List of security mechanisms supported.

• outbound_auth - Authentication object(s) to be used for outbound registrations.

  Note

  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.

• outbound_proxy - Full SIP URI of the outbound proxy used to send registrations

• max_random_initial_delay - Maximum interval in seconds for which an initial registration may be randomly delayed
• retry_interval - Interval in seconds between retries if outbound registration is unsuccessful
• forbidden_retry_interval - Interval used when receiving a 403 Forbidden response.

• fatal_retry_interval - Interval used when receiving a Fatal response.

  Note

  if also set the forbidden_retry_interval takes precedence over this one when a 403 is received. Also, if auth_rejection_permanent equals 'yes' then a 401 and 407 become subject to this retry interval.

• server_uri - SIP URI of the server to register against

• transport - Transport used for outbound authentication

  Note

  A transport configured in pjsip.conf. As with other res_pjsip modules, this will use the first available transport of the appropriate type if unconfigured.

• line - Whether to add a 'line' parameter to the Contact for inbound call matching

• endpoint - Endpoint to use for incoming related calls
• type - Must be of type 'registration'.
• support_path - Enables advertising SIP Path support for outbound REGISTER requests.
• support_outbound - Enables advertising SIP Outbound support (RFC5626) for outbound REGISTER requests.
• user_agent - Overrides the User-Agent header that should be used for outbound REGISTER requests.