Outgoing calls attempted/completed mismatch 409Base code self-testThe 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 testField-Programmable Gate Array (FPGA) testingBefore communicating with the system, the 8051XA controller downloadsFPGA and performs tests to check correct programming of the FPGA.Outgoing calls attempted/completed mismatchThe difference between the attempted and completed outgoing call numbersshould never be less than the sum of the QoS Fallback, Address Translationfallback, and Calls Rejected fallback (totaled as "Outgoing Fallback"). Itmay be more. A caller may release a call before the attempt reaches thefar node, but since the originator released before the call could complete, itmight 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 incorrectDN (with an incorrect last digit). As soon as the user dials the digit, he orshe realizes the mistake and releases the call. The SETUP message hasalready gone to the ITG card, but the call is cleared before the H.323 SETUPmessage traversed the IP network, so no call reaches the destination. Anoutgoing attempt has been made and cleared, so no fallback occurred andno 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, althoughboth ITG cards were read at 10:00, it is important to know if the clocksare synchronized, and when statistics were last cleared. A one-minutediscrepancy could mean quite a few calls in the difference. Therefore,the first eight calls of one card may have already been counted for theother card. The statistics are more reliable when looked at over the day.• "Messages in flight"This ranges from trivial to extreme. In the extreme case, if a CONNECTmessage is delayed several tenths of seconds (or even seconds) bytraffic bursts, the snapshot may occur while the CONNECT messageis still traversing the network. Therefore, one or more calls is stillunaccounted for. In the trivial case, even in a lightly loaded network, itNortel Communication Server 1000IP Trunk FundamentalsNN43001-563 02.01 StandardRelease 5.5 21 December 2007Copyright © 2007, Nortel Networks.
