Nortel Compact Ics 6.0 Installer Guide
Have a look at the manual Nortel Compact Ics 6.0 Installer Guide online for free. It’s possible to download the document as PDF or print. UserManuals.tech offer 211 Nortel manuals and user’s guides for free. Share the user manual or guide on Facebook, Twitter or Google+.
Alarm codes / 311 P0992669 03Compact ICS 6.0 Installer Guide “X” = DS-30 port number (1-8) “Y” = Trunk Cartridge number (numbered from left to right) “Z” = Trunk port number Alarm troubleshooting Refer to the previous table before following these procedures. Alarm: 10 1. Check to see if there is a device connected to the ICS (that has a port number beginning with the number 1). 2. If there are no devices connected to the ICS, connect one and then press CLEAR. 3. If there are any devices connected to the ICS, check all the wiring associated with the devices. 4. Refer to the section in the Troubleshooting chapter entitled ICS down. Alarm: 37 1. Check that the BRI Card is properly installed. 2. Remove and re-install the BRI Card. 3. If the alarm persists, replace the BRI Card with another BRI Card of the same type. Alarm: 63 ZNo available DTMF receiversDTMF receivers are busy, not working properly, or have not been installed. Alarm: 74The ICS is unable to synchronize with the ISDN network.No clocking cartridge is installed. Alarm: 75Clocking for BRI lines is no longer synchronized with the network connection.The digital link has been disconnected. Example displayMeaningPossible causes
312 / Alarm codes Compact ICS 6.0 Installer GuideP0992669 03 Alarm: 52-X-Y 1. Check all connections to the Trunk Cartridge. 2. Check that the proper Trunk Cartridge is inserted in the appropriate slot of the ICS. 3. Remove and re-install the Trunk Cartridge. 4. If the alarm persists, replace the Trunk Cartridge with another Trunk Cartridge of the same type. Alarm: 61-X-Y 1. Check that the proper Trunk Cartridges are inserted in the proper slots of the ICS. 2. Enter programming and look under the Trunk/Line data heading. Check that the Trunk Cartridge type is correctly configured. Check that the Trunk mode and Answer mode settings do not conflict for every line connected to Trunk Cartridge Y. If Trunk mode is set to unsupervised, Answer mode must be set to Manual. OR Install a Trunk Cartridge in slot Y that matches the type of trunk you have configured. Alarm: 62-X-Y 1. Check that the proper Trunk Cartridges are inserted in the proper slots of the ICS. 2. Enter programming and look under the Trunk/Line data heading. Check that the Trunk Cartridge type is correctly configured. Check that the Trunk mode and Answer mode settings do not conflict for every line connected to Trunk Cartridge Y. If Trunk mode is set to unsupervised, Answer mode must be set to Manual. Alarm: 63-Z Enter programming and look under Lines in the Trunk/Line data heading. Check that the Answer mode is correct for all the loop start lines.
Alarm codes / 313 P0992669 03Compact ICS 6.0 Installer Guide Alarm: 74 Ensure an Expansion Cartridge with Clocking or Clocking Cartridge is installed in the ICS. Alarm: 75 Check the connection to your ISDN service provider.
314 / Event messages Compact ICS 6.0 Installer GuideP0992669 03 Event messages Event messages appear as items in the System administration log or the System test log of the Maintenance session. Most of these event messages can only be caused by an unusual combination of events, and should rarely occur. Each event is assigned a severity number. An S preceding this number, S4 for example, may appear in the event message. S9 is the most severe. If the Log is full, new event messages with a higher severity number replace existing event messages of a lower severity. For this reason, you should check event messages at regular intervals. You can then deal with all messages before they are replaced. For a complete list of Norstar events, consult the Norstar Alarm & Event Code Manual. Dealing with event messages For every event message that you see: 1. Record the event on the appropriate Maintenance record. 2. Consult the next section entitled Significant event messages. 3. To see if the event caused the Norstar system to automatically restart, consult the subsequent section entitled Complete list of event numbers. Significant event messages The table on the next page lists event messages that are relevant to Maintenance activities. The time that the message is recorded is also provided.
Event messages / 315 P0992669 03Compact ICS 6.0 Installer Guide Displays Event messageThe event message is recorded when… EVT196 S4there was a software error on the built-in modem EVT197 S4system operation is slow or there was a software error with the auto-attendant feature EVT210-YYYZ S4Loopback test YYY on Trunk Cartridge Z has been started EVT211-YYYZ S4Loopback test YYY on Trunk Cartridge Z has been stopped EVT220-21 S4the System administration log has been cleared by the DN (21 in this example) EVT221-21 S4the System test log has been cleared by the DN (21 in this example) EVT222-21 S5the DN (21 in this example) enters the debugging facility that is password protected EVT255 S9administered mode is not supported by the cartridge plugged into the slot EVT268-07 S8Restriction filter 07 has lost data due to a fault in the system memory EVT269-21 S8the Line/set restriction for the DN (21 in this example) has lost data due to a fault in the system memory EVT299 S1the system powers up after a power failure EVT373 S5the ICS restart diagnostic tool has been activated EVT400 S9Startup programming is performed using ² EVT407 S2there are no more codes for Speed Dial numbers EVT408 S2there is no more memory for Speed Dial codes EVT416-21 S3an invalid password has been entered by the DN (21 in this example)
316 / Event messages Compact ICS 6.0 Installer GuideP0992669 03 EVT418 S7a DN change is successful EVT419 S2the time setting has been changed EVT421 S8a DN change failed EVT422-21 S6a length change by the DN (21 in this example) has been requested EVT423-21 S6an individual DN change has been requested by the DN (21 in this example) EVT425 S6an attempt has been made to add a DN or access code which is already in use by the system EVT448 S8the system has started to copy data to a range of telephones EVT449 S4the system has completed copying data to a range of telephones EVT451 S5a remote user made three unsuccessful attempts to enter the installer password to access the Remote monitoring feature EVT452-21 S4a programming password has been changed by the DN (21 in this example) EVT453-21 S4a programming session has been initiated by a DN (21 in this example) EVT454-21 S5an invalid password has been entered by the DN (21 in this example) while attempting to start a programming session EVT799-00040BS7a call processing error on the fourth BRI loop; see Event message 799 on page 317 EVT822 S8Alarm code 63 is sent because there are no DTMF receivers for an incoming call Event messageThe event message is recorded when…
Event messages / 317 P0992669 03Compact ICS 6.0 Installer Guide Event message 799 Event message 799 indicates a call processing error has occurred on an ISDN line. The event number is followed by a number representing the line or loop number, and a code for the type of error. EVT799-XXXX YYS7In this example, the error has occurred on line XXX and the error code is 0A. 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.
318 / Event messages Compact ICS 6.0 Installer GuideP0992669 03 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. 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
Event messages / 319 P0992669 03Compact ICS 6.0 Installer Guide 151Yes615-629No 152No630Yes 160-164No631-646No 170-173No800-802No 196-211No803Yes 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
320 / Tests Compact ICS 6.0 Installer GuideP0992669 03 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.