From 642a4e6f802718cd5862a72d39d09b19a23aacb4 Mon Sep 17 00:00:00 2001
From: Jonathan Rose <jrose@digium.com>
Date: Mon, 21 Apr 2014 17:53:29 +0000
Subject: [PATCH] chan_sip: trust_id_outbound CHANGES message improvement
(closes issue AST-1301)
(closes issue ASTERISK-19465)
Reported by: Krzysztof Chmielewski
........
Merged revisions 412821 from http://svn.asterisk.org/svn/asterisk/branches/1.8
git-svn-id: https://origsvn.digium.com/svn/asterisk/branches/11@412822 65c4cc65-6c06-0410-ace0-fbb531ad65f3
---
CHANGES | 24 +++++++++++++-----------
1 file changed, 13 insertions(+), 11 deletions(-)
diff --git a/CHANGES b/CHANGES
index ec0aeeee00..6fd5cee161 100644
--- a/CHANGES
+++ b/CHANGES
@@ -17,17 +17,19 @@ chan_sip
* 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 from Asterisk 10 to Asterisk 11 --------------------
--
GitLab