Mitel SX 200 DIGITAL Pabx General Descriptions Manual

							System Features
consistently create the proper flash time thus preventing confusion between
flash and hang up attempts. On rotary dial sets, the user sends a calibrated
flash by dialing the digit “1”. On DTMF sets equipped with a flash key, the
user presses this key to send a switch hook flash to the PABX.Conditions
The following conditions apply to this feature:
lFor rotary dial telephones in analog Bays, the Calibrated Flash feature and
Message Waiting are mutually exclusive.
lDTMFsets equipped with a flash button must have a calibrated flash time
of 50 to 140 ms.
lRotary dial set users can perform a calibrated flash at any time, except
while dialing a number. (During dialing, the system interprets the digit 1
as part of the number).
l To use rotary dial telephones and the Calibrated Flash feature in analog
bays, a calibrated flash line card 
PN91 lo-310-OOO-NA, must be installed.
lFor ONS and OPS line cards, flash timers have no effect on the calibrated
flash detection circuits.
lFor DTMF telephones in analog Bays, the Calibrated Flash card must be
used if the telephone sends a flash between 50 and 140 ms; the card ex-
pands it to a 200 ms flash.
ProgrammingIn CDE Form 04 (System Options/System Timers):
l Enable Option 37 (Calibrated Flash).
lSet Option 52 (Minimum Flash Timer) to 200 ms. if a Calibrated Flash line
card is used.
l Enable Option 38 (Switchook Flash).
In the CDE Form 03 (COS Define):
lDisable COS Option 223 (Flash Disable) to allow a flash to be processed.Operation
In an established call:
lFrom a rotary set, dial the digit 1 and proceed as appropriate for the fea-
ture.
lFrom a DTMF set, press the cali brated flash button and proceed as appro-
priate for the feature.
CallbacksDescription
3.14 The Callback feature allows a user to be notified when a busy device be-
comes is free or when a set has been used after a no answer condition was en-
countered. 
						

							Features Description
Callback busy allows a user who has encountered a busy set, hunt group or
trunk group to have the call completed when the required set, hunt group or
trunk group becomes idle. The system continuously monitors the originating
set or console and the required device. When the originating set or console is
idle and the call can now be completed, the system calls the originating set or
console; when that set or console answers, it calls the required device.
Callback No Answer allows a user, after dialing an extension which does not
answer, to have the call completed later after the called party uses the tele-
phone. The system continuously monitors the originating set or console and
the called set. When the called set goes off-hook and then returns to idle, the
‘callback is handled in the same way as Callback Busy.
Up to 100 Callback requests may be active within the system at any time; how-
ever, a maximum of only 25 ARS callbacks is permitted in these requests.
See ATTENDANT CALLBACK BUSY/NO ANSWER and CALLBACK BUSY/NO AN-
SWER.Conditions
The following conditions apply to this feature:
lIf more than one callback request is active on any device, the requests are
queued and serviced in order of placement.
lDuplicate callback requests supercede the original request.
lif the two parties involved in a callback hold a telephone conversation
(not a conference) before the callback is honored, the callback is canceled
automatically.l
Callbacks to a busy ARS digit string are NOT canceled if the same ARS digit
string to which the callback was set is successfully dialed.
lA callback is canceled as soon as the telephone that originated it is rung,
even if a conversation is not established.l
Internal callbacks outstanding for more than 8 hours are canceled auto-
matically; callbacks to a busy ARS digit string are canceled after 1 hour.
lIf a callback is not answered by the originating set or console within 20
seconds, it is automatically canceled.l
If the called party becomes busy before the originating party answers the
callback, the originating party hears busy tone when the callback is an-
swered. The callback is not canceled and 
remains.active.l
When a callback is placed to a hunt group, it is placed to the whole hunt
group and not to any particular member.l
The scan for an idle hunt group member for the callback does not alter the
next extension to hunt for in a circular hunt group.l
Callback - Busy must be activated within 10 seconds of receiving busytone.
105 
3-14l
Campons to extensions are honored before callbacks.9 109-094-l 05-NA
Issue 3Revision 1 
						

							System Features
lOriginate Only extensions do not have access to this feature.
lCall Forwarding is ignored when a callback rings at the originating set.
lCallbacks ringing at a set cannot be picked up using CALL PICKUP.
lIf a SUPfRSETtelephone originates a callback, the callback always rings
the set’s Prime Line. If the prime line has Key line appearances, the system
places the key appearances’into a simulated busy state to prevent them
from ringing during the callback. If the prime line has Multiline appear-
ances, they remain unchanged.
lA callback only rings a SUPERSETor industry-standard telephone if the set
and the prime line are available.
ProgrammingNoneOperation
None
Call ReroutingDescription
3.15 This feature provides flexibility for the routing of incoming calls, atten-
dant access, call interception, and routings for various features. Different
types of calls can be routed to different answering points in DAY, NIGHT 1,
and NIGHT 2 service for each tenant. For a summary of call types, see Appen-
dix B.
Rerouted calls are processed differently than normal calls. The system consid-
ers rerouted calls to be important calls that must get through. Some features
on the reroute point are ignored because of this.
Also see DID/DIAL-IN/Tie INTERCEPTS, NIGHTSERVICES, CO TRUNK TYPES, and
UNIFORM CALL DISTRIBUTION.Conditions
The following conditions apply to this feature:
l Do Not Disturb is ignored on reroute points.
lRerouted callers are automatically camped on to the reroute point regard-
less of COS options. 
Campon is not done for consoles.
lValid access codes for reroute types, with the exceptions listed below, are:
LDNs, consoles, industry-standard telephones, SUPERSET telephones, log-
ical lines, hunt groups (all types except data hunt groups), ACD paths and
Night Bells.
lConsole access codes are not valid rerouting points for the following:
DID always routing to this tenant.
DID forward on busy/no answer.
Dial-in Tie always routing to this tenant.
Dial-in Tie forward on busy/no answer.
lLDN Access Codes are not valid rerouting points for Non-dial-in trunks
alternate recall points.9 109-094-I 05-NA
Issue 3Revision 1105 3-15 
						

							Features Description
lOnly Recording Hunt Groups are valid for recording routings.
ProgrammingOperation
lCO trunks use rerouting when they originate, following the routing points
programmed for each individual trunk; see CO TRUNKS TYPES.
lForwarding is examined on a reroute point (regardless of the number of
forwardings already done). See CALL FORWARDING.
lWhenever a DID trunk reroutes to the Night 1 point of its Attendant Access
Night Point, it does not recall due to a no answer on that point. The same
applies for Tie trunks and the Tie Attendant Access Night Point and for
DISA trunks, and for internal extensions and the Dial 0 point.
lDevice Interconnection checking is done between the rerouted party and
the reroute point. For LDN keys as reroute points, the checking is done be-
tween the calling party and the console with the lowest Bay/Slot/Circuit
PLID where the LDN key appears. If the connection is not allowed then the
reroute point is ignored.
All Call Rerouting entries are programmed in CDE Form 19 (Call Rerouting
Table). Enter a valid extension number or LDN access code in one of the DAY,
Nlor 
N2 service columns as desired. Whether the tenant of the calling or
called party is used depends upon the feature selected.
Also see NIGHT SERVICES.
See ATTENDANT NIGHT/DAY SWITCHING and 
SUPERSETNIGHT/DAY SWITCH-
ING for changing the night/day service.
Campon0
Description3.16 A device is able to indicate to a busy party that communication is desired,
and to be connected when the party is free. Also, the user can make a contin-
uing request for a trunk when the Trunk Group is busy, and be connected to a
trunk when one becomes free.
1
When calling an extension, hunt group, or ARS, if the destination is busy, the
caller usually receives a tone for a period and then camps on to the busy de-
vice. The tone given indicates whether or not 
campon is allowed during the
period, or is done at the end of the period.For some calls, the period is
skipped.
The busy called extension receives a tone alerting the par&y that there is a call
waiting; see 
CAMPON WARNING TONE.
An extension can consult the first waiting party (in hunt groups as well) using
the SWAP 
CAMPON feature.
Campon may be initiated on a trunk group that has been programmed to
give the expensive route warning; see EXPENSIVE ROUTE WARNING.
105 3-169 109-094-l 05-NAIssue 3Revision 1 
						

							System Features
For recall from 
Campon, see RECALL.Conditions
The following conditions apply to this feature:l
The identity of the first waiting party appears for a few seconds on a
SUPERSET~ telephone in talking mode (then reverts to normal display); on
a 
SUffRSET4DN telephone the identification display occurs in any mode.
lOn a SUPERSET4DN, the camped on party identification display takes pre-
cedence over the held party display.
lCalls camped on to a device are serviced in two groups, trunks and internal
callers, with trunks being served first. Within each group calls are 
serriced
on a first-come, first-served basis.
lWhen a party camps on to a busy trunk group, the DTMF receiver used to
reach the trunk group is released. The 
campon to the trunk group is hon-
ored when a trunk group is free and a DTMF receiver is free.l
The Attendant or an extension can transfer a call to a busy destination. The
transferred party camps on immediately.l
The transferred party can camp on as long as the transferring party can
camp on. COS checks are done on the transferring party and the transfer is
disallowed if the transferring party cannot camp on.
lThe transferred party hears system music while camped on; if there is no
system music, silence is heard.
lAll devices,except the console can camp on; consoles and extensions can
transfer a call into 
campon.
lIf Campon is allowed for a call, special busy tone is supplied for10 seconds,
after which the device is camped on automatically.
lIf campon is not allowed for the call then busy tone is heard for 30 seconds
and then the call is disconnected.
l DID and CO trunk calls that campon to busy devices receive ringback tone.
lTie and DISA trunk calls that campon to-busy devices receive busy tone (the
same audio as internal callers).
lIf there is no busy intercept then a DID trunk immediately camps on to a
busy device if the trunk is allowed to 
campon to the device.
lOn busy tone timeout, a serial call is dropped, and does not recall.l
On SUPERSET or SUfERSET4DN telephones, a CAMPON softkey is pro-
vided. On a 
SUPfRSfT3DN telephone a programmable feature key may be
provided.
lIf a SUPfRSfTtelephone is using the display or SUPERKEY feature while
camped on to ARS, the 
campon is not honored when ARS becomes avail-
able; it 
is only honored after the telephone exits from the feature and ARS
is available.l
Industry-standard telephones and SUPfRSfTteIephones that camp on to a
device without using a 
softkey hear busy tone while camped on. 
						

							Features Description
lAll trunk types and station and SUPfRSETtelephones can camp on.
lCalls can camp on to busy industry-standard telephones, SUPERSETtele-
phones, logical lines, hunt groups, and trunk groups.
lCampon is done immediately for reroute points that are busy regardless of
Campon COS options; see CALL REROUTING.
lCampon is done for Automated Attendant hunt groups regardless of cam-
pon COS options; see AUTOMATED ATTENDANT..
lCampon tones are not passed to lines which have COS Option 216 (Data
Security) enabled in their COS.
lThe Campon warning tone applies to the party being transferred to.
ProgrammingEnable COS Option 301 
(Campon) for the device to allow it to camp on.
If 
Campon is to be permitted on outgoing trunks, enable COS Option 237(Outgoing Trunk 
Campon) for the device in addition to COS Option 301 (Cam-
pod.Operation
Operation varies depending upon the device as described below:Industry-standard and 
SUPERSET 3 Telephones
To camp on to a busy device:l Dial the number-special busy tone is returned.
lAfter 10 seconds of special busy tone, Campon is done and busy tone is re-
turned. The called extension receives 
campon warning tone.
lWhen the called extension goes on-hook, the calling extension hears ring-
ing tone and the called extension is rung, or,
lThe called trunk group becomes idle-the system dials the originally
dialed digits.
SUPERSET3DN Telephone
If the set does not have a 
Campon feature key programmed, use the proce-dure for industry-standard telephones, above. If the 
Campon feature key is
programmed, use the following procedure.
To camp on:
lDial the number - busy tone is returned.
lPress the Campon feature key. Remain off-hook.105 3-18
SUPERSET 4 Telephone
9 109-094-l OS-NA
Issue 3Revision 1 
						

							System Features
l While receiving special busy tone, press the CAMP ON softkey. Remain off-
hook.
SUPERSET 4DN Telephone
lWhile receiving special busy tone, press the I WILL WAIT softkey. Remainoff-hook.
To Transfer into Busy:
lPut a party on consultation hold.
lDial the extension to transfer the call to. Special busy tone is heard.
.
0 Hang up.
Console
See ATTENDANT TRANSFER INTO 
CAMPON.
Campon Warning ToneDescription
3.17 When a device camps on to an extension or hunt group, a warning tone
is sent to the extension user over the current call. The warning tone can be
programmed to repeat every 5 to 15 seconds.Conditions
The following conditions apply to this feature:
lA different tone is given for internal and external calls. When an industry-
standard telephone or SUIJEKErtelephone calls, a single burst of 440 Hz
tone is given for 200 ms. For trunks and consoles calling, a double burst of
the same tone is given.
lThe tone is not heard by other parties involved in the call with the busy
extension, but a short silent period may be noticed.
lCOS Options 242 (Repeated Campon Beeps) and 216 (Data Security) are
mutually exclusive.l
COS Option 216 (Data Security) prevents the tone from being applied to
particular extensions. This has no effect on the SWAP 
CAMPON feature.
lRepeated campon beeps applies only when trunks are camped on.
lTrunks camped onto extensions with Repeated Campon Beeps do not re-
call.
lFor hunt groups, the tone is given to the first busy member of the huntgroup that is not Do Not Disturb and that is logged in (UCD).
9 109-094-l 05-NA
Issue 3Revision 1105 3-19 
						

							Features Description
lThe COS of this member is used to check if repeated campon beeps on a
hunt group applies to the first party in the hunt group. The tone is applied
irrespective of the line that is in use.
aIf the extension selected from the hunt group for the tone has Data Securi-
ty enabled then no tone is given. No other extension is selected.
lThe tone is not given to members of recording hunt groups.
lThe feature applies to SUPERSETtelephones only if their prime line.is a key
line (in which case all parties on the line get the tone) or their prime line
has no appearances and they are on their prime line appearance. 
_l
The feature applies to logical lines only if the line is a key line or a single
appearance multicall line. The first 
SUPEf?!XTtelephone where the line
appears gets the tone. All parties on the key line get the tone.
lThe warning tone is applied only if the party to get the tone is talking to
another party or is held by another party.
lMusic is removed while the Campon tone is applied (digital Bays only).
lExtensions in analog bays do not receive Campon tone if they are con-
nected to Music on Hold.
ProgrammingEnable COS Option 242 (Repeated 
Campon Beeps) for the extension if trunk
calls should continue to notify the extension. For hunt groups, this option
should be enabled for the first extension in the hunt group.
Enable COS Option 216 (Data Security) for the extensions that should not re-
ceive the warning tone. For hunt groups, this option should be enabled for
each extension in the group.
Set the cycle time for the repeated beeps via COS Option 255 (Repeated 
Cam-
pon Beeps Timer). The default setting is 10 seconds.Operation
A call camps on and a tone is heard. For SUPfRSETtelephones, the SWAP
CAMPON feature can be used to consult with the party that camped on. Alter-
nativety, for any extension, finish the current call; hang up, and the camped
on party rings the extension.
Class of Restriction (COR)Description
3.18 Fifty Class Of Restriction (COR) groups are available in the system to pro-
vide 50 different levels of outgoing 
call capabilities. Each extension,
SUPERSETtelephone, dataset, console or dial-in trunk is assigned a COR
which defines the outgoing call capabilities for that device. All devices with
the same COR have access to the same outgoing call capabilities. By using
CORs, the amount of ARS programming is reduced.
The Class of Restriction allows the system to restrict which trunk scan not be
accessed by a user. For example, COR 01 could restrict users from accessing CO105 3-209 109-094-l OENA
tssue 3Revision 1 
						

							System Features
trunks (local and DDD), WATS, and tie lines. COR 02 could restrict users from
accessing WATS, tie lines, and DDD (but allow local calls). COR 03 could re-
strict users from accessing DDD and WATS (but allow local calls and tie line
calls).
NOTE: All extensions belong to COR group 
1 in the default database.Conditions
The following conditions apply to this feature:
lCO trunks do not have a COR. When they access ARS, it is either using the
COR of the 
transfqrring or forwarding party, or no COR at all, giving uni-
versal access.
lThe COR may change temporarily for a caller through Verified Account
Codes.
lThe maximum dialed digits feature is based on the COR of the caller. Refer
to Practice 
9109-094-220-NA, Automatic Route Selection and Toll Con-
trol.
ProgrammingAssign a COR number to each extension, 
SUPERSE~telephone, dataset, Dial-
In Trunk and console via CDE Forms 09 (StationslSUPfRSETSets), 07 (ConsoleAssignments), 15 (Dial-In Trunks) and 12 (Data Assignment).
Refer to Practice 9109-094-220, Automatic Route Selection and Toll Controlfor additional information on COR programming,
Operation
None
Class of Service (COS)Description
3.19 Each extension, trunk, SUPERSET telephone, dataset, ACD Position, or
console is assigned a Class Of Service (COS) which defines the features avail-
able for that device. All devices with the same COS (which defines the COS
Options) have access to the same features. Fifty Classes Of Service are available
in the system to provide 50 different levels of feature accessibility. Each CO5
can have a name associated with it. COS names are not available with Generic
1002.
In the default database, all devices belong to COS 1.Conditions
The following conditions apply to this feature:
lSeveral COS options are mutually exclusive; these are identified with the
description of each feature.
lThe COS may change temporarily for a caller through Ve.rified Account
Codes (Travelling Class Marks). 
						

							Features Description
lThe COS used is sometimes that of the caller and sometimes that of the
called party. Check the feature to determine whose COS is used.
lLDNs do not have a COS. The COS for an LDN is determined from the low-
est Bay/Slot/Circuit 
PLID of the console where the LDN is programmed.
lLogical lines do not have a COS. The COS is determined from the first
SWERSETtelephone on which it is programmed. See LOGICAL LINES.
ProgrammingAssign the desired features to each COS via CDE Form 03 (COS Define).
Assign a COS to each console, extension, Dial-In Trunk, Non Dial-in Trunk,
dataset,andACDpositionviaCDEForms07,09,12,14,15,39and40.Operation
None
Conflict Dialing
Description3.20 The system can differentiate between conflicting extension numbers
such as “52345” and “5234”. This implies that extensions can be programmedas 
l-, 2-, 3-, 4-, or 5-digit numbers with the first digits being identical. The
system selects the shorter extension number if the next digit is not dialed
within a preselected time.
A conflict exists between two extension numbers if the first number is con-
tained in the second number, starting with the first digit. For example, 1234conflicts with 12345 but 1234 does not conflict with 123 (123 conflicts with
1234).Conditions
The following conditions apply to this feature:
lFirst digit conflict between the access codes assigned to Executive Busy
Override and the Callback 
- Busy features, and other numbers within the
numbering plan, are permitted.
lFeature Access Codes are not permitted to conflict with any other access
codes in the system. Extension numbers may conflict with Feature Access
Codes.
lARS leading digit strings are not permitted to conflict with any other ac-
cess codes in the system. Extension numbers may conflict with ARS leading
digits.
lModem Pool Hunt group access codes cannot conflict with any other ac-
cess code in the system and no access code may conflict with a Modem
Pool Hunt group access code.
lConflict dialing applies to features that need to have access codes entered
(call forwarding for example). This includes the programming features on
the 
SUPERSET telephones.105 3-22
9 109-094-l 05-NAIssue 3Revision 1