mirror of
				https://github.com/asterisk/asterisk.git
				synced 2025-11-03 20:38:59 +00:00 
			
		
		
		
	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 ........ Merged revisions 412822 from http://svn.asterisk.org/svn/asterisk/branches/11 ........ Merged revisions 412823 from http://svn.asterisk.org/svn/asterisk/branches/12 git-svn-id: https://origsvn.digium.com/svn/asterisk/trunk@412824 65c4cc65-6c06-0410-ace0-fbb531ad65f3
This commit is contained in:
		
							
								
								
									
										24
									
								
								CHANGES
									
									
									
									
									
								
							
							
						
						
									
										24
									
								
								CHANGES
									
									
									
									
									
								
							@@ -30,17 +30,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 12.1.0 to Asterisk 12.2.0 ------------
 | 
			
		||||
 
 | 
			
		||||
		Reference in New Issue
	
	Block a user