Igate 400 Maintenance Manual

fJd~íÉ=QMMM=badb=
pt=sÉêK=h~äóéëç=RKNKN=
mìÄK=sÉêK=MN=
=
j~áåíÉå~åÅÉ=j~åì~ä=
This product is marked with a CE Mark. This mark has been affixed to demonstrate full product
compliance with the following European directives:
a) Directive 73/23/EEC - Council Directive of 19/02/1973 on the harmonization of the laws of
Member States relating to electrical equipment designed for use within certain voltage limits.
b) Directive 89/336/EEC - Council Directive of 3/05/1989 on the approximation of laws of the
Member States relating to Electro-Magnetic Compatibility (EMC).
Issue Date: February 6, 1996
This product is marked with a TUV Mark. This mark has been affixed to demonstrate full product
compliance with UL60950 for US and Canada.
This product is marked with a GS Mark. This mark has been affixed to demonstrate full product
compliance with German Safety Requirements.
This product is compliant with IEC60950 with all countries deviations, according to the CB scheme.
CB
Japan The product complies with Japan requirements per VCCI V-3/2001.04
Australia The product complies with Australian requirements per AS/NZS CISPR 22:04
Germany The product complies with Deutche Telecom requirements per FTZ1TR9
US Complies with US requirements FCC part 15

Revision record: I-Gate 4000 EDGE Maintenance
Dwg. Pub. Date Update Description
Rev. Rev.
A01 01 Apr-06 Ver. Kalypso 5.1.1. Author: JH

Publication No. 05050303
Dwg. No. 480206-1000-103-95-A01
®
Veraz is a registered trademark of VERAZ NETWORKS INC., 2006. All rights reserved worldwide.
The information contained in this document is proprietary and is subject to all relevant copyright, patent and other
laws protecting intellectual property, as well as any specific agreement protecting VERAZ NETWORKS INC.'s
rights in the aforesaid information. Neither this document nor the information contained herein may be published,
reproduced or disclosed to third parties, in whole or in part, without the express, prior, written permission of VERAZ
NETWORKS INC. In addition, any use of this document or the information contained herein for any purposes other
than those for which it was disclosed is strictly forbidden.
Any representation(s) in this document concerning performance of VERAZ NETWORKS INC.'s product(s) are for
informational purposes only and are not warranties of future performance, either express or implied. VERAZ
NETWORKS INC.'s standard limited warranty, stated in its sales contract or order confirmation form, is the only
warranty offered by VERAZ NETWORKS INC. in relation thereto.
VERAZ NETWORKS INC. reserves the right, without prior notice or liability, to make changes in equipment design
or specifications. This document may contain flaws, inaccuracies, omissions or typesetting errors; no warranty is
granted nor liability assumed in relation thereto, nor responsibilities for third-party rights which may be affected in
any way by the use thereof, unless specifically undertaken in VERAZ NETWORKS INC.'s sales contract or order
confirmation. Information contained herein is periodically updated and changes will be incorporated into
subsequent editions. If you have encountered an error, please notify VERAZ NETWORKS INC.
Direct any comments or questions to Veraz Customer Service at Service@Veraznetworks.com.
I-Gate 4000 EDGE Maintenance Manual Contents
Contents
1 Introduction .............................................................................................. 1-1
1.1. Purpose of this Manual ....................................................................... 1-1
1.2. Intended Audience .............................................................................. 1-1
1.3. Referenced Documentation................................................................. 1-1
2 Safety Precautions ................................................................................... 2-1

2.1. Handling Precautions .......................................................................... 2-1
2.1.1. Handling Printed Circuit Boards (modules) .......................... 2-2
2.1.2. Service Tool Precautions...................................................... 2-2
2.2. Safety Instructions............................................................................... 2-3
2.3. Power Precautions .............................................................................. 2-4
2.3.1. Applicable to DC powered terminals only............................. 2-4
2.3.2. Applicable to AC and DC powered terminals ....................... 2-4
2.4. BPSM/XPSM Card Battery Replacement............................................ 2-5
2.5. Electrostatic Discharge (ESD) Precautions......................................... 2-7
2.6. Radio Interference Precautions........................................................... 2-8
3 Repair and Return Procedure ................................................................. 3-1

3.1. Ordering Replacement Equipment ...................................................... 3-2
3.2. Insurance Policy .................................................................................. 3-4
3.3. Substitutions and Modifications........................................................... 3-4
3.4. Limitations of Liability .......................................................................... 3-4
3.5. Shipping Information ........................................................................... 3-5
3.6. Technical Assistance Centers (TACs)................................................. 3-6
3.7. Terminal Malfunction Check................................................................ 3-6
4 Replacing Modules................................................................................... 4-1

4.1. Extracting the Modules........................................................................ 4-3
4.2. Inserting the Modules .......................................................................... 4-4
05050303-01 Veraz Networks Inc. Proprietary i

Contents I - G a t e 4 0 0 0 E DG E M a i n t e n a n c e M a n u a l
5 Module Redundancy ............................................................................. 5-1

5.1. VerazView-xMS Hardware View ......................................................... 5-2
5.1.1. Hardware View window displays .......................................... 5-3
5.1.2. Hardware View right-click Menu options .............................. 5-3
5.2. License Verification ............................................................................. 5-5
5.3. Module Changeover Operations ......................................................... 5-6
5.4. Maintenance Procedures after Automatic Changeover....................... 5-7
5.4.1. XPSM Redundancy .............................................................. 5-8
5.4.2. BPSM Redundancy ............................................................ 5-12
5.4.3. Input Power Source Redundancy....................................... 5-16
6 System and Network Alarms................................................................... 6-1

6.1. Alarm Handling.................................................................................... 6-2
6.1.1. Alarm Severity ...................................................................... 6-2
6.1.2. Alarm Priority ........................................................................ 6-3
6.1.3. Environment Entities, Interfaces, and Configurations........... 6-4
6.1.3.1. Environment Entities .............................................. 6-4
6.1.3.2. Environment Interfaces and Configurations........... 6-5
6.1.3.3. PSTN Switch Interfaces ......................................... 6-5
6.1.3.4. Interfaces towards the IP Network ......................... 6-6
6.1.3.5. Terminal Cards ...................................................... 6-6
6.1.4. Terminal Alarm Indications ................................................... 6-7
6.1.4.1. Alarm Display......................................................... 6-7
6.1.4.2. Alarm Cut-Off (ACO).............................................. 6-8
6.1.4.3. Alarm Relays.......................................................... 6-8
6.1.4.4. VerazView-xMS Alarm and Event Reports ............ 6-8
6.2. PSTN Alarms....................................................................................... 6-9
6.2.1. Alarm Extension (Static Trunking Mode Only).................... 6-10
6.2.2. PSTN Alarms Priority Trees ............................................... 6-11
6.2.3. Alarm Filtering for E1 Links ................................................ 6-12
6.2.4. PSTN Alarms Summary ..................................................... 6-13
6.2.5. PSTN Alarms Detailed Description..................................... 6-17
ii Veraz Networks Inc. Proprietary 05050303-01

I-Gate 4000 EDGE Maintenance Manual Contents
6.2.5.1. E1 PSTN-side Alarms .......................................... 6-17

6.2.5.2. DS1 (T1) PSTN-side Alarms................................ 6-24
6.2.5.3. High Slip............................................................... 6-27
6.2.5.4. Low Slip ............................................................... 6-27
6.3. ISDN PRI Signaling Alarms............................................................... 6-28
6.4. IP Network Interface Alarms.............................................................. 6-30
6.4.1. IP Network Ethernet Link Failure Alarms............................ 6-31
6.4.1.1. Ethernet Link Failure............................................ 6-31
6.4.2. Ethernet Link Auto-Negotiation Failure............................... 6-31
6.4.2.1. Link is in half-duplex mode
(Auto-Negotiation failure) ...................................... 6-32
6.4.2.2. Link rate is 10 Mb/s.............................................. 6-32
6.4.3. PPP/MLPPP ALARMS ...................................................... 6-33
6.4.3.1. PPP link alarm ..................................................... 6-33
6.4.3.2. MLPPP link alarm ................................................ 6-33
6.5. Switched MG Alarms......................................................................... 6-34
6.5.1. MGC Communication Loss Alarm ...................................... 6-34
6.5.1.1. MGC Not Responding.......................................... 6-34
6.5.1.2. MGC Connection Re-establishment .................... 6-34
6.5.1.3. MGC Has Changed.............................................. 6-35
6.5.1.4. Available channel ratio below threshold............... 6-35
6.6. Static Trunking (Far-End terminal) alarms ........................................ 6-36
6.6.1.1. Static Trunking Alarm Principles .......................... 6-36
6.6.1.2. Static Trunking alarms priority tree ...................... 6-37
6.6.1.3. Far-End Alarm Handling ...................................... 6-37
6.6.2. IUA Alarms ......................................................................... 6-42
6.6.2.1. IUA AS Down ....................................................... 6-42
6.6.2.2. Connection to IUA AS congested ........................ 6-42
6.6.3. IUA and ISDN alarm priority tree ........................................ 6-43
6.6.4. SNTP SERVER ALARMS .................................................. 6-43
05050303-01 Veraz Networks Inc. Proprietary iii

Contents I - G a t e 4 0 0 0 E DG E M a i n t e n a n c e M a n u a l
6.7. System Clock Alarms ........................................................................ 6-44

6.7.1. Primary Clock Failure ......................................................... 6-44
6.7.2. Secondary Clock Failure .................................................... 6-44
6.7.3. All clocks Failure................................................................. 6-44
6.8. Temperature Alarms.......................................................................... 6-45
6.8.1. System Requirements ........................................................ 6-45
6.9. Equipment Alarms ............................................................................. 6-47
6.9.1. BPSM/XPSM card .............................................................. 6-47
6.9.2. Power Supply card ............................................................. 6-47
6.9.3. FAN module........................................................................ 6-47
6.9.4. Card missing and card mismatch ....................................... 6-48
6.9.4.1. Alarm handling Requirements.............................. 6-49
6.9.5. H/W failure Derived alarms................................................. 6-50
6.10. S/W Alarms ..................................................................................... 6-51
6.10.1. CPU Usage Above Threshold .......................................... 6-51
6.11. Event Log ........................................................................................ 6-52
6.11.1. Event Log - Alarms ........................................................... 6-53
6.11.2. Other Logged Events........................................................ 6-54
7 DIP Switch Settings.................................................................................. 7-1

7.1. BPSM (S410-013) ............................................................................... 7-4
7.2. XPSM (S410-021) ............................................................................... 7-4
A Glossary ....................................................................................................A-1
iv Veraz Networks Inc. Proprietary 05050303-01

1
Introduction
This introductory chapter of the manual covers items such as: purpose, intended
audience, and referenced documentation.
1.1. Purpose of this Manual

The purpose of this manual is to describe the maintenance procedures for the I-Gate
4000 EDGE terminal. These procedures include one-time and ongoing maintenance
for the I-Gate 4000 EDGE.
1.2. Intended Audience

This manual is intended for the person (operator or Veraz engineer) responsible for
maintaining the I-Gate 4000 EDGE.
1.3. Referenced Documentation

For a detailed description of items covered by other manuals, the following I-Gate
4000 EDGE documentation can be referenced:
I-Gate 4000 EDGE General Description (p/n 05050301)
I-Gate 4000 EDGE Installation Manual (p/n 05050302)
VerazView-xMS Configurator for I-Gate 4000 EDGE (p/n 06011901)
VerazView-xMS Fault and Performance Management (p/n 99060409)
VerazView-xMS Administration Guide (p/n 99110003)
05050303-01 Veraz Networks Inc. Proprietary 1-1

Introduction I - G a t e 4 0 0 0 E DG E M a i n t e n a n c e M a n u a l
This page intentionally left blank.

2
Safety Precautions
This chapter provides preliminary information that the operator should be familiar
with before performing maintenance operations.
2.1. Handling Precautions

The I-Gate 4000 EDGE uses MOS Semiconductor devices. Special handling
precautions must be observed when handling PCBs (modules). All personal tools,
test equipment, and metal objects that come in contact with Metal Oxide
Semiconductor (MOS) devices must be electrically grounded. Any static and/or
external voltage that is introduced into these devices can damage them permanently.
Caution: The following precautions must be observed when handling I-Gate

4000 EDGE equipment.

Safety Precautions I-Gate 4000 EDGE Maintenance Manual
2.1.1. Handling Printed Circuit Boards (modules)

Caution: Use of a grounding strap is obligatory when a printed circuit board
(PCB) card (module) is extracted or inserted into the terminal chassis.
Please adhere to the following precautions when handling PCBs (modules):

Do not rub, scratch, or scrape the printed wiring side with a sharp or abrasive
object.
Do not expose to excessive heat or humidity.
Do not make any unauthorized modifications, repairs, or adjustments.
Do not use abrasive cleaners.
Do not mark the cards with any writing instrument that leaves a conductive
deposit, such as lead pencil.
Do not stack PCBs (modules) on top of each other.
Do not store PCBs (modules) in an area that contains air pollutants (gas, smoke,
dust, etc.) that may contain harmful agents. Always store PCBs (modules) in
anti-static conductive bags.
2.1.2. Service Tool Precautions

When servicing the I-Gate 4000 EDGE, make sure that no tools are placed on the
top of the terminal.
A rack may house several terminals. Special precautions should be taken when
servicing the terminals located at the top of the cabinet/rack, to prevent tools,
screws, washers, etc. from falling into the lower terminals.

I-Gate 4000 EDGE Maintenance Manual Safety Precautions
2.2. Safety Instructions

The following safety instructions must be observed.
Restricted Access Area: The equipment should only be installed in a Restricted
Access Area.
Installation Codes: The equipment must be installed according to country
national electrical codes. In North America, equipment must be installed in
accordance with US National Electrical Code, Articles 110-16, 110-17 and 110-
18 and the Canadian Electrical Code, Section 12.
Overcurrent Protection: For a DC powered unit, a readily accessible Listed
branch circuit overcurrent protective device rated 6A for 1 Terminal or 12A for 2
Terminals or 18A for 3 Terminals or 24A for 4 Terminals must be incorporated
in the building wiring.
For an AC powered unit, the overcurrent protection relies on the building
installation.
Caution: For DC powered units, this equipment is designed to permit

connection between the earthed conductor of the DC supply circuit and the
earthing conductor at the equipment.

2.3. Power Precautions
2.3.1. Applicable to DC powered terminals only

The equipment shall be connected directly to the DC Supply System earthing
electrode conductor.
All equipment in the immediate vicinity shall be earthed the same way, and shall
not be earthed elsewhere.
The DC supply system is to be local, i.e. within the same premises as the
equipment.
There shall be no disconnect device between the earthed circuit conductor of the
DC source (return) and the point of connection of the earthing electrode
conductor.
2.3.2. Applicable to AC and DC powered terminals

Disconnect BOTH power cords before servicing.

2.4. BPSM/XPSM Card Battery Replacement
Warning There is a danger of explosion if the battery located on the

BPSM/XPSM module is replaced incorrectly. Replace the battery only with the
same or equivalent type recommended by the manufacturer. Dispose of used
batteries according to the manufacturer's instructions.
Waarschuwing Er is ontploffingsgevaar als de batterij verkeerd vervangen wordt.

Vervang de batterij slechts met hetzelfde of een equivalent type dat
door de fabrikant aanbevolen is. Gebruikte batterijen dienen
overeenkomstig fabrieksvoorschriften weggeworpen te worden.
Varoitus Räjähdyksen vaara, jos akku on vaihdettu väärään akkuun. Käytä

vaihtamiseen ainoastaan saman- tai vastaavantyyppistä akkua, joka on
valmistajan suosittelema. Hävitä käytetyt akut valmistajan ohjeiden
mukaan.
Attention Danger d'explosion si la pile n'est pas remplacée correctement. Ne la

remplacer que par une pile de type semblable ou équivalent,
recommandée par le fabricant. Jeter les piles usagées conformément
aux instructions du fabricant.
Warnung Bei Einsetzen einer falschen Batterie besteht Explosionsgefahr.

Ersetzen Sie die Batterie nur durch den gleichen oder vom Hersteller
empfohlenen Batterietyp. Entsorgen Sie die benutzten Batterien nach
den Anweisungen des Herstellers.
Avvertenza Pericolo di esplosione se la batteria non è installata correttamente.

Sostituire solo con una di tipo uguale o equivalente, consigliata dal
produttore. Eliminare le batterie usate secondo le istruzioni del
produttore.

Battery instructions (continued)
Advarsel Det kan være fare for eksplosjon hvis batteriet skiftes på feil måte.
Skift kun med samme eller tilsvarende type som er anbefalt av
produsenten. Kasser brukte batterier i henhold til produsentens
instruksjoner.
Aviso Existe perigo de explosão se a bateria for substituída incorrectamente.

Substitua a bateria por uma bateria igual ou de um tipo equivalente
recomendado pelo fabricante. Destrua as baterias usadas conforme as
instruções do fabricante.
¡Advertencia! Existe peligro de explosión si la batería se reemplaza de manera

incorrecta. Reemplazar la batería exclusivamente con el mismo tipo o
el equivalente recomendado por el fabricante. Desechar las baterías
gastadas según las instrucciones del fabricante.
Varning! Explosionsfara vid felaktigt batteribyte. Ersätt endast batteriet med

samma batterityp som rekommenderas av tillverkaren eller
motsvarande. Följ tillverkarens anvisningar vid kassering av använda
batterier.

2.5. Electrostatic Discharge (ESD) Precautions

Warning: The I-Gate 4000 EDGE terminal contains devices that can be
damaged by accidental introduction of ground or foreign voltages. Therefore,
read carefully all points in this section regarding electrostatic discharge (ESD)
and other electrical precautions before proceeding with installation.
Notes:
1. For DC powered units, better ESD performance will result if the Ground
cable is connected from the Terminal's GND screw via the shortest route to the
Exchange Ground point.
2. Ensure that the mounting points are paint-free and deliver ground contact to
the flanges.
3. It is recommended to use a filtered, 9-pin D-type, male connector with hood
on the Alarm connector located at the rear of the terminal. This will protect the
inputs to the system from ESD. Using this filtered connector also applies even
if there is no cable connection.
Certain tools and test equipment commonly used on electromechanical systems

should never be used on the I-Gate 4000 EDGE. These include: battery buzzers, AC
wire-wrap guns, electric soldering irons and guns, test picks and test lamps.
The following precautions must be observed:
The I-Gate 4000 EDGE uses various Metal Oxide Semiconductor (MOS)
devices. All personal tools, test equipment and metal objects that come in
contact with MOS devices must be electrically grounded. Any static or foreign
voltage that is introduced into these devices may damage them permanently.
Do not use tools or test equipment, such as test lamps and picks that draw an
appreciable amount of current when attached to the system.
Do not use tools or test equipment that could introduce foreign voltages into the
system. For example, a battery-powered buzzer operates on only six or nine
volts, but the voltage introduced across the buzzer coil when the magnetic field
collapses can reach a momentary peak in excess of 100V, which can destroy
solid-state devices.

Use only hand-powered or battery-powered wire-wrap guns in equipment

cabinets. AC-powered wire-wrap guns and lead verification equipment can be
used at the distribution frames only if all cabling has been disconnected from the
cabinet.
When handling I-Gate 4000 EDGE modules, always use an anti-static strap.
2.6. Radio Interference Precautions
Warning (CE Standard EN 55022): 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.
Note:
This equipment has been tested and found to comply with the limits for a Class
A digital device, pursuant 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.

3
Repair and Return Procedure
Repair and return orders are issued to fix customer-owned material where service
conditions do not require advance replacement or when least-costly service is
desired. Generally, repair and return orders are mailed to the Technical Assistance
Center (TAC), as listed in Section 3.6, "Technical Assistance Centers (TACs)". The
TAC will either repair or replace the equipment accordingly. Typical delivery
interval is up to 30 days from the arrival of the operator's equipment at the TAC.
In-warranty repair service is free of charge. In-bound freight charges are paid for by
the customer, whereas outgoing freight charges are paid by Veraz.

Repair and Return Procedure I -G a t e 4 0 0 0 E D G E M a i n t e n a n c e M a n u a l
3.1. Ordering Replacement Equipment

All defective materials/equipment returned to Veraz for repairs/update must have a
Returned Materials Approval (RMA) number clearly marked on it. To receive an
RMA number, the operator must contact the operator's TAC representative. (A TAC
list appears in Section 3.6 "Technical Assistance Centers (TACs)"). After the TAC
representative has approved the operator's request, the operator will be issued with
an RMA number and form. Repair request approval is based on the service
agreement warranty. Any discrepancies will be cleared up prior to issuing the RMA
number.
Note: Before contacting the TAC representative, the operator must prepare
the operator's material requirements, warranty status, shipping instructions,
purchase order number and name of the person authorizing the purchase
order.
Complete the form and then fax or email it to the relevant TAC. You will receive
your RMA form signed by the TAC within one working day.
Each shipment returned to Veraz must be clearly marked with an RMA number. A
complete description of the failure should be written for each part returned. Goods
must be returned to Veraz in one shipment. Do not send components separately.
Your TAC representative will prepare an order and file it in our receiving area
pending arrival of all the parts.
Emergency orders (high priority) must be shipped via express/traceable means.
Regular orders are shipped via a standard carrier.

I - G a t e 4 0 0 0 E D G E M a i n t e n a n c e M a n u al Repair and Return Procedure
Customer Service
Date: ____________ RMA Request Form Page ____ of ____
To: Customer Ref:#

Veraz Networks Inc. - TAC
Order Ref.#
Email: Service@Veraznetworks.com
From: Deliver To:
(Company name) (Return address)
Contact Person:
Phone:
Fax:
Email:
Item System Veraz Veraz S/N Covered RMA#
Name Type Drawing # under (completed
- Option warranty or by Veraz)
contract:
(for Veraz use
only)
----"--- ----------------
----"--- ----------------
----"--- ----------------
----"--- ----------------
----"--- ----------------
----"--- ----------------
----"--- ----------------
Priority: HR PHR AR
Reason for Return: Repair ECN Replacement (upgrade)
Remarks:
Authorized by: Signature:

Figure 3-1: RMA Request form

3.2. Insurance Policy

Veraz will insure, at its own expense, materials shipped from Veraz to the customer.
However, materials shipped by the customer to the TAC are insured by the customer
at the customer's expense.
3.3. Substitutions and Modifications

Veraz reserves the right to make modifications without prior warning to the
specifications of equipment designed by Veraz that neither materially nor adversely
affects the performance of the equipment.
3.4. Limitations of Liability

Except as described under "Warranty", Veraz shall not be legally responsible for any
liability, loss, damage, or expense relating to, arising out of, or in connection with
the purchase, operation, use of licensing of equipment, software, and services. In no
event shall Veraz be liable for any SPECIAL, indirect, accidental, or consequential
damages of any nature, regardless of whether Veraz has been advised of the
possibility of such damages.

I - G a t e 4 0 0 0 E D G E M a i n t e n a n c e M a n u al Repair and Return Procedure
3.5. Shipping Information

1. Returned goods should be shipped to your nearest TAC address. To receive the
correct address contact: Service@Veraznetworks.com.
2. Attach a proforma invoice containing the following information to the carton/s:
RMA# received from the TAC.
Unit price (for customs purposes).
Return address for goods after repairs.
Consigned to: as instructed by your nearest TAC.
3. Instruct your Forwarder to:
Write the RMA# on the AWB
Attach both the House and Master AWB's to your shipment
4. After sending the shipment, and for Customs clearance purposes, fax the
following documents to your TAC fax number:
A copy of the proforma invoice
AWB number
Flight details
Note: Always write the RMA# on the shipment.

The above instructions, when carried out, help Customs to handle your
shipment quickly and efficiently.

3.6. Technical Assistance Centers (TACs)

USA
Tel: +1-214-6473397
E-mail: noc@cmsnoc.net
India
Tel: + 9111-51524570
Fax: + 9111-51524580
UK
Tel: +44-1276-388117
Fax: +44-1256-388148
For further contact information for our TAC offices:
Web page: : http://www.veraznetworks.com/content.asp?pageId=242
Email: Service@Veraznetworks.com
3.7. Terminal Malfunction Check

In the event that a terminal ceases to operate, perform the following:
Perform a power up reset.
Verify return of the terminal to normal operation.
Report to Veraz's Technical Assistance Center (TAC) as soon as possible. Attach
all relevant information to the report such as history.

4
Replacing Modules
This chapter provides step-by-step procedures for removing and inserting the I-Gate
4000 EDGE modules. This is required in cases such as module replacement (e.g. due
to module failure) or when setting DIP switches for initialization and debugging.
Warnings:
1. If the I-gate 4000 EDGE is installed in a cabinet/rack, ensure that the relevant
circuit breaker is in the OFF position before connecting to the PDU
(-48VDC). Then insert the power supply module(s) (either EACM or EDCM,
depending on the configuration ordered). Switch on the circuit breaker and verify
that the front panel LEDs are activated.
2. Use of a grounding strap is obligatory when a (PCB) Printed Circuit Board
(module) is extracted or inserted into the terminal chassis.
3. Personnel handling PCBs (modules) should be grounded, using a grounding
strap
Figure 4-1: Module Location ID

Replacing Modules I-Gate 4000 EDGE Maintenance Manual
Table 4-1: I-Gate 4000 EDGE Module Types and Locations

Module Type Name Module Description
(*)
TDM Network IC4P (1) 4-Port TDM Network Interface
Interface modules IC8P (1) 8-Port TDM Network Interface
ICHP (1) 20-Port TDM Network Interface
Traffic processing and BPSM (2) and / or Basic Processing and Switching Module
switching modules (3) - Supports Redundancy
XPSM (2) and / or Expanded Processing and Switching Module
(3) - Supports Redundancy
Fan Tray module EFTM (4) Fan Tray Module (4 fans)
Power supply modules EDCM (5) and / or DC Power Supply Module
EACM (5) and / or AC Power Supply Module
Mid Plan MDP (7) Motherboard (part of the chassis)
* Note: The module number and location are shown in Figure 4-1

I-Gate 4000 EDGE Maintenance Manual Replacing Modules
4.1. Extracting the Modules

To extract a Module:
1. Select module (with the appropriate functionality) for removal from the slot (see
Figure 4-1.
2. Unscrew (turn anti-clockwise) the module screws (two M2.5 captive screws)
with a Phillips screwdriver until loose (see Figure 4-2).
Note: that all modules have two retaining screws with the exception of the Fan
Tray Module which has only one retaining screw.
3. Grasp the module handle and slide module out of the slot. Do not use undue
force.
Untighten the M2.5 Untighten the M2.5

Captive screw Captive screw
Figure 4-2: Extracting a module

Replacing Modules I-Gate 4000 EDGE Maintenance Manual
4.2. Inserting the Modules

To insert a Module:
1. Align the module with the slot appropriate for the functionality of the card (see
Figure 4-1).
2. Slide the module straight back into the slot until the module is aligned flush with
the other modules. Do not force the module.
3. Tighten (turn clockwise) the module screws (two M2.5 captive screws) with a
Phillips screwdriver until secure (see Figure 4-3). Do not over-tighten.
Tighten the M2.5 Tighten the M2.5

Captive screw Captive screw
Figure 4-3: Inserting a module

5
Module Redundancy
This chapter explains the module and Ethernet Interface redundancy protection
mechanism of the I-Gate 4000 EDGE. It also recommends operator procedures after
switchover to the redundancy module. In this chapter, the "Hardware View" window
of the VerazView-xMS Management System is described (Section 5.1). This is
followed by an explanation of how to perform maintenance and changeover
procedures on the redundant modules (Section 5.3). The procedures described in
detail the steps that the technician should follow: i.e. replacing the failed module
with the protecting module and, after repair, putting the module back into service.
All I-Gate 4000 EDGE traffic-affecting modules support module-redundancy
according to the following:
XPSM modules (1+1 redundancy)
BPSM modules (1+1 redundancy)
EDCM modules (1+1 redundancy)
EACM modules (1+1 redundancy)

Module Redundancy I-Gate 4000 EDGE Maintenance Manual
5.1. VerazView-xMS Hardware View

When using the VerazView-xMS Management System, the Hardware View displays
a representation of the actual modules that are installed in the selected Media
Gateway. The Status Manager reads the hardware information directly from the
Media Gateway. Therefore, if there is any discrepancy between this hardware
information and the cards defined in the Media Gateway's active configuration map,
it can be detected in the Hardware View. For details on defining modules in a
gateway's configuration map, refer to the "VerazView-xMS Configurator User's
Guide".
To access the Hardware Details View:
In the Topology View, right-click a gateway (or in the Logical View, right-click
anywhere) and select Hardware View. The Hardware View window is displayed in
Figure 5-1.
Figure 5-1: Typical I-Gate 4000 EDGE Hardware View window

I-Gate 4000 EDGE Maintenance Manual Module Redundancy
5.1.1. Hardware View window displays

The Hardware View is a visual representation of the gateway and the modules
installed in their respective locations. The information displayed here is
automatically updated from the gateway.
The Hardware View displays four elliptical icons above the gateway:
Highest Severity: Displays the highest severity alarm currently active on the
gateway.
xMS Server: Confirms that communication exists between the VerazView-xMS
Fault and Performance Manager and the current gateway. The xMS Link field
displays Link OK when communication is active, or Fail when communication
links are severed.
ACO: Displays whether the audible alarms ring or not. When ACO is ON,
audible alarms emanating from this gateway stop ringing, regardless of whether
the action that caused the alarm has been dealt with.
Invalid License: Appears if the license of the current gateway is invalid.
The view shows each card's front panel, including its LED's. If a card's
administrative state is Out Of Configuration, a round orange icon appears in the
upper-right corner of a BPSM or XPSM module.
5.1.2. Hardware View right-click Menu options

Right-clicking anywhere in the Hardware View displays these options
(see Figure 5-2):
Current Alarms: opens the Current Alarms view, confirming the alarms that are
currently on for the selected Media Gateway.
History Browser: opens the History Browser, in which you can view a list of all
alarms and events sent by the selected gateway to the VerazView-xMS Fault and
Performance Manager.
Terminal Details: opens the Terminal Details window, in which you can view
additional information about the selected gateway.

Maintenance: enables you to perform one of the gateway maintenance options:

Reset or ACO.
Card Details: View various inventory details and other identifying information
of a selected module.
Set As Working: Changes the status of the protected module to be in working
mode.
Card Reset: Reset a gateway module in the event of a map mismatch. See
Section
Refresh: Refreshes the display in the Hardware View if configuration changes
have been made since you opened this window.
Help: this option is not yet available
Figure 5-2: Hardware View Right-Click Menu options

5.2. License Verification

If you are attempting to install new or additional modules into the I-Gate 4000
EDGE terminal, make sure before-hand that the terminal's license supports your
specific configuration (reference VerazView-xMS Configurator Manual, Chapter 5,
"Defining System Parameters and License Key", Pub. No. 06011901).
In Figure 5-3, an elliptical Invalid License icon is displayed. This indicates a
mismatch with the permitted configuration and the terminal will not be able to
handle traffic. A Critical alarm indicating a license-terminal ID mismatch is
generated and displayed in the Current Alarms window.
Figure 5-3: Hardware View Window, displaying Invalid License icon
Figure 5-4: Current Alarms Table showing License Mismatch

5.3. Module Changeover Operations

If a fault occurs on the working module (e.g. hardware BIT or software Exception
fault), the module is automatically taken out of service and replaced with a
redundant module. Later, after maintenance has been completed, the out-of-service
module can be returned back to service. The maintenance procedure after automatic
changeover to a redundant module is explained in Section 5.4.
The changeover icons (see Table 5-1) appear on the front panel of the module to
signify its changeover status:
Table 5-1: Changeover icon definitions

Icon Description
Protected module is in process of initialization or in transition from active to replaced. A
warning alarm (blue icon) appears.
W Indicates that this Module is currently working (the active module).
P Indicates that this Module is currently in protecting mode (the inactive module).
When a fault in a module has been discovered, an automatic changeover process to

the protection module is initiated. The user can then remove the faulty card, repair it
and reinsert the module in the terminal. The terminal will then "sense" the repaired
module, initialize it and put it back into operation as the Protecting module.
Notes:
1. The BPSM or XPSM modules indicate a changeover from working to
protected modes with the letters "W" and "P".
2. When a module is returned to the system after repair, it will assume the
Protection role by default.

5.4. Maintenance Procedures after Automatic

Changeover
This section describes maintenance procedures after automatic changeover occurs
for the following redundancies:
XPSM modules
BPSM modules
EDCM modules
EACM modules

5.4.1. XPSM Redundancy

If a hardware or software fault has occurred in the XPSM working module, an alarm
will be generated and the protecting (standby module) will automatically replace the
faulty XPSM module.
Figure 5-5: Card layout with XPSM redundancy support - after Automatic Changeover
To perform maintenance operations:

1. Check the changeover status (working - W and protecting - P) on the XPSM
Hardware View front panels. This indicates that it is currently being replaced by
the protection card in slot 3. In addition, the normally redundant card that is
currently replacing the active card has the letter "W" showing.
2. Physically remove the XPSM module from slot 2.
3. You now can safely perform appropriate maintenance on the out-of-service
XPSM module without affecting traffic.

4. The Current Alarms dialog box (Figure 5-6) displays details of the failure in
the XPSM card (see top line of table).
Figure 5-6: Current Alarms window (XPSM) -- Card Missing
5. Physically install the XPSM module back to slot 2. The Current Alarms window
indicates "Card SW Reset". This means that the repaired card is being initialized
and will function as the Protecting module.
Figure 5-7: Current Alarms window (XPSM) -- Card SW Reset
Notes:
1. The XPSM modules indicate a changeover from working to protected modes
with the letters "W" and "P".
6. If the user wishes to return to the original hardware configuration -- location #2

module in working (W) role -- the following operation should be performed.

To perform manual Set As Working operation:

1. Once you have completed the appropriate maintenance procedures, return to the
Hardware View window, right-click the Protecting XPSM card, and choose Set
As Working to display the menu.
Figure 5-8: XPSM Card Reset Menu
2. Click the Set As Working item on the menu and Figure 5-9 will appear.
Figure 5-9: XPSM Card Reset Dialog Box

3. An Operation Confirmation dialog box will appear. Check if you wish to

continue with this operation.
4. Click the OK button to return the previously inactive XPSM module into
service.

5.4.2. BPSM Redundancy

If a hardware or software fault has occurred in the BPSM working module, an alarm
will be generated and the protecting (standby module) will automatically replace the
faulty BPSM module.
Figure 5-10: Card layout with BPSM support -- after Automatic Changeover

1. Check the changeover status (working - W and protecting - P) on the BPSM
Hardware View front panels. This indicates that it is currently being replaced by
the protection card in slot 3. In addition, the normally redundant card that is
currently replacing the active card has the letter "W" showing.
2. Physically remove the BPSM card from slot 2.
3. You can now safely perform appropriate maintenance on the out-of-service
BPSM card without affecting traffic.

4. The Current Alarms dialog box (Figure 5-11) displays details of the failure in
the BPSM card (see top line of table).
Figure 5-11: Current Alarms window (BPSM)
5. Physically install the BPSM module back to slot 2.
Notes:
1. The BPSM modules indicate a changeover from working to protected modes
with the letters "W" and "P".
6. If the user wishes to return to the original configuration, where the module in
location #2 takes on its original working (W) role, the following operation
should be performed.

To perform manual Set As Working operations:

1. Once you have completed the appropriate maintenance procedures, return to the
Hardware View window, right-click the working BPSM card, and choose Card
Reset to display the Card Reset menu.
Figure 5-12: BPSM Card Reset Menu
2. Click the Set As Working item on the menu and Figure 5-13 will appear.
Figure 5-13: BPSM Card Reset Dialog Box

3. An Operation Confirmation dialog box will appear. Check if you wish to

continue with this operation.
4. Click the OK button to return the previously inactive BPSM module into
service.
5. Verify that the status on the Hardware View front panels of the BPSM cards has
been reset (i.e. slot #2, W and slot #3, P).

5.4.3. Input Power Source Redundancy

The I-Gate 4000 EDGE can support either one or two voltage input connections (via
two EDCM modules or two EACM modules). Both modules are required to support
external power feed redundancy.
Only one type of power supply may be installed at any one time (i.e. 2 x EDCM
modules or 2 x EACM modules). They are located in slots 5 and 6 respectively (at
the rear of the terminal).
The power supply modules support connection to an independent building power
source (EDCM: -48/-60 VDC and EACM: 110/220 VAC). Each can handle the
power consumption required for a fully configured I-Gate 4000 EDGE.
At any specific time, the I-Gate 4000 EDGE will operate the higher of the two
external voltage sources to supply the system. If voltage at one of the power sources
falls below 40V, a Major alarm will be activated or if its voltage falls below the
voltage of the other external supply, this is immediately detected and the second
(redundant) power source is automatically activated.
Figure 5-14 illustrates a layout of the modules for the I-Gate 4000 EDGE gateway
whose configuration supports one or two external source power units.
Figure 5-14: Card layout with support for two input power sources

If a power supply source ceases to operate, a Warning severity alarm will be

generated. This can be seen in the Current Alarms window.
Figure 5-15: Current Alarms window (Power Failure)
By double-clicking on the Power Input Failure message in the Current Alarms

dialog box, an Event Information window will be displayed in which you can see
in the description field, if the power failure relates to the respective power supply
inputs.

1. Check the power input to the EDCM/EACM modules and perform the
appropriate power maintenance in order to restore the correct power to the
terminal.
2. When the correct power has been restored, the card will automatically detect it
and the alarm icon/message in the Current Alarm window will disappear.

This page intentionally left blank.

6
System and Network Alarms
This chapter deals with the I-Gate 4000 EDGE system alarms and events. It
describes the alarms by tracking environmental defects through the processes that
handle the defect and terminate at the consequent actions generated (due to the
detected defect/alarm). The network entities covered are:
PSTN (TDM) switch interfaces -- E1 and DS-1
IP network
Clock Synchronization
VerazView-xMS
ISDN PRI signaling alarms
MGC (MGCP and IUA protocols)
DNS server
SNTP server
Far End I-Gate 4000 Terminals
Terminal internal environment: Temperature, H/W (BIT), S/W, configuration
maps, flash memory synchronization
The internal entities covered in this chapter are the software and hardware processes
which react to detected failures and alarms. Most of the alarm types are related to
the transmitted and received traffic (transmission alarms). The alarm handling
process is performed by the BPSM or XPSM modules.

S y s t e m a n d N e tw o r k Al a r m s I-Gate 4000 EDGE Maintenance Manual
6.1. Alarm Handling

All links between telecommunication equipment are bi-directional, and the interface
of two telecommunication devices requires two links: Incoming and Outgoing.
Transmission retry over these links is not possible at the physical and link layers,
and consequently the error correction mechanism is not applicable. However,
monitoring the signal quality is very important both for bypassing services assigned
to failed or poor quality links, and for billing purposes. The equipment detects
incoming signal defects and signals back this defect on the corresponding outgoing
link.
The interfaces may be located on several communication layers (physical, Data
Link, Network, Application). Each layer has its own defect detection and alarm
indication mechanism.
6.1.1. Alarm Severity

The I-Gate 4000 EDGE uses the ITU-TX.733 terminology for alarm categories. The
I-Gate 4000 EDGE provides four levels of terminal alarms:
Critical: indicates that a service affecting condition has occurred and an
immediate corrective action is required. Critical alarm can be reported, for
example, when a H/W module has failed in the BIT tests and no redundancy is
available.
Major: indicates that a service affecting condition has developed and an urgent
corrective action is required. Major alarm can be reported, for example, when an
input TDM span is in LOS or LOF alarm.
Minor: indicates the existence of a non-service affecting fault condition and that
corrective action is to be taken in order to prevent a more serious (for example,
service-affecting) fault. Minor alarms are reported in case of a H/W failure of a
redundant card.
Warning: indicates the detection of a potential or impending service-affecting
fault, before any significant effects have been felt. Action is taken to further
diagnose (if necessary) and correct the problem in order to prevent it from
becoming a more serious service-affecting fault.

I - G a t e 4 0 0 0 E D G E M a i n t e n a n c e M a n u al S y s t e m a n d N e tw o r k Al a r m s
The alarm severity of most terminal alarm types is configurable off-line and during
run-time.
The only alarm with non-configurable severity is H/W failure (BIT), which has
Critical severity when card redundancy is not available and Minor severity when
switchover to a redundant card is performed.
Run-time changes of alarm severity shall be affective from the next alarm
declaration.
6.1.2. Alarm Priority

Each alarm type in the system has a priority. This priority mechanism is required in
order to prevent multiple actions and reports for a single failure.
Any single failure will result in only one alarm output message.
In a case where two alarms occur simultaneously, in the same physical interface,
only the higher priority alarm will be displayed and its consequent actions
implemented.
If an alarm is declared after a lower priority alarm has already been reported, the
lower priority alarm is considered as terminated.
Each physical interface uses an independent alarm handling process.

6.1.3. Environment Entities, Interfaces, and

Configurations
6.1.3.1. Environment Entities

The I-Gate 4000 EDGE environment includes:
PSTN switch - the I-Gate 4000 EDGE receives/transmits from/to the PSTN
switch telephony and Signaling channels.
IP network - the I-Gate 4000 EDGE is connected to the far-end I-Gate 4000
EDGE terminals as well as to remote VerazView-xMS stations and MGC
through the IP network.
Far End terminals - the I-Gate 4000 EDGE receives/transmits telephony
channels from/to the Far End terminals (Media Gateways).
VerazView-xMS Operator Station - for system management. Local VerazView-
xMS may be connected through a specific Fast Ethernet interface. Remote
VerazView-xMS communicates with the terminal through the network router.
Media Gateway Controller (MGC) - an element which is a part of the call
signaling net, receives alarm indications from the I-Gate regarding the trunk side
physical links
ASP (Primary and Secondary, each with one or two IP interfaces), for IUA
protocol communication
SNTP server - enables update of the terminal Real Time clock and maintains
accurate and correlated timing between all terminals in the network
Terminal alarm indicators (LEDs, relays)
System Clock sources
Terminal Hardware cards and input power supply

6.1.3.2. Environment Interfaces and Configurations

In this section, the alarms related to all of the different I-Gate configurations are
described. Figure 6-1 depicts the terminal alarm-handling environment.
Figure 6-1: I-Gate 4000 EDGE alarm-handling environment
6.1.3.3. PSTN Switch Interfaces

E1
DS1

6.1.3.4. Interfaces towards the IP Network

In the I-Gate 4000 EDGE, up to four 100BaseT and three Gigabit Ethernet IP
interfaces can be configured (depending on the I/O card). Each Ethernet/IP link may
be configured with a redundant link.
The I-Gate 4000 EDGE terminal communicates with the following network entities
through the IP network:
VerazView-xMS (one or more)
MGC (Primary and Secondary, each with one or two IP interfaces), for MGCP
ASP (Primary and Secondary, each with one or two IP interfaces), for IUA
DNS server
SNTP server
Far End terminals (relevant for Static Trunking)
6.1.3.5. Terminal Cards

Hardware failures, card extraction, card insertion and card redundancy, manual and
automatic operations change the terminal alarm severity and cause specific traps to
be sent. The relationship between environmental alarms and hardware failures is
taken into account (e.g. in the priority tree diagrams).

6.1.4. Terminal Alarm Indications
6.1.4.1. Alarm Display

The terminal displays alarm conditions by using fault indicators (LEDs), which
remain ON for the duration of the alarm condition and extinguish automatically
upon removal of the alarm condition. Four LEDs are mounted on the BPSM or
XPSM panel (marked with abbreviations for CRITICAL, MAJOR, MINOR and
STATUS). The LEDs are activated by the software in the BPSM or XPSM card.
Status LED behavior
The Status LED is ON according to the following rules:
a) Green - When the card is active and not faulty
b) Yellow -- When the card is in standby mode and not faulty
c) Red -- The card is faulty while in active or in standby mode
d) Off -- The card is not configured
Alarm LED behavior

Only one LED of the 3 is ON at a given time, indicating the alarm of highest
severity.
a) The Critical and Major LEDs are lit with red color.
b) The Minor LED is lit with an amber color.
c) No LED is activated for Warning alarm.
d) The LEDs are lit only on the active BPSM card
e) Only one LED, indicating the alarm of highest severity, is activated at a given
time (CRITICAL, MAJOR, MINOR and STATUS) are alarm severity indicators
in descending order).

6.1.4.2. Alarm Cut-Off (ACO)

An xMS operator command (action) enables cut-off of audible alarms.
The alarm mechanism may be connected to an audible alarm facility (via the alarm
relays). This audible alarm may be shut off by the ACO xMS command.
A new alarm with a higher severity will re-activate the audible alarm.
From the time that the ACO xMS command is issued for the duration of the alarm
signal, the cut-off state is indicated by the alarm cut-off indicators on the xMS status
display. After sending an xMS command, the ACO indicator on the xMS is lit until
the alarm condition is terminated.
In case of several simultaneous alarms, the ACO indicator is lit until all the alarms
are off.
6.1.4.3. Alarm Relays

Three alarm relays are mounted on the BPSM/XPSM card. The relays' state reflects
the alarm status. The relays are assigned to the alarms as follows:
Relay #1: Critical plus Major
Relay #2: Minor
If the ACO command is received during an alarm, the alarm relays will be
deactivated.
6.1.4.4. VerazView-xMS Alarm and Event Reports

See Section 6.11 "Event Log".

6.2. PSTN Alarms

The PSTN alarm indications are set and cleared according to well-defined criteria
based on the occurrence and duration of specific events. Some events lead
immediately to alarm indications, while others must persist for a specific
"integration" period prior to activation of an alarm.
The principle of the required consequent actions to be taken after detection of a fault
condition is described here.
When an I-Gate terminal detects any alarm on an incoming trunk bit-stream it
performs the following consequent actions:
All affected TDM channels are classified according to their type: MGC
controlled (MGCP/H.248), Static Trunking, CCS, ISDN/IUA), x-connect,
IPoTDM or Idle (inactive).
For all TDM channels that are controlled by MGC, if the failure severity is major
(LOS, LOF, AIS, HBER) or if RAI alarm is declared, the Media Gateway
informs the MGC, using RSIP force command. Since the entire Trunk BS
channels are affected, a wildcard message is sent to the MGC. The MGC
releases all calls which are transferred on the faulty TDM channels and will not
open new calls on these time slots. When the alarm stops, the Media Gateway
informs the MGC using RSIP restart message (wildcard) so as to return the
relevant time slots to normal functioning.
For Static Trunking (Trunk replacement) TDM channels, a forward alarm
indication to the far-end terminal is sent for the same alarm types ("FE-TDM"
alarm). For RAI, a separate alarm ("FE-RAI") is sent. The far end terminal will
extend this alarm to the next PSTN switch, only if all output trunk channels are
marked with an AIS/64K or with RAI/64K. In this case the terminal will send
the AIS/2M or RAI signal towards the PSTN switch.
The terminal sends a backward alarm indication (RAI or RDI) to the equipment
from the PSTN switch.
Every change of PSTN alarm is notified to all registered VerazView-xMS
stations using Trap and Status mechanisms

E1/DS1 LOS defect is notified to the clock selection mechanism

For the PSTN bit stream maintenance operation (bit stream is taken out of
service in order to perform maintenance loop-back), no transmission alarm
indications are delivered and no alarm consequent actions are performed.
If the E1 or DS1 is controlled by MGC, and the ISDN PRI signaling layer 2
terminates in the system, then the corresponding data link must be disconnected.
The possibility of bringing up a link by any external element (i.e. PBX or ASP)
during a major PSTN failure (LOS, LOF, AIS and HBER) must be prevented.
When the alarm stops the system must be ready to establish a link by the request
of an ISDN peer (public switch or by PBX) or by an entity with backhauled
Q.931.
Note: For Static Trunking TDM channels, the AIS/64k alarm indication is
transferred to the far-end terminal using RTCP Application messages. These
messages are transmitted at least once per second until the alarm conditions
are removed. As long as the alarm condition stays, the terminal stops sending
any other RTP or RTCP packets. The far-end terminal removes the alarm
indication when it receives the first RTP or RTCP packet.
6.2.1. Alarm Extension (Static Trunking Mode Only)

The alarm extension per BS mode is essential in order to inform the PSTN switch to
ignore the incoming traffic from the I-Gate as a result of a major problem at the IP
network or at the far-end PSTN switch.
If a far-end alarm is detected (see section 6.6), the I-Gate terminal injects an AIS to
the entire trunk out BS (AIS/2M) concurrently for all the channels of a specific
trunk.
Note: For trunks that contain even a single time slot that is controlled by
MGCP, no AIS is injected as used for alarm extension.

6.2.2. PSTN Alarms Priority Trees

Figure 6-2 and Figure 6-3, depict the alarm priority trees for E1 and DS1
configurations for PSTN alarms.
H/W failure (no rdcy)

Interface H/W
Transmission LOS
AIS
LOF CRC MFR
HBER HCRC
HSLIP-TX
ISDN
LSLIP-TX Link Down
MFR LBER RAI
ISDN
Link Congestion
RMFR
Figure 6-2: E1 alarm priority display tree

H/W failure (no rdcy)

Interface H/W
Transmission LOS
failure
AIS
failure
LOF
failure
HBER
failure
HSLIP- ISDN
TX Link Down
RAI
LSLIP-TX ISDN Link

Congested
Figure 6-3: DS1 alarm priority display tree
6.2.3. Alarm Filtering for E1 Links

Although the various E1 standards do not specify any integration period or any other
means of alarm filtering, the I-Gate performs alarm filtering for E1 links using a
"trunk alarm delay" mechanism which has the same functionality of the "hit
integration" with three exceptions:
The ON and OFF integration periods are equal.
The integration period is configurable from 0 seconds (no integration) to 3
seconds.
The minimal value of the alarm OFF period is one second, even if the alarm
integration period is set to 0.

During the integration period of a specific defect, lower priority defects are
cleared. In addition, lower priority counters (CRC and Slip counters) are also
cleared.
6.2.4. PSTN Alarms Summary

E1 and DS1 alarms are presented in Table 6-1 and Table 6-2, respectively.
Table 6-1: I-Gate 4000 EDGE E1 TDM-side alarms

No. Alarm Alarm On Alarm Off Default Generate Switched Static Far End I-Gate
Type conditions conditions Severity backward channels channels Alarm
alarm consequent consequent consequent
towards actions actions action
PSTN
(Static Trunking
switch only)
1. LOS LOS defect No LOS defect Major RAI (3) RSIP force Stop RTP/RTCP AIS/2M if all TS
persists more more than 0-3 wildcard if entire send App packets affected
than 0-3 seconds seconds BS, disconnect every second
ISDN data link
2. AIS AIS defect No AIS defect Major RAI (3) RSIP force Stop RTP/RTCP AIS/2M if all TS
ISDN data link
3. LOF LOF defect No LOF defect Major RAI (3) RSIP force Stop RTP/RTCP AIS/2M if all TS
ISDN data link
4. HBER CRC counter > CRC counter < Major RAI (3) RSIP force Stop RTP/RTCP AIS/2M if all TS
(BER >10 )-3 805 or 805 or wildcard if entire send App packets affected
FE counter> 28 FE counter < 28 BS, disconnect every second
for continuous 5 for continuous 5 ISDN data link
seconds seconds
5. CRC-MFR 3 consecutive 2 valid CRC Major
multiframes multiframe
contain errored alignment signals
multiframe can be located
alignment signals within 8 ms
6. LBER CRC counter > CRC counter < Minor
(10-6 <BER 120 or 120 or
>10-3) FE counter> 3 FE counter < 3
for continuous for continuous
120 seconds 120 seconds
7. MFR MFR defect at least one bit in Major RMFR (3) Stop RTP/RTCP AIS/2M if all TS
persists more state 1 is present send App packets affected
than 0-3 seconds in time slot 16 every second
Frame 0 bits 1-4

No. Alarm Alarm On Alarm Off Default Generate Switched Static Far End I-Gate
Type conditions conditions Severity backward channels channels Alarm
alarm consequent consequent consequent
towards actions actions action
PSTN
(Static Trunking
switch only)
8. RMFR bit 6 in TS16, Deactivation of Minor
Frame 0 is on for TS 16, frame 0
at least one bit 6
frame
9. RAI Bit 3 in TS0 of bit 3 in TS0 is Minor RSIP force send App packets RAI/2M if all TS
frame not "0". wildcard every second affected
containing frame
alignment signal
10. HSLIP >30 slips in less An hour with Minor
than an hour less than 30 slips
11. LSLIP >5 slips in less 24 hours with Warning
than 24 hours less than 5 slips
12. ISDN link LAP-D LAP-D re- Minor
down disconnects the connects the
ISDN data link ISDN data link
and no PSTN or PSTN alarm
alarm on on corresponding
corresponding E1 or IP link loss
E1, and no IP or AS down
link loss and no alarm or
AS down alarm maintenance on
and no corresponding
maintenance on E1 or
corresponding maintenance on
E1 and no MG
maintenance on
MG
13. ISDN link LAP-D measures LAP-D measures Warning
congested congestion normal
conditions on conditions on
or ISDN link is
down or PSTN
alarm on
corresponding
E1 or IP link loss
or AS down
alarm or
maintenance on
corresponding
E1 or
maintenance on
MG

Table 6-2: I-Gate 4000 EDGE DS1 TDM-side alarms

No. Alarm Alarm On Alarm Off Default Generate Switched Static channels Far End I-Gate
Type conditions conditions Severity backward channels consequent Alarm
alarm consequent actions consequent
towards actions action
PSTN (Static Trunking
switch
only)
1. LOS LOS defect No LOS defect Major RAI (3) RSIP force Stop RTP/RTCP AIS/2M if all TS
persists more more than 20 wildcard if entire send App packets affected
than 2.5 seconds seconds BS every second
2. AIS AIS defect No AIS defect Major RAI (3) RSIP force Stop RTP/RTCP AIS/2M if all TS
persists more more than 20 wildcard if entire send App packets affected
than 2.5 seconds seconds BS every second
3. LOF LOF defect No LOF defect Major RAI (3) RSIP force Stop RTP/RTCP AIS/2M if all TS
persists more more than wildcard if entire send App packets affected
than 2.5 seconds 20seconds BS every second
4. HBER 5 consecutive 5 consecutive Major RAI (3) RSIP force Stop RTP/RTCP AIS/2M if all TS
(BER >10-3) Severely Errored Seconds with wildcard if entire send App packets affected
Seconds with BER 10-3 BS, disconnect every second
SES ISDN data link
5. RAI RAI is declared RAI is cleared Minor Stop RTP/RTCP AIS/2M if all TS
(yellow) when bit #6 of when bit #6 of at send App packets affected
all channels has least one channel every second
been zero for at is non- zero for a
least 335 msec. period of less
than 1 sec.
6. HSLIP >30 slips in less An hour with Minor
than an hour less than 30 slips
7. LSLIP >5 slips in less 24 hours with Warning
than 24 hours less than 5 slips
8. ISDN link LAP-D LAP-D re- Minor
down disconnects the connects the
T1, and no IP or PSTN alarm
link loss and no on corresponding
AS down alarm T1 or IP link loss
and no or AS down
maintenance on alarm or
corresponding maintenance on
E1 and no corresponding
maintenance on E1 or
MG maintenance on
MG

No. Alarm Alarm On Alarm Off Default Generate Switched Static channels Far End I-Gate
Type conditions conditions Severity backward channels consequent Alarm
alarm consequent actions consequent
towards actions action
PSTN
(Static Trunking
switch only)
9. ISDN link LAP-D measures LAP-D measures Warning
congested congestion normal
conditions on conditions on
or ISDN link is
down or PSTN
alarm on
corresponding
T1 or IP link loss
or AS down
alarm or
maintenance on
corresponding
T1 or
maintenance on
MG.
NOTES
1. Alarm classification may be changed by configuration
2. AIS/2MB should be injected only if all time slots are configured in trunk static
trunking mode and entire far-end trunk time slots are failed.
3. RAI and RMFR indications for E1 spans shall be transmitted to the near-end PSTN
switch immediately. For DS1, RAI is injected to the PSTN switch after the
integration period (2.5 seconds). RAI signal shall be sent to the PSTN switch for at
least one second.

6.2.5. PSTN Alarms Detailed Description
6.2.5.1. E1 PSTN-side Alarms

The E1 PSTN-side alarms include the following:
Loss Of Signal (LOS) -- see Table 6-3
Loss Of Frame (LOF) -- see Table 6-4
High Bit Error Rate (HBER) -Table 6-5
Alarm Indication Signal (AIS) - Table 6-6
Low Bit Error Rate (LBER) - Table 6-7
Remote Alarm Indication (RAI) - Table 6-8
High CRC error counts (HCRC) - Table 6-9
CRC Multi-frame synchronization loss (CRC-MFR) - Table 6-10
Loss of Multi Frame alignment (MFR) - Table 6-11
Remote Multi-frame Alarm Indication (RMFR) - Table 6-12
High Slip - Table 6-13
Low Slip - Table 6-14
Loss of Incoming Signal Failure (LOF) -- Table 6-15
Loss of Frame Alignment Failure (LOF) - Table 6-16
Alarm Indication Signal Failure (AIS) - Table 6-17
Remote Alarm Indication (RAI) - Table 6-18
High Bit Error Rate (HBER) - Table 6-19

Table 6-3: Loss Of Signal (LOS)

Alarm Parameter Description
Alarm declaration: G.775 paragraph 4.2: "A LOS defect at 2048 kbit/s is detected when the
incoming signal has "no transmission" i.e. when the signal level is less
than or equal to 9 dB below nominal for N consecutive pulse interval
where 10≤N≤255".
If Trunk alarm delay is greater than 0, consequent actions including
reporting to VerazView-xMS are delayed accordingly. The clock
selection algorithm is informed immediately.
Alarm clear: The LOS defect is cleared when the incoming signal has "transitions"
i.e. when the signal level is greater or equal to a signal level of 9 dB
below nominal, for N consecutive pulse intervals, where 10≤N≤255.
If Trunk alarm delay is greater than 0, the alarm clearance is delayed
accordingly.
Default severity: Major (configurable)
Alarm Consequent Upon detection of LOS defect:
Actions: • All BER and SLIP counters will be cleared.
• Inform the clock select mechanism to update its database and change
clock if necessary. This action is performed immediately upon the
alarm detection.
Upon alarm (failure) declaration (after integration period)
• Check which MGCP channels are in the faulty trunk and if there are
any, send an RSIP force message to the MGC with faulty TDM
channels End Point names, using wildcards. When the alarm is
cleared, it will send RSIP restart messages to the MGC with the End
Point names of the TDM channels to be recovered.
• Stop sending RTP/RTCP packets.
• Start sending App Alarm packets for all static trunking channels
every second to the relevant far-end destinations
• IUA service and ISDN link are handled.
• CCS service and CCS links are handled.
• Update terminal status and send traps to all registered VerazView-
xMS stations. Change terminal top most alarm according to priority
tree
• The appropriate line interface LED of the card will show red

Table 6-4: Loss Of Frame (LOF)

Alarm declaration: Frame alignment will be assumed lost when three consecutive incorrect
frame alignment signals have been received. Loss of Frame alignment
can also be declared in response to failure to achieve CRC multi-frame
alignment in accordance with G.706, paragraph 6.4.2.
reporting to VerazView-xMS will be delayed accordingly.
Alarm clear: Basic frame alignment is assumed to recover when the following
sequence is detected:
• The presence of correct frame alignment signal
• The absence of the frame alignment signal in the following frame
detected by verifying that bit 2 of the basic frame is a 1
• The presence of the correct frame alignment signal in the next frame
If Trunk alarm delay is greater than 0, the alarm clearance will be
delayed accordingly.
Default severity: Same as LOS
Consequent action Same as LOS
Table 6-5: High Bit Error Rate (HBER)

Alarm declaration: Under the following conditions:
• 5 consecutive severely errored seconds (SES)
• SES criteria (more than 10-3 errors)
• If bit stream includes CRC: failed CRC counter > 805.
• For bit stream without CRC: number of frame errors >28
errors/second.
Alarm clear: 5 consecutive seconds with BER less than 10-3.
Note: BER counter is cleared during higher layer defects (LOS, LOF,
AIS).
Default severity: Same as LOS
Consequent action: Same as LOS

Table 6-6: Alarm Indication Signal (AIS)

Alarm declaration: AIS alarm goes "ON" when an unframed "ALL ONES" signal is
received on the PCM path for the duration of two frames (250 μsec).
reporting to VerazView-xMS will be delayed accordingly.
Alarm clear: AIS alarm goes "OFF" if no alarm condition exists. G.775, paragraph
5.2: "The defect is cleared when each of two consecutive double frame
periods contain three or more zeros or when Frame Alignment Signal
(FAS) has been found".
If Trunk alarm delay is greater than 0, the alarm clearance will be
delayed accordingly.
Indication method: Same as LOS
Default severity: Minor
Consequent action: Same as LOS
Table 6-7: Low Bit Error Rate (LBER)

Alarm declaration: One two-minute interval with BER in the range of 10-6 to 10-3. Bit stream
without CRC formats: 2 consecutive minutes having 3 or more frame
errors per minute.
Bit stream with CRC format: 2 consecutive minutes having 120 < CRC
error count per minute.
Bit stream without CRC format: 2 consecutive minutes having 3 < frame
error count per minute.
Alarm clear: One 2-minute interval with BER less than 10-6.
Note: BER counter is cleared during higher layer defects (LOS, LOF, AIS).
Consequent action: Update terminal status and send trap to all registered VerazView-xMS
stations.
Change terminal top-most alarm according to priority tree.

Table 6-8: Remote Alarm Indication (RAI)

Alarm declaration: Far-end equipment indicates loss of frame alignment by activating the
remote alarm indication (Bit 3 in TS0 of frame not containing frame
alignment signal). Activation of incoming RAI alarm will be delayed for
30-50 msec.
Alarm clear: RAI alarm is cleared if bit 3 in TS0 is "0". The RAI alarm will be set for at
least one second.
Consequent actions: Checks which MGCP channels are in the faulty trunk and if there are any,
sends an RSIP force message to the MGC with faulty TDM channels End
Point names, using wildcards. When the alarm is cleared, it will send RSIP
restart messages to the MGC with the End Point names of the TDM
channels to be recovered.
For Static Trunking only:
Start sending FE-RAI App Alarm packets for all static trunking channels
every second to the relevant far-end destinations.
Update terminal status and send trap to all registered VerazView-xMS
stations.
The Amber LED on the line interface card will be activated.
Depending on the alarm severity, the appropriate alarm LED will be lit.
Table 6-9: High CRC error counts (HCRC)

Alarm declaration: This alarm is issued only for bit streams that include a CRC field. High
CRC Error alarm is detected if the CRC error count in a one-second
interval exceeds 914 errors.
Alarm clear: On detection of such an event, search for frame alignment is initiated.
Default severity: Major
Consequent actions: Update terminal status and send trap to all registered VerazView-xMS
stations.
Change terminal top most alarm according to priority tree

Table 6-10: CRC Multi-frame synchronization loss (CRC-MFR)

Alarm declaration: This alarm is issued only for bit streams that include a CRC field. CRC-
4 multiframe alignment is lost (entering the Out of MFA state) if three
consecutive multiframes contain errored multiframe alignment signals
(MFAS). An errored MFAS is defined as: "an MFAS with errors in one
or more of the six MFAS bits (001011) in a multiframe".
Alarm clear: CRC multiframe alignment is deemed to have occurred if at least two
valid CRC multiframe alignment signals can be located within 8 ms, the
time separating two CRC multiframe alignment signals being 2 ms or a
multiple of 2 ms.
Consequent action: Update terminal status and send trap to all registered VerazView-xMS
stations. Change terminal top-most alarm according to priority tree.
Table 6-11: Loss of Multi Frame alignment (MFR)

Alarm declaration: Multiframe alignment is assumed to have been lost when two
consecutive multiframe alignment signals have been received with an
error (i.e. all the bits in TS 16 are in state 0).
The E1 integration period is used before consequent actions and
VerazView-xMS reporting are performed.
The received TS#16 "abcd" bits are ignored when MF alignment is lost.
Alarm clear: Multiframe alignment is assumed to have recovered when at least one
bit in state 1 is present in time slot 16 Frame 0 bits 1-4. The MF alarm
is cleared after the E1 integration period.
The reading of the signaling bits is started again when the MF
alignment is recovered only if the MFR alarm is off.
Consequent actions: Inject RMFR towards the near end PSTN switch.
Send alarm notification to VerazView-xMS systems and change
terminal top-most alarm according to priority tree.
The Red LED is activated on the Line Interface card

Table 6-12: Remote Multi-frame Alarm Indication (RMFR)

Alarm declaration: A PSTN switch indicates loss of multiframe alignment by activating the
Remote Multiframe Alarm Indication (bit 6 in TS16, Frame 0)
Alarm clear: Deactivation of TS 16, frame 0, bit 6.
Consequent action: Send alarm notification to VerazView-xMS systems and change
terminal top-most alarm according to priority tree.
The Amber LED is activated on the Line Interface card.
Table 6-13: High Slip

Alarm declaration: More than 30 slip events per one hour
Alarm clear: Less than 30 slip events per one hour
Note: slip counter is reset during LOS, LOF and AIS defects
Default severity Minor
Consequent action: Trap is sent to the registered VerazView-xMS stations
Table 6-14: Low Slip

Alarm declaration: More than 5 slip events per 24 hours
Alarm clear: Less than 5 slip events per 24 hours
Note: slip counter is reset during LOS, LOF and AIS defects
Default severity Trap is sent to the registered VerazView-xMS stations
Consequent action: None

6.2.5.2. DS1 (T1) PSTN-side Alarms

The DS1 (T1) PSTN-side alarms include the following:
Loss Of incoming Signal Failure (LOS) - Table 6-15
Loss Of Frame alignment Failure (LOF) - Table 6-16
Alarm Indication Signal failure (AIS) - Table 6-17
Remote Alarm Indication (RAI, "Yellow") - Table 6-18
High Bit Error Rate (HBER) - Table 6-19
Note: High Slip and Low Slip are identical to E1 (see Section 6.2.5.1, "E1
PSTN-side Alarms").

Table 6-15: Loss Of incoming Signal Failure (LOS)

Failure declaration: LOS failure is declared when the LOS defect persists for 2.5 sec.
Failure clear: An existing LOS failure is cleared when LOS defect is absent for more
than 20 sec.
Consequent actions: Same as for E1 LOS except RAI injection towards the PSTN switch
which is performed after the integration period.
Table 6-16: Loss Of Frame alignment Failure (LOF)

Failure declaration: LOF failure is declared when the LOF defect persists for 2.5 sec, except
when the AIS defect or failure is present.
Failure clear: An existing LOF failure is cleared when an AIS failure is declared, or
when a valid framing is detected for 10 seconds.
Table 6-17: Alarm Indication Signal failure (AIS)

Failure declaration: AIS failure is declared when the AIS defect persists for a user
programmable time of 2.5 sec.
Failure clear: An existing AIS failure is cleared when the AIS defect is absent for 20
sec.
The red LED is lit on the Line Interface card.

Table 6-18: Remote Alarm Indication (RAI, "Yellow")

Alarm declaration: A far-end equipment device indicates loss of frame alignment by
activating the remote alarm indication. In the SF mode, far-end failure
is declared when bit #6 on all channels has been zero for at least 335
msec.
In the ESF mode, far-end failure is declared if the Yellow alarm signal
pattern occurs in at least 7 out of 10 contiguous 16 bit pattern intervals.
Alarm clear: An RAI alarm is cleared as soon as the DS1 terminal determines that it
is no longer receiving an RAI signal from the far-end.
• In the SF mode, far-end failure is cleared when bit #6 of at least one
channel is non-zero for a period T, where T is usually less than 1
second and always less than 5 seconds.
• In the ESF mode, the far-end failure is cleared if the Yellow alarm
signal pattern does not occur in 10 contiguous 16 bit pattern
intervals.
Consequent actions: Checks which MGCP channels are in the faulty trunk and if there are
any, sends an RSIP force message to the MGC with faulty TDM
channels End Point names, using wildcards. When the alarm is cleared,
it will send RSIP restart messages to the MGC with the End Point
names of the TDM channels to be recovered.
For Static Trunking only:
Start sending FE-RAI App Alarm packets for all static trunking
channels every second to the relevant far-end destinations
Update terminal status and send trap to all registered VerazView-xMS
stations.
The Amber LED on the line interface card will be activated.
Depending on the alarm severity, the appropriate alarm LED will be lit.

Table 6-19: High Bit Error Rate (HBER)

Alarm declaration: 5 consecutive Severely Errored Seconds with SES criteria:
(more than 10-3).
If bit stream includes CRC field (ESF):
CRC counter > 320
For bit stream without CRC (SF):
No. of frame errors > 8 errors/second.
Alarm clear: 5 consecutive seconds with BER less than 10-3.
Consequent actions: Same as for LOS
6.2.5.3. High Slip

Same as for E1
6.2.5.4. Low Slip

Same as for E1

6.3. ISDN PRI Signaling Alarms

ISDN data links are supported on the D-channel of E1/DS1 facility (usually 16th
channel of E1 or 24th channel of DS1). The SG elements in I-Gate terminate the
second layer of ISDN PRI signaling (LAP-D layer). The Q.931 messages are
transferred to the MGC using a dedicated IUA protocol from the SIGTRAN protocol
suit. The SCTP provides transport layer functionality between SG in I-Gate and ASP
in MGC. The ISDN PRI alarms correspond to the failures on data links between I-
Gate and peer PBX/Public exchanges. The failures in connection to the ASP are
described in Section 6.6.
The ISDN alarms are part of E1 Alarm Priority Tree (see Figure 6-2) and DS1
Alarm Priority Tree (see Figure 6-3).
The ISDN alarms include the following:
ISDN Link Down (see Table 6-20)
ISDN Link Congested (see Table 6-21)

Table 6-20: ISDN Link Down

Alarm declaration: Alarm is declared when LAP-D disconnects the ISDN data link while
not one of the following events occurs: PSTN alarm, or IUA AS down,
maintenance shutdown for specific E1/DS1 span or entire MG
maintenance shutdown.
Alarm clear: Alarm is cleared when LAP-D connects the ISDN data link; or one of
the following events occurs: PSTN alarm, IUA AS down failure,
maintenance shutdown for the specific E1/DS1 span or MG
maintenance shutdown or operator removes the link from configuration.
Consequent actions: Trap is sent to the registered VerazView-xMS stations
Table 6-21: ISDN Link Congested

Alarm declaration: The flow control of LAP-D measures congestion on the ISDN data link.
Alarm clear: Flow control of LAP-D measures normal conditions on ISDN data link,
or LAP-D disconnects the ISDN data link, or one of following events
occurs:
PSTN alarm, IP network link loss, IUA AS down failure, maintenance
shutdown for the specific E1/DS1 span or MG maintenance shutdown.
Consequent actions: Trap is sent to the registered VerazView-xMS stations

6.4. IP Network Interface Alarms

The IP Interface alarms supported in I-Gate 4000 EDGE include:
Ethernet Link Failure Alarms
Ethernet Link Auto-negotiation failure
PPP/MLPPP Alarms
MGC Communication Loss Alarm
Static Trunking alarms (Far-End terminal alarms)
IUA alarms
H/W failure
Ethernet Link failure
Auto-negotiation failure
Rate failure
(Half duplex)
Figure 6-4: IP network side alarm priority tree

6.4.1. IP Network Ethernet Link Failure Alarms

The following alarm types may occur to any of the six 100BaseT interfaces (3 per
BPSM or XPSM module) independent of the activity state of the interfaces (active
or standby).
6.4.1.1. Ethernet Link Failure

Table 6-22: ISDN Link Congested
Alarm declaration: Ethernet link failure is informed when a 100BaseT link is physically
disconnected (LOS).
Alarm clear: Link is physically connected.
Consequent actions: Card redundancy switchover is performed if the redundant card is
configured, licensed and not faulty and if the number of faulty Ethernet
links in the redundant card is smaller. "Ethernet Link failure" trap is
sent towards the xMS.
6.4.2. Ethernet Link Auto-Negotiation Failure

The I-Gate 4000 EDGE supports the auto-negotiation procedure as defined in IEEE
802.3-2000 for 100BaseT interface. Using the auto-negotiation procedure, Ethernet
switches select the Ethernet link rate (10Mbit/s and 100 Mbit/s) and the duplex
mode (full/half).
The auto-negotiation procedure is automatically activated at initialization and after
every link failure recovery. If the procedure fails to select the correct rate (100
Mbit/s) or the correct duplex mode (full), an alarm is raised. The procedure will
continue indefinitely until a success is achieved. The alarm is cleared immediately
after that.
The following alarms may occur and declared as a result of the link auto negotiation
procedure which shall take place after card initialization, card or link adding in run-
time configuration and after every link failure recovery.

6.4.2.1. Link is in half-duplex mode (Auto-Negotiation failure)

Alarm declaration: Auto-negotiation procedure terminated with half-duplex mode. The
duplex mode is read by the S/W from the PHY device after
initialization and in addition interrupt is delivered to the S/W after any
status change in order to re-check the duplex mode.
Alarm clear: Auto-negotiation procedure terminated with full-duplex mode..
Consequent actions: IP packets are not sent to the faulty link.
6.4.2.2. Link rate is 10 Mb/s

Alarm declaration: Auto-negotiation procedure terminated with rate of 10 Mb/s. The rate
(10/100) is read by the S/W from the PHY device after initialization and
in addition interrupt is delivered after any status change in order to re-
check the rate.
Alarm clear: Auto-negotiation procedure terminated with rate of 100 Mb/s.
Consequent actions: IP packets are not sent to the faulty link.

6.4.3. PPP/MLPPP ALARMS
6.4.3.1. PPP link alarm

Alarm declaration: PPP link is down (link is down after echo-interval X retr-num seconds
without replies)
Alarm clear: PPP link is up
Consequent actions: None
6.4.3.2. MLPPP link alarm

Alarm declaration: MLPPP link is down (declared when all related PPP links are down)
Alarm clear: MLPPP link is up
Consequent actions: None

6.5. Switched MG Alarms
6.5.1. MGC Communication Loss Alarm

The MGC Communication Loss alarm includes the following:
MGC Not Responding
MGC Connection Re-establishment
MGC Has Changed
Available channel ratio below threshold
6.5.1.1. MGC Not Responding

The MG detects that the MGC does not respond and acts upon this event according
to MGCP. It informs the xMS but does not stop the calls.
The I-Gate 4000 EDGE sends a trap to VerazView-xMS for this action indicating,
"Communication with the Call Agent failed". This message is sent when the End
Point enters the "disconnected state" after all retries.
Severity: Major
6.5.1.2. MGC Connection Re-establishment

The MG detects that the MGC (actually any MGC) responds and acts upon any
notification sent according the MGCP 1.0. If another Call Agent answers or sends
commands, MG acts as usual and informs the xMS of the new Call Agent.
If the Call Agent responds after the disconnected state, disconnected method RSIP is
sent to Call Agent.
I-Gate 4000 EDGE sends a Trap to the xMS for this action indicating that the
communication with MGC is recovered.

6.5.1.3. MGC Has Changed

As soon as the MG detects that a different MGC controls it (with a different
configured IP address) the MG informs the operator by sending a brief event.
6.5.1.4. Available channel ratio below threshold

This alarm is raised per MG when the ratio of switched TDM channels available for
traffic from the total number of the MG's switched channels is below the configured
"Available channel low ratio".
The alarm is cleared when the ratio of switched TDM channels available for traffic
from the total number of the MG's switched channels is above the configured
"Available channel high ratio".
Default severity: Warning

6.6. Static Trunking (Far-End terminal) alarms

In the static trunking facility there is no external controller (such as MGC), which
collects information regarding the availability of the path and elements involved in
the transportation of the channel. Furthermore, some of the endpoints connected by a
static trunking channel are limited in their ability to detect a failure or an error in the
traffic transportation (as opposed to signaling points which do not have this
limitation).
For error detection and announcement, the RTP/RTCP built-in mechanisms can be
used:
1. An Application RTCP packet
2. A Time-Out mechanism
Three alarm types are defined for static trunking channels:
a) Far-end TDM alarm (see section 6.6.1.3.1)
b) Far-end RAI alarm (see section 6.6.1.3.2)
c) Far-end connection loss (see section 6.6.1.3.3)
6.6.1.1. Static Trunking Alarm Principles

Static Trunking status is defined per channel (alarm type) and per destination
group (ok, fail).
A Static Trunking destination status is set as 'failed' if at least one channel is
alarmed.
Static Trunking alarm is defined per destination for a change in destination-
group status.
A detailed report, containing the status of all channels in the destination, is
applied to the VerazView-xMS according to the user request.
A Static Trunking status is set as OK, only if no channel in the destination-group
is alarmed.

Any Static Trunking alarm per channel masked by a higher priority alarm is
deleted.
The default severity of all Static Trunking - alarms (FE_conn_loss or
FE_TDM_alarm) is "warning".
6.6.1.2. Static Trunking alarms priority tree

The following drawing depicts the priority tree of the static trunking far-end alarms
FE_conn_loss
FE_TDM
FE_RAI
Figure 6-5: Far-end alarms priority tree
6.6.1.3. Far-End Alarm Handling
6.6.1.3.1. Far-End TDM Alarm (AIS/LOS/LOF/HBER)
Requirements:
AIS injection to the far-end PSTN side is provided within 2 seconds of the alarm
declaration at the alarm-detecting terminal.
AIS injection to the far-end PSTN side is removed within 2 seconds after the
alarm clearance at the alarm-detecting terminal.

Procedure:
1. If a terminal receives an RTCP APP packet with FE TDM alarm indication it
marks the corresponding TDM channel with an AIS flag.
2. For TDM alarms of one of the following types: LOS, LOF, AIS, HBER a
forward alarm indication is sent to the far-end MG using RTCP APP Packets
every one second. Reference paragraph 6.2.
3. If at least one channel of a specific FE destination is alarmed, a notification is
sent to the xMS.
4. If all TDM channels of an E1/DS1 span are marked with AIS, inject AIS on the
specific span towards the PSTN side.
5. Continue transmission of RTP/RTCP packets to the IP network.
6. Set the status of the channel to FE TDM alarm.
7. When the first RTP/RTCP packet is received for a specific channel, clear the
AIS flag and set off the alarm.
8. If at least one channel of an E1/DS1 span is not alarmed, stop the AIS injection
towards the PSTN side.

xMS
FE TDM alarm
per destination
LOS
(1) (5)AIS
(2) RAI (4) (6)RAI
(7)
RTCP APP packets
(FE TDM alarm) (3)
NE NE FE FE
PSTN TERMINAL TERMINAL PSTN
Switch Switch
Note: The bracketed numbers

indicate the alarm sequence
through the system
Figure 6-6: Far-end TDM alarm handling
6.6.1.3.2. Far-End RAI alarm
Requirements:
RAI injection to the far-end PSTN side is provided within 2 seconds from the
declaration of the alarm at the alarm-detecting terminal
RAI injection to the far-end PSTN side is removed within 2 seconds after the
clearance of the alarm at the alarm-detecting terminal.
Procedure
1. For an RAI alarm, a forward alarm indication is sent to the far-end MG using
RTCP APP Packets every one second. The alarm indication is forwarded
separately for each TDM channel.

2. If a terminal receives an RTCP APP packet with FE RAI alarm indication it

marks the corresponding TDM channel with an RAI flag.
3. If at least one channel of a specific FE destination is alarmed, a notification is
sent to the xMS.
4. If all TDM channels of an E1/DS1 span are marked with RAI, then inject RAI
on the specific span towards the PSTN side.
5. Continue transmission of RTP/RTCP packets to the IP network.
6. Set the status of the channel to FE RAI alarm.
7. When the first usual RTCP packet is received for a specific channel, clear the
RAI flag and set off the alarm.
8. When at least one channel of an E1/DS1 span is not alarmed, stop the RAI
injection towards the PSTN side.
xMS
RAI per span FE RAI alarm

per destination
(5) RAI
(1) RAI (4)
(2) RCTP APP. packets

FE RAI alarm (3)
NE
PSTN
NE FE FE
PSTN
Switch TERMINAL TERMINAL Switch
Note: The bracketed numbers

indicate the alarm sequence
through the system
Figure 6-7: Far-end RAI alarm handling

6.6.1.3.3. Far-End Connection Loss
If no RTP/RTCP packet is received for 30 sec (timeout expired), change the status of
the channel to FE connection loss.
The consequent actions of FE connection loss are:
The corresponding port in the opposite direction stops sending its transmission
to the Far-End. ARP request is sent every few seconds to the far-end destination
(or to the default router if exist).
If at least one channel received from a specific destination is marked with FE
connection loss, an FE connection loss alarm is raised for the entire destination.
While the alarm is set-on, an AIS pattern mark is set on for the corresponding
TDM channel. If all channels of a specific span are marked with AIS, then AIS
signal is injected towards the PSTN switch (6.2.1).
When the connection is rebuilt:
The FE connection loss alarm is cleared when the first RTCP or RTP packet is
received for that channel or an ARP response is received.
When the FE connection alarm is cleared for a channel, the AIS flag for the
specific channel is reset and the transmission of RTP/RTCP packets to the IP
network is resumed.
When at least one channel of an E1/DS1 span is not marked with an AIS flag,
the AIS injection towards the PSTN side is stopped.
When none of the TDM channels of a specific destination are marked with FE
connection loss alarm, the FE connection loss alarm will be removed.

6.6.2. IUA Alarms
6.6.2.1. IUA AS Down

Alarm declaration: SG is informed by every ASP that the last one is inactive or down; or all
SCTP associations to all ASPs are terminated and no IP network link
loss alarm is declared.
Alarm clear: SG is informed by one of the ASPs that the last became active; or IP
network link loss alarm is declared, or operator removes the IUA SG or
MGCP MG from the configuration.
6.6.2.2. Connection to IUA AS congested

Alarm declaration: When SG enters a congestion condition (buffer overflow) on SCTP
associations with active ASP.
Alarm clear: SG returns to normal condition on association with active ASP as result
of ASP switchover or end of corresponding buffer overflow; or
declaration of IUA AS down, or IP network link loss alarm is declared;
or shutdown caused by an operator MG card maintenance; or operator
removes the IUA SG or MGCP MG from the configuration.

6.6.3. IUA and ISDN alarm priority tree

The IUA and ISDN alarms comply with the alarm priority tree of Figure 6-8.
IUA AS down
ISDN link Conn .to AS

down congested
ISDN link
congested
Figure 6-8: IUA/ISDN alarm priority tree
6.6.4. SNTP SERVER ALARMS

The following 3 alarm types are defined for the SNTP feature:
SNTP IP address resolve fail -- DNS server is not responding
SNTP IP address resolve fail -- alias is not existing in the DNS server
No connection with the SNTP server
All SNTP alarms have a "warning" severity

6.7. System Clock Alarms

The System Clock alarms are described in the subsections below.
6.7.1. Primary Clock Failure

Alarm declaration: The configured primary clock is disconnected (LOS defect).
Alarm clear: A valid clock signal is detected
Consequent action: The next priority clock source is selected. If the secondary clock source
is not available then internal clock is selected.
When the primary clock source is recovered from the alarm it becomes
the current clock source.
6.7.2. Secondary Clock Failure

Alarm declaration: The configured secondary clock is disconnected (LOS defect).
Alarm clear: Valid clock signal is detected
Consequent action: If the secondary clock source is the current clock, internal clock is
selected instead.
When the primary or the secondary clock source is recovered from the
alarm it becomes the current clock source.
6.7.3. All clocks Failure

Alarm declaration: All configured clock sources are disconnected (LOS defect).
Alarm clear: When at least one TDM clock source is available (without LOS)
Consequent action: None

6.8. Temperature Alarms

The BPSM/XPSM card has a temperature sensor through which the temperature can
be measured.
Three Temperature thresholds are defined for the temperature reading:
Temp_Thershold_1 (45oC), Temp_Thershold_2 (55oC) and Temp_Thershold_3
(75oC).
6.8.1. System Requirements

The software periodically reads the temperature sensors and executes the following
algorithm:
1. When the temperature of at least one of the cards is above Temp_Threshold_2
then:
Issue command to activate TURBO-ON mode.
Report to VerazView-xMS and raise an alarm (default severity = warning).
Temp
Threshold_3
Turbo On
Threshold_2 + Alarm
Turbo Off
Threshold_1 + alarm off
Time
Start timer_1
Figure 6-9: Turbo activation and related alarm

2. When the temperature of all cards falls below Temp_Threshold_1 then:

Set TURBO-OFF
Report to VerazView-xMS and clear the alarm
3. Report to VerazView-xMS and raise a "High temperature" alarm (default
severity = minor). This alarm is cleared when the temperature of the card falls
below Temp_Threshold_1 (together with the TURBO OFF operation).
Temp
Extreme high temp alarm

High Temp Alarm
Threshold_3
Turbo On
Threshold_2 + Alarm
Threshold_1
Time
Time_Threshold_1
Figure 6-10: High temp. and extreme high temp. alarms
4. When the temperature of at least one card is above Temp_Thershold_3 then:

Report to VerazView-xMS and raise "Extreme high Temp" alarm (default
severity = critical). When the temperature falls to below 75oC, the severity of the
alarms changes from Critical to Warning.

6.9. Equipment Alarms
6.9.1. BPSM/XPSM card

Detection of a BIT failure for BPSM/XPSM card which is protected by a
configured/licensed redundant card causes a switchover to the redundant card. An
alarm with a "minor" severity is declared.
Detection of a BIT failure for a BPSM/XPSM card which has no redundancy causes
an alarm with a "critical" severity to be reported. In addition, in case of such a BIT
failure, the terminal will inject AIS to all affected TDM trunks if possible.
In case of a critical alarm due to BIT failure, wildcard RSIP force messages are sent
to the MGC regarding all affected E1/DS1 spans.
The switching to the redundant card happens automatically upon detection of a
hardware failure in the Working card. The switchover is not revertive.
6.9.2. Power Supply card

This card works in load sharing mode, thus both cards are in "Working" mode.
The alarm severity of a faulty power supply or a power supply which has no input
power or out of range input power is "Minor".
Note: If power supply redundancy is not configured in the configuration map, no
alarm is raised if one of the two power supplies fails.
6.9.3. FAN module

The FAN alarm is raised when at least one fan is not working properly. The default
severity is "Minor".

6.9.4. Card missing and card mismatch

There are 3 types of mismatch between the configuration map and the installed
hardware:
1. Hardware mismatch - E1/T1 span is configured in the map at IfIndex which is
not supported by the H/W (e.g. E1 is configured in IfIndex 105 but BPSM is
installed or XPSM with IC4P are installed).
The following are the possible hardware mismatch cases:
I/O card is not suitable for at least one configured E1/T1 (e.g. E1 at IfIndex
105 is configured while IC4P card is installed).
At least one E1/T1 span is configured in IfIndex 105-120 in a terminal with
Left and/or Right BPSM card (CMG base).
Note: The second case can be specified more generally for future options: A span is
configured in IfIndex while the hardware does not contain a framer for that IfIndex.
2. License to TermId mismatch - the burned Serial Number is not the same as
written in the License key (in the map).
3. Hardware module is missing. The following hardware modules can be declared
as missing along with an alarm (specified in section 6.2)
Second Main card (BPSM/XPSM) -- only if "Main card redundancy" is
configured.
Power supply -- only if "Power supply redundancy" is configured
I/O card -- if no I/O card is installed
FAN tray -- if FAN tray is not installed
When such a mismatch of one of the 3 types (H/W mismatch, H/W missing and
License to TermId mismatch) is detected, an alarm is raised and consequent actions
are taken (as specified further on).

The above alarms are detected and cleared in the following cases:
1. After system start-up including switch to redundant main card (both events)
2. After a configuration run-time change (adding and deleting E1/T1 spans) (H/W
mismatch only).
Note: Adding and removing of the illegal spans will not affect the service status of
the legal spans.
3. After card extraction and hot insertion (H/W Mismatch and H/W Missing alarms
only)
6.9.4.1. Alarm handling Requirements
6.9.4.1.1. License to TermId mismatch

Alarm declaration: When the Serial Number which is burned in the H/W (backplane) is not
equal to the number written in the License key.
Alarm clear: The Serial Number in the H/W and in the License key are the same
Default severity: Critical
Consequent action: 1. Prevent media traffic by simulating TDM alarm for the services of all
spans (as specified for "Disconnect" alarms in item 6.2.5.1). However no
indication is sent to the TDM switch and IPoTDM channels are not
affected.
2. Voice packets are not sent to the far-end GW (RTCP packets including
FE-TDM alarm packets are sent forever).
3. AIS shall be injected towards the PSTN for all spans with only static
trunking + CCS + X-connect channels on them (without switched or
IPoTDM channels).
4. Exit from this state only by reset.

6.9.4.1.2. H/W mismatch alarm

Alarm declaration: The card inventory which is not suitable for the current configuration
map. Two cases are handled:
1. I/O card is not suitable for at least one configured E1/T1 (e.g. E1 at
IfIndex 105 is configured while IC4P card is installed).
2. At least one E1/T1 span is configured in IfIndex 105-120 in a terminal
with Left and/or Right BPSM card.
Alarm clear: The H/W and/or the configuration map are changed so that no
discrepancy exist.
Default severity: Working card (no redundancy available) -- Critical Redundant card --
Minor Source Card (Left or right BPSM, IC4P, IC8P)
Consequent action: Not applicable for the power supply. If protecting card has no H/W
mismatch -- perform switch-over (same as BIT) otherwise:
All not-served spans shall have upper alarm (see item 6.2.5.1)
Channel view: All extra channels are indicated as "upper alarm" .In case
of unmatched BPSM, the media driver handles the extra channels as "not
configured".
No DSP channels are opened by the media driver for static channels in
IfIndex without a matched framer. Received UDP packets to these
channels respond with ICMP port unreachable.
6.9.4.1.3. Missing H/W alarm

Alarm declaration: When one of the listed cards is missing (missing second main card and
missing second power supply are indicated only if redundancy is defined in
the map for these cards)..
Alarm clear: No card is missing
Default severity: Critical for the I/O card, Minor for all other cards. Source card
Consequent action: 1. Main card -- Same as H/W BIT or H/W mismatch in the redundant card.
2. I/O card -- Upper alarm to all spans
3. Power supply and Fan tray - none
6.9.5. H/W failure Derived alarms

If the E1/T1 I/O card is missing or not matched to the configuration map definitions,
all E1/T1 interfaces will have alarm indication with "derived" severity.

6.10. S/W Alarms

Two types of S/W alarms are defined:
CPU usage above the configured percentage: This alarm is set when the CPU
utilization of a card is above the pre-configured percentage for a pre-configured
duration. The alarm will be cleared when the CPU utilization falls below another
pre-configured threshold.
S/W mismatch: This alarm is set when a new S/W is downloaded to the active
BPSM/XPSM card in run-time without applying reset to the terminal (S/W hot
swap). The alarm is cleared when the card is re-initiated using a reset command
or when the entire terminal is re-initiated.
Note: usually this alarm is not raised as the operator will use the "automatic S/W
upgrade" action instead of "activate S/W without reset", which is required only for
debug purposes.
6.10.1. CPU Usage Above Threshold

For every card with CPU, the CPU utilization will be constantly measured. An
hysteresis with pre-configured thresholds will be used in order to prevent alarm
fluctuations. The measurement will be performed and averaged over a pre-
configured time window.
Short name: CPU usage above threshold
Alarm declaration: Average CPU usage is above <HighThr> during the last
<MeasureTime> seconds
Alarm clear: Average CPU usage is below <LowThr> during the last
<MeasureTime> seconds
(Default) severity: Minor
Configuration parameters Config parameters per the entire terminal (system):
(SysInfo): High Threshold (%), [0 to 100],
0 = no alarm
Default = 90%
Low Threshold (%), (LowThr in MIB), [0 to 100], def=80%
Cpu usage Measure Time (seconds), [10 to 300],
default = 60 seconds.

6.11. Event Log

The Event Log is a summary of alarms and events that have occurred in the I-Gate
terminal in recent hours. The Event Log indicates all types of alarms and other
logged events in the system, together with the time and date of their occurrence, the
equipment involved and a brief description of the occurrence.
There are two types of event:
On/Off events: These events are always in 'ON' and 'OFF' pairs. An 'ON' event
is generated by the terminal as a result of the beginning of a specific situation.
An 'OFF' event is generated when the situation is ended or when a higher priority
alarm occurs in the same interface/transmission entity.
One-shot event (spurious event): a one-time event without duration (e.g.
terminal reset).
The terminal events are transmitted as "traps" to all registered VerazView-xMS
stations.
Note: When activation of an alarm requires ignoring another alarm with lower
priority, the I-Gate software generates an "alarm off" event message for the
other alarm.
Event record structure (minimum):

Event name and ID
Event description
Time stamp (Date & Time)
Source (Trunk BS#, Ethernet link etc.)
Event status (ON, OFF, one-time event)
Event severity (CRIT, Major, Minor, Warning, Cleared)

6.11.1. Event Log - Alarms

The alarm section of the report includes the alarms detailed below. The report lists
them in order of time of occurrence, and category: Critical, Major, Minor or
Warning. It is possible to select the degree of severity (critical, major, minor,
warning) for different alarm types via the VerazView-xMS configuration map.
The BPSM or XPSM sends an alarm message (trap) to the VerazView-xMS only
once upon a change of the alarm status.
Clearance of the alarm condition will cause an "alarm cleared" message to be
logged.
Alarm status and other events are reported to the management system.
The events included in this category are:
Transmission alarms - Trunk side alarms
Transmission alarms - IP network side alarms
Transmission alarms - Far End alarms (Trunk Replacement)
System Clock alarms
Signaling link alarms (ISDN/IUA)
Temperature alarms
H/W (BIT) alarms
S/W alarms

6.11.2. Other Logged Events

The additional list added to the Event History Report contains all monitored events
affecting the traffic handling operation of the terminal, which did not raise an alarm.
The events included in this category are:
Map activation operations
Software down-loading
Card extraction and insertion
Clearance of alarm conditions by the operator (ACO)
All user maintenance commands

7
DIP Switch Settings
This chapter describes the Dual In-Line package (DIP) switch settings for the I-Gate
4000 EDGE cards (modules). DIP switch settings are relevant only for the
Processing and Switching modules (BPSM and XPSM). The settings for DIP
switches are typically required for initialization (initial configuration) and/or
debugging (synchronization). Table 7-1 lists the number and names of DIP switches
of the Processing and Switching modules.
Table 7-1: DIP switch blocks of BPSM/XPSM Modules
Module Part No. No. of DIP Switch Blocks Remarks
BPSM S410-013 4 (S2, S3, S4 and S5) E1/T1 interface
XPSM S410-021 4 (S2, S3, S4 and S5) E1/T1 interface
Table 7-2, Table 7-3, Table 7-4 and Table 7-5 show the appropriate DIP switch
settings for the four DIP switches.
Note: The bold text in the following tables indicates the factory-installed
(default) settings.
Table 7-2: DIP switch S5 settings

Switch Function Setting Description
1 Boot type ON Auto boot
4 3 2 1
OFF counting boot
2 Security ON Enable security
OFF Disable security
ON 3 SVM ON Load SVM (rescue)

OFF Load application
S5
4 Disable ON Stop before application init
(enables Test application init).
application Init
OFF Normal Init application.

D I P Sw i t c h S e t t i n g s I-Gate 4000 EDGE Maintenance Manual
Table 7-3: DIP switch S4 settings

1 DSP JTAG chain ON BPSM DSP in chain
OFF DSP chain
4 3 2 1 disconnected
2 DSP JTAG bypass ON BPSM DSP
bypassed
OFF BPSM DSP not
ON
bypassed
S4 3 FPGA JTAG download ON Enabled
OFF Disabled
4 Reserved for Future Use ON NA
OFF NA
Table 7-4: DIP switch block S3 settings

1 Boot Write Enable ON Enabled
OFF Disabled
4
2 Not in use** ON NA
3
OFF NA
2
1
ON
3 CPU watch dog ON Disabled
S3 OFF Enabled
4 Reserved for Future Use ON NA
OFF NA

I-Gate 4000 EDGE Maintenance Manual D I P Sw i t c h S e t t i n g s
Table 7-5: DIP switch block S2 settings

1 Not in use ON NA
OFF NA
4
2 Not in use ON NA
3
OFF NA
2
1
ON
3 Not in use ON NA
S2 OFF NA
4 Not in use ON NA
OFF NA
Note: S2 Switches 1,2,3 and 4 are reserved for future use.

D I P Sw i t c h S e t t i n g s I-Gate 4000 EDGE Maintenance Manual
7.1. BPSM (S410-013)

The BPSM card contains four DIP switch blocks (S2, S3, S4 and S5), as shown in
Figure 7-1.
Figure 7-1: BPSM Module DIP switch locations
7.2. XPSM (S410-021)

The XPSM module contains four DIP switch blocks (S2, S3, S4, and S5), as shown
in Figure 7-2.
Figure 7-2: XPSM Module DIP switch locations

A
Glossary
100 BaseT Fast Ethernet Interface
AC Alternating current
ACO Alarm Cut-Off
AIS Alarm Indication signal
ANSI American National Standards Institute
ARP Address Resolution Protocol
ASP Application Service Provider
AWB AirWay Bill
BER Bit Error Rate
BIT Built In Test
BPSM Basic Processing and Switching Module
BS Bitstream
CCS Common Channel Signaling
CPU Central Processing Unit
CRC Cyclic Redundancy check
CRC-MFR CRC Multi Frame Synchronization Loss
DC Direct current
DCME Digital Circuit Multiplication Equipment
DIP Dual In-Line Process switch
DNS Domain Name System
DS1 Digital Signal 1 (synonymous with T1)
DSP Digital Signal Processor
05050303-01 Veraz Networks Inc. Proprietary A-1

Glossary I-Gate 4000 EDGE Maintenance Manual
E1 2.048 Mbit/s interface

EACM EDGE AC Power Supply Module
EDCM EDGE DC Power Supply Module
ESD Electro-Static Discharge
ETFM EDGE Fan Tray Module
FCC Federal Communication Commission
FE Far End
GB Gigabit
Gbit/s Gigabit per second
GND Ground
H.248 Media Gateway Control Protocol for handling the signaling and
session management
HBER High Bit Error Rate
HCRC High CRC Error Counts
HUB Center of star network topology
H/W Hardware
IC4P 4-Port TDM Network Interface Module
IC8P 8-Port TDM Network Interface Module
ICHP 20-Port TDM Network Interface Module
ICMP Internet Control Massage Protocol
IEEE Institute of Electronic and Electrical Engineering
I/O Input/Output
IP Internet Protocol; Internet Protocol Network
IPoTDM Internet Protocol over Time Division Multiplexing network
ISDN Integrated Services Digital Network
ITU-T Body that has replaced CCITT, now responsible for defining
telephony standards
A-2 Veraz Networks Inc. Proprietary 05050303-01

I-Gate 4000 EDGE Maintenance Manual Glossary
IUA ISDN User Adaptation, a type of signaling

LAN Local Area Network
LAP-D Link Access Procedure (channel-D). Used in ISDN data channel
LBER Low Bit Error Rate
LED Light Emitting Diode
LOF Loss of Frame Alignment
LOS Loss of (incoming) Signal
MDP Mid Plan (motherboard -- part of the chassis)
MEGACO Same as H.248
MGC Media Gateway Controller
MGCP Media Gateway Control Protocol
MLPPP Multi-Link Point-to-Point Protocol
MOS Metal Oxide Semiconductor
MS Multiplex Section
NE Near End
OPS Operator Station
PABX Private Automatic Branch Exchange
PBX Private Branch Exchange
PCB Printed Circuit Board
PDU Power Distribution Unit
PPP Point-to-Point Protocol
PSTN Public Switched Network
RAI Remote Alarm Indication
RAM Random Access Memory
RDI Remote Defect Indication
RMA Returned Materials Approval
05050303-01 Veraz Networks Inc. Proprietary A-3

Glossary I-Gate 4000 EDGE Maintenance Manual
RMFR Remote Multiframe Alarm Indication

RS-232 Recommended Standard 232
RSIP Restart In Progress (for MGCP)
RTP/RTCP Communications Protocols
SF Signal Failure defect
SG Signaling Gateway
SIGTRAN Signaling Transport architecture
SNMP Simple Network Management Protocol
SNTP Simple Network Time Protocol
Softswitch Switching Control Layer
SS7 Signaling System #7
STM-1 Synchronous Transfer Mode (155 Mbit/s interface)
SVM Software Version Management
S/W Software
T1 1.544 Mbit/s interface/rate (US)
TAC Technical Assistance Centers
TDM Time Division Multiplexing
TOH Transport Overhead
TS0 Time Slot Zero
VerazView-xMS VerazView-xMS Fault and Performance Manager
FPM
VBD Voice Band Data
VoIP Voice over Internet Protocol network
WAN Wide Area Network
xMS VerazView-xMS Management Station, the PC containing xMS
application suite
XPSM Expanded Processing and Switching Module
A-4 Veraz Networks Inc. Proprietary 05050303-01

Igate 400 Maintenance Manual

Загружено:

Сведения о документе

Оригинальное название

Авторское право

Доступные форматы

Поделиться этим документом

Поделиться или встроить документ

Параметры публикации

Этот документ был вам полезен?

Это неприемлемый материал?

Авторское право:

Доступные форматы

Igate 400 Maintenance Manual

Загружено:

Авторское право:

Доступные форматы

fJd~íÉ=QMMM=badb=

US Complies with US requirements FCC part 15

A01 01 Apr-06 Ver. Kalypso 5.1.1. Author: JH

2 Safety Precautions ................................................................................... 2-1

3 Repair and Return Procedure ................................................................. 3-1

4 Replacing Modules................................................................................... 4-1

05050303-01 Veraz Networks Inc. Proprietary i

5 Module Redundancy ............................................................................. 5-1

6 System and Network Alarms................................................................... 6-1

ii Veraz Networks Inc. Proprietary 05050303-01

6.2.5.1. E1 PSTN-side Alarms .......................................... 6-17

05050303-01 Veraz Networks Inc. Proprietary iii

6.7. System Clock Alarms ........................................................................ 6-44

7 DIP Switch Settings.................................................................................. 7-1

iv Veraz Networks Inc. Proprietary 05050303-01

1.1. Purpose of this Manual

1.2. Intended Audience

1.3. Referenced Documentation

05050303-01 Veraz Networks Inc. Proprietary 1-1

This page intentionally left blank.

1-2 Veraz Networks Inc. Proprietary 05050303-01

2.1. Handling Precautions

Caution: The following precautions must be observed when handling I-Gate

05050303-01 Veraz Networks Inc. Proprietary 2-1

2.1.1. Handling Printed Circuit Boards (modules)

Please adhere to the following precautions when handling PCBs (modules):

2.1.2. Service Tool Precautions

2-2 Veraz Networks Inc. Proprietary 05050303-01

2.2. Safety Instructions

Caution: For DC powered units, this equipment is designed to permit

05050303-01 Veraz Networks Inc. Proprietary 2-3

2.3. Power Precautions

2.3.1. Applicable to DC powered terminals only

2.3.2. Applicable to AC and DC powered terminals

2-4 Veraz Networks Inc. Proprietary 05050303-01

2.4. BPSM/XPSM Card Battery Replacement

Warning There is a danger of explosion if the battery located on the

Waarschuwing Er is ontploffingsgevaar als de batterij verkeerd vervangen wordt.

Varoitus Räjähdyksen vaara, jos akku on vaihdettu väärään akkuun. Käytä

Attention Danger d'explosion si la pile n'est pas remplacée correctement. Ne la

Warnung Bei Einsetzen einer falschen Batterie besteht Explosionsgefahr.

Avvertenza Pericolo di esplosione se la batteria non è installata correttamente.

05050303-01 Veraz Networks Inc. Proprietary 2-5

Battery instructions (continued)

Aviso Existe perigo de explosão se a bateria for substituída incorrectamente.

¡Advertencia! Existe peligro de explosión si la batería se reemplaza de manera

Varning! Explosionsfara vid felaktigt batteribyte. Ersätt endast batteriet med

2-6 Veraz Networks Inc. Proprietary 05050303-01

2.5. Electrostatic Discharge (ESD) Precautions

Certain tools and test equipment commonly used on electromechanical systems

05050303-01 Veraz Networks Inc. Proprietary 2-7

Use only hand-powered or battery-powered wire-wrap guns in equipment

2.6. Radio Interference Precautions

Warning (CE Standard EN 55022): This is a class A product. In a domestic

2-8 Veraz Networks Inc. Proprietary 05050303-01

05050303-01 Veraz Networks Inc. Proprietary 3-1

3.1. Ordering Replacement Equipment

3-2 Veraz Networks Inc. Proprietary 05050303-01

Date: ____________ RMA Request Form Page ____ of ____

To: Customer Ref:#

Authorized by: Signature:

05050303-01 Veraz Networks Inc. Proprietary 3-3

3.2. Insurance Policy

Date: ________ RMA Request Form Page of