Mitel SX 200 ML PABX Instructions Guide
Have a look at the manual Mitel SX 200 ML PABX Instructions Guide 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+.
Features External DTRX Modem Pooling Call l Originate a DTRX session (see Data: DTRX Call Originate/Disconnect l Enter “CALL” followed by the Modem Pool Hunt Group access code, (omit the Modem Pool Hunt Group access code if the default modem pool hunt group is to be used), l Enter the destination name or number. (For external calls, dial the ARS leading digit string and the destination number). l Press RETURN. l The DTE displays RINGING while the destination is ringing and CONNECTED when the data connection is established. Data: Modem Pooling Queuing Description Modem Pooling callers who encounter a busy modem pool hunt group, destination dataset, data hunt group, or trunk group can queue for it. Conditions The following conditions apply to this feature: l DID trunk callers cannot queue. They receive busy tone unless an answer point is programmed in the Call Rerouting table for DID Recall Points on Busy. l DIL trunks can queue for a modem pool hunt group, dataset, or data hunt group, but they receive ringback tone, not busy. l Trunk callers have higher priority than internal callers for queuing. Programming Enable COS Option 900 (Data Station Queuing) in the caller’s Class of Service. Operation Operation varies depending upon the modem configuration as described below. Incoming Modem Pool Queuing The modem pool hunt group or destination is busy. Special busy tone is returned for 2 seconds, followed by busy tone when the campon occurs. ADL Outgoing Modem Pool Queuing The modem pool hunt group or trunk group is busy. Special busy tone is returned for 2 seconds, followed by busy tone when the campon occurs. DTRX Outgoing Modem Pool Queuing The originator receives the message “Call is Queued”. March 1997 issue 1 Revision 0 2-141
Features Description Device Interconnection Control Description This feature provides a means of disallowing connection between devices of different types. The feature is primarily intended to control trunk interconnection but applies to other devices as well. This is intended to provide a method of meeting interconnection regulations imposed by various regulatory authorities. The checks apply when a device calls another device, when a transfer (supervised or unsupervised) is attempted and when the console attempts to perform operations on devices. The sections in this practice mention Device Interconnection checks where they apply. See Flash Con&o/for details on controlling the ability of extensions to flash when extensions are involved with trunk calls. There are three aspects of the feature: Tenant Interconnection, the Device Interconnection Table, and COS Options. Tenant Interconnection, CDE Form 05 (Tenanting Interconnection Table) is described in the Tenanting Practice. The check for tenant connection is done when the Device Interconnection Table check is done. Other aspects of interconnection are done only if the tenant connection check passes. The Device Interconnection Table is a table that the installer can program to limit interconnection from one device type with another and with itself. This restriction can be applied in either direction if desired. The Device Interconnection Table alone applies when the two devices in question are not both trunks. When two trunks are to be connected together, the Device Interconnection Table restrictions apply. In this case, COS options may apply additional restrictions. The COS options apply additional checks when trunks are to be connected together. The COS options do not override the Device Interconnection Table but add finer control to the table. The options apply when a third party (a console, extension or trunk) attempts to leave two or more trunks connected together by a supervised transfer. The COS of the third party is used for the checks. The following rules apply for the COS option checks: l CO to CO trunk checks COS Option 313 (CO Trunk To CO Trunk Connect) l CO to Tie checks COS Option 314 (CO Trunk To Tie Trunk Connect) l Tie to CO checks COS Option 314 (CO Trunk To Tie Trunk Connect) and 319 (Extension non-CO Trunk To Trunk Connect) l CO to DID checks COS Options 315 (CO Trunk To DID Trunk Connect) l DID to CO checks COS Options 315 (CO Trunk To DID Trunk Connect) and 319 (Extension Non-CO Trunk To Trunk Connect) l Tie to Tie checks COS Option 316 (Tie Trunk To Tie Trunk Connect) and 319 (Extension Non-CO Trunk To Trunk Connect) 2-142 Issue 1 Revision 0 March 1997
Features Conditions l DID to Tie, Tie to DID checks COS Option 317 (Tie Trunk To DID Trunk Connect) and 319 (Extension Non-CO Trunk To Trunk Connect) l DID to DID checks COS Option 318 (DID Trunk To DID Trunk Connect) l For DISA trunks, the underlying circuit descriptor trunk types are checked against the device interconnection COS Options. l Incoming Tie trunks have no COS option checking. The following conditions apply to this feature: . . . . . . . . . . When a device hangs up from a three party call, the Device Interconnection feature applies between the remaining parties. The third party that is used in the COS option checks is the party that hung up. If the two remaining parties cannot connect, then the call is cleared down. When a device hangs up from a four or five party conference call, if there are only trunks left in the call, the Device Interconnection feature is applied between each trunk in the call (both ways). The third party that is used in the COS option checks is the party that hung up from the call. If at least one trunk can connect to one other trunk in the conference then the Device Interconnection check passes. If no trunks can connect to any other trunks in the call then the call is completely cleared down. If the console is not allowed connection to a device, it cannot exercise features affecting that device. Device Interconnection applies directly to trunks, stations, sets, data stations, modem pools and consoles. Connection is always allowed to night bells, call announce ports and LDNs. Device connection checking is done when an ACD position is directly dialed. The checks apply between the caller and the set where the position is logged in. No checking is done for ACD calls from an ACD path. No checking is done between callers and members of recording or auto attendant hunt groups. Checking is done with hunt groups using the tenant of the first programmed member of the hunt group. Checking is done with logical lines using the tenant of the SUPERSET telephone where the first appearance of the line resides. When a trunk is accessing ARS directly, or for trunks transferred into ARS before a trunk is seized, the COS used is that of the trunk itself. When an extension times out from reorder tone with a conference on hold, the above rules apply to the call that is left; it is as if the extension had hung up from the call. Programming Set the interconnection rules in CDE Form 30 (Device Interconnection Table) as required. Operation Enable the appropriate trunk connection COS options, see Description. None. March 1997 Issue 1 Revision 0 2-143
Features Description Dial Tone Disable Description Assignment of this feature to a dial-in trunk suppresses dial tone on an incoming trunkcall. If this feature is assigned to an extension, the extension does not receive dial tone whenever dialing is initiated. Conditions When applied to DISA trunks, the option suppresses the initial dial tone returned for dialing the DISA feature access code. The second dial tone, after a successful code is dialed, is not affected by the option. Programming Enable COS Option 701 (No Dial Tone) for the device. Operation None. Dial Tone - Discriminatina Description An extension having a feature enabled that prevents calls from ringing the extension hears a distinct dial tone (350/440 Hz, 400 ms on, 100 ms off for six cycles, then continuous tone) when going off-hook to make a call. These features include Do Not Disturb, Call Forwarding - Follow Me, or Call Forwarding - I Am Here. Conditions The following conditions apply to this feature: l The tone heard is the same one that is used for transfer dial tone. l COS Option 701 (No Dial Tone) must be disabled. Programming Enable COS Option 219 (Discriminating Dial Tone) for the extension. Operation None. Dictation Trunks Description This feature indefinitely extends the dialing stage on a trunk to allow tone-to-pulse or pulse-to-tone conversion, based on trunk circuit descriptors, of all digits dialed during a trunk call. Without the feature, only DTMF signaling is possible from extensions so equipped. Conditions The following conditions apply to this feature: l A DTMF receiver circuit is used for the duration of the call. l Dictation trunks cannot be put on hold but callers can be transferred to dictation trunks. l The dialing stage cannot be terminated on the trunk during the call. l A dictation trunk can’t be used for an outgoing modem pool. 2-144 Issue 1 Revision 0 March 1997
Features Programming Set the switches on the analog CO trunks cards to the appropriate setting; refer to the installation information Practice. Enable appropriate options for the trunks via CDE Form 13 (Trunk Circuit Descriptors); also see Trunk Circuit Descriptor Options. Operation Dial the necessary digits to access the dictation trunk. The system keeps the extension in dialing mode on the trunk and converts all digits dialed to the appropriate format for the trunk selected (tone or pulse). DID/Dial-in/Tie Intercepts if E 5 Description This feature allows a customer to specify that all DID and Dial-in Tie Trunk 8 calls directed to a busy extension (or one which does not answer within a 8 selected time period) are rerouted to a call rerouting point. As well, the 3. trunks can be programmed to be redirected immediately or to be redirected ‘D under certain error conditions. See Recallfor how this fits in with general I 8 3 recall operation. When a DID trunkdials in, the following conditions are tested in the following order: l If calling an LDN and the DID Attendant Access Night point is defined, then the trunk is rerouted to that point. l If calling a station, SUPERSET telephone, hunt group, or logical line and the DID Routing Point is defined, then the trunk is rerouted to that point. l If calling a busy industry-standard telephone, SUPERSET telephone, or logical line and the extension has forwarding - busy/always programmed, then the trunk is forwarded. l If calling a busy industry-standard telephone, SUPERSET telephone, logical line, or hunt group and the DID Recall Points on Busy is defined, then the trunk is rerouted to that point. l If calling a station or SUPERSETtelephone with Do Not Disturb enabled and a Do Not Disturb Intercep? point is defined, then the trunk is rerouted to that point. l If the station or SUP ERSETtelephone called does not answer and the extension has forwarding - no answer programmed, then the trunk is forwarded. l If the industry-standard telephone, SUPERSETtelephone, hunt group member, or logical line called does not answer and the DID no answer point is defined, then the trunk is rerouted to that point. The above applies, except for DND intercept, for Tie trunks, but using the equivalent Tie routing points. March 1997 Issue 1 Revision 0 2-145
Features Description Conditions The following conditions apply to this feature: l If an illegal number is dialed or an illegal feature is attempted and the DID Intercept Routing point is defined, then the DID trunk is rerouted to that point. The tenant of the trunk is used. The same applies for Tie trunks and the Dial-in Tie Intercept point. If no point is specified, reorder tone is given. l Calls routed to an LDN or to a console through the DID/Tie intercepts are identified as intercepted calls on the console display, when they are answered. l Calls routed to an LDN through DID Intercept busy/no answer routing point, show the tenant name of the called party when answered at the console. l If a vacant number is dialed and the DID Vacant Number Routing point is defined, then the DID trunk is rerouted to that point. The tenant of the trunk is used. The same applies for Tie trunks and the Dial-in Tie Vacant Number Routing point. l The DID or Tie no answer point applies in recall situations if the trunk was ringing a party and has not been answered yet by any device in the system (excluding recordings). See Last Number Red&l. l The reroute for no answer does not occur if calling a console, LDN or Night Bell. It also does not occur if already ringing the reroute point. l The reroute point on busy or no answer cannot be a console. l The tenant of the called party is used to determine the rerouting point. When a logical line is called, the tenant of the first appearance of the line is used. When a hunt group is called, the tenant of the first member of the hunt group is used. When an LDN is called, the tenant of the console with the lowest Bay/Slot/Circuit plid where the LDN appears is used. l The answer time timing for reroute/no answer is taken from COS Option 115 (Attendant Timed Recall - No Answer) of the trunk used for the reroute on no answer. If the time value is zero, then no reroute is done. l The application of busy and attendant night access points applies only when the trunk initially dials in. The no answer point applies when ringing any extension unless the trunk has been answered. This includes ringing an extension after a call forward no answer on the initial dialed destination. l COS Option 210 (Call Forwarding Inhibit on Dial-In Trunks) for the called party is checked on the always, busy, and no answer routing points. If the COS option is enabled for the point, then the reroute is not done. l Extensions may be restricted from receiving DID trunkcallsdirectlyfrom DID trunks, by selecting COS Option 226 (Inward Restriction - DID) for the extension. l For DID and Tie calls, the routing for all calls is done once dialing is completed. l The busy and no answer points do not apply when calling consoles, LDNs, or Night Bells. 2-146 Issue 1 Revision 0 March 1997
Features l If the console is programmed as the DID/TIE Busy/No Answer recall point (in Form 19, Call Rerouting Table), DID/TIE calls that are redirected to the console will not go to Attendant Automatic Overflow. Programming Enter the desired rerouting points via CDE Form 19 (Call Rerouting Table) in the appropriate tenant. Refer to Form 79 - Call Rerouting Tab/e in the Customer Data Entry Practice, for a list of the call rerouting options. To disable rerouting when a particular station or SUPERSETtelephone is called, enable COS Option 210 (Call Forwarding Inhibit on Dial-In Trunks) for the required extension(s). See Inward Restriction (DID) for details on blocking DID trunk calls altogether to a particular extension. Operation None. Digit Translation Description You can program the PABX to provide one of four Digit Translation Plans for rotary telephone sets. The default Digit Translation Plan is Plan 0. Table 2-5 Digit Translation Plans 7 pulses 8 pulses 9 pulses 10 pulses 8 pulses 9 pulses 10 pulses 1 pulse 3 pulses 2 pulses 1 pulse 10 pulses 4 pulses 3 pulses 2 pulses 1 pulse Conditions Only one translation plan may be in effect at a time. Programming Select the desired translation plan via System Option 46 (Digit Translation Plan). Operation None. March 1997 Issue 1 Revision 0 2-147
Features Description Direct-in Lines (DIL) Description Conditions Programming Operation This feature allows non-dial-in type trunks to ring specific answering points, rather than at the attendant console; this may vary with night service changes. An answering point may be one of the following in addition to a console or LDN: l an ACD Path l an extension number (industry-standard telephone, SUPERSET telephone, logical line) . a hunt group access code . a modem pool access code . a night bell access code. See Recall for effects on recall. Refer to Trunk Operation - Non-dial-in CO. In CDE Form 14 (Non-Dial-In Trunks) enter the desired answering points for each of the DAY, NIGHT1 and NIGHT2 modes of operation. None. Direct Station Select (DSS) Key Description You use the Direct Station Select (DSS) keys on a SUPERSETtelephone, or Programmable Key Module (PKM) in conjunction with the Busy Lamp Field (BLF) indicators located beside each DSS key. A DSS key is used to call, and connect calls to a device. The BLF indicator corresponding to the DSS key indicates the busy status of the device. The DSS key operates when the line appearance of the device is: . idle - pressing the DSS key will initiate,a call to the associated device. l talkingtoanother parby@atcanb eputnn..softhold - pressing the DSS key will put the other party on consultation hold, and initiate a call to the associated device. l listeningtodialtone - pressing the DSS key will initiate a call to the associated device. The DSS key is inoperable in all other states. For example, if the device is talking to one party with another party on soft hold, the DSS key will have no effect. Secretarial Option The BLF indicator associated with the DSS key always displays the status of the BLF party, thus limiting the need for supervised transfers. An 2-148 Issue 1 Revision 0 March 1997
Features Conditions The following conditions apply to this feature: . . DSS keys will not function on line appearances associated with trunks. DSS keys will not function when any feature associated with a template such as Hotel/Motel and Automatic Call Distribution are placed on the line appearance. Programming SUPERS/3 telephones To program DSS keys: March 1997 Automatic Transfer option is available to users with the SECRETARIAL enabled on their DSS keys. To transfer a call, the DSS key is pressed - the call is transferred with an automatic release to the BLF party. If the BLF party is idle, the transferred patty rings it. If the BLF party is busy, the system camps on the transferred call. If the two parties are not allowed to be connected together because of device interconnection restrictions, the system prevents the automatic transfer; i.e., the same conditions apply to these transfers as to any others. See also Busy Lamp Field in this document. . While in CDE Form 09 (StationlSUPERSETTelephones) or CDE Form 45 (Key System Telephones), position the cursor on the desired device and select the EXPAND SET softkey (Expand Set sub-form is displayed). Move cursor to the desired key. Move cursor to the TYPE column (use TAB key if necessary). Select the BLF/DSS softkey (Type becomes “Busy Lamp”). Press the TAB key twice to get to the DSS column OR Tp program the key with Secretarial Option, press the TAB key once to g”et to the SEC column. Then press the SECRETARIAL softkey (YES appears in the SEC column). Press the TAB key again to get to the DSS column. Select the DSS softkey (YES appears in the DSS column). Press the TAB key to get to the EXT NUM column. Enter the extension number of the device to be monitored by the BLF appearance. Select the ENTER softkey. Programmable Key Modules To program DSS keys: l Display CDE Form 09 (StationslSUPERSETTelephones) or CDE Form 45 (Key System Telephones). l Move the cursor to the bay/slot/circuit number of the SUPERSET 470, SUPERSET 420, or SUPERSET 430 telephone. An asterisk (*) appears to the left of the set type (410, 420, 430) if PKMs are programmed for the set. Issue 1 Revision 0 2-149
Features Description Operation . Select the EXPAND PKM softkey. “ENTER PKM NUMBER (l-3):” appears in the command line. . Type the address setting (1,2, or 3) of the desired PKM in the command line. . Select the Enter softkey. The system displays the Expand PKM Set Subform for the PKM. The Expand PKM Set Subform allows you to program the functions of the 30 available PKM keys. Keys 31 and 32 in the form are listed as RESERVED since the PKM only has 30 keys. Move cursor to the desired key. Move cursor to the TYPE column (use TAB key if necessary). Select the BLF/DSS softkey (Type becomes “Busy Lamp”). Press the TAB key twice to get to the DSS column OR To program the key with Secretarial Option, press the TAB key once to get to the SEC column. Then press the SECRETARIAL softkey (YES appears in the SEC column). Press the TAB key again to get to the DSS column. Select the DSS softkey (YES appears in the DSS column). Press the TAB key to get to the EXT NUM column. Enter the extension number of the device to be monitored by the BLF appearance. . Select the ENTER softkey. To call the BLF party: l Press the DSS key. To transfer a call to a station (without Secretarial option): * Press the DSS key. l press the RELEASE key/softkey. To transfer a call to a station (Secretarial option): l Press the DSS key. 2-150 Issue 1 Revision 0 March 1997