Mitel Sx 200 Ml Pabx Lightware 16 Instructions Guide

							Software Troubleshooting Procedures 
Call Forwarding 
6.6 Table 6-7 outlines the procedure for troubleshooting Call Forwarding. 
Table 6-7 Call Forwarding Troubleshooting 
Problem 
Possible Cause/Solution 
No access to call forwarding. 
l If an attendant, ensure that COS option 123 - Attendant Call 
Forward Setup And Cancel is enabled. 
l If an extension user, ensure that at least one of the following COS 
options is enabled: 
- 206 - Call Forward - Busy 
- 207 - Call Forward - Don’t Answer 
- 209 - Call Forward - Follow Me 
No access to split (internal / 
l Ensure that COS option 260 Internal/External Split Call 
external) call forwarding. Forwarding is enabled. 
Reordertone and/or INVALID 
l Ensure that the forwarding destination you are entering is valid. 
error message. 
The forwarding destination must be (directly or translate into) one 
of the following: 
- an industry standard telephone 
- a SlJPERSETtelephone 
- an attendant console 
- a hunt group (not data or modem) 
- a night bell 
- an ACD path 
- a dial 0 access code 
- an LDN 
l The extension must be allowed (i.e., device interconnection) to 
connect to the forwarding destination. 
l The forwarding destination must not have COS option 234 - Never 
A Forwardee enabled. 
l The forwarding destination cannot be the same as your extension 
number (i.e. you can’t forward to yourself). 
l If entering a personal abbreviated dial access code as a 
forwarding destination, the forwarding extension must be 
programmed as a key system set. 
Page 1 of 3 
March 1997 Issue 1 Revision 0 6-15  
						

							Troubleshooting 
Table 6-7 Call Forwarding Troubleshooting (continued) 
Problem Possible Cause/Solution 
Reorder tone and/or INVALID 
l If entering a personal or system abbreviated dial access code as 
srror message. (cont’d) a forwarding destination, the forwarding extension must have the 
following COS option settings: 
- 245 - Abbreviated Dialing Access - enabled 
- 208 - Call Forwarding - External - enabled 
- 200 - Account Code, Forced Entry - External Calls - disabled. 
l If entering a personal speedcall button as a forwarding 
destination, the forwarding extension must have the following 
COS option settings : 
- 208 - Call Forwarding - External - enabled 
- 200 - Account Code, Forced Entry - External Calls - disabled. 
. Programming call forwarding while a system copy database 
operation is in progress is not permitted. 
l If programming “I’m Here” forwarding, the from party must be a 
industry standard telephone or a SUPEf!SE~ telephone, and 
cannot be a member of any type of voice mail hunt group. 
l If programming forwarding using dialed forwarding access codes, 
verify the following: 
- the extension is permitted access to the feature, 
- For feature access codes 03,04 and 05, the access code is 
entered, followed by one of: 1 (always), 2 (busy), 3 (no answer) 
or 4 (busy/no answer). 
Calls are not being forwarded 
l If a display set user, use the appropriate softkeys to examine the 
Droperly. current forwarding settings. The forwarding may have been 
changed by the attendant console or a sub-attendant. 
l If the forwarding was set using a personal speedcall button, 
ensure that the contents of the button still translate into a valid 
forwarding destination. Ensure using Form 9/ Form 45 that the 
key is still in fact programmed as a speedcall key. 
l Ensure that the COS options permit Call Forwarding. Check 
specifically COS options 200,206, 207, 208,209,245, and 260. 
Consult the features Description practice for proper settings. 
0 Ensure that the forwarding destination is idle and has COS option 
234 - Never A Forwardee disabled. 
l Ensure that the forwarding destination has not been 
deprogrammed. 
Page 2 of 2 
6-16 Issue 1 Revision 0 March 1997  
						

							Software Troubleshooting Procedures 
Table 6-7 Call Forwarding Troubleshooting (continued) 
Problem Possible Cause/Solution 
Calls are not being forwarded 
l Note that calls will not be forwarded if: 
properly. (cont’d) 
- it is the attendant or a SU/?ERSE~ telephone that is 
overriding/intruding 
- it already has been forwarded via any type of speedcall 
- it already has been forwarded twice without being answered or 
rerouted. 
l If a logical line appears on the extension and on another 
extension, calls to the first extension on the logical line will not be 
forwarded. 
l If the last programmed call forwarding with COS option 260 
(Internal/External Split Call Forwarding) enabled and 
subsequently the option was disabled, calls will be forwarded 
according to the external forwarding settings. 
l Any changes in device interconnection rules may prohibit calls 
from being forwarded. Ensure that the calling party can indeed 
connect to the forwarding destination. 
l Trunk calls to the extension will not be forwarded if calls are 
forwarded using any type of speedcall, with System option 21 
(Incoming To Outgoing Call Forward) disabled. 
l Calls will not be forwarded if the forwarding destination is the 
same as the calling party (i.e., calling party cannot be forwarded 
to itself). 
l Cannot forward a caller to a busy hunt group if the caller does not 
have the capability of camping on to the hunt group. 
l Cannot forward calls from the attendant console if the forwarding 
destination is a Dial 0 Access Code. 
l If forwarded via a speedcall of any type, the system may be 
encountering difficulty acquiring the necessary resources to 
complete the forwarding. Ensure that there are ample available 
receivers and/or outgoing trunks to allow this type of forwarding. 
Page 3 of 2 
March 1997 Issue 1 Revision 0 6-17  
						

							Troubleshooting 
Table 6-8 SUPERSE~Telephone Troubleshooting 
Problem Possible Cause/Solution 
Audio always come out of the 
l Check that COS option 612 - Headset Operation is not enabled 
handset, even when onhook. in the set COS, the ACD position COS or the COS of a verified 
account code that the user dialed. This is usually the source of 
the problem. 
l Ensure that the call is not being answered handsfree when COS 
option 612 - Headset Operation is enabled in the set’s COS. The 
call will go to the handset even if the call is answered using the 
speaker key or a line key. 
l Run the loopback test to ensure that the hookswitch is working 
correctly. 
6-18 Issue 1 Revision 0 March 1997  
						

							7 Maintenance Log 
Messages 
General 
7.1 This part contains the complete set of information messages which are recorded in 
the maintenance log when a significant event occurs. Each message is 
self-explanatory, identifying the event and providing details about it. Information on 
options available to maintenance personnel is included under the Action Required 
heading. 
There are three types of log reports: 
1. Fault Report - a report generated when the maintenance system or Call 
Processing detects a fault, or an abnormal condition. 
2. 
Reset Report - a report generated when a bay or the system is reset. 
3. Alarm Report - a report generated when a change in any of the alarm levels 
occurs. 
This part is divided into three sections which correspond to the three types of log 
messages. The Fault Reports section is arranged using the Alarm Code, an index 
number specific to the type of fault indicated. The Reset and Alarm Report sections 
are arranged in a logical manner. 
Information on access to the maintenance log, and the use of other maintenance tools 
may be found in the M-232 Maintenance Termha/ Practice. Information on overall 
maintenance philosophy and specific diagnostic tests may be found in the Genera/ 
Mahtenafxe hformation Practice. 
Table 7-l Fault Reports 
Alarm 
Code 
06 
Message 
ONS card failed at 02 01 01 00 ext 2101 
inject codec test Alarm Code = 06 
COV card failed at 01 0.5 01 00 ext 1501 
inject codec test Alarm Code = 06 
LS/GS trnk card failed at 02 02 0100 
inject codec test Alarm Code = 06 
E&M module failed at 02 02 01 00 
inject codec test Alarm Code = 06 
DTMF RX module failed at 02 02 01 00 
inject codec test Alarm Code = 06 
Action Required 
Do a directed test on the specified circuit to 
verify the problem. If the problem persists, 
refer to the Fault Isolation part of this Practice. 
Otherwise, investigate further, using the 
MONITOR DIAGNOSTICS and SHOW 
STATUS commands. 
Pagelofl5 
March 1997 Issue 1 Revision 0 7-l  
						

							Troubleshooting 
Table 7-l Fault Reports (continued) 
Alarm 
Code Message Action Required 
07 
08 
09 
10 ONS card failed at 02 01 01 00 ext 2101 Do a directed test on the specified circuit to 
Dgl L/B codec test Alarm Code = 07 verify the problem. If the problem persists, 
COV card failed at 01 05 01 00 ext 1501 refer to the Fault isolation part of this Practice 
Dgl L/B codec test Alarm Code = 07 forthis card or module. Otherwise, investigate 
further, using the MONITOR DIAGNOSTICS 
LWGS trnk card failed at 02 02 0100 and SHOW STATUS commands. 
Dgl L/E3 codec test Alarm Code = 07 
E&M module failed at 02 02 0100 
Dgl L/E3 codec test Alarm Code = 07 
DTMF RX module failed at 02 02 01 00 
Dgl L/B codec test Alarm Code = 07 
ONS card failed at 02 01 01 00 ext 2101 Ang Do a directed test on the specified circuit to 
L/B codec test Alarm Code = 08 verify the problem. If the problem persists, the 
COV card failed at 01 05 01 00 ext 1501 fault is isolated to the specified circuit. Refer 
Ang L/B codec test Alarm Code = 08 to the appropriate part of this Practice. 
Replace as required. Otherwise, investigate 
LWGS tmk card failed at 02 02 0100 further, using the MONITOR DIAGNOSTICS 
Ang L/B codec test Alarm Code = 08 and SHOW STATUS commands. 
E&M module failed at 02 02 0100 
Ang L/B codec test Alarm Code = 08 
DTMF RX module failed at 02 02 0100 
Ang L/B codec test Alarm Code = 08 
ONScardfailedatO201 01 OOext2101 The specified station has been unplugged, or 
Message lamp test Alarm Code = 09 lamp bulb needs to be replaced. 
ONS card failed at 02 010100 ext 222 Do a directed test on the specified circuit to 
Hook test Alarm Code = 10 verify the problem. If the problem persists, 
refer to the ONS Line Card part of this 
Practice. Replace as required. Otherwise, 
investigate further, using the MONITOR 
DIAGNOSTICS and SHOW STATUS 
commands. 
11 ONS card failed at 02 01 01 00 ext 2101 
Adc reference test Alarm Code = 11 
LWGS trnk card failed at 02 02 0100 
Adc reference test Alarm Code = 11 Do a directed test on the specified circuit to 
verify problem. If the problem persists, refer 
to the Fault Isolation part of this Practice. 
Otherwise, investigate further, using the 
MONITOR DIAGNOSTICS and SHOW 
STATUS commands. 
12 Card read test Alarm code = 12 
Page2of I! 
7-2 Issue 1 Revision 0 March 1997  
						

							Maintenance Log Messages 
Table 7-l Fault Reports (continued) 
Alarm 
Code Message Action Required 
13 LS/GS trnk card failed at 02 02 01 00 
Do a directed test on the specified circuit to 
Hybrid loopback test Alarm Code =13 verify the problem. If the problem persists, the 
fault is isolated to the specified circuit. Refer 
to the appropriate part of this Practice. 
Otherwise, investigate further, using the 
MONITOR DIAGNOSTICS and SHOW 
STATUS commands. 
14 
15 
16 
17 
18 
19 
20 DIG line card failed at 01 OS 01 01 ext 111 
DNIC output L/B test 
Alarm Code =14 
DIG line card failed at 01 08 01 01 ext 111 
DNIC input L/B test 
Alarm code =15 
DIG line card failed at 0108 0101 ext 111 
dn set cls test Alarm Code = 16 
DIG line card failed at 01 08 01 01 ext 122 
dn set bphone test AlarmCode = 17 
DIG line card failed at 01 08 01 01 ext 122 
dn set t’ducer test Alarm Code= 18 
DIG line card failed at 01 08 01 02 ext 222 
dataset L/B test Alarm Code = 19 
DTMF RX module failed at 02 02 01 00 
DTMF receiver test Alarm Code = 20 DNIC chip failed at circuit 01. Problem with 
DIGITAL Line Card. 
DNIC chip failed at circuit 07. Problem with 
DIGITAL Line Card. 
Replace the specified digital SUPERSfT 
telephone. 
Replace the specified digital SUPERSET 
telephone. 
Replace the specified digital SUPERSET 
telephone. 
Replace the specified dataset. 
Do a directed test on the specified circuit to 
verify the problem. If the problem persists, the 
fault is isolated to the specified DTMF 
Receiver. Refer to the DTMF Receiver part of 
this Practice. Otherwise, investigate further, 
using the MONITOR DIAGNOSTICS and 
SHOW STATUS commands. 
21 
34 
36 
40 
41 
42 
43 PRINTER failed at 00 00 02 00 
Printer test Alarm Code = 21 
Link 07 Channel 19 Failed isol to mcc PCM 
loopback test Alarm Code = 34 
DIG line card passed at 01 08 01 01 ext 111 
Alarm Code = 36 
ONS card failed at 03 01 01 00 
Analog 8804 test Alarm Code = 40 
ONS card failed at 03 01 01 00 
Analog 8804 test Alarm Code = 41 
ONS card failed at 03 01 01 00 
No path to junct # # Alarm Code = 42 
DIGlinecardfailedatOlO8OlOlextlll 
dn set earpiece test Alarm Code = 43 Do a directed test on the printer to verify this. 
Check if printer is off-line or disconnected. 
Refer to printer troubleshooting procedures. 
Failure on DX module. Replace Main Control 
Card Il. 
Information only. Previous problem 
corrected. 
Card fault - replace card. 
Card fault - replace card. 
Card fault - replace card. 
Refer to Digital set troubleshooting 
procedures. 
Page3of 1: 
March 1997 Issue 1 Revision 0  
						

							Troubleshooting 
Table 7-l Fault Reports (continued) 
Alarm 
Code Message Action Required 
44 
45 
46 
47 
46 DIG line card failed at 02 02 01 00 ext 111 Refer to Digital set troubleshooting 
dn set speaker test Alarm Code = 44 procedures. 
DIG line card failed at 02 02 0100 ext 111 Refer to Digital set troubleshooting 
dn set microphe test Alarm Code = 45 procedures. 
DIG line card failed at 02 02 01 00 ext 211 dn Refer to Digital set troubleshooting 
set mouthpce test Alarm Code = 46 procedures. 
Tl trunk card failed at 01 06 01 00 Trk 19 Refer to Tl Trunk troubleshooting 
tl channel LB test Alarm Code =47 procedures. 
DIG line card failed at 05 01 01 The modem at this location is not able to 
Modem answer test Alarm Code = 48 answer a call. Refer to applicable Dataset 
Troubleshooting procedure. 
49 
52 
53 
57 DIG line card failed at 05 01 01 The modem at this location is not able to 
Modem originate test Alarm Code = 49 originate a call. Refer to applicable Dataset 
Troubleshooting procedure. 
ONS card failed at 03 01 01 00 Card fault - replace card. 
Analog 8804 test Alarm Code = 52 
ONS card failed at 03 01 0100 Card fault - replace card. 
No path to junct # # Alarm Code = 53 
Link 07 Channel 19 failed Junctor l/back test Do a directed test on the specified link to verify 
Alarm Code = 57 the problem. Refer to the ,Ef?g;f?.eefji?g 
hformatbn Practice for link assignments. 
Investigate further, using the MONITOR 
DIAGNOSTICS command. 
101 ONS card failed at 02 01 01 00 ext 2101 OFF Information only. 
hook too long Alarm Code = 101 
COV card failed at 01 05 01 00 ext 1501 OFF 
hook too long Alarm Code = 101 
102 ONScardfailedatO201 01 OOext2101 Card Verify card has been removed. If alarm is 
removed Alarm Code = 102 raised due to this, either replace/t-e-install the 
card, or deprogram it via CDE. Refer to the 
Customer Data Entry Practice for details. 
COV card failed at 01 05 01 00 ext 1501 Card 
removed Alarm Code = 102 
DIG line card failed at 03 01 01 01 
Card removed Alarm Code = 102 
LWGS trnk card failed at 02 02 0 100 Tk 9 Card 
removed Alarm Code = 102 
CO trunk card failed at 02 02 0100 Tk 09 Card 
removed Alarm Code = 102 
Page4of 15 
7-4 Issue 1 Revision 0 March 1997  
						

							Maintenance Log Messages 
Table 7-l Fault Reports (continued) 
Alarm 
Code Message Action Required 
102 E&M trunk card failed at 02 02 0100 Tk9 Card 
(cont’d) removed Alarm Code = 102 
DID trunk card failed at 02 02 0100 Tk9 Card 
removed Alarm Code = 102 
UNIVERSAL card failed at 02 03 01 00 
Card removed 
Alarm Code = 102 
Tl trunk card failed at 02 06 00 00 
Card removed Alarm Code = 102 
103 ONS card passed at 02 01 01 00 ext 2101 Card Information only. 
installed Alarm Code =103 
COV card passed at 0105 01 00 ext 32 
Card installed Alarm Code =103 
DIG line card passed at 03 01 01 01 
Card installed Alary Code = 103 
LS/GS trnk card passed at 02 02 0100 Tk 9 Card 
installed Alarm Code = 103 
CO trunk card passed at 02 02 01 00 
Tk08 Card installed Alarm Code = 103 
E&M trunk card passedat 02 02 0 100 Tk8 Chid 
installed Alarm Code = 103 
DID trunk card passed at 02 02 0100 Tk 8 Card 
installed Alarm Code = 103 
UNIVERSAL card passed at 02 03 0100 Card 
installed Alarm Code = 103 
Tl trunk card passed at 02 06 00 00 
Card installed Alarm Code = 103 
Page5of 15 
March 1997 Issue 1 Revision 0 7-5  
						

							Troubleshooting 
Table 7-l Fault Reports (continued) 
1 
Alarm 
Code Message 
104 
105 ONS card failed at 02 010100 ext 2101 Wrong 
card in slotAlarm Code = 104 
COV card failed at 0 105 0 100 ext 1501 Wrong 
card in slotAlarm Code = 104 
LS/GS trk card failed at 02 02 01 00 Tk 08 
Wrong card in slotAlarn~ Code = 104 
CO trunk card failed at 02 02 0100 Tk 8 Wrong 
card in slotAlarm Code = 104 The specified card type is not programmed 
for the specified card slot. Use the SHOW 
CONFIG command to observe the correct 
configuration. Either insert the correct card 
type, or reprogram the card slot (see the 
Customer f%fa f3tfv Practice). 
E&M trunk card failed at 02 02 0100 Tk 8 
Wrong card in slotAlarm Code = 104 
DID trunk card failed at 02 02 01 00 Tk 09 
Wrong card in slotAlarn~ Code = 104 
UNIVERSAL card failed at 02 03 0100 Wrong 
card in slotAlarm Code = 104 
COV card failed at 0105 0100 ext 1501 The specified extension has been unplugged. 
Superset unplugged Alarm Code = 105 If this is not the case, check wiring. 
106 Database failed at 00 00 04 00 
Serious ram shortage Alarm Code = 106 
107 
108 Database failed at 00 00 03 00 
Serious CMOS shortage 
Alarm Code = 107 
RAM failed at 00 00 04 00 
No Ram space left Alarm Code = 108 
DNS card failed 
at 02 01 01 00 ext 120 
Msg reg overflow Alarm Code = 110 
COV card failed at 01 
05 01 00 ext 1501 
Msg reg overflow Alarm Code = 110 Action Required 
This is a warning. Stop CDE programming 
activity. Wait for a low traffic period, and reset 
the system. If this persists, search for an 
Alarm Code 108 message. Watch for further 
occurrences. 
This is a warning. Stop CDE activity. Wait for 
a low-traffic period, perform a COPY 
DATABASE, and reset the system using the 
new database. If this persists, search for an 
Alarm Code 109 message. Watch for further 
occurrences. 
NofurtherCDE programming will be possible. 
There is no RAM space available. Wait for a 
period of low traffic, and reset the system. If 
further programming is required, other 
devices, account code numbers, ARS strings, 
lr speed call numbers will have to be 
deprogrammed. 
The message registration counter for the 
specified extension has overflowed. The 
overflow threshold is 50,000. Ensure that the 
zounters are periodically reset at the 
Attendant Console. 
Page6ofl5 
7-6 Issue 1 Revision 0 March 1997