Page 1 Critical Release Notice Publication number: 297-8331-815 Publication release: Standard 10.02 The content of this customer NTP supports the SN06 (DMS) and ISN06 (TDM) software releases. Bookmarks used in this NTP highlight the changes between the baseline NTP and the current release.
Page 2 Changes in section “Remote Switching Center Multi-access (RSC-M)” due to CR Q00693785: • Change of range of FRAME parameter in “Datafilling table GPPTRNSL” • Additional error message in “Error messages for table GPPTRNSL” Change of phone number for Nortel Networks documentation support from 1-800-684-2273 to 1-877-662-5669, Option 4 + 1.
Page 3 297-8331-815 DMS-100 Family Extended Peripheral Module International Translations Reference Manual XPM12 and up Standard 10.01 August 1999...
Page 5 The information contained herein is the property of Nortel Networks and is strictly confidential. Except as expressly authorized in writing by Nortel Networks, the holder shall keep all information contained herein confidential, shall disclose the information only to its employees with a need to know, and shall protect the information, in whole or in part, from disclosure and dissemination to third parties with the same degree of care it uses to protect its own confidential information, but with no less than reasonable care.
Page 7: Table Of Contents
Contents About this document When to use this document vii How to check the version and issue of this document vii References in this document vii What precautionary messages mean viii How commands, parameters, and responses are represented ix Input prompt (>) ix Commands and fixed parameters ix Variables ix Responses ix...
Page 8 iv Contents Activating the RSC-S 3-10 When to update the RCO2 static data 3-10 Alarms produced when a static data mismatch occurs 3-10 Tuple changed (TUPC) logs for static data updates 3-11 Types of TUPC logs 3-11 TUPC log format 3-11 Basic call processing 3-13 ESA lines and trunks 3-107 PCM-30 R1 Trunking 3-126...
Page 9 Contents v Updating static data 5-9 Static data update 5-9 Bulk data update 5-11 Dynamic data update 5-12 Remote Switching Center Multi-access (RSC-M) 5-14 Index DMS-100 Family XPM International Translations Reference Manual XPM12 and up...
Page 11: About This Document
About this document When to use this document How to check the version and issue of this document The version and issue of the document are indicated by numbers, for example, 01.01. The first two digits indicate the version. The version number increases each time the document is updated to support a new software release.
Page 12: What Precautionary Messages Mean
SERVORD Reference Manual Translations Guide What precautionary messages mean The types of precautionary messages used in Nortel Networks documents include attention boxes and danger, warning, and caution messages. An attention box identifies information that is necessary for the proper performance of a procedure or task or the correct interpretation of information or data.
Page 13: How Commands, Parameters, And Responses Are Represented
About this document ix CAUTION Possibility of service interruption or degradation CAUTION Possible loss of service Before continuing, confirm that you are removing the card from the inactive unit of the peripheral module. Subscriber service will be lost if you remove a card from the active unit.
Page 14 x About this document The following excerpt from a procedure shows the command syntax used in this document: Manually busy the CTRL on the inactive plane by typing >BSY CTRL ctrl_no and pressing the Enter key. where ctrl_no is the number of the CTRL (0 or 1) Example of a MAP response : FP 3 Busy CTRL 0: Command request has been submitted.
Page 15: Xpm International Translations Introduction
XPM International Translations Introduction This extended peripheral module (XPM) translations reference manual provides the following information: product overview translations datafill procedures description of basic and optional XPM feature abilities description of how specified tables activate, deactivate, or alter product abilities for Remote Switching Center-SONET (Synchronous Optical Network) (RSC-S) international systems Section 3 describes translation table datafill for international systems.
Page 17: Introduction To Data Tables
Introduction to data tables The translations database contains many data tables. Each table has a purpose and contains a specified type of data. When you enter datafill, you enter specified data in a table. The following section describes the structure of data tables.
Page 18: Using The Table Editor
2-2 Introduction to data tables Examples of table, subtable and sub-subtable TABLE Field names and/or numbers ..DATA DATA DATA DATA DATA DATA ..DATA DATA DATA SUBTABLE Cursor movement Field names and/or numbers (same for all tables .
Page 19: Procedures For Datafilling Any System
Introduction to data tables 2-3 The TE allows users to perform the following functions: add, delete or change tuples or fields in a table or subtable list one or more tuples of a table or subtable move the cursor to display a tuple in a table or subtable display specified valid field values search for tuples that contain specified field values Procedures for datafilling any system...
Page 20: Nonprompt Mode
2-4 Introduction to data tables Nonprompt mode WARNING Possible loss of service if you use the NONPROMPT mode In tables with fields with multiple entries, like OPTCARD, EXECTAB, CSLINKTAB and PSLINKTAB, do not use the NONPROMPT mode of datafill. When you use the NONPROMPT mode, enter all datafill of a field in one entry.
Page 21 Introduction to data tables 2-5 Table editor commands The following table lists TE commands. The table provides a description for each command. The table provides parameters of each command. Table editor commands Command Description TABLE table name Opens the table table name . Adds the tuple given as a parameter to the table.
Page 22 2-6 Introduction to data tables Table editor commands (continued) Command Description LIST n or all condition Displays one or more tuples of the current table, as follows: n is the number of tuples to display. This display starts with the current tuple.
Page 23 Introduction to data tables 2-7 Table editor commands (continued) Command Description VERify ON or OFF Sets a verify mode. This mode delays performance of following commands. This mode lets you check the display, as follows: ON causes the system to prompt you to confirm that the tuple addition, change, replacement or deletion data is correct.
Page 25: Remote Switching Center-Sonet International
Remote Switching Center-SONET International Understanding RSC-S International translations You must understand the RSC-S concepts and terminology before you enter data in the Remote Switching Center-SONET (RSC-S) product. This chapter describes the product in general terms as a background to enter data in the RSC-S.
Page 26: Revised System Architecture
3-2 Introduction to RSC-S International Revised system architecture The RSC-S design is like the common peripheral module (CPM) architecture. The CPM replaces the current expanded peripheral modules (XPM) for host and remote applications. The CPM is a family of peripheral modules (PM) that the DMS-100 family uses.
Page 27: Cabinetized Remote Switching Center (Crsc) Cabinet
Introduction to RSC-S International 3-3 The RSC-S can contain the following: a maximum of two CRSC cabinets a minimum of one cabinetized power distribution centers (CPDC) one cabinetized extension module (CEXT) a maximum of five cabinetized line concentrating equipment (CLCE) cabinets a minimum of one cabinetized miscellaneous equipment (CMIS) cabinets...
Page 28: Crsc Extension (Cext) Cabinet
3-4 Introduction to RSC-S International The CRSC cabinet appears in the following figure. Cabinetized remote switching center cabinet CRSC cabinet—NTMX89 MSP (NTRX40) LCME (NTBX31) LCME (NTBX31) RMM (NT6X13) RCO2 CRSC extension (CEXT) cabinet A single-configuration RSC-S can have one CEXT cabinet that contains one: extension shelf (EXT) LCME...
Page 29: Cabinetized Line Modules (Clce)
Introduction to RSC-S International 3-5 Cabinetized line modules (CLCE) A single-configuration RSC-S can have a maximum of five CLCE cabinets. Each CLCE cabinet supports a maximum of two completely duplicated LCMs. Each duplicated LCM provides a 640-line card capacity. The CLCE cabinet appears in the following figure.
Page 30: Rsc-S Configurations
3-6 Introduction to RSC-S International Electronic business sets (EBS) and P-phones ISDN basic rate interface attendant console Custom Local Area Signaling Services (CLASS) The CPM in the same module can support the following. This CPM can support ISDN primary rate interface (PRI). The PRI includes functional stimulus and Meridian feature transparency.
Page 31 Introduction to RSC-S International 3-7 Basic single-configuration RSC-S without ISDN Messaging links Network DS30 links PLGC / LGCO PCM-30 links Host RSC-S C-side RCO2 P-side DS30A PCM-30 DS30A links links links CDO, PBX LCME DMS-100 Family XPM International Translations Reference Manual XPM12 and up...
Page 32 3-8 Introduction to RSC-S International Basic single-configuration RSC-S with ISDN Messaging links Network DS30 PCM-30 links links Packet B sub-d PLGC / LGCO handler channel PCM-30 Host links RSC-S C-side RCO2 P-side DS30A PCM-30 DS30A links links links CDO, PBX LCME 297-8331-815 Standard 10.01 August 1999...
Page 33: Preparing To Datafill For Rsc_S_International
Introduction to RSC-S International 3-9 Preparing to datafill for RSC_S_International After BCS36, Northern Telecom delivers Product Computing-Module Loads (PCL) instead of BCS releases or Universal Software Loads (USL). A description of PCLs appears in the following section. PCL—New Software Delivery Vehicle A PCL contains features selected from the development stream software product for a specified application in a specified market.
Page 34: Configurations
3-10 Introduction to RSC-S International Configurations The RSC-S configuration can occur with or without ISDN. An RSC-S configuration has a family of peripherals that are not ISDN. This configuration provides a wide range of services. These services do not include ISDN services. An RSC-S with ISDN provides all the services of the RSC-S.
Page 35: Tuple Changed (Tupc) Logs For Static Data Updates
Introduction to RSC-S International 3-11 At the RCO2 level of the MAP display, the response to the QUERYPM FLT command is the same message as the PM128 log message. The required steps are like the steps to update static data. Tuple changed (TUPC) logs for static data updates With the DMS, the journal file (JF) can track changes to DMS data tables.
Page 36 3-12 Introduction to RSC-S International The important tuple or tuples appear. Note: The TUPC logs can help to track inventory changes. Northern Telecom personnel use TUPC logs to solve field problems. Do not use TUPC logs instead of the JF utility. 297-8331-815 Standard 10.01 August 1999...
Page 37: Basic Call Processing
3-13 Datafilling BAS on RSC-S International 3-13 3-13 Basic call processing Functional group BAS00012 BAS00026 Feature packages NTX145AA Remote Switching Center NTX150AA RSC-Intra RSC Calling NTXP92AA RSC-S Basic NTXK77AA PCM-30 RSCO-S Support Release applicability XPM05 and higher Requirements Basic call processing requires the following feature packages: NTXR42AA Firmware Downloading NTX000AA Bilge NTX001AA Common Basic...
Page 38 3-14 Datafilling BAS on RSC-S International Basic call processing (continued) Description This description contains tables that apply directly to basic call processing. For details on call translations, refer to the Translations Guide. Basic call processing tables provide entries for: DMS recognition of the switching unit and all remote locations physical device location identification data link assignments for the RCO2 and peripherals recovery...
Page 39 Datafilling BAS on RSC-S International 3-15 Basic call processing (continued) Recovery Table PMLOADS stores the device location of every peripheral module (PM) load file. The table stores the location to map between load names and devices on which the loads reside. Autoload can locate load files without intervention of personnel.
Page 40 3-16 Datafilling BAS on RSC-S International Basic call processing (continued) Negate partial ground diagnostics If the suffix of the NT6X18 card is -AA or -AB, the system identifies the line as ground start (GND equals Y in table LNINV). First diagnostics fail. Run the diagnostics.
Page 41 Datafilling BAS on RSC-S International 3-17 Basic call processing (continued) Add the SITE option to field CONDITION. Enter field SITE when CONDITION equals SITE. This change affects the following tables when the selector is set to CND: table IBNRTE table OFRT subtable HNPACONT.RTEREF subtable FNPACONT.RTEREF The SITE condition allows a call to transfer to a route list or an element in a...
Page 42 3-18 Datafilling BAS on RSC-S International Basic call processing (continued) Datafilling data in table OFRT (continued) Subfield or Field Entry Description refinement RTESEL Route selector. The CND sets conditional routing. CNDSEL refer to Condition select. This field contains the refinements condition selector CNDSEL.
Page 43 Datafilling BAS on RSC-S International 3-19 Basic call processing (continued) Datafilling data in table OFRT (continued) Subfield or Field Entry Description refinement INTERLATA Index into table TRKLATA to obtain originating LATA of calling number. Index into table LATAXLA of called number to determine inter-LATA or intra-LATA status.
Page 44 3-20 Datafilling BAS on RSC-S International Basic call processing (continued) Datafilling data in table OFRT (continued) Subfield or Field Entry Description refinement CONDRTE refer to If a match selects the following subfields in subfields CNDSEL, these subfields: RTETYPE, RTEREF, SKIPNUM, EXTREID, TABNAME and INDEX define the conditional route.
Page 45 Datafilling BAS on RSC-S International 3-21 Basic call processing (continued) Entry example for table OFRT Sample entries for table OFRT appears in the following example. MAP display example for table OFRT RTELIST _____________________________________________________________________ T120)$ 2 (S D T60 (S D LKOUT) $ 3 (S D BLDNANNC) (S D T120) (S D LKOUT)
Page 46 3-22 Datafilling BAS on RSC-S International Basic call processing (continued) Route to specified table at specified index If a call transfers to another route list in table OFRT, complete fields RTETYPE and EXTREID. To complete field RTETYPE, enter T as the route type.
Page 47 Datafilling BAS on RSC-S International 3-23 Basic call processing (continued) The following procedure provides field definitions for table IBNRTE. The fields that apply directly to basic call processing appear in the procedure. Refer to the data schema section of the Translations Guide for a description of the other fields.
Page 48 3-24 Datafilling BAS on RSC-S International Basic call processing (continued) In this example, route list 1, element 1, sends the call to route list 2 if the call origination is HOST. If the call originates at REM1, the DMS sends the call to route list 3.
Page 49 Datafilling BAS on RSC-S International 3-25 Basic call processing (continued) Translations table flow The basic call processing translation process appears in the flowchart that follows the table descriptions. Table CLLI identifies the far end of the trunk group by: the name of the city or town the state or province the building group the destination of the traffic unit...
Page 50 3-26 Datafilling BAS on RSC-S International Basic call processing (continued) Field SITE in table LCMINV, field SITENM in tables RCCINV and RMMINV, and subfield SITE_ID in table ISTRKGRP must be available to table SITE, field NAME. Table CARRMTC allows DMS switch administration to enter maintenance control information in peripherals, out-of-service (OOS) limits for alarms, and system return-to-service (RTS) occurrences.
Page 51 Datafilling BAS on RSC-S International 3-27 Basic call processing (continued) Table RCCPSINV contains the P-side link assignments for an RCO2. When you add a tuple in table RCCINV, the system adds a corresponding tuple in table RCCPSINV. Table RCCPSINV uses field LOAD to identify load information.
Page 52 3-28 Datafilling BAS on RSC-S International Basic call processing (continued) Table TRKSGRP lists additional information for each subgroup assigned to one of the trunk groups that appear in table TRKGRP. Field CLLI in table TRKSGRP corresponds to the CLLI code for the trunk group. Table TRKMEM lists the data for each trunk assigned to one of the trunk groups and subgroups specified in tables TRKGRP and TRKSGRP.
Page 53 Datafilling BAS on RSC-S International 3-29 Basic call processing (continued) operator verification trunks metallic jacks (MJACK) incoming test access trunks Field EXTRKNM in table MTAHORIZ is the external trunk number assigned to the line test unit or the metallic test unit. The EXTRKNM entry must correspond to an entry in table TRKMEM in field EXTRKNM.
Page 54 3-30 Datafilling BAS on RSC-S International Basic call processing (continued) Table flow for basic call processing Table Table Table CLLI PMLOADS CARRMTC CLLI Table LOADNAME CLLI TRKGRP TMPLTNM OPRVCLLI LOAD Table SITE CLLI Table CLLI LTCINV Table NAME LTCNAME TRKSGRP LOAD Table LTCNAME...
Page 55 Datafilling BAS on RSC-S International 3-31 Basic call processing (continued) Activation/deactivation by the end user Basic call processing does not require activation or deactivation by the end user. Billing Basic call processing does not affect billing. Station Message Detail Recording Basic call processing does not affect Station Message Detail Recording.
Page 56 3-32 Datafilling BAS on RSC-S International Basic call processing (continued) Data entry tables for basic call processing Table Purpose of table CLLI Common language location identifier. Codes identify the far end of each announcement, tone, trunk group, test trunk, national milliwatt test lines and service circuit.
Page 57 Datafilling BAS on RSC-S International 3-33 Basic call processing (continued) Data entry tables for basic call processing (continued) Table Purpose of table RMMINV Remote maintenance module inventory. Identifies: RLCM RSC-S or outside plant module (OPM) site with: frame type, frame number, floor, row, frame position, product engineering code (PEC), PM load, and executive program loaded C-side PM...
Page 58 3-34 Datafilling BAS on RSC-S International Basic call processing (continued) Data entry tables for basic call processing (continued) Table Purpose of table MTAMDRVE Metallic test access (MTA) minibar driver. The MTA network is a matrix of vertical and horizontal crosspoints, comparable to a minibar. The crosspoints connect specified vertical connections to horizontal connections in the network.
Page 59 Datafilling BAS on RSC-S International 3-35 Basic call processing (continued) The following table describes the office parameter you use to control SREX test execution. For additional information about office parameters, refer to Office Parameters Reference Manual. For information about SREX scheduling, refer to table REXSCHED in this document.
Page 60 3-36 Datafilling BAS on RSC-S International Basic call processing (continued) Example of OFCENG table MAP display Table OFCENG PARMNAME PARMVAL –––––––––––––––––––––––––––––––––––––––––––––– TALK_BATTERY_ALARM Parameter TALK_BATTERY_ALARM This parameter turns on the automatic audits of the talk battery in LCM/XLCM/LCME/RLCM/OPM/OPAC peripheral modules. When this parameter changes, activation is immediate.
Page 61 Datafilling BAS on RSC-S International 3-37 Basic call processing (continued) Datafilling table CLLI (continued) Subfield or Field Entry Description refinement PROV alphanumeric Province or state. This 2-character code identifies the province or state at the far end of the trunk group. BLDG alphanumeric Building.
Page 62 3-38 Datafilling BAS on RSC-S International Basic call processing (continued) Datafilling table CLLI (continued) Subfield or Field Entry Description refinement OFFCLS alphanumeric Office class. This field is optional and is for or – for no administrative purposes. When field entry TRKGRTYP is blank, OFFCLS can be left blank.
Page 63 Datafilling BAS on RSC-S International 3-39 Basic call processing (continued) Datafilling table SITE Table SITE contains data for the switching unit and for the remote locations that use the switching unit. Enter data in table SITE to enable the DMS system to recognize the equipment.
Page 64 3-40 Datafilling BAS on RSC-S International Basic call processing (continued) Datafilling table SITE Subfield or Field refinement Entry Description SITE alphanumeric Site name. Enter the site name assigned to the remote switching unit. The first character must be alphabetical. Site names can contain a maximum of four characters.
Page 65 Datafilling BAS on RSC-S International 3-41 Basic call processing (continued) Datafilling table PMLOADS The following procedure shows the entries for table PMLOADS. Table PMLOADS stores the device location of every PM load file. This permits the DMS-100 switch to locate load files. The XPM loadfile patching introduces the concept of an active loadfile and a backup loadfile.
Page 66 3-42 Datafilling BAS on RSC-S International Basic call processing (continued) Pre-patched XPM loads The following sections describe pre-patched XPM loads. Pre-patched XPM loads background Pre-patched XPM loads (PPXLs) are XPM loadfiles that have corrective patches built in the loadfile. The PPXLs are incremental loads built with patch updates.
Page 67 Datafilling BAS on RSC-S International 3-43 Basic call processing (continued) PPXL naming convention The PPXL file names have “_<date>” appended to the end of the corresponding base load name. For example, a PPXL load file created for base load ECL03BX is called ECL03BX_941129. The base load name always remains the same.
Page 68 3-44 Datafilling BAS on RSC-S International Basic call processing (continued) Upgrading the base load To load a PPXL in an office where the baseload is new to the office, use the following procedure: 1 Copy the base loadfile and the PPXL loadfiles to the disk volumes to be used for PM loads.
Page 69 Datafilling BAS on RSC-S International 3-45 Basic call processing (continued) 6 To set the loadset against the two units of the XPM, type >PATCHER and press the Enter key. >SET loadname PM pm_type device_no unit_no and press the Enter key. where loadname is the name of the loadfile...
Page 70 3-46 Datafilling BAS on RSC-S International Basic call processing (continued) Adding PPXLs to an current PM load lineup To add PPXLs to an XPM load lineup that is present, use the following procedure: 1 Verify that patch_ids for the PPXL are present on the disk volume identified in table PMLOADS, field ACTVOL.
Page 71 Datafilling BAS on RSC-S International 3-47 Basic call processing (continued) 6 To load each unit of the XPM with the PPXL, type >BSY UNIT unit_no and press the Enter key. >LOADPM UNIT unit_no and press the Enter key. >RTS UNIT unit_no and press the Enter key.
Page 72 3-48 Datafilling BAS on RSC-S International Basic call processing (continued) Datafilling table PMLOADS Subfield or Field Entry Explanation and action refinement LOADNAME alphanumeric Peripheral module load name. Enter the XPM load name. The range for the load name is a maximum of 32 characters.
Page 73 Datafilling BAS on RSC-S International 3-49 Basic call processing (continued) Data entry example for table PMLOADS The following example displays sample entries for table PMLOADS. MAP display example for table PMLOADS LOADNAME ACTFILE ACTVOL BKPFILE BKPVOL UPDACT ________________________________________________________ ESA02CM ESA02CM S00DXPM ESA02CM S00DXPM...
Page 74 3-50 Datafilling BAS on RSC-S International Basic call processing (continued) Datafilling table LTCINV Subfield or Field Entry Description refinement LTCNAME refer to Link trunk controller name. Subfields: subfields XPMTYPE and XPMNO. XPMTYPE PLGC XPM type. Enter PLGC. Entry values: PLGC, DTC, LGCO, SMR, SMS, SMU, IDTC, ILGC, ILTC, PDTC, TRCC, DTCI, TMS, and SMA.
Page 75 Datafilling BAS on RSC-S International 3-51 Basic call processing (continued) Datafilling table LTCINV (continued) Subfield or Field Entry Description refinement NMPAIR 0 to 31 Network module pair number. Enter the network link where the PM is assigned, corresponding to PM C-side links 0 through 15. NMPORT 0 to 63 Network module port.
Page 76 3-52 Datafilling BAS on RSC-S International Basic call processing (continued) Datafilling table LTCINV (continued) Subfield or Field Entry Description refinement PEC6X40 alphanumeric The 6X40 equipment PEC. Enter the version of the NT6X40 to be used. EXTINFO EXTENSION_INFO. Note 1: Make changes to fields with multiple entries in the PROMPT mode. In nonprompt mode, leave out current entries.
Page 77 Datafilling BAS on RSC-S International 3-53 Basic call processing (continued) Note 1: in field LOAD and in field E2LOAD represent xxxx alphanumeric entries, for example , in that order. XE01 Note 2: If the shelf has a processor other than NTMX77 or the optional NTAX74, the system enters value NILLOAD in field E2LOAD.
Page 78 3-54 3-54 Datafilling BAS on RSC-S International 3-54 Basic call processing Basic call processing (continued) (continued) Datafilling table CARRMTC Table CARRMTC allows DMS switch administration to enter maintenance control information on peripherals, OOS limits for alarms, and system RTS occurrences. Fields CSPMTYPE and SELECTOR and subfield of ATTR are expanded to include new PM type RCO2 for table CARRMTC.
Page 79 Datafilling BAS on RSC-S International 3-55 Basic call processing (continued) Datafilling table CARRMTC Subfield or Field Entry Explanation and action refinement CSPMTYPE RCO2 C-side node PM type. Enter the PM type of the node on the C-side of the carrier link. TMPLTNM DEFAULT Template name.
Page 80 3-56 Datafilling BAS on RSC-S International Basic call processing (continued) Datafilling table CARRMTC (continued) Subfield or Field Entry Explanation and action refinement LLFAOST 0 to 255 Local loss of frame alignment OOS time. Enter the local loss of frame alignment OOS time. LLFARST 0 to 255 LLFAML...
Page 81 Datafilling BAS on RSC-S International 3-57 Basic call processing (continued) Datafilling table CARRMTC (continued) Subfield or Field Entry Explanation and action refinement RFAIML 0 to 255 Remote frame alignment indication maintenance limit. Enter the remote frame alignment indication maintenance limit. RFAIOL 0 to 255 Remote frame alignment indication OOS limit.
Page 82 3-58 Datafilling BAS on RSC-S International Basic call processing (continued) Datafilling table CARRMTC (continued) Subfield or Field Entry Explanation and action refinement RFAIOL 0 to 255 Remote frame alarm indication OOS limit. Enter the remote frame alarm indication OOS limit. RMAIOST 0 to 255 Remote multiframe alarm indication OOS time.
Page 83 Datafilling BAS on RSC-S International 3-59 Basic call processing (continued) Datafilling table CARRMTC (continued) Subfield or Field Entry Explanation and action refinement SLIPML 0 to 255 Slip maintenance limit. Enter the slip maintenance limit. SLIPOL 0 to 255 Slip OOS limit. Enter the slip OOS limit. SLIPSYNC SLIP SYNC.
Page 84 3-60 Datafilling BAS on RSC-S International Basic call processing (continued) Datafilling table CARRMTC (continued) Subfield or Field Entry Explanation and action refinement SIGNTYPE refer to list Signal type. Enter the signal type. Value ranges: CAS, CASX, CCS, CCSIPML, and D30RCC. Note 1: The DMS system adds the first tuple for RCO2 to table CARRMTC during IPL or first restart after IPL.
Page 85 Datafilling BAS on RSC-S International 3-61 Basic call processing (continued) Datafilling table LTCPSINV Subfield or Field Entry Explanation and action refinement LTCNAME refer to Link trunk controller name. Subfields: subfields XPMTYPE and XPMNO. XPMTYPE PLGC PM type. Must match the entry in subfield XPMTYPE in table LTCINV.
Page 86 3-62 Datafilling BAS on RSC-S International Basic call processing (continued) Datafill example for table LTCPSINV Sample datafill for table LTCPSINV appears in the following example. MAP display example for table LTCPSINV Table: LTCPSINV LTCNAME PSLNKTAB CONTMARK ––––––––––––––––––––––––––––––––––––––––––––––––––––––––––– PLGC 1 (0 D30 D30RCO2 N) (1 D30 D30RCO2 N) (2 D30 D30RCO2 N) (3 D30 D30RCO2 N) (4 D30 DEFAULT N) (5 D30 DEFAULT N) (6 D30 DEFAULT N) (7 D30 DEFAULT N) (8 NILTYPE) (9 NILTYPE) (10 NILTYPE) (11 NILTYPE) (12 NILTYPE) (13 NILTYPE)
Page 87 Datafilling BAS on RSC-S International 3-63 Basic call processing (continued) Datafilling table RCCINV Subfield or Field Entry Explanation and action refinement RCCNAME refer to RCO2 name. Contains subfields SITE, subfields PMTYPE, and RCCNO. SITE alphanumeric Site. Enter the site name assigned to the remote location.
Page 88 3-64 Datafilling BAS on RSC-S International Basic call processing (continued) Datafilling table RCCINV (continued) Subfield or Field Entry Explanation and action refinement EXEC refer to list Executive programs. Enter the execs that associate with the terminal type. Examples are POTSEX, KSETEX, DTCEX, ESAEX, and RSMEX.
Page 89 Datafilling BAS on RSC-S International 3-65 Basic call processing (continued) Datafilling table RCCINV (continued) Subfield or Field Entry Explanation and action refinement OPTCARD see list Optional card. This is a vector of a maximum of 10 entries. For the RCO2, slot 4 must be used for the ISDN signaling pre-processor (ISP) card.
Page 90 3-66 Datafilling BAS on RSC-S International Basic call processing (continued) Datafilling table RCCINV (continued) Subfield or Field Entry Explanation and action refinement CMRLOAD alphanumeric CLASS modem resource load. If the CMR card is used the card must be followed by the CMR loadname.
Page 91 Datafilling BAS on RSC-S International 3-67 Basic call processing (continued) Datafilling table RCCINV (continued) Subfield or Field Entry Explanation and action refinement EXTSHELF Y or N Extension shelf. Enter Y if the CPM has an extension shelf. If Y, the refinements to this field are listed below.
Page 92 3-68 Datafilling BAS on RSC-S International Basic call processing (continued) Datafill example for table RCCINV The NTMX77AA UP appears in the following example. Sample datafill for table RCCINV for an RCO2 that has the optional NTAX74AA CAP appears in following examples. MAP display example for table RCCINV datafilled for NTMX77AA UP Table: RCCINV RCCNAME...
Page 93 Datafilling BAS on RSC-S International 3-69 Basic call processing (continued) MAP display example for table RCCINV datafilled for NTAX74AA CAP Table: RCCINV RCCNAME FRTYPE FRNO SHPOS FLOOR ROW FRPOS EQPEC LOAD ––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––– MELB RCO2 0 1101 CRSC MX85AA WRI07xx EXECTAB CONTMARK –––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––...
Page 94 3-70 Datafilling BAS on RSC-S International Basic call processing (continued) Error messages for table RCCINV (continued) Error message Explanation and action A user tried to delete an extension Delete P-side links prior to shelf that has P-side links entered in deleting the extension table RCCPSINV.
Page 95 Datafilling BAS on RSC-S International 3-71 Basic call processing (continued) the data schema section of the Translations Guide for a description of the other fields. Datafilling table RCCPSINV Subfield or Field Entry Explanation and action refinement RCCNAME refer to Remote cluster controller name. Enter the RCC subfields name.
Page 96 3-72 Datafilling BAS on RSC-S International Basic call processing (continued) Table: RCCPSINV RCCNAME PSLNKTAB ––––––––––––––––––––––––––––––––––––––––––––––––––––––––––– MELB RCO2 0 (0 NILTYPE) (1 NILTYPE) (2 NILTYPE) (3 NILTYPE) (4 NILTYPE)(5 NILTYPE) (6 NILTYPE) (7 NILTYPE) (8 NILTYPE) (9 DCH) (10 NILTYPE) (11 NILTYPE) (12 NILTYPE) (13 NILTYPE) (14 NILTYPE) (15 DS30A) (16 NILTYPE) (17 DCH) (18 NILTYPE) (21 DS30A) (22 DS30A) (23 DS30A) (24 DS30A) (25 DS30A) (26 DS30A) (27 DS30A) (28 DS30A)
Page 97 Datafilling BAS on RSC-S International 3-73 Basic call processing (continued) Datafilling table LCMINV Table line concentrating module inventory (LCMINV) lists data assignments for each bay that associate with a local or remote LCM unit. The SITE is the only field different for the RSC-S configuration. The datafill for table LCMINV appears in the following example.
Page 98 3-74 Datafilling BAS on RSC-S International Basic call processing (continued) Datafilling table LCMINV (continued) Subfield or Field Entry Explanation and action refinement LOAD alphanumeric Load. Enter the load for the LCM. CSPMNO see subfields C-side PM. Subfields: PMTYPE and XPMNO. RCO2 PM type.
Page 99 Datafilling BAS on RSC-S International 3-75 Basic call processing (continued) Datafilling table LCMINV (continued) Subfield or Field Entry Explanation and action refinement RNGTYPE see list Ringing type. Refinements: RNGCADENCE, FREQUENCIES, and PROMVOLT. LCDI_INFO 0 to 53 Line concentrating device ISDN information. A maximum of 18 vectors of link numbers (0 to 53) of the C-side peripheral (RCO2).
Page 100 3-76 Datafilling BAS on RSC-S International Basic call processing (continued) DS30A link relationship (continued) Chip number DS30A link numbers 30, 31, 32, 33 34, 35, 36, 37 38, 39, 40, 41 42, 43, 44, 45 46, 47, 48, 49 50, 51, 52, 53 —end—...
Page 101 Datafilling BAS on RSC-S International 3-77 Basic call processing (continued) Error message for table LCMINV Error message Explanation and action This message indicates that the RCO2 is connected to an RCO2 can connect to an LCM or LCM/LCME only. LCME (phase one) on P-side links. Datafilling table RMMINV Table remote maintenance module inventory (RMMINV) identifies an RLCM, RSC-S, or OPM site with the frame type, frame number, floor or...
Page 102 3-78 Datafilling BAS on RSC-S International Basic call processing (continued) Datafilling table RMMINV (continued) Subfield or Field Entry Explanation and action refinement FRTYPE refer to list Frame type. Enter CRSC for the RCO2 shelf. Enter CEXT for the RCO2 extension shelf. For an RLCM, enter RLCM.
Page 103 Datafilling BAS on RSC-S International 3-79 Basic call processing (continued) Datafill example for table RMMINV Sample datafill for table RMMINV appears in the following example. MAP display example for table RMMINV Table: RMMINV RMMNAME FRTYPE FRNO SHPOS FLOOR ROW FRPOS –––––––––––––––––––––––––––––––––––––––––––––––––––...
Page 104 3-80 Datafilling BAS on RSC-S International Basic call processing (continued) Datafilling table LNINV Table line circuit inventory (LNINV) defines the site, line equipment number, and associated data for each line card circuit. Then SERVORD can add or delete table LNINV line datafill for remote fiber terminal (RFT) lines in an S/DMS AccessNode system.
Page 105 Datafilling BAS on RSC-S International 3-81 Basic call processing (continued) Datafilling table LNINV (continued) Subfield or Field Entry Explanation and action refinement Y or N Manual override. Enter Y when the on-hook balance network test cannot update field BNV in this table.
Page 106 3-82 Datafilling BAS on RSC-S International Basic call processing (continued) Datafilling table TRKGRP Subfield or Field Entry Explanation and action refinement GRPKEY refer to Group key. Subfield: CLLI. subfield CLLI alphanumeric CLLI. Enter the CLLI code for the trunk group assigned in table CLLI.
Page 107 Datafilling BAS on RSC-S International 3-83 Basic call processing (continued) Datafill example for table TRKGRP Sample datafill for table TRKGRP appears in the following example. MAP display example for table TRKGRP Table: TRKGRP GRPKEY GRPINFO ––––––––––––––––––––––––––––––––––––––––––––––––––– VER90 MAINT 0 NPDGP NCRT 2X90AB MAINT IAO NCRT...
Page 108 3-84 Datafilling BAS on RSC-S International Basic call processing (continued) Datafilling table TRKSGRP Subfield or Field Entry Explanation and action refinement SGRPKEY see subfields Subgroup key. Subfields: CLLI and SGRP. CLLI alphanumeric CLLI. This subfield contains the code assigned in table CLLI to the trunk group where the subgroup belongs.
Page 109 Datafilling BAS on RSC-S International 3-85 Basic call processing (continued) Datafilling table TRKSGRP (continued) Subfield or Field Entry Explanation and action refinement SGRPVAR CCONT Coin control. For maintenance and test trunks, (continued) the entry is MW (multiwink). RNGBCK Ringback. For maintenance and test trunks, the entry is IB (inband).
Page 110 3-86 Datafilling BAS on RSC-S International Basic call processing (continued) MAP display example for table TRKSGRP Table: TRKSGRP SGRPKEY CARDCODE SGRPVAR ––––––––––––––––––––––––––––––––––––––––––––––––––– VER90 0 2X90AB STD OG 0 0 NO NO F N N TTT 0 2X96AA STD OG 0 0 NO NO F N 17 LTU 0 2X11AA STD OG...
Page 111 Datafilling BAS on RSC-S International 3-87 Basic call processing (continued) Datafilling table TRKMEM Subfield or Field Entry Explanation and action refinement CLLI alphanumeric CLLI. Enter the code assigned in table CLLI to the trunk group where the trunk is a member. EXTRKNM 0 to 9999 External trunk name.
Page 112 3-88 Datafilling BAS on RSC-S International Basic call processing (continued) MAP display example for table TRKMEM Table: TRKMEM CLLI EXTRKNM SGRP MEMVAR ––––––––––––––––––––––––––––––––––––––––––––––––––– RCO20TI RCO2 0 RCO20T2 RCO2 0 Datafilling table ALMSCGRP Table alarm scan group (ALMSCGRP) records the circuit equipment, location, and type of circuit pack that contains scan points.
Page 113 Datafilling BAS on RSC-S International 3-89 Basic call processing (continued) Datafill example for table ALMSCGRP Sample datafill for table ALMSCGRP appears in the following example. MAP display example for table ALMSCGRP Table: ALMSCGRP SCGROUP TMTYPE TMNO TMCKTNO CARDCODE –––––––––––––––––––––––––––––––––––––––– 3X82AA 3X82AA 3X84AA 0X10AA...
Page 114 3-90 Datafilling BAS on RSC-S International Basic call processing (continued) Datafill example for table ALMSDGRP Sample datafill for table ALMSDGRP appears in the following example. MAP display example for table ALMSDGRP Table: ALMSDGRP SDGROUP TMTYPE TMNO TMCKTNO CARDCODE –––––––––––––––––––––––––––––––––––––––– 3X82AA 3X82AA 3X84AA 2X57AA...
Page 115 Datafilling BAS on RSC-S International 3-91 Basic call processing (continued) Datafilling table ALMSD Subfield or Field Entry Explanation and action refinement FUNCTION alphanumeric Function. Enter the alarm function. SDGROUP 0 to 255 Signal distributor group. Enter the signal distributor group to which the SD point belongs. POINT 0 to 7 Signal distributor point.
Page 116 3-92 Datafilling BAS on RSC-S International Basic call processing (continued) Datafilling table ALMSC The function each of the assigned scan points in the alarm scan groups appears in table alarm scan (ALMSC). Refer to the data schema section of the Translations Guide for a description of the other fields. Datafilling table ALMSC Subfield or Field...
Page 117 Datafilling BAS on RSC-S International 3-93 Basic call processing (continued) Datafilling table ALMSC (continued) Subfield or Field Entry Explanation and action refinement LOGIC ALMXFR Y or N Alarm transfer. Enter Y if the alarm is activated (continued) when the alarm transfer key is activated. Otherwise, enter N.
Page 118 3-94 Datafilling BAS on RSC-S International Basic call processing (continued) Datafilling table MTAMDRVE The metallic test access (MTA) network is a matrix of vertical and horizontal crosspoints. This matrix is like a minibar that connects verticals to horizontals in the MTA. The MTA tests equipment. The horizontal connections in the MTA connect the test equipment to the vertical connections where the circuit lines attach.
Page 119 Datafilling BAS on RSC-S International 3-95 Basic call processing (continued) Table MTA minibar driver (MTAMDRVE) specifies the location and the type of minibar driver assigned to the minibar switch. The NT2X50AB driver is part of the NT2X46 minibar switch. The NT3X09 driver has relays on the card and does not require an associated minibar switch.
Page 120 3-96 Datafilling BAS on RSC-S International Basic call processing (continued) The datafill for table MTAMDRIVE appears in the following example. Refer to the data schema section of the Translations Guide for a description of the other fields. Datafilling table MTAMDRIVE Subfield or Field Entry...
Page 121 Datafilling BAS on RSC-S International 3-97 Basic call processing (continued) MAP display example for table MTAMDRIVE Table: MTAMDRVE MTAMEM VERT HORIZ TMTYPE TMNO TMCKNO MTACARD ––––––––––––––––––––––––––––––––––––––––––––––––––– 3X09AA 3X09AA 3X09AA Datafilling table MTAVERT The metallic test access vertical connection table identifies the vertical connectivity to the MTA matrix.
Page 122 3-98 Datafilling BAS on RSC-S International Basic call processing (continued) Datafilling table MTAVERT (continued) Subfield or Field Entry Explanation and action refinement FRAME Frame number. Enter the frame number. UNIT 0 or 1 Unit number. Enter the unit number. CONTMARK + or $ Continuation mark.
Page 123 Datafilling BAS on RSC-S International 3-99 Basic call processing (continued) A maximum of 32 MTAMs can be multiplied (grouped) to connect to a horizontal agent. A horizontal agent can only be used once. The datafill for table MTAHORIZ appears in the following example. This procedure only contains fields that apply to .
Page 124 3-100 Datafilling BAS on RSC-S International Basic call processing (continued) Note 8: An LTU or MTU must be datafilled in table TRKMEM before added to table MTAHORIZ. If the LTU or MTU is deleted from table TRKMEM, the corresponding tuple in table MTAHORIZ is marked as deleted.
Page 125 Datafilling BAS on RSC-S International 3-101 Basic call processing (continued) Datafilling table MTAHORIZ Subfield or Field Entry Explanation and action refinement HORIZ 0 to 127 MTA horizontal. Enter the MTA horizontal where the test equipment (horizontal agent) connects. HORIZGRP 0 to 159 MTA horizontal group.
Page 126 3-102 Datafilling BAS on RSC-S International Basic call processing (continued) Datafilling table MTAHORIZ (continued) Subfield or Field Entry Explanation and action refinement SELECTOR CLLI alphanumeric Common language location identifier. (continued) Enter LTU for line test unit. Enter MTU for metallic test unit. Enter MJACK for metal jack.
Page 127 Datafilling BAS on RSC-S International 3-103 Basic call processing (continued) Datafilling table MTAHORIZ (continued) Subfield or Field Entry Explanation and action refinement MTAGRP HORIZ Read-only field provides information about the (continued) horizontal to which the MTA drivers connect. Enter 0 to satisfy table control. ALTUSE Y or N Automatic line test use.
Page 128 3-104 Datafilling BAS on RSC-S International Basic call processing (continued) The datafill for basic call processing for table REXSCHED appears in the following table. The only fields that are shown apply directly to basic call processing. Refer to the data schema section of the Translations Guide for a description of the other fields.
Page 129 Datafilling BAS on RSC-S International 3-105 Basic call processing (continued) Datafilling table REXSCHED (continued) Subfield or Field Entry Explanation and action refinement DAYSDSBL character DAYSDSBL. List the days when the REX test must not be invoked. The day refers to the start time of the REX test.
Page 130 3-106 Datafilling BAS on RSC-S International Basic call processing Basic call processing (end) (continued) Example of the addition of the NPGD option in the prompt mode >ADO SONUMBER: SR 12345 Q 95 4 13 PM > DN_OR_LEN: >4817251 OPTION: >NPGD OPTION: >$ Example of the addition of the NPGD option in the no-prompt mode...
Page 131: Esa Lines And Trunks
3-107 Datafilling ESA lines and trunks on RSC-S International 3-107 3-107 ESA lines and trunks Functional group BAS00012 Feature package NTX149AA ESA lines and trunks Release applicability XPM05 and later versions Requirements The ESA lines and trunks require the following feature packages to operate: NTX000AA Bilge NTX001AA Common Basic NTX145AA Remote Switching Center...
Page 132 3-108 Datafilling ESA lines and trunks on RSC-S International ESA lines and trunks (continued) ESA, the RSC-S always routes the first party on a multiparty line. The hunts start with the first party. The system can encounter a corrupt emergency service trunk.
Page 133 Datafilling ESA lines and trunks on RSC-S International 3-109 ESA lines and trunks (continued) Meridian Digital Centrex (MDC) customer groups use this data. This table is not in use during normal operation of the RCO2 , and translations occur in the central control (CC).
Page 134 3-110 Datafilling ESA lines and trunks on RSC-S International ESA lines and trunks (continued) RSC_XPMESAEXIT The timeout, RSC_XPMESAEXIT, in Office Parameters Reference Manual, is implemented in ESA-EXIT to protect against links that bounce. This parameter is the informal exit delay parameter. This parameter allows time for a bad link to gain stability after the link recovers.
Page 135 Datafilling ESA lines and trunks on RSC-S International 3-111 ESA lines and trunks (continued) RSC_ESASDUPD_BOOL The RSC_ESASDUPD_BOOL office parameter, in Office Parameters Reference Manual, specifies when static data updates must occur every night. The value can be at the default value of Y. When this condition occurs, the system downloads the static data during the updates that occur every night.
Page 136 3-112 Datafilling ESA lines and trunks on RSC-S International ESA lines and trunks (continued) To determine when the REx occurs, view parameters CC-REX_SCHEDULED_HR and CMC_REX_SCHEDULED_HR in table OFCENG. The CC tests take approximately 12 min to complete and start 15 min after the time set in the parameter. The central message controller (CMC) tests take approximately 15 min to complete and start 5 min after the time set in the parameter.
Page 137 Datafilling ESA lines and trunks on RSC-S International 3-113 ESA lines and trunks (continued) Operation Download data to the RCO2 before the RCO2 enters ESA. The ESA static data is a subset of translation data from the DMS CC. The system generates ESA logs when the downloaded data exceeds the RSC-S ESA maximum.
Page 138 3-114 Datafilling ESA lines and trunks on RSC-S International ESA lines and trunks (continued) Translations table flow The ESA lines and trunks translation process appears in the following flowchart. Table flow for ESA lines and trunks Table RCCINV PMTYPE SITENM RCCNO PMTYPE SITE...
Page 139 Datafilling ESA lines and trunks on RSC-S International 3-115 ESA lines and trunks (continued) Field RCCNAME stores the original site information entered in the field NAME from table SITE, the PM type and the PM number. Limits The following limits apply to ESA lines and trunks: When you enter data in table ESAPXLA for POTS, each RSC-S can have a maximum of 16 entries.
Page 140 3-116 Datafilling ESA lines and trunks on RSC-S International ESA lines and trunks (continued) Office parameters that ESA lines and trunks use Table name Parameter name Description OFCENG RSC_ESASDUPD_BOOL Specifies when updates of static data (continued) must occur every night. Default: YES RSC_ESASDUPD_HOUR Specifies start time for update of ESA static data that occurs every night.
Page 141 Datafilling ESA lines and trunks on RSC-S International 3-117 ESA lines and trunks (continued) Datafilling table RCCINV The remote cluster controller inventory (RCCINV) table contains the inventory data, except P-side link assignments, for the RCO2. The datafill for ESA lines and trunks for table RCCINV appears in the following table.
Page 142 3-118 Datafilling ESA lines and trunks on RSC-S International ESA lines and trunks (continued) Datafilling table RCCINV (continued) Subfield or Field Entry Description refinement EXEC ESAEX Executive programs. Enter the set of executive programs required for the PM specified in the TRMTYPE entry.
Page 143 Datafilling ESA lines and trunks on RSC-S International 3-119 ESA lines and trunks (continued) MAP display example for table RCCINV entered for NTMX77AA CAP Table: RCCINV RCCNAME FRTYPE FRNO SHPOS FLOOR ROW FRPOS EQPEC LOAD ––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––– MELB RCO2 0 CRSC MX85AA KRI07xx EXECTAB...
Page 144 3-120 Datafilling ESA lines and trunks on RSC-S International ESA lines and trunks (continued) MAP display example for data entered in table RCCINV for NTAX74AA CAP Table: RCCINV RCCNAME FRTYPE FRNO SHPOS FLOOR ROW FRPOS EQPEC LOAD ––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––– MELB RCO2 0 CRSC MX85AA WRI07xx...
Page 145 Datafilling ESA lines and trunks on RSC-S International 3-121 ESA lines and trunks (continued) Datafilling table ESAPXLA Subfield or Field Entry Description refinement PXLAKEY refer to Prefix translator key. This key identifies a set of subfields prefix digits on a certain site for a particular set of customers.
Page 146 3-122 Datafilling ESA lines and trunks on RSC-S International ESA lines and trunks (continued) Datafilling table ESAPXLA (continued) Subfield or Field Entry Description refinement RESULT refer to Translation result. This field defines the action subfield to take when the subscriber dials previously defined prefix digits on the remote.
Page 147 Datafilling ESA lines and trunks on RSC-S International 3-123 ESA lines and trunks (continued) Datafilling table ESAPXLA (continued) Subfield or Field Entry Description refinement refer to If selector is R , enter subfields: multiple with subfields the route number (RR) from table ESARTE, for standard trunking translations, number of digits (NUMDIG) to outpulse to outpulse.
Page 148 3-124 Datafilling ESA lines and trunks on RSC-S International ESA lines and trunks (continued) MAP display example for table ESAPXLA Table: ESAPXLA PXLAKEY RESULT –––––––––––––––––––––––––––––––––––––––––––––––––––– ESAPOTS RC02 MELB 411 L MELB00 0 00 02 IBN1 RCO2 MELB REORDER IBN1 RCO2 MELB SRPXLA IBN1 RCO2 MELB SRPDXLA...
Page 149 Datafilling ESA lines and trunks on RSC-S International 3-125 ESA lines and trunks ESA lines and trunks (end) (continued) Datafill example for table CUSTHEAD Sample datafill for table CUSTHEAD appears in the following example. MAP display example for table CUSTHEAD Table: CUSTHEAD CUSTNAME CUSTXLA DGCOLNM OPTIONS –––––––––––––––––––––––––––––––––––––––––––––––––––...
Page 150: Pcm-30 R1 Trunking
3-126 3-126 Datafilling PCM-30 trunks on RSC-S International 3-126 PCM-30 R1 Trunking Functional group BAS00012 Feature package NTXT00AA PCM-30 RSC-S R1 Trunking Release applicability XPM05 and later versions Requirements The PCM-30 R1 Trunking requires the following feature packages: NTXH52AA PCM-30 RSCO Support NTXK77AA PCM-30 RSCO-S Support NTXP92AA RSC-S Basic Description...
Page 151 Datafilling PCM-30 trunks on RSC-S International 3-127 PCM-30 R1 Trunking (continued) Table SITE identifies equipment for the switching unit and remote locations that connect to the unit. You must enter data in this table before you assign LEN or enter data for a PM. The host switching unit is the first entry in field NAME.
Page 152 3-128 Datafilling PCM-30 trunks on RSC-S International PCM-30 R1 Trunking (continued) Table TRKMEM lists the data associated with each trunk assigned to a trunk group and subgroup in tables TRKGRP and TRKSGRP. Table TRKSGRP identifies the circuits associated with static trunks, dynamic trunks, and equipment to test lines and trunks.
Page 153 Datafilling PCM-30 trunks on RSC-S International 3-129 PCM-30 R1 Trunking (continued) Limits The following limits apply to PCM-30 RSC-S R1 Trunking: The P-side of the RCO2 supports a maximum of 46 PCM-30 links. The main shelf has 22 PCM-30 links, and the extension shelf has 24 PCM-30 links.
Page 154 3-130 Datafilling PCM-30 trunks on RSC-S International PCM-30 R1 Trunking (continued) Datafill tables required for PCM-30 R1 Trunking Table Purpose of table CLLI Common language location identifier. Contains codes that identify the far end of announcements, tones, trunk groups, test trunks, national milliwatt test lines, and service circuits.
Page 155 Datafilling PCM-30 trunks on RSC-S International 3-131 PCM-30 R1 Trunking (continued) Datafilling table CLLI The following table shows the data entry for PCM-30 R1 Trunking for table CLLI. The fields that appear apply to PCM-30 R1 Trunking. Refer to the data schema section of the Translations Guide for a description of the other fields.
Page 156 3-132 Datafilling PCM-30 trunks on RSC-S International PCM-30 R1 Trunking (continued) Datafilling table SITE Subfield or Field Entry Explanation and action refinement SITE alphanumeric Site name. Enter the remote switching unit site name. The first character must be alphabetical. Site names can have a maximum of four characters.
Page 157 Datafilling PCM-30 trunks on RSC-S International 3-133 PCM-30 R1 Trunking (continued) Datafilling table PMLOADS Table PMLOADS stores the device location of every PM loadfile to map between load names and devices that contain the loads. The system automatically reloads the PMs that can have a damaged load are automatically reloaded.
Page 158 3-134 Datafilling PCM-30 trunks on RSC-S International PCM-30 R1 Trunking (continued) Datafilling table CARRMTC The data entry for PCM-30 R1 Trunking for table CARRMTC appears in the following table. The fields that appear apply to PCM-30 R1 Trunking. Refer to the data schema section of the Translations Guide for a description of the other fields.
Page 159 Datafilling PCM-30 trunks on RSC-S International 3-135 PCM-30 R1 Trunking (continued) Datafilling table RCCINV Subfield or Field Entry Explanation and action refinement RCCNAME see subfields RCO2 name. The field RCCNAME contains subfields SITE, PMTYPE, and RCCNO. SITE alphanumeric Site. Enter the remote location site name. This entry must appear in table SITE.
Page 160 3-136 Datafilling PCM-30 trunks on RSC-S International PCM-30 R1 Trunking (continued) MAP example for table RCCINV datafilled for NTMX77AA UP Table: RCCINV RCCNAME FRTYPE FRNO SHPOS FLOOR ROW FRPOS EQPEC LOAD –––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––– MELB RCO2 0 CRSC MX85AA KRI07xx EXECTAB (POTS POTSEX)(KEYSET KSETEX)(ABTRK DTCEX) (RMM_TERM RSMEX) (ESALINES ESAEX) CSPM CSLNKTAB...
Page 161 Datafilling PCM-30 trunks on RSC-S International 3-137 PCM-30 R1 Trunking (continued) MAP example for table RCCINV datafilled for NTAX74AA CAP Table: RCCINV RCCNAME FRTYPE FRNO SHPOS FLOOR ROW FRPOS EQPEC LOAD –––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––– MELB RCO2 0 CRSC MX85AA WRI07xx EXECTAB (POTS POTSEX)(KEYSET KSETEX)(ABTRK DTCEX) (RMM_TERM RSMEX) (ESALINES ESAEX) CSPM CSLNKTAB...
Page 162 3-138 Datafilling PCM-30 trunks on RSC-S International PCM-30 R1 Trunking (continued) Datafilling table RCCPSINV Subfield or Field Entry Explanation and action refinement RCCNAME see subfields Remote cluster controller name. Enter the RCC name. Subfields: SITE, PMTYPE, and RCCNO. SITE alphanumeric Site.
Page 163 Datafilling PCM-30 trunks on RSC-S International 3-139 PCM-30 R1 Trunking (continued) MAP example for table RCCPSINV Table: RCCPSINV RCCNAME PSLNKTAB –––––––––––––––––––––––––––––––––––––––––––––––––––––––––– MELB RCO2 0 (0 D30 DEFAULT N) (1 D30 DEFAULT N) (2 D30 DEFAULT N) (3 D30 DEFAULT N) (4 D30 DEFAULT N) (5 D30 DEFAULT N) (6 D30 DEFAULT N) (7 D30 DEFAULT N) (8 NILTYPE) (9 NILTYPE) (10 NILTYPE) (11 NILTYPE) (12 NILTYPE) (48 NILTYPE) (49 NILTYPE) (50 NILTYPE) (51 NILTYPE)
Page 164 3-140 Datafilling PCM-30 trunks on RSC-S International PCM-30 R1 Trunking (continued) MAP example for table TRKGRP Table: TRKGRP GRPKEY GRPINFO ________________________________________________________ MELB TLD NCRT IE MIDL 7 N $ QUEENSLAND + IBNTO 0 ELO NCBN RCO20 0 MIDL ANSDISC + 0 N O 1 8 9 N N N N N N N $ Datafilling table TRKSGRP Table trunk subgroup (TRKSGRP) lists additional information for subgroups...
Page 165 Datafilling PCM-30 trunks on RSC-S International 3-141 PCM-30 R1 Trunking (continued) Datafill example for table TRKSGRP The following is an example of data entry for PCM-30 R1 Trunking in table TRKSGRP. MAP example for table TRKSGRP Table: TRKSGRP SGRPKEY CARDCODE SGRPVAR ________________________________________________________ QUEENSLAND 0...
Page 166 3-142 Datafilling PCM-30 trunks on RSC-S International PCM-30 R1 Trunking PCM-30 R1 Trunking (end) (continued) Datafilling table TRKMEM (continued) Subfield or Field Entry Explanation and action refinement MEMVAR PMTYPE RCO2 Peripheral module type. This field is the PM (continued) type that contains the trunk. Enter RCO2. RCO2NO 0 to 511 RCO2 number.
Page 167: Isdn Operations
3-143 Datafilling ISDN on RSC-S International 3-143 3-143 ISDN operations Functional group BAS00012 BAS00026 Feature package Refer to Basic call processing in the Remote Switching Center-SONET International section of this document. NTX145AA Remote Switching Center NTX150AA RSC Intra-RSC Calling NTXP92AA RSC-S Basic NTXK77AA PCM-30 RSCO-S Support Release applicability This module supports the following BCS releases:...
Page 168 3-144 Datafilling ISDN on RSC-S International ISDN operations (continued) Note: This list of required packages does not include feature packages NTX143AA, NTX150AA, NTX381AA, and NTXP92AA. International support requires the following feature packages: NTXH52AA PCM-30 RSCO Support NTXP92AA RSC-S Basic NTX001AA Common Basic Description The integrated services digital network (ISDN) is provided through the Remote Cluster Controller Offshore #2 (RCO2) module of the Remote...
Page 169 Datafilling ISDN on RSC-S International 3-145 ISDN operations (continued) NI-2 support for Telecom Service Interface Specification (TSIS) of BS interworking and datafill to allow data rate adaptation Profile of basic rate access (BRA) and primary rate interface (PRI) lines The BRA and PRI lines are important categories of ISDN service. The BRA line services use a two-wire loop.
Page 170 3-146 Datafilling ISDN on RSC-S International ISDN operations (continued) Access privileges (AP) The line equipment number (LEN) and terminal identifier (TEI) are associated. At this point, the terminal that connects to the ISDN interface can originate and receive calls. Datafill determines if terminals can have the following access privileges: voice and circuit-switched data on a B-channel (B) low-speed packet-switched data on a D-channel (D)
Page 171 Datafilling ISDN on RSC-S International 3-147 ISDN operations (continued) Attributes of datafill according to AP LTD, AP of B No attributes required LEN/TEI CAP (DN) FAP (options and features) LTID, AP of D DIU/TIM/SIM/AM/PI/PO LAPDX25 packet LEN/TEI/DCHCHNL LTID parameters: LAPDX25 packet parameters: L2 and L3 L2 and L3...
Page 172 3-148 Datafilling ISDN on RSC-S International ISDN operations (continued) ISDN variants using protocol version control (PVC) Static table download from the CC allows PVC options to a generic ISDN software module. The static download indicates if ISDN supports A-Law and variable length directory numbers (DN) for NI–2 compatibility for offshore.
Page 173 Datafilling ISDN on RSC-S International 3-149 ISDN operations (continued) DCH_BD_STATMUX_RATIO Switching units with ISDN require this parameter. This parameter controls the maximum number of logical terminals (LT) that you can multiplex on one Bd channel. Multiplex these LTs in order to route the packet data to the data packet network (DPN).
Page 174 3-150 Datafilling ISDN on RSC-S International ISDN operations (continued) DEFAULT_BEARER_CAPABILITY This parameter defines the default bearer capability (BC) of an office. The default is SPEECH. A change in the default can have an important impact on call completion. If the value changes to 3_1KHZ, investigate table RTECHAR for any entries that use a BC of speech.
Page 175 Datafilling ISDN on RSC-S International 3-151 ISDN operations (continued) Operation Describe the datafill for the RCO2 in terms of physical configuration, service capabilities, and bearer capabilities. Defining the physical configuration Use the following translations tables to identify the hardware components and the connections between the components.
Page 176 3-152 Datafilling ISDN on RSC-S International ISDN operations (continued) Defining service capabilities These tables contain the attributes of the BRA: LTGRP (Logical Terminal Group) LTDEF (Logical Terminal Definition) LTMAP (Logical Terminal Map) KSETINV (Key Set Inventory) KSETLINE (Keyset Line) KSETFEAT (Keyset Features) Note: The SERVORD automatically fills some of these tables.
Page 177 Datafilling ISDN on RSC-S International 3-153 ISDN operations (continued) Table CLLI identifies the far end of the trunk group by the name of city or town, and the state or province. Table CLLI identifies the trunk group by the building group, and the destination of the traffic unit. Table CLLI identifies the trunk group through the code that identifies trunk groups that end at the same CLLI location.
Page 178 3-154 Datafilling ISDN on RSC-S International ISDN operations (continued) Table LTCINV contains inventory data for PM types. The P-side link assignment of table LTCINV does not contain inventory data for PM types. This table defines the PCM-30 line group controller (PLGC) or line group controller overseas (LGCO) on the C-side of the RCO2.
Page 179 Datafilling ISDN on RSC-S International 3-155 ISDN operations (continued) Enter load information for table RCCINV in field LOAD. Load information for table RCCINV corresponds to the LOADNAME tuple from table PMLOADS. The RCCNAME tuple in table RCCINV corresponds to the RCCNAME tuple from table RCCPSINV. The field RCCNAME stores site information entered in field NAME from table SITE.
Page 180 3-156 Datafilling ISDN on RSC-S International ISDN operations (continued) Table ISGDEF contains service and channel information for the PM which supports the DCH. The field in table ISGDEF isolates the DCH card and the PM that houses the DCH card. The PMTYPE, PMNO fields match the PMTYPE, PMNO, and DCHNO tuples in table DCHINV.
Page 181 Datafilling ISDN on RSC-S International 3-157 ISDN operations (continued) Table KSETINV identifies an LTID as an ISDN keyset. Table KSETINV defines the attributes of an LTID. The KSETLEN tuple in table KSETINV includes the LTID tuple. Table KSETLINE associates call appearances, ISDN LT call activators and indicators, to directory numbers and different feature options.
Page 182 3-158 Datafilling ISDN on RSC-S International ISDN operations (continued) Table flow for ISDN operations OPVRCLLI Table Table Table LOADNAME PMLOADS CARRMTC SITE LOADNAME TMPLTNM NAME LOAD Table CLLI LTCINV Table CLLI LTCNAME CLLI Table LTCPSINV CARRIDX CLLI XPMNO Table XPMTYPE TRKGRP CLLI SITE...
Page 183 Datafilling ISDN on RSC-S International 3-159 ISDN operations (continued) Table flow for ISDN operations (continued) PMTYPE PMNO D_CHNL Table Table DCHINV ISGDEF PMTYPE PMNO ISGNO DCHNO ISGNO Table LTGRP Table SPECCONN GROUP GROUPNO OPTION LTKEY SCSEL Table Table Table LTDEF LTMAP LNINV LTKEY...
Page 184 3-160 Datafilling ISDN on RSC-S International ISDN operations (continued) Limits The ISDN operations require that the PM type be entered as PLGC for an LGCOi+. Plain ordinary telephone service (POTS) lines on a DMS-100G switch do not support the ESA warm exit. Interactions The requirements for the use of ISDN enhanced D-channel features are as follows:...
Page 185 Datafilling ISDN on RSC-S International 3-161 ISDN operations (continued) Datafilling office parameters The office parameters that ISDN operations uses appear in the following table. Refer to Office Parameters Reference Manual for more information about office parameters. Office parameters by ISDN on RSC-S International Table Parameter name Explanation and action...
Page 186 3-162 Datafilling ISDN on RSC-S International ISDN operations (continued) Datafill requirements for ISDN operations Table Purpose of table DATASIZE Data size. Specifies the size of certain tables. For BRA services, enter table DATASIZE to specify the size needed for table SPECCONN. CLLI Common language location indicator.
Page 187 Datafilling ISDN on RSC-S International 3-163 ISDN operations (continued) Datafill requirements for ISDN operations (continued) Table Purpose of table RCCPSINV Remote cluster controller P-side link inventory. Contains only RCO2 P-side link assignments. LCMINV Line concentrating module inventory. Lists data assignments for each bay associated with a local line concentrating module (LCM).
Page 188 3-164 Datafilling ISDN on RSC-S International ISDN operations (continued) Datafill requirements for ISDN operations (continued) Table Purpose of table TRKMEM Trunk member. Lists the data associated with each trunk assigned to trunk groups and subgroups specified in tables TRKGRP and TRKSGRP.
Page 189 Datafilling ISDN on RSC-S International 3-165 ISDN operations (continued) Datafill requirements for ISDN operations (continued) Table Purpose of table LTMAP Logical terminal map. Maps the ISDN LTs to a LEN or the TEI, from table LTDEF. The AP determines if LTMAP maps the LTs to a LEN or the TEI.
Page 190 3-166 Datafilling ISDN on RSC-S International ISDN operations (continued) Datafilling table LTCINV Table line trunk controller inventory (LTCINV) identifies a host XPM peripheral to the DMS software. Information about the peripheral includes location, required load, and network link connections. This table also supports the universal tone receiver (UTR) as an optional card.
Page 191 Datafilling ISDN on RSC-S International 3-167 ISDN operations (continued) Datafilling table LTCINV for ISDN on RSC-S International (continued) Subfield or Field Entry Explanation and action refinement EQPEC 6X02UA Product equipment code. Enter the code for the PLGC with ISDN. LOAD alphanumeric Load.
Page 192 3-168 Datafilling ISDN on RSC-S International ISDN operations (continued) Datafilling table LTCINV for ISDN on RSC-S International (continued) Subfield or Field Entry Explanation and action refinement OPTCARD ISP16 Optional card. This field is a vector. This field can have a maximum of ten entries. If the CMR card is present, enter the CMRLOAD.
Page 193 Datafilling ISDN on RSC-S International 3-169 ISDN operations (continued) Datafilling table LTCINV for ISDN on RSC-S International (continued) Subfield or Field Entry Explanation and action refinement OPTATTR Optional attribute. This is not a DTC for CCS7. Leave this field blank. PEC6X40 6X40AC For 6X40 equipment PEC.
Page 194 3-170 Datafilling ISDN on RSC-S International ISDN operations (continued) Note 1: An LGCO and an LGCOI+ is entered as PLGC. Note 2: The in field LOAD and the in field E2LOAD represent xxxx alphanumeric entries like XE01 Note 3: The shelf can have a processor other than NTMX77 or the optional NTAX74.
Page 195 3-171 Datafilling ISDN on RSC-S International 3-171 3-171 ISDN operations ISDN operations (continued) (continued) Datafilling table LTCPSINV Table line trunk controller P-side link inventory (LTCPSINV) contains P-side assignments for host peripheral links. You can enter these links as DS30A, D30, or DCH. The key for this table is the same as for table LTCINV.
Page 196 3-172 Datafilling ISDN on RSC-S International ISDN operations (continued) Datafilling table LTCPSINV Subfield or Field refinement Entry Explanation and action LTCNAME see subfields Line trunk controller name. Subfields: XPMTYPE and XPMNO. XPMTYPE PLGC PM type. Contains the same entry in field XPMTYPE of table LTCINV.
Page 197 Datafilling ISDN on RSC-S International 3-173 ISDN operations (continued) Datafilling table LTCPSINV (continued) Subfield or Field Entry Explanation and action refinement PSDATA see subfield P-side data. Subfield: AREASELCT. AREASELCT P-side data. Enter D30 for trunks and remote nodes. Enter DS30A for P-side interface to a local LCM.
Page 198 3-174 Datafilling ISDN on RSC-S International ISDN operations (continued) Datafilling table RCCINV Subfield or Field Entry Explanation and action refinement OPTCARD ISP16 Optional card. This is a vector of a maximum of 10 entries. Examples: UTR14, UTR6, UTR7, CMR18, ISP16, PRL. Note: Make changes to fields with multiple entries in the PROMPT mode only.
Page 199 Datafilling ISDN on RSC-S International 3-175 ISDN operations (continued) Note 1: in field LOAD and in field E2LOAD represent xxxx alphanumeric entries, for example , in the order given. XE01 Note 2: If the shelf has a processor other than NTMX77 or the optional NTAX74, the following occurs.
Page 200 3-176 Datafilling ISDN on RSC-S International ISDN operations (continued) The datafill example for table RCCPSINV shows only the fields that apply to the ISDN on RSC. Refer to the data schema section of the Translations Guide for a description of the other fields. Datafilling table RCCPSINV Subfield or Field...
Page 201 Datafilling ISDN on RSC-S International 3-177 ISDN operations (continued) Datafilling table LCMINV The data assignment for the LCM and expanded line concentrating module (LCNE) appears in table line concentrating module inventory (LCMINV). Enter LCMEs off the RCO2 with the same values as LCMEs configured at the host site.
Page 202 3-178 Datafilling ISDN on RSC-S International ISDN operations (continued) Datafilling table LCMINV (continued) Subfield or Field Entry Explanation and action refinement LOAD alphanumeric Software load number. Contains the name of the software issue. CSPMNO see subfields C-side PM number. Subfields: PMTYPE and PMNO.
Page 203 Datafilling ISDN on RSC-S International 3-179 ISDN operations (continued) Datafill example for table LCMINV The following is an example of datafill for table LCMINV. MAP example for table LCMINV LCMNM FRTYPE SHPOS FLOOR ROW FRPOS EQPEC LOAD –––––––––––––––––––––––––––––––––––––––––––––––––––––––– MELB 05 0 CRSC BX30AB KRI06AY CSPMNO...
Page 204 3-180 Datafilling ISDN on RSC-S International ISDN operations (continued) Datafilling table ISGDEF Subfield or Field Entry Explanation and action refinement ISGNO 0 to 255 Integrated services group number. Enter the number of the D-channel handler card in the PMTYPE RCO2 PM type.
Page 205 Datafilling ISDN on RSC-S International 3-181 ISDN operations (continued) Datafilling table ISGDEF (continued) Subfield or Field Entry Explanation and action refinement CHNLTAB see subfields Channel information. This field is a vector with a maximum of 32 entries specifying the functions of each channel. Subfields: D_CHNL and CH_TYPE.
Page 206 3-182 Datafilling ISDN on RSC-S International ISDN operations (continued) Datafilling table ISGDEF (continued) Subfield or Field Entry Explanation and action refinement CHNLTAB D_CHNL 1 to 31 D-channel port. Enter the D-channel port (continued) assigned on the D-channel card. Port 0 is always reserved for the ISDN signal processor (ISP) functions.
Page 207 Datafilling ISDN on RSC-S International 3-183 ISDN operations (continued) Datafilling table DCHINV Table D-channel inventory (DCHINV) contains information about the DCH for peripherals that contain this card. The data includes the following: DCH ID number for each DCH name and number of the host PM and the associated NTMX82 port PEC (NTBX02BA) load file port number...
Page 208 3-184 Datafilling ISDN on RSC-S International ISDN operations (continued) Datafill example for table DCHINV The sample datafill for table DCHINV appears in the following example. MAP example for table DCHINV DCHNO PMTYPE PMNO DCHPEC LOAD PORT –––––––––––––––––––––––––––––––––––––––––––––––––––– RCO2 BX02BA DCH31AW RCO2 BX02BA DCH31AW...
Page 209 Datafilling ISDN on RSC-S International 3-185 ISDN operations (continued) Datafilling table LTGRP Subfield or Field refinement Entry Explanation and action GROUP alphanumeric Logical group name. Enter the name of the logical group of terminals. GROUPNO 0 to 15 Logical group number. Enter the group number corresponding to a group name.
Page 210 3-186 Datafilling ISDN on RSC-S International ISDN operations (continued) Datafilling table LNINV Table LNINV lists data for each line card slot. The LEN tuple in table LNINV corresponds to the LEN tuple in table LTMAP. With ISDN lines, the values for some of the fields have changed. The datafill example for table LNINV shows only the fields that apply to the ISDN on RSC-S.
Page 211 Datafilling ISDN on RSC-S International 3-187 ISDN operations (continued) Datafilling table LNINV (continued) Subfield or Field Entry Explanation and action refinement Manual override. Since an on-hook balance network test will not update field BNV, enter Y. CARDINFO Card information. Since this field does not apply to ISDN lines, enter NIL.
Page 212 3-188 Datafilling ISDN on RSC-S International ISDN operations (continued) The Bb-channel connection provides packet data service on a B-channel. The connection is between a B1 or B2 channel on a line card and a PCM-30 channel to the PH. The B-channel to B-channel connection is between a B1 or B2 channel on a line card to another B1 or B2 channel.
Page 213 Datafilling ISDN on RSC-S International 3-189 ISDN operations (continued) Datafilling table SPECCONN (continued) Subfield or Field Entry Explanation and action refinement PMTYPE RCO2 If entry is RCO2, enter subfields RCO2NO, RCO2CKTNO, and RCO2CKTTS. RCO2NO 0 to 511 RCO2NO. Enter external number of the PM. RCO2CKTNO 0 to 47 RCO2CKTNO.
Page 214 3-190 Datafilling ISDN on RSC-S International ISDN operations (continued) Datafilling table SPECCONN (continued) Subfield or Field Entry Explanation and action refinement CONTYPE Connection type. In the connection type field, PEND indicates pending, CON indicates connected, and CAB indicates connected with A-bit and B-bit signaling.
Page 215 Datafilling ISDN on RSC-S International 3-191 ISDN operations (continued) Datafilling table LTDEF Table logical terminal definition (LTDEF) defines ISDN terminals and AP for the type of service the terminal can access. The datafill example for table LTDEF shows only the fields that apply to the ISDN on RSC.
Page 216 3-192 Datafilling ISDN on RSC-S International ISDN operations (continued) Datafilling table LTDEF (continued) Subfield or Field Entry Explanation and action refinement LTAP B, D, BD, PB LT access privilege. Enter B for circuit switching or D for D-channel packet switching. Enter BD for combined circuit switching and D-channel packet switching, or PB for B-channel packet switching.
Page 217 Datafilling ISDN on RSC-S International 3-193 ISDN operations (continued) Datafill example for table LTDEF The sample datafill for table LTDEF appear in the following example. MAP example for table LTDEF LTKEY LTAP LTCLASS ––––––––––––––––––––––––––––––––––––––––––––––––– LTCO BRAKS LTCO BRAKS RCO2 0 BRAFS RCO2 0 BRAFS...
Page 218 3-194 Datafilling ISDN on RSC-S International ISDN operations (continued) Datafilling table KSETINV Subfield or Field Entry Explanation and action refinement KSETLEN see subfield Keyset line equipment number. The key to table KSETINV. Subfield: LEN, or for ISDN terminals subfields LTGRP and LTNUM. see subfields Line equipment number for the card that has the keyset.
Page 219 Datafilling ISDN on RSC-S International 3-195 ISDN operations (continued) Datafilling table KSETLINE Table keyset line (KSETLINE) associates CAPs, ISDN LT call activators and indicators, with directory numbers (DN) and different feature options. The datafill example for table KSETLINE shows only the fields that apply to the ISDN on RSC.
Page 220 3-196 Datafilling ISDN on RSC-S International ISDN operations (continued) Datafilling table KSETLINE (continued) Subfield or Field Entry Explanation and action refinement FORMAT see list Format of datafill. Possible entries: directory number(DN), multiple appearance DN (MADN), group intercom (GIC), and automatic call distribution (ACD).
Page 221 Datafilling ISDN on RSC-S International 3-197 ISDN operations (continued) Datafilling table LTMAP Table logical terminal map (LTMAP) maps ISDN LTs to a LEN or the TEI, depending on the AP, from table LTDEF. The datafill example for table LTMAP shows only the fields that apply to the ISDN on RSC-S.
Page 222 3-198 Datafilling ISDN on RSC-S International ISDN operations (continued) Datafilling table LTMAP (continued) Subfield or Field Entry Explanation and action refinement OPTION see list Terminal end point identifier for B, D, BD type (continued) terminals. Enter 1 or 2 for M5317 devices, and 21 through 26 for D-channel devices.
Page 223 Datafilling ISDN on RSC-S International 3-199 ISDN operations (continued) Datafilling table KSETFEAT Table keyset feature (KSETFEAT) associates ISDN LT feature activators and indicators (FAP) with feature instances and options. The datafill example for table KSETFEAT shows only the fields that apply to the ISDN on RSC-S.
Page 224 3-200 Datafilling ISDN on RSC-S International ISDN operations (continued) Datafilling table KSETFEAT Subfield or Field refinement Entry Explanation and action FEATKEY see list Feature key. The key to table KSETFEAT. Subfields: LEN, KEY, and FEAT. see subfields Line equipment number. Subfields: SITE, FRAME, UNIT, DRAWER, and CIRCUIT.
Page 225 Datafilling ISDN on RSC-S International 3-201 ISDN operations (continued) on NI-2 lines. The MCH option has a basic rate access functional (BRAFS) business set. The datafill example for table KSETKEYS shows only the fields that apply to the ISDN on RSC-S. Refer to the data schema section of the Translations Guide for a description of the other fields.
Page 226 3-202 Datafilling ISDN on RSC-S International ISDN operations (continued) Datafill example for table KSETKEYS The sample datafill for table KSETFEAT appears in the following example. MAP example for table KSETFEAT TEMPLATE SETINFO FEATLIST ––––––––––––––––––––––––––––––––––––––––––––––––––– BRAFS Tools for verifying translations Translations verification (TRAVER) uses datafill to check the routing of a call.
Page 227 Datafilling ISDN on RSC-S International 3-203 ISDN operations (continued) SERVORD example for creating an LTID in prompt mode > SLT SONUMBER : NOW 90 03 14 AM > LTID: > ISDN 1 FUNCTION: > ADD > Y > N SERVORD example for creating an LTID in no-prompt mode >SLT $ ISDN 1 ADD Y N SERVORD example for attaching an LEN and TEI to LTID ISDN operations in prompt mode...
Page 228 3-204 Datafilling ISDN on RSC-S International ISDN operations (continued) SERVORD example for ISDN operations in no-prompt mode >SLT $ ISDN 1 ATT 2 0 6 0 TEI 1 $ SERVORD example for defining the CAP/DN on the M5317T key in prompt mode >NEW SONUMBER...
Page 229 Datafilling ISDN on RSC-S International 3-205 ISDN operations ISDN operations (end) (continued) SERVORD example for defining CAP/DN on the M5317T key in no-prompt mode >NEW $ 8344040 ISDNKSET ISDNGRP 0 0 919 1 33 24 NILLATA 0 ISDN 1 25 DMS-100 Family XPM International Translations Reference Manual XPM12 and up...
Page 230: Firmware Downloading
3-206 3-206 Datafilling Firmware downloading on RSC-S International 3-206 Firmware downloading Functional group BAS00003 Feature package NTXR42AA Firmware downloading Release applicability XPM05 and higher Requirements Firmware downloading requires the following feature packages: NTX000AA Bilge NTX001AA Common Basic NTX270AA New Peripheral Maintenance NTXR34AA XPM-PLUS Basic Description The MX77 firmware downloading implements a process for loading...
Page 231 Datafilling Firmware downloading on RSC-S International 3-207 Firmware downloading (continued) Operation The UP is equipped with flash memory chips. The system upgrades the UP after an image is loaded like the software loading method from a host switch. There are two flash EEPROMs or banks on the NTMX77AA card. These banks are 256-kbyte programmable chips.
Page 232 3-208 Datafilling Firmware downloading on RSC-S International Firmware downloading (continued) To download firmware to the XPM, execute one of the following commands. The following are examples of the LOADFW command. >LOADFW PM >LOADFW UNIT unit_no >LOADFW INACTIVE Note 1: If the firmware_file is not specified with the LOADFW command, the command applies the firmware_file datafilled in the appropriate inventory table.
Page 233 Datafilling Firmware downloading on RSC-S International 3-209 Firmware downloading (continued) >BSY PM >LOADFW PM UPGRADE >RTS PM >BSY UNIT unit_no >LOADFW UNIT unit_no UPGRADE >RTS UNIT unit_no >BSY INACTIVE >LOADFW INACTIVE UPGRADE >RTS INACTIVE Note: By using the LOADFW command with the UPGRADE option, the firmware is upgraded to the new firmware load.
Page 234 3-210 Datafilling Firmware downloading on RSC-S International Firmware downloading (continued) Table RCCINV maintains a list of RCO2s entered in the DMS that contains RCO2 inventory data. The exception is P-side link assignments. Table information identifies RCO2 location, required load and exec lineups, and network link connections. You enter RCO2 C-side PCM-30 assignments in table RCCINV.
Page 235 Datafilling Firmware downloading on RSC-S International 3-211 Firmware downloading (continued) Billing Firmware downloading does not affect billing. Station Message Detail Recording Firmware downloading does not affect Station Message Detail Recording (SMDR). Entering office parameters Firmware downloading does not affect office parameters. Datafill sequence The following table lists tables that require datafill to implement firmware downloading.
Page 236 3-212 Datafilling Firmware downloading on RSC-S International Firmware downloading (continued) name of the backup loadfile—the load used if a problem is present in loading or returning to service the active loadfile. The backup loadfile is always the loadfile shipped with the RC02 that is not patched. file locations update active loadfile field—indicates if the site wants the active field updated automatically.
Page 237 Datafilling Firmware downloading on RSC-S International 3-213 Firmware downloading (continued) When you enter the PPXL in table PMLOADS, the following two procedures apply to the loadset. The system modifies the loadset if a loadset exists for the base load. The system creates a loadset if the base load is new to the DMS-100 switch.
Page 238 3-214 Datafilling Firmware downloading on RSC-S International Firmware downloading (continued) Loading a PPXL There are two methods to add PPXLs to an office. The first is for upgrading an office to a new base load lineup. You use this method when the base loadname is not now in table PMLOADS.
Page 239 Datafilling Firmware downloading on RSC-S International 3-215 Firmware downloading (continued) 6 To set the loadset against both units of the XPM, type >PATCHER and press the Enter key. >SET loadname PM pm_type device_no unit_no and press the Enter key. where loadname is the name of the loadfile pm_type...
Page 240 3-216 Datafilling Firmware downloading on RSC-S International Firmware downloading (continued) Adding PPXLs to an existing PM load lineup To add PPXLs to an existing XPM load lineup, use the following procedure: 1 Verify that all patch_ids associated with the PPXL are on the disk volume identified in table PMLOADS, field ACTVOL.
Page 241 Datafilling Firmware downloading on RSC-S International 3-217 Firmware downloading (continued) 6 To load each unit of the XPM, type >BSY UNIT unit_no and press the Enter key. >LOADPM UNIT unit_no and press the Enter key. >RTS UNIT unit_no and press the Enter key. where unit_no is the unit number of the XPM to be loaded...
Page 242 3-218 Datafilling Firmware downloading on RSC-S International Firmware downloading (continued) Datafilling table PMLOADS Subfield or Field Entry Explanation and action refinement LOADNAME alphanumeric Peripheral module load name. Enter the XPM load name. Range is a maximum of 32 characters. This loadname must be the same as the load name entered in tables LTCINV and RCCINV.
Page 243 Datafilling Firmware downloading on RSC-S International 3-219 Firmware downloading (continued) Datafill example for table PMLOADS Sample datafill for table PMLOADS appears in the following example. MAP display example for table PMLOADS LOADNAME ACTFILE ACTVOL BKPFILE BKPVOL UPDACT ________________________________________________________ ELI36xx ELI36xx S00DXPM ELI36xx S00DXPM...
Page 244 3-220 Datafilling Firmware downloading on RSC-S International Firmware downloading (continued) Datafilling table LTCINV Subfield or Field Entry Explanation and action refinement LOAD Load. Enter the load the RCO2 uses. The display should show a load listed in table PMLOADS. PROCPEC MX77AA Processor equipment product engineering MX77AA, or...
Page 245 Datafilling Firmware downloading on RSC-S International 3-221 Firmware downloading (continued) MAP display example for table LTCINV datafilled for NTMX77AA UP Table: LTCINV LTCNAME FRTYPE FRNO SHPOS FLOOR ROW FRPOS EQPEC LOAD ––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––– PLGC 1 6X02AG OLG07xx EXECTAB CONTMARK ––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––– (POTS POTSEX)(KEYSET KSETEX)(RMM_TERM RSMEX)(ABTRK DTCEX) CSLNKTAB CONTMARK –––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––...
Page 246 3-222 Datafilling Firmware downloading on RSC-S International Firmware downloading (continued) MAP display example for table LTCINV datafilled for NTAX74AA CAP Table: LTCINV LTCNAME FRTYPE FRNO SHPOS FLOOR ROW FRPOS EQPEC LOAD ––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––– PLGC 1 6X02AG OLG07xx EXECTAB CONTMARK ––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––– (POTS POTSEX)(KEYSET KSETEX)(RMM_TERM RSMEX)(ABTRK DTCEX) CSLNKTAB CONTMARK –––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––...
Page 247 Datafilling Firmware downloading on RSC-S International 3-223 Firmware downloading (continued) Datafilling table RCCINV Subfield or Field Entry Explanation and action refinement LOAD Load. Enter the load the RCO2 must use. The display should show a load listed in table PMLOADS. PROCPEC MX77AA Processor equipment product engineering...
Page 248 3-224 Datafilling Firmware downloading on RSC-S International Firmware downloading (continued) MAP display example for table RCCINV entered for NTMX77AA UP Table: RCCINV RCCNAME FRTYPE FRNO SHPOS FLOOR ROW FRPOS EQPEC LOAD –––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––– MELB RCO2 0 CRSC MX85AA KRI07xx EXECTAB CONTMARK ––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––...
Page 249 Datafilling Firmware downloading on RSC-S International 3-225 Firmware downloading Firmware downloading (end) (continued) MAP display example for table RCCINV datafilled for NTAX74AA CAP Table: RCCINV RCCNAME FRTYPE FRNO SHPOS FLOOR ROW FRPOS EQPEC LOAD –––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––– MELB RCO2 0 CRSC MX85AA WRI06xx EXECTAB CONTMARK...
Page 251: Remote Switching Center-Sonet (Uk / Europe)
Remote Switching Center-SONET (UK / Europe) Understanding RSC-S translations You must understand the Remote Switching Center-SONET (RSC-S) methods and terminology before you enter data in the product. This chapter describes the product in general terms as a background to enter data in the RSC-S.
Page 252: Revised System Architecture
4-2 Introduction to RSC-S International This release includes the following capabilities: Intraswitching allows calls that originate and terminate on the RSC-S to be switched without the use of host links. ESA allows the continuation of service in the RSC-S when a loss of communication with the host occurs.
Page 253: Packaging
Introduction to RSC-S International 4-3 Packaging The RSC-S packaging differs from normal RSC packaging, for example: The RSC-S can be provisioned in cabinets instead of equipment frames. The RSC-S model A uses the equipment frame and model B is configured in cabinets. The base of the RSC-S design is the RCO2.
Page 254: Crsc Extension (Cext) Cabinet
4-4 Introduction to RSC-S International The CRSC cabinet appears in the following figure: Cabinetized remote switching center cabinet CRSC cabinet—NTMX89 MSP (NTRX40) LCME (NTBX31) LCME (NTBX31) RMM (NT6X13) RCO2 CRSC extension (CEXT) cabinet A single-configuration RSC-S can have one CRSC extension (CEXT) cabinet that contains one: extension shelf (EXT) LCME...
Page 255: Cabinetized Line Modules (Clce) Cabinet
Introduction to RSC-S International 4-5 The CEXT cabinet appears in the following figure: CRSC extension cabinet CEXT cabinet—NTMX88 MSP (NTRX40) LCME (NTBX32) LCME (NTBX32) RMM (NT6X13) EXT (not available) Cabinetized line modules (CLCE) cabinet A single-configuration RSC-S can have a maximum of five CLCE cabinets. Each cabinet supports a maximum of two completely duplicated LCMs.
Page 256: Cabinetized Power Distribution Center (Cdpc) Cabinet
4-6 Introduction to RSC-S International Cabinetized power distribution center (CDPC) cabinet The CDPC is a cabinetized module that provides distribution of power for RSC-S equipment. Cabinetized miscellaneous equipment (CMIS) cabinet A single-configuration RSC-S can have one CMIS cabinet to contain customer-specified equipment.
Page 257: Rsc-S Configurations
Introduction to RSC-S International 4-7 RSC-S configurations Northern Telecom offers the basic RSC-S configuration without ISDN, or with ISDN. These configurations appear in the following two figures. Support of CDO and private branch exchanges (PBX) is provided on the peripheral side (P-side) of the RCO2. Note: Interchangeable use of the PCM-30 line group controller (PLGC) or the line group controller overseas (LGCO) can occur.
Page 258 4-8 Introduction to RSC-S International Basic single–configuration RSC-S without ISDN Messaging links Network DS30 links PLGC / LGCO PCM-30 links Host RSC-S C-side RCO2 P-side DS30A PCM-30 DS30A links links links CDO, PBX LCME 297-8331-815 Standard 10.01 August 1999...
Page 259 Introduction to RSC-S International 4-9 Basic single-configuration RSC-S with ISDN Messaging links Network DS30 links PLGC / LGCO PCM-30 Host links RSC-S C-side RCO2 P-side DS30A PCM-30 DS30A links links links CDO, PBX LCME DMS-100 Family XPM International Translations Reference Manual XPM12 and up...
Page 260: Preparing To Datafill Rsc-S Uk/Europe
4-10 Introduction to RSC-S International Preparing to datafill RSC-S UK/Europe PCL—New Software Delivery Vehicle After BCS36, Northern Telecom delivers Product Computing-Module Loads (PCL) instead of BCS releases or Universal Software Loads (USL). A PCL has features selected from the development stream software product intended for an application in a market.
Page 261: Configurations
Introduction to RSC-S International 4-11 Configurations The RSC-S can be configured with or without ISDN. An RSC-S configuration with a group of peripherals without ISDN provides a wide range of services. These services do not include ISDN services. An RSC-S with ISDN offers all the services of the RSC-S.
Page 262: Tuple Changed (Tupc) Logs For Static Data (Sd) Updates
4-12 Introduction to RSC-S International At the RCO2 level of the MAP display, the response to the QUERYPM FLT command is the same message as that of the PM128 log. The required steps are like the steps to update SD. Tuple changed (TUPC) logs for static data (SD) updates The DMS and the journal file (JF) together can track changes to DMS data tables.
Page 263 Introduction to RSC-S International 4-13 The important tuple or tuples appear. Note: The TUPC logs can help track inventory changes. Northern Telecom personnel use TUPC logs to solve field problems. Do not use TUPC logs instead of the JF utility. DMS-100 Family XPM International Translations Reference Manual XPM12 and up...
Page 264: Basic Call Processing
4-14 4-14 Datafilling BAS on RSC-S UK / Europe 4-14 Basic call processing Functional group BAS00012 BAS00026 Feature packages NTX145AA Remote Switching Center NTX150AA RSC–Intra RSC Calling NTXP92AA RSC-S Basic NTXK77AA PCM-30 RSCO-S Support Release applicability XPM05 and higher Requirements Basic call processing requires the following feature packages: NTXR42AA Firmware Downloading NTX000AA Bilge...
Page 265 Datafilling BAS on RSC-S UK / Europe 4-15 Basic call processing (continued) Basic call processing tables provide entries for the following: DMS recognition of the switching unit and remote locations physical device location identification data link assignments for the RCO2 and peripherals recovery trunks and trunk groups alarm functions...
Page 266 4-16 Datafilling BAS on RSC-S UK / Europe Basic call processing (continued) Trunks and trunk groups Tables TRKGRP, TRKSGRP and TRKMEM define the trunk groups that associate with a switching unit. These tables define additional information for subgroups assigned to trunk groups. These tables also define data for each trunk, trunk group, and subgroup.
Page 267 Datafilling BAS on RSC-S UK / Europe 4-17 Basic call processing (continued) Operation The RSC software provides each feature. The RSC-S basic package activates the features and provides the Synchronous Optical Network (SONET) remote. Tables and data entry methods do not change for RSC-S in comparison to the RSC.
Page 268 4-18 Datafilling BAS on RSC-S UK / Europe Basic call processing (continued) The following pages detail the fields entered in tables OFRT and IBNRTE for conditional routing. The fields in table OFRT are the same for subtable HNPACONT.RTEREF and for subtable FNPACONT.RTEREF. Table OFRT The following table describes the data entries for Basic call processing in table OFRT.
Page 269 Datafilling BAS on RSC-S UK / Europe 4-19 Basic call processing (continued) Datafilling table OFRT for basic call processing (continued) Subfield or Field Entry Description refinement CONDITION CALLCHR The selected condition is a match of field (continued) CALLCHR. Use a call characteristic from table CALLCHR.
Page 270 4-20 Datafilling BAS on RSC-S UK / Europe Basic call processing (continued) Datafilling table OFRT for basic call processing (continued) Subfield or Field Entry Description refinement SITE HOST or Enter in field SITE, HOST or a site name alphanumeric entered in table SITE. The selected condition to match is time of day.
Page 271 Datafilling BAS on RSC-S UK / Europe 4-21 Basic call processing (continued) Datafilling table OFRT for basic call processing (continued) Subfield or Field Entry Description refinement SKIPNUM 0 to 7 SK, skip in same table specified. Enter in field SKIPNUM the number of elements to skip in the route reference list.
Page 272 4-22 Datafilling BAS on RSC-S UK / Europe Basic call processing (continued) Note: The route reference number must be higher in the table to which translations transfer when the condition is met. Route after specified number of route elements skipped If the call must skip to another route element in the same route list, complete field RTETYPE.
Page 273 Datafilling BAS on RSC-S UK / Europe 4-23 Basic call processing (continued) the data schema section of the Translations Guide for a description of the other fields. Datafilling table IBNRTE for basic call processing Subfield or Field Entry Explanation and action refinement 0 through Extended route reference index.
Page 274 4-24 Datafilling BAS on RSC-S UK / Europe Basic call processing (continued) After the DMS sends a call to a route list, the system tries the first element in the route list. If the attempt fails, the DMS tries the next element and the elements that follow.
Page 275 Datafilling BAS on RSC-S UK / Europe 4-25 Basic call processing (continued) Note: You must enter some data, according to the trunk group type required. Each trunk group type requires an exact form. Correct trunk group types are TI, TO, T2, IBNTI, IBNTO, IBNT2, PX and ES. Table PMLOADS stores the device location of every peripheral module (PM) load file to map between the load names and devices.
Page 276 4-26 Datafilling BAS on RSC-S UK / Europe Basic call processing (continued) Table RCCINV maintains a list of RCO2s entered in the DMS switch. This list contains inventory data for the RCO2s. The inventory data does not contain P-side assignments. Table information identifies the location of the RCO2, the load and exec lineups, and the network link connections.
Page 277 Datafilling BAS on RSC-S UK / Europe 4-27 Basic call processing (continued) Table TRKSGRP lists additional information for each subgroup assigned to one of the trunk groups in table TRKSGRP. Field CLLI in table TRKSGRP corresponds to the CLLI code for the trunk group. Table TRKMEM lists the data for each trunk assigned to a trunk group and subgroup specified in tables TRKGRP and TRKSGRP.
Page 278 4-28 Datafilling BAS on RSC-S UK / Europe Basic call processing (continued) Table MTAVERT identifies the vertical connection points of the MTA matrix. For RSC-S, the connection is single, not multiple. Field SITE in table MTAVERT must correspond to field NAME in table SITE. This match identifies the equipment for the switching unit and for remote locations that use the unit.
Page 279 Datafilling BAS on RSC-S UK / Europe 4-29 Basic call processing (continued) Table flow for basic call processing Table Table Table CLLI CLLI PMLOADS CARRMTC Table LOADNAME CLLI TRKGRP TMPLTNM OPRVCLLI LOAD Table SITE CLLI Table LTCINV CLLI Table NAME LTCNAME TRKSGRP LOAD...
Page 280 4-30 Datafilling BAS on RSC-S UK / Europe Basic call processing (continued) Activation/deactivation by the end user Basic call processing does not require activation or deactivation by the end user. Billing Basic call processing does not affect billing. Station Message Detail Recording Basic call processing does not affect Station Message Detail Recording.
Page 281 Datafilling BAS on RSC-S UK / Europe 4-31 Basic call processing (continued) Data tables required for Basic call processing Table Purpose of table CLLI Common language location identifier. Codes identify the far end of each announcement, tone, trunk group, test trunk, national milliwatt test lines, and service circuit.
Page 282 4-32 Datafilling BAS on RSC-S UK / Europe Basic call processing (continued) Data tables required for Basic call processing (continued) Table Purpose of table LNINV The line circuit inventory lists the data for each line card slot. REXSCHED System REX scheduling of frequency and number of concurrent SREX tests.
Page 283 Datafilling BAS on RSC-S UK / Europe 4-33 Basic call processing (continued) Data tables required for Basic call processing Table Purpose of table MTAVERT The metallic test access vertical connection table identifies the vertical connectivity to the MTA matrix. MTAHORIZ The metallic test access horizontal lists the assignment of horizontal agents to a horizontal connection and horizontal group of MTAMs.
Page 284 4-34 Datafilling BAS on RSC-S UK / Europe Basic call processing (continued) Datafilling table OFCENG The following table describes the data for RSC-S International for table OFCENG. The table describes the fields that apply to Basic call processing. For additional information about office parameters, refer to Office Parameters Reference Manual.
Page 285 Datafilling BAS on RSC-S UK / Europe 4-35 Basic call processing (continued) The following table describes the entries for Basic call processing for table CLLI. The table describes the fields that apply directly to Basic call processing. The following example does not apply to a Gateway Switching Center.
Page 286 4-36 Datafilling BAS on RSC-S UK / Europe Basic call processing (continued) Datafilling table CLLI (continued) Subfield or Field Entry Description refinement TRKGRPSIZ 0 to 2047 Trunk group size is 4-character field. This field is equal to the maximum expected number of trunk members in the trunk group.
Page 287 Datafilling BAS on RSC-S UK / Europe 4-37 Basic call processing (continued) Datafilling table SITE Table SITE contains data for the switching unit and for the remote locations that use the unit. Enter data in table SITE before you assign a line equipment number or enter a PM.
Page 288 4-38 Datafilling BAS on RSC-S UK / Europe Basic call processing (continued) Datafilling table SITE (continued) Subfield or Field Entry Description refinement OPVRCLLI alphanumeric Operator verification CLLI. Enter the CLLI assigned to the operator verification trunk group at the remote location. ALMDATA ALMTYPE, Alarm data.
Page 289 Datafilling BAS on RSC-S UK / Europe 4-39 Basic call processing (continued) Datafilling table PMLOADS The following procedure describes the data for table PMLOADS. Table PMLOADS stores the device location of every PM load file. This storage permits the DMS-100 switch to locate load files. The XPM Loadfile Patching, introduces an active loadfile and a backup loadfile.
Page 290 4-40 Datafilling BAS on RSC-S UK / Europe Basic call processing (continued) Implementation of PPXLs At the start of each PPXL loadfile, a 1K data block that contains patch IDs is present. These patch IDs are for the patches in the PPXL. The patch files for each patch ID in the 1K data block must be present.
Page 291 Datafilling BAS on RSC-S UK / Europe 4-41 Basic call processing (continued) Loading a PPXL There are two ways to add PPXLs to an office. The first way is to upgrade an office to a new base load lineup. This is possible when the base loadname is not in table PMLOADS.
Page 292 4-42 Datafilling BAS on RSC-S UK / Europe Basic call processing (continued) 6 To set the loadset against the two units of the XPM, type: >PATCHER and press the Enter key. >SET loadname PM pm_type device_no unit_no and press the Enter key. where loadname is the name of the loadfile...
Page 293 Datafilling BAS on RSC-S UK / Europe 4-43 Basic call processing (continued) Adding PPXLs to present PM load lineup To add PPXLs to a present XPM load lineup, use the following procedure: 1 Verify that patch_ids that associate with the PPXL are present on the disk volume identified in table PMLOADS, field ACTVOL.
Page 294 4-44 Datafilling BAS on RSC-S UK / Europe Basic call processing (continued) 6 To load each unit of the XPM with the PPXL, type: >BSY UNIT unit_no and press the Enter key. >LOADPM UNIT unit_no and press the Enter key. >RTS UNIT unit_no and press the Enter key.
Page 295 Datafilling BAS on RSC-S UK / Europe 4-45 Basic call processing (continued) Datafilling table PMLOADS Subfield or Field Entry Explanation and action refinement LOADNAME alphanumeric Peripheral module load name. Enter the XPM load name. Range is a maximum of 32 characters.
Page 296 4-46 Datafilling BAS on RSC-S UK / Europe Basic call processing (continued) Example of entries for table PMLOADS The following is an example of entries for table PMLOADS. MAP display example for table PMLOADS LOADNAME ACTFILE ACTVOL BKPFILE BKPVOL UPDACT ________________________________________________________ ESA02CM ESA02CM...
Page 297 Datafilling BAS on RSC-S UK / Europe 4-47 Basic call processing (continued) Datafilling table LTCINV Subfield or Field Entry Description refinement LTCNAME refer to Link trunk controller name. Contains subfield subfields XPMTYPE and XPMNO. XPMTYPE PLGC XPM type. Enter PLGC. Entry values include PLGC, DTC, LGCO, SMR, SMS, SMU, IDTC, ILGC, ILTC, PDTC, TRCC, DTCI, TMS, and SMA.
Page 298 4-48 Datafilling BAS on RSC-S UK / Europe Basic call processing (continued) Datafilling table LTCINV (continued) Subfield or Field Entry Description refinement CSLNKTAB NMPAIR 0 to 31 Network module pair number. Enter the (continued) network link where the PM is assigned, corresponding to C-side links 0 through 15 of the PM.
Page 299 Datafilling BAS on RSC-S UK / Europe 4-49 Basic call processing (continued) Datafilling table LTCINV (continued) Subfield or Field Entry Description refinement PEC6X40 alphanumeric The 6X40 equipment PEC. Enter the version of the NT6X40 to be used. EXTINFO EXTENSION_INFO. Note 1: Make changes to fields with multiple entries in the PROMPT mode. In nonprompt mode, you can leave out present entries.
Page 300 4-50 Datafilling BAS on RSC-S UK / Europe Basic call processing (continued) Note 1: The xx in field LOAD stands for alphanumeric, for example Note 2: If the shelf is equipped with a processor different from NTMX77, the system enters the value of NILLOAD in field E2LOAD. Note 3: When field PROCPEC is entered with AX74AA AX74AA, not MX77AA MX77AA, the load name prefix in field LOAD changes from .
Page 301 4-51 Datafilling BAS on RSC-S UK / Europe 4-51 4-51 Basic call processing Basic call processing (continued) (continued) Datafilling table CARRMTC Table CARRMTC allows Digital Multiplex System (DMS) switch administration to enter maintenance control information on the following: peripherals OOS limits for alarms system RTS occurrences For table CARRMTC, fields CSPMTYPE and SELECTOR expand to include the current PM type RCO2.
Page 302 4-52 Datafilling BAS on RSC-S UK / Europe Basic call processing (continued) When you change an entry in table CARRMTC, the system checks table LTCPSINV to determine if in-service carriers refer to the entry. If the in-service carriers refer to the entry, the system rejects the change command.
Page 303 Datafilling BAS on RSC-S UK / Europe 4-53 Basic call processing (continued) Datafilling table CARRMTC (continued) Subfield or Field Entry Explanation and action refinement VOICELAW A_LAW Voice law. Enter the voice law that the carrier uses. The carrier uses A_LAW in international switches.
Page 304 4-54 Datafilling BAS on RSC-S UK / Europe Basic call processing (continued) Datafilling table CARRMTC (continued) Subfield or Field Entry Explanation and action refinement RFAIML 0 to 255 Remote frame alignment indication maintenance limit. Enter the remote frame alignment indication maintenance limit. RFAIOL 0 to 255 Remote frame alignment indication...
Page 305 Datafilling BAS on RSC-S UK / Europe 4-55 Basic call processing (continued) Datafilling table CARRMTC (continued) Subfield or Field Entry Explanation and action refinement RMAIRST 0 to 255 Remote multiframe alarm indication signal return-to-service time. Enter the remote multiframe alarm indication signal return-to-service time.
Page 306 4-56 Datafilling BAS on RSC-S UK / Europe Basic call processing (continued) Datafilling table CARRMTC (continued) Subfield or Field Entry Explanation and action refinement AIS16OST 0 to 255 Return-to-service time for AIS16 alarm. The default is 4. AIS16RST 0 to 255 Return-to-service time for AIS16 alarm.
Page 307 Datafilling BAS on RSC-S UK / Europe 4-57 Basic call processing (continued) Datafilling table CARRMTC (continued) Subfield or Field Entry Explanation and action refinement SIGNTYPE refer to list Signal type. Enter the signal type. The value ranges are: CASX CCSIPML D30RCC Note 1: The DMS system automatically adds the first tuple for RCO2 to table CARRMTC during IPL or first restart after IPL.
Page 308 4-58 Datafilling BAS on RSC-S UK / Europe Basic call processing (continued) Datafilling table Line Trunk Controller P–Side Link Inventory (LTCPSINV) Table LTCPSINV contains P-side link assignments for host PMs. The key for table LTCPSINV is the same as the key for table LTCINV. The system allocates memory automatically for a maximum of 128 tuples.
Page 309 Datafilling BAS on RSC-S UK / Europe 4-59 Basic call processing (continued) Datafilling table LTCPSINV (continued) Subfield or Field Entry Explanation and action refinement PSLNKTAB PSDATA Refer to P-side data. The P-side data contains subfield (continued) subfield AREASELCT. AREASELCT Area select. Enter D30 for trunks and remote nodes, including the RCC, RCO2, and RLCM.
Page 310 4-60 Datafilling BAS on RSC-S UK / Europe Basic call processing (continued) Datafilling table Remote Cluster Controller Inventory (RCCINV) Table RCCINV contains inventory data for the RCO2. The RCCINV does not contain inventory data for P-side link assignments. The C-side PCM-30 assignments for the RCO2 are entered in table RCCINV.
Page 311 Datafilling BAS on RSC-S UK / Europe 4-61 Basic call processing (continued) Datafilling table RCCINV (continued) Subfield or Field Entry Explanation and action refinement FRTYPE Refer to list Frame type. Enter CRSC for the RCO2 shelf. Enter CEXT for the RCO2 extension shelf. Enter the location of the RCO2 in fields FRNO, SHPOS, FLOOR, ROW, and FRPOS.
Page 312 4-62 Datafilling BAS on RSC-S UK / Europe Basic call processing (continued) Datafilling table RCCINV (continued) Subfield or Field Entry Explanation and action refinement CSPM Refer to C-side PM. Contains subfields PMTYPE and subfields XPMNO. PMTYPE PLGC PM type. Enter the type of peripheral attached to the RCO2.
Page 313 Datafilling BAS on RSC-S UK / Europe 4-63 Basic call processing (continued) Datafilling table RCCINV (continued) Subfield or Field Entry Explanation and action refinement OPTCARD Refer to list Optional card. This is a vector of a maximum of 10 entries. For the RCO2, you must use slot 4 for the ISDN signaling pre-processor (ISP) card.
Page 314 4-64 Datafilling BAS on RSC-S UK / Europe Basic call processing (continued) Datafilling table RCCINV (continued) Subfield or Field Entry Explanation and action refinement PROTOCOL HDLC or Protocol. Defines if HDLC mode is present and DMSX is active. If so, the remote shelf operates in HDLC after initialization.
Page 315 Datafilling BAS on RSC-S UK / Europe 4-65 Basic call processing (continued) Datafilling table RCCINV (continued) Subfield or Field Entry Explanation and action refinement EXTSHELF Y or N Extension shelf. Enter Y if the CPM has an extension shelf. If Y, the refinements to this field appear below.
Page 316 4-66 Datafilling BAS on RSC-S UK / Europe Basic call processing (continued) Entry example for table RCCINV A sample entry for table RCCINV appears in the following example. MAP display example for table RCCINV Table: RCCINV RCCNAME FRTYPE FRNO SHPOS FLOOR ROW FRPOS EQPEC LOAD –––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––...
Page 317 Datafilling BAS on RSC-S UK / Europe 4-67 Basic call processing (continued) Error messages for table RCCINV The following error messages occur when you enter table RCCINV. Error messages for table RCCINV Error message Explanation and action The system did not allocate memory Failed to allocate pslinks for P-side tables.
Page 318 4-68 Datafilling BAS on RSC-S UK / Europe Basic call processing (continued) When you add an extension shelf, datafill restrictions apply to RCO2 P-side links connected to the extension shelf. You must enter an extension shelf in RCCINV before you enter the PCM-30 and D-channel handler (DCH) links connected to the extension shelf.
Page 319 Datafilling BAS on RSC-S UK / Europe 4-69 Basic call processing (continued) Datafilling table RCCPSINV (continued) Subfield or Field Entry Explanation and action refinement PSLNKTAB Refer to P-side link table. Contains subfields PSLINK, subfields PSDATA, and CONTMARK. Enter the vector number.
Page 320 4-70 Datafilling BAS on RSC-S UK / Europe Basic call processing (continued) Entry example for table RCCPSINV A sample entry for table RCCPSINV appears in the following example. MAP display example for table RCCPSINV Table: RCCPSINV RCCNAME PSLNKTAB ––––––––––––––––––––––––––––––––––––––––––––––––––––––––––– MELB RCO2 0 (0 NILTYPE) (1 NILTYPE) (2 NILTYPE) (3 NILTYPE) (4 NILTYPE)(5 NILTYPE) (6 NILTYPE) (7 NILTYPE) (8 NILTYPE) (9 DCH) (10 NILTYPE) (11 NILTYPE) (12 NILTYPE) (13 NILTYPE)
Page 321 Datafilling BAS on RSC-S UK / Europe 4-71 Basic call processing (continued) Datafilling table Line Concentrating Module Inventory (LCMINV) Table LCMINV lists data assignment for each bay associated with a local or remote LCM unit. The only field that is different for the RSC-S configuration is SITE.
Page 322 4-72 Datafilling BAS on RSC-S UK / Europe Basic call processing (continued) Datafilling table LCMINV (continued) Subfield or Field Entry Explanation and action refinement CSPMNO Refer to The C-side PM. Contains subfields PMTYPE subfields and XPMNO. RCO2 The PM type. Enter the type of peripheral attached to the C-side of the LCM.
Page 323 Datafilling BAS on RSC-S UK / Europe 4-73 Basic call processing (continued) Datafilling table LCMINV (continued) Subfield or Field Entry Explanation and action refinement RINGDATA RNGTYPE refer to list Ringing type. Improvements are (continued) RNGCADENCE, FREQUENCIES, and PROMVOLT. LCDI_INFO 0 to 63 Line concentrating device ISDN information.
Page 324 4-74 Datafilling BAS on RSC-S UK / Europe Basic call processing (continued) Error messages for table LCMINV The following error messages occur when you enter data in table LCMINV. Error messages for table LCMINV Error message Explanation and action This message indicates that the RCO2 is connected to an RCO2 can connect on P-side links to LCM/LCME only.
Page 325 Datafilling BAS on RSC-S UK / Europe 4-75 Basic call processing (continued) Datafilling table RMMINV Subfield or Field Entry Explanation and action refinement RMMNAME refer to list The RMM name. Enter the name for the RMM. Contains subfields SITENM, PMTYPE, and RMMNO.
Page 326 4-76 Datafilling BAS on RSC-S UK / Europe Basic call processing (continued) Datafilling table RMMINV Subfield or Field Entry Explanation and action refinement Note: If the field RMMSELECTOR is RMMRCO2, enter subfield CSIDPORT as follows. CSIDPORT C-side PORT. Enter the C-side port connected to the RMM.
Page 327 Datafilling BAS on RSC-S UK / Europe 4-77 Basic call processing (continued) Datafilling table Line Circuit Inventory (LNINV) Table LNINV defines the site, line equipment number, and associated data for each line card circuit. The system can add or delete table LNINV line datafill for remote fiber terminal (RFT) lines in an S/DMS AccessNode system.
Page 328 4-78 Datafilling BAS on RSC-S UK / Europe Basic call processing (continued) Datafilling table LNINV (continued) Subfield or Field Entry Explanation and action refinement STATUS character Status. Enter the line inventory availability status. The correct entries are: HASU WORKING UNEQUIP CUTOFF RESERVED Y or N...
Page 329 Datafilling BAS on RSC-S UK / Europe 4-79 Basic call processing (continued) Datafilling table Trunk Group (TRKGRP) Table TRKGRP defines data for each trunk group associated with the switching unit. Each trunk group entry in table TRKGRP contains a CLLI for the trunk group.
Page 330 4-80 Datafilling BAS on RSC-S UK / Europe Basic call processing (continued) Datafilling table TRKGRP (continued) Subfield or Field Entry Explanation and action refinement GRPTYP refer to list Group type. Enter the group type for the trunk group. For maintenance and test trunks, the range is: ITL2 TTL2...
Page 331 Datafilling BAS on RSC-S UK / Europe 4-81 Basic call processing (continued) Entry example for table TRKGRP A sample entry for table TRKGRP appears in the following example. MAP display example for table TRKGRP Table: TRKGRP GRPKEY GRPINFO ––––––––––––––––––––––––––––––––––––––––––––––––––– VER90 MAINT 0 NPDGP NCRT 2X90AB...
Page 332 4-82 Datafilling BAS on RSC-S UK / Europe Basic call processing (continued) Datafilling table TRKSGRP Subfield or Field Entry Explanation and action refinement SGRPKEY refer to Subgroup key. This field contains subfields subfields CLLI and SGRP. CLLI alphanumeric The CLLI. This subfield contains the code assigned in the CLLI table to the trunk group where the subgroup belongs.
Page 333 Datafilling BAS on RSC-S UK / Europe 4-83 Basic call processing (continued) Datafilling table TRKSGRP (continued) Subfield or Field Entry Explanation and action refinement SIGDATA Signaling data. This subfield lists the signaling code. The STD is for standard signaling. Direction. For maintenance and test trunks, the entry is OG (outgoing).
Page 334 4-84 Datafilling BAS on RSC-S UK / Europe Basic call processing (continued) Datafilling table TRKSGRP (continued) Subfield or Field Entry Explanation and action refinement SGRPVAR DIALMODE Dial mode. For maintenance and test trunks, (continued) this subfield is blank. TRKGDTIM Trunk guard timing. For maintenance and test trunks, this value is 16.
Page 335 Datafilling BAS on RSC-S UK / Europe 4-85 Basic call processing (continued) Datafilling table Trunk Member (TRKMEM) Table TRKMEM contains data associated with trunks assigned to trunk groups and subgroups specified in tables TRKGRP and TRKSGRP. For an RSC-S, this table identifies circuits associated with static trunks and test equipment used to test lines and trunks.
Page 336 4-86 Datafilling BAS on RSC-S UK / Europe Basic call processing (continued) Datafilling table TRKMEM (continued) Subfield or Field Entry Explanation and action refinement MEMVAR RCO2CKTNO 0 to 47 Remote cluster controller equipment circuit card (continued) number. Enter the RCO2 card number where the TRKGRP member is assigned.
Page 337 Datafilling BAS on RSC-S UK / Europe 4-87 Basic call processing (continued) Datafilling table Alarm Scan Group (AMSCGRP) Table ALMSCGRP records the circuit equipment, location and type of circuit pack that contains scan points. Refer to the data schema section of the Translations Guide for a description of the other fields.
Page 338 4-88 Datafilling BAS on RSC-S UK / Europe Basic call processing (continued) Datafilling table Alarm Signal Distributor Group (ALMSDGRP) Table ALMSDGRP records circuit equipment, location and circuit pack type that contains SD points. Refer to the data schema section of the Translations Guide for a description of the other fields.
Page 339 Datafilling BAS on RSC-S UK / Europe 4-89 Basic call processing (continued) Datafilling table Alarm Signal Distributor Point (ALMSD) Table ALMSD identifies functions that each assigned signal distributor (SD) point in alarm signal distributor groups performs. Refer to the data schema section of the Translations Guide for a description of the other fields.
Page 340 4-90 Datafilling BAS on RSC-S UK / Europe Basic call processing (continued) Entry example for table ALMSD A sample entry for table ALMSD appears in the following example. MAP display example for table ALMSD Table: ALMSD FUNCTION SDGROUP POINT NORMALST AUDIBLE LAMPTEST ––––––––––––––––––––––––––––––––––––––––––––––––––...
Page 341 Datafilling BAS on RSC-S UK / Europe 4-91 Basic call processing (continued) Datafilling table ALMSC (continued) Subfield or Field Entry Explanation and action refinement NORMALST 0 or 1 Normal state. Enter the normal state of the scan point. Entry value is 0, if the scan point is normally off or open.
Page 342 4-92 Datafilling BAS on RSC-S UK / Europe Basic call processing (continued) Datafilling table ALMSC (continued) Subfield or Field Entry Explanation and action refinement ALMXFR Y or N Alarm transfer. Enter Y if the system activates the alarm when the system activates the alarm transfer key.
Page 343 Datafilling BAS on RSC-S UK / Europe 4-93 Basic call processing (continued) Datafilling table MTAMDRVE The metallic test access (MTA) network is a matrix of vertical and horizontal crosspoints. The matrix is like a minibar that connects specified verticals to horizontals in the MTA. The MTA tests equipment. The horizontal connections in the MTA connect the test equipment to the vertical connections.
Page 344 4-94 Datafilling BAS on RSC-S UK / Europe Basic call processing (continued) Table MTA Minibar Driver (MTAMDRVE) specifies the location and the type of minibar driver assigned to the minibar switch. The NT2X50AB Driver is part of the NT2X46 Minibar Switch. The NT3X09 Driver has relays on the card.
Page 345 Datafilling BAS on RSC-S UK / Europe 4-95 Basic call processing (continued) Datafilling table MTAMDRIVE Subfield or Field Entry Explanation and action refinement MTAMEM 0 to 255 Metal test access minibar driver member. Enter the MTA driver member number. This number is the key to the table.
Page 346 4-96 Datafilling BAS on RSC-S UK / Europe Basic call processing (continued) Datafilling table Metallic Test Access Vertical Connection Table (MTAVERT) Table MTAVERT identifies the vertical connection to the MTA matrix. Two connection types can occur. The connection types are single and multiple. A maximum of 32 LCMs can share a metal test pair.
Page 347 Datafilling BAS on RSC-S UK / Europe 4-97 Basic call processing (continued) Entry example for table MTAVERT A sample entry for RSC-S basic call processing in table MTAVERT appears in the following example. MAP display example for table MTAVERT Table: MTAVERT VERT VERTCONN...
Page 348 4-98 Datafilling BAS on RSC-S UK / Europe Basic call processing (continued) Note 2: The system assigns an LTU to the host switching. The horizontal that the LTU is assigned to is multiplied to the minibar switches assigned to the host switching unit. When an LTU is assigned to a remote location, the horizontal is multiplied to all minibar switches assigned to the remote location.
Page 349 Datafilling BAS on RSC-S UK / Europe 4-99 Basic call processing (continued) Note 9: The system dynamically allocates memory for this table to a maximum of 2000 tuples. Datafilling table MTAHORIZ Subfield or Field Entry Explanation and action refinement HORIZ 0 to 127 The MTA horizontal.
Page 350 4-100 Datafilling BAS on RSC-S UK / Europe Basic call processing (continued) Datafilling table MTAHORIZ (continued) Subfield or Field Entry Explanation and action refinement SELECTOR CLLI alphanumeric Common language location identifier. continued Enter LTU for line test unit. Enter MTU for metal test unit. Enter MJACK for metal jack.
Page 351 Datafilling BAS on RSC-S UK / Europe 4-101 Basic call processing (continued) Datafilling table MTAHORIZ (continued) Subfield or Field Entry Explanation and action refinement MTAGRP HORIZ Read-only field that provides information about (continued) the physical horizontal to which the MTA drivers connect.
Page 352 4-102 Datafilling BAS on RSC-S UK / Europe Basic call processing (continued) Datafilling table Routine Exercise Schedule (REXSCHED) Table REXSCHED contains information that the Routine Exercise Text (REX) coordinator or scheduler requires to schedule the REX tests. You can schedule the different REX tests according to the characteristics of the switch.
Page 353 Datafilling BAS on RSC-S UK / Europe 4-103 Basic call processing (continued) Datafilling table REXSCHED (continued) Subfield or Field Entry Explanation and action refinement ENABLE N or Y Enable. Enter either N(o) or Y(es) to disable or enable the REX test. The default value is Y(es).
Page 354 4-104 Datafilling BAS on RSC-S UK / Europe Basic call processing Basic call processing (end) (continued) Entry example for table REXSCHED A sample entry for table REXSCHED appears in the following example. MAP display example for table REXSCHED Table: REXSCHED REXTSTID ENABLE PERIOD...
Page 355: Esa Lines And Trunks
4-105 Datafilling ESA lines and trunks on RSC-S UK / Europe 4-105 4-105 ESA lines and trunks Functional group BAS00012 Feature package NTX149AA ESA lines and trunks Release applicability XPM05 and later versions Requirements The ESA lines and trunks feature requires the following packages to operate: NTX000AA Bilge NTX001AA Common Basic NTX145AA Remote Switching Center...
Page 356 4-106 Datafilling ESA lines and trunks on RSC-S UK / Europe ESA lines and trunks (continued) CUSTHEAD. The ESA office parameters for lines control entry to and exit from ESA control the download of ESA static data. Table RCCINV Table remote cluster controller inventory (RCCINV) contains inventory data, except RCO2 P-side link assignments.
Page 357 Datafilling ESA lines and trunks on RSC-S UK / Europe 4-107 ESA lines and trunks (continued) For MDC lines, the information in the ESAPXLA prefix tables must link to a specified customer group. Option ESAPXLA allows the specification of the prefix translator name associated with the customer group. If the ESA feature package is present, enter data in fields OPTION and XLANAME of table CUSTHEAD.
Page 358 4-108 Datafilling ESA lines and trunks on RSC-S UK / Europe ESA lines and trunks (continued) The RCO2 continues to operate in ESA mode during the RSC_XPMESAEXIT timeout period. The CC communicates with the ESA unit every 10 s to determine if the links to the RCO2 can operate. If communications fail again during the RSC_XPMESAEXIT timeout, the CC does not proceed with the ESA-EXIT.
Page 359 Datafilling ESA lines and trunks on RSC-S UK / Europe 4-109 ESA lines and trunks (continued) data are downloaded during the update each night. The following section describes the fields for office parameter RSC_ESASDUPD_BOOL and gives an example for each field. Fields for RSC_ESASDUPD_BOOL Field Example...
Page 360 4-110 Datafilling ESA lines and trunks on RSC-S UK / Europe ESA lines and trunks (continued) (CMC) tests take approximately 15 min and start 5 min after the time set in the parameter. Modifying ESA parameters Use the table editor to modify the following parameters: RSC_XPMESAEXIT RSC_ESAUPD_HOUR RSC_ESAUPD_BOOL...
Page 361 Datafilling ESA lines and trunks on RSC-S UK / Europe 4-111 ESA lines and trunks (continued) maximum. Entry of the RSC-S ESA mode cannot occur until the ESA task software is loaded with ESA static data. Download of ESA static data must occur from DMS CC to ESA task software if you change any of the following tables: translation data tables table ESAPXLA...
Page 362 4-112 Datafilling ESA lines and trunks on RSC-S UK / Europe ESA lines and trunks (continued) Translations table flow The ESA lines and trunks translation process appears in the following flowchart. Table flow for ESA lines and trunks Table RCCINV PMTYPE SITENM RCCNO...
Page 363 Datafilling ESA lines and trunks on RSC-S UK / Europe 4-113 ESA lines and trunks (continued) information first entered in the field NAME from table SITE, PM type, and PM number. Limits The following limits apply to ESA lines and trunks: When data entries occur in table ESAPXLA for POTS, a maximum of 16 entries can occur for each RSC-S.
Page 364 4-114 Datafilling ESA lines and trunks on RSC-S UK / Europe ESA lines and trunks (continued) Datafilling office parameters Office parameters that ESA lines and trunks use appear in the following table. For additional information about office parameters, refer to Office Parameters Reference Manual.
Page 365 Datafilling ESA lines and trunks on RSC-S UK / Europe 4-115 ESA lines and trunks (continued) Datafill tables that ESA lines and trunks require Table Purpose of table ESAPXLA Emergency stand-alone. This table supports line-to-trunk, trunk-to-trunk, and trunk-to-line call processing in the RSC-S during ESA.
Page 366 4-116 Datafilling ESA lines and trunks on RSC-S UK / Europe ESA lines and trunks (continued) Datafilling table RCCINV Subfield or Field Entry Explanation and action refinement EXECTAB refer to Executive table. This field contains subfields subfields TRMTYPE, EXEC, and CONTMARK. Note that use of more than one combination (eight maximum) can occur for any one PM.
Page 367 Datafilling ESA lines and trunks on RSC-S UK / Europe 4-117 ESA lines and trunks (continued) Datafilling table RCCINV (continued) Subfield or Field Entry Explanation and action refinement EXECTAB EXEC ESAEX Executive programs. Enter the set of executive (continued) programs the PM requires. The TRMTYPE entry specifies this PM.
Page 368 4-118 Datafilling ESA lines and trunks on RSC-S UK / Europe ESA lines and trunks (continued) Datafilling table RCCINV (continued) Subfield or Field Entry Explanation and action refinement WSXWACT Y or N Warm exit switch activity. If ESA is set to Y, you (continued) can enter Y if RCO2 supports warm ESA exit.
Page 369 Datafilling ESA lines and trunks on RSC-S UK / Europe 4-119 ESA lines and trunks (continued) Note: The in field LOAD stands for two letters, for example, Datafilling table ESAPXLA The ESA trunk translations tables support call processing during ESA. This call processing consists of line-to-trunk, trunk-to-trunk, and trunk-to-line call processing in the RSC-S.
Page 370 4-120 Datafilling ESA lines and trunks on RSC-S UK / Europe ESA lines and trunks (continued) Datafilling table ESAPXLA (continued) Subfield or Field Entry Explanation and action refinement PXLAKEY PMTYPE RCO2 Peripheral module type. This field identifies the (continued) peripheral node as an RLCM, an RCC, an RCO2 or an RDLM.
Page 371 Datafilling ESA lines and trunks on RSC-S UK / Europe 4-121 ESA lines and trunks (continued) Datafilling table ESAPXLA (continued) Subfield or Field Entry Explanation and action refinement RESULT 0 to 19 Line subgroup. Enter the number of the line (continued) subgroup of the unit for the assigned line card.
Page 372 4-122 Datafilling ESA lines and trunks on RSC-S UK / Europe ESA lines and trunks (continued) Datafilling table CUSTHEAD To implement ESA lines, the operating company uses table CUSTHEAD. This table specifies the prefix translator name data entry in table ESAXPLA for field XLANAME.
Page 373 Datafilling ESA lines and trunks on RSC-S UK / Europe 4-123 ESA lines and trunks ESA lines and trunks (end) (continued) Datafill example for table CUSTHEAD Sample datafill for table CUSTHEAD appears in the following example. MAP display example for table CUSTHEAD CUSTNAME CUSTXLA DGCOLNM OPTIONS ––––––––––––––––––––––––––––––––––––––––––––––––––_ POTSDATA POTSXLA POTS...
Page 374: Pcm-30 R1 Trunking
4-124 4-124 Datafilling PCM-30 trunks on RSC-S UK / Europe 4-124 PCM-30 R1 Trunking Functional group BAS00012 Feature package NTXT00AA PCM-30 RSC-S R1 Trunking Release applicability XPM05 and later versions Requirements The PCM-30 R1 Trunking requires the following feature packages to operate: NTXH52AA PCM-30 RSCO Support NTXK77AA PCM-30 RSCO-S Support...
Page 375 Datafilling PCM-30 trunks on RSC-S UK / Europe 4-125 PCM-30 R1 Trunking (continued) Table SITE identifies equipment for the switching unit and for all remote locations that connect to the switching unit. This table must contain data before you can assign a LEN or enter a PM. The host switching unit is the first entry in field NAME.
Page 376 4-126 Datafilling PCM-30 trunks on RSC-S UK / Europe PCM-30 R1 Trunking (continued) Table TRKMEM lists the data associated with each trunk assigned to one of the trunk groups and subgroups. Tables TRKGRP and TRKSGRP specify the trunk groups and subgroups. This table identifies the circuits associated with static trunks, dynamic trunks and the test equipment to test lines and trunks.
Page 377 Datafilling PCM-30 trunks on RSC-S UK / Europe 4-127 PCM-30 R1 Trunking (continued) Limits The following limits apply to PCM-30 RSC-S R1 Trunking: On the P-side of the RCO2, this feature supports a maximum of 46 PCM-30 links. Twenty-two PCM-30 links are on the main shelf, and 24 PCM-30 links are on the extension shelf.
Page 378 4-128 Datafilling PCM-30 trunks on RSC-S UK / Europe PCM-30 R1 Trunking (continued) Datafill tables required for PCM-30 R1 Trunking Table Purpose of table CLLI Common language location identifier. Contains codes that identify the far end of each announcement, tone, trunk group, test trunk, national milliwatt test lines and service circuit.
Page 379 Datafilling PCM-30 trunks on RSC-S UK / Europe 4-129 PCM-30 R1 Trunking (continued) Datafilling table CLLI The following table describes the datafill specific to PCM-30 R1 Trunking for table CLLI. Fields that apply to PCM-30 R1 Trunking appear. Refer to the data schema section of the Translations Guide for a description of the other fields.
Page 380 4-130 Datafilling PCM-30 trunks on RSC-S UK / Europe PCM-30 R1 Trunking (continued) Datafilling table SITE Subfield or Field Entry Explanation and action refinement NAME alphanumeric Site name. Enter the site name assigned to the remote switching unit. The first character must be alphabetic.
Page 381 Datafilling PCM-30 trunks on RSC-S UK / Europe 4-131 PCM-30 R1 Trunking (continued) Datafill example for table SITE The following is an example of datafill for the PCM-30 RSC-S R1 Trunking package in table SITE. MAP display example for table SITE Table: SITE NAME LTDSN MODCOUNT...
Page 382 4-132 Datafilling PCM-30 trunks on RSC-S UK / Europe PCM-30 R1 Trunking (continued) Datafilling table PMLOADS Subfield or Field refinement Entry Explanation and action LOADNAME alphanumeric Peripheral module load name. Enter the XPM load name. Range is a maximum of 32 characters.
Page 383 Datafilling PCM-30 trunks on RSC-S UK / Europe 4-133 PCM-30 R1 Trunking (continued) Datafill example for table CARRMTC The following example describes sample datafill for the PCM-30 RSC-S R1 Trunking package in table CARRMTC. MAP example for table CARRMTC Table: CARRMTC CSPMTYPE TMPLTNM RTSML RTSOL ATTR –––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––...
Page 384 4-134 Datafilling PCM-30 trunks on RSC-S UK / Europe PCM-30 R1 Trunking (continued) Datafill example for table RCCINV The following is an example of datafill for the PCM-30 R1 Trunking in table RCCINV. MAP example for table RCCINV Table: RCCINV RCCNAME FRTYPE FRNO SHPOS FLOOR ROW FRPOS EQPEC LOAD...
Page 385 Datafilling PCM-30 trunks on RSC-S UK / Europe 4-135 PCM-30 R1 Trunking (continued) Datafilling table RCCPSINV Table Remote Cluster Controller P-side link Inventory (RCCPSINV) contains RCO2 P-side link assignments. The RCO2 can accept a maximum of 54 multiples of P-side link information. When the addition of an extension shelf occurs, the RCO2 P-side links that connect to the extension shelf have datafill limits.
Page 386 4-136 Datafilling PCM-30 trunks on RSC-S UK / Europe PCM-30 R1 Trunking (continued) Datafilling table RCCPSINV (continued) Subfield or Field Entry Explanation and action refinement RCCNAME PMTYPE RCO2 Periperal module type. Enter RCO2. (continued) RCCNO 0 to 127 RCO2 number. PSLNKTAB 0 to 53 P-side link table.
Page 387 Datafilling PCM-30 trunks on RSC-S UK / Europe 4-137 PCM-30 R1 Trunking (continued) Datafill example for table RCCPSINV The following is an example of datafill for PCM-30 R1 Trunking in table RCCPSINV. MAP example for table RCCPSINV Table: RCCPSINV RCCNAME PSLNKTAB ––––––––––––––––––––––––––––––––––––––––––––––––––––––––––...
Page 388 4-138 Datafilling PCM-30 trunks on RSC-S UK / Europe PCM-30 R1 Trunking (continued) Datafill example for table TRKGRP The following is an example of datafill for the PCM-30 R1 Trunkingin table TRKGRP. MAP example for table TRKGRP Table: TRKGRP GRPKEY GRPINFO ________________________________________________________ MELB...
Page 389 Datafilling PCM-30 trunks on RSC-S UK / Europe 4-139 PCM-30 R1 Trunking (continued) The following procedure describes the datafill for table TRKSGRP. The fields that apply to PCM-30 R1 Trunking appear. Refer to the data schema section of the Translations Guide for a description of the other fields. Datafilling table TRKSGRP Subfield or Field...
Page 390 4-140 Datafilling PCM-30 trunks on RSC-S UK / Europe PCM-30 R1 Trunking (continued) Datafill example for table TRKSGRP The following is an example of datafill for the PCM-30 R1 Trunking in table TRKSGRP. MAP display example for table TRKSGRP Table: TRKSGRP SGRPKEY CARDCODE SGRPVAR...
Page 391 Datafilling PCM-30 trunks on RSC-S UK / Europe 4-141 PCM-30 R1 Trunking PCM-30 R1 Trunking (end) (continued) Datafilling table TRKMEM (continued) Subfield or Field Entry Explanation and action refinement MEMVAR PMTYPE RCO2 Peripheral module type. This field is the PM (continued) type on which the trunk is mounted.
Page 392: Isdn Operations
4-142 4-142 Datafilling ISDN on RSC-S UK / Europe 4-142 ISDN operations Functional group NIO00007 Feature package The RSC-S UK/Europe Integrated Services Digital Network (ISDN) Call Processing uses the following feature packages: NTX750AD ISDN Basic NTX145AA Remote Switching Center NTX150AA RSC Intra-RSC Calling NTXK77AA PCM-30 RSCO-S Support Release applicability XPM05...
Page 393 Datafilling ISDN on RSC-S UK / Europe 4-143 ISDN operations (continued) European Telecommunications Standards Institute (ETSI) BRI functionality is provided without terminal portability. The ISDN ETSI BRI services require the following feature packages: NTX756AA ISDN Display Services NTX796AA Enhanced number delivery NTX755AC ISDN supplementary services compliance Description Integrated Services Digital Network (ISDN) is provided through the remote...
Page 394 Telephony (CCITT) defines a maximum of 128 TEIs for each ISDN loop. Northern Telecom (Nortel) uses a maximum of eight TEIs defined for each loop. Nortel has TEI 1 and TEI 2 assigned to devices that associate with ISDN basic rate interface (BRI) B-channels. Nortel has TEI 21 through 26 assigned to devices with BRI D-channels.
Page 395 Datafilling ISDN on RSC-S UK / Europe 4-145 ISDN operations (continued) Generic Services Framework (GSF) on XPMs When software enables the GSFXPM ability, the call processing architecture treats ISDN calls as independent entities. The call processing architecture does not treat the calls as calls that associate with a keyset ability. With GSFXPM, the system can support two non-initializing ETSI BRI terminals on one ISDN loop.
Page 396 PLGC and the RCO2. Changing office parameters Nortel sets the default value of parameters during load build. Use the following procedure to change an office parameter. Use the table editor to perform the procedure. The following procedure changes the MAX_BRA_LINES parameter in table OFCOPT.
Page 397 Datafilling ISDN on RSC-S UK / Europe 4-147 ISDN operations (continued) For additional information about how to enter data in office parameters, refer to Office Parameters Reference Manual. Operation The description of the datafill for the RCO2 is in terms of physical configuration, service capabilities and bearer capabilities.
Page 398 4-148 Datafilling ISDN on RSC-S UK / Europe ISDN operations (continued) Defining service capabilities These tables contain the attributes of the BRA. LTGRP (Logical Terminal Group) LTDEF (Logical Terminal Definition) LTMAP (Logical Terminal Map) KSETINV (Key Set Inventory) KSETLINE (Keyset Line) KSETFEAT (Keyset Features) Translations table flow The user can enter data in some of the tables through SERVORD.
Page 399 Datafilling ISDN on RSC-S UK / Europe 4-149 ISDN operations (continued) Table CLLI stores the maximum number of trunk groups that can be assigned to the trunk group. The table also stores a miscellaneous entry for administrative information that the switching unit does not use. The system adds some CLLI codes to table CLLI when the feature is present in the switch.
Page 400 4-150 Datafilling ISDN on RSC-S UK / Europe ISDN operations (continued) Table RCCINV maintains a list of RCO2s entered in the DMS switch. This table contains inventory data, except P-side link assignments, for the RCO2s. The table information identifies the location of the RCO2, the load and exec lineups required and the network link connections.
Page 401 Datafilling ISDN on RSC-S UK / Europe 4-151 ISDN operations (continued) The access privilege (AP) determines if table LTMAP maps the ISDN LTs to a LEN or the TEI. The AP data corresponds to the LTKEY tuple in table LTDEF. Table LTMAP uses the LEN tuple to access data for each line card slot.
Page 402 4-152 Datafilling ISDN on RSC-S UK / Europe ISDN operations (continued) Table flow for ISDN operations OPVRCLLI Table Table Table SITE LOADNAME PMLOADS CARRMTC LOADNAME TMPLTNM NAME LOAD Table CLLI LTCINV Table CLLI LTCNAME CLLI Table LTCPSINV CARRIDX CLLI XPMNO Table XPMTYPE TRKGRP...
Page 403 Datafilling ISDN on RSC-S UK / Europe 4-153 ISDN operations (continued) Table flow for ISDN operations (continued) PMTYPE PMNO D_CHNL Table Table DCHINV ISGDEF PMTYPE PMNO ISGNO DCHNO ISGNO Table LTGRP Table SPECCONN GROUP GROUPNO OPTION LTKEY SCSEL Table Table Table LTDEF LTMAP...
Page 404 4-154 Datafilling ISDN on RSC-S UK / Europe ISDN operations (continued) Limits The ISDN operations does not have limits. Interactions Requirements for the implementation of ISDN enhanced D-channel features are: the RCO2 must have the NTMX77 unified processor (UP) card the RCO2 must have an enhanced ISDN signal processor card (NTBX01BA) the RCO2 must have an enhanced D-channel card (NTBX02BA)
Page 405 Datafilling ISDN on RSC-S UK / Europe 4-155 ISDN operations (continued) Datafilling office parameters Office parameters that ISDN operations use appear in the following table. For additional information about office parameters, refer to Office Parameters Reference Manual. Office parameters that are used by ISDN on RSC-S International Table Parameter name Description...
Page 406 4-156 Datafilling ISDN on RSC-S UK / Europe ISDN operations (continued) Datafill requirements for ISDN operations (continued) Table Purpose of table LTCPSINV Line trunk controller P-side link inventory (LTCPSINV). Contains XPM peripheral P-side link assignments. RCCINV Remote cluster controller inventory. Contains RCO2 inventory data, except P-side link assignments.
Page 407 Datafilling ISDN on RSC-S UK / Europe 4-157 ISDN operations (continued) Datafill requirements for ISDN operations (continued) Table Purpose of table RMMINV Remote maintenance module inventory. Identifies an RLCM, RSC-S or OPM site with the following information: the frame type frame number floor frame position...
Page 408 4-158 Datafilling ISDN on RSC-S UK / Europe ISDN operations (continued) Datafill requirements for ISDN operations (continued) Table Purpose of table SPECCONN Special connections. Contains connections that the use of Service Orders (SERVORD) cannot modify. KSETINV Business set inventory. Identifies an LTID as an ISDN keyset and defines the attributes of the LTID.
Page 409 Datafilling ISDN on RSC-S UK / Europe 4-159 ISDN operations (continued) Note: Enter data in table LTCINV after tables CLLI, SITE and PMLOADS. Tables CLLI, SITE and PMLOADS datafill examples appear in the basic call processing section for the RSC. Datafilling table LTCINV for ISDN on RSC-S International Subfield or Field...
Page 410 4-160 Datafilling ISDN on RSC-S UK / Europe ISDN operations (continued) Datafilling table LTCINV for ISDN on RSC-S International (continued) Subfield or Field Entry Description refinement TONESET UK100 TONESET. Enter UK100. Range of values includes DEFAULT, NORTHAM and UK100. PROCPEC MX77AA Processor equipment product engineering MX77AA...
Page 411 Datafilling ISDN on RSC-S UK / Europe 4-161 ISDN operations (continued) Datafill example for table LTCINV Sample datafill for table LTCINV appears in the following example. MAP example for table LTCINV LTCNAME FRTYPE FRNO SHPOS FLOOR ROW FRPOS EQPEC LOAD –––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––...
Page 412 4-162 4-162 Datafilling ISDN on RSC-S UK / Europe 4-162 ISDN operations ISDN operations (continued) (continued) Datafilling table LTCPSINV Table line trunk controller P-side link inventory (LTCPSINV) contains P-side assignments for host peripheral links. You can enter data for these links as DS30A, D30, or DCH.
Page 413 Datafilling ISDN on RSC-S UK / Europe 4-163 ISDN operations (continued) Datafilling table LTCPSINV (continued) Subfield or Field Entry Explanation and action refinement LTCNAME XPMNO 0 to 255 PM number. Contains the unit number of the (continued) PLGC in field XPMNO of table LTCINV. PSLNKTAB refer to P-side link table.
Page 414 4-164 Datafilling ISDN on RSC-S UK / Europe ISDN operations (continued) Datafilling table RCCINV The Remote Cluster Controller Inventory (RCCINV) table contains inventory data for the RCO2. Table RCCINV does not include inventory data for the P-side links. Only fields that apply to the ISDN on RSC-S appear in the datafill example for table RCCINV.
Page 415 Datafilling ISDN on RSC-S UK / Europe 4-165 ISDN operations (continued) Datafilling table RCCINV (continued) Subfield or Field Entry Explanation and action refinement INTRASW Y or N Intra-switching allowed. Enter Y if RCO2 intra-switched calling is enabled. OPTCARD Optional card. This entry is a vector of a maximum of ten entries.
Page 416 4-166 Datafilling ISDN on RSC-S UK / Europe ISDN operations (continued) Datafill example for table RCCINV Sample datafill for table RCCINV appears in the following example. MAP example for table RCCINV RCCNAME FRTYPE FRNO SHPOS FLOOR ROW FRPOS EQPEC LOAD –––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––...
Page 417 Datafilling ISDN on RSC-S UK / Europe 4-167 ISDN operations (continued) You can enter data for a maximum of ten DCH cards in table RCCPSINV. Only fields that apply to the ISDN on RSC appear in the datafill example for table RCCPSINV.
Page 418 4-168 Datafilling ISDN on RSC-S UK / Europe ISDN operations (continued) Datafill example for table RCCPSINV Sample datafill for table RCCPSINV appears in the following example. MAP example for table RCCPSINV RCCNAME PSLNKTAB --------------------------------------------------------- MELB RCO2 0 (0 NILTYPE) (1 DCH) (2 NILTYPE) (3 NILTYPE) (4 NILTYPE) (5 NILTYPE) (6 NILTYPE) (7 NILTYPE) (8 NILTYPE)(9 DS30A) (10 DS30A) (11 NILTYPE) (12 NILTYPE) (13 NILTYPE) (14 NILTYPE) (15 NILTYPE) (16 NILTYPE)
Page 419 Datafilling ISDN on RSC-S UK / Europe 4-169 ISDN operations (continued) Datafilling table LCMINV Subfield or Field Entry Explanation and action refinement LCMNM refer to Line concentrating module name. Enter the subfields LCM name. This field contains subfields SITE, FRNO, and UNITNO. SITE alphanumeric Site.
Page 420 4-170 Datafilling ISDN on RSC-S UK / Europe ISDN operations (continued) Datafilling table LCMINV (continued) Subfield or Field Entry Explanation and action refinement CSPMNO PMTYTPE RCO2 Peripheral module type. Subfield of CSPMNO. (continued) Enter the type of PM where the LCM connects on the C-side.
Page 421 Datafilling ISDN on RSC-S UK / Europe 4-171 ISDN operations (continued) Datafill example for table LCMINV Sample datafill for table LCMINV appears in the following example. MAP example for table LCMINV LCMNM FRTYPE SHPOS FLOOR ROW FRPOS EQPEC LOAD –––––––––––––––––––––––––––––––––––––––––––––––––––––––– REM3 05 0 CRSC BX30AB KRI06AY...
Page 422 4-172 Datafilling ISDN on RSC-S UK / Europe ISDN operations (continued) Datafilling table ISGDEF Subfield or Field Entry Explanation and action refinement ISGNO 0 to 255 Integrated services group number. Enter the number of the DCH card in the PM. PMTYPE RCO2 PM type.
Page 423 Datafilling ISDN on RSC-S UK / Europe 4-173 ISDN operations (continued) Datafilling table ISGDEF (continued) Subfield or Field Entry Explanation and action refinement CHNLTAB D_CHNL 1 to 31 D-channel port. Enter the D-channel port (continued) assigned on the D-channel card. The ISDN signal processor (ISP) functions reserve port 0.
Page 424 4-174 Datafilling ISDN on RSC-S UK / Europe ISDN operations (continued) Datafilling table DCHINV Table D-Channel Inventory (DCHINV) contains information about the DCH for the peripherals that contain this card. The data includes the following: the DCH ID number for each DCH the name and number of the host PM the associated NTMX82 port the PEC (NTBX02BA)
Page 425 Datafilling ISDN on RSC-S UK / Europe 4-175 ISDN operations (continued) Datafill example for table DCHINV Sample datafill for table DCHINV appears in the following example. MAP example for table DCHINV DCHNO PMTYPE PMNO DCHPEC LOAD PORT –––––––––––––––––––––––––––––––––––––––––––––––––––– RCO2 BX02BA DCH31AW RCO2 BX02BA...
Page 426 4-176 Datafilling ISDN on RSC-S UK / Europe ISDN operations (continued) Datafilling table LTGRP Subfield or Field refinement Entry Explanation and action GROUP alphanumeric Logical group name. Enter the name of the logical group of terminals. GROUPNO 0 to 15 Logical group number.
Page 427 Datafilling ISDN on RSC-S UK / Europe 4-177 ISDN operations (continued) Datafilling table LNINV Table LNINV lists data for each line card slot. The LEN tuple in table LNINV corresponds to the LEN tuple in table LTMAP. With ISDN lines, the values for some of the fields change.
Page 428 4-178 Datafilling ISDN on RSC-S UK / Europe ISDN operations (continued) Datafilling table LNINV (continued) Subfield or Field Entry Explanation and action refinement Manual override. An on-hook balance network test does not update field BNV. Enter Y. CARDINFO Card information. This field does not apply to ISDN lines.
Page 429 Datafilling ISDN on RSC-S UK / Europe 4-179 ISDN operations (continued) This table changes to accommodate an RCO2 entry in PMTYPE. The PMTYPE is a subfield of SCSEL. The PCM-30 end point of the RCO2 shelf can be defined in ports higher than 19, to a maximum of 47. Only fields that apply to the ISDN on RSC-S appear in the datafill example for table SPECCONN.
Page 430 4-180 Datafilling ISDN on RSC-S UK / Europe ISDN operations (continued) Datafilling table SPECCONN (continued) Subfield or Field Entry Explanation and action refinement refer to Line equipment number for the ISDN card. subfields Contains subfields SITE, FRAME, UNIT, DRAWER and CIRCUIT. refer to list Basic rate access channel to nail up.
Page 431 Datafilling ISDN on RSC-S UK / Europe 4-181 ISDN operations (continued) Datafilling table SPECCONN (continued) Subfield or Field Entry Explanation and action refinement CONTYPE Connection type. In the connection type field: PEND indicates pending CON indicates connected CAB indicates connected with A-bit and B-bit signaling RES indicates reserved STATUS...
Page 432 4-182 Datafilling ISDN on RSC-S UK / Europe ISDN operations (continued) Datafill example for table SPECCONN Sample datafill for table SPECCONN appears in the following example. MAP example for table SPECCONN ENDPT1 ENDPT2 CONTYPE STATUS –––––––––––––––––––––––––––––––––––––––––––––––––––––––– RCO2 DCHCHNL 0 ACTIVE RCO2 DCHCHNL 0 ACTIVE...
Page 433 Datafilling ISDN on RSC-S UK / Europe 4-183 ISDN operations (continued) Datafilling table LTDEF Subfield or Field Entry Explanation and action refinement LTKEY refer to Logical terminal key. Contains subfields LTGRP subfields and LTNUM. LTGRP alphanumeric Logical terminal group. Enter the LT group. Group ISDN is defined.
Page 434 4-184 Datafilling ISDN on RSC-S UK / Europe ISDN operations (continued) Datafilling table KSETINV Table Business Set Inventory (KSETINV) identifies an LTID as an ISDN keyset. Table KSETINV defines the attributes for the LTID. The keyset can be a T2317 business set, an M5317t business set and terminals, or equipment by other manufacturers.
Page 435 Datafilling ISDN on RSC-S UK / Europe 4-185 ISDN operations (continued) Datafilling table KSETINV (continued) Subfield or Field Entry Explanation and action refinement SETDATA refer to Set data. Contains subfields KSET and subfields FANUM. KSET ISDNKSET Keyset. Contains keyset type for ISDN terminals.
Page 436 4-186 Datafilling ISDN on RSC-S UK / Europe ISDN operations (continued) Datafilling table KSETLINE Table keyset line (KSETLINE) associates CAPs with directory numbers (DN) and feature options. The CAPs are ISDN LT call activators and indicators. CAUTION Make sure you use SERVORD to add and delete tuples to and from table KSETLINE.
Page 437 Datafilling ISDN on RSC-S UK / Europe 4-187 ISDN operations (continued) Datafilling table KSETLINE (continued) Subfield or Field Entry Explanation and action refinement 1 to 69 Key. Enter the number associated with the physical set key where the DN is assigned. You must program key number 1 for the set primary DN.
Page 438 4-188 Datafilling ISDN on RSC-S UK / Europe ISDN operations (continued) Datafill example for table KSETLINE Sample datafill for table KSETLINE appears in the following example. MAP example for table KSETLINE KSETKEY FORMAT DNRESULT CONTMARK ––––––––––––––––––––––––––––––––––––––––––––––––––– ISDN51 0 Y 2265235 KINGSA 0 10 181 Datafilling table KSETFEAT Table keyset feature (KSETFEAT) associates ISDN LT feature activators and indicators (FAP) with feature instances and options.
Page 439 Datafilling ISDN on RSC-S UK / Europe 4-189 ISDN operations (continued) Datafilling table KSETFEAT Subfield or Field Entry Explanation and action refinement FEATURE alphanumeric KSET feature. Contains feature type. To support multiple services on ISDN, you must enter data for additional call offering unrestricted (ACOU) and addition functional call (AFC).
Page 440 4-190 Datafilling ISDN on RSC-S UK / Europe ISDN operations (continued) SERVORD limits The ISDN operations does not have SERVORD limits. The SERVORD examples are for ISDN on RSC-S. For complete information on the application of SERVORD, refer to the SERVORD Reference Manual. Setting up a logical terminal (with the use of the SLT command) Command SLT is a SERVORD command.
Page 441 Datafilling ISDN on RSC-S UK / Europe 4-191 ISDN operations (continued) SERVORD example for attaching an LEN and TEI to a LTID ISDN operations in prompt mode >SLT SONUMBER : NOW 90 03 14 AM > LTID: >ISDN 1 FUNCTION: >ATT >2 0 6 0 OPTION:...
Page 442 4-192 Datafilling ISDN on RSC-S UK / Europe ISDN operations ISDN operations (end) (continued) SERVORD example for defining the CAP/DN on the M5317T key in prompt mode >NEW SONUMBER NOW 90 03 14 AM >$ > 8344040 LCC: > ISDNKSET GROUP >...
Page 443: Firmware Downloading
4-193 Datafilling Firmware downloading on RSC-S UK / Europe 4-193 4-193 Firmware downloading Functional group BAS00003 Feature package NTXR42AA Firmware Downloading Release applicability XPM05 and later Requirements Firmware downloading has the following feature package requirements: NTX000AA Bilge NTX001AA Common Basic NTX270AA New Peripheral Maintenance NTXR34AA XPM-PLUS Basic Description...
Page 444 4-194 Datafilling Firmware downloading on RSC-S UK / Europe Firmware downloading (continued) In-service firmware downloading In-service firmware downloading permits XPM firmware loading in an XPM unit while the unit is in service (InSv). This feature reduces the amount of time one unit of the XPM is out-of-service (OOS). In-service firmware downloading supports NTMX77 and NTAX74 processors.
Page 445 Datafilling Firmware downloading on RSC-S UK / Europe 4-195 Firmware downloading (continued) Note 2: By using the LOADFW command without the UPGRADE option, the firmware downloads to the DMS system. XPM Firmware Loader Robustness CM Component disables the firmware option of the LOADPM command. A message is output to the user if the firmware option of the LOADPM command is used.
Page 446 4-196 Datafilling Firmware downloading on RSC-S UK / Europe Firmware downloading (continued) Note: By using the LOADFW command with the UPGRADE option, the firmware is upgraded to the new firmware load. When this procedure is performed on a by-unit basis, perform a switch of activity (SwAct) followed by the RTS command.
Page 447 Datafilling Firmware downloading on RSC-S UK / Europe 4-197 Firmware downloading (continued) The firmware downloading translation process appears in the following flowchart. Table flow for firmware downloading Table PMLOADS Table LTCINV Table RCCINV Limits The following limits apply to firmware downloading. The unit must be at task level.
Page 448 4-198 Datafilling Firmware downloading on RSC-S UK / Europe Firmware downloading (continued) Datafilling office parameters Firmware downloading does not affect office parameters. Datafill sequence The following table lists tables that require data to use firmware downloading. Enter the tables in the order that the tables appear in the list. Datafill tables required for firmware downloading Table Purpose of table...
Page 449 Datafilling Firmware downloading on RSC-S UK / Europe 4-199 Firmware downloading (continued) Datafill for table PMLOADS The following procedure shows the datafill for table PMLOADS. Table PMLOADS stores the device location of every PM load file. This table allows the DMS-100 switch to locate load files. The XPM Loadfile Patching consists of an active loadfile and a backup loadfile.
Page 450 4-200 Datafilling Firmware downloading on RSC-S UK / Europe Firmware downloading (continued) Implementation of PPXLs Each PPXL loadfile contains a 1K data block at the start. This block contains the patch IDs for the patches in the PPXL. The associated patch files for each patch ID listed in the 1K data block must be present.
Page 451 Datafilling Firmware downloading on RSC-S UK / Europe 4-201 Firmware downloading (continued) Loading a PPXL There are two ways to add PPXLs to an office. The first method upgrades an office to a current base load lineup. This upgrade occurs when the base loadname is not in table PMLOADS.
Page 452 4-202 Datafilling Firmware downloading on RSC-S UK / Europe Firmware downloading (continued) 6 To set the loadset against both units of the XPM, type >PATCHER and press the Enter key. >SET loadname PM pm_type device_no unit_no and press the Enter key. where loadname is the name of the loadfile...
Page 453 Datafilling Firmware downloading on RSC-S UK / Europe 4-203 Firmware downloading (continued) Adding PPXLs to a current PM load lineup Use the following procedure to add PPXLs to a current XPM load alignment: 1 Verify that all patch_ids associated with the PPXL are present on the disk volume that field ACTVOL in table PMLOADS identifies.
Page 454 4-204 Datafilling Firmware downloading on RSC-S UK / Europe Firmware downloading (continued) 6 To load each unit of the XPM with the PPXL, type >BSY UNIT unit_no and press the Enter key. >LOADPM UNIT unit_no and press the Enter key. >RTS UNIT unit_no and press the Enter key.
Page 455 Datafilling Firmware downloading on RSC-S UK / Europe 4-205 Firmware downloading (continued) The datafill that applies to downloads for table PMLOADS appears in the following table. Only the fields that apply directly to firmware downloads appear. Refer to the data schema section of the Translations Guide for a description of the other fields.
Page 456 4-206 Datafilling Firmware downloading on RSC-S UK / Europe Firmware downloading (continued) Datafill example for table PMLOADS The following example shows sample datafill for table PMLOADS. MAP display example for table PMLOADS LOADNAME ACTFILE ACTVOL BKPFILE BKPVOL UPDACT ________________________________________________________ ELI36xx ELI36xx S00DXPM ELI36xx...
Page 457 Datafilling Firmware downloading on RSC-S UK / Europe 4-207 Firmware downloading (continued) Datafilling table LTCINV Subfield or Field Entry Explanation and action refinement LOAD Load. Enter the load the RCO2 must use. The RCO2 displays a load that appears in table PMLOADS.
Page 458 4-208 Datafilling Firmware downloading on RSC-S UK / Europe Firmware downloading (continued) Datafilling table RCCINV Table Remote Cluster Controller Inventory (RCCINV) contains inventory data for the RCO2. The RCCINV does not contain P-side link assignments for the RCO2. The C-side PCM-30 assignments for the RCO2 appear in table RCCINV.
Page 459 Datafilling Firmware downloading on RSC-S UK / Europe 4-209 Firmware downloading Firmware downloading (end) (continued) Datafill example for table RCCINV The following is an example of datafill for table RCCINV. MAP display example for table RCCINV Table: RCCINV RCCNAME FRTYPE FRNO SHPOS FLOOR ROW FRPOS EQPEC LOAD –––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––...
Page 461: Introduction To Rsc-M
Introduction to RSC-M This chapter describes datafill for the Remote Switching Center Multi-access version of the Remote Controller Overseas (RSC-M) . Understanding RSC-M translations Table RSC-M translate (GPPTRNSL) defines the nodes on the peripheral side (P-side) of the RSC-M. Use table GPPTRNSL because the RSC-M is a remote peripheral module (PM) that the remote cluster controller inventory (RCCINV) table defines.
Page 462: Signaling For The Rsc-M
5-2 Introduction to Remote Switching Center Multi-access Table datafill to CAS link associations (continued) In field LEN of table LNINV, subfield BAY relates to field GROUP in table GPPTRNSL Explanation Refers to P-side links 32 to 39 Refers to P-side links 40 to 47 —end—...
Page 463 Introduction to Remote Switching Center Multi-access 5-3 channels provide CAS protocols to groups of the following analog line interfaces. Note: The AN generates the physical subscriber line signaling (off- and on-hook, ring generation). Implementation of RSC-M interfaces to CAS ANs indicates the following signaling differences: the signaling processor (SIGP) circuit card provides the messaging control of CAS links...
Page 464: Preparing To Datafill Rsc-M
5-4 Introduction to Remote Switching Center Multi-access Preparing to datafill RSC-M The AN is a virtual entity to the DMS switch. The datafill of the DMS switch and the AN must coincide. Operating company personnel must coordinate the assignment of directory numbers (DNs) on the DMS switch with the assignment of DNs on the AN.
Page 465: Class
Introduction to Remote Switching Center Multi-access 5-5 support for RSC-M PM maintenance, carrier maintenance, line maintenance and call processing support for static data downloads of information from the AN nodes to the RSC-M. The RSC-M provides information about the card type of the terminals support for data and human-machine interface (HMI) for the following: —...
Page 466 5-6 Introduction to Remote Switching Center Multi-access deliver the current time and date to the Customer Premises Equipment (CPE). For the CND to occur, the number of the calling subscriber must be available at the destination exchange. The number must pass before the number can appear at the MAP display.
Page 467 Introduction to Remote Switching Center Multi-access 5-7 F3446—Message Waiting – Stuttered Dial Tone F6567—Network Ring Again F0407, F3704—Private Dial Plan F1151—Ring Again F0416, F0417—Speed Dialing NC0011—Warm Line (d) BR19420—Family and Friends Name Delivery AG0781—Calling Number Delivery AG1515—Dialable Directory Number AG1954—Visual Message Waiting Indication Note 1: The CLASS features display the calling number in North American DN format.
Page 468: Rsc-M Call Process
5-8 Introduction to Remote Switching Center Multi-access CLASS services signaling Called V5.2 Subscriber Initial Ring Burst ESTABLISH PS: Initial Ring EST ACK End of Initial Ring SIGNAL PS: pulse notification Calling Line Identity Delivery (over bearer channel) Cadenced Ringing SIGNAL off hook SIGNAL SS: off hook...
Page 469: Updating Static Data
Introduction to Remote Switching Center Multi-access 5-9 Updating static data Three types of updates provide the inactive unit of the RSC-M with data to control maintenance and call processing. The three types of updates are: static data update bulk data update dynamic data update Static data update Static data holds RSC-M and AN configuration information, like the...
Page 470 5-10 Introduction to Remote Switching Center Multi-access Node table audits determine if the XPM unit information corresponds to data in the CM table PMNODES. The CM maintains the node information to prevent differences in datafill for the XPM units. To clear an ISTb condition on one unit, set the XPM to BSY and RTS the XPM.
Page 471 Introduction to Remote Switching Center Multi-access 5-11 Display one or more tuples in a table that binds to CDT management. To display the tuples, enter the CHNL:PROT level of PMDEBUG command, and type: <DISPTBL table_id [<tuple_no> | R <begtuple> <endtuple> | all ] where table_id is the name of the table that appears...
Page 472 5-12 Introduction to Remote Switching Center Multi-access A bulk data update transfers the following information from the active RSC-M unit to the inactive unit. The update transfers the information when the inactive unit is RTS: the AN status (InSv or BSY) frequency selective ringing (FSR) codes subscriber states (idle or BSY) A bulk data update updates the inactive unit of the RSC-M with the active...
Page 473 Introduction to Remote Switching Center Multi-access 5-13 The following table lists critical dynamic data that transfer to the inactive unit. The active unit sends the critical dynamic data to the mate. The active unit first sends the data in bulk form. The active unit begins to send the data continuously as the data in the active unit change.
Page 474: Remote Switching Center Multi-Access (Rsc-M)
5-14 5-14 Datafilling Remote Switching Center Multi-Access 5-14 Remote Switching Center Multi-access (RSC-M) Functional groups BAS00012 Release applicability XPM07 Requirements Future software releases provides the requirement information for the Remote Switching Center Multi-access (RSC-M). Description This function describes the RSC-M peripheral with access multiplexers capabilities (AMC).
Page 475 Datafilling Remote Switching Center Multi-Access 5-15 Remote Switching Center Multi-access (RSC-M) (continued) A standard DMS 28 in. cabinet contains RSC-Ms. A standard DMS 28 28 in. cabinet contains a maximum of four shelves. The line group controller supports groups of main and extension (EXT) shelves. The minimum configuration requires one main shelf.
Page 476 5-16 Datafilling Remote Switching Center Multi-Access Remote Switching Center Multi-access (RSC-M) (continued) Note 1: This document does not cover translation datafill information for the AMC node. Note 2: This document does not cover how to provision of the AMC node. Limits The RSC-M module can handle a specified volume of traffic from a PBX interface.
Page 477 Datafilling Remote Switching Center Multi-Access 5-17 Remote Switching Center Multi-access (RSC-M) (continued) Datafill tables for RSC-M interfaces Table Purpose of table CLLI Common language location identifier. Identifies the far end of each announcement, tone, trunk group and test trunk. Also identifies national milliwatt test lines, and service circuit used in the RSC-M subsystem.
Page 478 5-18 Datafilling Remote Switching Center Multi-Access Remote Switching Center Multi-access (RSC-M) (continued) Datafill tables for RSC-M interfaces (continued) Table Purpose of table RCCPSINV Remote cluster controller P-side line inventory. Identifies the RSC-M module type, number, and port identification of the P-side links. Associates types of P-side links that connect the RSC-M and the remote with RSC-M ports.
Page 479 Datafilling Remote Switching Center Multi-Access 5-19 Remote Switching Center Multi-access (RSC-M) (continued) Datafilling table CLLI Subfield or Field Entry Description refinement CLLI refer to Common language location identifier. This subfields 16-character field identifies the far end of each announcement, tone, trunk group, test trunk, national milliwatt test lines, and service circuit.
Page 480 5-20 Datafilling Remote Switching Center Multi-Access Remote Switching Center Multi-access (RSC-M) (continued) Datafilling table CLLI (continued) Subfield or Field Entry Description refinement ADMININF refer to Administrative information. Operating company subfields personnel use this 32-character field to record administrative information. The switching unit does not use the information in this field.
Page 481 Datafilling Remote Switching Center Multi-Access 5-21 Remote Switching Center Multi-access (RSC-M) (continued) Datafill example for table CLLI Sample datafill for table CLLI appears in the following example. MAP display example for table CLLI CLLI ADNUM TRKGRSIZ ADMININF –––––––––––––––––––––––––––––––––––––––––––––––––––– MH5_RSCM 1204 RSCM Datafilling table SITE Table SITE contains data for the switching unit and for the remote locations...
Page 482 5-22 Datafilling Remote Switching Center Multi-Access Remote Switching Center Multi-access (RSC-M) (continued) Datafilling table SITE (continued) Subfield or Field Entry Description refinement MODCOUNT Module count. Range is 0 to 1000. OPVRCLLI Ver90 or Operator verification CLLI. Enter the CLLI alphanumeric assigned to the operator verification trunk group at the remote location.
Page 483 Datafilling Remote Switching Center Multi-Access 5-23 Remote Switching Center Multi-access (RSC-M) (continued) Table PMLOADS stores data for: the name of the active loadfile, which is the default load used with the LOADPM command and most system initiated activities the name of the backup loadfile, which is the load used if a problem occurs when the system loads or returns the active loadfile to service the file locations the update active loadfile field, indicates if the site wants the system to...
Page 484 5-24 Datafilling Remote Switching Center Multi-Access Remote Switching Center Multi-access (RSC-M) (continued) Datafilling table PMLOADS (continued) Subfield or Field Entry Description refinement ACTVOL alphanumeric Active volume. Identifies the device that stores the active loadfile. Range is the set of disk drive unit (DDU) volumes and system load module (SLM) disks available to the computing module (CM) (S00DXPM).
Page 485 Datafilling Remote Switching Center Multi-Access 5-25 Remote Switching Center Multi-access (RSC-M) (continued) Datafilling table PMNODES Table peripheral module nodes (PMNODES) is a read only table, that the CM uses to control XPM unit node tables. The system enters data in table PMNODES when you add or change entries in inventory tables.
Page 486 5-26 Datafilling Remote Switching Center Multi-Access Remote Switching Center Multi-access (RSC-M) (continued) Datafilling table PMNODES (continued) Subfield or Field Entry Description refinement MSGHOST 0 to 4095 Messaging host. External node transfers messages to this node. A messaging host must be able to transfer messages. PHYSHOST 0 to 4095 Physical host.
Page 487 Datafilling Remote Switching Center Multi-Access 5-27 Remote Switching Center Multi-access (RSC-M) (continued) Datafilling table PMNODES (continued) Subfield or Field Entry Description refinement PACKED Y or N Packed internal tables. Enter Y if internal node tables are packed on this node. Before this feature, the node table was compressed when the user used NODATASYNC option to RTS the XPM.
Page 488 5-28 Datafilling Remote Switching Center Multi-Access Remote Switching Center Multi-access (RSC-M) (continued) The datafill for basic call processing for table LTCINV appears in the following table. Fields that apply directly to basic call processing appear. Refer to the data schema section of the Translations Guide for a description of the other fields.
Page 489 Datafilling Remote Switching Center Multi-Access 5-29 Remote Switching Center Multi-access (RSC-M) (continued) Datafilling table LTCINV (continued) Subfield or Field Entry Description refinement CSLNKTAB refer to C-side link table. Subfields: NMPAIR and subfields NMPORT. NMPAIR 0 to 31 Network module pair number. Enter the network link where the PM is assigned, that corresponds to PM C-side links 0 through 15.
Page 490 5-30 Datafilling Remote Switching Center Multi-Access Remote Switching Center Multi-access (RSC-M) (continued) Datafilling table LTCINV (continued) Subfield or Field Entry Description refinement PROCPEC MX77AA Processor equipment product engineering MX77AA or codes. One PEC is required for each LTCO AX74AA unit. Enter the PEC for unit 0 first. The PEC AX74AA must reflect the minimum firmware capabilities in the processor complex of each unit.
Page 491 Datafilling Remote Switching Center Multi-Access 5-31 Remote Switching Center Multi-access (RSC-M) (continued) Datafilling table LTCINV (continued) Subfield or Field Entry Description refinement PEC6X40 alphanumeric The 6X40 equipment PEC. Enter the version of the NT6X40 you must use. EXTINFO EXTENSION_INFO. Note 1: Make changes to fields with multiple entries in the PROMPT mode. In nonprompt mode, you can leave out current entries.
Page 492 5-32 Datafilling Remote Switching Center Multi-Access Remote Switching Center Multi-access (RSC-M) (continued) Note 1: One LGCOi+ supports a maximum of two RSC-M main and extension shelves. Datafill tables and MAP displays indicate the PLGC is the host peripheral. For this reason, the LGCOi+ is referred to as a PCM30 line group controller (PLGC).
Page 493 Datafilling Remote Switching Center Multi-Access 5-33 Remote Switching Center Multi-access (RSC-M) (continued) for other fields. The default tuple is a CAS interface and has the value of CAS in the signaling type (SIGNTYPE) subfield in field attributes (ATTR). The system cannot delete this tuple. The system can change fields ES, SES, and thresholds for frame and slip losses.
Page 494 5-34 Datafilling Remote Switching Center Multi-Access Remote Switching Center Multi-access (RSC-M) (continued) Datafilling table CARRMTC (continued) Subfield or Field Entry Description refinement RTSML numeric RTS maintenance limit. Enter the number of (0–255) times in the audit interval that a carrier the system RTS before the system issues a warning.
Page 495 Datafilling Remote Switching Center Multi-Access 5-35 Remote Switching Center Multi-access (RSC-M) (continued) Datafilling table CARRMTC (continued) Subfield or Field Entry Description refinement ATTR LLFARST numeric Local loss of frame alignment RTS. Enter the (continued) (0 to 255) local loss of frame alignment RTS time limit. 30=3 sec This value appears in units of 100 ms.
Page 496 5-36 Datafilling Remote Switching Center Multi-Access Remote Switching Center Multi-access (RSC-M) (continued) Datafilling table CARRMTC (continued) Subfield or Field Entry Description refinement ATTR RFAIRST numeric Remote frame alignment indication RTS time. (continued) (0 to 255) Enter the remote frame alignment indication 30=3 sec RTS time.
Page 497 Datafilling Remote Switching Center Multi-Access 5-37 Remote Switching Center Multi-access (RSC-M) (continued) Datafilling table CARRMTC (continued) Subfield or Field Entry Description refinement ATTR AIS16OST numeric OOS time for AIS16 alarm. Enter the OOS time (continued) (0 to 255) for the AIS16 alarm. This value appears in 4=400 msec units of 100 ms.
Page 498 5-38 Datafilling Remote Switching Center Multi-Access Remote Switching Center Multi-access (RSC-M) (continued) Datafilling table CARRMTC (continued) Subfield or Field Entry Description refinement ATTR CRCRST numeric RTS time for CRC4 alarm. Enter the RTS time (continued) (0 to 255) for the CRC4 alarm. This value appears in 5=500 msec units of 100 ms.
Page 499 Datafilling Remote Switching Center Multi-Access 5-39 Remote Switching Center Multi-access (RSC-M) (continued) Datafilling table RCCINV Table RCCINV defines the RSC-M. To delete a RSC-M node from table RCCINV, you must delete tuples in GPPTRNSL that correspond to that RSC-M node first. Datafill for RSC-M for table RCCINV appear in the following table.
Page 500 5-40 Datafilling Remote Switching Center Multi-Access Remote Switching Center Multi-access (RSC-M) (continued) Datafilling table RCCINV (continued) Subfield or Field Entry Description refinement OPTCARD card list Optional cards. Enter the list of optional cards. List cards required to support the RSC-M, and appropriate optional cards.
Page 501 Datafilling Remote Switching Center Multi-Access 5-41 Remote Switching Center Multi-access (RSC-M) (continued) Datafilling table RCCINV (continued) Subfield or Field Entry Description refinement EXTINFO see subfields Y or N Extension shelf information. The boolean field EXTIINFO is set to default value N (no), and indicates the occurrence of an EXT shelf.
Page 502 5-42 Datafilling Remote Switching Center Multi-Access Remote Switching Center Multi-access (RSC-M) (continued) Datafilling table RCCINV (continued) Subfield or Field Entry Description refinement EXTINFO EXTSHELF Y or N Extension shelf. This field is datafilled with Y (continued) (yes) for an RSC-M with an EXT shelf. The field is a boolean with a default value of N (no).
Page 503 Datafilling Remote Switching Center Multi-Access 5-43 Remote Switching Center Multi-access (RSC-M) (continued) Datafilling table RCCINV (continued) Subfield or Field Entry Description refinement EXTINFO EXTSIDE L or R Extension shelf side. This field defines the EXT (continued) half shelf, left or right side. Note 1: For each RSC-M that table RCCINV defines, table RCCPSINV defines a corresponding tube to allow PCM30 links to be entered on the RSC-M P-side.
Page 504 5-44 Datafilling Remote Switching Center Multi-Access Remote Switching Center Multi-access (RSC-M) (continued) Datafill example for table RCCINV Sample datafill for table RCCINV appear in the following example. MAP example for table RCCINV RCCNAME FRTYPE FRNO SHPOS FLOOR FRPOS EQPEC LOAD EXECTAB CSPM CSLNKTAB...
Page 505 Datafilling Remote Switching Center Multi-Access 5-45 Remote Switching Center Multi-access (RSC-M) (continued) Datafilling table RCCPSINV Subfield or Field Entry Description refinement RCCNAME refer to Link trunk controller. This field consists of subfield subfields XPMTYPE and XPMNO. XPMTYPE RCO2 External peripheral module type. Enter the extended multi-processor system PM type RCO2.
Page 506 5-46 Datafilling Remote Switching Center Multi-Access Remote Switching Center Multi-access (RSC-M) (continued) Datafilling table RCCPSINV (continued) Subfield or Field Entry Description refinement CARRIDX MELCAS Carrier index. Enter a valid template name from table CARRMTC. If this action does not occur, enter DEFAULT for the default template name in table CARRMTC.
Page 507 Datafilling Remote Switching Center Multi-Access 5-47 Remote Switching Center Multi-access (RSC-M) (continued) Field selector (SEL) contains the definition for data selection for CAS interfaces. If CAS is selected, read-only information appears. This information is about RSC-M P-side links. Before you delete a tuple from table GPPTRNSL, make sure that lines do not connect to the RSC-M in table LNINV.
Page 508 5-48 Datafilling Remote Switching Center Multi-Access Remote Switching Center Multi-access (RSC-M) (continued) Datafilling table GPPTRNSL (continued) Subfield or Field Entry Description refinement AMCNO FRAME 0 to 99 Frame number. Consists of the frame number (continued) of the AMC. Entry can be different in the site, or different across the office.
Page 509 Datafilling Remote Switching Center Multi-Access 5-49 Remote Switching Center Multi-access (RSC-M) (continued) Datafilling table GPPTRNSL (continued) Subfield or Field Entry Description refinement AMC_SEL SELECTOR see subfield AMC type selector. Consists of CAS selector for CAS interfaces. MELCAS CAS interface selected. Refer to the following field.
Page 510 5-50 Datafilling Remote Switching Center Multi-Access Remote Switching Center Multi-access (RSC-M) (continued) Error messages for table GPPTRNSL The following error messages apply to table GPPTRNSL. Error messages for table GPPTRNSL Error message Explanation and action The switch adds an invalid tuple to table ADDING TUPLES .
Page 511 Datafilling Remote Switching Center Multi-Access 5-51 Remote Switching Center Multi-access (RSC-M) (continued) Error messages for table GPPTRNSL (continued) Error message Description Enter the CHA command to change a Info: Tuple already exist. tuple in GPPTRNSL. The tuple is present. Verify that the switch does not generate swerrs or traps.
Page 512 5-52 Datafilling Remote Switching Center Multi-Access Remote Switching Center Multi-access (RSC-M) (continued) At the CI level of the MAP display, CAS command LNTOGPP translates SITE, FRAME, GROUP, and DRAWER to RSC-M and carrier number. Command GPPTOLINE translates RSC-M and carrier numbers to the equivalent SITE, FRAME, GROUP, and DRAWER numbers.
Page 513 Datafilling Remote Switching Center Multi-Access 5-53 Remote Switching Center Multi-access (RSC-M) (continued) Datafilling table LNINV (continued) Subfield or Field Entry Description refinement CARDCODE see list Card code. The NT product codes define DMS switch physical line cards. Codes T1LOOP, T1ERTH, DC5A, and DC5ADD on CAS AMCs identify card codes equivalent to the LOOP, EARTH, DC5A, and DC5ADD line cards.
Page 514 5-54 Datafilling Remote Switching Center Multi-Access Remote Switching Center Multi-access (RSC-M) (continued) Tools for verifying translations The RSC-M does not use translation verification tools. SERVORD The RSC-M uses SERVORD to add or change lines that connect to an AMC. When the NEW command is used to declare a line in SERVORD, an unblocking command goes to the AMC to which that line connects.
Page 515 Datafilling Remote Switching Center Multi-Access 5-55 SERVORD example for RSC-M in prompt mode >NEW and press the Enter key. SONUMBER: NOW 94 5 11 AM > and press the Enter key. > 2790011 and press the Enter key. LCC: > 1FR and press the Enter key.
Page 517: Index
Index RSC–S (INTL) basic call processing 3-31, 4-30 datafilling activating nonprompting mode 2-4 BAS RSC–S (INTL) ESA operations–line and procedures 2-3 trunk 3-115, 4-113 prompts and prompting mode 2-3 Firmware downloading 3-210, 4-197 DATASIZE, table, datafilling 3-165 ISDN on RSC–S 3-160, 4-154 DCHINV , table, datafilling 3-183, 4-174 PCM–30 RSC–SR1 Trunking 3-129, 4-127 deactivating...
Page 518 6-2 Index KSETFEAT, table, datafilling 3-199, 4-188 PMLOADS, table, datafilling 3-41, 3-133, 3-211, KSETINV , table, datafilling 3-193, 4-184 4-39, 4-198, 4-199, 5-22 KSETKEYS, table, datafilling 3-200 PMNODES, table, datafilling 5-25 KSETLINE, table, datafilling 3-195, 4-186 prerequisites BAS RSC–S (INTL) ESA operations–line and trunk 3-107, 4-105 Firmware downloading 3-206 LCMINV, table, datafilling 3-73, 3-177, 4-71,...
Page 519 Index 6-3 Firmware downloading 3-209, 4-196 ISDN on RSC–S 3-152, 4-148 Signaling PCM–30 RSC–SR1 Trunking 3-126, 4-124 CAS interface, block diagram 5-3 RSC–S (INTL) basic call processing 3-25, 4-24 functionalities, CLASS services 5-5 tables, changing 2-4 overview of 5-2 translating types 5-2 BAS RSC–S (INTL) ESA operations–line and SITE, table, datafilling 3-39, 3-131, 4-37...
Page 522 Except as expressly authorized in writing by Nortel Networks, the holder is granted no rights to use the information contained herein. Information is subject to change without notice. Northern...

Nortel DMS-100 Series Reference Manual

Quick Links

Related Manuals for Nortel DMS-100 Series

Summary of Contents for Nortel DMS-100 Series

Table of Contents