[asterisk-commits] jrose: branch 1.8 r412821 - /branches/1.8/CHANGES

[SVN commits to the Asterisk project]

Author: jrose
Date: Mon Apr 21 12:51:49 2014
New Revision: 412821

URL: http://svnview.digium.com/svn/asterisk?view=rev&rev=412821
Log:
chan_sip: trust_id_outbound CHANGES message improvement

(closes issue AST-1301)

(closes issue ASTERISK-19465)
Reported by: Krzysztof Chmielewski

Modified:
    branches/1.8/CHANGES

Modified: branches/1.8/CHANGES
URL: http://svnview.digium.com/svn/asterisk/branches/1.8/CHANGES?view=diff&rev=412821&r1=412820&r2=412821
==============================================================================
--- branches/1.8/CHANGES (original)
+++ branches/1.8/CHANGES Mon Apr 21 12:51:49 2014
@@ -17,17 +17,19 @@
  * SIP peers can now specify 'trust_id_outbound' which affects RPID/PAI
    fields for prohibited callingpres information. Values are legacy, no, and
    yes. By default, legacy is used.
-   trust_id_outbound=legacy: behavior remains the same as 1.8.26.1 - When
-   dealing with prohibited callingpres, RPID/PAI headers are created for both
-   sendrpid=pai and sendrpid=rpid are appended, but the data is anonymized.
-   When sendrpid=rpid, only the remote party's domain is anonymized.
-   trust_id_outbound=no: when dealing with prohibited callingpres, RPID/PAI
-   headers are not sent.
-   trust_id_outbound=yes: RPID/PAI headers are applied with the full
-   remote party information in tact even for prohibited callingpres
-   information. In the case of PAI, a Privacy: id header will be appended for
-   prohibited calling information to communicate that the private information
-   should not be relayed to untrusted parties.
+   trust_id_outbound=legacy - behavior remains the same as 1.8.26.1. When
+     dealing with prohibited callingpres and sendrpid=pai/rpid, RPID/PAI
+     headers are appended to outbound SIP messages just as they are with
+     allowed callingpres values, but data about the remote party's identity is
+     anonymized.
+     When sendrpid=rpid, only the remote party's domain is anonymized.
+   trust_id_outbound=no - when dealing with prohibited callingpres, RPID/PAI
+     headers are not sent.
+   trust_id_outbound=yes - RPID/PAI headers are applied with the full remote
+     party information in tact even for prohibited callingpres information.
+     In the case of PAI, a Privacy: id header will be appended for prohibited
+     calling information to communicate that the private information should
+     not be relayed to untrusted parties.
 
 ------------------------------------------------------------------------------
 --- Functionality changes since Asterisk 1.8.19.1 ----------------------------