Navigation: Fault Management > Troubleshooting Guide > Trunk Faults >
This topic describes how to troubleshoot a call fails that occurs on the R2 trunk.
Symptom
The following faults often occur on the R2 trunk:
ϒ⁄A busy tone is heard when an incomplete called number is dialed.
ϒ⁄A busy tone is heard when a complete called number is dialed.
Possible Causes
The possible causes are as follows:
ϒ⁄The clock source is not configured.
ϒ⁄The intra-office and outgoing prefixes are not configured.
ϒ⁄The board status is abnormal.
ϒ⁄The trunk circuit is faulty.
ϒ⁄The register type is not MFC.
ϒ⁄The R2 adaptation script is not imported.
Procedure
1.See E1/T1 Trunk Exception to check the clock source is configured.
2.See step 3 and step 4 in Call Fails on the PRA Trunk to check whether the intra-office and outgoing prefixes are configured and whether the board status is normal.
3.Run the show tkc by office no officenocommand to check the trunk circuit status (the value of State field).
ϒ⁄If the status is ISOLATET, run the config cancelisolate board slot slot command to cancel board isolation.
ϒ⁄If the status is FAULT, seeConfiguring Signaling Data to check whether the trunk data is correct.
ϒ⁄If the status is OK, go to the next step.
4.Run the show cassignal command to check whether the register type is MFC (value of RegisterType field).
ϒ⁄If no, run the config modify cassignal casnamecasname registertype mfc command to modify the register type.
ϒ⁄If yes, go to the next step.
5.Check whether the R2 adaptation script has been imported.
6.If the fault still persists, collect detailed fault information and related logs by referring to Collecting and Reporting Fault Information and send them to the service provider.
Parent Topic: Trunk Faults