Call Fails on the R2 Trunk

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.

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.

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.
   1. Run the following command to check whether the R2 adaptation script has been imported:

      show line send id <0-254>
      show line report id <0-254>
      show register send id <0-254>
      show register report id <0-254>

   2. Check whether the number of displayed lines is the same as that of command lines corresponding to the script.
      • If no, delete the configuration and re-import the adaptation script. To delete the configuration, run the following commands:

        config delete line send id <0-254>
        config delete line report id <0-254>
        config delete register send id <0-254>
        config delete register report id <0-254>

      • If yes, go to the next step.

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.