No relevant resource is found in the selected language.

This site uses cookies. By continuing to browse the site you are agreeing to our use of cookies. Read our privacy policy>Search


To have a better experience, please upgrade your IE browser.


CloudEC V600R019C00 Troubleshooting (Enterprise On-premises, Convergent Conference)

Rate and give feedback:
Huawei uses machine translation combined with human proofreading to translate this document to different languages in order to help you better understand the content of this document. Note: Even the most advanced machine translation cannot match the quality of professional translators. Huawei shall not bear any responsibility for translation accuracy and it is recommended that you refer to the English document (a link for which has been provided).
Fault Location

Fault Location

The call service is the main service of the SC and consists of H.323 call and SIP call services. Different call services use different protocols.

Background Information

The session management and call control modules interact through messages and function invocation. Key processes such as call parsing, connection, and disconnection are implemented through message interfaces. Other interaction processes during a call are implemented through messages or function invocation. When the caller and callee use the same protocol, for example, H.323 or SIP, and media trunking is not required, other non-key interaction processes are implemented through function invocation. When the caller and callee use different protocols or media trunking is required, other non-key interaction processes are implemented through messages.

During a call, call control is not related to the call control messages from the peer end and the interaction method between session management. Session management provides a unified message interface processing function to be invoked by call control. Then, call control implements the detailed process.

Locating the Fault

The NE where a call fault occurs can be located quickly through packet capture.

  1. When initiating a call, check whether the call data is successfully sent to the SC.
  2. When a call is connected, check whether the call is rejected or the SC does not properly send the call data to the callee.
  3. If the fault occurs on the SC, filter the call in logs or trace files and check the fault cause.

    1. To obtain trace files, in the SC CLI, run the trace traceon module all level debug command, obtain the trace files, and save them.
    2. In the captured packets, call-id of the call can be obtained. Filter out call-id in trace logs and find Send msg to CONTROL:CallRspMsg.

      In the trace log, the error code is displayed after the word "Result". Locate the fault based on the error code.

Updated: 2019-08-07

Document ID: EDOC1100059098

Views: 19502

Downloads: 12

Average rating:
This Document Applies to these Products
Related Documents
Related Version
Previous Next