Table Name
Common Language Location Identifier.
Functional Description of Table CLLI
The Common Language Location Identification (CLLI) codes identify the far-end of each announcement, tone, or trunk group.
The CLLI codes describe each announcement, tone, trunk group, test trunk, national milliwatt test line, and service circuit.
You must enter the CLLI codes for all national milliwatt test lines in tables CLLI and TRKGRP. In table TRKGRP, type TTL2, field MWDBLEVEL specifies the card code of the milliwatt test line. The card code indicates the dB level of the milliwatt source. Field MWSPRVSN specifies the supervision. The old fixed pseudo CLLI codes can be present. Pseudo CLLI code cannot assume the dB level and supervision.
The international milliwatt test lines continue to use the fixed pseudo CLLI codes, INTL102T, INTL102L, and INTL100Q. In table TRKGRP (type TTL2), the international test lines, INTL102T, INTL102L, and INTL100Q have datafill in fields MWDBLEVEL and MWSPRVSN. The switch does not use the information in these fields.
The list of codes must contain the fixed pseudo codes that apply to the switch. The list of codes must contain the codes that the operating company defines.
Use the Command Interpreter (CI) command RENAMECLLI to rename or change the spelling of a current CLLI code. Use the CI command CLLINUMBER to obtain the number associated with the CLLI name. Specified tables require the CLLI number and not the CLLI name. Refer to the Basic Translations Tools Guide for additional information.
Note: Do not use the CI command RENAMECLLI for primary rate interface (PRI) trunks that are used as a PRI Public Safety Answering Point (PSAP).
The following are the four types of CLLI codes:
The CLLI codes the EXT files contain appear in the following table. The system adds these codes to table CLLI for an associated feature.
The type of restart the system requires after the addition of the CLLI code to table CLLI appears in the following list. This addition allows this CLLI code to occur in another table. The system requires this restart to increase the TRKGRSIZ for the specified CLLI.
If your switch has the NORESTARTSWACT utility, a service interruption does not occur when you activate data changes. Refer to the NORESTARTSWACT User Guide.
-----------------------------------------------------------------------------------------
CLLI Codes that Depend on the Feature
CLLI Explanation Related Table Restart
-----------------------------------------------------------------------------------------
BBTOUT Board-to-Board Testing None None
DLSE Dial Line Service Evaluation None None
DMODEMC Digital Modem, Bell 212 DMODEM None
Communication Protocol
DPPSC Distributed Processing Peripheral DPP None
Scan Circuits
DSCKT Dialable Short MTAHORIZ None
EADNMCLLI Engineering and Administration Data EADNMTG None
Acquisition System for Network
Management
FRBTONE Faultsman's Ringback Tone (Use this DRAMS Cold
tone to access acknowledgement tone.
The acknowledgement tone is a special
information tone that resides in the
Digital Recorded Announcement Machine
[DRAM].)
ITSE Incoming Toll Service Evaluation None None
MISCSC Miscellaneous Scan Group (SC) SCGRP None
Circuits (See note 9.)
MISCSD Miscellaneous Signal Distributor (SD) SDGRP None
Circuits (See note 9.)
NWMSC Network Management Scan Point NWMSC None
NWMSD Network Management Signal NWMSD None
Distributor Point
OFFHKSUP Supervision Signal Off-Hook OFRT and all None
(See note 5.) RTEREF subtables
ONHKSUP Supervision Signal On-Hook OFRT and all None
(See note 5.) RTEREF subtables
ROTLSC Remote Office Test Line Scan Point ROTLSCSD None
ROTLSD Remote Office Test Line Signal ROTLSCSD None
Distributor Point
STGOVFL Equal Access Shared Trunk Group IBNRTE None
Overflow Peg
-----------------------------------------------------------------------------------------
-continued-
-----------------------------------------------------------------------------------------
CLLI Codes that Depend on the Feature (continuted)
CLLI Explanation Related Table Restart
-----------------------------------------------------------------------------------------
STRG Station Ringer (Refer to the None None
current station ringer test example.)
SYNCH Synchronous Test Line (Refer to route OFRT and all None
reference 11 for table OFRT.) RTEREF subtables
TERMARTER International ARTER Transmission None Cold
Testing of Turkish Trunks (The addition
of these trunks occurs at Initial
Program Load [IPL] time by terminating
ARTER software code.)
TOPSCOINCOLLECT TOPS Coin Collect OFRT and all None
(See note 4.) RTEREF subtables
TOPSCOINDISABLE TOPS Coin Key Pad Disable OFRT and all None
(See note 4.) RTEREF subtables
TOPSCOINENABLE TOPS Coin Key Pad Enable OFRT and all None
(See note 4.) RTEREF subtables
TOPSCOINRETURN TOPS Coin Return OFRT and all None
(See note 4.)
TRKLPBK Dialable Loopback for Trunks that are None None
DS-0 Channels (These trunks include
ISDN User Part [ISUP] trunks. See
note 10.)
WINKSUP Supervision Signal Wink OFRT and all None
(See note 5.) RTEREF subtables
-----------------------------------------------------------------------------------------
-End-
The fixed CLLI codes to add to table CLLI appear in the following table. The spelling of the fixed CLLI codes must be the same as the spelling that appears.
-----------------------------------------------------------------------------------------
Fixed CLLI Codes
CLLI Explanation Related Table Restart
-----------------------------------------------------------------------------------------
AIS Automatic Intercept System Trunk TRKGRP (type AI) None
ALL SATOVER Table Generic CLLI SATOVER None
AOSSANN Auxiliary Operator Services System ANNS None
(ADSS) Announcement DRMUSERS
AOSSDEV ADSS Device AOSSDEV Cold
AOSSPOS ADSS Position AOSSPOS Cold
AOSSPOSDATA ADSS Position Data AOSSPOS Cold
ASCS Alarm Sending and Checking ASCS None
-----------------------------------------------------------------------------------------
-continued-
-----------------------------------------------------------------------------------------
Fixed CLLI Codes (continued)
CLLI Explanation Related Table Restart
-----------------------------------------------------------------------------------------
ATMERA ATME2 Type-A Responder OVR0-9 Cold
(See note 11.)
ATMERB ATME2 Type-B Responder OVR0-9 Cold
(See note 11.)
ATMERC ATME2 Type-C Responder OVR0-9 Cold
(see note 11)
BVTONE Busy Verification Tone STN Warm
(See note 7.)
CAPOX CAMA Call Waiting Suspension CAMACSWS Cold
CF3P Three-Port Conference Circuit CONF3PR None
CF6P Six-Port Conference Circuit CONF6PR None
COPP Cutoff on Permanent Signal and Partial None None
Dial
CPOS CAMA Position Talk Circuit CAMACSW Cold
CPOSKEY CAMA Position Key Circuit CPOS Cold
CSUSP Traffic Operator Position System CSUSP None
(TOPS) CAMA Suspension Circuit
CWT Call Waiting Tone STN Warm
DCLTONE Dialable Cable Locator Tone TRKGRP (type MAINT) None
DCTTERMBERT Data Call Tester Bit Error Tester DNIBERT None
Termination Application
DGT300 DMS-300 Digital Digitone Receivers RECEIVER None
DISTCWT Distinctive Call Waiting Tone STN Warm
DMODEM Digital Modem (Integrated Business None None
Network [IBN], TOPS.)
DQB300 Dial-up Autoquote Modem at 300 Baud DQMODEM None
DQB1200 Dial-up Autoquote Modem at 1200 Baud DQMODEM None
DRCWTONE Distinctive Ringing/Call Waiting Tone STN Warm
DTU Digital Test Unit TRKGRP (type MAINT) None
EAPEG Equal Access Overflow Peg AMAOPTS None
EBOT Executive Busy Override Warning Tone STN Warm
(Most switches use this tone. The UK
switches are the only switches that
do not use this tone.)
-----------------------------------------------------------------------------------------
-continued-
-----------------------------------------------------------------------------------------
Fixed CLLI Codes (continued)
CLLI Explanation Related Table Restart
-----------------------------------------------------------------------------------------
ENHCWT1 Enhanced Call Waiting Tone for the STN Warm
First Secondary Directory Number
(SDN)
ENHCWT2 Enhanced Call Waiting Tone for the STN Warm
Second SDN
ENHCWT3 Enhanced Call Waiting Tone for the STN Warm
Third SDN
ERWT Expensive Route Warning Tone STN Warm
ESADGTR Emergency Stand-Alone Digitone TRKGRP None
Receivers
ESUP1 to ESUP5 Digital Echo Suppressors ECHOSUP None
(See note 3.)
FMTSC Fiber Multiplex Terminal Scan Point FMTSC None
FPOT Foreign Potential Test (Refer to OFRT and all None
example at the end of this section.) RTEREF subtables
GTERM102T Terminates Testlines on Global 100 None None
Trunks (This CLLI routes an incoming
call to the MTM test equipment. The
MTM generates a T102 toll milliwatt
tone.)
GTERM100Q Terminates Testlines on Global 100 None None
Trunks (This CLLI routes an incoming
call to the MTM test equipment. The
MTM generates a T100 quiet
termination.)
GTERM102S Terminates Testlines on Global 100 None None
Trunks (This CLLI routes an incoming
call to the MTM test equipment. The
MTM generates a T102 steady tone.)
GTERM102L Terminates Testlines on Global 100 None None
Trunks (This CLLI routes an incoming
call to the MTM test equipment. The
MTM generates a T102 local milliwatt
tone.)
HOBICDEV Hotel Billing Information Center Device HOBICDEV Cold
HSET Maintenance Head Set Circuit TRKGRP (type MAINT) None
IEBOT International Executive Busy Override STN Warm
Tone (Only UK switches use this tone.)
IDLE Idle (Only in a North American switch OFRT and all None
uses this CLLI. Refer to example at RTEREF subtables
the end of this section.)
-----------------------------------------------------------------------------------------
-continued-
-----------------------------------------------------------------------------------------
Fixed CLLI Codes (continued)
CLLI Explanation Related Table Restart
-----------------------------------------------------------------------------------------
INTL100Q International 100 Balance Test Line TRKGRP (type ITL2) None
INTL102T International 102 Test Line TRKGRP (type ITL2) None
INTL102L International 102 Test Line TRKGRP (type MAINT) None
ISDNBRIVOE Integrated Services Digital Network STDPRI None
RTEREF
IROH International Receiver Off-Hook TONES Warm
ITOPSDEV International TOPS Device ITOPSDEV Cold
(See note 6.)
ITOPSPOS International TOPS Position Voice ITOPSPOS Cold
(See note 6.)
ITOPSPOSDATA International TOPS Position Data Trunk ITOPSPOS Cold
(See note 6.)
JACK TTP - Toll Jack Circuit TRKGRP (type MAINT) None
KSR2ICVR For Licensee Use Only RECEIVERl None
KSR2OCVR For Licensee Use Only RECEIVER None
LKOUT Lockout (Refer to example at the OFRT and all None
end of this section.) RTEREF subtables
LOOPA1 Loop-Around Test Line, Port 1 TRKGRP (type LOOPA) None
LOOPA2 Loop-Around Test Line, Port 2 TRKGRP (type LOOPA) None
LTU Line Test Unit TRKGRP (type MAINT) None
MF300 DMS-300 Analog and Digital MF Receivers RECEIVER None
MJACK Metallic Jack MTAMDRVE Cold
MOBICPT Mobile Intercept None Cold
MOBRODR Mobile Reorder None Cold
MONTALK Talk and Monitor (This CLLI is for Line TRKGRP (type MAINT) None
Test Unit [LTU].)
MTADRIVER Metallic Test Access Driver MTAHORIZ None
MTU Metallic Test Unit (nondomestic) or TRKGRP (type MAINT) None
Multiline Test Unit (domestic)
NOSYN Nonsynchronous Test Line (See route OFRT and all None
reference 11 for table OFRT.) RTEREF subtables
OAUSC Office Alarm Unit Scan Groups ALMSCGRP None
(See note 2.)
-----------------------------------------------------------------------------------------
-continued-
-----------------------------------------------------------------------------------------
Fixed CLLI Codes (continued)
CLLI Explanation Related Table Restart
-----------------------------------------------------------------------------------------
OAUSD Office Alarm Unit Signal Distributor ALMSDGRP None
(See note 2.)
OCKT Open Circuit Termination TRKGRP (type SOCKT) None
OHQT Off-Hook Queuing Tone STN Warm
OOCDEV Overseas Operator Center (OOC) TOPSDEV Cold
Device
OOCPOS OOC Operator Position - Voice TOPSPOS Cold
OOCPOSDATA OOC Operator Position - Data TOPSPOS Cold
OPMPES Outside Plant Module Power and OPMINV None
Environmental System
PCNOR Preset Conference Normal Notification STN Warm
Tone
RCVATDUK A-Law Automatic Tone Detector (UK) RECEIVER None
RCVRATD Audio Tone Detector RECEIVER None
RCVRCDC Coin Detection Circuit Receiver RECEIVER None
RCVRCOIN Automatic Coin Toll Service Receiver RECEIVER None
RCVRDGT Digital Digitone Receiver Circuits RECEIVER None
RCVRDTUK A-Law Digitone Receiver (UK) RECEIVER None
RCVRMCCS Mechanized Calling Card Receiver RECEIVER None
RCVRMF Analog and Digital MF Receivers RECEIVER None
ROH Receiver Off-Hook STN Warm
ROTLTP Remote Office Test Line (ROTL) Port TRKGRP (type ROTL) None
SIGTERM CCS6 Signaling Terminal None None
SCKT Short Circuit Termination TRKGRP (type SOCKT) None
SSMAN Silent Switchman (See table OFCENG None
OFCENG, parameter
SILENT_SWITCHMAN_TIMEOUT.)
SVDTMF Dual-Tone Multifrequency (DTMF) SVRCKT Warm
Transmitter
SVMFC R2 Interregister Signaling Cicuit SVRCKT Warm
SVOBSV Service Observing Circuit SVRCKT Warm
TASISC TASI State Controller TASIB None
-----------------------------------------------------------------------------------------
-continued-
-----------------------------------------------------------------------------------------
Fixed CLLI Codes (continued)
CLLI Explanation Related Table Restart
-----------------------------------------------------------------------------------------
TASISD TASI State Controller TASIB None
TERM100Q Termination 100 Test Line TRKGRP (type TTL2) None
TERM102L Termination 102 Test Line TRKGRP (type TTL2) None
TERM102T Termination 102 Test Line TRKGRP (type TTL2) None
TERM103T Terminating 103 Test Line OFRT and all None
RTEREF subtables
TERM105 Terminating 105 Test Line (The use of TRKGRP (type T105) Cold
fixed pseudo CLLI TERM105 occurs if
ROTL equipment is present.)
TERM105T Terminating 105 Test Line (The use of None
fixed pseudo CLLI TERM105T occurs
if ROTL equipment is not present.
This condition permits the use of the
105 test line with the Transmission Test
Unit (TTU) at the terminating office.
Tables TRKGRP, TRKSGRP or TRKMEM do not
require additional datafill.)
TERM107T Terminating 107 Test Line None Cold
(Preemption test line.)
TERM108 Terminating 108 Test Line TRKGRP None
TISS Terminating International 103 Signal TSTLCONT None
Supervisory Test Line (subtable TLNOS)
TOPSDEV TOPS Device TOPSDEV Cold
(See note 6.)
TOPSPOS TOPS Position - Voice TOPSPOS None
(See note 12.)
TOPSPOSDATA TOPS Position - Data TOPSPOS None
(See note 12.)
TTT Transmission Trunk Test TRKGRP (type MAINT) None
TTU Transmission Test Unit TRKGRP (type MAINT) None
VER90 Operator Verification TRKGRP (type VR) None
(See note 1.)
-----------------------------------------------------------------------------------------
-End-
A list of suggested CLLI codes you must add to table CLLI appears in the following table. The spelling of these codes can be different. The spelling of the code must be the same in each table in which the code appears. Use the spelling that appears.
-----------------------------------------------------------------------------------------
Suggested CLLI Codes
CLLI Explanation Related Table Restart
-----------------------------------------------------------------------------------------
ACCSTOPS Automatic Calling Card Service ANNS None
Bilingual Announcement
ACTSTOPS Automatic Coin Toll Service ANNS None
RING Ringback Tone TONES None
(See note 8.)
DSCDBUSY DSCWID Busy Announcement RESOFC None
DSCWDDFLT DSCWID Default Announcement RESOFC None
DSCWDDSCN DSCWID Disconnect Announcement RESOFC None
DSCWDHOLD DSCWID Hold Announcement RESOFC None
DSCWDRMDR DSCWID Reminder Announcement RESOFC None
-----------------------------------------------------------------------------------------
Note 1: Code VER90 is for the operator verification trunk group in the host switch. The operating company defines the codes for the operator verification trunk groups at the remote location.
Note 2: Trunk group size for fixed pseudo CLLI codes OAUSC and OAUSD equals the number of scan and signal distributor groups. The office alarm requires the scan and signal distributor groups.
Note 3: For codes ESUP1 to ESUP5, the value in field TRKGRSIZ must be equal to two times the number of digital echo suppressors. The digital echo suppressors are for the code in table ECHOSUP. One digital echo suppressor must be present for each port.
Note 4: The pseudo CLLI codes TOPSCOINCOLLECT, TOPSCOINENABLE, TOPSCOINDISABLE, and TOPSCOINRETURN allow the operating company to specify coin signals. These coin signals are for calls that arrive at an access tandem on TOPS trunks. These calls do not route to an operator. One CLLI code allows the operating company to make sure the system enables Digitone key pads. These Digitone key pads are on coin phones. The system allows these Digitone key pads for feature group B calls and for 800 service calls. Some end offices do not leave the key pads in the correct state. Special CLLI code TOPSCOINENABLE allows the operating company to have complete flexibility to enable these pads. To use this CLLI code, place this code at the beginning of a route list. This route list must route the call to an incoming (IC) trunk. To route a call on trunk group OGEACAR1, the operating company can enter the following data in a route in table OFRT:
999 ( S D TOPSCOINENABLE) (N D OGEACAR1 0 N N)
This datafill sends a coin enable signal to enable a Digitone key pad for all coin calls that use route list. After the coin signal finishes, the call routes to trunk group OGEACAR1. A coin call can originate from an end office that left the key pad in the correct state. When this event occurs, calls from these offices can route to a different route list. This route list does not include the coin enable the CLLI code. This routing avoids the additional post-dial delay the coin enable signal causes.
The addition of a coin signal to a route list can occur. This addition adds approximately 3 seconds of post-dial delay to each coin call that uses this route list. The time for the transmission of the coin signal is 3 seconds.
The three other types of coin signals are pad disable, coin collect, and coin return. A requirement to send these signals for some calls on TOPS trunks that do not route to TOPS operators can occur. Three CLLI codes, TOPSCOINDISABLE, TOPSCOINCOLLECT, and TOPSCOINRETURN are available for this purpose.
The position of these coin CLLI codes is at the beginning of a route list before any trunk CLLI codes. The system can require more than one coin signal. When this event occurs, the addition of more than one CLLI code to the route list can occur. Only calls that originate on TOPS trunks and that a TOPS operator does not complete can use the CLLI codes. The Centralized Automatic Message Accounting (CAMA) calls that route to a TOPS operator can use the CLLI codes. Calls that transfer to an IC operator service can use the CLLI codes. These conditions occur because the TOPS operator does not complete these calls.
The system can route non-coin calls to a route list with the special coin CLLI code. The software determines that the call is non-coin. The system does not attempt coin signaling.
To use the four CLLI codes, add the codes to table CLLI. The system does not require a restart. The removal of restart requirement occurred in CSP04.
Note 5: The system can use the CLLI codes at the end of a route list. The CLLI codes send the correct supervision signal to the originating office. This event occurs if all members of the outgoing trunk group are busy. The system performs the standard treatment after the system completes this procedure. The system only supports the following trunk group types: SC, IS, IT, OI, OC, OP, TI, T2, TOPS, A5, and TDDO.
Note 6: You can enter the fixed CLLI code TOPSDEV, ITOPSPOS, ITOPSPOSDATA, or ITOPSDEV in table CLLI. When you perform this action, you must perform a cold restart before you enter tuples in the associated tables. To increase the size of tables TOPSDEV, ITOPSPOS, or ITOPSDEV, you must delete all members of these tables. The value in field TRKGRSIZ in table CLLI increases for the associated fixed CLLI code or codes. Perform a cold restart or a reload restart. Enter the members of the table again.
Note 7: The remote switch in the network Busy Verification Line (BVL) requires the Busy Verification Tone (BVTONE) circuit. You must enter the fixed CLLI code BVTONE on the remote switch in table CLLI.
Note 8: Treatment No Terminal Responding (NTRS) or Call Rejected (CREJ) can occur on an ISDN Basic Rate Access (BRA) call. When this event occurs, the caller receives audible ringback. The system can apply ringback at the originating agent after these events occurred. The definition of a tone that software generated appears in table TONES for ISDN switches. This tone is *RING. Enter the *RING tone in table CLLI. Table OFRT and fields LNT and OFFTREAT in table TMTCNTL.TREAT define tuples. This action maps treatments NTRS and CREJ to this tone. When one of these treatments occurs, the system sustains audible ringback at the originating end of the call.
Note 9: You can enter members of the SC and SD groups in tables SCGRP and SDGRP. When this event occurs, the system automatically enters a tuple in table CLLI for pseudo fixed CLLI codes MISCSC and MISCSD.
Note 10: Trunk group size for CLLI code TRKLPBK is equal to 0 (zero). This event occurs because table TRKMEM does not assign trunks.
Note 11: For ATME2 to function, add the three CLLI codes ATMERA, ATMERB, and ATMERC to table CLLI. Perform a cold restart. If you do not perform this action, the system does not bind the correct CLLI codes.
Note 12: For CSP04, the system eliminates the restart requirement when the size of table TOPSPOS changes. Before CSP04, the size increased as Note 6 indicated for the other TOPS tables. In CSP04, to increase the size, increase the value of TRKGRSIZ in table CLLI for TOPSPOS and TOPSPOSDATA CLLIs. Add the new tuples in table TOPSPOS. The system does not require a restart.
Deallocation of memory does not change. You must delete all tuples as follows:
The system does not require a restart.
Warning: The maximum size of table TOPSPOS is 1023 tuples. The TRKGRSIZ can be higher than 1023 for fixed CLLI (TOPSPOS or TOPSPOSDATA). When this event occurs, the addition of tuples to table TOPSPOS cannot occur and an error message appears. You cannot change tuples. You must delete and add all tuples again. The steps for this action appear above. For releases before CSP04, this condition causes an outage because of the cold restart requirement.
Deleting CLLI Codes from Table CLLI
To delete a CLLI code, you must delete the CLLI code from all tables in which the code appears. You must perform this action before you delete the tuple from table CLLI. The system does not require that you delete the tuple from table CLLIMTCE. When you delete the tuple table CLLI, the system deletes the tuple from table CLLIMTCE.
The CI command TABREF can determine the other tables that a CLLI code can reference.
Assigning CLLI Codes for Spare Analog Trunks
All spare analog trunks in the switch must appear in the table TRKGRP with a CLLI code of SPAREXXXXXX. The XXXXXX is the card code of the spare analog trunk or trunks. If spare analog trunks are present with a card code of 2X83AA, the CLLI code is SPARE2X83AA. The value of field TRKGRSIZ must be large enough to handle all spare analog trunks until the next extension. You must add the spare analog trunks to table CLLIMTCE.
Signaling Engineering and Administration System (SEAS) 1.1 Enhancements
Feature AL1334 (SEAS 1.1 Enhancements) changed the design of routeset CLLI codes. Routeset CLLI codes are the key to table C7RTESET when the SEAS commands ADD_RTE or CHG_RTE modify data routing information.
Feature AL1334 maintained tuples in table CLLI. These tuples are the key to table C7LKSET. Field ADMININF in table CLLI contains the far-end office name. This name is in field FECLLI of table C7LKSET as SEAS commands ADD_LS or CHG_LS provide.
Note: For feature AE0901 for BT7, you must enter EMERGENCY_CALL_ANN in field ADMININF in table CLLI. This entry specifies that an emergency call announcement will occur.
Routeset CLLI Codes
For feature AL1334, the name that is the routeset name changes to reflect information about the routeset the data determines. This action can occur by the two following methods.
The name can be the exact name entered in field FECLLI of table C7LKSET of the linkset. This table defines the linkset as the associated route of the routeset. A route is associated if the far-end point code of this linkset is the correct point code of this routeset. The far-end point code is in field FEPC of table C7LKSET. The routeset is in field DPC of table C7RTESET.
If the routes are not associated, the routeset name can be the textual representation of the point code of the routeset. This textual representation is a field that contains nine digits.
You must create the name of the routeset when the definition of a route for a new destination occurs. Routes are not defined to this point code. When the addition of a route to a current routeset occurs, the routeset name does not change. When the following events occur, the routeset name changes to reflect the new configuration:
Field ADMININF for Linkset CLLI Tuples
Field ADMININF of table CLLI stores any additional information on the CLLI code you define. With feature AL1334, the field ADMININF indicates the associated far-end CLLI name of the linkset you add. The associated far-end CLLI name is in field FECLLI in table C7LKSET. You can use the SEAS command CHG_LS to change the name in field FENAME of the linkset. When you change the name, you must update field ADMININF to maintain this new relationship.
The SEAS commands ASGN_LS and CHG_LS provide the far-end name information.
Limits
The system maintains the routeset name relationship that feature AL1334 defines only if the SEAS interface changes the data. If the DMS table control interface changes this data, the routeset name does not change.
The DMS table control interface can change table C7LKSET. When this event occurs, the system does not update field ADMININF of table CLLI to reflect the far-end name of the linkset.
The DMS table control interface can make changes. When this event occurs, operating company personnel must maintain the name relationships manually.
To invoke the DMS-100G Terminating Test Line Service, you must enter the CLLI name. Provisioned CLLI names are fixed. You cannot delete the CLLI names.
The DMS-100 Terminating Test Line datafill must be in the office for a DMS-100G Terminating Test Line to function. A warning message appears if the datafill is not present when you provision table CLLI. Calls that originate in an office where DMS-100 datafill is not available transfer to datafill_error treatment. Offices can use DMS-100 and DMS-100G Terminating Test Line routing. For these offices, use different digits for digits the originating office outpulses.
Tables TRKGRP, TRKSGRP, and TRKMEM do not require additional datafill. The DMS-100 test line datafill must be present in the office for DMS-100G Test Line to function correctly.
Station Ringer Test Examples
To activate the Station Ringer Test (SRT), dial a two-digit code and the last five digits of the Directory Number (DN). This DN is the DN for which the test occurs. The two-digit code can be 57. For example, to test DN 621-1234, the tester dials 571-1234. This condition applies if the DNs in an office do not share the same last five digits. The same office can serve two DNs, 621-1234 and 631-1234. When this event occurs a separate test cannot occur for each station because the only dialing pattern possible is 571-1234. This dialing pattern refers to both DNs.
A more current method to invoke SRT is to dial the SRT access code and the DN for which the test occurs. This method can be present with the method that appears above.
The SRT access code is nominally three digits. Datafill can change the SRT access code. Both access methods function on the same switch. You can use datafill access codes for both methods to dial SRT.
The DN for which the test occurs can be seven digits without the Numbering Plan Area (NPA). This DN can be ten digits with NPA. The DN can be a seven-digit DN. If this condition occurs, the SRT tests that compare the number dialed against the station dialing cannot include the NPA. This condition does not cause a problem often. A problem occurs only if the same switch serves two DNs that differ only by NPA. Operating companies can use different datafill to allow one the following events to occur:
If the operating company specifies the first option, and the subscriber dials seven digits, a pause of several seconds occurs. After the pause, the system processes the call. The pause occurs because the line module (LM) waits. The LM waits to make sure the subscriber does not dial additional digits.
Example
The DN to test is DN 613-621-1234. The older SRT access code is 57. The newer SRT access code is 999. Dial 571-1234, 999-621-1234, or 999-613-621-1234 from that station to invoke SRT.
Administrative Trunk Group Number (ADNUM)
In table CLLI, field ADNUM can range from 0 to 8191. This range is one less than the maximum size of table CLLI. This field allows the operating company to associate an ADNUM with each DMS-100 family trunk group CLLI code. This ADNUM must be different between the CLLI codes. This ADNUM remains fixed for the life of the trunk group. The number of dump-and-restore actions that occur on the switch does not affect this condition.
The range of values for field ADNUM starts at 0 (zero). The range is from 0 to a number that is one less than the size of table CLLI. The size of table CLLI appears in table DATASIZE. For example, if the size of table CLLI is 650, the maximum value that for field ADNUM is 649.
For pseudo CLLI codes, the operating company assigns a specified ADNUM occurs. The pseudo CLLI codes are CLLI codes added from EXT files. These numbers start with 1 and continue in ascending order. Avoid a value of 0 (zero) because specified downstream processors do not accept 0 as an allowed identifier. These downstream processors include Engineering and Administrative Data Acquisition System (EADAS) for Network Management (EADAS/NM). To assign a 0 causes an error message. The system does not reject the entry.
Assign CLLI codes that the operating company defines in sequence. Start with the lower numbers. The ADNUM values 1 to 50 are for pseudo CLLI codes. The value 0 (zero) is not always correct for some downstream processing.
The number of CLLI codes the operating company defines can be greater than the size of table CLLI minus 50. When this event occurs, increase the size of table CLLI. This increase in table size prevents the use of ADNUM values reserved for additional future pseudo CLLI codes.
Modifying the Value in Field ADNUM
You can change the value in field ADNUM. You can change this value if other tables in the DMS-100 switch do not refer to the CLLI code. To change the ADNUM value, you must remove tuples that contain the CLLI code from the following tables:
You must delete the tuple that contains the CLLI code in table CLLI. You must enter this tuple again in table CLLI to change the value of field ADNUM.
See sections EADAS/DC changes and EADAS/NM changes.
Default ADNUMs for Pseudo CLLI Codes
The default ADNUM assigned to each pseudo CLLI code that an EXT file adds appears in the following table:
----------------------------------------------------------------------------------------- Default ADNUMs CLLI ADNUM ----------------------------------------------------------------------------------------- DLSE 1 DMODEMC 2 DPPSC 3 DSCKT 4 EADNMCLLI 5 FRBTONE 6 ITSE 7 NWMSC 8 NWMSD 9 OFFHKSUP 10 ONKHSUP 11 STGOVFL 12 STRG 13 SYNCH 14 TERM105T 15 TOPSCOINCOLLECT 16 TOPSCOINDISABLE 17 TOPSCOINENABLE 18 TOPSCOINRETURN 19 WINKSUP 20 BBTOUT 21 ROTLSC 22 ROTLSD 23 TRKLPBK 24 TERMARTER 25 MISCSC 26 MISCSD 27 NILWAITANNC 29 -----------------------------------------------------------------------------------------
Note: The ADNUM assigned to a CLLI code must be different. The system does not allow you to assign an ADNUM associated with another CLLI code. Do not use an ADNUM assigned to a pseudo CLLI code for CLLI codes the operating company defines.
The EADAS for Data Collection (EADAS/DC) and EADAS Network Management (EADAS/NM) interfaces to the DMS-100 change. This change allows the use of the ADNUM in table CLLI.
EADAS/DC Changes
The record identification (ID) fields in the EADAS/DC sections for the following Operational Measurement (OM) groups contain the administrative number. This number relates to the CLLI code:
The ADNUM orders the records in these sections.
The EADAS/DC section contains the counts for the preceding OM groups. The information associated with these counts is as follows:
The operating company cannot change the ADNUM for a CLLI code if both of the following conditions apply:
To change an ADNUM, you must remove the tuples that refer to the CLLI code of the ADNUM from all tables. You must delete the tuple in table CLLI that contains the ADNUM. You must enter this tuple again in table CLLI with the new ADNUM value. Enter tuples that contain the CLLI code again. Enter these tuples in the tables from which you removed these tuples.
EADAS/NM Changes
If an ADNUM changes, the ADNUM sets the EADAS/NM trunk group list discrete to indicate the change. The office can have feature package X455AB (1A EADAS Network Management). If the office has this package, a change to the ADNUM creates two entries. These entries are in the EADAS/NM trunk group changed list. One entry identifies the old ADNUM. The other entry identifies the new ADNUM.
Table TRKNAME
Table TRKNAME is a read-only table. The system enters data in this table with entries in table CLLI. With an ADNUM value, the associated CLLI code can appear in table TRKNAME. The reverse mapping appears in table CLLI. See the example at the end of this section.
Datafill Sequence
You do not need to enter data in other tables before you enter data in table CLLI.
Table Size
0 to 8192 tuples
The system allocates memory by field SIZE in table DATASIZE for the entry with field DATSKEY equal to CLLI. To extend table CLLI, increase the value of field SIZE in table DATASIZE. Perform a cold restart. If your switch has the NORESTARTSWACT utility, an interruption of service does not occur when you activate data changes. Refer to the NORESTARTSWACT User Guide.
Datafill
Datafill for table CLLI appears in the following table:
-----------------------------------------------------------------------------------------
Field Descriptions for Table CLLI
Field or Subfield Entry Explanation
-----------------------------------------------------------------------------------------
CLLI alphanumeric Common Language Location Identifier
(vector of a
maximum of Enter a CLLI code to identify the far-end of each
16 characters) announcement, tone, or trunk group.
Note: You can only enter alphabetic characters,
numeric characters, and _ (underscores) in this
field. The first character must be alphabetic. The
use of other special characters like @, #, $, %, ^,
&, *, (, ), -, +, =, /, , ;, :, ?, }, and { can
cause errors in the data in this field.
For best use, a CLLI code must contain a
maximum of 12 characters. Only the first 12
characters appear on the MAP. When a CLLI code
appears in a log report, the whole 16-character
CLLI code appears.
The recommended code for a gateway switch
contains the following elements:
* SITE - Site. This element has three
characters. This element identifies
of the site. The site is a switch. If more than
one site is present in a city, each site has a
name. If only one site is in a city, enter the
abbreviated city name.
* SUFX - Suffix. This element has two
characters. This element identifies the trunk
group. If more than one trunk group is in the
same site, each trunk group has a different
number for identification.
* COUNTRY - Country. This element has three
characters. This element identifies the name
of the country that is the location of the site.
* CITY - City. This element has three
characters. This element identifies the name
of the city at the far-end of each trunk group.
If only one site is in a city, and the abbreviated
city name identified the entry, leave CITY
blank. If more than one site is present in a city,
use both element SITE and element CITY.
Note: The CLLI code can occupy 11 characters of
the string of 16 characters. The field ends at the
first blank character. For example, only one trunk
group can be present for a specified switch. When
this event occurs, only the element SITE requires
data entry as the CLLI code.
-----------------------------------------------------------------------------------------
-continued-
-----------------------------------------------------------------------------------------
Field Descriptions for Table CLLI (continued)
Field or Subfield Entry Explanation
-----------------------------------------------------------------------------------------
The recommended CLLI code for other than a
gateway switch contains the following elements:
* PLACE - Place. This element has four
characters. This element identifies the name
of the city or town at the far-end of each group.
This element can identify the name for each
tone or announcement.
* STATE - State or Province. This element has
two characters. This element identifies the
state or province at the far-end of the trunk group.
* BLDG - Building. This element has two
characters. This element identifies the
building number at the far-end of the trunk group.
* TRAFUNIT - Traffic Unit. This element has
three characters. This element identifies the
designation of the traffic unit at the far-end of
the trunk group.
* SUFX - Suffix. This element has one
character. This element identifies trunk
groups that terminate at the same location.
Note 1: This CLLI code can occupy 12 characters
of the field of 16 characters. The system treats the
CLLI code as a character string. The field ends at
the first blank character. If only one trunk group
ends at a specified switch, only the element
PLACE requires data entry for the CLLI code.
Note 2: For feature AE0901 for BT7, the entry EMERCALL
in this field specifies the emergency call feature.
-----------------------------------------------------------------------------------------
ADNUM numeric Administrative Trunk Group Number
(0 to 8191)
Enter a number in the range from 0 to one less than
the current size of table CLLI. The current size of
table CLLI appears in field SIZE of table DATASIZE.
The operating company must not assign
Administrative Numbers (ADNUM) below 51. This
condition allows for future growth in the number of
pseudo CLLI codes.
The ADNUMs for fixed CLLI codes and CLLI codes
the operating company defines have a specified
range. This range is from 51 to the size of table
CLLI that appears in table DATASIZE minus one.
The ADNUMs for pseudo CLLI codes external
(EXT) files add must use the default value.
The value of field ADNUM in table CLLI must be
different. The system rejects attempts to add a
CLLI code with an ADNUM that is in use.
-----------------------------------------------------------------------------------------
-continued-
-----------------------------------------------------------------------------------------
Field Descriptions for Table CLLI (continued)
Field or Subfield Entry Explanation
-----------------------------------------------------------------------------------------
You cannot change field ADNUM in table CLLI if
one of the following events occurs:
* The system reports Operational Measurement
(OM) counts to the Engineering and
Administrative Data Acquisition System
(EADAS). The system reports OM counts for
Data Collection (EADAS/DC). These OM
counts are for OM groups TRK, NWMSILC,
TRK250, or DCRICTRK.
* The CLLI code is in the EADAS Network
Management (EADAS/NM) trunk group
schedule.
The operating company can change the ADNUM
value. This event can occur if other tables in the
switch do not refer to the CLLI code of the ADNUM
value.
You must delete the tuple that contains the
ADNUM value to change an ADNUM value. You
must perform the following actions:
* Delete the tuple
* Change the ADNUM value
* Enter the tuple again in table CLLI
-----------------------------------------------------------------------------------------
TRKGRSIZ numeric Trunk Group Size
(0 to 2047)
Enter the maximum number of trunk members to
assign in the trunk group. This number allocates
storage. This number can be greater than the
number of initial working trunks.
The only continuous change you can make to this
quantity is to increase the size. An attempt to
decrease TRKGRSIZ causes an error message.
The only size reduction that can occur is to
decrease the quantity in field TRKGRSIZ to 0
(zero). When this event occurs, you must delete all
members that use this CLLI code before you
decrease the quantity to 0.
Enter 10 for a DRAM or EDRAM of 4 minues. Enter 33
for an EDRAM of 16 minutes.
You must define an announcement CLLI
Audiogram Delivery Services (ADS). If the ADS
has only one EDRAM card, you can set the field
TRKGRSI to 30. This action allows all 30 channels
on the EDRAM card to connect at the same time.
These channels connect to play ADS OOSPs. See
the Audiogram Delivery Services-Offer of Service
Prompt functionality (ENSV0013) in this document.
-----------------------------------------------------------------------------------------
-continued-
-----------------------------------------------------------------------------------------
Field Descriptions for Table CLLI (continued)
Field or Subfield Entry Explanation
-----------------------------------------------------------------------------------------
ADMININF alphanumeric Administrative Information
(vector of a
maximum of Enter operating company administration
32 characters) information. The switch does not use the
information in this field.
Note: Use only alphabetical characters, numeric
characters, and _ (underscores) to enter data in
this field. The use of other special characters, like
@, #, $, %, ^, &, *, (, ), -, +, =, /, , ;, :, ?, }, and { can
cause errors in the data in this field.
The following entries are the recommended entries
in field ADMININF for a gateway switch:
* DIR
* MED
* SIG
* SRVCAT
* N6MODE
* MISC
DIR - Direction. This entry is optional datafill for
administration only. If the system requires
specification of the direction, enter the direction of
the traffic in the trunk group. If the system does not
require direction, enter a - (dash) for entry DIR.
MED - Medium. This entry of one character is
optional datafill for administration only. If the
system requires specification of the medium, enter
the medium of the trunk group. The medium is S
for satellite or C for cable. If the system does not
require the medium, enter a - (dash) for entry MED.
If the entries that follow MED do not contain
information, leave MED blank.
SIG - Signaling. This entry of one character
is optional datafill for administration only.
If the system requires specification of the signaling
type, enter the signaling type for the trunk group.
The signaling type is 5 for CCITT Signaling No. 5 (N5)
and 6 for CCITT Signaling No. 6 (N6). If the system does
not require specification of the signaling type, enter
a - (dash) for entry SIG. If the entries that follow
entry SIG do not contain information, leave SIG blank.
SRVCAT - Service Category. This entry of three
characters is optional datafill for administration only.
If the system requires specification of the service
category, enter the type of service the trunk group
provides. The type of service is TEL for telephone.
If the system does not require specification of the
service category, enter a - (dash) in entry SRVCAT.
If the entries that follow entry SRVCAT do not contain
information, leave SRVCAT blank.
-----------------------------------------------------------------------------------------
-continued-
-----------------------------------------------------------------------------------------
Field Descriptions for Table CLLI (continued)
Field or Subfield Entry Explanation
-----------------------------------------------------------------------------------------
NO6MODE - Signaling 6 Mode. This entry of four
characters is optional datafill for administration
only. If the system requires specification of the N6
mode, enter the following:
* FA for fully associated
* QA for quasi-associated
* FQ for fully and quasi-associated
This entry can identify which route set or signaling
link set carries the signal for this trunk group. If the
system does not require specification of the N6
mode, enter a - (dash) for entry NO6MODE. If the
entries that follow entry NO6MODE do not contain
information, leave MO6MODE blank.
MISC - Miscellaneous Information. This entry of
12 characters is optional datafill for administration
only. If the system requires miscellaneous
information, you can enter any data in this field.
For example, the entry can contain the full name of
the abbreviated site name. If the system does not
require this entry, leave MISC blank.
Note: The field ADMININF can occupy 32
characters. The system treats this field like a
character string. The field ends at the first blank
character. You must enter an _ (underscore)
between each entry in field ADMININF, if the
entries that follow this entry are not blank.
The recommended entries for field ADMININF for
other than a gateway switch are TRAFCLS,
OFFCLS, and TRKGRTYP.
TRAFCLS - Trunk Group Traffic Class. This
entry is optional datafill for administration only.
If the system requires specification of traffic class,
enter one of the traffic classes that operating company
practices define. If the system does not require
specification of traffic class, enter a - (dash) for
entry TRAFCLS.
OFFCLS - Office Class. This entry is optional
datafill for administration only. If the system
requires specification of office class, enter one of
the office classes that operating company
practices define. If the system does not require
specification of office class, enter a - (dash) for
entry OFFCLS. If entry TRKGRTYP is blank, entry
OFFCLS can be blank.
-----------------------------------------------------------------------------------------
-continued-
-----------------------------------------------------------------------------------------
Field Descriptions for Table CLLI (continued)
Field or Subfield Entry Explanation
-----------------------------------------------------------------------------------------
TRKGRTYP - Trunk Group Type. This entry is
optional datafill for administration only. The
system can require specification of the trunk group
type. When this event occurs, enter an
alphanumeric entry equal to one of the trunk group
types that the operating company practices define.
If the system does not require specification of trunk
group type, leave TRKGRTYP blank.
Note 1: The field ADMININF can occupy 32
characters. The system treats this field like a
character string. The field ends at the first blank
character. You must enter an _ (underscore)
between each entry in field ADMININF, if the
entries that follow this field are not blank.
Note 2: For feature AE0901 for BT7, the entry
EMERGENCY_CALL_ANN in this field specifies
that an emergency call announcement will occur.
-----------------------------------------------------------------------------------------
-End-
Datafill Example
An example of datafill for table CLLI for a North American local, toll, or combined local & toll DMS-100 switch appear in the following figure:
----------------------------------------------------------------------------------------- Datafill Example for Table CLLI ----------------------------------------------------------------------------------------- Example of a MAP display: CLLI ADNUM TRKGRSIZ ADMININF ______________________________________________ HLFXNS0101T 100 24 PH_43_IT OTWAON23CG00 101 225 FG_45_DTS OTWAON23CG00 102 30 CO_54_CA OTWAON2323H1 103 150 LA_54_LA CF3P 54 12 MI ESUP1 55 128 MI TERM102T 57 1 MI TERM102L 58 0 MI TERM100Q 59 0 MI SCKT 60 0 MI OCKT 61 0 MI ASCS 62 0 MI FBOT 51 0 MI LKOUT 52 0 MI IDLE 53 0 MI CF6P 56 12 MI ______________________________________________
The associated datafill of table TRKNAME appears in the following figure:
----------------------------------------------------------------------------------------- Datafill Example for Table TRKNAME ----------------------------------------------------------------------------------------- Example of a MAP display: ADNUM CLLI ______________________________________________ 51 FPOT 52 LKOUT 53 IDLE 54 CF3P 55 ESUP1 56 CF6P 57 TERM102T 58 TERM102L 59 TERM100Q 60 SCKT 61 OCKT 62 ASCS 100 HLFXNS0101T0 101 OTWAON23CG00 102 OTWAON23CG01 103 OTWAON2323H1 ______________________________________________
An example of datafill for a gateway DMS switch appears in the following figure:
----------------------------------------------------------------------------------------- Datafill Example for Table CLLI ----------------------------------------------------------------------------------------- Example of a MAP display: CLLI ADNUM TRKGRSIZ ADMININF _______________________________________________________ MOS01URS 300 2 BS5TEL_MOSCOW MOL03GBNLON 301 52 OC5TEL_MOLLISON CF3P 51 12 MI ESUP1 52 128 MI TERM102T 53 1 MI TERM102L 54 0 MI TERM100Q 55 0 MI ALL 56 2 SATOVER_CLLI MF300 57 250 MF_RECEIVERS DGT300 58 100 DIGITONE_RCVRS _______________________________________________________
An example of datafill for feature AE0901 in BT7 appears in the following figure:
----------------------------------------------------------------------------------------- Datafill Example for Table CLLI ----------------------------------------------------------------------------------------- Example of a MAP display: CLLI ADNUM TRKGRSIZ ADMININF ___________________________________________________________ EMERCALL 124 3 EMERGENCY_CALL_ANN ___________________________________________________________
Description of Previous Examples
Switches that have three-port conference circuits require this pseudo fixed CLLI code CF3P. The trunk group size is equal to three times the number of conference circuits assigned in table CONF3PR. One trunk group is present for each port.
Switches that are not gateway, and have less than 1024 digital echo suppressors require this pseudo fixed code ESUP1. The trunk group size is equal to two times the number of digital echo suppressors assigned to this code in table ECHOSUP. One trunk group is present for each port.
Switches that have the terminating 102 test lines require CLLI codes TERM102T, TERM102L, and TERM100Q. You must enter the CLLI codes in table TRKGRP (type TTL2). This table defines the dB level and supervision.
Trunk group size for CLLI code TERM102T is equal to 1. You can assign only 1 mW trunk for each dB level in table TRKMEM. Trunk group size for CLLI codes TERM102L and TERM100Q is equal to 0 (zero). This condition applies because trunks are assigned in table TRKMEM.
The pseudo fixed CLLI codes SCKT and OCKT are associated with the transmission termination trunk group. This trunk group is in a local or combined local/toll switch.
Trunk group size for CLLI code SCKT is equal to the number of transmission termination trunk circuits table CLLI allocates. Trunk group size for CLLI code OCKT is equal to 0 (zero).
The system requires this pseudo fixed CLLI code ASCS in a local or a combined local/toll switch. One of the following conditions must apply to the switch:
The system requires the Foreign Potential Test Code (FPOT) in a local or combined local and toll switch. The FPOT must be one of the routes in the route lists for partial dial time-out and permanent signal time-out treatments for lines. This condition applies if the system requires a foreign potential test.
The system requires line lockout (LKOUT) and idle (IDLE) codes in a North American local or combined local and toll switch.
One of these codes must be the last route in the route lists associated with the treatments for lines. You must not use the code IDLE in an international switch.
Switches that have six-port conference circuits require this pseudo fixed code CF6P. The trunk group size is equal to six times the number of six-port conference circuits.
Some DMS-300 gateway switches require the pseudo fixed code ALL. These switches permit an incoming trunk group that receives signaling by satellite to connect to an outgoing trunk group that transmits signals by satellite.
The DMS-300 gateway switches that have digital Digitone receivers and digital or analog multifrequency (MF) receivers require the following pseudo fixed CLLI codes:
Table CLLI for BT7
For feature AE0901 for BT7, table CLLI must contain the entry EMERCALL in the field CLLI. This entry specifies the emergency call feature. Table CLLI must contain the entry EMERGENCY_CALL_ANN in the field ADMININF. This entry specifies that an emergency call announcement will occur.