EasyManua.ls Logo

Vigilant QE20 - Fault Finding; Fault Finding Using VIF, ATA, and PIB Leds; Fault Finding Using ATA and PIB Status Pages

Default Icon
64 pages
Print Icon
To Next Page IconTo Next Page
To Next Page IconTo Next Page
To Previous Page IconTo Previous Page
To Previous Page IconTo Previous Page
Loading...
Document: LT0732 QE20 Fibre Networking User Manual
Issue 1.0 24 May 2023 Page 7-1
7. Fault Finding
Fault Finding Using VIF, ATA, and PIB LEDs
If there is a problem with the networked Speech or WIP VoIP connections, the first
check is to make sure there are no faults at the affected QE20s, with the fibre ring, or
associated equipment.
If the problem is the calls are established and no fault is generated indicating the
VoIP calls failed, but no audio is transferred then check the cable connecting the VIF
PA/WIP signals on the RS485 Network Module to the VIF Module in the Fibre
Network kit at each end of the call.
If the calls are not being established (results in a PA Segment or WIP Segment fault
being generated soon after making the call) the LEDs on the VIF modules and ATA
modules at each end of the audio connection should be checked.
If the VIF “Off Hook” LED is repeatedly turning on for ~0.2 seconds then off for about
1.0 seconds, this indicates that the VIF is trying to make a call, but there is no
voltage on the line from the ATA. Check the cable to the ATA and that the ATA is
powered up and not in faut. If the RJ11 cable has just been replaced (the polarity
may be different), it may be necessary to alter the ATA settings as described in
section 3.8.4. Check that the ATA has an Ethernet connectionits Power LED
should be ON steady, and its Network LED should be ON, with some flickering.
If the VIF “Off hook” LED is repeatedly: turning on, then after ~0.2 seconds the
Connect LED is turning on for ~2.0 seconds then both LEDs turn off for about 1
second, this indicates that the VIF and ATA are trying to make the call, but it is not
being answered. At the QE20 that should be receiving the call check the ATA that is
being called is powered up, has an Ethernet connection its Power LED should be
ON steady, its Network LED should be ON with some flickering, and the RJ-11 cable
connects to the VIF. Check that the receiving ATA is visible on the network - try
pinging or browsing to its IP address with a laptop plugged into a spare Ethernet port
at the same location as the ATA that is unsuccessfully trying to connect. Check the
configuration of the QE20s and ATAs.
Note: if an ATA Power LED is flashing, this may indicate no Ethernet connection, the
ATA is determining its IP address, it is rebooting, or it could not boot up correctly.
Consult the ATA User Guide for an explanation of the flash cadence.
If a PIB VoIP proxy is utilised for the call, the power LED of the PIB should be lit, the
Ethernet Link LED should be flickering if a call is active, and if no call is active it
should at least be lit if there is an Ethernet cable attached. The PIB system fault
LEDs may indicate if a fault is present as well. To get specific diagnostic information
for the VoIP proxy functionality the PIB status web page should be visitedsee
Section 7.2.
Fault Finding Using ATA and PIB Status Pages
Additionally, it is useful to check the voice status page of the web interfaces of each
of the ATAs. This will show if there is a call being attempted, in-progress, and when
there is a connected call, it will show the IP address of the remote ATA or PIB VoIP
proxy.

Table of Contents

Other manuals for Vigilant QE20

Related product manuals