Page 506 of 1814 Calling Party Privacy Override553-2901-301 Standard 9.00 January 2002When a user dials the Flexible Feature Code defined for the CPPO feature andif CPPO is not provisioned on the outgoing trunk route, the call proceedswithout carrying the Privacy Override Indicator.The CPPO feature does not affect whether or not the Calling Party Numberand Name information is displayed for internal calls within the Meridian 1system, even if the originator requests CPPO.All incoming non-ISDN calls with the Privacy Override Indicator terminateon the Meridian 1. If the Privacy Override Indicator is not defined in theFlexible Feature Code for CPPO, an overflow tone (unrecognized digits) isprovided to the user.If the Stored Number Redial (SNR)/Last Number Redial (LNR) feature isused by the originator of a CPPO call to store the dialed digits, the CPPOFlexible Feature Code is stored against the SNR/LNR database. If the userremoves that CPPO Flexible Feature Code and then the SNR/LNR feature isused to re-initiate the call, overflow tone is returned to the user.ISDN implementation for this feature includes DMS100/250, SL-100,AT&T4, AT&T5, TR-1268 (NI-2), Meridian Customer Defined Network(MCDN) Private Networks, EuroISDN, QSIG, and BRI trunks.The CPPO feature is supported on the following International PRI (IPRI)connectivities: Ericsson AXE-10 CO Connectivity (Australia), EricssonAXE10-CO Connectivity (Sweden), French Numeris CO Connectivity,Japan D70 CO Connectivity, Swissnet 2 CO Connectivity, SYS-12 COConnectivity, 1TR6 CO Connectivity (Germany), and Asia Pacific ISDNPhase 2.The CPPO feature supports the following North American connectivities:DMS100/250, S1100, Lucent #4 ESS (ESS4), Lucent #5 EES (ESS5), andTR-1268 (NI-2).CPPO does not support R2MFC signaling.
