Call Fails on the SIP Trunk

The following faults often occur on the SIP 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 intra-office and outgoing prefixes are not configured.
• The trunk data is not configured.

1. See 2 to check that the intra-office and outgoing prefixes are configured.
2. Run the show protocol sip command to check whether the trunk data is configured.

   SIP
   
   
   ---------- ----------- ------------ ------------ ----------- ----------------- -------------- ------------------ 
     Office    IPAddress   DomainName   LocalPort    PeerPort    TransportType     MaxCallNum     DefaultCLDNum1     
   ---------- ----------- ------------ ------------ ----------- ----------------- -------------- ------------------ 
   
   
   
   ====  Command executed success !  ====

   • If If the preceding information is displayed, the intra-office and outgoing prefixes are not configured. Run the config protocol sip officeno officeno domainname domainname peerportpeerport maxcallnum maxcallnum command to configured. The domainname is domain name of a device of the peer office. The officeno is number of an office direction that the trunk belongs to. The peerport is SIP port number of a device of the peer office. The maxcallnum is maximum number of calls.
   • If the intra-office and outgoing prefixes are configured, go to the next step.

3. 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.