Nortel DMS-100 Calling Line Identification Table (CLIDN)

Table Name

Calling Line Identification Table.

Functional Description of Table CLIDN

Table CLIDN contains the ten-digit Directory Numbers (DN) for which Calling Line Identification (CLI) is available.  These DNs are external to the switching unit.  The ten-digit DNs include an area code + office code + directory number.

In a local switching unit, the Number Planning Area (NPA - area code) must be the same NPA as the originating subscriber to produce log report TRK163.

The Trunk Maintenance (TRK) log subsystem generates TRK163 when the system routes a local line call over a trunk to a line in a distant office.  This office receives a CLI request.

In a toll switching unit, the NPA must be the same as the serving NPA of the incoming trunk to produce log report TRK164.

The Trunk Maintenance (TRK) log subsystem generates TRK164 when the system routes a call that originates from an external line through the office to a line in a distant office.  This office has a CLI.

To generate a TRK164 log for Feature Group D (FGD) calls with two-stage outpulsing, include SNPA+0ZZ+XXX in table CLIDN.  If this event does not occur, the system does not generate a TRK164 log.

The letter N must prefix service codes like 411, 911, and 0 to make the total digit count equal to 10.  The system internally translates the letter N to 0.  This condition requires two entries.  One entry, NPANNNN911, has the Serving NPA (SNPA) of the trunk.  The other entry, NNNNNNN911, does not have the SNPA of the trunk.

For CLI numbers internal to the switching unit, see feature CLI in table LENFEAT (Line Equipment Number Features).

Use feature CLI in a local, toll or local/toll switching unit.

If a local line calls an external DN that table CLIDN identifies for calling line identification, the system generates log report TRK163.  Log report TRK163 contains the following:

If the system cannot identify the calling DN, the Line Equipment Number (LEN) and tip-and-ring side identification replace the number.  The tip-and-ring side identification must be available.

An incoming trunk can receive a call for an external DN that table CLIDN identifies for CLI.  When this event occurs the system generates log report TRK164.  Log report TRK164 contains:

An incoming Signaling System 7 (SS7) trunk on a tandem switch can receive a call for an external DN that table CLIDN identifies for CLI.  When this event occurs the system generates log report TRK605.  Log report TRK605 contains:

The TRK605 log is used in a tandem switch to identify the origination number when the called number is being traced.  It is generated when the called number is datafilled in table CLIDN in the tandem switch and the call came in on a SS7 trunk.  To generate this log when the line being traced is a remote call forwarded line, simply datafill the DN in table RCFCLI (Remote Call Forwarding Calling Line Identification) in the same terminating End Office (EO) in which the Remote Call Forward (RCF) line exists.

United Kingdom

In the UK market, log TRK164 cannot trace the origin of a call.  Log report TRK602 replaces TRK164 in this market for PCM30 Digital Trunk Controller (PDTC) MEL and Digital Private Network Signaling System No. 1 (DPNSS) calls to BTUP.  The BTUP is the UK variant of national user part.

The TRK602 contains the same information as log TRK164 and a default CLI in table TRKMEM (Trunk Member).

Datafill Sequence

You do not need to enter data in other tables before you enter data in table CLIDN.

Table Size

67 tuples.

Datafill

The following table describes datafill for table CLIDN:










-----------------------------------------------------------------------------------------
Field Descriptions

Field       Subfield       Entry               Explanation and Action
----------------------------------------------------------------------------------------
DIGITS                     Numeric and         Digits.
                           N                   The entry is equal to the ten-digit DN of 
			                       a line external to the switching unit.

					       * The letter "N" must prefix service codes 
					         like 411, 911, and 0.  This action makes 
						 the total digit count equal to 10.  The
						 system translates the letter "N" internally 
						 to 0.  This condition requires two entries. 
						 One entry, NPANNN911, has the NPA.  One 
						 entry, NNNNNNN911, does not have the NPA.

                                               * To produce log report TRK163 in a local 
					         switching unit, the NPA must be the same 
						 NPA as the originating subscriber.

					       * You can produce log report TRK164 in a toll 
					         switching unit.  The NPA must be the same 
						 NPA as the serving NPA of the incoming trunk.

					       * Log report TRK602 replaces log TRK164 in the 
					         UK market.  This log report contains the same 
						 information, and a default CLI.
----------------------------------------------------------------------------------------
-End-

Datafill Example

An example of datafill for table CLIDN appears in the following table.  The example contains two lines in NPA 613 with assigned DNs 224-4579 and 238-2378.  These DNs appear for CLI in table CLIDN.

-----------------------------------------------------------------------------------------
Datafill Example for Table CLIDN
-----------------------------------------------------------------------------------------
Example of a MAP display:

    DIGITS
_______________________________________________________________________________________
6132244579
6132382378
_______________________________________________________________________________________