Home
>
Toshiba
>
Telephone
>
Toshiba Perception E Ex Digital Pbx Installation And Maintenance Manual
Toshiba Perception E Ex Digital Pbx Installation And Maintenance Manual
Have a look at the manual Toshiba Perception E Ex Digital Pbx Installation And Maintenance Manual online for free. It’s possible to download the document as PDF or print. UserManuals.tech offer 566 Toshiba manuals and user’s guides for free. Share the user manual or guide on Facebook, Twitter or Google+.
PROGRAMMING PROCEDURES SECTION 200-255-319 FEBRUARY 1992 TABLE 19-5a (continued) 7 7. Dialing was not complete when q was entered. A second q is required. 12. Enter the port number (TNNX) of the trunk (B) to be tested. 73. Requested trunk was idle and has been seized. 14. Requested trunk (B) is busy. 15. Requested trunk (B) does not exist in the system. 16. Enter the DN that should be dialed by the trunk under test, followed by a q , 17. After the dialing is complete, the audio from the trunk under test will be heard via the monitor link. Enterm when the test is complete. 18. The test has ended. The program will automatically return to the TRKprompt to allow another trunk to be selected. 19. The trunk under test(B) was released due to a ma/function or outside influence, such as the distant endgoing on-hook (ground start). 20. [9 was entered while Trunk B was still dialing. (See Note 17.) TABLE 19-5 (continued) Error Codes Error Code ERTPE 00 Program Name: Peripheral Diagnostic Data Block (TPER) Meaning The PCB tvoe conflicts with customer data. ERTPE 01 A PCB is not equipped in that location (enable). ERTPE 02 The cable is open or the port is inhibited by heavy traffic (enable). ERTPE 03 The entered port is a maintenance terminal (enable). ERTPE 04 No PCB is eauiooed in that location (disable). ERTPE 05 ERTPE 06 The port is busy. The PCB number or electronic/digital telephone number is out of range. ERTPE 07 ERTPE 08 The PCB type is not an NSTU or NEKWNDKU. The PCB type is not a trunk. ~~~ ~ -1 ~~ ~ - ERTPE 09 The PCB tvoe is not a DTMF receiver. I ERTPE 10 ERTPE 11 The entered PCB type is incorrect. No PCB is eauiooed in that location (inhibit). ERTPE 13 I No PCB is eQIJiDPed in that location (REQ = CALL TNNX). ERTPE 14 1 ~ ~~ ~~~~ The entered universal sort (slot) is uneauiooed or unassianed. I 19-14
PROGRAMMINGPROCEDURES SECTION 200-255-319 FEBRUARY1992 TABLE19-6 DISKDRIVEOPERATIONERRORCODES Error Codes Program Name: Floppy Disk Drive Error Error Code Meaning ERFD 01 File is closed. ERFD 02 Read error. ERFD 03 ERFD 04 ERFD 05 Write error. Directory is full. Disk is full. I ERFD 06 I End-of-file error. 1 ERFD 07 1 Disk drive is not readv. I ERFD 08 I Incorrect version number. I ERFD 09 ERFD 10 File is write-protected. File not found. ERFD 11 ERFD 12 ERFD FF Volume not initialized. File already exists. Other hardware is causina the error. 19-15
PERCEPTIONea, LCFVTR PROGRAMMING GUIDE MARCH 1991 Perception& 63 ex DIGITAL HYBRID PBX APPENDIX #2 LEAST COST ROUTING (LCR) and TOLL RESTRICTION (TR) PROGRAMMING GUIDE
PERCEPTIONeh, LCR/TR PROGRAMMING GUIDE MARCH 1991 PARAGRAPH 1. 2. 2.00 2.10 3. 3.00 4. 4.00 5. 5.00 6. 6.00 6.10 6.20 7. 7.00 PERCEPTION,,, LCR/TR PROGRAMMING GUIDE TABLE OF CONTENTS SUBJECT PAGE INTRODUCTION .............................................................................................. GENERAL DESCRIPTION ............................................................................... Least Cost Routing (LCR) ............................................................................. Toll Restriction (TR) ....................................................................................... NUMBERING PLAN (North America) ............................................................... Description ..................................................................................................... SPECIAL COMMON CARRIER.. ...................................................................... Description ..................................................................................................... PROGRAMMING .............................................................................................. General .......................................................................................................... CUSTOMER DATA PROGRAMMING FLOWCHART ...................................... PROGRAMMING EXAMPLES ......................................................................... General .......................................................................................................... Programming Example #I ............................................................................. PSYS Printout.. .............................................................................................. PACD Printout ............................................................................................... PCOS Printout ............................................................................................... PLCR (PAR) Printout.. ................................................................................... PLCR (ACTALL) Printout.. ............................................................................. Route Table #l Printout.. ............................................................................... Route Table #2 Printout.. ............................................................................... Route Table #15 Printout.. ............................................................................. Modify Digits Table Printout.. ......................................................................... PTOL (PAR) Printout ..................................................................................... Programming Example #2 ............................................................................. PSYS Printout.. .............................................................................................. PACD Printout ............................................................................................... PCOS Printout ............................................................................................... PLCR (PAR) Printout.. ................................................................................... PLCR (ACTALL) Printout.. ............................................................................. PLCR (AOCNOOi) Printout ........................................................................... Route Table #l Printout.. ............................................................................... Route Table #2 Printout.. ............................................................................... Route Table #3 Printout.. ............................................................................... Route Table #15 Printout.. ............................................................................. Modify Digits Table Printout ........................................................................... PTOL (PAR) Printout ..................................................................................... DTOL (CLS) - PTOL (CLSCNO) Restriction Class #0 Printout ..................... DTOL (CLS) - PTOL (CLSCNl) Restriction Class #1 Printout ..................... DTOL (CLS) - PTOL (CLSCN2) Restriction Class #2 Printout ..................... DTOL (CLS) - PTOL (CLSCN3) Restriction Class #3 Printout ..................... LOGIC ............................................................................................................... General .......................................................................................................... GENERAL LOGIC FLOWCHART ..................................................................... DETAILED LOGIC FLOWCHART ................................................................. 1 1 1 1 2 2 3 3 3 3 4 8 8 8 9 9 10 10 11 12 12 12 13 13 14 15 15 16 16 17 18 18 19 19 20 20 20 21 22 23 24 25 25 25 27
1. INTRODUCTION 1 .Ol This document has two main purposes: a) to describe the Least Cost Routing (LCR) and Toll Restriction (TR) features, and b) to serve as a supplement to Section 200-255-300, System Pro- gramming, in order to guide the service technician in LCRflR programming. Various examples, tables, and flowcharts are provided to clarify feature expla- nations. a .02 This document assumes that the reader is familiar with PERCEPTIONekex programming procedures and the mnemonics used with the LCR and TR data entry utility programs. 2. GENERAL DESCRIPTION 2.00 Least Cost Routing (LCR) 2.01 Least Cost Routing causes the system to select the least expensive trunk available for that particular time of day. The station user simply dials an LCR access code and the required telephone number. LCR will then select the optimally-priced route and automatically delete and/or insert any necessary digits (for MCI, Sprint, etc.) by analyzing the dialed telephone number (including area code and, in some cases, office code). 2.02 The three variable time schedules per 24- hour clock allow the end-user to take advantage of rate variations during these hours. The various routing combinations for the three time schedules are contained in 15 Route Tables. Each table is selected as a function of the dialed telephone number. 2.03 The LCR feature is compatible with and transparentto all other PERCEPTIONehex features. It is designed so that it is completely disabled until a simple parameter (LCR) is enabled in the System Data Block (DSYS Program). 2.04 If a Direct Trunk Access code (not the LCR access code) is dialed, the outgoing call is handled as a normal direct trunk access call without using LCR. PERCEPTIONeh, LCR/TR PROGRAMMING GUIDE MARCH 1991 2.05 LCR Data Blocks are separated from all other Data Blocks. It is unnecessary to change a com- pleted Data Block when adding the LCR feature to a system already in use, except to assign the LCR access code (DACD Program) or to enable LCR (DSYS Program). 2.06 There are three LCR classes (LCI , LC2, and LC3), which allow specific stations to be denied access to the most expensive routes. LC3 is the lowest class; LCl is the highest. LC3 routes are always selected first, no matter what class the station is allowed. If all LC3 routes are busy, and the calling station is allowed LC2, the system will try to select an LC2 route in the order programmed. If LCl is allowed, and all LC2 routes are busy, the system will try to select an LCI route. l The Class of Service Data Block indicates the LCR class of that particular Class of Service. l A warning tone is received by the station user if the last choice route is selected (if the WTA prompt, PAR table, DLCI Program, is pro- grammed to Y). l If all the routes are busy, busy tone is received by the station user, who may then activate the Automatic Callback feature. The station will then be called when the first trunk in that sta- tion’s LCR class is idle. When the station answers the callback, the idle trunk will be seized and the telephone number will be auto- matically dialed out to the distant end. 2.07 All of the above logic and the remainder of the Least Cost Routing and Toll Restriction features are described, and can be followed step-by-step, in the Detailed Logic Flowchart. Thisflowchartcan be used as a fault finding procedure for customer data programming, and to answer questions regarding what will happen when certain parameters are programmed in a certain way. 2.10 Toll Restriction (TR) 2.11 The Toll Restriction (TR) program causes the system to restrict (or not restrict) specific stations from calling certain area codes and/or office codes. 2.12 Toll Restriction can be used for long distance toll restriction, for restriction in the local area (home area), or both. The TR class also decides whether
PERCEPTIONea, LCWTR PROGRAMMING GUIDE MARCH 1991 to restrict calls to the local central office operator, international calls, and/or long distance directory assistance. 2.13 Eight different TR classes (CLS 0 w 7) can be programmed in the previously-described manner. +I+ Also, CLS 8 restricts all I+ and a + calls. 2.14 All stations programmed for TOL = NONE will have no restrictions. The TOL parameter (TR class number) is located in the DEKT, DSlT, and DTGP (TIECCSA Trunks) Programs. 2.15 Before a call via Least Cost Routing or Direct Trunk Access (DTA) is completed, the DTOL Program will decide whether or not the number being dialed is allowed. If not allowed, the originating station will receive overflow tone. If allowed, the call will be processed further. 2.16 All of the above logic and the remainder of the TOL parameter are described, and can be followed step-by-step, in the Detailed Logic Flowchart. Example: Fpllow a call through the Logic Flowchati according to what is programmed in Example #2. 3. NUMBERING PLAN (NORTH AMERICA) 3.00 Description 3.01 All telephone systems in the USA and Can- ada use the North American Numbering Plan. All PERCEPTION,&,, LCR/TR features are based on this plan. 3.02 The routing codes for Direct Distant Dialing (DDD) within the North American Numbering Plan consist of two basic parts: 1) A 3-digit area code or Numbering Plan Area (NPA) code. 2) A 7-digit telephone number made up 0f.a 3-digit central office (CO) code and a 4-digit station number. NOTE: When used together, these ten digits com- prise the network “‘address” or destination code for each telephone. l The first digit of the area code must be a number between 2 and 9. The second digit must be a 1 or 0. The third digit may be any number between 0 and 9. l The first two digits in the CO code must be any numbers between 2 and 9, except when inter- changeable codes are used (then the second digit can be any number between 0 and 9). The third digit of the CO code on all four subscriber numbers may be any number between 0 w 9 TABLE A NORTH AMERICAN NUMBERING PLAN Area Code Off ice Code NO/l X NNX X = any number from 0 - 9 N = any number from 2 - 9 Subscriber No. xxxx O/l = number 0 or 1 I (Table A). 3.03 The following are exceptions to the rule: 1) 2) 3) Service Code (Nli): This is used for various special local services and, when programmed properly, is recognized only as a service code. In this case, the system will act immediately after this 3-digit number is completed. Interchangeable Codes (ICC): In some areas, the second digit of the office code is allowed to be any number from 0 w 9. In this case, the office code may look like an area code (if the second digit is 0 or 1). If so, the PERCEPTlONe or PERCEPTIONex looks for a DD prefix (1) to identify whether or not the next 3-digit number is an area code. When ICC is used, 0 + a 3-digit number is always an areacode. When ICC is not used, the system identifies the area code by looking at the second digit of the first 3-digit number (if this digit is 0 or 1, the number is an area code; if not, the number is an office code). Inward WATS: This is a form of long distance service without a charge to the originating party. ,. - -.. t i;- .-1 -- i ‘i ,‘ -_. The area code is always 800. In PERCEPTIONeLex LCR, this type of call can be programmed (in the PAR table) as either a regular DDD call with an area code of 800, or as a toll free 800 call, routed via the -2-
4) local call route table (LCR). Long distance directory assistance (555): This is a call using any area code (or no area code) plus 5551212. If allowed, this type of call is routed via the LDI route table, as indicated in the PAR table, or via the route table (DAC = N) to which this area code is assigned. NOTE: When a DDD callis dialed, needed before the area cause the local operator to be connected. 4. SPECIAL COMMON CARRIER 4.00 Description 4.01 Dialing extra digits to access the Special Common Carrier (SPCC) trunks is not necessary if the LCR feature has been activated. The selection of SPCC trunks (like all other trunks) and the outpulsing of the extra digits (access code, authori- zation code, etc.), is accomplished automatically by the PERCEPTIONeLex LCR feature. This func- PERCEPTION,&, LCR/TR PROGRAMMING GUIDE MARCH 1991 tion is completely transparent to the station user. 5. PROGRAMMING 5.00 General 5.01 Customer data programming can be done in many different ways with the same results. The starting point and the particular order may differ according to personal preferences. As an example, one logical sequence for programming customer data is shown in the Customer Data Programming Flowchart. 5.02 For detailed information, see Programming Procedures, Section 200-255-300, in the PERCEPTIONekex Insfaallation and Maintenance manual, and the Logic paragraph in this LCR/TR programming guide (Paragraph 7). -3-
PERCEPTIONeh, LCR/TR PROGRAMMING GUIDE MARCH 1991 CUSTOMER DATA PROGRAMMING FLOWCHART To 0 Pate 6 NO 4 ------ YES ; Assign an LCR accesscode (LCWDACD). Telecom environment and - - - - - - Define parameters miscellaneous (PAR/DLCl). parameters. Comments: Assign area codes to - - - - respective route tables. YES NOTE: in any application where an SPCC is to be automatically dialed and accessed, LCR must be used. i NO AOC table is area code requires more than one route table. -4-
PERCEPTIONeb, LCR/TR PROGRAMMING GUIDE MARCH 1991 CUSTOMER DATA PROGRAMMING FLOWCHART (continued) List the office codes for the respective area codes that belong to a route table other than that shown in the ACT table (AOC/DLCl). I- Deny the LCR class as required for the respective class of service (DCOS). one LCR class NO NOTE: Always complete the SCHB prompt even when schedule B is not used. Define the route tables for all the assigned ACT and AOC tables (RTB/DLC2). I Modify digits as required (MDT/DLC2).
PERCEPTIONek, LCR/TR PROGRAMMING GUIDE MARCH 1991 CUSTOMER DATA PROGRAMMING FLOWCHART (continued) From NO Comments: Absorb the SPCC authorization code _ _ _ - - - 1 anator AL I ‘^../ (l’AH/U I VI I Define AUTHl *. - * IT,,2 paramebl (s) -. - ‘--v. NO toll restriction? From r A -0 Page 4 LCR programmed? NO Define the TOL arameters (PAWDTOL). Assign a TR class restricted stations 4 and TIE trunks (DSlT/DEKT/DTGP). Define each TR class used (CLSDTOL). -6-