From: Joshua Colp Date: Sat, 27 Feb 2016 16:18:26 +0000 (-0600) Subject: Merge "res_pjsip/config_transport: Allow reloading transports." X-Git-Tag: 14.0.0-beta1~379 X-Git-Url: http://git.ipfire.org/cgi-bin/gitweb.cgi?a=commitdiff_plain;h=62d98b5a7f096b39bde412bac5cb310aeb7ee068;p=thirdparty%2Fasterisk.git Merge "res_pjsip/config_transport: Allow reloading transports." --- 62d98b5a7f096b39bde412bac5cb310aeb7ee068 diff --cc CHANGES index 7b1dfb65ba,260aa2f3cf..91e170ffbb --- a/CHANGES +++ b/CHANGES @@@ -240,16 -229,15 +240,23 @@@ res_pjprojec This displays the compiled-in options of the pjproject installation Asterisk is currently running against. + * Another feature of this module is the ability to map pjproject log levels + to Asterisk log levels, or to suppress the pjproject log messages + altogether. Many of the messages emitted by pjproject itself are the result + of errors which Asterisk will ultimately handle so the messages can be + misleading or just noise. A new config file (pjproject.conf) has been added + to configure the mapping and a new CLI command (pjproject show log mappings) + has been added to display the mappings currently in use. + res_pjsip ------------------ + * Transports are now reloadable. In testing, no in-progress calls were + disrupted if the ip address or port weren't changed, but the possibility + still exists. To make sure there are no unintentional drops, a new option + 'allow_reload', which defaults to 'no' has been added to transport. If + left at the default, changes to the particular transport will be ignored. + If set to 'yes', changes (if any) will be applied. + * Added new global option (regcontext) to pjsip. When set, Asterisk will dynamically create and destroy a NoOp priority 1 extension for a given endpoint who registers or unregisters with us.