1. Manuals
  2. Brands
  3. Northern Telecom Manuals
  4. Switch
  5. DMS-100 Series
  6. User manual

Northern Telecom DISPCALL DMS-100 Series User Manual

Hide thumbs Also See for DISPCALL DMS-100 Series:
Table of Contents

Advertisement

Quick Links

Download this manual
TAM-1001-003
DMS-100 Family
DISPCALL user guide
Technical Assistance Manual
BCS34 and up
Standard 3.01
July 1992

Advertisement

Table of Contents
loading
Need help?

Need help?

Do you have a question about the DISPCALL DMS-100 Series and is the answer not in the manual?

Questions and answers

Related Manuals for Northern Telecom DISPCALL DMS-100 Series

Summary of Contents for Northern Telecom DISPCALL DMS-100 Series

  • Page 1 TAM-1001-003 DMS-100 Family DISPCALL user guide Technical Assistance Manual BCS34 and up Standard 3.01 July 1992...
  • Page 3 Copyright © Northern Telecom 1988,1989,1990 1992 All rights reserved. Information is subject to change without notice. Northern Telecom reserves the right to make changes in design or components as progress in engineering and manufacturing may warrant. DMS , DMS SuperNode , and NT are trademarks of Northern Telecom.
  • Page 4 Publication history March 1991 BCS32 Standard • restructured and released as standard June 1992 BCS34 Standard 03.01 • added help command • converted commands to software format Revision bars in the table of contents identify the sections where technical information has been changed. Revision bars in the outside margin of a page indicate text that has been added or revised.

  • Page 5: Table Of Contents

    Contents About this document v When to use this document v How to identify the software in your office v Where to find information vi What precautionary messages mean vi How commands, parameters, and responses are represented in command descriptions vii Command examples ix DISPCALL utility 1-1 DISPCALL access level 1-1...
  • Page 6 iv Contents Interpreting DISPCALL output 5-1 Log reports and SWERRs 5-1 CCB dump 5-8 Call processing terminal linkage block (CPTLB) 5-8 PORT1PERM and PORT2PERM 5-12 Call handler block (CHB) 5-16 Call data block 5-29 Call processing mailbox (CPMB) data area 5-30 Call data block routing block (CDBRTEB) 5-32 PROT dump 5-33 UNPROT dump 5-33...

  • Page 7: About This Document

    When to use this document Northern Telecom (NT) software releases are referred to as batch change supplements (BCS) and are identified by a number, for example, BCS29. This document is written for DMS-100 Family offices that have BCS34 and More than one version of this document may exist.

  • Page 8: Where To Find Information

    More than one version of these documents may exist. To determine which version of a document applies to the BCS in your office, check the release information in DMS-100 Family Guide to Northern Telecom Publications, 297-1001-001. Number...

  • Page 9: How Commands, Parameters, And Responses Are Represented In Command Descriptions

    About this document vii WARNING Damage to backplane connector pins Use light thumb pressure to align the card with the connectors. Next, use the levers to seat the card into the connectors. Failure to align the card first may result in bending of the backplane connector pins.
  • Page 10 viii About this document Commands The command is represented in bold type. When commands are not case-sensitive, they are in lowercase. The command appears to the left of all other elements (parameters and variables). When truncated or abbreviated forms of a command are allowed, they appear directly beneath the long form of the command.

  • Page 11: Command Examples

    About this document ix The following is an example of a command expansion. bsy command parameters and variables Command Parameters and variables link ps_link noforce wait force nowait unit unit_no Parameters and variables Description force overrides all other commands and states in effect on the specified units. If the whole PM is to be taken out-of-service, confirmation, yes or no, is required.

  • Page 13: Dispcall Utility

    DISPCALL utility This part describes the DISPCALL utility, DISPCALL uses, and restrictions and limitations. DISPCALL access level DISPCALL is a low level internal diagnostic tool that monitors data associated with the death of a call or with a call being held for analysis. This data includes the originating and terminating ports of the call and the software and hardware resources used on the call.

  • Page 14: Restrictions And Limitations

    1-2 DISPCALL utility • translation omissions • network module speech errors or faults. The death of a call can cause any of the following customer problems: • cutoff Note: Cutoffs in the DMS-100 caused by network module troubles or by the death of a call are counted by the CPSUIC counter in the CP table of the Operational Measurements (OM).

  • Page 15: Calculating Node And Terminal Numbers

    Calculating node and terminal numbers Terminal identifiers A terminal is an external connection to the DMS-100, such as a line, a trunk, or a data link. DISPCALL recognizes which terminal to monitor by the terminal identifier entered by the DISPCALL user. A terminal identifier is composed of a node number and a terminal number.
  • Page 16 2-2 Calculating node and terminal numbers Figure 2-1xxx QDN command example >qdn 6213010 ------------------------------------------------------- 6213010 TYPE: SINGLE PARTY LINE SNPA: 613 LINE EQUIPMENT NUMBER: REM1 00 0 00 23 LINE CLASS CODE: SIGNALLING TYPE: DIGITONE LINE TREATMENT GROUP: LINE ATTRIBUTE INDEX: CARDCODE: 2X17AB GND: N PADGRPL STDLN...
  • Page 17 Calculating node and terminal numbers 2-3 Figure 2-2xxx QLEN command example >qlen 1 0 11 1 ------------------------------------------------------- LEN: HOST 01 0 11 01 TYPE: SINGLE PARTY LINE SNPA: 613 DIRECTORY NUMBER: 6215111 LINE CLASS CODE: SIGNALLING TYPE: DIGITONE LINE ATTRIBUTE INDEX: CARDCODE 6X17 GND N PADGRP STDLN BNV NL MNO N OPTIONS:...
  • Page 18 2-4 Calculating node and terminal numbers Figure 2-3 QUERYPM command example >post dtc 0 POST: >querypm PM TYPE DTC PM NO.: 0 Int. No.: 1 Node_No.:24 PMs Equipped: 38 Loadname: DT723AY1E,CHKSUM: 018 1 WARM SWACT is supported: VALID FNAME: BTMIA01 DTC 0 is included in the REX schedule.
  • Page 19 Calculating node and terminal numbers 2-5 Calculate the terminal number for Digital Trunk Controllers (DTCs) and Line Trunk Controllers (LTCs) as follows: terminal number = (carrier 32) + <channel> + 1 Note: Determine the carrier number, channel number, circuit number, and similar information by posting the peripheral.

  • Page 21: Dispcall Level Commands

    DISPCALL level commands Use the DISPCALL level of the MAP to monitor data associated with the death of a call or with a call being held for analysis. Accessing the DISPCALL level To access the DISPCALL level, enter the following from the CI level: dispcall and pressing the Enter key.

  • Page 22: Dispcall Commands

    3-2 DISPCALL level commands DISPCALL commands All of the commands available at the DISPCALL MAP level are described in this chapter. They are arranged in alphabetical order. The table below lists every command and indicates the page where its description is located. DISPCALL commands (continued) Command...

  • Page 23: Help

    DISPCALL level commands 3-3 help Function Use the help command to access online information on DISPCALL commands. help command parameters and variables Command Parameters and variables help command dispcall Parameters and variables Description command displays brief information and syntax of the DISPCALL command specified. The following commands are valid entries: quit show...
  • Page 24 3-4 DISPCALL level commands help Examples of the help command Example Task, response, and explanation help dispcall and pressing the Enter key. ↵ Task: Display information about DISPCALL commands. Response: QUIT - Quits from the DISPCALL environment - Set various parameters SHOW - Display saved calls SAVETID - Save a call based on tid...

  • Page 25: Clear

    DISPCALL level commands 3-5 clear Function Use the clear command to clear all the buffers of their contents. clear command parameters and variables Command Parameters and variables clear Qualifications None Examples The following table shows examples of the clear command. Examples of the clear command Example Task, response, and explanation...

  • Page 26: Death

    3-6 DISPCALL level commands death Function Use the death command to enable or disable data collection during the death of a call. death command parameters and variables Command Parameters and variables death search Parameters and variables Description when set to ON, saves the Protected or Unprotected (PUP) data for the agents in the call.
  • Page 27 DISPCALL level commands 3-7 death Responses for the death command MAP output Meaning and action UNDEFINED COMMAND Meaning: Something other than ON or OFF was entered as a parameter. Action: Verify command string and reenter. DISPCALL user Guide Technical Assistance Manual BCS34 and up...

  • Page 28: Disptid

    3-8 DISPCALL level commands disptid Function Use the disptid command to convert the terminal identifier (TID) number of an agent to a call process identifier (CPID) designation (text). To determine the TID of an agent, refer to “Calculating Terminal Identifiers” on page 2-1.
  • Page 29 DISPCALL level commands 3-9 disptid Responses The following table shows possible responses to the disptid command. Responses for the disptid command MAP output Meaning and action BAD TID Meaning: The terminal identifier entered was not valid. Action: Verify terminal identifier and reenter entire command string. DISPCALL user Guide Technical Assistance Manual BCS34 and up...

  • Page 30: Free

    3-10 DISPCALL level commands free Function Use the free command to deallocate and free all buffers. free command parameters and variables Command Parameters and variables free Qualifications To see how many buffers are currently allocated, use the query command. Responses The following table shows possible responses to the free command.

  • Page 31: Query

    DISPCALL level commands 3-11 query Function Use the query command to display • the number of allocated buffers • the number of allocated buffers currently in use • the current settings of the death parameters. query command parameters and variables Command Parameters and variables query...

  • Page 32: Quit

    3-12 DISPCALL level commands quit Function Use the quit command to exit DISPCALL. quit command parameters and variables Command Parameters and variables quit Qualifications All buffers are maintained even after the quit command is executed. TAM-1001-003 Standard 3.01 July 1992...

  • Page 33: Savelen

    DISPCALL level commands 3-13 savelen Function Use the savelen command to take a snapshot of the call on which a given line is currently active. The savelen command saves the CCB, and protected and unprotected data associated with the call. savelen command parameters and variables Command Parameters and variables...
  • Page 34 3-14 DISPCALL level commands savelen Examples of the savelen command Example Task, response, and explanation savelen host 00 0 05 07 and pressing the Enter key. ↵ where host is the site 00 0 05 07 is the LEN. Task: Specify a call by LEN 00 0 05 07.

  • Page 35: Savetid

    DISPCALL level commands 3-15 savetid Function Use the savetid command to take a snapshot of the call. The call is specified by supplying the TID of an agent or terminal in the path of the call. The savetid command saves the CCB, protected and unprotected data associated with the call.
  • Page 36 3-16 DISPCALL level commands savetid Examples of the savetid command Example Task, response, and explanation savetid 03 02 and pressing the Enter key. ↵ where is the node number is the terminal number Task: This command displays information saved from node 03, terminal 02. Response: No response.

  • Page 37: Set

    DISPCALL level commands 3-17 Function Use the set command to allocate the buffers needed to save the call data. set command parameters and variables Command Parameters and variables type Parameters and variables Description is the number of buffers to allocate and has the following ranges per bufer type: 0 to 30 for ccb 0 to 31...
  • Page 38 3-18 DISPCALL level commands Examples of the set command Example Task, response, and explanation set ccb 10 and pressing the Enter key. ↵ where is the type of buffer is the number of ccb buffers to allocate. Task: Allocate 10 CCB buffers. Response: Explanation: Responses...

  • Page 39: Show

    DISPCALL level commands 3-19 show Function Use the show command to display the collected data. show command parameters and variables Command Parameters and variables show what which format Parameters and variables Description format indicates the format to use when dumping the DATA. Acceptable formats include: formatted what...
  • Page 40 3-20 DISPCALL level commands show Examples of the show command Example Task, response, and explanation show cdb 0 and pressing the Enter key. ↵ where is the what variable and specifies the type of buffer to be displayed. is the which variable and indicates the buffer number to be displayed. is the format variable and indicates the format to use when dumping the DATA.

  • Page 41: Figure 3-1 Example Of Show Cdb 0 F Command

    DISPCALL level commands 3-21 show Figure 3-1 Example of show cdb 0 f command SHOW CDB 0 F > ** CDB Dump (0) for CALLID 426908 saved at 1987/02/04 CPMB: LINK/CPTLBPTR = 2C0D90 MAILBOX: MBQLINK = FFFFFF MBPROCQD = N CLONED = N MBINDEX = 0 MBLETTERCOUN = 0002 MBPROCPTR = 37E9E2 MBLETTERQ = FFFFFF STATUS = DISPLAYING MESSAGE:...

  • Page 43: Collecting And Displaying Call Data

    Collecting and displaying call data Several methods exist for collecting and displaying call processing data information. These methods and the procedures associated with them are described in this part. Recommendations for operation Following are recommendations for displaying accurate and complete DISPCALL output.

  • Page 44: Collecting Data When A Call Dies

    4-2 Collecting and displaying call data 8 If a Network is running in simplex, loss of integrity can cause a call to drop. In this instance analyzing a call death at the integrity analysis (NETINTEG) sublevel of the Network (NET) level of the MAP can aid in troubleshooting.

  • Page 45: Collecting Data For A Call Specified By Terminal Identifier

    Collecting and displaying call data 4-3 a. Periodically determine how many buffers are in use by entering QUERY DISPCALL b. Display all the information associated with the call by entering SHOW CALL buffer format For example, to display the data contained in the first buffer in a formatted form, type SHOW CALL 0 F To obtain a hard copy of the data of each in-use buffers, enter...

  • Page 46: Collecting Data For A Call Specified By Line Equipment Number

    4-4 Collecting and displaying call data type . For more information on the SET command, refer to SET CCB 10 SET on page 3-17. 3 To save the CCB, and protected and unprotected data for the specified node and terminal number, type SAVETID nodeno termno Note: The call must be up before the SAVETID command is processed.
  • Page 47 Collecting and displaying call data 4-5 type . For more information on the SET command, refer to SET CCB 10 SET on page 3-17. 3 To save the CCB, and protected and unprotected data for a specified LEN, type SAVELEN len Note: The call must be up before the SAVELEN command is processed.

  • Page 49: Interpreting Dispcall Output

    Interpreting DISPCALL output This part provides instructions for troubleshooting a call death using DISPCALL, log reports, and SWERRs. Log reports and SWERRs DISPCALL can be used in association with LOGUTIL to troubleshoot the source of a call death. In this part, the sample call death is a valid DN dialing a maintenance circuit.
  • Page 50 5-2 Interpreting DISPCALL output Figure 5-1xxx Log reports for call death AUD398 OCT14 16:41:35 7622 INFO CDB DUMP CALLID: 820001 4B00 1E00 FFFF FFFF FD80 0002 A5F1 3700 FFFF FFFF FDFD FDFD FD88 0016 A127 0AAA 550F 7055 9887 BE04 8540 8E02 9C71 8190 9090 9090 9080 9090 8080 9090 0289 0202 0202 0202 0202 0202 0202 0202 0202 0011 0041 23BA 0024 0000 FDE0 0030 1B00 0030 1B00 FD00...
  • Page 51 Interpreting DISPCALL output 5-3 procedure LINE_SETUP_PROCESSOR calls NIL_PROCESSOR. This procedure call indicates that the line setup processor cannot determine how to route the call to the terminating agent. This information indicates that the terminating agent is invalid. Therefore, procedure NIL_PROCESSOR calls CALLERROR, which causes the call to die.
  • Page 52 5-4 Interpreting DISPCALL output Figure 5-2xxx DISPCALL output with hexadecimal format DISPCALL>> >>>query BUFFER ALLOCATED IN USE PROT UNPROT MBUFF DEATH ON SEARCH ON PUP ON >>> show call 0 h ** Call Data Dump (0) for CALLID 820001 saved at 1987/10/14 16:41:35.766 WED.
  • Page 53 Interpreting DISPCALL output 5-5 Figure 5-3xxx Formatted DISPCALL output (part 1 of 3) >>>dispcall DISPCALL>> >>>query dispcall BUFFER ALLOCATE IN USE PROT UNPROT MBUFF DEATH ON SEARCH ON PUP ON % make call >>>query dispcall BUFFER ALLOCATED IN USE PROT UNPROT MBUFF DEATH ON...
  • Page 54 5-6 Interpreting DISPCALL output Figure 5-4xxx Formattted DISPCALL output (part 2 of 3) CHNL = 0000 PORT = 0000 NM_PAIR = 0000 NM_CHNL = 0000 LOGICAL = 0001 GAIN = 0000 LOSS = 0000 INTEG_VAL = 00FF PREFERRED_PL = EVEN_PLANE PMCHNL = PORT = 02...
  • Page 55 Interpreting DISPCALL output 5-7 Figure 5-5xxx Formatted DISPCALL output (part 3 of 3) RESELECT DIST_RING FTR_IN_EFFECT = N LCO_CALL CHARGE_TREATMENT = CHGA FORCE_CC_TIMI = N AC_ATTACHED EAEO_DATA: EA_CARRIER = NILC EA_LOCAL = N EA_OCS_NEEDED = N CALL_EVENT = INITIAL_EVENT: OVLPD : REALCMI = 0 DRCOUNT = 0 OLSTATE = OLFIRST...

  • Page 56: Ccb Dump

    5-8 Interpreting DISPCALL output CCB dump The Call Condense Block (CCB) is a data structure that contains information about a call in progress. A CCB may be displayed using the SAVETID and SAVELEN commands or when a call death occurs. This section provides an example of the formatted CCB dump shown in Figure 5-3 on page 5-5.
  • Page 57 Interpreting DISPCALL output 5-9 2 CPMBPTR: a pointer to the associated Call Data Block (CDB) while the CCB is linked to a call process. MYINDEX the index of the CCB in the segmented store table. PROCQD a boolean bit used while the CCB is linked to a call process. If true, it indicates that the call process is suspended on its own SOS mailbox waiting for a message.
  • Page 58 5-10 Interpreting DISPCALL output UP_OVER_WARM if true, indicates that a call can survive a warm restart. ECCBINDEX index of an Extended Call Condense Block (if one is involved in the call). EXTPTR pointer to extension block (if used). SEQNO sequence number used in conjunction with the CCB index to generate a unique call ID for each call.
  • Page 59 Interpreting DISPCALL output 5-11 • 20: xproc all messages are driven from the starter to the cross processor. • 21: preserved calls preserved over WARM SWACT, LM/RLM WARM takeback/takeover. • 22: one_end_disc a call is waiting on the last agent in the call to be disconnected, which usually occurs after talking and before idle.

  • Page 60: Port1Perm And Port2Perm

    5-12 Interpreting DISPCALL output Figure 5-7xx Cross matrix index diagram POTS LINE IBN LINE IBN TRUNK MADN LINE CTRLPORT call processing port number (0-31). CCBFC CCB Format Code (0-3). RECEIVER call processing identifier (CPID) of the receiver. CCBFA CCB Format Area often used to define formats for local and toll calls.
  • Page 61 Interpreting DISPCALL output 5-13 Figure 5-8xxx Example of PORT1PERM and PORT2PERM areas of CCB pump PORT1PERM : AGENT = LEN HOST 02 0 02 00 DN 7210061 PATHEND : CHNL=000F PORT=001B NM_PAIR = 0001 NM_CHNL = 0B6F LOGICAL = 0000 GAIN=0000 LOSS=0003 INTEG_VAL = 0007E PREFERRED_PL = ODD_PLANE PMCHNL =...
  • Page 62 5-14 Interpreting DISPCALL output • LOGICAL logical connection; boolean. This field is set to true if the call is an intraswitch call. If true, there if no physical pathend and all other fields are meaningless. If this field is false, a physical connection has been made and the field is set to false.
  • Page 63 Interpreting DISPCALL output 5-15 • 132 to 134 - IBN TWO-W AY TRUNK • 120 - 4-WIRE SUBSCRIBER • 199 - KEY SET • 203 - MADN DP • 204 - MADN DGT. FMTCODE agent format code that indicates which of the 32 refinements of the TEMP_FORMAT_AREA is being used.

  • Page 64: Call Handler Block (Chb)

    5-16 Interpreting DISPCALL output Call handler block (CHB) The Call Handler Block contains the translation and routing blocks associated with a call. Figure 5-9 on page 5-16 contains an example of the CHB. Figure 5-9xxx Example of CHB area of CCB dump CHB: XLAB: =XLA_RO...
  • Page 65 Interpreting DISPCALL output 5-17 RC translation return code. The return codes are as follows: • XLA_MORE_DIGITS more digits are required to complete translations at the current translation step. • XLA_CONTINUE the current translation step is complete. Translations continues with the next step. •...
  • Page 66 5-18 Interpreting DISPCALL output TX_TRMT extended treatment. IBN_TRMT_SET set to yes when the IBN treatment is also set. This prevents a Generalized No Circuit Treatment (GNCT) after an IBN treatment; boolean. MIN_DIGITS minimum digits required. MAX_DIGITS maximum digits required. PREFIX_FENCE number of digits to be consumed by translations. DATA_VER boolean set to true to initiate a trace of translations, route, and DMI.
  • Page 67 Interpreting DISPCALL output 5-19 RETRANSLATE retranslation required. This is a special boolean used for the DMS-250. CALLING_DR/AUTH_CODE_DR calling directory number or authorization code for the DMS-250. SCREENING_IN boolean indicating whether screening was incomplete. CAN_LCS boolean to cancel local call screening. CAN_SCRN boolean to cancel screening.
  • Page 68 5-20 Interpreting DISPCALL output • toll denied; boolean. • COIN coin phone; boolean. • Restricted Sent Paid, ANI digit 7; boolean. • ANI_FAIL boolean indicating whether the ANI received is in the correct format. This field is used by Service Switching Point (SSP) number services code call;...
  • Page 69 Interpreting DISPCALL output 5-21 • DIAL_CALL_WAITING_DEST dial call waiting • GROUP_INTERCOM group intercom • LNR_CODE last number redial code • FEATURE_ACTIVATION_VIA_ROUTING a feature is activated when the FTR terminator is called • VMX_DEST voice message exchange. CUSTGRP customer group (0 - 4095). SUBGRP subgroup number (0 - 7).
  • Page 70 5-22 Interpreting DISPCALL output ATTDNDOV a boolean indicating attendant override for Do Not Disturb (DND). CALLED_DR_SHIFTED a boolean indicating open-ended numbering. DOD_DESTIN a boolean for direct outward dial destination, which is used when there is a need to know that the destination was Direct Outward Dial (DOD).
  • Page 71 Interpreting DISPCALL output 5-23 Figure 5-10xxx Example of RTEB area of CCB dump RTEB: ROUTE = DNT_RT RC = 0 RTE_TYPE=DNT ROUTE_CHAIN = IN_CHA PREV_SATELLITE = N CHOICE =DIRECT OHQT_APPLIED = N QUEUEING_ACTIVE = N OHQ CANCSTDL INHIBIT_QUEUEING= N HUNT TRMT = UNDT = 0000...
  • Page 72 5-24 Interpreting DISPCALL output • 1: CPID_RTR_SET terminal agent identifier has been found by routing operations and is usually set into the call processing block. • 2: RTE_EXHAUST router exhausted the route list specified by the route identifier. Treatment is determined by the client procedure.
  • Page 73 Interpreting DISPCALL output 5-25 QUEUEING_ACTIVE boolean indicating whether queueing was in process. OHQ boolean indicating whether to allow queueing. CANCSTDL boolean indicating whether to cancel standard outpulsing logic. INHIBIT_QUEUEING boolean indicating whether no queuing is allowed. HUNT a boolean, when set to false, suppresses terminators from advancing through the member list.
  • Page 74 5-26 Interpreting DISPCALL output RESELECT boolean indicating whether an outgoing agent is reselected; boolean. DIST_REG boolean indicating distinctive ringing. FTR_IN_EFFECT boolean indicating whether the Feature Processing Environment (FPE) needs to be accessed to implement special features. LCO_CALL boolean indicating local coin overtime charging. CHARGE_TREATMENT charge treatment type for TDC (time dependency control);...
  • Page 75 Interpreting DISPCALL output 5-27 PFIXCNT prefix count (0 - 3). This field is no longer used. DSTSW number of the destination switch. ECHOSUP CPID of the echo suppressor. Entry is NIL if no echo suppressor is associated with the call. OVLPD Overlap data contains information on the trunks associated with a call.
  • Page 76 Entry point is from 0 to 15. MBI Message Billing Index, used for MUMR. CHARGE boolean; default is false. DATA_CALL boolean for Datapath use only. Note: Datapath is a trademark of Northern Telecom. TIMESTAMP CP timestamp. ORIGDISP traffic separation information. TERMDISP traffic separation information.

  • Page 77: Call Data Block

    Interpreting DISPCALL output 5-29 Call data block The Call Data Block (CDB) is a data structure that is used during active call processing. Each call process has a permanently associated CDB. The CDB contains the temporary data that is associated with a call when a call is being processed.

  • Page 78: Call Processing Mailbox (Cpmb) Data Area

    5-30 Interpreting DISPCALL output Call processing mailbox (CPMB) data area The Call Processing Mailbox data area contains information concerning the call processing mailboxes and associated queues as well as the pointer to the CPTLB for the call. The fields are as follows: LINK/CPTLBPTR an overlay of 1 LINK: a queue link that is used under the following conditions: - While the CDB is enqueued on the queue of unused CDBs.
  • Page 79 Interpreting DISPCALL output 5-31 • CPMBIDLE - initial state when the CDB is allocated; also used as a transient state during recovery from error conditions. MULTIWAIT boolean indicating whether a process can wait for up to 16 mailboxes simultaneously. STATUS status of the call processing system. Status indicates what action should be taken.

  • Page 80: Call Data Block Routing Block (Cdbrteb)

    5-32 Interpreting DISPCALL output • - NCIT • - NCIM • - NCON • 10 - NCOF. Call data block routing block (CDBRTEB) Call Data Block Routing Block (CDBRTEB) contains data concerning how the call routed to the terminator. Information contained in this area can indicate whether a call failed during routing.

  • Page 81: Prot Dump

    Interpreting DISPCALL output 5-33 • 3 - INCAMA to intertoll • 4 - local to local. PROT dump The PROT dump area is not currently used. UNPROT dump The UNPROT dump area is not currently used. DISPCALL user Guide Technical Assistance Manual BCS34 and up...

  • Page 83: List Of Terms

    List of terms Agency An optional plug-in software Module or subsystem at the top of the hierarchy of modules in the system. It encloses data, sequences run-time commands sent to terminals, and processes calls through their different stages. See also Call Processing Agency. Agent See Call Processing Agent.
  • Page 84 6-2 List of terms Call Processing The software system that handles the processes involved in setting up connections through the DMS-100 Family network between calling and called parties. Call Processing Agency A subsystem of software containing the code and data relating to a specific set of call processing features, and representing a number of Call Processing Agents with similar functions.
  • Page 85 List of terms 6-3 CPID Call Processing Identifier Directory Number (DN) The full complement of digits required to designate a subscriber’s station within one NPA - usually a three-digit Central Office code followed by a four-digit station number. Directory Number Extension Block Extension Block (EXT) In DMS-100 Call Processing, used to provide additional data space for a...
  • Page 86 6-4 List of terms Node Any unit that can accept or originate messages. Node Number A system assigned number unique to a node. Peripheral Module Intercept System Test (PMIST) A debugging tool that traces messages between the Peripheral Modules. PMIST Peripheral Module Intercept System Test PROT Protected Terminal Table...
  • Page 87 DISPCALL user guide Technical Assistance Manual © Copyright Northern Telecom 1988,1989,1990 1992 All rights reserved. Information is subject to change without notice. Northern Telecom reserves the right to make changes in design or components as progress in engineering and manufacturing may warrant.

Table of Contents