Nortel Compact Ics 6.1 Installer Guide

							Event messages / 331
P0603539  02Compact ICS 6.1 Installer Guide
Displays
You should rarely see any event messages that are not described in the 
section entitled Significant event messages. If you do see one of these event 
messages, the Norstar system has followed its normal recovery from an 
unusual combination of system events. Although the problem is not a 
serious one, repeated occurrences of the event number should be reported 
as soon as possible.
Error 
codeMeaning
01Internal software error. Cannot acquire the B-channel from 
the B-channel arbitrator.
02Internal software error. There is no free line available for 
the call.
03A call that is not on the B-channel has been attempted. 
These kind of calls are part of EKTS service, which is not 
supported by this version of the software. Check with your 
service provider to make sure your your package does not 
include EKTS service.
04Internal software error. Failed to instantiate on the chain.
05Internal software error. Activation procedure failed.
06Internal software error. Index conversion failed.
07Unexpected digits on a Manual answer mode line. 
Configuration of the ICS and the network connection may 
not match.
08Internal software error. Cannot seize central office (CO) 
line on a BRI connection.
09Cannot get vterm (virtual terminal) from the Vterm Server.
0ACentral office did not respond to the SPID initialization 
request.
0BCentral office has rejected the SPID. Verify your SPID 
information programmed under Hardware and with your 
ISDN service provider.
0CInternal software error. Already instantiated on the chain. 
						

							332 / Event messages
Compact ICS 6.1 Installer GuideP0603539  02
As a result of some events, the Norstar system automatically restarts itself. 
The table on the next two pages lists all the event numbers and tells you 
which of these events are associated with Norstar system restarts. 
Most of these events are recorded in the System test log. The few 
exceptions to this are recorded in the System administration log, as 
indicated.
Event
MessageSystem 
RestartEvent 
MessageSystem 
Restart
101-106Yes285-298Yes
107No299No
108-112Yes362-363No
113No373No
114-116Yes400 (Admin log)Yes
117No401-411No
118-120Yes412-423 (Admin log)No
121-123No424-425No
124-125Yes426-430Yes
126-129No431No
130Yes432Yes
131-132No433No
133-134Yes441-451No
135-136No600-602Yes
137Yes603-613No
138-150No614Yes
151Yes615-629No
152No630Yes
160-164No631-646No
170-173No800-802No
196-211No803Yes 
						

							Event messages / 333
P0603539  02Compact ICS 6.1 Installer Guide
220 (Admin log)No804-807No
221-222No808Yes
223 (Admin log)Yes809No
224Yes810Yes
225-228No811-820No
229 (Admin log)Yes823Yes
230-235No824-825No
245-248No883No
250-256No900No
260-271No940-943No
280-283No950-989No
Event
MessageSystem 
RestartEvent 
MessageSystem 
Restart 
						

							334 / Tests
Compact ICS 6.1 Installer GuideP0603539  02
Tests
Norstar allows you to run a test which verifies the integrity of the 
installation wiring for Norstar sets. In addition, you can evaluate the 
transmission quality of a BRI loop through your service provider using a 
loopback test. 
Loopback test
The loopback test for BRI lines loops the incoming BRI payload back to 
the local exchange (service provider) for evaluation of the transmission 
quality. Loopback tests should be conducted only with guidance from the 
service provider. The results from the tests are returned to the service 
provider.
You can run loopback payload tests simultaneously on multiple loops or 
multiple cards. The loop must be provisioned to perform the test. All calls 
on the card you are testing will be dropped at the start of a loop payload test.
Starting and stopping a payload loopback test
Start with the display reading Tests.
1. Press 
≠. The display shows BERT-DN testsˆ.
2. Press 
‘. The display shows Loopback tests:.
3. Press 
≠. The display shows Show Module.
4. Press 
‘ the display shows Cards on KSU. If you want to run 
a test on the second card, or go to the next step.
 All calls on a BRI loop are dropped when you 
start loopback test.
While the loopback test is in progress, the BRI 
lines go out of service. There is no warning from 
the system. Pick an appropriate time to do a test 
and warn users that they will lose any calls in 
progress. 
						

							Tests / 335
P0603539  02Compact ICS 6.1 Installer Guide
5. Press ≠. The display shows the first S or T loop (if you are 
looking at a BRI-ST Card) or first NT-loop (if you are looking at a 
BRI-U Card). Payload loopback tests are not available for S-loops.
6. Press 
‘ until you see the loop you want to test.
7. Press 
≠. The display shows Payload loopback.
8. Press 
START to begin the test. The display shows the test name 
followed by 
running.
You can exit programming or move on to other programming tasks 
while the test is running, or begin a test on another loop. 
9. Press 
STOP to end the test. 
						

							336 / Tests
Compact ICS 6.1 Installer GuideP0603539  02 
						

							P0603539  02Compact ICS 6.1 Installer Guide
Usage Metrics
Hunt groupsInstaller password required
This feature gives you statistical information about hunt group calls.
From 
Usage Metrics, start with the display showing Hunt groups.
1. Press 
≠ the display shows Show group:
2. Enter the group number. The display shows Hg1 metrics.
3. Press 
≠ to display the date the information was last cleared.
4. Press 
‘ the display shows TotalCalls:
The displayed value is the total number of calls received by the hunt 
group, up to a maximum value of 99999.
5. Press 
‘ the display shows Ans:
The displayed values are the number of calls that were answered up to 
a maximum value of 99999 and the percentage of answer calls versus 
total calls up to a maximum value of 999.
6. Press 
‘ the display shows Avg ans: _ sec.
The displayed value is the average time in seconds that it took to 
answer a call, up to a maximum value of 999.
7. Press 
‘ the display shows Abndn:
The displayed values are the number of calls that were abandoned up 
to a maximum value of 99999 and the percentage of abandoned calls 
versus total calls up to a maximum value of 999.
8. Press 
‘ the display shows Busy:
The displayed values show the number of times the hunt group was 
busy up to a maximum value of 99999 and the percentage of busy call 
versus total calls up to a maximum value of 999.
9. Press 
‘ the display shows Ovrfl:
The displayed values show the number of calls that were sent to the 
overflow position up to a maximum value of 99999 and the percentage 
of overflow calls versus total calls up to a maximum value of 999. 
						

							338 / Usage Metrics
Compact ICS 6.1 Installer GuideP0603539  02
10. Press ‘ the display shows Avg Q:_ sec
The displayed value is the average time in seconds the call waited  in 
the queue, up to a maximum value of 999. 
						

							P0603539  02Compact ICS 6.1 Installer Guide
Maintenance records
Maintenance records are tables used to record information you have 
obtained while running a Maintenance session.
Before you begin, photocopy the tables in this section.
Recording information on the Maintenance 
records
To use the following records, do the following:
1. While running a Maintenance session, enter the information on a 
photocopy of the appropriate Maintenance record. 
2. Return the completed records to your Norstar distributor. 
						

							340 / Maintenance records
Compact ICS 6.1 Installer GuideP0603539  02
Version number record
The Maintenance session tells you the software versions of the System 
Processor (SP), and devices connected to the Norstar system. Use the 
following table to record these version numbers when you run a 
Maintenance session. You can check the SP version number under the 
heading System version. Device version numbers are found under the 
heading Port/DN status.
Version numbers
System versionPort/DN status
SP:Device:
Device:
Device:
Device:
Device:
Device:
Device:
Device:
Device:
Device:
Device:
Device:
Device:
Device:
Device:
Device:
Device:
Device:
Device:
Device: