Merge "res_pjsip/config_transport: Allow reloading transports." into 13

diff --cc CHANGES
index f57b1902a8fc1c465c2a23d8d90d094e7a05ce68,2f970b9c882ff807886c219b37292ee6ec1510cb..0e84678309a365255c4d37c3507b9b8822a04724
--- 1/CHANGES
--- 2/CHANGES
+++ b/CHANGES
@@@ -37,16 -31,15 +37,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.