The eSpace USM processes registration and voice call services for users. When a service fault occurs, you need to collect fault information on the eSpace USM.
Fault Information Collection Rules
Information | When to Collect |
|---|---|
Product version number | Collect the product version number when any fault occurs. |
System information | Collect system information when any fault occurs. |
Configuration information | Collect configuration information when any fault occurs. |
SIP message | SIP messages enable you to clearly understand how a call is established, including media negotiation information between the calling and called parties, whether call signaling is complete, and the party that releases the call, helping you find the fault cause. Collect SIP messages based on the terminal IP address when a service fault such as a call fault occurs on a terminal. |
E2E message | Collect E2E messages when a call fault occurs. |
Host log | Host logs record service processing on hosts. Collect host logs when a service fault occurs. |
Platform logs | Collect platform logs when a system fault such as a restart occurs. |
Black box information | The black box records key events and information during the system running. Collect black box information when a system fault such as a restart occurs. |
Alarm information | Alarms help engineers locate faults intuitively. Collect alarm information when a service fault occurs. |
- If you can log in to the OM server properly using the LMT, you are advised to collect fault information online.
- If the OM process runs abnormally and you cannot log in to the OM server using the LMT, you can collect fault information offline. In offline mode, you can collect only OM logs, system information, and USM web logs. The collection method is the same in online and offline modes.
Collecting System Information, Alarm Information, and Logs
- Log in to the LMT as the admin user.
- Choose .Figure 1 Collecting logs
- Select the modules for which logs are collected, set the time period for collecting logs, enter the user name and password, and click Collect. To collect system information and alarm information, ensure that System Info and Warning Info are selected.
If you do not know which modules need to be selected, select Collect All. If security hardening has been performed, select SafeMode and enter the common user name (such as omu) and password. If security hardening has not been performed, enter the root user name and its password without selecting SafeMode.
Figure 2 Setting the parameters for collecting logs - After the collection is completed, set the path for downloading logs and the logs to download, and click Download.Figure 3 Setting the parameters for downloading logs
Collecting SIP Messages
- Log in to the LMT as the admin user.
- Click the Tracing tab.
- Double-click SIP under the Call Signaling Trace node.
- Set tracing parameters and click OK.
Figure 4 shows the page for setting SIP message tracing parameters.
Figure 4 Tracing SIP messagesThe name of a message tracing file contains the message type, date, and time. You can open the directory for automatically saving files to view saved files. - Repeat an operation that triggers a fault. The system will automatically obtain the tracing messages.
Collecting E2E Messages
- Log in to the LMT as the admin user.
- Click the Tracing tab.
- Double-click E2E Trace under the User Message Trace node.
- Set tracing parameters and click OK.
Figure 5 shows the page for setting E2E message tracing parameters.
- E2ETrace: Use the calling and called numbers of a single call as the index for tracing.
- E2ESample: Randomly select numbers for tracing based on the sampling rate.
Figure 5 Tracing E2E messages - Repeat an operation that triggers a fault. The system will automatically obtain the tracing messages.
Follow-up Procedure
