Skip to end of metadata
Go to start of metadata

SIP resource for outbound publish

This configuration documentation is for functionality provided by res_pjsip_outbound_publish.

Overview

Outbound Publish

This module allows res_pjsip to publish to other SIP servers.

pjsip.conf

outbound-publish

The configuration for outbound publish

Configuration Option Reference

Option Name

Type

Default Value

Regular Expression

Description

expiration

 

3600

 

Expiration time for publications in seconds

outbound_auth

 

 

 

Authentication object(s) to be used for outbound publishes.

outbound_proxy

 

 

 

Full SIP URI of the outbound proxy used to send publishes

server_uri

 

 

 

SIP URI of the server and entity to publish to

from_uri

 

 

 

SIP URI to use in the From header

to_uri

 

 

 

SIP URI to use in the To header

event

 

 

 

Event type of the PUBLISH.

max_auth_attempts

 

5

 

Maximum number of authentication attempts before stopping the publication.

transport

 

 

 

Transport used for outbound publish

multi_user

 

no

 

Enable multi-user support

type

 

 

 

Must be of type 'outbound-publish'.

Configuration Option Descriptions

outbound_auth

This is a comma-delimited list of auth sections defined in pjsip.conf used to respond to outbound 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.

server_uri

This is the URI at which to find the entity and server to send the outbound PUBLISH to. This URI is used as the request URI of the outbound PUBLISH request from Asterisk.

from_uri

This is the URI that will be placed into the From header of outgoing PUBLISH messages. If no URI is specified then the URI provided in server_uri will be used.

to_uri

This is the URI that will be placed into the To header of outgoing PUBLISH messages. If no URI is specified then the URI provided in server_uri will be used.

transport

Note

Icon

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.

multi_user

When enabled the user portion of the server uri is replaced by a dynamically created user

Import Version

This documentation was imported from Asterisk Version GIT-14-4349eda

  • No labels