LMT Operation Guide

eSpace U1900 Unified Gateway
V200R003
LMT Operation Guide
Issue 02
Date 2018-12-29
HUAWEI TECHNOLOGIES CO., LTD.

Copyright © Huawei Technologies Co., Ltd. 2018. All rights reserved.
No part of this document may be reproduced or transmitted in any form or by any means without prior
written consent of Huawei Technologies Co., Ltd.
Trademarks and Permissions
and other Huawei trademarks are trademarks of Huawei Technologies Co., Ltd.
All other trademarks and trade names mentioned in this document are the property of their respective
holders.
Notice
The purchased products, services and features are stipulated by the contract made between Huawei and
the customer. All or part of the products, services and features described in this document may not be
within the purchase scope or the usage scope. Unless otherwise specified in the contract, all statements,
information, and recommendations in this document are provided "AS IS" without warranties, guarantees or
representations of any kind, either express or implied.
The information in this document is subject to change without notice. Every effort has been made in the
preparation of this document to ensure accuracy of the contents, but all statements, information, and
recommendations in this document do not constitute a warranty of any kind, express or implied.
Huawei Technologies Co., Ltd.

Address: Huawei Industrial Base
Bantian, Longgang
Shenzhen 518129
People's Republic of China
Website: https://e.huawei.com
Issue 02 (2018-12-29) Huawei Proprietary and Confidential i

Copyright © Huawei Technologies Co., Ltd.
LMT Operation Guide Contents
Contents
1 Overview......................................................................................................................................... 1
2 Lock .................................................................................................................................................. 4
3 Device .............................................................................................................................................. 5
4 Version ............................................................................................................................................ 7
4.1 Upgrade ........................................................................................................................................................................ 8
4.2 Rollback ........................................................................................................................................................................ 8
4.3 Load License ................................................................................................................................................................. 9
4.4 Patch ........................................................................................................................................................................... 10
4.5 Voice File .................................................................................................................................................................... 11
4.6 Configuration File Management ................................................................................................................................. 13
4.7 Data Upgrade for the Same Model ............................................................................................................................. 13
4.8 Cross-Model Data Upgrade ........................................................................................................................................ 14
5 Command Delivery..................................................................................................................... 15
5.1 Command Tree............................................................................................................................................................ 15
5.1.1 Command Tree Structure ......................................................................................................................................... 15
5.1.2 Command Tree Operations ...................................................................................................................................... 16
5.2 Script Load ................................................................................................................................................................. 19
6 Alarm Management .................................................................................................................... 20

7 Log Management ......................................................................................................................... 24
7.1 Signaling Collect ........................................................................................................................................................ 24
7.1.1 SIP ........................................................................................................................................................................... 25
7.1.2 QSIG ........................................................................................................................................................................ 28
7.1.3 PRA ......................................................................................................................................................................... 31
7.1.4 BRI........................................................................................................................................................................... 34
7.1.5 SS7 ........................................................................................................................................................................... 37
7.1.6 R2 ............................................................................................................................................................................ 40
7.1.7 Subscriber ................................................................................................................................................................ 42
7.2 Run Log ...................................................................................................................................................................... 45
7.3 Operate Log ................................................................................................................................................................ 47
7.4 Call Log ...................................................................................................................................................................... 49
Issue 02 (2018-12-29) Huawei Proprietary and Confidential ii

LMT Operation Guide Contents
7.5 Debug Log .................................................................................................................................................................. 52

7.6 Call Analyzer .............................................................................................................................................................. 57
7.7 Control Block ............................................................................................................................................................. 60
8 Information Collection............................................................................................................... 62
8.1 Device Information ..................................................................................................................................................... 63
8.2 Blackbox Information ................................................................................................................................................. 63
8.3 Trunk Information ....................................................................................................................................................... 64
8.4 Diagnostic Information Collection ............................................................................................................................. 64
8.5 Custom Configuration Information Collection ........................................................................................................... 65
8.6 AT0 Trunk Record Collect .......................................................................................................................................... 65
8.7 Message Collect .......................................................................................................................................................... 66
9 Information View........................................................................................................................ 67
9.1 Alarm File ................................................................................................................................................................... 67
9.2 Signaling File .............................................................................................................................................................. 70
9.3 Log File....................................................................................................................................................................... 71
9.4 Call Analyzer File ....................................................................................................................................................... 74
9.5 Data File ..................................................................................................................................................................... 77
Issue 02 (2018-12-29) Huawei Proprietary and Confidential iii

LMT Operation Guide 1 Overview
1 Overview
The Local Maintenance Terminal (LMT) is a management system for eSpace U1900 series
and SoftCo. It provides various functions such as alarm management, configuration
management, signaling collecting, upgrade, log collection, and offline operations.
Function Description
The LMT connects to the eSpace U1900 and SoftCo using SSH/Telnet. A maximum of four
devices can be connected to the LMT. Table 1-1 describes the management functions provided
by the LMT.
Telnet is an insecure protocol. It is recommended that you not use it unless you have no choice.
Table 1-1 Main functions
Function Subfunction Description
System - Sets parameters including the language, lock, file

server, host file path, and FTPS.
Device - Adds, modifies, and deletes a device.
Version Upgrade Upgrades the host version when the device runs
properly, which implements a smooth upgrade of
configured service data.
Rollback Restores the software version and configuration
data to the previous version.
Load License Loads the license that you apply for to the device to
use it properly.
Patch Manages device patches, including loading,
Management uninstalling, activating, deactivating, and saving
patches.
Voice File Uses the LMT to make a voice compression
Management package and load it to the device.
Config Backs up the configuration files for system recovery
Management in case of a damage.
Issue 02 (2018-12-29) Huawei Proprietary and Confidential 1


Data Upgrade Upgrades the data.bin file.
Download Command Tree Runs commands to operate the device or view
Command relevant command help information.
Script Load Loads the script CLI file to the device.
Alarm -  Receives device alarm information in real time.
 Provides alarm handling suggestions to locate
and clear alarms to ensure the normal running of
the system.
Log Signaling Collects the broadband signaling, narrowband
Collect signaling, and users. After this function is enabled,
the LMT listens on the data sent from and received
by the device in real time.
Run Log Obtains or views key information about the system
running status or process running.
Operate Log Obtains or views records of instructions performed
by system users or system scheduled tasks.
Call Log Views service running processes.
Debug Log Obtains or views background records of involved
function modules during calls for fault locating.
Call Analysis Analyzes the call processes for the calls that are
made based on the PRA, R2, QSIG, SIP and SS7
trunk.
Control Block Views the call control module information during a
call.
Information Device Runs commands to obtain system information and
Collect Information fault information, helping fault analysis and
locating.
Blackbox Obtains black box information, helping fault
Information analysis and locating.
Trunk Collects the configuration and status information
Information about common trunks, such as SIP, SS7, PRA, R2,
and AT0.
Diagnostic Provides a button to quickly obtain all information
Information including the system information, fault information,
Collection black box information, operation logs, run logs, and
alarm information.
Custom This function helps you quickly collect required
Configuration command line information.
Information
Collection
AT0 Trunk This function helps you collect AT0 trunk recording


Record Collect files for analyzing and locating system faults.
Message Collect This function helps you collect voice message files
for analyzing and locating system faults.
Information Alarm File Imports alarm files offline for service providers to
View view alarm information.
Signaling File Imports signaling files offline for service providers
to view signaling information.
Log File Imports log files offline for service providers to
view log information.
Call Analyzer Imports call data offline for service providers to
File view call data.
Data File This topic describes how to import and parse the
data.bin file on the LMT. You can also generate a
command line file using the configuration file and
export the generated command line file on the
LMT. All these help users quickly obtain device
configuration information to analyze and locate
faults.
System Requirement
The LMT supports Windows 7, Windows 8 and Windows 10 (The V200R003C30SPC300 and
later versions support Windows 10) 32-bit and 64-bit operating systems. When the LMT runs
on a 64-bit operating system, compatibility issues may occur. In this case, load and install the
patch for 32-bit program compatibility at the Microsoft official website
http://www.microsoft.com/en-us/download/confirmation.aspx?id=5582.
Obtaining Help
 See the Help Topic on LMT modules.
 For details about how to configure the device, see the product documentation.

LMT Operation Guide 2 Lock
2 Lock
To prevent unauthorized operations, the LMT provides manual and automatic lock functions.
You can use the required password to unlock the operation page.
Locking the Operation Page

 Manual lock
Choose System > Lock. The operation page is locked immediately.
 Automatic lock
Choose System > Lock Setting. On the page that is displayed, select the option for
automatic lock, set the timeout time, and click OK. When no operation is performed
within the preset time, the operation page is automatically locked.
Unlocking the Operation Page

Press Ctrl+Alt+U, enter the unlock password, and click OK.
The default unlocking password is Change_Me.
Changing the Unlock Password

Choose System > Lock Setting, and click Change Unlock Password. On the page that is
displayed, enter the old password and new password. The password must be a string of 8–16
characters consisting of at least two kinds of combination of letters, numbers and special
characters.

LMT Operation Guide 3 Device
3 Device
This topic describes how to add, modify, delete, connect, and disconnect a device.
Adding a Device
Access the page in either of the following ways:
 Choose Device > Add Device.
 Right-click Device Tree and choose Add Device from the shortcut menu.
Table 3-1 Parameter description (1)
Parameter Description Setting

Name Name of the device. For example, device.
IP IP address of the device. Only  IPv4: 172.16.15.60
the following models can  IPv6: 1900:0:0:0:0:0:0:212
support IPv6.
 U1911
 U1960
 U1981
 SoftCo 7500
If the device uses an IPv6 IP address, the PC where the LMT is installed must support IPv6 IP addresses.
Modifying a Device
 Choose Device > Modify Device.
 Right-click Device Tree and choose Modify Device from the shortcut menu.
 Right-click the device in the device tree and choose Modify Device from the shortcut
menu.

LMT Operation Guide 3 Device
Deleting a Device
 Choose Device > Delete Device.
 Right-click Device Tree and choose Delete Device from the shortcut menu.
 Right-click the device in the device tree and choose Delete Device from the shortcut
menu.
Connecting a Device
The device must be available in the device tree and not connected to the LMT. If the device is
not in the device tree, see Adding a Device to add the device.
Right-click the device in the device tree and choose Connect from the shortcut menu.
Parameter Description
Username Host login account.
View mode password Password to access View mode
Config mode password Password to access Config mode.
If you want to access Config mode of the command tree or
enable the fault collection, remote packet capture, and
signaling collect functions, you must set Config mode
password when connecting the device to the LMT.
SSH authentication By default, the LMT supports login to the host over SSH by
default. The LMT supports login over Telnet if the Telnet
function is enabled.
The SSH encryption ensures secure login to the host.
Select SSH authentication if the Telnet function is not
enabled. See the product documentation to enable the Telnet
function.
NOTE
Telnet is an insecure protocol. It is recommended that you not use it
unless you have no choice.
If the LMT is disconnected from a device due to problems such as device restart or network outage, the
LMT automatically attempts to connect and log in to the device using the original authentication account
and password in 10s.
Disconnecting a Device
Right-click the device in the device tree and choose Close from the shortcut menu.
You can right-click a device in the device tree and choose Service to log in to the web management
system of the device for service configuration.

LMT Operation Guide 4 Version
4 Version
About This Chapter

This topic describes how to use the LMT for version upgrade, system rollback, patch
management, license loading, voice file management, configuration file management, and
data upgrade.
4.1 Upgrade
This topic describes how to upgrade the host software using LMT.
4.2 Rollback
This topic describes how to roll back to the source version using the LMT.
4.3 Load License
This topic describes how to a load license file.
4.4 Patch
This topic describes how to load, delete, and activate patches using LMT.
4.5 Voice File
This topic describes how to load voice files using LMT.
4.6 Configuration File Management
To ensure system stability, it is recommended that you back up the configuration file each
time before the version upgrade or configuration change. The backup configuration file can be
used to restore the system in case of any system faults.
4.7 Data Upgrade for the Same Model
This topic describes how to upgrade data.bin files by means of data upgrading function.
4.8 Cross-Model Data Upgrade
This topic describes how to upgrade the data.bin file using the cross-model data upgrade
function. Currently, only the U1980 data can be converted into U1981 data, and the software
versions of the U1980 and U1981 must be the same.

4.1 Upgrade
This topic describes how to upgrade the host software using LMT.
Prerequisite
 The device and LMT have been connected. If the device and LMT are not connected, see
Connecting a Device.
 Choose System > File Server from the menu bar to set the file transfer protocol.
Accessing Configuration Pages

Choose Version > Upgrade.
Procedure
1. Click Browse and select the target version.
2. Select a device to upgrade.
3. Click Upgrade.
4. In the Upgrade preparation dialog box, select Upgrade data and click OK.
Data is also backed up during data upgrade to ensure smooth service migration. The backup data can be
used for version rollback. The upgrade time will be shortened if data is not upgrade, but no data is
available for version rollback, and after the upgrade is complete, you need to enter the user name and
password to log in to the device again.
Paramete Description
r
No. Device number.

IP Address IP address of the device.
Current Current version of the device.
Version
Target Target version of the device.
Version
Execution Current upgrade status.
4.2 Rollback
This topic describes how to roll back to the source version using the LMT.

Prerequisite
The device and LMT have been connected. If the device and LMT are not connected, see

Choose Version > Rollback.
Procedure
1. Select the device for version rollback.
2. Select a version in Select the version.
3. Click Rollback.
r
No. Device number.

Current Current version of the device.
Version
Target Target version for a rollback.
Version
Execution Current rollback status.
Status
4.3 Load License

This topic describes how to a load license file.
Prerequisite

Choose Version > Load License.
Procedure
1. Select a device that needs to load a license file.
2. Click Browse, and select the path where the license file is saved.

3. Click Load.
r
No. Device number.

License Path for saving the license file
File
Check Inspection on the current license information.
License
Execution Current loading status.
Status
4.4 Patch
This topic describes how to load, delete, and activate patches using LMT.
Prerequisite

Choose Version > Patch.
Procedure
 Loading a patch
a. Click the Main Control Board or I/O Board tab and select the main control board
or IO board as the board for patch loading.
b. Click Refresh to view the patch information of the current version.
c. Click Browse and select the directory for storing the patch file.
d. Select the device to be loaded with a patch.
e. Set Execution Mode to load.
f. Click Execute.
 Activating a patch
c. Select the device whose patch is to be activated.

d. Set Execution to activate.
To save a patch, set Execution Mode to save. To delete a patch, set Execution Mode to delete.
e. Click Execute.
 Deactivating a patch
c. Select the device whose patch is to be deactivated.
d. Set Execution Mode to deactivate.
To save a patch, set Execution Mode to save.

e. Click Execute.
Device IP IP address of the device.
Address
Slot ID Slot number of the board.
Board Board type.
Existing Patch Existing patch of the device.
Patch Status Patch status, including activated and deactivated.
Execution Status Execution result, including activation success, deactivation success, and
save success.
Execution Mode Patch execution mode, including load, save, activate, deactivate, and
delete.
4.5 Voice File

This topic describes how to load voice files using LMT.
Prerequisite
 The voice files are available.
 Choose System > File Server from the menu bar and set the file transfer protocol to
TFTP.


Choose Version > Voice File.
Procedure
 Create the voice package file.
a. In the Generate Compressed Voice File Package area, click Browse next to Step
1 to select the folder where the prepared .pcm voice file is stored.
b. Click Generate Voice File.
The MakeTone Configuration window is displayed, as shown in Figure 4-1.
Figure 4-1 MakeTone Configuration
c. Set Voice File Type and click OK.

A voice package file is created in <LMT_PATH>\tools\MakeTone.
Table 4-1 Voice package
Voice File Type Voice Package

voice voice.zip
mrsvoice mrsvoice.zip
crbt crbt.zip
 Decompress the voice package.

a. Click Browse and select the voice package to decompress.
b. Click Decompose Voice File. The system automatically extracts the .pcm voice file
from the voice package.
 Load the voice.zip file.
a. In the Load voice file area, click Browse next to Select a voice file you want to
load and select the voice package file.
b. Select the device to which the voice file is loaded.
c. Click Load.

4.6 Configuration File Management

To ensure system stability, it is recommended that you back up the configuration file each
time before the version upgrade or configuration change. The backup configuration file can be
used to restore the system in case of any system faults.
Prerequisite
 The file transfer protocol has been set under Set > File Server from the menu bar.

Choose Version > Configuration File Management.
Procedure
1. In the Configuration File List area, select a configuration file.
2. Select the device to have data loaded or backed up.
3. In the Execution Mode area, select Load or Back Up, set the path for saving the backup
data, and click Execute.
After the backup is complete, click Open Directory, open the backup directory, and check
whether the folder named after the device IP address contains a configuration file with the file
name in format of <filename>_YYYYMMDDhhmmss (for example,
license_20131106114255.dat).
4.7 Data Upgrade for the Same Model

This topic describes how to upgrade data.bin files by means of data upgrading function.
Prerequisite
 There is a data.bin file to upgrade.
 The dbupgrade.jar file (saved in the device version file package) is obtained.

Choose Version > Data Upgrade.
Procedure
1. Click Load dbupgrade.jar.
2. Select the dbupgrade.jar file and click Open.
The system displays the message "Load success".
3. Click Browse.... Select the save path of a data.bin file that is to upgrade.
4. From the drop-down list box of Please select the target version, select a version to
upgrade for the data.bin file.
5. Click Upgrade.

4.8 Cross-Model Data Upgrade

This topic describes how to upgrade the data.bin file using the cross-model data upgrade
function. Currently, only the U1980 data can be converted into U1981 data, and the software
versions of the U1980 and U1981 must be the same.
Prerequisites
 The data.bin file to be upgraded exists.
 The dbconvert.jar file (in the device version software package) has been obtained.
Accessing the Configuration Page

Choose Version(B) > Data Upgrade(D).
Procedure
1. Upgrade the data.bin file of the U1980 to the target version using the dbupgrade.jar
database upgrade tool for the U1980. For details, see 4.7 Data Upgrade for the Same
Model.
2. Use the LMT to load the upgraded U1980 data converted by the dbconvert.jar file.
a. Click Load dbconvert.jar.
b. Select the dbconvert.jar file in the U1981 version software package and click
Open. The system displays the "Load success" message.
c. Click Browse, select the data.bin file to be upgraded, and click Upgrade.
d. Obtain the upgraded data.bin file in the specified directory as prompted.
3. Upgrade the U1981 software to the target version.
This step is optional. Cross-model data upgrade can be implemented only when the models are of the
same version. Perform this step only when the software version of the U1981 is different from that of the
U1980.
4. Load the data.bin file of the target version on the U1981 and restart the U1981.
a. Choose Version(B) > Configuration File Management(F). Select data.bin in
Configuration File List and set the execution mode to Load.
b. Click Browse and select the directory that stores the data.bin file of the target
version.
c. Select the target device and click Execute.
d. In the complete command input area, run the reboot command to restart the device.

LMT Operation Guide 5 Command Delivery
5 Command Delivery
About This Chapter

5.1 Command Tree
This topic describes how to classify commands and display commands in tree mode.
5.2 Script Load
The specified functions such as the automatic switchboard function are available only when
some specified script command line files are loaded.
5.1 Command Tree

This topic describes how to classify commands and display commands in tree mode.
5.1.1 Command Tree Structure

This topic describes the command tree structure.
Figure 5-1 shows the command tree structure.

Figure 5-1 Command tree structure
5.1.2 Command Tree Operations

This topic describes how to use the LMT command tree to run commands.
Context
The command tree can work in View mode, Config mode or Debug mode.
In View mode, only the show command can be executed; in Config mode, only show and
config commands can be executed; in Debug mode, only show, config, and debug commands
can be executed.
Prerequisite
 The file storage path has been set on the page that is displayed after you click Set TFTP
Server or Set FTPS Server for file uploading or downloading in the command tree.


Assume that the device IP:172.16.15.60 page is displayed when the device is connected to the
LMT.
 On the device IP:172.16.15.60 page, click the Command Tree tab.
 Right-click device IP:172.16.15.60 and choose Command Tree from the shortcut menu.
 Choose Command Delivery > Command Tree.
 Click the Command tab, select device IP:172.16.15.60 from the Device drop-down list,
and click the Command Tree tab.
Procedure
The following procedure takes the show board slot 0 command as an example to describe
how to use the command tree.
 Using the command tree to search for a command
a. Choose Device Management > Board Management and double-click Show
Board, as shown in Figure 5-2.
Figure 5-2 Using the command tree to search for a command
b. Set Slot to 0 in the command input area.

c. Click Execute.
 Searching for a command
a. Click the Command tab, as shown in Figure 5-3.

Figure 5-3 Searching for a command
b. Enter a keyword such as board in the search bar.

c. Double-click the Show Board command in the search tree.
d. Set Slot to 0 in the command input area, as shown in Figure 5-4.
Figure 5-4 Entering the command
e. Click Execute.
 Entering part of a command in the command input area
a. Enter the show board command in Enter Command in the command input area
and press Enter, as shown in Figure 5-5.
Figure 5-5 Entering the command (1)
b. Set Slot to 0 in the command input area.

c. Click Execute.

 Entering a whole command

a. Enter the show board slot 0 command in the whole command input area or the
batch command input area, as shown in Figure 5-6.
Figure 5-6 Entering the command (2)
b. Click Execute.
When you want to execute commands in batches, enter each command in a line.
Click Help to view parameter description.
5.2 Script Load

The specified functions such as the automatic switchboard function are available only when
some specified script command line files are loaded.
Prerequisite
 The script command line files exist.

Choose Command Delivery > Script Load.
Procedure
1. Click Browse and select the script command file to load.
2. Click Load.

LMT Operation Guide 6 Alarm Management
6 Alarm Management
This topic describes how to view alarms and suggestions that are displayed on the LMT to
rectify faults.

Choose Alarm Management > Alarm.
Procedure
 Viewing detailed alarm information
a. Double-click an alarm to view detailed alarm information, as shown in Figure 6-1.

Figure 6-1 Detail alarm
You can also right-click an alarm and choose Detail from the shortcut menu to view detailed alarm
information.
b. Click or on the Alarm Information tab page to view the

complete alarm information.
c. Click the Alarm Suggestions tab and handle the alarm according to troubleshooting
suggestions.
d. Click the Alarm Information tab, enter the handling result or other fault
information in Remarks, and click Save Remarks.
 Querying alarm information
a. Click Search Alarm.
b. Set search criteria by referring to Parameter Description and click Search.
 Selecting alarm parameters to be displayed
a. Click Config Column.
b. Select the items to be displayed by referring to Parameter Description and click
OK.
 Saving alarm information
Right-click an alarm and choose Save Selected Alarms or Save all Alarms from the
shortcut menu.
Alarm information is stored in <LMT_PATH>\hostfile\alarm by default. Choose System > Host File
Path to view and set the path where the hostfile file is stored.

 Synchronizing alarm information

a. Click the Sync Alarm tab.
b. On the Sync Alarm tab page, select the device to have alarms synchronized, as
shown in Figure 6-2.
Figure 6-2 Synchronizing alarms
c. Click OK. The Synchronizing alarms message is displayed. After the alarms are
synchronized, the Sync alarms succeeded message is displayed.
 During alarm synchronization, Search Alarm, Config Column, Sync Alarm, turning pages, and
closing windows are unavailable. the alarms are cleared after the alarms are synchronized.
 During alarm synchronization, other devices cannot be connected. After the alarm synchronization is
complete, the alarm is cleared.
r
Device IP IP address of the device that generates an alarm.

Alarm Alarms are classified into different levels according to their severities.
Level The options are as follows:
 Critical: indicates global alarms, such as the power supply fault, that
seriously affect the running of devices. Critical alarms must be handled
immediately to prevent the system from breaking down.
 Major: indicates board or circuit alarms, such as the physical circuit fault,
that occur partially. Major alarms must be handled promptly to ensure
properly running of services.
 Minor: indicates general faults or event alarms that describe the working
status of each board or circuit. Causes of minor alarms must be located to
prevent potential problems.

r
 Warning: indicates messages that provide information. For example, an
alarm is generated, indicating that a device is restored. Such alarms do not
affect system performance or services. No manual intervention is required.
Device Type of the device that generates an alarm.
Type
Alarm ID ID of an alarm. Each alarm has a unique alarm ID.
Alarm Name of an alarm.
Name
Alarm Detailed information about an alarm.
Content
Event Event type corresponding to a type of alarms.
Type
Alarm Alarm type.
Type
SID Sequence number generated by the system.
Alarm Time when an alarm is generated.
Time
Recover Time when an alarm is cleared.
Time
Acknowle Indicates whether an alarm is acknowledged.
dge Flag
Acknowle Time when an alarm is acknowledged.
dge Time
Clear Flag Indicates whether an alarm is cleared.
Clear Time when an alarm is cleared.
Time

LMT Operation Guide 7 Log Management
7 Log Management
About This Chapter

This topic describes how to manage logs including operation logs, run logs, and call logs, and
view control block information. Refer to log information to locate faults.
7.1 Signaling Collect
This topic describes how to collect signaling using LMT. It is an important method to locate
faults.
7.2 Run Log
Run logs record key information about the system running status or process running. Refer to
run logs to locate faults.
7.3 Operate Log
Operation logs record instructions performed by system users including administrators,
operators, and supervisors. Use operation logs to locate the time and content of an operation.
7.4 Call Log
Call logs record service running processes and are used to locate faults or for reference.
7.5 Debug Log
Debug logs record background information about involved function modules during calls.
These logs can be used as a reference for fault locating.
7.6 Call Analyzer
This topic describes how to use the LMT to analyze the call processes for the calls that are
made based on the SIP, PRA, R2, SS7 or QSIG trunk.
7.7 Control Block
This topic describes how to view the call control module information during a call.
7.1 Signaling Collect

This topic describes how to collect signaling using LMT. It is an important method to locate
faults.

7.1.1 SIP
The Session Initiation Protocol (SIP) signaling collecting task is used to collect SIP signaling.
Prerequisite

Choose Log Management > Signaling Collect.
Procedure
 Adding a task
a. Double-click SIP.
You can also right-click SIP and choose Add from the shortcut menu.
If you have not accessed the Config Mode when connecting the LMT to the device, the system prompts
you to enter a value for Config mode password.
b. Set the parameters according to Table 7-1 and then click OK.
The signaling information page is displayed, as shown in Figure 7-1.

Figure 7-1 Signaling information page
 Deleting a task
Right-click a task (for example, sip: 0) and choose Delete from the shortcut menu.
 Stopping a task
Right-click a task (for example, sip: 0) and choose Stop from the shortcut menu.
 Searching for signaling information
a. Select the items to be searched out in the Search and Filter area and set parameters
according to Table 7-2. If the parameters are incorrectly set or need to be reset,
click Reset to reset the parameters.
b. Click Query.
 Filtering out signaling information
b. Click Filter.
 Viewing detailed signaling information
Click a signaling record to view the detailed signaling information, as shown in Figure
7-2.

Figure 7-2 Signaling collecting result
 Deleting signaling information

Right-click a signaling record and choose Delete Selected Records or Delete All
Records.
r
IP Address IP address of the device to perform the signaling collecting.

Begin Whether to set a scheduled signaling collecting task. If a scheduled signaling
Time collecting task is set, data within the scheduled time is displayed on the page.
If no scheduled signaling collecting task is set, all data since the start of
device is displayed.
AutoSave Automatically save the information displayed on the page in the preset
directory.
r
Begin Start time of the time segment within which the signaling information is
Time searched or filtered out.
End Time End time of the time segment within which the signaling information is
searched or filtered out.
Direction Whether to send or receive the signaling for the device connected to the
LMT.
IP Address IP address of the signaling sender or recipient.

r
Call-ID Unique ID for identifying an SIP message group.

Task No Unique ID assigned to a task.
Caller Number of the calling party.
Callee Number of the called party.
7.1.2 QSIG
The QSIG signaling collecting task is used to collect the QSIG signaling on a QSIG link.
Prerequisite

Procedure
 Adding a task
a. Double-click QSIG.
You can also right-click QSIG and choose Add from the shortcut menu.
b. Set the parameters according to Table 7-3, and then click OK.

 Deleting a task
Right-click a task (for example, qsig:0) and choose Delete from the shortcut menu.
 Stopping a task
Right-click a task (for example, qsig:0) and choose Stop from the shortcut menu.
b. Click Query.
b. Click Filter.

7-4.

Records.
r
Slot No Slot number of the MTU board where the QSIG signaling link resides.
Trunk Port Port number of the MTU board where the QSIG signaling link resides.
Time Task Whether to set a scheduled signaling collecting task. If a scheduled signaling
collecting task is set, data within the scheduled time is displayed. If no
scheduled signaling collecting task is set, all data since the start of device is
displayed.
AutoSave Whether to automatically save the information displayed on the page in the
preset directory.
r

r
LMT.
Layer Layer of the QSIG protocol, for example, layer 2 or layer 3.
Message Message type of QSIG signaling.
Type
CRV Call reference value, which is used to identify the call or device
registration/deregistration request related to a message on the QSIG
user-network interface.
7.1.3 PRA
The PRA signaling collecting task is used to collect the PRA signaling on a PRA link.
Prerequisite

Procedure
 Adding a task
a. Double-click PRA.
You can also right-click PRA and choose Add from the shortcut menu.

 Deleting a task
Right-click a task (for example, pra:0) and choose Delete from the shortcut menu.
 Stopping a task
Right-click a task (for example, pra:0) and choose Stop from the shortcut menu.
b. Click Query.
b. Click Filter.
7-6.


Records.

r
Slot No Slot number of the MTU board where the PRA signaling link resides.
Trunk Port Port number of the MTU board where the PRA signaling link resides.
displayed.
preset directory.
r

r
LMT.
Layer Layer of the PRA protocol, for example, layer 2 or layer 3.
Message Message type of PRA signaling.
Type
registration/deregistration request related to a message on the PRA
7.1.4 BRI
The BRI signaling collecting task is used to collect the BRI signaling on a BRI link.
Prerequisite

Procedure
 Adding a task
a. Double-click BRI.
You can also right-click BRI and choose Add from the shortcut menu.

 Deleting a task
Right-click a task (for example, bri:2) and choose Delete from the shortcut menu.
 Stopping a task
Right-click a task (for example, bri:2) and choose Stop from the shortcut menu.
b. Click Query.
b. Click Filter.
7-8.


Records.

r
Slot No Slot number of the BTU board where the BRI signaling link resides.
Trunk Port Port number of the BTU board where the BRI signaling link resides.
displayed.
preset directory.
r

r
LMT.
Layer Layer of the BRI protocol, for example, layer 2 or layer 3.
Message Message type of BRI signaling.
Type
registration/deregistration request related to a message on the BRI
7.1.5 SS7
The Signaling System Number 7 (SS7) signaling collecting task is used to collect the
signaling on an SS7 link between the device and the peer device.
Prerequisite

Procedure
 Adding a task
a. Double-click SS7.
You can also right-click SS7 and choose Add from the shortcut menu.

 Deleting a task
Right-click a task (for example, ss7: 1) and choose Delete from the shortcut menu.
 Stopping a task
Right-click a task (for example, ss7: 1) and choose Stop from the shortcut menu.
b. Click Query.
b. Click Filter.
7-10.


Records.

r
By  If the type is set to Link, the SS7 link is used to collect signaling. All the
signaling that is collected is received and sent by the SS7 link of the
specified index.
 If the type is set to DPC, the DPC is used to collect signaling. All the
signaling that is collected is received and sent by the DPC of the specified
index.
Index ID. The value of Index can be queried using the following methods.
 If the type is set to Link, run the show mtplink command and check the
value of Index.
 If the type is set to DPC, run the show dsp command and check the value
of Index.
Filter Set the filter conditions. One or all of the MTP3 signaling, ISUP signaling,
and TUP signaling can be filtered.
displayed.

r
preset directory.
r
LMT.
CIC Circuit ID of the signaling, for example, 0x1.
Signal Type of the SS7 signaling, for example, ACM, IAM, and CPG.
7.1.6 R2
The R2 signaling collecting task is used to collect the R2 signaling on a R2 link.
Prerequisite

Procedure
 Adding a task
a. Double-click R2.
You can also right-click R2 and choose Add from the shortcut menu.

 Deleting a task
Right-click a task (for example, r2: 0) and choose Delete from the shortcut menu.
 Stopping a task
Right-click a task (for example, r2: 0) and choose Stop from the shortcut menu.
b. Click Query.
b. Click Filter.

Records.
r
Start Global circuit number that corresponds to the global timeslot ID.
GlbNo You can run the show tkc command to check the global circuit number.
End
GlbNo
displayed.
preset directory.
r
LMT.
Signal Signaling type, which can be the line signaling or the register signaling.
Type
Logic Signaling name, for example, CALLERONHOOK, SEIZE, A3, or B1.
Signal
Name
7.1.7 Subscriber
The Subscriber signaling collecting task is used to collect the interactive signaling between
modules involved in a call of a user.

Prerequisite

Procedure
 Adding a task
a. Double-click Subscriber.
You can also right-click Subscriber and choose Add from the shortcut menu.
b. Set the parameters according to Table 7-13 and then click OK.The signaling
information page is displayed, as shown in Figure 7-12.

 Deleting a task
Right-click a task (for example, subscriber: 1) and choose Delete from the shortcut
menu.
 Stopping a task
Right-click a task (for example, subscriber: 1) and choose Stop from the shortcut menu.
b. Click Query.
b. Click Filter.
7-13.

Records.

Dn Phone number to be collected.
Filter Set the filter conditions. One or all of the CCM signaling, USAM
signaling, STPTK signaling, and PRI signaling can be filtered.
Time Task Whether to set a scheduled signaling collecting task. If a scheduled
signaling collecting task is set, data within the scheduled time is
displayed. If no scheduled signaling collecting task is set, all data since
the start of device is displayed.
AutoSave Whether to automatically save the information displayed on the page in
the preset directory.
Begin Time Start time of the time segment within which the signaling information is
LMT.
Message Two modules between which the signaling is communicated. For
Interface example, the signaling is communicated between the CCM and the
USAM.
Message Type Signaling type, for example, SETUP.
7.2 Run Log

Run logs record key information about the system running status or process running. Refer to
run logs to locate faults.
Prerequisite
The device and LMT have been connected.


Choose Log Management > Run Log.
Procedure
 Obtaining log information
When you access the configuration page, the LMT automatically obtains log information,
as shown in Figure 7-14.
Figure 7-14 Log information
You can click or to stop or start refreshing the page where log information is
displayed, and click Open to view the generated log file.
 Querying log information
a. Click Search Log.
b. Select the items to be searched out in the Search And Filter area and set
parameters according to Parameter Description.
c. Click Search.

 Filtering log information

c. Click Search.
 Selecting log parameters to be displayed
Click Select Column and select the log parameters to be displayed according to
Parameter Description.
 Deleting log information
Right-click a log and choose Delete Selected Records or Delete All Records from the
shortcut menu.
r
Time Time when a log is generated.

Slot Slot number of the board.
Content Content of a log.
Level Log level. The options are INFORMATION, WARNING, ERROR, OMU,
and CLI.
Pid Software module number.
7.3 Operate Log

Operation logs record instructions performed by system users including administrators,
operators, and supervisors. Use operation logs to locate the time and content of an operation.
Prerequisite

Choose Log Management > Operate Log.
Procedure
When you access the configuration page, the LMT automatically obtains log information,

 When a device is connected to the LMT, the device's operation logs are stored in the device buffer
and the LMT. When the device is disconnected from the LMT, the device's operation logs are stored
only in the device buffer, and the logs are synchronized to the LMT incrementally once the device is
reconnected to the LMT. A maximum of 5000 operation logs can be stored in the device buffer. If
the number of operation logs reaches the upper limit, new logs overwrite the oldest ones. If the
device is restarted, its buffer is cleared.
 The operation logs in the device buffer are stored in the Command History Information area of the
black box file. The administrator can view such logs in the black box file. The Session field maps
the SessionId field in the VTY Connect Information area.
c. Click Search.
 Filtering log information
c. Click Search.

Click Select Column and select the log parameters to be displayed according to
shortcut menu.
r
Result Command execution result. The options are SUCCESS and FAILED.
Client IP address of the PC where a configuration tool is installed.
IpAddress
Client ID ID of the client for a configuration tool.
Operate Instructions initiated by system users or system scheduled tasks.
Content
UserName Name of the user who initiates an instruction.
CTLType Type of the configuration tool connected to the device, which includes the
CLI, Web, eSight|LMT, BMU, and CENTERSERVER.
NOTE
CENTERSERVER is used for the local node or standby node to record logs of the active
node's data synchronization in a centralized call management network.
7.4 Call Log

Call logs record service running processes and are used to locate faults or for reference.
Prerequisite

Choose Log Management > Call Log.
Procedure
a. Click Module Switch Configuration.
b. Set parameters according to Table 7-15.

If you are not familiar with the functions of service modules, you can select the appropriate module
based on the scenario. After you select the scenario based on actual conditions, the system automatically
selects the corresponding service module.
c. Click Start Configuration.
After enabling the switches, you can click Query Configuration to view the collect items configured
previously, and click Close All Configuration to disable all the switches.
d. Click to close the page.
 Querying or filtering log information
parameters according to Table 7-16.
c. Click Search or Filter.
 Setting the column to display log information
Click Config Column and select the items to be displayed according to Table 7-16.
 Viewing detailed log information
a. Double-click a log that is displayed to view detailed log information.
You can right-click a log and choose View Details from the shortcut menu to view detailed log
information.
b. Set Keyword and click Query to search detailed log information for required
information.
If you viewing logs about R2 or primary rate interface (PRI) messages, you can right-click a log and
choose PRI / R2 Chart Parse from the shortcut menu to view graphical analysis results.
shortcut menu.
Table 7-15 Business Modules
Module Description
CCM Call control module where operations such as number analysis and called
party location are performed. It is used to display logs about calls.
USAM User abstract module where operations such as plain old telephone service
(POTS) pickup and hangup operations are performed. It is used to display
logs about user states.
VU Virtual switchboard module. It is used to display logs about virtual users
(VUs).

Module Description
H248 H248 module.
CM Connection control module. It is used for communication between the control
layer (including the USAM, TK, and users) and the resource management
layer (including the RM, PATH, and NCM).
RM Resource management module that manages digital signal processing (DSP)
resources for playing announcements, encoding, and decoding. The module
can be used to display announcement playing logs.
NM Network management module. It is used to manage the connection status and
port status of each SS component.
CONSOL Attendant group management module.
EGROUP The options are as follows:
 Database function
Provides line selection, static database update, dynamic queue update, and
maintenance queue update.
 Call function
Provides message forwarding between VUs and the device.
CONFER Conference management module.
ENCE
BINCLI BIN channel data synchronization module.
PRI Primary Rate Interface (PRI) trunk module.
QSIG QSIG trunk module.
BRI Basic Rate Interface (BRI) trunk module.
ISUP Integrated Services Digital Network User Part (ISUP) trunk module.
TUP Telephone User Part (TUP) trunk module.
SIP Intra-office Simple Internet Protocol (SIP) trunk module.
SIPTK Outer-office SIP trunk module.
AT0 AT0 trunk module.
CNO1 R2 trunk module.
ISUP ISUP signaling module.
Signal
H248 H248 signaling module.
Signal
USAM IE User abstract signaling module.
CALL SIP-call message module.
REGISTE SIP-registration message module.
R

Module Description
OPTION SIP-heartbeat message module.
SUBSCRI SIP-subscription message module.
BE
NOTIFY SIP-notification message module.
INFO SIP-INFO message module.
MESSAG SIP-MESSAGE message module.
E
PUBLISH SIP-PUBLISH message module.
MTP3 Message Transfer Part Level 3 (MTP3) protocol.
POTSCP POTS control protocol.
Q921 Q921 messages.
DSP DSP resources of the media resource board.
TSAM Trunk service abstract module.
Table 7-16 Parameter description
r
CallerDn Number of the calling party.
Time Time when a call is set up.
CalleeDn Number of the called party.
LogID Log ID.
ReleaseCa Digital identifier of the cause for releasing a call.
use
Descriptio Description of the call release cause.
n
7.5 Debug Log

Debug logs record background information about involved function modules during calls.
These logs can be used as a reference for fault locating.

Prerequisite

Choose Log Management > Debug Log.
Procedure
a. Click Module Switch Configuration.
b. Set parameters according to Parameter Description.
If you are not familiar with the functions of service modules, you can select the appropriate module
based on the scenario. After you select the scenario based on actual conditions, the system automatically
selects the corresponding service module.
c. Click Start Configuration.
After enabling the switches, you can click Query Configuration to view the collection items configured
previously, and click Close All Configuration to disable all the switches.
d. Click to close the page.
 You can click to stop refreshing the page where log information is displayed.
 You can click to refresh the page to update log information.

 You can click Open to view the generated log file.
 Querying or filtering log information
b. In the Search And Filter area, enter keywords and click Search or Filter.
Table 7-17 Business Modules
Module Description
CCM Call control module where operations such as number analysis and called
party location are performed. It is used to display logs about calls.
USAM User abstract module where operations such as plain old telephone service
(POTS) pickup and hangup operations are performed. It is used to display
logs about user states.
VU Virtual switchboard module. It is used to display logs about virtual users
(VUs).
H248 H248 module.
CM Connection control module. It is used for communication between the control
layer (including the USAM, TK, and users) and the resource management
layer (including the RM, PATH, and NCM).

Module Description
RM Resource management module that manages digital signal processing (DSP)
resources for playing announcements, encoding, and decoding. The module
can be used to display announcement playing logs.
NM Network management module. It is used to manage the connection status and
port status of each SS component.
CONSOL Attendant group management module.
EGROUP The options are as follows:
 Database function
Provides line selection, static database update, dynamic queue update, and
maintenance queue update.
 Call function
Provides message forwarding between VUs and the device.
CONFER Conference management module.
ENCE
BINCLI BIN channel data synchronization module.
PRI Primary Rate Interface (PRI) trunk module.
QSIG QSIG trunk module.
BRI Basic Rate Interface (BRI) trunk module.
ISUP Integrated Services Digital Network User Part (ISUP) trunk module.
TUP Telephone User Part (TUP) trunk module.
SIP Intra-office Simple Internet Protocol (SIP) trunk module.
SIPTK Outer-office SIP trunk module.
AT0 AT0 trunk module.
CNO1 R2 trunk module.
ISUP ISUP signaling module.
Signal
H248 H248 signaling module.
Signal
USAM IE User abstract signaling module.
CALL SIP-call message module.
REGISTE SIP-registration message module.
R
OPTION SIP-heartbeat message module.
SUBSCRI SIP-subscription message module.
BE
NOTIFY SIP-notification message module.

Module Description
INFO SIP-INFO message module.
MESSAG SIP-MESSAGE message module.
E
PUBLISH SIP-PUBLISH message module.
POTSCP POTS control protocol.
Q921 Q921 messages.
DSP DSP resources of the media resource board.
TSAM Trunk service abstract module.
Table 7-18 Platmodules of the Main Control Board
Module Description Module Description

ONSET Database synchronization DEVICE Device management
BILL CDR VCOM VCOM protocol
DIAMETER Charging PFORWAR External packet forwarding
D
ALARM_SE Alarm server BILL_SERV CDR server
RVER ER
SEP SEP protocol NET Network drive
NODE Internal board SNMP SNMP
communication using the
serial port
LICENSE License SNTP SNTP
DNS DNS service URM URM module
BIN Binary channel WORKMO Active/standby status of
DE multiple network ports
M3UA M3UA module TLS TLS protocol
EWS_WEB Web server CWMP TR-069 network
management
NTP NTP MEMORY Memory
EXC Black box PATCH Patch
TIME Time FLASH Flash memory


DBLOAD Database loading DB Database
ALARM Alarm client DEBUG Debug module
OS Operating system BOARD Board management
MAINTAIN Maintenance DEV_CALL Device callback
BACK
LOG Log TRC Collecting
TFTP TFTP LOAD Load
BACKUP Backup LSW5328 Switch chip
FPGA FPGA packet filtering LSW Switch chip
module
NCM NCM module MRSDSP DSP
E1 E1 drive management SPC E1 semi-permanent
connection (SPC)
M2PA M2PA - -
Table 7-19 Platmodules of the I/O Board

MEMORY Memory EXC Black box
PATCH Patch TIME Time
FLASH Flash memory DBLOAD Database loading
DB Database ALARM Alarm
DEBUG Debug OS Operating system
BOARD Board management MAINTAIN Maintenance using
CLI
DEV_CALLBACK Device callback LOG Log
TRC Collecting TFTP TFTP
LOAD File loading BACKUP Backup
LSW5328 Switch chip FPGA FPGA packet
filtering
LSW Switch MTP2 MTP2 module
NCM NCM module DSP DSP drive
MRSDSP DSP module E1 E1 trunk
management


SPC E1 SPC Q921 Q921 internal
signaling
M2PA M2PA module BRI BRI trunk
7.6 Call Analyzer

This topic describes how to use the LMT to analyze the call processes for the calls that are
made based on the SIP, PRA, R2, SS7 or QSIG trunk.
Prerequisite
 The device and LMT have been connected.
 Choose Host Log > Call Log > Module Switch Configuration to configure the module
switch.

Choose Log Management > Call Analyzer.
Procedure
 Viewing call flow
a. Select Online Analysis.
b. Set up a call. The call log information is displayed on the UI, as shown in Figure
7-16.

Figure 7-16 Call Analysis(1)
c. Click Analyze Call Log.

d. Select a call record on the displayed Call Analysis page. The call flow chart of the
selected call is displayed, as shown in Figure 7-17.

 Saving call logs

a. Select Online Analysis.
b. Set up a call. The call log information is displayed on the UI.
c. Click Save.
d. Select a path for storing the logs and enter the file name on the displayed Save
dialog box. Click Save.
r
Time Time when a call starts.

Source Name of the device that initiates a message.

r
Destinatio Name of the device that receives a message.
n
Protocol SIP, PRA, R2, SS7 and QSIG are included.
Call ID ID of the call process.
Informatio Message type.
n
7.7 Control Block

This topic describes how to view the call control module information during a call.
Prerequisite
 The call is set up.

Choose Log Management > Control Block.
Procedure
In the call control module area, double-click a module name. Or, right-click a module name
and select Query Control Block Information.
Name of Description
Control
Module
CB_CCM Call control module such as call analysis and called party location.
CB_USAM_CR User application module, for example, a module to perform the POTS
user's pick-up and hang-up.
CB_SIPUSM_C Intra-office SIP trunk module. The module can be viewed only when an
R intra-office call through the SIP trunk is set up.
CB_RM_RCB Resource management module that manages DSP resources for playing
announcements, encoding, and decoding.
CB_SIPTK_CR Outer-office SIP trunk module. The module can be viewed only when
an inter-office call through the SIP trunk is set up.

Name of Description
Control
Module
CB_PRI_CR PRI trunk module. The module can be viewed only when an inter-office
call through the PRI trunk is set up.
CB_ALL All modules.

LMT Operation Guide 8 Information Collection
8 Information Collection
About This Chapter

LMT can collect system information, fault information, and black box information, to
facilitate system troubleshooting.
8.1 Device Information
This topic describes how to collect system and fault information to facilitate system
troubleshooting.
8.2 Blackbox Information
The black box information contains the basic system information including restart logs, basic
information, and running status. The black box information helps locate and analyze faults.
8.3 Trunk Information
This function allows users to collect the configuration and status information about common
trunks, such as SIP, SS7, PRA, R2, and AT0.
8.4 Diagnostic Information Collection
A button is provided to quickly obtain all information including the system information, fault
information, black box information, operation logs, run logs, and alarm information. The
information obtained helps fault analysis and locating.
8.5 Custom Configuration Information Collection
This function helps you quickly collect required command line information.
8.6 AT0 Trunk Record Collect
This function helps you collect AT0 trunk recording files for analyzing and locating system
faults.
8.7 Message Collect
This function helps you collect voice message files for analyzing and locating system faults.

8.1 Device Information

This topic describes how to collect system and fault information to facilitate system
troubleshooting.
Prerequisite

Choose Information Collection > Device Information.
Procedure
 Collecting system information
Click System Information Collect. The system information is displayed.
 Collecting fault information
Click Fault Information Collect. The fault information is displayed.
It takes about four minutes to collect fault information.

If you have not accessed the Config Mode when connecting the LMT to the device the system prompts
 Exporting fault information
a. When information collection succeeds, click Export.
b. Set the path to save the fault information.
c. Click Save.
8.2 Blackbox Information

The black box information contains the basic system information including restart logs, basic
information, and running status. The black box information helps locate and analyze faults.
Prerequisite

Choose Information Collection > Blackbox Information.

Procedure
Click Get Blackbox Information. The black box information is displayed. About 30 seconds
later, the system displays a prompt message Get blackbox information success.
 If you have not accessed the Config Mode when connecting the LMT to the device, the system
prompts you to enter a value for Config mode password.
 Click to open the stored data file.
 Click to open the folder that stores data files.
 By default, the data is saved <LMT_PATH>\conf\errorcollect\blackboxfiles.
8.3 Trunk Information

This function allows users to collect the configuration and status information about common
trunks, such as SIP, SS7, PRA, R2, and AT0.
Prerequisite

Choose Information Collection > Trunk Information.
Procedure
Select the desired trunk type and click Collect. After the collection, the system generates the
related log package in the IPT_LMT\hostfile\msgcollect directory by default.
8.4 Diagnostic Information Collection

A button is provided to quickly obtain all information including the system information, fault
information, black box information, operation logs, run logs, and alarm information. The
information obtained helps fault analysis and locating.
Prerequisite

Choose Information Collection > Diagnostic Information Collection.
Procedure
1. Select the information type, and set the time segment and path for saving the
information.

2. Click Collect.
 If you have not accessed the Config Mode when connecting the LMT to the device, the system
prompts you to enter a value for Config mode password.
 By default, the data is saved in <LMT_PATH>\hostfile\msgcollect.
8.5 Custom Configuration Information Collection

This function helps you quickly collect required command line information.
Prerequisite

Choose Information Collection > Custom configuration Information Collection.
Procedure
1. Click Open Xml and open the Command.xml file. Configure the commands to be
collected according to the rules in the file.
2. Save the file and click Collect.
After the collection, the system generates the related log package in the
IPT_LMT\hostfile\msgcollect\convert directory and generates the TXT file by default. You
can also specify the storage path in Defined save path.
8.6 AT0 Trunk Record Collect

This function helps you collect AT0 trunk recording files for analyzing and locating system
faults.
Prerequisite

Choose Information Collection > AT0 Trunk Record Collect.
Procedure
1. Select Dsp, and set OSUSlot and Port. Alternatively, select User, and set UserDn and
SubpbxNo.
2. When a call starts or when you want to collect recordings, click Start Collect.
3. When a call ends or when you want to stop collecting recordings, click Stop Collect.

After the collection is complete, the system generates the recording file in
IPT_LMT\hostfile\msgcollect by default. You can also specify the storage path in Defined
save path.
8.7 Message Collect

This function helps you collect voice message files for analyzing and locating system faults.
Prerequisite

Choose Information Collection > Message Collect.
Procedure
1. Set Memory Size to the size of the file to be collected. The default size is 30 MB, and
the maximum size is 100 MB.
2. When a call starts or when you want to collect voice messages, click Start.
3. When a call ends or when you want to stop collecting voice messages, click Stop.
After the collection is complete, the system generates the voice message file in
IPT_LMT\hostfile\msgcollect by default. You can also specify the storage path in Defined
save path.

LMT Operation Guide 9 Information View
9 Information View
About This Chapter

This topic describes how to use the LMT to query the stored information such as alarm
information and log information.
9.1 Alarm File
This topic describes how to use the LMT to export the stored alarm information and view the
alarm information.
9.2 Signaling File
This topic describes how to use the LMT to export and view the stored signaling information.
9.3 Log File
This describes how to use the LMT to export the stored log information (including run logs,
commission logs, and operation logs and view these logs).
9.4 Call Analyzer File
This topic describes how to view the call process for a call that is made based on the SIP, PRA,
R2, SS7 or QSIG trunk.
9.5 Data File
This topic describes how to import and parse the data.bin file on the LMT. The parsing result
is displayed in a data table. You can also generate a command line file using the configuration
file and export the generated command line file on the LMT. All these help users quickly
obtain device configuration information to analyze and locate faults.
9.1 Alarm File

This topic describes how to use the LMT to export the stored alarm information and view the
alarm information.

Choose Information View > Alarm File.

Procedure
 Opening an alarm file
a. Click Open Alarm File.
b. Select an alarm file and click Open.
 Viewing detailed alarm information
a. Double-click an alarm to view detailed alarm information, as shown in Figure 9-1.
Figure 9-1 Detail alarm
You can also right-click an alarm and choose Detail Information from the shortcut menu to view
detailed alarm information.
b. Click or on the Alarm Information tab page to view the

complete alarm information.
c. Click the Alarm Suggestions tab and handle the alarm according to troubleshooting
suggestions.
d. Click the Alarm Information tab. Enter the alarm processing result or fault
information in Remarks.
 Querying alarm information
a. Click Search Alarm.
b. Set search criteria by referring to Parameter Description and click Search.
 Selecting alarm parameters to be displayed
a. Click Config Column.

b. Select the items to be displayed by referring to Parameter Description and click

OK.
r
Device IP IP address of the device that generates an alarm.
Alarm Alarms are classified into different levels according to their severities.
Level The options are as follows:
 Critical: indicates global alarms, such as the power supply fault, that
seriously affect the running of devices. Critical alarms must be handled
immediately to prevent the system from breaking down.
 Major: indicates board or circuit alarms, such as the physical circuit fault,
that occur partially. Major alarms must be handled promptly to ensure
properly running of services.
 Minor: indicates general faults or event alarms that describe the working
status of each board or circuit. Causes of minor alarms must be located to
prevent potential problems.
 Warning: indicates messages that provide information. For example, an
alarm is generated, indicating that a device is restored. Such alarms do not
affect system performance or services. No manual intervention is required.
Device Type of the device that generates an alarm.
Type
Alarm ID ID of an alarm. Each alarm has a unique alarm ID.
Alarm Name of an alarm.
Name
Alarm Detailed information about an alarm.
Content
Event Event type corresponding to a type of alarms.
Type
Alarm Alarm type.
Type
SID Sequence number generated by the system.
Alarm Time when an alarm is generated.
Time
Recover Time when an alarm is cleared.
Time
Acknowle Indicates whether an alarm is acknowledged.
dge Flag
Acknowle Time when an alarm is acknowledged.
dge Time
Clear Flag Indicates whether an alarm is cleared.

r
Clear Time when an alarm is cleared.
Time
9.2 Signaling File

This topic describes how to use the LMT to export and view the stored signaling information.

Choose Information View > Signaling File.
Procedure
 Opening a signaling file
a. Click Open Signaling File.
b. Select a signaling file and click Open.

according to Parameter Description. If the parameters are incorrectly set or need to
be reset, click Reset to reset the parameters.

b. Click Query.
according to Parameter Description. If the parameters are incorrectly set or need to
be reset, click Reset to reset the parameters.
b. Click Filter.
9-3.
Figure 9-3 Signaling result

Records.
For the signaling parameter description, see 7.1 Signaling Collect.
9.3 Log File

This describes how to use the LMT to export the stored log information (including run logs,
commission logs, and operation logs and view these logs).

Choose Information View > Log File.
Procedure
 Opening a log file
a. Click Open Log File.
b. Select a log file and click Open, as shown in Figure 9-4.


b. Select the items to be searched out in the Search area and set parameters according
to Parameter Description.
c. Click Search.
Click Config Column, and select the log parameters to be displayed according to
shortcut menu.
If the exported log is a commission log, you can right-click the log in the display area and select Detail
Information or double-click the log to view the detailed log information. You can use keywords to
search for and view the required information.

 Run log parameter description
r

Slot Slot number of the board.
Content Content of a log.
Level Log level. The options are INFORMATION, WARNING, ERROR, OMU,
and CLI.
Pid Software module number.
 Operation log parameter description
r
Result Command execution result. The options are SUCCESS and FAILED.
Client IP address of the PC where a configuration tool is installed.
IpAddress
Client ID ID of the client for a configuration tool.
Operate Instructions initiated by system users or system scheduled tasks.
Content
UserName Name of the user who initiates an instruction.
CTLType Type of the configuration tool connected to the device, which includes the
CLI, Web, eSight|LMT, BMU, and CENTERSERVER.
NOTE
CENTERSERVER is used for the local node or standby node to record logs of the active
node's data synchronization in a centralized call management network.
 call log parameter description
r
CallerDn Number of the calling party.

Time Time when a call is set up.
CalleeDn Number of the called party.
LogID Log ID.
ReleaseCa Digital identifier of the cause for releasing a call.

r
use
Descriptio Description of the call release cause.
n
9.4 Call Analyzer File

This topic describes how to view the call process for a call that is made based on the SIP, PRA,
R2, SS7 or QSIG trunk.

Choose Information View > Call Analyzer File.
Procedure
1. Click Open Call File, as shown in Figure 9-5.

2. Click Analyze Call Log.

3. Select a call record on the displayed Call Analysis page. The call flow chart of the
selected call is displayed, as shown in Figure 9-6.

r
Time Time when a call starts.

Source Name of the device that initiates a message.
Destinatio Name of the device that receives a message.
n
Protocol SIP, PRA, R2, SS7 and QSIG are included.
Call ID ID of the call process.
Informatio Message type.

r
n
9.5 Data File

This topic describes how to import and parse the data.bin file on the LMT. The parsing result
is displayed in a data table. You can also generate a command line file using the configuration
file and export the generated command line file on the LMT. All these help users quickly
obtain device configuration information to analyze and locate faults.
Method of Accessing the Operation Page

Choose Information View > Data File. The Data File page is displayed.
Parsing Procedure
1. Click Browse next to Please select the dbupgrade.jar file to import the dbupgrade.jar
file.
The version of the dbupgrade.jar file cannot be earlier than V200R003C50SPC700.
2. Click Browse next to Please select the data.bin file and select Data.bin Online or
Data.bin Offline.
The version of the data.bin file cannot be later than that of the dbupgrade.jar file.
− Data.bin Online
i. Select the desired device.
ii. Click Backup the data.bin and wait until Execution Status changes to Back
Up success, as shown in Figure 9-7.
Click Open Directory to view the backup data.bin file.

Figure 9-7 Data.bin Online
iii. Click Start parsing. Wait until the parsing result is displayed in a data table,
Figure 9-8 Data table obtained after parsing
System Tables, User Tables, Trunk Tables, Prefix Tables, and Other Tables
are provided. Enter a table ID or name in the search box to search for the
desired table. Click a table to view the data.

Table data operations are described as follows:

 Click Filter. The search window is displayed. Enter the filter values to
filter out the desired table data.
 Click Config Column and select the desired columns to filter out the
columns to be queried.
 Click Data Export to export table data to the local PC.
 Double-click a table heading row to sort the data in ASCII mode.
− Data.bin Offline
i. Click Data.bin Offline.
ii. Select the data.bin file.
iii. Click Open. The system loads the data.bin file. Wait until the parsing result is
displayed in a data table, as shown in Figure 9-8.
Exporting a Command Line File

1. Click Browse next to Please select the config_cmd file and select the config file in the
installation package of the corresponding version.
If the version of the data.bin file is earlier than V200R003C50SPC700, select the config file of the
V200R003C50SPC700 version. The version of the data.bin file is V200R003C50SPC700 or later, select
the config file of the corresponding version.
2. Click Commands Export.
3. When the message "Parse to commands success!" is displayed, the system automatically
displays the directory where the generated command line file (.txt) is saved.
The default saving directory is the directory where the data.bin file is located, as shown
in Figure 9-9.
Figure 9-9 Exporting a command line file
4. Open the generated command line file and check the data configuration of the device.


LMT Operation Guide

Uploaded by

Copyright:

Available Formats

LMT Operation Guide

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

LMT Operation Guide

Uploaded by

Copyright:

Available Formats

eSpace U1900 Unified Gateway

HUAWEI TECHNOLOGIES CO., LTD.

Trademarks and Permissions

Huawei Technologies Co., Ltd.

Issue 02 (2018-12-29) Huawei Proprietary and Confidential i

6 Alarm Management .................................................................................................................... 20

Issue 02 (2018-12-29) Huawei Proprietary and Confidential ii

7.5 Debug Log .................................................................................................................................................................. 52

Issue 02 (2018-12-29) Huawei Proprietary and Confidential iii

Table 1-1 Main functions

Function Subfunction Description

System - Sets parameters including the language, lock, file

Issue 02 (2018-12-29) Huawei Proprietary and Confidential 1

Function Subfunction Description

Issue 02 (2018-12-29) Huawei Proprietary and Confidential 2

Function Subfunction Description

Issue 02 (2018-12-29) Huawei Proprietary and Confidential 3

Locking the Operation Page

Unlocking the Operation Page

The default unlocking password is Change_Me.

Changing the Unlock Password

Issue 02 (2018-12-29) Huawei Proprietary and Confidential 4

Table 3-1 Parameter description (1)

Parameter Description Setting

Issue 02 (2018-12-29) Huawei Proprietary and Confidential 5

Table 3-2 Parameter description (2)

Issue 02 (2018-12-29) Huawei Proprietary and Confidential 6

About This Chapter

Issue 02 (2018-12-29) Huawei Proprietary and Confidential 7

Accessing Configuration Pages

No. Device number.

Issue 02 (2018-12-29) Huawei Proprietary and Confidential 8

Accessing Configuration Pages

No. Device number.

4.3 Load License

Accessing Configuration Pages

Issue 02 (2018-12-29) Huawei Proprietary and Confidential 9

No. Device number.

Accessing Configuration Pages

Issue 02 (2018-12-29) Huawei Proprietary and Confidential 10

d. Set Execution to activate.

To save a patch, set Execution Mode to save.

4.5 Voice File

Issue 02 (2018-12-29) Huawei Proprietary and Confidential 11

Accessing Configuration Pages

Figure 4-1 MakeTone Configuration

c. Set Voice File Type and click OK.

Table 4-1 Voice package

Voice File Type Voice Package

 Decompress the voice package.

Issue 02 (2018-12-29) Huawei Proprietary and Confidential 12

4.6 Configuration File Management

Accessing Configuration Pages

4.7 Data Upgrade for the Same Model

Accessing Configuration Pages

Issue 02 (2018-12-29) Huawei Proprietary and Confidential 13

4.8 Cross-Model Data Upgrade

Accessing the Configuration Page

Issue 02 (2018-12-29) Huawei Proprietary and Confidential 14