NEC Univerge SV8500, FP85-104 S1E Maintance Manual

FP85-104 S1E

Operations and Maintenance Manual

NWA-041693-001

ISSUE 2.0

Stock # 439TBA

To view the latest issue of this document go to NEC Knowledgebase @ http://www.kbase.cns.nec.com.au & search for NEC-10789

LIABILITY DISCLAIMER

NEC Australia Pty Ltd. reserves the right to change product specifications,
functions, or features, at any time, without notice.
Periodically changes are made to the information contained in this manual.
Although all efforts have been made to ensure that the contents are correct,
NEC shall not be liable for any direct, indirect, consequential or incidental
damages resulting from the use of the equipment, manual or any related
materials.

Should you find any error, NEC welcomes your comments. Please contact
NEC on 1800 819 766.
NEC Australia Pty Ltd. has prepared this document for use by its
employees and customers. The information contained herein is the
property of NEC Australia Pty Ltd. and shall not be reproduced without
prior written approval from NEC Australia Pty Ltd.

REFERENCES

This document may contain references to models, features and specifications
marketed in other countries and may not be applicable to the Australian and
New Zealand markets. Please contact your system representative for det ails.

The related Service/Technical Information Bulletin should be read in
conjunction with this document.

TRADE MARKS

term

is a registered trademark of NEC Corporation. ElectraMail and Electra

D

Elite are registered trademarks of NEC America, inc. PCPro is a trademark of
NEC Corporation. UNIVERGE is a trademark of NEC Corporation.

This document may include references to other brand and product names that
are trademarks or registered trademarks which belong to the respective
trademark owner.

Copyright © 2009

NEC Australia Pty Ltd.

Printed in Australia

Note:

This disclaimer also applies to all related documents previously published.

LIABILITY DISCLAIMER

NEC Infrontia Corporation reserves the right to change the specifica­tions, functions, or features, at any time, without notice.

NEC Infrontia Corporation has prepared this document for use by its
employees and customers. The information contained herein is the
property of NEC Infrontia Corporation, and shall not be reproduced
without prior written approval from NEC Infrontia Corporation.

All brand names and product names on this document are trade­marks or registered trademarks of their respective companies.

Copyright 2008 - 2009

NEC Infrontia Corporation

PRODUCT LIABILITY

PRODUCT LIABILITY

1. USING THE EQUIPMENT SAFELY

The following safety information describes how to avoid injuries while working with the equipment and how to
prevent damage to the equipment. Learn the meaning of the following symbols and then read this section
carefully before using the equipment.

SYMBOL DESCRIPTION

DANGER

Incorrect use of the equipment may cause personal injury or death.

WARNING

Incorrect use of the equipment may cause personal injury or a serious
system fault.

ATTENTION

Incorrect use of the equipment may limit the system performance or
cause the system to fail.

The telephone system can only be used in NEC-designated countries.

If a system-down, malfunction, defect or external factor such as an electrical failure indirectly causes a loss of profit, the
company (or affiliates) will not be held responsible.

The goal is to produce a comprehensive and accurate manual. However, if errors or omissions are found in this manual,
please notify NEC Infrontia Corporation.

If the system requires installation or repair, contact the dealer or its service technician.

Carefully read all the manuals that relate to the system.

PL- 1

PRODUCT LIABILITY

2. SAFETY CONSIDERATIONS

The following describes the safety considerations that must be observed before using the system, the power­related equipment and the peripheral equipment, such as consoles, the Main Distribution Frame (MDF),
telephones, PCs, printers, etc.

DANGER

If the system emits smoke or a burning, acrid odor, immediately turn off the system power.
Operating the system in this state might cause a fire, an electrical shock, or a system failure. After
turning off the power and confirming that the smoke has disappeared, contact the dealer.

If any equipment, such as the system, the main power source, a cabinet or peripheral equipment tips
over, turn off the power and contact the dealer.

If liquid reaches the inside of the system or the main power source, turn off the power. Operating
the system in this state might cause a fire, an electrical shock, or a system failure.

Do not touch the internal parts of the main power source to disassemble or configure it. This action
may cause a fire, an electrical shock or a system failure.

R

W

P

NEC Infrontia Corporation does not take any responsibility for disassembled or reconfigured
equipment.

Do not put any container objects (such as a vase or a cup) on the main power source or any
peripheral equipment. It might cause a fire, an electrical shock or a system failure.

Do not tamper with, modify, forcefully bend, forcefully remove or twist an electrical cord or any
wiring to or from the system, the main power source or any peripheral equipment. It might cause a
fire, an electrical shock, or a system failure. If the wiring is damaged, contact the dealer.

dust

Correctly insert all of the electrical plugs into the electrical outlets. Before inserting a plug into an
electrical outlet, ensure that there is no dust on the plug’s blades. If there is dust on a blade, it might
cause a fire.

Do not use power other than the power that was designated for the system when it was installed.

PWR

PL- 2

DANGER

PRODUCT LIABILITY

PWR

Do not put any metal or combustible objects into a vent of the system, the main power source, or
any peripheral equipment. Operating the system in this state might cause a fire, an electrical shock,
or a system failure. If this occurs, turn off the power and contact the dealer.

Be careful when using any peripheral equipment’s Liquid Crystal Display (LCD). If the liquid
leaks, it can be harmful to the user and to the system.

Before connecting any non-NEC, customer-provided equipment, check with the supplier to ensure

Do not attempt to repair or move the main power source without assistance from the dealer.

?

that the equipment is compatible. If the supplier cannot confirm the compatibility, do not connect
the equipment. Connecting incompatible equipment might cause a fire or an electrical shock.

PL- 3

PRODUCT LIABILITY

WARNING

Do not place any object on the system or the main power source. If the object falls, it might cause
personal injury or damage to the equipment.

When removing a plug from an outlet, be sure to grip the plug, not the cord. Gripping the cord to
remove the plug could cause a fire or an electrical shock to occur.

If lightning causes a fault, contact the dealer.

ATT EN TIO N

Contents
Static Sensitive
Handling
Precautions Required

Provide the appropriate temperature, humidity, and ventilation on an around-the-clock basis. For
example, at a height that is one meter (3.28 feet) above the floor, the temperature should be between
20° C and 25qC (68° F to 77° F) and the humidity should be approximately 50%.

Take appropriate anti-static measures so that the other end of the anti-static kit can be connected to
the metal part of the frame.

PL- 4

PRODUCT LIABILITY

WARNING

Observe the following precautions when using any optional batteries:

• The system’s emergency back-up battery may be a rechargeable lead battery. Check the
emergency battery for an electrical failure.

• Battery acid (electrolyte) is extremely harmful to human skin and eyes. If battery acid
contacts skin, wash the affected area with soap and water. If battery acid contacts the eyes,
flush the eyes with water. In either event, seek medical attention. If there is battery acid on a
cloth, use water to wash the battery acid from the cloth.

• Do not intentionally short batteries. Do not put the battery near a fire or in a fire. Do not
disassemble the battery, drop it or knock it against another object.

• The battery’s life expectancy is affected by its environment. The normal battery life is
approximately three years. If the battery is used in an outdoor setting and is exposed to high
temperatures, its life expectancy drops to approximately one year.

• Perform periodic diagnostic tests and maintenance procedures on the emergency battery and
its terminals to ensure their readiness. If there is a power failure and the emergency battery is
not ready, then the system will not work. Additionally, a damaged or dead battery, or terminals
that need replacement might cause battery acid to leak, which might cause smoke or a fire.
The battery and terminals are periodic replacement parts (the cost is chargeable to the
customer). A service contract, with the supplier or service technician, to perform routine
maintenance for the battery is recommended.

Do not touch peripheral equipment with wet hands. Do not allow any liquid to touch any of the
peripheral equipment.

Do not touch the printer’s internal components when replacing disposables such as a cartridge or a
ribbon. Ensure that the printer is turned off and that it is not hot in order to prevent burns from any
accidental contact with the internal components.

Do not drop the peripheral equipment or knock it against another object. These actions might cause
an equipment failure.

PL- 5

Thinner

ATTENTION

Do not use benzine, thinner or alcohol for cleaning. When removing dust and dirt, put diluted, mild
detergent on a cloth and then wring out the cloth. Remove the dust and dirt with the cloth and then
wipe the cleaned area with a dry cloth.

Do not place any equipment in the following environments:

• Locations that are exposed to direct sunlight

• Locations where the moisture level exceeds the allowed level

• Locations where the equipment might be exposed to water, oil, and chemicals

• Locations with very low temperatures, such as in a walk-in cooler or freezer

• Locations that are exposed to Electromagnetic Interference (EMI) from devices such as

television sets and two-way radios

• Locations that receive illegal electric waves

The life expectancies of the system and the main power source will be shortened if placed in a
location that is affected by hydrogen sulfide or salt, such as a seaside area.

PL- 6

REGULATORY NOTICE (For North America)

1. CUSTOMER INFORMATION FOR TELEPHONE TERMINAL EQUIPMENT (TTE)

This equipment complies with Part 68 of the FCC Rules and the requirements adopted by the ACTA. On the
equipment is a label that contains, among other information, a product identifier in the format:
US:AAAEQ##TXXXX. If requested, this number must be provided to the telephone company.

The telephone company may make changes in its technical operations and procedures. When such changes af­fect the compatibility or use of the UNIVERGE SV8500 system, the telephone company is required to give
adequate notice of the changes in order for you to maintain uninterrupted service.

The REN is used to determine the number of devices that may be connected to a telephone line. Excessive
RENs on a telephone line may result in the devices not ringing in response to an incoming call. In most, but
not all areas, the sum of RENs should not exceed five (5.0). To be certain of the number of devices that may
be connected to a line, as determined by the total RENs, contact the local telephone company. For products
approved after July 23, 2001, the REN for this product is the product identifier in format:
US:AAAEQ##TXXXX. The digits represented by ## are the REN without a decimal point (e.g., 03 is a REN
of 0.3).

Connection to party line service is subject to state tariffs. Contact the state public utilities commission, public
service commission or corporation commission for information.

For single and two-line equipment that connects to the telephone network via a plug and jack, the plug and jack
used with this equipment must comply with FCC Part 68 rules.

A plug and jack used to connect this equipment to the premises wiring and telephone network must comply
with the applicable FCC Part 68 rules and requirements adopted by the ACTA. A compliant telephone cord
and modular plug is provided with this product. It is designed to be connected to a compatible modular jack
that is also compliant.

1.1 TELEPHONE/SERVICE PROVIDER COMPANY NOTIFICATION

Before connecting this telephone system to the telephone network, the following information must be provided
to the telephone company:

• Your telephone number.

• FCC registration number:

For SV8500 system, use the following number:

FCC Product Identifier: US:NIFMF21BSN8153, US:NIFPF21BSN8153, US:NIFKF21BSN8153

Ringer Equivalence Number (REN): 2.1B

USOC jacks required: RJ21X, RJ2EX, RJ2GX

REGULATORY

R-1

1.2 INCIDENCE OF HARM

If this equipment causes harm to the telephone network, the telephone company will notify you in advance that
temporary discontinuance of service may be required. But if advance notice is not practical, the telephone com­pany will notify the customer as soon as possible. Also, you will be advised of your right to file a complaint
with the FCC if you believe it is necessary.

The telephone company may make changes in its facilities, equipment, operations or procedures that could af­fect the operation of the equipment. If this happens, the telephone company will provide advance notice in or­der for you to make necessary modifications to maintain interrupted service.

1.3 REPAIR SERVICE REQUIREMENTS

If the equipment is causing harm to the telephone network, the telephone company may request that you dis­connect the equipment until the problem is resolved.

If equipment malfunctions, all repairs must be performed by an authorized agent of NEC Unified Solutions,
Inc. or by NEC Unified Solutions, Inc. The user requiring service is responsible for reporting the need for ser­vice to an NEC Unified Solutions, Inc. authorized agent or to NEC Unified Solutions, Inc.

1.4 PRIVATE (LEASED) LINES

For Private (Leased) Line (Analog Data Format) equipment, type JM8 jack is required. Refer to ATIS Tech­nical Report No. 5 for details on this connector.

The Facility Interface Code (FIC) associated with each private line application represents the type of service
that will be provided by the telephone company. The user instructions must contain a detailed list of private
line ports and the associated FICs for which the equipment has been approved. In addition, the Service Order
Code (SOC) must also be included for analog systems. The SOC indicates the degree of network protection
provided by the equipment,.

For Private (Leased) Line (Digital Format) equipment, in addition to the general requirements for all equip­ment, certain digital connections require that an encoded analog content and billing protection affidavit be pro­vided the telephone company. Customer instructions must contain information on the preparation and
submission of the affidavit.

To comply with state tariffs, the telephone company must be given notification prior to connection. In some
states, the state public utility commission, public service commission or corporation commission must give pri­or approval of connection.

1.5 TOLL RESTRICTION AND LEAST COST ROUTING EQUIPMENT

The consumer/purchaser/supplier instructions accompanying this equipment and/or software features must
contain the following notice:

The software contained in the UNIVERGE SV8500 to allow user access to the network must be upgraded to
recognize newly established network area codes and exchange codes as they are placed into service.

REGULATORY

R-2

Failure to upgrade the premises systems or peripheral equipment to recognize the new codes as they are estab­lished will restrict the customer and the customer’s employees from gaining access to the network and these
codes.

1.6 DIRECT INWARD DIALING

Note: ALLOWING THIS EQUIPMENT TO BE OPERATED IN SUCH A MANNER AS TO NOT PROVIDE

FOR PROPER ANSWER SUPERVISION IS A VIOLATION OF PART 68 OF THE FCC RULES.

Direct Inward Dialing (DID) must contain the following:

Proper Answer Supervision is when this equipment returns answer supervision to the Public Switched Tele­phone Network (PSTN) when Direct Inward Dialing (DID) calls are:

• Answered by the called station.

• Answered by the Attendant.

• Routed to a recorded announcement that can be administered by the Customer Premise Equipment (CPE)
user.

• Routed to a dial prompt.

This equipment returns answer supervision on all DID calls forwarded to the Public Switched Telephone Net­work (PSTN). Permissible exceptions are:

• A call is unanswered.

• A busy tone is received.

• A reorder tone is received.

1.7 VOICE ANNOUNCEMENT/MONITORING OVER DID LINES

When using voice announcement or monitoring over DID Lines, observe the following.

CAUTION

• Using the Voice Announcement feature to eavesdrop or record sound activities at the other end of the tele­phone line may be illegal under certain circumstances and laws. Consult a legal advisor before imple­menting any practice to monitor or record a telephone conversation. Some federal and state laws require
a party monitoring or recording a telephone to use a beep-tone(s), notify all parties to the telephone con­versation and/or obtain consent of all parties to the telephone conversation. In monitoring or recording
sound activities at the other end of the telephone line using the Voice Announcement feature, the sound of
the alert tone at the beginning of the Voice Announcement may or may not

be considered sufficient under
applicable laws. Some of the applicable laws provide for strict penalties for illegal monitoring or record­ing of telephone conversations.

REGULATORY

R-3

1.8 EQUAL ACCESS REQUIREMENTS

If equipment such as Private Branch Exchanges (PBX), key systems or customer-owned coin/credit card tele­phones is sold to a call aggregator, it must be capable of providing users access to interstate providers of op­erator services through the use of access codes. Modification of this equipment by call aggregators to block
access dialing codes is a violation of the Telephone Operator Consumers Act of 1990.

1.9 ELECTRICAL SAFETY ADVISORY

Parties responsible for equipment requiring AC power should consider including an advisory notice in their
customer information suggesting the customer use a surge arrestor. Telephone companies report that electrical
surges, typically lightening transients, are very destructive to customer terminal equipment connected to AC
power sources. This has been identified as a major nationwide problem.

1.10 HEARING AID COMPATIBILITY

NEC Multiline Terminals and NEC Single Line Telephones that are provided for this system are hearing aid
compatible. The manufacturer of other Single Line Telephones for use with the system must provide notice of
hearing aid compatibility to comply with FCC rules that now prohibit the use of non-hearing aid compatible
telephones.

1.11 MUSIC ON HOLD

Note: "In accordance with U.S. Copyright Law, a license may be required from the American Society of Com-

posers, Authors and Publishers, or other similar organization, if radio or TV broadcasts are transmit­ted through the Music On Hold feature of this telecommunication system. NEC Unified Solutions, Inc.,
hereby disclaims any liability arising out of the failure to obtain such a license."

2. RADIO FREQUENCY INTERFERENCE

In compliance with FCC Part 15 rules, the following statement is provided:

Note: “This equipment has been tested and found to comply with the limits for a Class A digital device, pur-

suant to Part 15 of the FCC Rules. These limits are designed to provide reasonable protection against
harmful interference when the equipment is operated in a commercial environment. This equipment
generates, uses, and can radiate radio frequency energy and, if not installed and used in accordance
with the instruction manual, may cause harmful interference to radio communications. Operation of
this equipment in a residential area is likely to cause harmful interference in which case the user will
be required to correct the interference at his own expense.

Note: Modifying this equipment without an approval from NEC Unified Solutions, Inc. may void your author-

ity granted by the FCC to operate the equipment.”

3. SAFETY INFORMATION

This equipment has been certified by Canadian Standards Association and found to comply with all applicable
requirements:

• CAN/CSA C22.2 No. 0-M – General Requirements – Canadian Electrical Code, Part II

REGULATORY

R-4

• CAN/CSA C22.2 No. 60950-1-03 – Safety of Information Technology Equipment – Part l: General Re­quirements

• UL 60950-1-SAFETY, 1st Edition – Safety of Information Technology Equipment – Part I: General Re­quirements

4. INDUSTRY CANADA REQUIREMENTS

Industry Canada has established rules that permit this telephone system to be directly connected to the tele­phone network. Prior to the connection or disconnection of this telephone system to or from the telephone net­work, the telephone company must be provided with the following information.

This product meets the applicable Industry Canada Technical Specifications/Le present material est conforme
aux specifications techniques applicables d’industrie Canada.

(1) Your telephone number.

(2) IC registration number: IC: 140L-SN8153

(3) Ringer Equivalence Number (REN) of the equipment: 2.1

Before installing this equipment, users should ensure that it is permissible to be connected to the facilities of
the local telecommunications company. The equipment must also be installed using an acceptable method of
connection. The customer should be aware that compliance with the above conditions may not prevent degra­dation of service in some situations.

Repairs to certified equipment should be coordinated by a representative designated by the supplier. Any re­pairs or alterations made by the user to this equipment, or equipment malfunctions, may give the telecommu­nications company cause to request the user to disconnect the equipment.

Users should ensure for their own protection that the electrical ground connections of the power utility, tele­phone lines and internal metallic water pipe system, when present, are connected together. This precaution
may be particularly important in rural areas.

CAUTION

• Users should not attempt to make such connections themselves, but should contact the applicable electri­cal inspection authority or electrician.

• The Ringer Equivalence Number (REN) is an indication of the maximum number of devices allowed to be
connected to the telephone interface. The termination on an interface may consist of any combination of
devices subject only to the requirement that the sum of RENs of all the devices does not exceed five/L’in­dice d’equivalence de la sonnerie (IES) sert a indiquer le nombre maximal de terminaus qui peuvent etre
raccordes a une interface telephonique. La terminaison d’une interface peut consister en une combinai­son quelconque de dispositifs, a la seule condition que la somme d’indices d’equivalence de la sonnerie
de tous les dispositifs n’excede pas 5.

• This equipment has been certified by the Canadian Standards Association and found to comply with all
applicable requirements of the standard for telephone equipment C 22.2 No. 225.

REGULATORY

R-5

• This equipment meets IC requirements CS03, PART II, PART III, PART VI.

• This digital apparatus does not exceed the Class A limits for radio noise emissions from digital apparatus
as set out in the radio interference regulations of Industry Canada/Le present appareil numerique n’emet
pas de bruits radioelectriques depassant les limites applicables aux appareils numeriques de Classe A
prescrites dans le reglement sur le brouillage radioelectrique edicte par Industrie Canada.

5. BATTERY DISPOSAL

The UNIVERGE SV8500 system includes the batteries listed below. When disposing of these batteries, Chas­sis, and/or Blades, you must comply with applicable federal and state regulations regarding proper disposal
procedures.

Battery Types and Quantities for Chassis and Blades

Unit Name Type of Battery Quantity

MH250 (WLPS3(E)-A) Lithium-ion 1

PSIII (PS3D) Lithium-ion 1

CT-12 Headset Cordless Nickel Metal-Hydride 1

DTH-4R-2 Nickel Metal-Hydride 1

DTL-8R-1 Nickel Metal-Hydride 1

DTR-1HM-1 TEL Lithium 1

DTR-1R-2 Nickel-Cadmium 1

DTR-4R-2 TEL Nickel-Cadmium 1

DTU-4R-1 TEL Lead Acid 1

Headset Cordless II Nickel Metal-Hydride 1

®

Bluetooth

Cordless Handset Lithium-ion 1

IMPORTANT SAFEGUARDS FOR BATTERY DISPOSAL

• DO NOT PLACE USED BATTERIES IN YOUR REGULAR TRASH! THE PRODUCT YOU PUR­CHASED CONTAINS LITHIUM, NICKEL-CADMIUM OR SEALED LEAD BATTERIES. LITHIUM,
NICKEL-CADMIUM OR SEALED LEAD BATTERIES MUST BE COLLECTED, RECYCLED, OR DIS­POSED OF IN AN ENVIRONMENTALLY SOUND MANNER.

• The incineration, landfilling or mixing of nickel-cadmium or sealed lead batteries with the municipal sol­id waste stream is PROHIBITED BY LAW in most areas. Contact your local solid waste management of­ficials for other information regarding the environmentally sound collection, recycling, and disposal of
the battery.

REGULATORY

R-6

• Nickel-Cadmium (or sealed lead) batteries must be returned to a federal or state approved nickel-cadmi­um (or sealed lead) battery recycler. This may be where the batteries were originally sold or a local seller
of automotive batteries. Contact your local waste management officials for other information regarding
the environmentally sound collection, recycling and disposal of the battery contained in this product. For
Ni-Cd batteries, you can also call 1-800-8-BATTERY

SM

when further information is required.

• The packaging for the UNIVERGE SV8500 system contains the following labels regarding proper dispos­al.

PRODUCT PACKAGE LABELING

CONTAINS NICKEL-CADMIUM BATTERY.
BATTERY MUST BE RECYCLED OR
DISPOSED OF PROPERLY. MUST NOT BE
DISPOSED OF IN MUNICIPAL WASTE.

Ni-Cd

CONTAINS SEALED LEAD BATTERY.
BATTERY MUST BE RECYCLED. MUST NOT
BE DISPOSED OF IN MUNICIPAL WASTE.

Pb

Ni-MH

CONTAINS NICKEL-METAL HYDRIDE
BATTERY. BATTERY MUST BE RECYCLED
OR DISPOSED OF PROPERLY. MUST NOT
BE DISPOSED OF IN MUNICIPAL WASTE.

REGULATORY

R-7

REGULATORY NOTICE (For EU)

1. PREFACE

This manual is valid for the UNIVERGE SV8500 telephone system.

Some products described in this manual are not (yet) available for specific countries or markets. For this rea­son, the related specifications, instructions for installation and use of these specific products are not valid for
these markets. Refer to NEC Philips for more details in case of any questions about these products.

1.1 CE Notice (European Union)

The equipment described in this manual is intended to be connected to local area networks (LAN) and supports
a wide range of peripheral equipment. Additional interfaces are available for connection to public analogue
and digital telecommunication networks which comply with:

• ETS 300 011 (PRI)

• ETS 300 012 (BRI)

• ETS 300 402 (PRI & BRI)

• ETS 300 403 (PRI & BRI)

• TBR3 :ISDN basic rate interface

• TBR4 :ISDN primary rate interface

• TBR21 :Analogue interface

To take advantage of all features of this system and the connected equipment, the country specific or network
specific features should match the supported features of the system. For an overview of the supported features,
refer to the detailed documentation that comes with this system, contact your local NEC Philips representative
or the support desk of NEC Philips Unified Solutions.

Hereby, “NEC Philips Unified Solutions”, declares that this product is in compliance with the essential require­ments and other relevant provisions of Directive 1999/5/EC.

1.2 Electromagnetic compatibility

For some of the SV8500 communication platform components the following warning is applicable:

WARNIG : This is a class A product.

In a domestic environment this product may cause radio interference in which
case the user may be required to take adequate measures.

REGULATORY

R-8

Notice that this warning is only applicable to components of the SV8500 communication platform of which
the product type plate indicates “Complies with EN55022 Class A”.

2. PRODUCT DISPOSAL INFORMATION

2.1 For countries in the European Union

The symbol depicted here has been affixed to your product in order to inform you that electrical and elec­tronic products should not be disposed of as municipal waste.

Electrical and electronic products including the cables, plugs and accessories should be disposed of separately
in order to allow proper treatment, recovery and recycling. These products should be taken to a designated fa­cility where the best available treatment, recovery and recycling techniques are available. Separate disposal
has significant advantages: valuable materials can be re-used and it prevents the dispersion of unwanted sub­stances into the municipal waste stream. This contributes to the protection of human health and the environ­ment.

Please be informed that a fine may be imposed for illegal disposal of electrical and electronic products via the
general municipal waste stream.

To facilitate separate disposal and environmentally sound recycling arrangements have been made for local
collection and recycling. If you need to dispose of your electrical and electronic products, please refer to your
supplier or the contractual agreements that your company made when these products were acquired.

At www.nec-philips.com/weee you can find information about separate disposal and environmentally sound
recycling.

2.2 For countries outside the European Union

Disposal of electrical and electronic products in countries outside the European Union should be done in line
with the local regulations. If no arrangement has been made with your supplier, please contact the local author­ities for further information.

3. Declaration of Conformity

• ýesky

“NEC Philips Unified Solutions” tímto prohlašuje, že tento “SV8500” je ve shodČ se základními
požadavky a dalšími pĜíslušnými ustanoveními smČrnice 1999/5/ES.

 http://www.nec-philips.com/doc

•Dansk

Undertegnede “NEC Philips Unified Solutions” erklærer herved, at følgende udstyr “SV8500” overhold­er de væsentlige krav og øvrige relevante krav i direktiv 1999/5/EF.

 http://www.nec-philips.com/doc

•Deutsch

REGULATORY

R-9

Hiermit erklärt “NEC Philips Unified Solutions”, dass sich das Gerät “SV8500” in Übereinstimmung mit
den grundlegenden Anforderungen und den übrigen einschlägigen Bestimmungen der Richtlinie 1999/5/
EG befindet.

 http://www.nec-philips.com/doc

• Eesti

Käesolevaga kinnitab “NEC Philips Unified Solutions” seadme “SV8500” vastavust direktiivi 1999/5/EÜ
põhinõuetele ja nimetatud direktiivist tulenevatele teistele asjakohastele sätetele.

 http://www.nec-philips.com/doc

• English

Hereby, “NEC Philips Unified Solutions”, declares that this “SV8500” is in compliance with the essential
requirements and other relevant provisions of Directive 1999/5/EC.

 http://www.nec-philips.com/doc

• Español
Por medio de la presente “NEC Philips Unified Solutions” declara que el “SV8500” cumple con los req-

uisitos esenciales y cualesquiera otras disposiciones aplicables o exigibles de la Directiva 1999/5/CE.

 http://www.nec-philips.com/doc

• ǼȜȜȘȞȚțȒ

ȂǼ ȉǾȃ ȆǹȇȅȊȈǹ Ǿ NEC Philips ǼȃȅȆȅǿǾȂǼȃǼS ȁȊ SǼǿS ǻǾȁȍȃǼǿ ȅȉǿ “SV8500”
ȈȊȂȂȅȇĭȍȃǼȉǹǿ ȆȇȅȈ ȉǿȈ ȅȊȈǿȍǻǼǿȈ ǹȆǹǿȉǾȈǼǿȈ Ȁǹǿ ȉǿȈ ȁȅǿȆǼȈ ȈȋǼȉǿȀǼȈ
ǻǿǹȉǹȄǼǿȈ ȉǾȈ ȅǻǾīǿǹȈ 1999/5/ǼȀ.

 http://www.nec-philips.com/doc

• Français
Par la présente “NEC Philips Unified Solutions” déclare que l'appareil “SV8500” est conforme aux exi-

gences essentielles et aux autres dispositions pertinentes de la directive 1999/5/CE.

 http://www.nec-philips.com/doc

• Íslenska
Hér með lýsir “NEC Philips Unified Solutions” yfir því að “SV8500” er í samræmi við grunnkröfur og

aðrar kröfur, sem gerðar eru í tilskipun 1999/5/EC.

 http://www.nec-philips.com/doc

• Italiano
Con la presente “NEC Philips Unified Solutions” dichiara che questo “SV8500” è conforme ai requisiti

essenziali ed alle altre disposizioni pertinenti stabilite dalla direttiva 1999/5/CE.

 http://www.nec-philips.com/doc

• Latviski

REGULATORY

R-10

Ar šo “NEC Philips Unified Solutions” deklarƝ, ka “SV8500” atbilst DirektƯvas 1999/5/EK bnjtiskajƗm
prasƯbƗm un citiem ar to saistƯtajiem noteikumiem.

 http://www.nec-philips.com/doc

• Lietuviǐ
Šiuo “NEC Philips Unified Solutions” deklaruoja, kad šis “SV8500” atitinka esminius reikalavimus ir ki-

tas 1999/5/EB Direktyvos nuostatas.

 http://www.nec-philips.com/doc

• Malti
Hawnhekk, “NEC Philips Unified Solutions”, jiddikjara li dan “SV8500” jikkonforma mal-ƫtiƥijiet es-

senzjali u ma provvedimenti oƫrajn relevanti li hemm fid-Dirrettiva 1999/5/EC.

 http://www.nec-philips.com/doc

• Magyar
Alulírott, “NEC Philips Unified Solutions” nyilatkozom, hogy a “SV8500” megfelel a vonatkozó

alapvetõ követelményeknek és az 1999/5/EC irányelv egyéb elõírásainak.

 http://www.nec-philips.com/doc

• Nederlands
Hierbij verklaart “NEC Philips Unified Solutions” dat het toestel “SV8500” in overeenstemming is met

de essentiële eisen en de andere relevante bepalingen van richtlijn 1999/5/EG.

 http://www.nec-philips.com/doc

• Norsk
“NEC Philips Unified Solutions” erklærer herved at utstyret “SV8500” er i samsvar med de grunn-

leggende krav og øvrige relevante krav i direktiv 1999/5/EF.

 http://www.nec-philips.com/doc

•Polski

Niniejszym, "NEC Philips Unified Solutions" deklaruje, ze “SV8500” jest zgodny z wymaganiami i in­nymi warunkami Dyrektywy 1999/5/EC.

 http://www.nec-philips.com/doc

• Português
“NEC Philips Unified Solutions” declara que este “SV8500” está conforme com os requisitos essenciais

e outras disposições da Directiva 1999/5/CE.

 http://www.nec-philips.com/doc

• Slovensko

REGULATORY

R-11

“NEC Philips Unified Solutions” izjavlja, da je ta “SV8500” v skladu z bistvenimi zahtevami in ostalimi
relevantnimi doloþili direktive 1999/5/ES.

 http://www.nec-philips.com/doc

• Slovensky
“NEC Philips Unified Solutions” týmto vyhlasuje, že “SV8500” spĎĖa základné požiadavky a všetky prís-

lušné ustanovenia Smernice 1999/5/ES.

 http://www.nec-philips.com/doc

• Suomi
“NEC Philips Unified Solutions” vakuuttaa täten että “SV8500” tyyppinen laite on direktiivin 1999/5/EY

oleellisten vaatimusten ja sitä koskevien direktiivin muiden ehtojen mukainen.

 http://www.nec-philips.com/doc

• Svenska
Härmed intygar “NEC Philips Unified Solutions” att denna “SV8500” står I överensstämmelse med de

väsentliga egenskapskrav och övriga relevanta bestämmelser som framgår av direktiv 1999/5/EG.

 http://www.nec-philips.com/doc

NEC PHILIPS Unified Solutions

Anton Philipsweg 1
1223 KZ Hilversum

The Netherlands

REGULATORY

R-12

TERMS IN THIS MANUAL

System Name

In this manual, the following are used unless the types of the Telephony Server and the PBX need to be identified.

TERMS USED IN THIS MANUAL

SYSTEM NAMES

SV8500, the system UNIVERGE SV8500
SV7000, the system UNIVERGE SV7000

Note 1

MPS, SV7000 MPS, the system UNIVERGE SV7000 MPS
IPX, 2400 IPX, NEAX 2400 IPX, the system NEAX2400 IPX Internet Protocol eXchange

Note 2

IPS, 2000 IPS, NEAX 2000 IPS NEAX2000 IPS INTERNET PROTOCOL SERVER Note 3
NEAX IMX, IMX NEAX2400 IMX

NEAX7400 IMX
NEAX7400 ICS (IMX)

NEAX IVS

, IVS

2

NEAX2000 IVS

2

2

NEAX2000 INTEGRATED VOICE SERVER
NEAX7400 ICS M100MX

NEAX IVS, IVS NEAX7400 ICS Model110

NEAX7400 ICS Model120
NEAX7400 ICS Model80VS
NEAX7400 ICS Model100

Note 1: UNIVERGE SV7000 Remote Node over IP is also included in the SV7000 series, which is migrated from

the existing IPX system. It is mentioned as “Remote Node over IP” or “the system” in this manual.

Note 2: In regard to China market, NEAX2400 IPX Internet Protocol eXchange has not been released but

NEAX2400 is released.

Note 3: In regard to China market, NEAX2000 IPS INTERNET PROTOCOL SERVER has not been released but

NEAX2000 is released.

TERMS-1

Terminal Name

In this manual, the following terminals are mentioned as each common term unless these types need to be identified.

Desktop
Terminal

GENERIC TERMS USED IN THIS MANUAL

Digital terminal

IP terminal

Soft Phone (Propri-

IP
Station

Soft Phone

etary Protocol)

Soft Phone (SIP)

TERMINAL NAMES

Dterm Series E/Dterm 75

Dterm

Dterm Series i
DT310

DT300 Series

DT330
Dterm Series E/Dterm 75

IP Enabled
Dterm

with IP adapter
Dterm Series i with IP

adapter

DtermIP INASET Note 4

DtermIP

DtermIP
(Proprietary Protocol)

DtermSP20

DtermSP30

DtermSP30

(Proprietary Protocol)
DtermSP30 (SIP)

Soft Client SP350

Note 4

Note 4

DtermIP DtermIP (SIP)
SIP
terminal

SIP Multiple Line terminal

DT700 Series

DT710
DT730

DT750
WLAN Handset (MH Series) MH250
Standard SIP terminal Third-party SIP terminal

PHS

PS

PCS

Note 4: This terminal provides users with all features currently available on DtermIP (Proprietary Protocol).

TERMS-2

Media Gateway (MG), Media Converter (MC), and Voice Conference Server (VS) Names

In this manual, the following are mentioned as each common term unless these types need to be identified.

GENERIC TERMS USED IN THIS MANUAL

EQUIPMENT NAMES

MG(PRI) Card [SCA-24PRIA]
MG(PRI) Box [MG-24PRIA]

MG(PRI)

MG(PRI) Card [SCA-30PRIA]
MG(PRI) Box [MG-30PRIA]
MG-PRI/MG-PRA

MG-T1(SIP) MG-T1(SIP) Card [SCA-24DTIA]

MG(BRI) Card [SCA-2BRIA]

MG(BRI)

MG(BRI) Box [MG-2BRIA]
MG-BRI
MG-SIP16

MG(SIP)

MG-SIP16 Card [SCA-16SIPMGA]
MG-SIP16 Box [MG-16SIPMGA]
MCMG Card [SCA-4LC2COTA]
MCMG Box [MG-4LC2COTA]

MC&MG-COT

MCMG Card [SCA-7COTA]

MG-COT

Analog MC

VS32

MC&MG-COT with PFT
MG-COT Card [SCA-6COTA]
MG-COT Card [SCA-6COTB]
MG-COT Card [SCA-6COTC]
Analog 2MC
8LC Card [SCA-8LCA]
8LC Card [SCA-8LCA-EMEA]
VS-32
VS-32(Dual) Card [SCA-VS32VA]
VS-32(Dual) Box [MG-VS32VA]

TERMS-3

General Terms

• PIR on this manual is a term equivalent to GC (Gateway Chassis) in the North America.

• Automatic Number Identification (ANI) on this manual is a term equivalent to Calling Line Identification
(CLI) in Australia.

TERMS-4

NWA-041693-001

ISSUE 2.0

JANUARY, 2009

UNIVERGE SV8500

Operations and Maintenance Manual

TABLE OF CONTENTS

Page

INTRODUCTION . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . INT-1

1. General Knowledge of SV8500 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . INT-1

1.1 About Release Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . INT-1

1.2 Structure of Telephony Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . INT-2

1.2.1 General . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . INT-2

1.2.2 TP and SP for System Changeover . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . INT-2

1.3 Registration Destination of IP Devices/Stations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . INT-3

1.4 Lan Interface Accommodation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . INT-5

1.4.1 LAN1 Accommodation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . INT-5

1.4.2 LAN2 Accommodation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . INT-7

1.5 Trunking Diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . INT-9

CHAPTER 1 GENERAL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1

1. ABOUT THIS MANUAL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1

2. SYSTEM ACCOMMODATION . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1

2.1 SV8500 Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1

2.2 PIR and TSWR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3

3. GLOSSARY . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4

4. HOW TO READ PRECAUTIONS, DIAGNOSTIC, AND FAULT REPAIR INFORMATION . . . . . . . . . 7

4.1 Precaution about Diagnostic Procedure/Fault Repair Procedure . . . . . . . . . . . . . . . . . . . . . . . . 7

4.2 How to Follow Diagnostic Procedure/Fault Repair Procedure . . . . . . . . . . . . . . . . . . . . . . . . . . 11

5. REPORTING FAULT TO NEC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15

5.1 Fault Reporting Method . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15

5.2 Forwarding Faulty Circuit Card Method . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17

6. SYSTEM MAINTENANCE OUTLINE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18

7. BASIC KNOWLEDGE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19

7.1 System Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20

7.2 Line Equipment Numbers (LENS) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24

7.2.1 Module Group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24

7.2.2 Unit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24

7.2.3 Group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26

7.2.4 Level . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27

7.3 Local Partition (LP) Number . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28

7.4 Fault Detecting Function . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29

7.5 Range of Faults Specification . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33

CHAPTER 2 OPERATIONS OF SV8500 SERVER . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41

1. HOW TO SET THE CURRENT DATE AND TIME . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42

1.1 General . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42

1.2 Programming to Specify How to Set Date and Time . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42

– i –

TABLE OF CONTENTS (CONTINUED)

Page

1.3 How to Adjust Date and Time . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43

2. ALARM INDICATIONS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44

2.1 Kinds of Alarm Indications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44

2.2 How to Stop Alarm Indications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44

2.3 Alarm Indications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45

2.4 Variable Alarm Indication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46

3. INITIALIZATION PROCEDURE OF THE SYSTEM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47

3.1 General . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47

3.2 Initialization by PCPro (SINZ) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48

3.3 Initialization by PCPro Tools . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50

3.4 Initialization by INIT key Operation (EMA card) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51

3.5 Initialization by Turning OFF and ON the System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52

3.5.1 How to Start Up the System by Turning OFF/ON . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52

4. ROUTINE DIAGNOSIS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53

4.1 Related System Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53

4.2 Routine Diagnosis Result . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55

5. OFFICE DATA MAINTENANCE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56

5.1 Office Data Maintenance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56

5.2 Office Data Maintenance Procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56

5.3 Office Data Backup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57

5.3.1 MEM_HDD / MEM_HDD_N . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57

5.3.2 PCPro Tools . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58

5.3.3 Explanations on Each Item . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61

5.4 INITIALIZATION PROCEDURE OF CF CARD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62

5.4.1 Procedure For FP85-104 S1E . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62

5.4.2 Procedure For FP85-104 S1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66

6. UNIT/CIRCUIT CARD REPLACEMENT PROCEDURE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70

6.1 CPU Card Replacement Procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70

6.2 EMA Card Replacement Procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76

6.3 EMA SUB Card Replacement Procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77

6.4 EXB (EXB-PIR/EXB-TSW) Card Replacement Procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78

6.5 IOC Card Replacement Procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84

7. FAN REPLACEMENT PROCEDURE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87

7.1 Replacement Procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87

7.2 Test Procedure After the Replacement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89

8. SYSTEM CONTROL PROCEDURES . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 90

8.1 Changeover of CPU/TSW/PLO . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 90

8.1.1 General . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 90

8.1.2 How to Check LED . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .93

8.1.3 How to Change over CPU Card . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97

8.1.4 How to Control Switching Block . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 100

8.1.5 Manual Changeover of Speech Path System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101

8.1.6 Manual Changeover of PLO . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 108

9. TRAFFIC MANAGEMENT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 112

9.1 Kind of Traffic Measurement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 112

9.1.1 Description of Traffic Measurement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 112

– ii –

TABLE OF CONTENTS (CONTINUED)

Page

9.2 Operating Procedure for PCPro . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 134

10. STATION MESSAGE DETAIL RECORDING SYSTEM (SMDR) . . . . . . . . . . . . . . . . . . . . . . . . . . . . 144

10.1 Transmission Data to SMDR Equipment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 144

10.2 Details on Transmission Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 148

10.2.1 Calling Party Information/Called Party Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 148

10.2.2 Call Start/Call End Time Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 149

10.2.3 Called Number . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 151

10.2.4 Account Code/Authorization Code . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 151

10.2.5 Route Advance Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 152

10.2.6 Condition B Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 153

10.2.7 Call Metering Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 153

10.2.8 Office Code of Calling (Called) Party and Billing Process Office . . . . . . . . . . . . . . . . . . . 154

10.2.9 Text Format of Centralized Billing - FCCS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 154

11. REDUNDANT DATA MEMORY BACKUP FOR OFFICE DATA . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 163

11.1 Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 163

11.2 Redundant Data Memory Backup Procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 163

11.2.1 Service condition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 163

11.2.2 Programming . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 164

12. RTP INFORMATION OUTPUT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 165

12.1 How to Display Log . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 166

12.1.1 Use of Collected Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 167

12.1.2 Examples of Using Logs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 183

13. DTERM IP CALL INFORMATION DISPLAY . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 186

13.1 Operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 186

13.2 Examples of Using Logs for Solution . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 186

14. IP DEVICE PC PORT REMOTE CONTROL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 187

14.1 Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 187

14.2 Operating Procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 187

14.3 Service Conditions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 187

15. LICENSE REGISTRATION INFORMATION DISPLAY . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 189

15.1 Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 189

15.2 Operating Procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 189

15.3 Service Conditions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 189

15.4 Data Assignment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 189

16. FTP SERVER SUPPORT (LAN1) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 190

16.1 Operating Procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 190

16.2 Service Conditions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 191

16.3 Programming . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 193

CHAPTER 3 SYSTEM MESSAGES . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 195

1. Observation Method of System Message . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 195

2. Collection of System Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 196

3. System Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 199

0-C Reset Interrupt . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 205

0-D CPU Clock Down . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 207

0-E C-Level Infinite Loop . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 208

0-F Memory Failure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 210

– iii –

TABLE OF CONTENTS (CONTINUED)

Page

0-G B1-Level Infinite Loop (Permanent) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 212

0-H B1-Level Infinite Loop (Temporary) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 213

0-I Mate CPU Failure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 214

0-J Abnormal Interrupt . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 215

1-A Both TSW Failure (Permanent) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 217

1-B TSW Failure (Permanent) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 218

1-C Both TSW Write Failure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 219

1-D TSW Write Failure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 220

1-E Both TSW Clock Failure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 221

1-F TSW Clock Failure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 222

1-O Both PLO Failure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 223

1-P PLO Failure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 225

1-S Module Group Down Failure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 227

1-T TSW ACT Change Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 228

1-U DLKC Data Transfer Failure (Permanent) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 231

1-V DLKC Data Transfer Failure (Temporary) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 232

1-W PLO Restore . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 233

3-B C-Level Infinite Loop (Permanent) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 234

3-C C-Level Infinite Loop (Temporary) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 235

3-D Lock-Up Failure (Permanent) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 236

3-E Lock-Up Failure (Temporary) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 237

3-F -48V Over Current . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 238

3-G Ground Failure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 239

3-H Digital Line Warning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 240

3-I Digital Line Failure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 241

3-J Digital Line Restore . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 243

3-K Line Fault . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 244

3-L Line Fault Release . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 245

4-C Both TSW Ready Failure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 246

4-D TSW Ready Failure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 247

4-Q DLKC Ready Failure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 248

4-S MUX Ready Failure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 249

4-T Both MUX Ready Failure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 250

4-U PCI Card Failure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 251

4-V PCI Card Failure Recovered . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 254

4-W TSW Ready Failure Restore . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 255

6-A System Failure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 257

6-B RGU & Howler Failure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 259

6-C Line Load Control Start . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 260

6-D Line Load Control Stop . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 261

6-H Bad Call Notification . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 262

6-I STA-Test Connection Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 267

6-J Emergency Call . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 271

6-L Emergency Control Start . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 272

6-M Emergency Control Stop . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 273

6-N Abnormal Call Duration Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 274

6-O SMDR Output Buffer Overflow Alarm . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 277

6-P SMDR Output Buffer Overflow Release . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 280

7-A System Initialize With Data Load . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 281

– iv –

TABLE OF CONTENTS (CONTINUED)

Page

7-B System Initialize . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 283

7-C CPU MBR Key Turn ON . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 284

7-D CPU MBR Key Turn OFF . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 285

7-E TSW MBR Key Turn ON . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 286

7-F TSW MBR Key Turn OFF . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 287

7-G TSW PLO Key Turn ON . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 288

7-H TSW PLO Key Turn OFF . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 289

7-K PM MB Key Turn ON . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 290

7-L PM MB Key Turn OFF . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 291

7-M NCU MB Key Turn ON . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 292

7-N NCU MB Key Turn OFF . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 293

7-O Cyclic Diagnosis Normal . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 294

7-P Cyclic Diagnosis Information (Error Detected) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 306

7-Q PFT Key ON . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 345

7-R PFT Key OFF . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 346

7-U PLO MB Key Turn ON . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 347

7-V PLO MB Key Turn OFF . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 348

10-A Activation Code Request Notice (SUP) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 349

10-B Activation Code Request Notice (MN) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 350

10-C Activation Code Request Notice (MJ) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 351

10-D IP License Excess Notice (SUP) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 352

10-E CPU Operation Mode Error Notification . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 353

10-F Connection Failure between Telephony Server and SR-MGC . . . . . . . . . . . . . . . . . 354

10-G Connection Recovery between Telephony Server and SR-MGC . . . . . . . . . . . . . . . 358

10-H Illegal Software Version Information Set . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 361

10-I Software Version Information Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 363

10-J Software Version Information Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 365

10-K Software Version Information Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 367

10-L SR-MGC State Notification . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 369

13-A CCH Clock Failure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 371

13-B CCH C-Level Infinite Loop Failure (Permanent) . . . . . . . . . . . . . . . . . . . . . . . . . . . . 372

13-C CCH C-Level Infinite Loop Failure (Temporary) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 373

13-D CCH Lock-Up Failure (Permanent) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 374

13-E CCH Lock-Up Failure (Temporary) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 375

13-F CCH B-Level Infinite Loop Failure (Permanent) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 376

13-G CCH B-Level Infinite Loop Failure (Temporary) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 377

13-H CCS Link Failure (Permanent) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 378

13-I CCS Link Failure (Temporary) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 380

13-J Restoration From CCS Link Failure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 382

13-K CCH Reset Interrupt Failure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 383

13-N Digital Line Warning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 384

13-O Digital Line Failure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 385

13-P Digital Line Restore . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 386

13-Q DRU Battery Operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 387

13-R DRU Line Operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 388

13-Z Power Failure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 389

15-A VPS Failure (Temporary) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 390

15-B VPS Failure (Permanent) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 391

15-C VPS Restore . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 392

– v –

TABLE OF CONTENTS (CONTINUED)

Page

16-A Inside Trunk All Busy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 393

16-B Virtual Tie Line Set Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 395

16-C Virtual Tie Line Cancel Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 396

16-E Virtual Tie Line Set Time Out . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 397

16-F Sender Start Time Out . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 400

16-M Hard Clock Failure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 406

16-N Hard Clock Restore . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 407

17-A CCH MBR Key Turn ON . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 408

17-B CCH MBR Key Turn OFF . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 409

17-C CCH MB Key Turn ON . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 410

17-D CCH MB Key Turn OFF . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 411

17-H Day/Night Change Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 412

17-O IOC MB Key Turn ON . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 414

17-P IOC MB Key Turn OFF . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 415

17-Q IOC MBR Key Turn ON . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 416

17-R IOC MBR Key Turn OFF . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 417

23-P DCH Back-Up Automatic Change Start/End . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 418

23-Q DCH Back-Up Manual Change Start/End . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 420

23-Y MUX Clock Failure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 422

23-Z Both MUX Clock Failure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 423

26-N MAT Log . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 424

26-R Call Trace . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 425

26-V LAN Interface Error Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 429

26-W LAN Interface Release Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 435

33-A MUX Clock Restore . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 437

33-B SDT Alarm Warning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 438

33-C SDT Alarm Trouble . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 440

33-D SDT Alarm Restore . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 443

33-E SDT Interface Change Notify . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 444

33-F PKG Download Failure Notification . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 445

33-G MUX PKG PCM Parity Error Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 447

33-H MUX PKG PCM Parity Error Recovery Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 448

33-R IP PKG Warning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 449

33-S IP PKG Failure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 469

33-T IP PKG Restore . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 471

33-U H.323 Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 473

35-A GK Operation Start Notification . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 475

35-B GK Operation Stop Notification . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 477

35-C SP Warning Notification . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 478

35-D SP Failure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 479

35-E SP Failure Recovery . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 480

35-F SP Process Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 481

35-G SP Process Warning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 486

35-I SP Process Stop . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 490

36-A Office Data Copy Status Notification . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 493

36-E Registration Security Alert . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 499

36-F Fusion Health Check Report (Temporary/Permanent) . . . . . . . . . . . . . . . . . . . . . . . . 501

36-G Bandwidth Warning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 504

36-H Bandwidth Warning Recovery . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 506

– vi –

TABLE OF CONTENTS (CONTINUED)

Page

36-I Bandwidth Fault . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 507

36-J Bandwidth Fault Recovery . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 509

36-K Fusion Health Check Report (Recovery) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 510

36-M IP Terminal Auto Assignment Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 512

36-N IP Equipment Status Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 515

36-O System Message Overflow Notification . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 523

36-T Fusion Health Check Report (Permanent) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 524

CHAPTER 4 FAULT REPAIR PROCEDURES . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 527

1. IP RELATED FAULT AND ITS REASON . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 528

1.1 TCP/IP Link Fault . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 529

1.1.1 Method of Checking and Repairing Each of “4-R”KIND=03ERRK . . . . . . . . . . . . . . . . . . 529

1.1.2 Method of Checking and Repairing Each of “26-V”ERRK . . . . . . . . . . . . . . . . . . . . . . . . 530

1.2 LAN/WAN Communication Fault . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 531

1.3 IP Related System Messages and the Reasons . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 536

1.3.1 IP Related System Message and Its Reason (33-R) . . . . . . . . . . . . . . . . . . . . . . . . . . . . 537

1.3.2 IP Related System Message and Its Reason (33-S) . . . . . . . . . . . . . . . . . . . . . . . . . . . . 539

1.4 System Down Fault . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 541

1.4.1 When Cannot Define the Reason of Failure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 541

1.4.2 When Circuit Card With Failure Is Indicated on System Message . . . . . . . . . . . . . . . . . . 541

1.4.3 Fault Repair/Localization Flow . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 542

1.4.4 Details of Fault Repair/Localizing Flow . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 546

1.5 Clock Failure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 549

CHAPTER 5 OPERATION PROCEDURE FOR SYSTEM WITH PIR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 551

1. PIR ACCOMMODATING UNIT/CIRCUIT CARD REPLACEMENT PROCEDURE . . . . . . . . . . . . . . . 551

1.1 PIR Face Layout . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 552

1.2 Replacement Procedure of Line/Trunk Circuit Cards . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 553

1.3 Replacement Procedure of SDT Card and Optical Fiber Cable . . . . . . . . . . . . . . . . . . . . . . . . . 554

1.3.1 How to Replace SDT (PS-SDTA/PA-SDTB) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 554

1.3.2 How to Replace Optical Fiber Cable . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 555

1.4 Replacement Procedure of IPPAD Circuit Card . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 556

1.5 Replacement Procedure of MUX (Multiplexer) Circuit Card . . . . . . . . . . . . . . . . . . . . . . . . . . . . 558

1.5.1 MUX Replacement: 1-IMG . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 558

1.5.2 MUX Replacement: 4-IMG . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 560

1.6 Replacement Procedure of PWR (Power) Circuit Card . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 562

1.7 Replacement Procedure of TSW (Time Division Switch) Circuit Card . . . . . . . . . . . . . . . . . . . . 563

1.7.1 TSW Replacement: 1-IMG . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 563

2. TSWR ACCOMMODATING CIRCUIT CARD REPLACEMENT PROCEDURE (4-IMG ONLY) . . . . . 565

2.1 Precaution . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 565

2.2 Circuit Card Mounting Face Layout . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 565

2.3 GT Card Replacement Procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 566

2.3.1 TSW Card Replacement Procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 568

2.3.2 DLKC Card Replacement Procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 571

2.3.3 PLO Card Replacement Procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 573

2.3.4 PWR SW Card Replacement Procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 575

– vii –

TABLE OF CONTENTS (CONTINUED)

Page

2.4 Replacement Procedure of CF Card . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 576

2.5 Replacement Procedure of FANC (PZ-M699) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 577

2.6 Replacement Procedure of FANs (PIR/TSWR) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 581

2.7 Replacement Procedure of 1U–C/DC Power Unit on 9U–IR (DC Power Input Version) . . . . . . . 586

2.7.1 Procedure for Upgrading to Dual Power Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . 587

2.7.2 Procedure for Replacing #0 Side of AC/DC Power Unit . . . . . . . . . . . . . . . . . . . . . . . . . . 589

2.8 Replacement Procedure of Fuse . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 590

3. FAULT REPAIR PROCEDURE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 595

3.1 LINE FAULT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 597

3.1.1 Check Point . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 597

3.1.2 Line Control . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 598

3.1.3 Line Fault - When DT Cannot Be Heard . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 599

3.1.4 Line Fault - When Dialing Results in Wrong Connection . . . . . . . . . . . . . . . . . . . . . . . . . 600

3.1.5 Line Fault - When Bell Does Not Ring . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 601

3.1.6 When Call Cannot Be Answered and Speech Cannot Be Made . . . . . . . . . . . . . . . . . . . 602

3.1.7 Line fault - Dterm . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 603

3.2 TRUNK FAULT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 604

3.2.1 Check Point . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 604

3.2.2 Trunk Control . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 607

3.2.3 Trunk (ORT, SND, CFT) Fault . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 608

3.2.4 Trunk (COT, TLT, DTI) Fault . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 609

4. ATTCON/DESKCON FAULT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 612

4.1 Check Point . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 612

4.2 ATTCON/DESKCON Control . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 612

4.3 ATTCON/DESKCON Fault . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 614

4.4 UNIT FAULT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 616

4.4.1 Check Point (1/2) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 617

4.4.2 Check Point (2/2) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 619

4.4.3 Unit Fault - Fault Related to Speech . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 621

4.4.4 Unit Fault - When Dial Tone (DT) Cannot Be Heard . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 623

4.4.5 Unit Fault - ACT-Side MUX Card Is Faulty and System Has Changed Over . . . . . . . . . . 626

4.5 SPEECH PATH (TSW) SYSTEM FAULT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 627

4.5.1 Check Point . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 628

4.5.2 Speech Path System Fault - Fault Related to Speech . . . . . . . . . . . . . . . . . . . . . . . . . . . 631

4.5.3 Speech Path System Fault - When Dial Tone (DT) Cannot Be Heard . . . . . . . . . . . . . . . 633

4.5.4 Speech Path System Fault - STBY Side Has Become Fault . . . . . . . . . . . . . . . . . . . . . . 634

4.6 CONTROL SYSTEM FAULT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 636

4.7 Check Point . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 637

4.7.1 Control System Fault - Fault Occurs Intermittently on ACT side . . . . . . . . . . . . . . . . . . . 640

4.8 Control System Fault - STBY Side Is Faulty . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 642

4.8.1 Fault That Cannot Be Detected . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 644

4.9 Power Supply Fault . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 645

4.9.1 Check Point . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 645

4.9.2 Fuse Blown Fault . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 648

4.9.3 Circuit Breaker OFF Fault in PWR Supply . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 648

4.9.4 Fault of Alarm Lamps on PWR Supply . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 649

– viii –

TABLE OF CONTENTS (CONTINUED)

Page

4.10 Fan Unit Fault . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 650

4.10.1 Check Point . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 650

4.11 Tone Fault . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 651

4.11.1 Check Point . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 651

4.11.2 Tone Fault . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 651

4.12 Common Channel Interoffice Signaling (CCIS) Line Fault . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 654

4.12.1 Check Point . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 654

4.12.2 CCIS Line Control . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 654

4.12.3 Specific CCH/CCT Card Is Faulty . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 655

4.12.4 Fault of CCH, DTI and Related Flat Cable . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 655

4.13 Integrated Service Digital Network (ISDN) Line Fault . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 657

4.13.1 Check Point . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 657

4.13.2 ISDN Line Control . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 657

4.13.3 Specific DCH/PRT Card Is Faulty . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 658

4.13.4 Fault of DCH, DTI, and Related Flat Cable . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 658

5. SYSTEM OPERATION . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 659

5.1 Indication of Lockout Stations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 660

5.2 Recovery Procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 661

5.3 Line Load Control . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 663

5.3.1 Operating Procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 663

5.4 IOC LINE MONITOR . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 667

5.5 Line Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 668

5.5.1 Make-Busy/Make-Busy Cancel of Station and Data Terminal . . . . . . . . . . . . . . . . . . . . . 668

5.5.2 Class Change and Number Change of Station and Data Terminal . . . . . . . . . . . . . . . . . 669

5.5.3 Make-Busy/Make-Busy Cancel of C.O. Line/Tie Line . . . . . . . . . . . . . . . . . . . . . . . . . . . . 669

5.5.4 Circuit Card Initialization Procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 670

5.6 How to Turn ON/OFF Whole System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 671

5.6.1 Power ON/OFF Procedure for Telephony Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 671

5.6.2 SV8500 Server Power ON/OFF Procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 672

5.6.3 PIR Power ON/OFF Procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 673

5.6.4 TSWR Power ON/OFF Procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 674

CHAPTER 6 ROUTINE MAINTENANCE PROCEDURE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 675

1. GENERAL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 675

2. FLOW OF PROCEDURES . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 675

2.1 Test Equipment and Tools . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 676

2.2 Routine Maintenance Procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 676

2.2.1 Check the Temperature and Relative Humidity in the Switch Room . . . . . . . . . . . . . . . . 677

2.2.2 Check the Operating Status of PCPro . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 677

2.2.3 Check To See If a System Message Indicating a Fault is Displayed . . . . . . . . . . . . . . . . 677

2.2.4 Check To See If There Is Any Lockout Station . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 678

2.2.5 Check Whether the FANU Is Operating Normally . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 678

2.3 Routine Maintenance Check List . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 679

CHAPTER 7 MAINTENANCE COMMANDS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 689

1. GENERAL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 689

– ix –

TABLE OF CONTENTS (CONTINUED)

Page

AACT Assignment of Activation Code . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 694

ALLC Assignment of Line Load Control . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 695

ALMG Assignment of Alarm Grade Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 696

AONE Assignment of One Activation Password Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 698

ASECL Assignment of Security Data (LDM) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 699

ASSW Assignment of Soft SW Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 700

ATDL Assignment of Terminal for Download . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 702

ATRF Assignment of Traffic Measurement Order . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 709

ATRFN Assignment of Traffic Measurement Order for FCCS Network . . . . . . . . . . . . . . . . . . . 711

AVERN Assignment of Software Version Information (NDM) For Fusion Network . . . . . . . . . . . 713

BOSD Back Up One-Touch Speed Call Memory Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 716

CADSD Continuous Assignment of Station Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 717

CARR Continuous Assignment of Alternative Route Restriction . . . . . . . . . . . . . . . . . . . . . . . . 720

CARRN Continuous Assignment of Alternative Route Restriction for NDM . . . . . . . . . . . . . . . . 721

CATK Continuous Assignment of Trunk Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 722

CBCN Control of Broadcasting for NDM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 729

CBCV Control of Broadcasting for VNDM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 730

CBKS Control Backup Station . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 731

CBND Calculate Bandwidth Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 733

CCSE Change of Common Signaling Channel Equipment . . . . . . . . . . . . . . . . . . . . . . . . . . . . 735

CDBU Change of Dch Backup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 736

CFCS Control of Flash Card System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 737

CLPB Control of Local Phone Book . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 739

CMNT Control of SR-MGC Maintenance Data (LDM) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 741

CMOD Change of System Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 746

CMWL Control Message Waiting Lamp . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 749

CMWL_T Control Message Waiting Lamps – Telephone Number . . . . . . . . . . . . . . . . . . . . . . . . 750

COSSL Control of SIP Server Data for LDM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 752

COSSN Control of SIP Server Data for NDM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 755

CPBKN Continuous Assignment of System Phone Book for NDM . . . . . . . . . . . . . . . . . . . . . . . 758

CPCP Control of PC Port . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 764

CPRS Controlled Alternate PRSCs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 766

CSCL Continuous Change of Station Class . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 767

CSPAL Continuous Delete of Special Access Code for LDM . . . . . . . . . . . . . . . . . . . . . . . . . . . 769

CSPAN Continuous Delete of Special Access Code for NDM . . . . . . . . . . . . . . . . . . . . . . . . . . 772

CSTN Continuous Change of Station Number . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 776

DCBD Display of Call Block Entry Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 777

DCEN Display of Connection Trunk LENS Data for LDM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 779

DCON Display of Connection Status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 780

DDMO Display of Data Memory Occupancy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 782

DEBUG General Purpose Debug Function . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 783

DFLN Display Up of Location Free Numbering . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 791

DFTD Display of System Message Details . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 792

DHDF Display of HD File Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 793

DICBD Display of Individual Call Block Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 795

DIMG Display Information of Media Gateway . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 797

– x –

TABLE OF CONTENTS (CONTINUED)

Page

DIPI Display IP equipment Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 798

DISD Display of IP Station Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 801

DISI Display of IP Statistics Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 808

DISS Display of Program Issue . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 814

DLEN Display of LENS Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 815

DLSL Display of Lockout Station - LENS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 817

DLSS Display of Lockout Station - Number . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 818

DLSS_T Display of Lock Out Station – Number – Telephone Number . . . . . . . . . . . . . . . . . . . . 819

DLTEL Display of Telephone Number from LENS for LDM . . . . . . . . . . . . . . . . . . . . . . . . . . . . 820

DNTEL Display of Telephone Number from LENS for NDM . . . . . . . . . . . . . . . . . . . . . . . . . . . . 821

DPHL Display of PHL Package Status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 822

DPKG Display of Setting Port Package . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 823

DPSW Display Package Switch Status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 824

DPTR Display of Capacity / License . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 826

DSTN Display of Station Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 827

DTELN Display of Telephone Number Data for NDM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 829

DTF101 Display of Terminal Traffic Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 831

DTF102 Display of Route Traffic Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 832

DTF103 Display of Station Peg Count Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 833

DTF104 Display of Attendant Peg Count Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 834

DTF105 Display of Route Peg Count Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 835

DTF201 Display of Service Peg Count Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 836

DTF301 Display of UCD Route Peg Count Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 837

DTF302 Display of UCD Group Peg Count Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 838

DTF303 Display of UCD Station Peg Count Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 839

DTF501 Display of Attendant Answering Peg Count Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 840

DTF601 Display of Connection Route Peg Count Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 841

DTF602 Display of Connection Route Traffic Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 842

DTF701 Display of IP Service Peg Count Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 843

DTF702 Display of IP Service Traffic Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 844

DTF801 Display of SIP Service Peg Count Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 845

DTF101N Display of Terminal Traffic Data for FCCS Network . . . . . . . . . . . . . . . . . . . . . . . . . . . . 846

DTF102N Display of Route Traffic Data for FCCS Network . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 847

DTF103N Display of Station Peg Count Data for FCCS Network . . . . . . . . . . . . . . . . . . . . . . . . . 848

DTF104N Display of Attendant Peg Count Data for FCCS Network . . . . . . . . . . . . . . . . . . . . . . . 849

DTF105N Display of Route Peg Count Data for FCCS Network . . . . . . . . . . . . . . . . . . . . . . . . . . 850

DTF201N Display of Service Peg Count Data for FCCS Network . . . . . . . . . . . . . . . . . . . . . . . . . 851

DTF301N Display of UCD Route Peg Count Data for FCCS Network . . . . . . . . . . . . . . . . . . . . . . 852

DTF302N Display of UCD Group Peg Count Data for FCCS Network . . . . . . . . . . . . . . . . . . . . . . 853

DTF303N Display of UCD Station Peg Count Data for FCCS Network . . . . . . . . . . . . . . . . . . . . . 854

DTF501N Display of Attendant Answering Peg Count Data for FCCS Network . . . . . . . . . . . . . . 855

DTF601N Display of Connection Route Peg Count Data for FCCS Network . . . . . . . . . . . . . . . . . 856

DTF602N Display of Connection Route Traffic Data for FCCS Network . . . . . . . . . . . . . . . . . . . . 857

FLINST File Install . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 858

HDFP HDD Format of SV8500 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 859

IPAN Display of IP machine status display function . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 860

– xi –

TABLE OF CONTENTS (CONTINUED)

Page

MBCT Make-Busy of Connection Trunk for LDM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 874

MBCTC Make-Busy of Connection Trunk-Continuous for LDM . . . . . . . . . . . . . . . . . . . . . . . . . . 875

MBLE Make-Busy of LENS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 876

MBPH Make Busy of PHL Package for LDM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 877

MBPM Make-Busy of Port Microprocessor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 879

MBRT Make-Busy of Route . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 880

MBRT_LR Make-Busy of Route - Logical Route Number . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 881

MBSM Make-Busy of System Message Printout . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 882

MBST Make-Busy of Station . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 883

MBST_T Make-Busy of Station – Telephone Number . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 884

MBTC Make-Busy of Trunk-Continuous . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 885

MBTC_LR Make-Busy of Trunk-Continuous – Logical Route Number . . . . . . . . . . . . . . . . . . . . . . 886

MBTK Make-Busy of Trunk . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 887

MBTK_LR Make - Busy of Trunk – Logical Route Number . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 888

MEM_HDD Data Control Between Memory and HDD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 889

MEM_HDD_N Data Control Between Memory and HDD for Fusion Network . . . . . . . . . . . . . . . . . . . . 891

MFCH Make Busy of FCCH . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 893

PMBU Port Microprocessor Back Up . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 894

RALM Release Alarm . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 895

RALMN Release Alarm for NDM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 896

RDPD Removal of Dterm IP Password . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 897

RINZ Route Initialize . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 898

RLMG Release of Media Gateway . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 899

RLST Release Station/Trunk . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 900

RLST_T Release of Station/Trunk – Telephone Number . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 902

RPID Remove of Pad Lock ID Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 904

SCVT Setting / Change of Virtual Trunk Operation Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 905

SINZ System Initialize . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 906

SINZN System Initialize for the FCCS Network . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 908

SPTS Scanning of Port Status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 909

SRTS Scanning of Route Status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 914

SRTS_LR Scanning of Route Status - Logical Route Number . . . . . . . . . . . . . . . . . . . . . . . . . . . . 915

TOGC Test of Originating Connection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 916

APPENDIX A MINOR VERSION UPDATE FOR ONLINE SOFTWARE . . . . . . . . . . . . . . . . . . . . . . . . . . . . 919

1. GENERAL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 919

2. PRECAUTIONS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 919

3. APPLYING THE PATCH FILES . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 919

4. Deleting Patch Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 922

5. Canceling Applied Patch Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 922

XPAT On–line Patch Install . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 923

– xii –

INTRODUCTION

1. General Knowledge of SV8500

1.1 About Release Information

The table below shows the relationship between IPX/SV7000 and SV8500 for the release information.

IPX/SV7000 SV8500

R25 S1

R25E S1E

R26 S2

– INT-1 –

1.2 Structure of Telephony Server

1.2.1 General

This section explains the structure of Telephony Server, mainly about processors it has. Telephony Server has
TP and SP as processors on its CPU. Both TP and SP work together to provide various features. The following
are general description of TP and SP.

• TP: Telephony Processor, supports all the features provided in the system.

• SP: Signaling Processor, works as SIP server that handles call control signals using Session Initiation

Protocol (SIP). SP consists of two parts - one for SIP terminals using a particular feature called
SIP TERMINAL ACCOMMODATION [S-146] (hereinafter called “SP (for SIP terminal)”), and
the other for other devices/stations using SP (hereinafter called “SP (MPH)”).

Note: Each of IP devices/stations communicates with either of them (TP/SP) as registration destination. For in-

formation about it, refer to “Registration Destination of IP Devices/Stations”.

1.2.2 TP and SP for System Changeover

In dual configuration, each processor may stay in active (ACT) or stand-by (STBY) state. ACT-side processors
handle each operation while STBY-side processors prepare for system changeover. Their states change when
system changeover is performed. The relationship between system changeover and the state of each processor
(TP/SP) is described below.

• TP: changes its state (ACT/STBY) according to the state of the system to which the TP belongs.

• SP: operates differently between two parts of SP.

• SP (for SIP terminal)

Note 1: operates simultaneously with ACT-side TP.

• SP (MPH): is always in ACT (changeover is not executed).

ACT

STBY

System #1 (STBY)

SP

(for SIP Terminal)

System #0 (ACT)

(for SIP Terminal)

Note 1

SP

Note 1

TP

TP

SP

(MPH)

SP

(MPH)

System

Changeover

System #1 (ACT)

SP

(for SIP Terminal)

System #0 (STBY)

(for SIP Terminal)

Note 1

SP

Note 1

TP

SP

(MPH)

TP

SP

(MPH)

Note 1: “SIP terminal” here refers to ones using SIP TERMINAL ACCOMMODATION [S-146] feature. For infor-

mation about this feature, refer to the Data Programming Manual - Business.

– INT-2 –

1.3 Registration Destination of IP Devices/Stations

Here lists IP addresses of Telephony Server to be assigned to each IP device/station as its registration destina­tion. The IP address varies depending on several conditions, consisting of PH kind that handles the device/sta­tion, protocol mode in which the device/terminal operates, and Telephony Server’s configuration. The table
below specifies the IP address necessary for each IP device/station, covering all the conditions.

CPU

Note 1

TP

SP

Category

PH

Internal PHE

Internal PHI

SP-

PHD

MPH

SP-

PHI

IP Address of

Registration Destination

Device/Station

Protocol

mode

Single

Configuration

Dual

Configuration

Analog 2MC

Proprietary

Protocol mode

MC&MG-COT (MC part)
IP-BS

LAN1 (ACT)

Note 4

LAN1 (ACT)

Note 4

VS32
MC&MG-COT (MG part)

Proprietary

Protocol mode

MG-COT
MG(BRI)
MG(PRI)

Note 2

LAN1 (ACT)

Note 4

LAN1 (ACT)

Note 4

MG(SIP)

Proprietary

Protocol mode

IP terminal

LAN1 (ACT)

Note 4

LAN1 (ACT)

Note 4

SIP mode SIP terminal Note 3 LAN1 (ACT) LAN1 (ACT)

Proprietary

Protocol mode

MC&MG-COT (MG part)
MG(BRI)

LAN1 (ACT)

Note 4

LAN1 (ACT)

Note 4

MG-COT

SIP mode

MG(BRI)
MG(PRI)
MG-T1(SIP)
8LC Card

LAN1 (ACT)

LAN1
(System #0)
/(System #1)

VS32

- SIP mode

Note: Device/terminal names in the table are general terms. If you want to know formal names of them, refer to

WLAN Handset (MH Series)
Standard SIP Terminal

LAN1 (ACT) LAN1 (ACT)

“TERMS IN THIS MANUAL” at the top of this manual.

Note: In this manual, Telephony Server may be referred as “DRS” or “SIP server” depending on the registration

destination. IP address of DRS/SIP server is, however, same as that of Telephony Server. Therefore, IP ad­dress of DRS/SIP server is also as the table above.

Note 1: Telephony Server has two parts of processors on its CPU, TP and SP. For the information about it, refer

to “Structure of Telephony Server”.

– INT-3 –

Note 2: MG(PRI) in Proprietary Protocol mode uses LAN1 as the registration destination while uses LAN2 as the

signaling control port. LAN interface for the signaling control port, however, can be changed to LAN1 by
ADTM command.

Note 3: “SIP terminal” excludes WLAN Handset (MH Series) here.

Note 4: When migrating from existing IPX/SV7000 to SV8500, LAN1/LAN2 can be selected as LAN interface for

IP equipment/terminals that use Proprietary Protocol mode. For the detail, refer to the Migration Manual.

– INT-4 –

1.4 Lan Interface Accommodation

There are four LAN ports on the front panel of Telephony Server, of which LAN1 and LAN2 play a central role
in managing the whole system. This section explains usage of them (LAN1/LAN2). Additional information
about the LAN ports is described in “Management by 4-LAN Port” of the Installation Manual.

1.4.1 LAN1 Accommodation

LAN1 mainly accommodates the devices/terminals for call controlling. They do not need to keep links with Te­lephony Server when system changeover is performed in dual configuration system. In each case where the sys­tem is in single configuration or dual configuration, IP address (ACT) is basically assigned to the devices/
terminals as Telephony Server address.

Note: When the system is in dual configuration, IP address (System #0/#1) is used instead of IP address (ACT)

in the following cases.

• Telephony Server address as FTP server

• Telephony Server address as registration destination for IP devices accommodated in SP-PHI and us-

ing SIP mode. (See Registration Destination of IP Devices/Stations)

ALM

MB

SYS

SYS

LINK OPE

SYS

PWR

ALM

SYS 1

SYS 0

LINE SPEED

LINE SPEED

1

PWR

ACT

ALM

PWR

ACT

ALM

3

2

4

LINE SPEED

LINE SPEED

LINE SPEED

LINE SPEED

1

3

2

4

LINE SPEED

LINE SPEED

(SUB)

12 12

SWO0 SWO1

PBI No.

LOCK

SEL

PFT

INIT

EMA MAIN

PSTN

FCCS

over IP

LAN3

LAN4

IP Terminal

SIP Terminal

LAN1

LAN2

– INT-5 –

Each communication using LAN1 as its interface is listed in the table below, where relationships between each
application and socket are shown.

Application Protocol Port No. IP Address

Registration by Proprietary Protocol UDP 3456 ACT
Registration by SIP UDP 5060 ACT/System #0/System #1
Internal PHI Note 1 UDP 64000
NMS TCP 60060
Receiving Health Check from SR-MGC (Server) UDP 60110
Sending Health Check to SR-MGC (Client) UDP 60120

ACT

SR-MGC Charge MGC Side TCP 60140
SR-MGC Charge SR-MGC Side TCP 60150
Internal PHE UDP 60130
Internal PHF UDP 60180
FTP TCP 20/21
SSH TCP 22

System #0/System #1

Telnet TCP 23
HTTP TCP 80

Note 1: Internal PHI may use LAN2 for communication with MG(PRI), which depends on your setting.

– INT-6 –

1.4.2 LAN2 Accommodation

LAN2 mainly accommodates the devices for operation/administration and some for call controlling. They need
to keep links with Telephony Server when system changeover is performed in dual configuration system. In
each case where the system is in single configuration or dual configuration, IP address (ACT) is basically as­signed to the devices as Telephony Server address.

ALM

MB

SYS

SYS

LINK OPE

SYS

PWR

ALM

SYS 1

SYS 0

LINE SPEED

LINE SPEED

1

PWR

ACT

ALM

PWR

ACT

ALM

3

2

4

LINE SPEED

LINE SPEED

LINE SPEED

LINE SPEED

1

3

2

4

LINE SPEED

LINE SPEED

(SUB)

12 12

SWO0 SWO1

PBI No.

LOCK

SEL

PFT

INIT

EMA MAIN

LAN3

LAN4

Maintenance

CCIS

Console

LAN1

LAN2

Server

ACT

PWR

ALM

LAN1LAN2

TxRx LINKTxRx LINK

LOAD

over IP

Each communication using LAN2 as its interface is listed in the table below, where relationships between each
application and socket are shown.

– INT-7 –

Application Protocol Port No. IP Address

PCPro TCP 60000
CCIS Cluster TCP 60001
SMDR TCP 60010
MCI TCP 60020
OAI TCP 60030
MIS TCP 60040
PMS TCP 60050
CS Report TCP 60080
MCC TCP 60190
FCCS Cluster TCP 60210
DEBUG UDP 1024-65535
SNMP UDP 161/162
SMTP (Client) TCP 1024-65535
DNS UDP 53
SNTP UDP 123
Internal PHI (for MG(PRI)) TCP 64000
Internal PHC (Server) TCP 57000
Internal PHC (Client) TCP 65030

ACT

– INT-8 –

1.5 Trunking Diagram

The figure below shows the trunking diagram of SV8500 for overviewing the network configuration.

Analog TEL

Digital terminal

ISDN terminal

Analog PSTN

Tie line

CCIS

BWT

DOD

DIT

DID

MDF

Telephony Server

NCU

LC

ELC

ILC

COT

COT

COT

DID

EMT

ODT

LDT

DTI

MUX/TSW

DTI

CCH

Note 1

ORT

IRT

SND

CFT

CCH

DTI

DCH

PRT

BRT

ATI

SV8500 Server

ATT/Desk Console

GW

ISDN (PRI)

ISDN (PRI)

ISDN (BRI)

AP

IP terminal

MODEM

SIP terminal

IP-BS

PS

Router

IP network

Note 1: In this manual, the range blocked in dotted red is called Telephony Server.

Note 2: In this manual, the range blocked in dotted blue is called SV8500 server.

Printer

PCPro

IOC

Note 2

– INT-9 –

This table identifies the function name of each line/trunk interface and switching controller.

SYMBOL DESCRIPTION

ATI Attendant Console Interface

BRT Basic Rate Interface Trunk

BWT Bothway Trunk

CCH Common Channel Handler

CFT Conference Trunk
COT Central Office Trunk
DCH D-Channel Handler

DID Direct Inward Dialing

DIT Direct-In Termination
DLC Digital Line Circuit
DOD Direct Outward Dialing

DTI Digital Interface

ELC Electronic Line Circuit
EMT E&M Trunk

IOC Input/Output Controller

IRT Incoming Register Trunk

LC Line Circuit

LDT Loop Dialing Trunk

LTST Line Test

MDF Main Distribution Frame

MUX Multiplexer

NCU Night Connection Unit
ODT Outband Dialing Trunk
ORT Outgoing Register Trunk

PRT Primary Rate Interface Trunk
SND Sender

TLT Tie Line Trunk
TSW Time Division Switch

– INT-10 –

CHAPTER 1 General

CHAPTER 1 General

1. ABOUT THIS MANUAL

This manual describes routine system maintenance procedures and fault repair procedures. This chapter explains
the system configuration as well as how to follow the manual and provides precautions pertaining to
maintenance jobs as a whole. Be sure to read this chapter thoroughly before starting the required maintenance
project.

2. SYSTEM ACCOMMODATION

SV8500 consists of the following components:

• SV8500 Server

•PIR

• TSWR

•FANU

The following shows a fully expanded system (DC-powered Model, 4-IMG) as an example.

SV8500 Server

FANU

TSWR

PIR 3

PIR 2

PIR 1

FANU

PIR 0

BASEU BASEU BASEU BASEU

PIR 7

PIR 6

PIR 5

FANU FANU FANU

PIR 4

FRONT

2.1 SV8500 Server

SV8500 Server can accommodate the following cards and modules:

•CPU Card

•EMA Card

• IOC Card (option)

• EMA SUB-A (option: required for PIR)

• EMA SUB-B (option: required for TSWR)

• EXB (option: required for PIR/TSWR)

• Power Module

• System Cooling FAN Module

PIR 11

PIR 10

PIR 9

PIR 8

PIR 15

PIR 14

PIR 13

PIR 12

– 1 –

CHAPTER 1 General

CPU Card #1

CPU Card #0

EMA SUB-A

EMA SUB-B

EXB #1

EXB #0

Front View

Rear View

EMA

IOC (Option)

Power Module

System Cooling FAN Module

Power Module

– 2 –

CHAPTER 1 General

00 01 01 02 03 04 05 06 07 08 09 10 11 12 13 14 15

DC-DC PWR #0 (PWR)

DC-DC PWR #1 (DPWR)

DLKC #00

DLKC #01

GT #00

GT #01

TSW #00

TSW #01

TSW #02

TSW #03

TSW #10

TSW #11

TSW #12

TSW #13

PLO #0

PLO #1

Slot number

Type of circuit card

2.2 PIR and TSWR

Figure 1-1 and Figure 1-2 show the slot configuration and the condition of mounted circuit card types.

Figure 1-1 Slot Accommodation (PIR)

Slot number

Type of circuit card

Number of ports

Circuit card label color

00 01 02 03 04 05 06 07 08 09 10 11 12 13 14 15 16 17 18 19 20 21 22

DC-DC PWR #0 (PWR)

DC-DC PWR #1 (DPWR)

Line / Trunk

Line / Trunk

Line / Trunk

Line / Trunk

Line / Trunk

Line / Trunk

16 1616 16 1616 16 16 16 16 16 16323232

Unieversal Slots

for Line/Trunk cards

Line / Trunk

Line / Trunk

Line / Trunk

TSW / MUX #0

TSW / MUX #1

Line / Trunk

Line / Trunk

Unieversal Slots

for Line/Trunk cards

Line / Trunk

Line / Trunk

Figure 1-2 Slot Accommodation (TSWR)

Line / Trunk

Line / Trunk

Line / Trunk

32 32

Line / Trunk

– 3 –

3. GLOSSARY

The following is a list of typical technical terms that are used in this document.

• C-Level Infinite Loop

• B-Level Infinite Loop

• Port Microprocessor (PM)

• Ready Error

• Parity Error

• Monitor Restart (Phase 0)

• Phase 1 Restart

• PM (Line/Trunk Card) Make-Busy Restart

CHAPTER 1 General

• Data Copy Restart

•MEM (Memory)

– 4 –

CHAPTER 1 General

• C-Level Infinite Loop
A program repeatedly executes specific routines due to a fault of the main memory, data destruction,

etc. The program is not able to process normally. This faulty condition is referred to as Program Infinite
Loop. C-Level infinite loop is a state where a specific program is endlessly repeated, blocking period­ical programs to be executed.

• B-Level Infinite Loop
This is a state where a program infinite loop has occurred during connection processing and the

connection for the next call is not able to process.

• Port Microprocessor (PM)
Each line/trunk card mounted in the PIR is equipped with a processor called Port Microprocessor (PM),

which continuously supervises the lines/trunks.

• Ready Error
For acknowledging the connection between the CPU and a circuit card, an interface signal called Ready

Signal is used. When the CPU has accessed a specific circuit card and the normality of the connection
is acknowledged, the Ready Signal is returned to the CPU within a certain time period. If the Ready
Signal is not returned to the CPU within the above time period after access, the situation is referred to
as Ready Error.

• Parity Error
For confirming the normality of data transfer between the CPU and the circuit card under the control

of the CPU, a parity check is made. When an error is detected in a parity check, it is referred to as Parity
Error. Parity check means to confirm the normality of data by adding an error detecting parity bit to a
set of data to transfer.

When a set of data is transferred, a parity bit is added to the data so that the data has an even-number
of “1” bits (referred to as Even Parity). When there is an odd-number of “1” bits in the received one set
of data, it is detected as an error.

• Monitor Restart (Phase 0)
Monitor Restart processing suspends current processing in progress without applying any hardware

controlling, allowing the system to restart its operations from the Monitor Program. The system aban­dons only the processing of the calls being handled by the program, and maintains all the connections
that have already been established. In the case of CPU system fault such as out-of-memory fault, the
system executes the monitor restart after outputting the system message and setting the hidden memory
fault.

• Phase 1 Restart
The system is initialized. All connections except for two-way connections that have already been

established are forcibly released.

• PM (Line/Trunk Card) Make-Busy Restart

– 5 –

CHAPTER 1 General

In this processing, the faulty PM (Line/Trunk Card) is isolated from the system and, at the same time,
the calls associated with that faulty PM (Line/Trunk Card) are released. No calls related to the faulty
PM (Line/Trunk Card) are processed and the system normally runs without the faulty PM (Line/Trunk
Card).

• Data Copy Restart
In a system of dual configuration, the RAM memory (including the data memory) is copied from the

ACT-side CPU into the STBY-side CPU, and ACT/STBY is changed over and monitor restart is exe­cuted.

In the case of this restart processing, only the ACT-side CPU and the STBY-side CPU are changed over
without any effect on the current connections. However, no call processing is executed while the restart
processing is in progress (from copying until the end of the changeover).

•MEM (Memory)

A memory module that is mounted on the CPU Card.

– 6 –

CHAPTER 1 General

SP

-2

34

SP-

2

3

4

SN12

34

4. HOW TO READ PRECAUTIONS, DIAGNOSTIC, AND FAULT REPAIR INFORMATION

4.1 Precaution about Diagnostic Procedure/Fault Repair Procedure

When performing diagnostic procedures/fault repair procedures, always adhere to the following actions:

(1) When replacing a circuit card with a spare, handle the circuit card using the Field Service Kit.

(a) To protect the circuit card from static electricity, wear a wrist strap before handling the circuit card.
(b) Before extracting the circuit card from its mounting slot, set its MB switch to the UP side (ON).

(2) When holding a circuit card by hand, wear gloves and be careful not to touch mounted parts, gold-plated

terminal, etc., on the circuit card.



The 3M

Model 8012 Portable Field Service Kit, shown in Figure 1-3, is recommended as an effective

countermeasure against static electricity.

Figure 1-3 How to Handle Circuit Cards

<How to handle circuit card>

Note 1:

Connector

Set MB key
to UP.

installer

SP-234

Card puller tab

Connect ground wire to
the frame. Note 1

Place the circuit card on
a conductive sheet.

Backboard
contact portion

wrist strap

SP-234

SN1234

wrist strap

U

U

P

P

( )

( )

U

U

P

P

( )

( )

PWR

ACT

ALM

EMA

APEX

SV7000

TP/S

LOAD

LAN1

LAN2

TxR
x

LIN
K
TxRx

PWR

ACT

LINK

ALM

APEX

SV7000

SP/S

LOAD

LAN1LAN2

TxRx LIN

K
TxRx LINK

conductive sheet

A ground wire should be connected to the frame which is not coated by an insulating material.

– 7 –

CHAPTER 1 General

SP-2

34

SN1

23

4

SP-2

34

SN1

2

3

4

CF

CO

NS

OLE

M

O
DE

US

B

L
INE

S
PEED

LINE

S
PEE

D

L
I

N
E

S

PEED

LI

N
E

SPE

ED

1

O

N

2

3

4

CF

CON

SO

LE

M

O
DE

US

B

1

O

N

2

3

4

M

B

(SUB)

SYS
LOC

K

SYS
SE

L

PFT

1

2

SWO0

SWO1

1

2

Figure 1-4 How to Hold a Circuit Card

When holding a circuit card with bare hands, do not touch the component mounted side of the card or
the connector portion.

Note

Connector
(Contact)

Set MB switch
to UP.

SP-234

SN1234

Card Puller
Tab

Portion

Component­Mounted Side

SP-234

SN1234

wrist strap

Note: Do not touch the Gold-Plated Terminal with bare hands.

(3) Be sure to take appropriate anti-static measures when handling a CF card.

Note: Do not insert or remove the CF card while the SV8500 server is in operation.

Figure 1-5 How to Handle a CF card

PWR

LOAD

ON

LINE

CF

wrist strap

Note 1:

CONSOLE

PWR

LOAD

ON

LINE

CF

CONSOLE

A ground wire should be connected to the frame which is not coated by an insulating material.

LINE SPEED

1

LINE

ON

SPEED

PWR

SPEED

LINE

EXPRESS GEAR

SPEED

LINE

SPEED

LINE

EXPRESS GEAR

SYS
ALM

3

LINK

SYS 1

OPE

SYS 0

4

SPEED

SPEED

3

4

SPEED

ALM

MB
(SUB)

PF

SYS
LOCK

SYS
SE

SWO0

INIT

SWO1

PBI No.

EMA MAIN

MODE

2

USB

LINE

LINE

1

ON

MODE

2

USB

LINE

CF card

Connect ground wire to
the frame.

Note 1

– 8 –

CHAPTER 1 General

(4) When a circuit card appears faulty, check the following items before replacing it with a spare:

(a) Poor connector contact at the circuit card may be responsible for the fault. Repeat insertion and ex-

traction of the circuit card a few times. Clean the connector portion, and recheck for proper operation.

(b) Check the lead wires of vertically-mounted parts (resistors, capacitors, etc.) to ensure they have not

shorted each other or broken.

(c) Check the back side of the circuit card to see if there is any short-circuited soldered portion, or mod-

ified cross connection wires erroneously left unconnected.

(d) Check the ROMs to ensure proper seating in the IC socket. Figure 1-6 shows a leg that is bent and not

set in the socket.

Figure 1-6 How to Set the ROM in IC Socket

A pin is bent, not
inserted in the socket.

ROM

SOCKET

(5) How to clean the connector portion (gold-plated terminal):

(a) Dip the gold-plated terminal portion in the cleaning fluid for three to five seconds (only PA-XX type

circuit card), as shown in Figure 1-7.

Figure 1-7 How to Clean the Connector Portion

Cleaning

Circuit

Container

Note 1:

Some of the parts are subject to damage if they come in contact with the cleansing liquid. Be careful to
allow only the connector portion (gold-plated terminal) to contact the cleaning liquid.

Note 2: Be sure to use fresh cleaning fluid (FREON or isopropyl alcohol).

– 9 –

CHAPTER 1 General

(b) Using a soft cotton cloth, wipe both sides of the connector portion (gold-plated terminal) clean (only

PA-XX type circuit card), as shown in Figure 1-8.

Figure 1-8 How to Clean Gold-Plated Terminal

gauze

Gold-plated terminal

Note 1:

Note 2: After wiping, be careful not to leave lint on the surface of the circuit card.

Use cloth (gauze, etc.) to clean.

(6) When a check on the flat cable or LT cable is directed in the tree, check the following items:

(a) Make a visual check to see if the connector is properly connected.
(b) Poor connector contact may be responsible for the fault. Repeat connection and disconnection a few

times, and check again to see if the connector is properly connected.

(c) Perform continuity test on the flat cable.

(7) When replacing the circuit card is directed in the tree, replace the circuit card with a spare as per Chapter 5.

(8) When multiple circuit cards appear faulty, before replacing them with spares, remount them (one at a time)

into their slots, to determine which cards should be replaced.

– 10 –

START

CHAPTER 1 General

• The following is an example where the fault was recovered after the replacement of circuit cards:

Set the first circuit card back into its mounting slot

If the fault recurs: Replace the circuit card.

Set the second circuit card back into its mounting slot

If the fault recurs: Replace the circuit card.

Set the third circuit card back into its mounting slot

If the fault recurs: Replace the circuit card.

END

If a circuit card is found faulty, send the faulty circuit card for repair.

The fault may be a temporary one, or due to poor contact of the circuit card. Observe the

situation for a while.

(9) When a fault recovery is completed, use the RALM command to clear all the alarm indications and regis-

tered system messages. If required, restore temporary cross connections and transient data for testing to the
original ones.

4.2 How to Follow Diagnostic Procedure/Fault Repair Procedure

(a) Diagnostic Work

A fault diagnostic procedure by system message is explained in the TREE format on an individual sys­tem message basis.

– 11 –

CHAPTER 1 General

• Proceed with judgment as to whether the fault status coincides with the indicated status, following
the sequence beginning from START.

• How to proceed with the diagnosis work is explained in Figure 1-9.

STEP 1 Determine whether the fault coincides with the fault status (1) in Figure 1-9.

STEP 2 If the fault status does coincide, the fault is indicated by (2). Repair the fault by referring to the

relevant section in Chapter 4. Otherwise, proceed to (3).

STEP 3 Perform the work indicated by (3). The result of the work (3) is broken down as indicated by (4).

STEP 4 Determine whether the result of work (3) coincides with the status indicated by (5). If so, the

fault(s) is/are indicated either by (6) or by (7). If not, proceed to the next Step.

STEP 5 Perform the work indicated by (8), and if the result of the work is the same as the status indicat-

ed, the fault is indicated by (9). If the fault repair work indicated by (9) affects another normal
line, recheck the work as indicated by (10).

(b) Fault Repair Procedure

A fault repair procedure is explained by means of TREE format in Chapter 4. The following explains
how to follow the TREE format and proceed with designated work. See Figure 1-10.

• Begin from START and proceed with the necessary repair work following the sequence.

• When a faulty circuit card (or circuit cards) is suspected, replace the faulty circuit card with a spare
in accordance with the work procedure pertaining to that specific circuit card.

STEP 6 Replace the circuit card indicated by (A) with a spare and check it. Perform the detailed work

as per (B). If the fault status is beyond repair, proceed to the next step.

STEP 7 If the range of the fault or the system configuration is as indicated by (C), perform a check as

indicated by (D). If the fault status is beyond repair, proceed to the next step.

STEP 8 Replace the circuit card indicated by (E) with a spare and check it. The detailed procedure indi-

cated by (G) varies with the system configuration indicated by (F).

– 12 –

Figure 1-9 Diagnostic Work Items and Symbols Example

CHAPTER 1 General

START

When

Perform

(4)

When

END

(1)

(3)

When

When

(8)

with

performed

Note: (1): Judgment of fault status

(2),(6),(7),(9): When the fault status coincides with the indication, the cause of the fault is indicated.
(11): When repairing the fault, refer to the relevant section in Chapter 4.
(3): Operating items for diagnosis
(4): Branching of the result of the operation
(5): Judgment of the status of the result of the operation
(8): When operating method is unknown, refer to Chapter 5.

(5)

(5)

(2)

FAULT

FAULT SUPERVISION

FAULT

FAULT

: It is the fault of

Section No.

(7)

: It is the fault of

Section No.

(9)

:

CHECK OF WORK

Section No.

(Chapter 5)

(11)

(6)

(Chapter 5)

(11)

(10)

(Chapter 5)

(11)

– 13 –

Figure 1-10 Recovery Procedure Example

CHAPTER 1 General

START

Check

When

Check

(A) (B)

(C) (D)

Check

(E)

(F) (G)

When

(F)

(G)

When

END

– 14 –

CHAPTER 1 General

5. REPORTING FAULT TO NEC

When the cause of a fault is uncertain, make note of the situation involved and report it to NEC. When
forwarding faulty circuit cards to NEC, exercise caution to protect from static electricity.

5.1 Fault Reporting Method

The following three items must be included in the report without fail:

(1) Faulty situation (reports should be similar to “dial tone is not heard only on individual lines,” “incoming

C.O. line calls are not able to be terminated only to a specific ATTCON/DESKCON,” etc.)

• Faulty phenomena
On lifting the handset, dial tone is not heard but side tone is heard, etc.

• History of fault
When did the fault occur? What kind of repair procedure has been executed? Does the fault still exist

or not exist? etc.

• Range of fault
Range of fault should be reported: Single line?, Specific trunk?, Specific circuit card?, Specific PIR?,

Whole system?, etc.

– 15 –

CHAPTER 1 General

(2) Circuit Card Version Number, Program Name, and Program Package Version Number of the circuit card.

See Figure 1-11.

Figure 1-11 Circuit Card Version Number, Program Name, and Program Package Version Number

16LC

Circuit Card Name

Circuit Card Version Number

Program Name

Program Package
Version Number

SPA­16LCBE

SP 785

A 6A

Front

9A 91-03

TR 5448

Right View of Circuit Card

– 16 –

CHAPTER 1 General

5.2 Forwarding Faulty Circuit Card Method

Send the faulty circuit card to the NEC agent to whom a request is made for a replacement card. Adhere to
the following procedure for sending the faulty circuit card:

(1) Insert connector covers onto the circuit card terminals.

(2) Put the circuit card into a static electricity protective bag.

(3) Pack the circuit card with air cap, etc.

(4) Set the circuit card into the cardboard box for that specific circuit card.

(5) If multiple circuit cards are sent, set each circuit card in a separate cardboard box and stuff the box with

shock absorbing material.

When sending a faulty circuit card, put it in a static guard bag. To prevent damage, never place the circuit card
in a vinyl bag or ship it without a protective bag.

– 17 –

6. SYSTEM MAINTENANCE OUTLINE

This chapter explains the outline of fault diagnosis and duties necessary to maintain the system. Figure 1­12 shows the workflow of the administrative management procedures.

Figure 1-12 Flow of Administrative Management Procedures

Administrative

Management Procedures

Administrative Procedures

CHAPTER 1 General

Expansion and Change of
Station Users

See Chapter 6

Traffic Management

Actions on Claims from
Station Users and/or Operators

Management Procedures

Station Message Detail
Recording System (SMDR)

Routine Diagnosis

Diagnosis result, system message displays abnormality

Routine Maintenance

System Status Monitor

Alarm Indications

Collection of System Messages

Indication of Lockout Stations

See Chapter 2

(A)

(B)

Office Data Management and Office
Data Protection

See Chapter 2

(A)

See Chapter 2

See Chapter 2

See Chapter 7

See Chapter 2

Fault Analysis/
Test Operation/
Changeover/
Make-Busy/Circuit
Card Change/
Initialization

Line fault

Circuit card fault

Terminal
(Tel., etc.) fault

Fault cause not
able to be localized

(B)

Refer to

Chapter 2,

Chapter 6

(Abnormal
Congestion)

Line Load Control

– 18 –

See Chapter 6

CHAPTER 1 General

7. BASIC KNOWLEDGE

This section identifies the information necessary for the system operations and maintenance procedures.

• System Configuration

• Line Equipment Numbers (LENS)

• Local Partition (LP) Number

• Fault Detecting Function

• Range of Faults Specification

– 19 –

CHAPTER 1 General

A

7.1 System Configuration

Figure 1-1 shows the system configuration of the fully expanded 1-IMG and 4-IMG type. For details on
each module accommodation, see Figure 1-2 through Figure 1-4.

Figure 1-1 System Configuration

DC Powered Model:

1-IMG 4-IMG

4-PIR (maximum) IMG 0 IMG 1 IMG 2 IMG 3

PIR 3

PIR 2

PIR 1

FANU

PIR 0

SV8500
server

BASEU

FANU

TSWR

SV8500
server

BASEU

PIR 3

PIR 2

PIR 1

FANU

PIR 0

BASEU

PIR 7

PIR 6

PIR 5

FANU

PIR 4

BASEU

PIR 11

PIR 10

PIR 9

FANU

PIR 8

BASEU

PIR 15

PIR 14

PIR 13

FANU

PIR 12

BASEU

max. 1536 physical ports

C-DC Powered Model:

1-IMG

4-PIR (maximum)

FANU

PIR 2

AC-DC

FANU

PIR 1

AC-DC

FANU

PIR 0

AC-DC

SV8500
server

max. 1536 physical ports

FANU

PIR 3

AC-DC

PIR: Port Interface Rack
FANU: FAN unit
BASEU: Base unit

– 20 –

Figure 1-2 Face Layout of 1-IMG System

PIR 0

PIR 3

SV8500 Server

FANU

BASEU

CPU Card #1

CPU Card #0

EMA Card

IOC Card (Option)

IOC Card (Option)

00 01 02 03 04 05 06 07 08 09 10 11 12 13 14 15 16 17 18 19 20 21 22

DC-DC PWR #0 (PWR)

DC-DC PWR #1 (DPWR)

Line / Trunk

Line / Trunk

Line / Trunk

Line / Trunk

Line / Trunk

Line / Trunk

Line / Trunk

Line / Trunk

Line / Trunk

Line / Trunk

Line / Trunk

Line / Trunk

Line / Trunk

Line / Trunk

Line / Trunk

Line / Trunk

Line / Trunk

TSW #0

TSW #1

00 01 02 03 04 05 06 07 08 09 10 11 12 13 14 15 16 17 18 19 20 21 22

DC-DC PWR #0 (PWR)

DC-DC PWR #1 (DPWR)

Line / Trunk

Line / Trunk

Line / Trunk

Line / Trunk

Line / Trunk

Line / Trunk

Line / Trunk

Line / Trunk

Line / Trunk

Line / Trunk

Line / Trunk

Line / Trunk

Line / Trunk

Line / Trunk

Line / Trunk

Line / Trunk

Line / Trunk

MUX #0

MUX #1

CHAPTER 1 General

– 21 –

CHAPTER 1 General

00 01 01 02 03 04 05 06 07 08 09 10 11 12 13 14 15

DC-DC PWR #0 (PWR)

DC-DC PWR #1 (DPWR)

DLKC #00

DLKC #01

GT #00

GT #01

TSW #00

TSW #01

TSW #02

TSW #03

TSW #10

TSW #11

TSW #12

TSW #13

PLO #0

PLO #1

TSWR

SV8500 Server

FANU

BASEU

CPU Card #1

CPU Card #0

EMA Card

IOC Card (Option)

IOC Card (Option)

Figure 1-3 Face Layout of 4-IMG System (SV8500 Server and TSWR)

– 22 –

Figure 1-4 Face Layout of 4-IMG System (IMG)

00 01 02 03 04 05 06 07 08 09 10 11 12 13 14 15 16 17 18 19 20 21 22

DC-DC PWR #0 (PWR)

DC-DC PWR #1 (DPWR)

Line / Trunk

Line / Trunk

Line / Trunk

Line / Trunk

Line / Trunk

Line / Trunk

Line / Trunk

PIR 3

PIR 2

Line / Trunk

00 01 02 03 04 05 06 07 08 09 10 11 12 13 14 15 16 17 18 19 20 21 22

DC-DC PWR #0 (PWR)

DC-DC PWR #1 (DPWR)

Line / Trunk

Line / Trunk

Line / Trunk

Line / Trunk

Line / Trunk

Line / Trunk

Line / Trunk

Line / Trunk

Line / Trunk

MUX #0

Line / Trunk

MUX #0

Line / Trunk

MUX #1

Line / Trunk

MUX #1

Line / Trunk

Line / Trunk

Line / Trunk

Line / Trunk

Line / Trunk

Line / Trunk

Line / Trunk

Line / Trunk

Line / Trunk

Line / Trunk

Line / Trunk

Line / Trunk

CHAPTER 1 General

Line / Trunk

Line / Trunk

PIR 1

PIR 0

00 01 02 03 04 05 06 07 08 09 10 11 12 13 14 15 16 17 18 19 20 21 22

DC-DC PWR #0 (PWR)

DC-DC PWR #1 (DPWR)

Line / Trunk

Line / Trunk

Line / Trunk

Line / Trunk

Line / Trunk

Line / Trunk

Line / Trunk

Line / Trunk

Line / Trunk

MUX #0

Line / Trunk

MUX #1

Line / Trunk

Line / Trunk

Line / Trunk

Line / Trunk

Line / Trunk

Line / Trunk

FANU

00 01 02 03 04 05 06 07 08 09 10 11 12 13 14 15 16 17 18 19 20 21 22

DC-DC PWR #0 (PWR)

DC-DC PWR #1 (DPWR)

Line / Trunk

Line / Trunk

Line / Trunk

Line / Trunk

Line / Trunk

Line / Trunk

Line / Trunk

Line / Trunk

Line / Trunk

MUX #0

Line / Trunk

MUX #1

Line / Trunk

Line / Trunk

Line / Trunk

Line / Trunk

Line / Trunk

Line / Trunk

BASEU

Line / Trunk

Line / Trunk

– 23 –

CHAPTER 1 General

7.2 Line Equipment Numbers (LENS)

The Line Equipment Numbers (LENS) are used to specify the location of a circuit (trunk/port) in any of
the PIR universal slots. Refer to the figures in this section, and confirm the LENS format used in the system.

As shown in Figure 1-5, the LENs consists of six digits: two digits for Module Group (MG), one digit for
Unit (U), two digits for Group (G), and one digit for Level (LV).

Figure 1-5 LENS Format

LENS = XX X XX X

Level (LV) : 0 - 7

Note:

If an FCH (PA-FCHA) card is used, Line Groups 24-31 can be used as the extended group numbers.

7.2.1 Module Group

Figure 1-6 explains the Module Group (MG). In a fully expanded system, the MG number ranges from
00 to 07.

IMG0

MG01

Group (G) : 00 - 23

Unit (U) : 0 - 3

Module Group (MG) : 00 - 07

Figure 1-6 Module Group Allocations

IMG1

MG03

IMG2

MG05

Note

IMG3

MG07

7.2.2 Unit

Figure 1-7, that represents a fully expanded system, explains the Unit (U) numbers. The numbers range
from 0 to 3, and each unit represents the PIR Universal Slot 04-12 (U 0/2) or 15-23 (U 1/3).

MG00

BASEU

MG02

BASEU

FRONT VIEW

– 24 –

MG04

BASEU

MG06

BASEU

CHAPTER 1 General

Figure 1-7 Unit Number Allocations

On each Module Group (MG: 00 - 07), a total of four Units (U0 - U3) can be assigned.

4-IMG

PIR3

PIR2

PIR1

PIR0

1-IMG

PIR3

PIR2

Slots No.

Number

of

Time Slots

IMG0

U2 U3

MG01

U1

U0

U2

U3

MG00

U1

U0

BASEU

00 02 04 05 06 07 08 09 10 11 12 13 14 15 16 17 18 19 20 21 22

PWR

PWR

(16)(16)

16 16 16 16 16 16

IMG0

TOPU

IMG1

U2 U3

MG03

U1

U0

U2

U3

MG02

U1

U0

BASEU

FRONT VIEW

Unit Number (U = 0/2) Unit Number (U = 1/3)

Control Control

IMG2

U2 U3

MG05

U1

U0

U2

U3

MG04

U1

U0

BASEU

MUX (PH-PC36) 0

MUX (PH-PC36) 1

16 16 16 16 16 16 32 3216 16 16 16 16 16 32 32 32

192 TS192 TS

U2 U3

MG01

U1

U0

IMG3

U2 U3

MG07

U1

U0

U2

U3

MG06

U1

U0

BASEU

PIR

(32)

TS : Time Slot

PIR1

PIR0

U2

U3

MG00

U0

U1

BASEU

– 25 –

7.2.3 Group

The Group (G) numbers are allocated as shown in Figure 1-8. A total of two Groups are assigned on
each universal slot within the PIR. Slots 10, 11, 12, 21, 22, 23 can contain a total of four Groups as an
exception.

Figure 1-8 Group Number Allocations

A total of two or four Groups (G) can be assigned on each PIR universal slot.

CHAPTER 1 General

4-IMG

PIR3

PIR2

PIR1

PIR0

1-IMG

PIR3

PIR2

PIR1

PIR0

IMG0

U2 U3

MG01

U0 U1

U2 U3

MG00

U0 U1

BASEU

IMG1

U2 U3

MG03

U0 U1

U2 U3

MG02

U0 U1

BASEU

IMG2

U2 U3

MG05

U1

U0

U3

U2

MG04

U1

U0

BASEU

PIR

00 02 04 05 06 07 08 09 10 11 12 13 14 15 16 17 18 19 20 21 22

MUX (PH-PC36) 0

PWR

PWR

MUX (PH-PC36) 1

FRONT VIEW

U2 U3

MG01

U0 U1

U2 U3

MG00

U0 U1

BASEU

IMG3

U2 U3

MG07

U0 U1

U2 U3

MG06

U0 U1

BASEU

G = 03

G = 02

Slot 05

16 ports total

Slot 10

G = 15

G = 14

32 ports total

G = 13

G = 12

15

11

10

14
13
12

19
18
17

16

Group No.

Slot No.

Extended
Group No.

Note

01

00(25)(24)

27 29 31
26 28 30

04 0500 02

030205040706090811

10

06 07 08 09 11 12 13 14 15 16 17 18 19 20 21 22 10

15
14
13
12

19
18
17
16

23
22
21
20

010003020504070609

08

27 29 31
26 28 30

U = 0 / 2 U = 1 / 3

Note: In addition to Group 00 - 19, the system can use 20 - 31 as theoretically valid numbers.

– 26 –

23

22
21
20

PIR

7.2.4 Level

Figure 1-9 explains the Level (LV) numbers. There are a total of eight Levels (LV 0 - LV 7) on every
Group number, that ranges from 00 to 31.

Figure 1-9 Level Number Allocations

A total of eight Levels (LV 0 - LV 7) can be assigned on each Group.

4-IMG 1-IMG

PIR3

U2 U3

PIR2

PIR1

PIR0

MG01

U0 U1

U2 U3

MG00

U0 U1

Group

(G = Odd No., < 11)

Group

(G = Even No., < 10)

IMG0

BASEU

Group No.

Level (LV)

7
6

5
4

3
2
1
0
7
6
5
4
3
2
1
0

IMG1

U2 U3

MG03

U0 U1

U2 U3

MG02

U0 U1

BASEU

FRONT VIEW

U = 0 / 2

00 02 04 05 06 07 08 09 10 11 12 13 14

0100030205040706090811

(24) (25)

2726292831

U2 U3

U0

U2

U0

15

14

13

10

12

30

16-port Slot

IMG2

MG05

U1

U3

MG04

U1

BASEU

23

19

22

18

21

17

20

16

U2 U3

MG07

U0 U1

U2 U3

MG06

U0 U1

U = 1 / 3

15 16 17 18 19 20 21 22

0100030205040706090811

2726292831

15

14

13

10

12

30

32-port Slot

IMG3

BASEU

19

18

17

16

23

22

PIR

21

20

CHAPTER 1 General

U2 U3

MG01

U1

U0

U2

U3

MG00

U1

U0

BASEU

Level (LV)

7
6
5
4
3

Group

(G = 15/19/23)

2
1
0
7
6
5
4
3

Group

(G = 14/18/22)

2
1
0

7
6
5
4
3

Group

(G = 13/17/21)

2
1
0

7
6
5
4
3

Group

(G = 12/16/20)

2
1
0

– 27 –

CHAPTER 1 General

FRONT VIEW

FRONT VIEW

4-IMG

1-IMG

PIR3

PIR2

PIR1

PIR0

FANU

BASEU

IMG0 IMG1 IMG2 IMG3

PIR3

PIR2

PIR1

PIR0

BASEU

PIR7

PIR6

PIR5

PIR4

BASEU

PIR11

PIR10

PIR9

PIR8

BASEU

PIR15

PIR14

PIR13

PIR12

FANU FANU FANU FANU

BASEU

LP = 00

LP = 00 LP = 02 LP = 04 LP = 06

7.3 Local Partition (LP) Number

The Local Partition (LP) number refers to a logical local processor number, theoretically assigned for each
IMG that consists of four (or less) Port Interface Racks (PIR). Though the local processor does not actually
exist in any of the IMGs, the system can apply the two-digit LP number to each IMG (see Figure 1-10) on
its data memory program. The LP numbers are used primarily in the following cases:

• Display of system messages

• Assignment of line load control data (ALLC command)

• Backup for Call Forwarding/Speed Calling data, etc.

Figure 1-10 LP Number Allocations

The Local Partition number (two digits, even number) is assigned as follows.

– 28 –

CHAPTER 1 General

7.4 Fault Detecting Function

The system finds a fault by its fault detecting circuit and the fault detecting program. Once a fault occurs,
the system initiates a remedial action such as system changeover, make-busy setting, or restart processing
by the automatic diagnosis function. This action reduces the influence of the fault so that system servicing
may be minimized. The result of the process taken and the fault situation are indicated for equipment
concerned.

Among the faults, those related to speech path (noise, one-way speech, speech inability, etc.) are not
detectable. Since these fault reports are obtained from a station or operator, periodic trunk tests must be
performed without failure to detect faults related to speech path.

Figure 1-11 shows an outline of fault detection. Figure 1-12 and Figure 1-13 show a block diagram of fault
detection.

Figure 1-11 Fault Detection General Diagram

Indication of
Fault Occurrence

System Messages

PCPro

printer, etc.

Indication of
Alarm Lamp
on EMA card

: Cards in SV8500 Server

ALM

Information
Collection and Diagnosis Example of Faults

Fault of line/trunk card

CPU

card

EMA

card

TSW write failure,
Fault of clocks, etc.

Abnormal temperature,
power supply failure,
fuse blowing, etc., within
the equipment frame

– 29 –

Figure 1-12 Block Diagram of Fault Detection (1-IMG)

CHAPTER 1 General

- Symbols -

PCPro

Printer, etc.

(Note)

Fault Information:
MJ, MN faults
Power OFF, blown fuse
CPU faults
Speech Path faults
RGU, Howler faults
CPU Clock faults

SYMBOL MEANING SYMBOL MEANING

: Circuit Card in PIR/TSWR
: Card in SV8500 Server
: Faults to be detected
: Speech Path
: Fault Information flow

(IOC)

Software abnormal

behavior monitor

CPU

Fault

Information

EXB

Ready
Clock

Ready
Clock

MUX

TSW

(Note)

EMA

CPU Central Processing Unit EXB GT card

EMA Emergency Alarm Controller PWR Power Supply

Firmware
faults

Howler,
Ringer fault

Howler,
Ringer fault

LC/TRK

PWR

PWR

Power off,
blown fuse

IOC I/O Controller TSW Time Division Switch

LC/TRK Line/Trunk MUX Multiplexer

– 30 –

Figure 1-13 Fault Detection Block Diagram (4-IMG)

CHAPTER 1 General

Firmware
faults

- Symbols -

PCPro

printer, etc.

(Note)

Fault Information:
MJ, MN faults
Power OFF, blown fuse
CPU faults
Speech Path faults
RGU, Howler faults
CPU Clock faults

: Circuit Card in PIR/TSWR
: Card in SV8500 Server
: Faults to be detected
: Speech Path
: Fault Information flow

(IOC)

Software abnormal

behavior monitor

CPU

Fault

Information

(Note)

EXB

EMA

Ready
Clock

MUX

TSW

GT

Ready
Clock

Ready
Clock

LC/TRK

PWR

TSWR

PWR

PLO

Power off,
blown fuse

SYMBOL MEANING SYMBOL MEANING

CPU Central Processing Unit PWR Power Supply

EMA Emergency Alarm Controller DLKC Data Link Controller

IOC I/O Controller TSW Time Division Switch
LC/TRK Line/Trunk MUX Multiplexer
GT/EXB Gate card TSWM Time Division Switch Module

(a) Main Faults

Faults that may occur in the system can be generally categorized into Processor System Fault, Speech
Path System Fault, Line/Trunk Fault, etc.

• Processor System Fault

The CPU alarm detecting circuit continuously monitors whether the CPU is working normally. If a
fault is detected, the CPU calls up the diagnostic program, that identifies the cause of the fault and
determines whether the fault is temporary or permanent. When the fault affects system operations,
Active/Standby status of the CPU is changed over (provided that the system has dual configuration).

• Bus System Fault

– 31 –

CHAPTER 1 General

The CPU transfers line/trunk card control information to the associated peripheral circuits via IO
Bus. When a party error is detected in the transfer data or when the required information cannot be
transferred from a circuit card, the CPU identifies the cause of the fault, changes over the CPU so
that system operation is not affected, and executes restart processing.

• Speech Path Fault

The CPU monitors the operating status of the TSW card, the occurrence of errors in writing data to
the switch memory, and the basic clocks supplied to the speech path. Upon detecting a fault, the
CPU identifies the cause of the fault, determines whether the fault is temporary or permanent, and
executes required processing such as changeover of the TSW card.

•Others

The alarm detecting circuit on the EMA card continuously monitors the occurrence of faults in the
PWR supply cards, such as abnormal status within the equipment frame, and lights the alarm lamp
on the front when a fault is detected.

(b) Lamp Indications on the Front Cover

When a fault occurs, the corresponding lamp on the front of EMA card indicates the location of the
fault.

– 32 –

CHAPTER 1 General

7.5 Range of Faults Specification

(1) Upon receiving a fault report from a station user or an operator, the technician can assume a faulty card

exists if the range affected by the fault can be determined. For the detailed procedure, refer to Chapter 6.
Use the following actions to check the MDF:

(a) Check the LENS of the reporter (Station or ATTCON/DESKCON).
(b) Check other circuits of the circuit card in which the reporter (station line or ATTCON/DESKCON) is

located.

(c) Check the other groups (other circuit cards mounted in the same module) in the module in which the

reporter is located.

(d) Check lines in each of the other modules on the basis of multiple lines.

(2) If the fault cannot be detected by the system (a fault related to the speech path such as noise during speech,

one-way speech, speech inability), the range of (a) through (d) (itemized above) should be limited.

(3) When a major fault is detected in the dual systems, the CPU or TSW system automatically changes over if

the fault range is (c) and (d). In this case, the whole module involved is placed into make-busy status even
if the fault is partial, and the station lines currently operating normally become faulty status. Diagnose the
fault from the content of the system message displayed and repair the fault as required.

(4) To narrow down the range of faults, consider the system circuitry that consists of the control (see Figures

1-17 and Figure 1-18, where CPU 0 is active) and speech path systems (see Figure 1-14 and Figure 1-19).

(5) As seen from the block diagrams in Figure 1-14 through Figure 1-19, if a fault that affects the common

portions occurs, all other associated portions will be affected by this fault. When CPU and TSW are pro­vided in dual configuration, they will be automatically changed over as far as the fault is detectable by the
system.

– 33 –

Figure 1-14 General System Block Diagram (1-IMG)

CHAPTER 1 General

PIR3

PIR2

PIR1

PIR0

TSW

MUX INT

EXB INT

Local I/O BUS

MUX

MUX

MUX

MUX

PM Bus

LC/TRK LC/TRK

PM Bus

LC/TRK LC/TRK

PM Bus

LC/TRK LC/TRK

PM Bus

LC/TRK LC/TRK

BUS0 BUS1

MUX

MUX

MUX

MUX

MUX INT

Local I/O BUS

TSW

EXB INT

SV8500 Server

EXB0

CPU0 CPU1

EMA

IOC

(option)

IOC

(option)

PCI-Ex bus
(PCI Express)

TSW : PH-SW10-A, etc.
MUX : PH-PC36

03/29/02

: Circuit Card

: CPU Control Routes

EXB1

PCI-Ex bus
(PCI Express)

: Signal
: Cable

– 34 –

PIR 3

PIR 2

PIR 1

PIR 0

Figure 1-15 Speech Path Block Diagram (1-IMG)

MUX

LC/TRK LC/TRK LC/TRK

MUX

LC/TRK LC/TRK LC/TRK

MUX

LC/TRK LC/TRK LC/TRK

MUX

MUX

MUX

CHAPTER 1 General

TSW

[Symbols]

: Speech Path
: Circuit Card (ACT)

TSW

MUX

LC/TRK LC/TRK LC/TRK

: Cable
: Circuit Card (STBY)

MUX

TSW

TSW

TSW : PH-SW10-A, etc.
MUX : PH-PC36

– 35 –

Figure 1-16 Range of Speech Path Fault (1-IMG)

Faults within this range affects
these two slots.

CHAPTER 1 General

PIR 3

PIR 2

PIR 1

LC/TRK

LC/TRK

Fault within this range
affects this circuit card.

LC/TRK

LC/TRK

Fault within this range
affects this circuit card.

LC/TRK

LC/TRK

Fault within this range
affects this circuit card.

32ch

MUX

Faults within this range affects
these two slots.

32ch

MUX

Faults within this range affects
these two slots.

32ch

MUX

Faults within this range affects
this module.

512ch

Faults within this range affects
this module.

512ch

Faults within this range affects
this module.

512ch

PIR 0

[Symbols]

Faults within this range affects
these two slots.

LC/TRK

LC/TRK

Fault within this range
affects this circuit card.

: Circuit Card :range that can be affected by this fault : Speech Path

32ch

TSW

MUX/INT

Faults within this range affects
the whole system.

– 36 –

Figure 1-17 CPU Controlling Block Diagram (4-IMG)

CHAPTER 1 General

PIR 3

PIR 2

PIR 1

PIR 0

MUX

MUX

MUX

MUX

IMG0

LC/TRK

LC/TRK

LC/TRK

LC/TRK

PM BUS

PM BUS

PM BUS

PM BUS

PM BUS

PM BUS

PM BUS

PM BUS

LC/TRK

LC/TRK

LC/TRK

LC/TRK

MUX

MUX

MUX

MUX

PIR 3

PIR 2

PIR 1

PIR 0

MUX

MUX

MUX

MUX

IMG1

LC/TRK

LC/TRK

LC/TRK

LC/TRK

PM BUS

PM BUS

PM BUS

PM BUS

PM BUS

PM BUS

PM BUS

PM BUS

LC/TRK

MUX

LC/TRK

MUX

LC/TRK

MUX

LC/TRK

MUX

To IMG 2To IMG 3 To IMG 3To IMG 2

SV8500 Server

(Note 3)

Note 1:

PCI-Ex bus

(PCI Express)

TSWR

CPU Board 0 CPU Board 1

M

M

M

M

U

U

U

U

X

X

X

X

003

002

001

000

MUX/INT MUX/INT MUX/INTMUX/INT

TSW 00 TSW 10 TSW 11TSW 01

DLKC BUS

(option)

IOC

(option)

IOC

EMA

EXB0

BUS0

GT 0

PCI-Ex bus

(PCI Express)

EXB1

GT 1

BUS1

GT :PH-GT09
TSW :PH-SW12
DLKC:PH-PC20
PLO :PH-CK16-D
MUX :PH-PC36

[Symbols]

Circuit cards shown in dotted line are in STBY mode.

M
U
X

013

Local I/O

DLKC 0

DLKC BUS

MUX

BUS

/INT

TSW
02

Local I/O BUS

MUX
/INT

TSW
03

M

M

M

M

M

M

M

U

U

U

U

X

X

X

X

100

101

102

103

U
X

110

Local I/O

DLKC BUS

DLKC 1

DLKC 1

DLKC BUS

M

U

U

U

X

X

X

111

112

113

M

M

M

U

U

U

X

X

X

012

011

010

PLO 0 PLO 1

Local I/O BUS

: CPU Controlling Routes : Cable
: Circuit Card (ACT) : Circuit Card (STBY)
: External Cable : Clock Oscillator
: Signal

Note 2: When the CPU ACT/STBY is changed over, GT will also be changed over in TSWR.

Note 3: IOC card is option.

BUS

MUX

MUX

/INT

/INT

TSW

TSW

13

12

– 37 –

Figure 1-18 Speech Path Block Diagram (4-IMG) (1 of 2)

CHAPTER 1 General

PIR3

PIR 2

PIR 1

PIR 0

MUX

MUX

MUX

MUX

LC/TRK

LC/TRK

LC/TRK

LC/TRK

IMG0

LC/TRK LC/TRK

LC/TRK LC/TRK

LC/TRK LC/TRK

LC/TRK LC/TRK

MUX

MUX

MUX

MUX

PIR 3

PIR 2

PIR 1

PIR 0

MUX

MUX

MUX

MUX

LC/TRK

LC/TRK

LC/TRK

LC/TRK

IMG1

MUX

LC/TRK LC/TRK

MUX

LC/TRK LC/TRK

MUX

LC/TRK LC/TRK

MUX

LC/TRK LC/TRK

TSWR

[Symbols]

㩷㩷㩷㩷㩷㩷㩷㩷㩷: Speech Path
㩷㩷㩷㩷㩷㩷㩷㩷㩷: Circuit Card (ACT)

TSW 00

MUX 003
MUX 002

MUX 001
MUX 000

MUX/INT

TSW 10

MUX 100
MUX 101

MUX 102
MUX 103

MUX/INT

: External Cable
: Circuit Card (STBY)

TSW 01

MUX 013
MUX 012

MUX 011
MUX 010

MUX/INT

TSW 11

MUX 110
MUX 111

MUX 112
MUX 113

MUX/INT

TSW: PH-SW12
MUX: PH-PC36

To IMG2

MUX/

INT

TSW

02

To IMG2

MUX/

INT

TSW

12

To IMG3

MUX/

INT

TSW

03

To IMG3

MUX/

INT

TSW

13

– 38 –

Figure 1-18 Speech Path Block Diagram (4-IMG) (2 of 2)

CHAPTER 1 General

PIR 3

PIR 2

PIR 1

PIR 0

MUX

MUX

MUX

MUX

LC/TRK

LC/TRK

LC/TRK

LC/TRK

IMG2

LC/TRK LC/TRK

LC/TRK LC/TRK

LC/TRK LC/TRK

LC/TRK LC/TRK

MUX

MUX

MUX

MUX

PIR 3

PIR2

PIR1

PIR 0

MUX

MUX

MUX

MUX

LC/TRK

LC/TRK

LC/TRK

LC/TRK

IMG3

MUX

LC/TRK LC/TRK

MUX

LC/TRK LC/TRK

MUX

LC/TRK LC/TRK

MUX

LC/TRK LC/TRK

[Symbols]

㩷㩷㩷㩷㩷㩷㩷㩷㩷: Speech Path
㩷㩷㩷㩷㩷㩷㩷㩷㩷: Circuit Card (ACT)

TSWR

TSW 02

MUX 023
MUX 022

MUX 021
MUX 020

MUX/INT

TSW 12

MUX 120
MUX 121

MUX 122
MUX 123

MUX/INT

: External Cable
: Circuit Card (STBY)

TSW 03

MUX 033
MUX 032

MUX 031
MUX 030

MUX/INT

TSW 13

MUX 130
MUX 131

MUX 132
MUX 133

MUX/INT

TSW: PH-SW12
MUX: PH-PC36

To IMG0

MUX/

INT

TSW

00

To IMG0

MUX/

INT

TSW

10

To IMG1

MUX/

INT

TSW

01

To IMG1

MUX/

INT

TSW

11

– 39 –

Figure 1-19 Range of Speech Path Fault (4-IMG)

Faults within this range affects
these two slots.

CHAPTER 1 General

PIR 3

PIR 2

PIR 1

LC/TRK

LC/TRK

Fault within this range
affects this circuit card.

LC/TRK

LC/TRK

Fault within this range
affects this circuit card.

LC/TRK

LC/TRK

32ch

MUX

Faults within this range affects
these two slots.

32ch

MUX

Faults within this range affects
these two slots.

32ch

MUX

Faults within this range affects
this module.

512ch

Faults within this range affects
this module.

512ch

Faults within this range affects
this module.

512ch

PIR 0

[Symbols]

Fault within this range
affects this circuit card.

Faults within this range affects
these two slots.

LC/TRK

LC/TRK

Fault within this range
affects this circuit card.

: Circuit Card :range that can be affected by this fault : Speech Path

32ch

TSW

MUX

MUX/INT

Faults within this range affects
the whole system.

512ch

– 40 –

CHAPTER 2 Operations of SV8500 Server

This chapter covers the following topics in this order:

• 1. HOW TO SET THE CURRENT DATE AND TIME

• 2. ALARM INDICATIONS

• 3. INITIALIZATION PROCEDURE OF THE SYSTEM

• 4. ROUTINE DIAGNOSIS

• 5. OFFICE DATA MAINTENANCE

• 6. UNIT/CIRCUIT CARD REPLACEMENT PROCEDURE

• 7. FAN REPLACEMENT PROCEDURE

• 8. SYSTEM CONTROL PROCEDURES

• 9. TRAFFIC MANAGEMENT

• 10. STATION MESSAGE DETAIL RECORDING SYSTEM (SMDR)

• 11. REDUNDANT DATA MEMORY BACKUP FOR OFFICE DATA

CHAPTER 2 Operations of SV8500 Server

• 12. RTP INFORMATION OUTPUT

• 13. DTERM IP CALL INFORMATION DISPLAY

• 14. IP DEVICE PC PORT REMOTE CONTROL

• 15. LICENSE REGISTRATION INFORMATION DISPLAY

• 16. FTP SERVER SUPPORT (LAN1)

– 41 –

CHAPTER 2 Operations of SV8500 Server

㪥㪦㪅 㪪㪥㪫㪧㩷㪪㪜㪩㪭㪜㪩 㪚㪦㪤㪤㪘㪥㪛 㪜㪯㪧㪣㪘㪥㪘㪫㪠㪦㪥

1. HOW TO SET THE CURRENT DATE AND TIME

1.1 General

System clock can be manually or automatically adjusted as shown below. For automatic adjustment, an SNTP
server is required.

㪈 㫅㫆㫋㩷㫌㫊㪼㪻 㪘㪫㪠㪤㪆㪘㪫㪠㪤㪥

㪉 㫌㫊㪼㪻 㪘㪥㪫㪧㪣

Figure 2-1 How to Set the Current Date and Time

㪙㫐㩷㫇㫉㪼㫊㫊㫀㫅㪾㩷㫋㪿㪼㩷 㵰㪪㪼㫋㵱㩷㪹㫌㫋㫋㫆㫅㩷㫆㫅㩷㫋㪿㫀㫊㩷㪺㫆㫄㫄㪸㫅㪻㪃㩷㫋㪿㪼㩷㫊㫇㪼㪺㫀㪽㫀㪼㪻㩷㪻㪸㫋㪼㩷㪸㫅㪻㩷
㫋㫀㫄㪼㩷㪸㫉㪼㩷㪸㫇㫇㫃㫀㪼㪻㩷㫋㫆㩷㫋㪿㪼㩷㫊㫐㫊㫋㪼㫄㪅

㪙㫐㩷㫊㫇㪼㪺㫀㪽㫐㫀㫅㪾㩷㪸㫅㩷㪪㪥㪫㪧㩷㫊㪼㫉㫍㪼㫉㩷㫎㫀㫋㪿㩷㫊㫋㪸㫉㫋㩷㫋㫀㫄㪼㩷㫋㫆㩷㫆㪹㫋㪸㫀㫅㩷㫋㫀㫄㪼㩷㫀㫅㪽㫆㫉㫄㪸㫋㫀㫆㫅㩷
㪽㫉㫆㫄㩷㫋㪿㪼㩷㫊㪼㫉㫍㪼㫉㪃㩷㫋㫀㫄㪼㩷㪸㪻㫁㫌㫊㫋㫄㪼㫅㫋㩷㫎㫀㫃㫃㩷㪹㪼㩷㪸㫌㫋㫆㫄㪸㫋㫀㪺㪸㫃㫃㫐㩷㫇㪼㫉㪽㫆㫉㫄㪼㪻㩷㫆㫅㩷㪸㩷㪻㪸㫀㫃㫐㩷
㪹㪸㫊㫀㫊㪅

ATIM/ATIMN

PCPro

manual adjustment automatic adjustment

SV8500 server

time-synchronization

1.2 Programming to Specify How to Set Date and Time

(1) When Not Using SNTP Server

STEP 1 ATIM/ATIMN

Date, Time, and Day Light Savings (Start/End) can be specified on this command. By pressing the “Set”

button on the command, the specified Date and Time will be applied to the system that is in operation.

(2) When Using SNTP Server

ANTPL

SNTP server

STEP 1 ATIM

When using Day Light Savings, set the data by using ATIM command.

STEP 2 ANTPL (SNTP Setting)

By this command, set time for time-synchronization (SNTP) service as well as an SNTP server by us­ing the domain name or IP address. Time adjustment will be automatically performed on a daily basis.
IP Address of the DNS Server must be set using the ADTM command when SNTP server is specified
the domain name.

– 42 –

CHAPTER 2 Operations of SV8500 Server

Note: For the details, refer to UNIVERGE SV8500 Data Programming Manual - Business.

Note: Activation of time-synchronization (SNTP) service is limited to once a day. Thus, if ANTPL command is

used to change the start time for SNTP service after SNTP service is already active for that day, the
change takes effect from the following day. Activate the SNTP service manually by pressing the Execute
button when immediate time adjustment is needed.

Example:

1) Existing start time for SNTP service is 01:00.

2) At 03:00, ANTPL command is used to change the start time from 01:00 to 05:00.

3) The next start time for SNTP service is 05:00 on the next day.

1.3 How to Adjust Date and Time

When the system is rebooted, the clock information will also be reset. Adjust the date and time by one of
the following procedures after system reboot.

(1) When Not Using SNTP Server

STEP 1 Execute ATIM/ATIMN command.

STEP 2 Set the current date and time.

STEP 3 Click on “Set” button to apply the date and time.

(2) When Using SNTP Server

STEP 1 Execute ANTPL command.

STEP 2 Click on “Execute” button to synchronize the date and time of the specified SNTP server.

– 43 –

CHAPTER 2 Operations of SV8500 Server

2. ALARM INDICATIONS

If trouble occurs in the system, the system activates an appropriate remedial action such as system changeover,
make-busy of the circuit card, restart processing by executing the automatic diagnostic function. Results of the
action taken and the faulty situation are displayed by the alarm indication and system message (s). This section
describes the alarm indication. For the system messages, refer to Chapter 3.

2.1 Kinds of Alarm Indications

The system will alert the maintenance personnel of any failure occurred in the system by the following in­dications.

(a) Alarm Lamps

• Front panel

• Each circuit card

• Each peripheral equipment

(b) System Messages

• Displayed on the PCPro

2.2 How to Stop Alarm Indications

To stop the alarm indication after the failure is solved, do the following.

STEP 1 Execute DFTD command from PCPro to collect the recorded system messages.

STEP 2 Execute the RALM command from PCPro.

Note:

When RALM is executed, all system messages will be cleared. Be sure to collect the system messages

Note

before using RALM.

– 44 –

CHAPTER 2 Operations of SV8500 Server

PWR

SYS
ALM

SYS 1

MB

(SUB)

SYS
LOCK

SYS
SEL

PFT

LINK OPE

ALM

INIT

PBI No.

SYS 0

12 12

SWO0 SWO1

LINE SPEED

LINE SPEED

3

4

LINE SPEED

LINE SPEED

1

2

LINE SPEED

LINE SPEED

3

4

LINE SPEED

LINE SPEED

1

2

ON

LINE

LOAD

PWR

ON

LINE

LOAD

PWR

PWR

SYS
ALM

SYS 1

MB

(SUB)

SYS

LOCK

SYS
SEL

1

0

PFT

LINK ACT

ALM

INIT

PBI No.

SYS 0

12 12

SW00 SW01

ON

SYS ALM lamp

ALM lamp (SYS1: used for CPU #1)

ALM lamp (SYS0: used for CPU #0)

EMA Card

2.3 Alarm Indications

The system has alarm lamps on EMA card as shown below. The table below lists the meaning of each lamp.

Alarm Indications on EMA card

SYS ALM lamp

ALM lamp

NAME COLOR DESCRIPTION REMARKS

Flashes in 1-second cycle.

Red

Lights.

MN (minor) alarm: One of the system cooling
fans is faulty, etc.

MJ (major) alarm: Two or more system cooling
fans are faulty, etc.

OFF No failure is detected.

Lights when failure occurs on software operation in CPU #0
(software operation failure during the system is operating).

SYS0

Red

Flashes when failure occurs on software operation in CPU #0
(software operation failure on starting up the system).

OFF No failure is detected.

Lights when failure occurs on software operation in CPU #1

SYS1

Red

(software operation failure during the system is operating).

Flashes when failure occurs on software operation in CPU #1
(software operation failure on starting up the system).

OFF No alarm is detected.

– 45 –

CHAPTER 2 Operations of SV8500 Server

2.4 Variable Alarm Indication

This allows users to make a flexible change of system message output grades that range 0 to 3 and alarm
lamp grades that consist of MJ, MN, SUP and NONE. The maintenance personnel can give a proper alarm
grade to each system message according to their requirements. When assigning no data, the default alarm
grades are automatically applied.

Note 1: The alarm grade of System Message [6-A] cannot be changed.

Note 2: Use LLMG (Listup of Alarm Grade Data) command TYPE=3 to output the default value of alarm lamp

grade for system message.

COMMAND COMMAND FULL NAME

ALMG Assignment of Alarm Grade Data

ASYD SYS1 INDEX 91 b2 and b3

Figure 2-1 Variable Alarm Indication Data Assignment

Assign the following data for modifying the default alarm grade.

START

ALMG

ASYD

END

: Assign output grade and alarm lamp grade on a system message basis.

FK: Fault Message Kind (0-7, 10-17, 20-27, 30-37)
FI: Fault Message Index (A-Z)
LMP: Alarm Lamp Grade (0-3)
GRD: Output Grade (0-3)

SYSM GRD: System Alarm Lamp Output Grade (0-3) Note

Note: Indicates the setting status of output grade for System Alarm Lamp and System Message,

which can be assigned by ASYD, SYS1, INDEX 91, b2 and b3.

: Assign the output grade of System Alarm Lamp and System Message on a node basis.

SYS1, INDEX 91, b2 and b3

b2

b3

0 = Output all fault

0

1 = Output the fault higher than Grade 1 (SUP/MN/MJ)

0

0 = Output the fault higher than Grade 2 (MN/MJ)

1
1

1 = Output the fault higher than Grade 3 (MJ)

– 46 –

CHAPTER 2 Operations of SV8500 Server

3. INITIALIZATION PROCEDURE OF THE SYSTEM

3.1 General

This section explains how to initialize the system. The following can be used:

• PCPro (SINZ)

• PCPro Tools (System Control - System Reboot)

• By INIT key Operation on EMA card

• By Turning OFF/ON the System

WARNING

When the system is initialized, all calls in progress will be disconnected.

System initialization can be roughly divided to “Non Load Initial” and “Load Initial.” The former reboots the
system using the program and office data that are currently loaded in the memory. On the other hand, the latter
loads the office data (and program) into the memory before rebooting the system. After loading the data into the
memory, system initialization will take place. Available initialization types vary depending on type of
operations.

Non Load Initial Load Initial

MEM

- Office Data

- Program

Initialization

CF Card

- Office Data

- Program

load

MEM

- Office Data

- Program

Initialization

– 47 –

CHAPTER 2 Operations of SV8500 Server

The relationship of operation types and Initialization types is as follows.

Relationship between Initialization Types and Available Operations

X: Available -: Not Available

Available Operations

Initialization Type

Non Load Initial X - X -

Office Data Load Initial X - - ­Office Data Load & Program Load Initial X - - -

Office Data Load & Program Load (& OS Load) Initial X X - X

Load Initial

Figure 2-2 Office Data Load and Program Load

PCPro
(SINZ)

PCPro

Too ls

INIT key Operation

(EMA card)

Tuning Off/On

CF Card

Program

(Main Memory)

- Basic Software

- Service Software

- IMAT Software

- TCP/IP Software

Office Data

- Data Memory

- Call Forwarding Data

- Speed Calling Data

- Name Display Data
etc.

3.2 Initialization by PCPro (SINZ)

All initialization types shown below are available.

• Non Load Initial

• Office Data Load Initial

• Office Data Load & Program Load Initial

• Office Data Load & Program Load (& OS Load) Initial

Note:

Use shutdown option on SINZ command.

Program Loading

Office Data Loading

Note

MEM

- Program

- Office Data

Initialization

STEP 1 Execute SINZ from the PCPro.

STEP 2 Select an appropriate initialization type, and then click “Execute” button.

• Initialization starts.

• PCPro is automatically placed in logout state.

– 48 –

CHAPTER 2 Operations of SV8500 Server

Note: For the detail, refer to SINZ on page 906 in this manual.

STEP 3 Make sure that the SYS ALM lamp (red) lights on the EMA card.

STEP 4 Log into the system again from the PCPro.

STEP 5 Set the current date and time from the PCPro. (Refer to How to Adjust Date and Time.)

STEP 6 Release the indicated alarm. (Refer to How to Stop Alarm Indications.)

– 49 –

CHAPTER 2 Operations of SV8500 Server

3.3 Initialization by PCPro Tools

The following initialization type is available.

• Office Data Load & Program Load (& OS Load) Initial

STEP 1 Run PCPro Tools on a PC.

STEP 2 Select “System Control” and then click “Execute” button.

STEP 3 Select “System Reboot” from the list box, and then click “Execute” button.

• Initialization starts.

• PCPro is automatically placed in logout state.

Note: For the detail, refer to “UNIVERGE SV8500 Command Manual“.

STEP 4 Make sure that the following lamps light green on the EMA card.

Lamp name Status

PWR Lights green

LINK Lights green

ACT Lights green

STEP 5 Log into the system again from the PCPro.

STEP 6 Set the current date and time from the PCPro. (Refer to How to Adjust Date and Time.)

STEP 7 Release the indicated alarm. (Refer to How to Stop Alarm Indications.)

– 50 –

CHAPTER 2 Operations of SV8500 Server

PWR

SYS
ALM

SYS 1

MB

(SUB)

SYS

LOCK

SYS

SEL

PFT

LINK ACT ALM

INIT

PBI No.

SYS 0

12 12

SW00

SW01

ON

0

1

3.4 Initialization by INIT key Operation (EMA card)

The following initialization type is available.

• Non Load Initial
All on-going calls will be disconnected. The system will be rebooted by using program and office data that

are in the MEM.

[MEM]

- Program

Initialization

- Office Data

STEP 1 Identify which system of CPU is in operation. The following shows an example when the system

is operating by CPU #0.

Lamp Layout on EMA Card (when CPU #0 is active) Lamp (Color) Status

PWR (Green) On

SYS ALM (Red) Off
LINK (Green) On

ACT (Green) On

ALM (Red) Off

STEP 2 Press “INIT” key on the EMA card to start Non Load Initial.

SYS

PWR

SYS
ALM

LINK ACT ALM

SYS 1

SYS 0

MB

(SUB)

SYS

LOCK

PFT

ON

12 12

SW00

SW01

SEL

INIT

1

0

PBI No.

INIT key

STEP 3 Check the lamp indications on the EMA card.

Lamp (Color) Status

PWR (Green) On

LINK (Green) On

ACT (Green) On

SYS ALM (Red) On

STEP 4 Set the current date and time from the PCPro. (Refer to How to Adjust Date and Time.)

STEP 5 Release the indicated alarm. (Refer to How to Stop Alarm Indications.)

– 51 –

CHAPTER 2 Operations of SV8500 Server

3.5 Initialization by Turning OFF and ON the System

This section explains how to start up the system that has been shut down for some reason. If the system
cannot be initialized by the SINZ/PCPro Tools/INIT key, shut down the system and restart the system by
this procedure. Available initialization type is as follows:

• Office Data Load & Program Load (& OS Load) Initial

3.5.1 How to Start Up the System by Turning OFF/ON

This procedure assumes that the system has been shut down for some reason.

STEP 1 Turn off the power of the system referring to Chapter 5 How to Turn ON/OFF Whole System.

STEP 2 Turn on the power again referring to Chapter 5 How to Turn ON/OFF Whole System.

STEP 3 Make sure that the system is in normal operation.

Lamp (Color) Status

PWR (Green) On

LINK (Green) On

ACT (Green) On

ALM (Red) On

STEP 4 Set the current date and time from the PCPro. (Refer to How to Adjust Date and Time.)

STEP 5 Release the indicated alarm. (Refer to How to Stop Alarm Indications.)

– 52 –

CHAPTER 2 Operations of SV8500 Server

4. ROUTINE DIAGNOSIS

For confirming its own servicing status, the system automatically executes self diagnosis every day, and
displays the result of the diagnosis as a system message. By this function, possible causes for trouble can be
discovered in an early stage and possible trouble can be prevented from remaining undetected.

4.1 Related System Data

• ASYD, SYS1, INDEX86,
b0 – When routine diagnosis starts, and the result of the routine diagnosis is normal, the result

displays as System Message [

7-O].

0/1: Not displayed/Displayed

b1 – When the result of the routine diagnosis is abnormal, it displays as System Message [

7-P].

0/1: Not displayed/To display

b3, b2 – Processing at the time when Trunk Ineffective Hold is detected. Note 1

BIT

b3 b2

00 X — X

01 — — X

10 — X X

Note 1: Trunk Ineffective Hold is a continuous state other than idle state within a predetermined duration while

The trunks being held at present are forcibly
released, except the trunks being held on two­way calls (station-to-station call, station-to­trunk, external trunk-to-external trunk call).

All trunks being held at
the present are forcibly
released

LENS of the trunk detected
display as System Message
[7-P]

routine diagnosis is in progress. Whether it is detected/not detected, it is assigned by ASYD, SYS1, IN­DEX 89.

Note 2: When Trunk Ineffective Hold on the FCCS Network is detected, setting of ASYD, SYS1, INDEX 86,

b2·b3 and SYS1, INDEX 89, b4·b5 must be the same at all nodes on the network.

• SYS1, INDEX 87, 88 - Routine Diagnosis Start Time
Start time should be such a time which the traffic of the office is the lowest.

INDEX 87 0 2 (Hour) 2:00 a.m. is the start time.
INDEX 88 0 0 (Minute)

To stop the routine diagnosis, set FF respectively to INDEX87, 88.

– 53 –