sysmocom
/
asterisk
11
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

res_pjsip: Update endpoint transport option documentation. 

Change-Id: I5394fdff6a296efc8e1695a156e616acd932ae52
This commit is contained in:
Richard Mudgett 2018-07-19 16:17:50 -05:00
parent 0353c34c61
commit dbffcdc561
2 changed files with 18 additions and 10 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

11
configs/samples/pjsip.conf.sample
View File

@ -288,8 +288,8 @@
; a transport that you'll need to uncomment from the previous examples.
;
; Uncomment one of the transport lines to choose which transport you want. If
; not specified then the default transport chosen is the first defined transport
; in the configuration file.
; not specified then the default transport chosen is the first compatible transport
; in the configuration file for the contact URL.
;
; Modify the "max_contacts=" line to change how many unique registrations to allow.
;
@ -670,7 +670,12 @@
;timers=yes ; Session timers for SIP packets (default: "yes")
;timers_sess_expires=1800 ; Maximum session timer expiration period
; (default: "1800")
;transport= ; Desired transport configuration (default: "")
;transport= ; Explicit transport configuration to use (default: "")
; 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.
;trust_id_inbound=no ; Accept identification information received from this
; endpoint (default: "no")
;trust_id_outbound=no ; Send private identification details to the endpoint

17
res/res_pjsip.c
View File

@ -471,14 +471,17 @@
</para></description>
</configOption>
<configOption name="transport">
<synopsis>Desired transport configuration</synopsis>
<description><para>
This will set the desired transport configuration to send SIP data through.
<synopsis>Explicit transport configuration to use</synopsis>
<description>
<para>This will <emphasis>force</emphasis> 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.
</para>
<warning><para>Not specifying a transport will <emphasis>DEFAULT</emphasis>
to the first configured transport in <filename>pjsip.conf</filename> which is
valid for the URI we are trying to contact.
</para></warning>
<note><para>Not specifying a transport will select the first
configured transport in <filename>pjsip.conf</filename> which is
compatible with the URI we are trying to contact.
</para></note>
<warning><para>Transport configuration is not affected by reloads. In order to
change transports, a full Asterisk restart is required</para></warning>
</description>