Troubleshooting guide

Trunking
111
Trunk Troubleshooting Tips
 If all the circuits supported by a module or card are out of service, it is likely defective. If
possible, swap the module or card with a known working module or card to confirm.
 For help with diagnosing trunk problems, see “Trunks” on page 203.
 In the System Administration Tool, use the
- Line Quality Measurement Tool to test Loop Start Trunks that are connected to the AX
Controller Card Chassis, Analog Main Board, Analog Option Board, or ASU II.
- Voice Quality Statistics form in combination with NetAlly (must be purchased
separately) to identify voice quality problems and performance trends for IP phones.
Analog Trunks
Table 33: Troubleshooting Analog Trunks
Symptom Possible Cause Corrective Action
System not receiving trunk
calls.
Analog trunk issues. Verify that the analog trunk is OK by using
individual trunk access and testing on the
frame.
.Answer point not programed. Verify SMDR records to see which trunks have
received incoming calls. Verify that the answer
point is programmed correctly and is
functional.
Outgoing calls are dropping
after a couple of minutes into
the conversation.
The system is not receiving
answer supervision from the
central office and is timing out.
If the Central office cannot provide answer
supervision on answered calls go to the CO
Trunk Circuit Descriptors form and change the
value in the field ”fake answer supervision after
outpulsing” to yes.
Unable to dial out on trunk. No dial tone Ensure dial tone is present from Central Office
(CO). You can disable dial tone detection on
the trunk to allow users to dial out on the trunk
in the absence of dial tone.
Calls are connecting to the far
end. Called party can hear
caller, but calling party cannot
hear party at far end.
The system is not receiving
answer supervision
immediately from the Central
Office.
Go to the CO Trunk Circuit Descriptors form
Change the Supervision parameters in the
value field “audio inhibit until answer
supervision after outpulsing” to No.
Trunks are programmed but
are appearing as unassigned
with the STAT location ID
command.
Card has not had the
information downloaded to
update the status of the
trunks.
Download the information to the ASU at an
appropriate time.
Page 1 of 3