Nortel Meridian Meridian 1 Feature Description And Administration page 1517

Private to Public CLID Conversion Page 1517 of 1814
Operating parameters
You can use the feature with the following types of ISDN interfaces at the
tandem node:
— DMS 100
— DMS 250
— #4 ESS
— #5 ESS
— SL-100
— NI-2 TR-1268
The conversion of the CLID also occurs when features such as Call Forward
All Calls, Forward No Answer, and Hunting divert calls to the public
network.
Some COs use the CLID to perform billing. When a Meridian 1 tandem node
interfaces with one of these COs, set the CPUB option to "LDN" to allow
correct billing. Or else, with the CPUB option on, the CO uses the originator's
CLID for billing purposes. The call used the private network part of the way;
the bill for the call is not correct when it is based on this CLID. If you use the
Incoming Trunk Programmable Calling Line ID feature, it takes priority over
the Private to Public CLID conversion feature (refer to Feature interactions).
The software does not validate the NPA and NXX you input for each LOC
and DSC. When you test the operation of this feature, check the CLID shown
on the display of the terminating telephone. Make sure it is the call
originator's CLID.
When used with CDP, the software automatically deletes the DSC from the
CLID. You must include the removed DSC at the end of the NXX field to
maintain the accuracy of the CLID. For example, if the DSC is 32 and the
NXX is 658, program the NXX as 65832 in order to construct the correct
CLID.
To activate the feature you must enable it in LD 16 on the outgoing PSTN
route. You must also program an NPA and NXX for each LOC in LD 90 or
each DSC in LD 87. If you do not program an NPA and NXX in LD 90 or
LD 87, the system cannot build the public format CLID.
International ISDN PRI Feature description and administration