Bios self-test, Base code self-test, Field-programmable gate array (fpga) testing – Nortel Networks NN43001-563 User Manual

Page 407: Outgoing calls attempted/completed mismatch

Advertising
background image

Outgoing calls attempted/completed mismatch

407

BIOS self-test

The IP trunk card contains its own VxWorks-based BIOS. At power-up, the
BIOS performs its own initial test of the hardware. These tests cover the
processor, PCI chipset, cache (if installed), and DRAM memory. The results
of the BIOS self-test are displayed on the RS-232 maintenance port.

Base code self-test

The IP trunk card base code performs the following tests:

flash integrity test

PGA read/write test

PC Card controller test (also tests the PCI bus)

timer and DMA tests

DSP test

Field-Programmable Gate Array (FPGA) testing

Before communicating with the system, the 8051XA controller downloads
FPGA and performs tests to check correct programming of the FPGA.

Outgoing calls attempted/completed mismatch

The difference between the attempted and completed outgoing call numbers
should never be less than the sum of the QoS Fallback, Address Translation
fallback, and Calls Rejected fallback (totaled as "Outgoing Fallback"). It
may be more. A caller may release a call before the attempt reaches the
far node, but since the originator released before the call could complete, it
might not even be recorded as an attempt by the remote ITG card.

For example, a user dials a valid ESN AC1 and LOC, but an incorrect
DN (with an incorrect last digit). As soon as the user dials the digit, he or
she realizes the mistake and releases the call. The SETUP message has
already gone to the ITG card, but the call is cleared before the H.323 SETUP
message traversed the IP network, so no call reaches the destination. An
outgoing attempt has been made and cleared, so no fallback occurred and
no call attempt is recorded at the destination.

The main reasons for valid completed call mismatches are:

Time of day that the statistics were last read and cleared may vary.

This is the most common reason for mismatch. For example, although
both ITG cards were read at 10:00, it is important to know if the clocks
are synchronized, and when statistics were last cleared. A one-minute
discrepancy could mean quite a few calls in the difference. Therefore,
the first eight calls of one card may have already been counted for the
other card. The statistics are more reliable when looked at over the day.

"Messages in flight"

Nortel Communication Server 1000

IP Trunk Fundamentals

NN43001-563

01.01

Standard

Release 5.0

30 May 2007

Copyright © 2007, Nortel Networks

.

Advertising