Mitel SX 200 DIGITAL Pabx General Descriptions Manual
Have a look at the manual Mitel SX 200 DIGITAL Pabx General Descriptions Manual online for free. It’s possible to download the document as PDF or print. UserManuals.tech offer 55 Mitel manuals and user’s guides for free. Share the user manual or guide on Facebook, Twitter or Google+.
Automatic Route Selection and Toll Control2.The ‘4800 baud CO trunk is used for data calls only. 3.The president and management are allowed use of the 4800 baud line subject to the time of day restrictions imposed by voice station requirements. 4.Technical staff are allowed use of the 4800 baud line at night only, but for local calls only. 5.Technical staff, management and the president can use any trunk to Florida (subject to time of day restrictions listed above). 6.The 1200 baud TIE line to Florida is only cheaper than CO trunks with lower or same baud rates during the day. 7.Administration staff are NOT allowed outgoing calls originating at a data station. TABLE 9-3 CUSTOMER REQUIREMENTS TABLE Digit String System Abbreviated Dial Number (England) System Abbreviated Dial Number (Florida) S-305-994-8500 (Florida) S-O (operator Long Distance) S-Else (Local) S-l -Else (Long Distance)Route Type 600Baud CO 600Baud CO 1200Baud CO 1200Baud CO 4800Baud CO 4800Baud CO 1200Baud Tie line 600 Baud CO 1200Baud CO 4800 Baud CO 1200Baud Tie line 600Baud CO 1200Baud CO 4800Baud CO 600Baud CO 1200Baud CO 4800Baud CO 600Baud CO 1200Baud CO 4800Baud CO 4800Baud CO 600Baud CO 1200Baud CO 4800Baud COTime DayNight DayNight DayNight DayNight COR’S 1..3 1..6 1..3 1..6 1..3 1..6 1..15 l..S 1 ..s 1.X 1..15 1 ..s 1 ..s 1..6 1 1 1 1 ..s 1 ..s 1..6 1 ..s 1..9 1..9 1..6Page 51
SECTION MITLS% Q9-094-22WNADay Zones 9.07In this example Day Zones (Form #21) are as follows: aDay Zone 1, Monday to Friday aDay Zone 2, Saturday l Day Zone 3, Sunday Modified Digits 9.98 The Modified Digit table (Form #22) defines digits which are replaced before outpulsing. Four digits are deleted because there are four digits in each system abbreviated dial number, described later in this section. The digit modification table used in this example follows: TABLE9-4 DIGIT MODIFICATION Entry OTY to DELDigits to Be Inserted 14011~44-62872821 24None 34l-305-994-8500 4 11 51None Route Definition 999 The Route Definition Table (Form #23) is derived from the Customer requirements table. The Route Definition Table final- izes the customer requirements table by specifying a trunk group number and the digit modification to use for the dialed digit string. Page 52
Automatic Route Selection and Toll Control TABLE 9-5 ROUTE DEFINITION Route ListsRoute NumTrunk GroupCOR GroupMod Digit Entry1121 2131 3221 4231 5321 6331 7452 8 143 924 3 1033311 4 52 12144 1324 4 14 3.44 15 114 162 14 17 3 14 18 144 1924 420 344 2134 422 14523 245 -24 3459.10If a call can use more than one route, Digit Translation pro- duces a Route List (Form #24) instead of a route. For example, if the digit string 8822 were produced, route 7, 8, 9 or 10 can be used to complete the call. Note here that the routes in each route list are entered in order of ascending cost. The following route list table defines the route lists for this example. Page 53
SECTION MITL9109-094-220-NAList Num i 2 34 5 6 7 8 9 IORoute PlanTABLE 9-6 ROUTE LIST TABLE First Second WTThird WTFourth I35 246 789 8910 11I213 1213 11 15I617 181920 18I921222324 IO 7I4 I4 9.11A Route Plan (Form #25) is used when time of day depen- dencies exist for a given digit string. Each entry in the route plan identifies either a route or route list from which a trunk group is selected. For this example the three time zones are: Time Zone 1 (TZl) = ( 08 . . I7 ) Time Zone 2 (TZZ) = ( 18 . . 22 ) . Time Zone 3 (TZ3) = ( 23, 0..7 ) The following route plans were created according to the customer’s requirements: ROUTE PLAN 1 TimeDayZone 1DayZone2DayZone3Zone Start Hr Rte List Start Hr Rte List Start Hr Rte List 1081081081 2I82182182 323 2232232 ROUTE PLAN 2 TimeDayZone 1DayZone2DayZone3Zone Start Hr Rte List Start Hr Rte List Start Hr Rte List 1083083083 2I84184I84 3234234234 Page 54
Automatic Route Selection and Toll ControlROUTEPIAN 3 TimeDayZone 1DayZone2DayZone3Zone Start Hr Rte List Start Hr Rte List Start Hr Rte List 1085085085 2186186186 3 236236236ROUTE PLAN 4 TimeDay Zone 1 ZoneStart Hr I Rte List 1 I 088 218 I 9 3 239Day Zone 2Day Zone 3 Start HrRte ListStart Hr 1Rte List The ARS programmer defines the digit string for the TIE trunk by the Digits Strings Form (Form #26). This trunk is programmed as shown below: ILeading Digits1 Return Dial Tone IRestricted COR Group 1 89NOUnrestricted In the System Abbreviated Dial Entry Form (Form #31), the following index numbers are defined: Index NumberDigit String I22 I 23 303059948500 89 0114462872821I1 These numbering plans result in the following system abbreviated dial numbers (sometimes referred to as system speed call numbers). LocationDirectory NumberSpeed Call Number Florida305-994-85008822 Florida89 (TIE Trunk) 8823 England011-44-62872821 8830An originator can dial either the speed call digit string or the full CO trunk directory number for Florida, but only the speed call digit string is used for any calls to England. Page 55
SECTION MITL9109-094-220-NA Scenarios 9.12The following illustrates how the ADRWARS system uses the tables in the above application. Each example assumes a [Monday..Friday] day zone (DZl). Abbreviations used are as follows: RPl= Route Plan 1 RLl= Route List 1 Rl= Route 1 DZl= Day Zone 1 TZl= Time Example 1At 1:00 PM a member of the administration staff dials the digit string 9-416-652-5555 from a 600 baud data terminal. Digit translation follows the path g-else to select RP4. 1:00 PM represents Tzl and RP4 [DZl, lZl] selects RL8. RL8 contains the routes R18, R19, R20.Each of the routes in the route list has legal COR values of [1..9], barring their use since administration staff COR is [10..153. The call cannot be completed.Example 2 A member of middle management dials the digit string 8830 from a 1200 baud data terminal at 10:00 AM.Digit translation follows the path 8-8-3-O to select RPl.10:00 AM represents TZl and RPl [DZl, lZl] selects RLl. RLl contains the routes Rl, R3, R5.Each of the routes in the route list allows only COR values from [1..31, barring their use, since a middle manager’s COR is [4..6]. The call cannot be completed. Example 3At. 9:00 PM a member of upper management dials the digit string 9-305-994-8500 from a 600 baud data terminal. Digit translation follows the path 9-3-0-5-9-9-4-8-5-0-O to select RP3. 9:00 PM represents lZ2 and RP3 [DZl, TZ2] selects RL6.Page 56
Automatic Route Selection and Toll Control RL6 contains the routes R12, R13, Rll, R14. Each of these routes will allow the call since 1.They all allow COR values 2..3 (upper management) 2.The originator’s baud rate of 600 is less than or equal to the baud rate of all trunk groups The call can be completed. Note the order in which the trunk groups are selected. All CO trunks of baud rate less than or equal to the TIE trunk are selected before the TIE trunk. Since the call originated during the night, the CO trunks are less expensive than the TIE trunk -as stipulated in the requirements - least cost route selection is demonstrated. Example 4 At 10:00 PM a’ member of the technical staff dials the digit string 8822 from a 4800 baud data terminal. Digit translation follows the path 8-8-2-2 to select RP2. 10:00 PM is lZ2, RP2 [DZl, IZ21 selects RL4. RL4 contains the routes R8, R9, RlO, R7. R7 allows technical staff’s COR. R7 uses trunk group 4. Trunks in trunk group 4 are each 1200 baud. The call is barred from completion on R7 based on incompatible baud rates. R8 allows technical staff’s COR. R8 uses trunk group 1. Trunks in trunk group 1 are each 600 baud. The call is barred from completion on R8 based on incompatible baud rates. R9 allows technical staff’s COR. R9 uses trunk group 2. Trunks in trunk group 2 are each 1200 baud. The call is barred from completion on R9based on incompatible baud rates. RlO does not allow technical staff COR, the call is barred on RlO.The call cannot be completed. Example 5 At 9:00 AM a member of the administration dials the digit string 8822 from 1200 baud data terminal. Digit translation follows the path 8-8-2-2 to select RP2. .9:00 AM is TZl, RP2 [DZl, I711 selects RL3. RL3 contains the routes R7, R8, R9, RlO.R7 is the TIE trunk to Florida. The call completes. If the TIE trunk is already in use, the call does not complete since no other route in the route list allows administration COR [10..15].Page 57
MITEL STANDARD PRACTICESECTION MITL9109-094-221 -NA Issue 3, September 1989 SX-200” DIGITAL PRIVATE AUTOMATIC BRANCH EXCHANGE (PABX) STATION MESSAGE DETAIL RECORDING @Copyright 1989, MITEL Corporation. All rights reserved. T”Trademark of MITEL Corporation @Registered Trademark of MITEL Corporationi
Station Message Detail Recording CONTENTSPAGE1. INTRODUCTION General................................... ;.........1Reason for Reissue....................................1 mBrief Description...................................... 12. DETAILED DESCRIPTION - TRUNK SMDR General............................................. 3Trunk Call Record Buffers................................ 3Recorded Information................................... 3Trunk SMDR Call Record Examples......................... 9Call Timing.......................................... 93. DETAILED DESCRIPTION - DATA SMDR General............................................13Recorded Information.................................. 13DATA SMDR Call Record Examples........................ 20Data Call Record Buffers............................... 264. DETAILED DESCRIPTION -ACD TELEMARKETERTM REPbRTlNG SYSTEM SMDR General............................................27Recorded Information.................................. 27ACD Call Record Examples.............................. 31ACD calls answered by Agents.......................... 31ACD calls answered by non-Agents..................... 32ACD calls abandoned................................ 32ACD calls interflowed................................ 33Unsupervised transfer of calls to the ACD system.......... 34Supervised transfer of calls to the ACD system............ 355. EXTERNAL DEVICES General............................................37Printer............................................. 37Tape Machine....................................... 37Cabling............................................ 37 .6. SMDR PROGRAMMING AND CONTROL General............................................39TRUNK SMDR Programming Options....................... 39DATA SMDR Programming Options........................ 407. OPERATIONAL PARAMETERS General............................................ 43Non-Recording Conditions.............................. 43Attendant-Handled Calls................................ 43Incoming Calls....................................... 44Data SMDR......................................... 44APPENDIX A - ACCOUNT CODES General . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-l Description. . . , . . . . . . . . , . . . . . . . . . . . . . . . . . . . . , . . . , . . A-l . . .III
SECTION MITL9109-094-221 -NA CONTENTS (CONT’D) PAGE Account Code Terminator..............................A-l Forced Account Codes................................A-l Operation..........................................A-2 APPENDIX B -DATA ACCOUNT CODES General.................................. Description................. :............. Incoming, Outgoing and Internal Data Calls....... incoming Data Calls....................... Outgoing and Internal Data Calls............. Incoming Call over Special DISA Trunk......... Other Calls Applying Account Codes.......... System Abbreviated Dial Numbers.............. Forced Account Codes....................... . . . . . . . .B-l . . . * . . . .B-l . . . . . . . .B-l . . . . * . . .B-l . . . . . . . . B-2 . . . . . . . . B-3 . . 9 . . . . . B-3 . . . . . . . . B-3 . . . . . . . .B-4 TABLE 2-l 3-l 3-2 3-3 4-l 6-l 6-2TITLEPAGE Summary of Fields in Trunk SMDR Records . . . . . . . . . . 7 Summary of Fields in a Data SMDR Record . . . . . . . . . 16 Data Call Disconnect Reasons . . . . . . . . . . . . . . . . . . . 17 Typical Data SMDR Call Records (Excluding Account Codes and System ID) . . . . . . . . . . . . . . . . . . . . . . . 20 ‘Summary of Fields in SMDR Records . . . . . ..~ . . . . . . . . 29 CDE-Selected SMDR Class of Service and System Options . . . . . . . . . . . . . . , . . . . . . . . . . . . . . . . . . . 40 CDE-Selected Data SMDR Class of Service and System Options . . . . . . , . . . . . . . . . . . . . . . . . . . . . . . . . . . 41 LIST OF CHARTS CHARTTITLEPAGE 2-1Trunk SMDR Printouts . . . . . . . . . . . . . . . . . . . . , . . , . . 9LIST OF TABLES iv