[asterisk-bugs] [Asterisk 0013279]: Impossible to retrieve privacy info in a PRI incoming call

[Asterisk Bug Tracker]

A NOTE has been added to this issue. 
====================================================================== 
http://bugs.digium.com/view.php?id=13279 
====================================================================== 
Reported By:                ibc
Assigned To:                seanbright
====================================================================== 
Project:                    Asterisk
Issue ID:                   13279
Category:                   Channels/chan_zap
Reproducibility:            always
Severity:                   minor
Priority:                   normal
Status:                     assigned
Asterisk Version:           SVN 
SVN Branch (only for SVN checkouts, not tarball releases): N/A 
SVN Revision (number only!):  
Disclaimer on File?:        N/A 
Request Review:              
====================================================================== 
Date Submitted:             2008-08-11 04:50 CDT
Last Modified:              2008-08-11 09:36 CDT
====================================================================== 
Summary:                    Impossible to retrieve privacy info in a PRI
incoming call
Description: 
Hi, AFAIK Asterisk doesn't provide a way to check, in the dialplan, if a
PRI incoming call has privacy set for the callerID. If we check
CALLERID(xxx) variable it returns the real callerid but we cannot know if
privacy has been requested.

I propose a variable or a function to retrieve this information, something
as PRIVACY (yes/no):

  [from-pri]
  exten => _XX.,1,NoOp(--- Privacy requested: ${PRIVACY} ---)

====================================================================== 

---------------------------------------------------------------------- 
 (0091298) blitzrage (administrator) - 2008-08-11 09:36
 http://bugs.digium.com/view.php?id=13279#c91298 
---------------------------------------------------------------------- 
Haha oops.. I apparently phat fingered this bug. I meant to assign a
different one :) 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2008-08-11 09:36 blitzrage      Note Added: 0091298                          
======================================================================