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

Reminder

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

upgrade

eSight V300R010C00SPC200, 300, and 500 Operation Guide 09

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).
Collecting Signaling Tracing Messages

Collecting Signaling Tracing Messages

You can use the signaling tracing task creation and import functions to collect SIP messages generated during a call.

Creating Signaling Tracing Tasks

After you set related information in the eSight and create a signaling tracing task, the eSight delivers trace commands to the NEs to be traced.

Prerequisites

  • The NEs to be traced have been added on the eSight.
  • The NE adaptation package has been installed on the eSight.
  • The current user has been assigned domain-based rights of the related NE objects.
  • You have the Management operations of Signaling Trace rights.

Context

If vMRFP or CloudUSM subscriber trace is required, the corresponding special attribute must be enabled on the CSC3300. That is, select SUPCALLTRACE for SPCATTR. The corresponding special attribute is enabled on the CSC3300 by default.

  • Command for enabling the special attribute: MOD MGW: MGWNAME="MRFPH2481", TRNST=SCTP, SPCATTR=SUPCALLTRACE-1;
  • Command for disabling the special attribute: MOD MGW: MGWNAME="MRFPH2481", TRNST=SCTP, SPCATTR=SUPCALLTRACE-0;
    NOTE:

    MRFPH2481 and SCTP in the preceding command are used as an example only. Replace them with the actual value.

    • MGWNAME (MGW name): This parameter identifies the MGW data record to be modified. To obtain the value of this parameter, run LST MGW.
    • TRNST(Transport protocol): This parameter specifies a transmission layer protocol for transmitting H.248 messages between the MGC and the MGW.
    • SUPCALLTRACE (supporting call message trace) is used to control whether ADD messages of the Ia/Ix interface (H.248) contain the IMPU of the calling and called parties. By default, the ADD messages do not contain the IMPU.

Procedure

  1. Choose Resource > Collaboration > Network Element Device Management from the main menu.
  2. Choose Network Element Device Management > Unified Communications > Signaling Trace from the navigation tree on the left.
  3. On the Signaling Trace page, click Add.
  4. Creating a signaling trace task.

    Figure 13-6 shows the status changes of tasks on eSight.

    Figure 13-6 Status changes of tasks on eSight
    • The instant trace task runs immediately and is in the Running state.
    • Before the scheduled trace task is executed, it is in the Initialized state. You can manually start this task. After the command for starting the trace task is delivered, the task is in the Starting state during interaction setup between the eSight and NE.
    • The trace task is in Running state after the interaction between the eSight and NEs is set up.
    • For a trace task in Starting state, if the communication between the eSight and NEs becomes abnormal (for example, when the NEs are disconnected from the eSight), the task stops automatically and is in Suspended state.
    • You can manually stop a trace task in Running state. After the command for stopping the task is sent, the task is in Stopping state and retains this state before the interaction between the eSight and NEs is terminated.
    • After a trace task is stopped manually or automatically, the task is in Finished state. You can restart a task in Finished state, the task is in Starting state after restart.
    NOTE:

    If the management objects of the current user's role change after the task is created (that is, management rights of certain NEs are not included in the current task), you are not allowed to start this task.

Importing Signaling Tracing Files

You can create a trace task or import the raw signaling trace file of NEs to eSight to view signaling trace data. Imported signaling trace data can be used for fault analysis and location.

Prerequisites

  • The original signaling tracing file exists. The raw signaling trace file exists. For details about how to export the raw signaling trace file, see Export trace tasks.
  • You have the Management operations of Signaling Trace rights.

Context

  • The eSight supports *.tmf and *.ptmf file types.
  • You can import only one *.tmf or *.ptmf file at a time.

Procedure

  1. Choose Resource > Collaboration > Network Element Device Management from the main menu.
  2. Choose Network Element Device Management > Unified Communications > Signaling Trace from the navigation tree on the left.
  3. On the Signaling Trace page, click Import.
  4. Importing signaling tracing files.

  5. Click Confirm.
Translation
Download
Updated: 2019-09-12

Document ID: EDOC1100044378

Views: 71949

Downloads: 378

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