From: Richard Mudgett Date: Thu, 19 Jul 2018 21:17:50 +0000 (-0500) Subject: res_pjsip: Update endpoint transport option documentation. X-Git-Tag: 13.23.0-rc1~63^2 X-Git-Url: http://git.ipfire.org/cgi-bin/gitweb.cgi?a=commitdiff_plain;h=0ade9df3b601f5faa00da6c047a18f7ae67c9b0b;p=thirdparty%2Fasterisk.git res_pjsip: Update endpoint transport option documentation. Change-Id: I5394fdff6a296efc8e1695a156e616acd932ae52 --- diff --git a/configs/samples/pjsip.conf.sample b/configs/samples/pjsip.conf.sample index f0dfdb5bdc..e1ccd69b03 100644 --- a/configs/samples/pjsip.conf.sample +++ b/configs/samples/pjsip.conf.sample @@ -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. ; @@ -668,7 +668,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 diff --git a/res/res_pjsip.c b/res/res_pjsip.c index e087564010..0dbfc41caf 100644 --- a/res/res_pjsip.c +++ b/res/res_pjsip.c @@ -471,14 +471,17 @@ - Desired transport configuration - - This will set the desired transport configuration to send SIP data through. + Explicit transport configuration to use + + 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. - Not specifying a transport will DEFAULT - to the first configured transport in pjsip.conf which is - valid for the URI we are trying to contact. - + Not specifying a transport will select the first + configured transport in pjsip.conf which is + compatible with the URI we are trying to contact. + Transport configuration is not affected by reloads. In order to change transports, a full Asterisk restart is required