Академический Документы
Профессиональный Документы
Культура Документы
V100R002C01SPC100
Troubleshooting Guide
Issue
02
Date
2012-07-04
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 the warranty of any kind, express or implied.
Website:
http://www.huawei.com
Email:
support@huawei.com
Issue 02 (2012-07-04)
eSpace UC
Troubleshooting Guide
Contents
Contents
1 Troubleshooting Overview ............................................................................................................. 1
1.1 Fault Levels ...................................................................................................................................................... 1
1.2 Precautions ....................................................................................................................................................... 2
1.3 Requirements for Maintenance Personnel ........................................................................................................ 3
1.4 Overall Troubleshooting Process...................................................................................................................... 3
1.4.1 Overall Troubleshooting Flowchart......................................................................................................... 4
1.4.2 Collecting Fault Scenario Information .................................................................................................... 4
1.4.3 Evaluating a Fault ................................................................................................................................... 4
1.4.4 Locating and Rectifying the Fault ........................................................................................................... 5
1.4.5 Verifying That the Fault Is Rectified ....................................................................................................... 5
1.4.6 Generating a Troubleshooting Report ..................................................................................................... 5
1.4.7 Seeking Help from Huawei ..................................................................................................................... 5
1.5 Huawei Technical Support ............................................................................................................................... 6
Issue 02 (2012-07-04)
ii
eSpace UC
Troubleshooting Guide
Contents
Issue 02 (2012-07-04)
iii
eSpace UC
Troubleshooting Guide
Contents
Issue 02 (2012-07-04)
iv
eSpace UC
Troubleshooting Guide
1 Troubleshooting Overview
Troubleshooting Overview
Fault Levels
Depending on the impact and scope of a fault, faults are classified as either emergency faults
or ordinary faults.
1.2
Precautions
This topic describes the precautions to be taken during fault locating and handling.
1.3
Description
Locating
Method
Handling Method
Emergen
cy fault
Recover services
immediately and
locate the root causes
Issue 02 (2012-07-04)
eSpace UC
Troubleshooting Guide
1 Troubleshooting Overview
Fault
Level
Ordinary
fault
Description
Locating
Method
Handling Method
as possible.
of the fault.
Criteria
Access service
More than 20% voice call services fail for more than 60 seconds.
More than 20% data services fail for more than 60 seconds.
CDR service
More than 50% CDR services fail for more than 60 minutes.
Service management
1.2 Precautions
This topic describes the precautions to be taken during fault locating and handling.
Comply with the operation regulations and industry security regulations to ensure your
safety and equipment security.
Take electrostatic discharge (ESD)-preventive measures; for example, wear ESD wrist
straps when replacing device parts.
Record information about all significant operations, for example, restarting a process or
enabling the debug function. Before performing such operations, check the feasibility of
the operations, back up data, and prepare emergency and safety measures. Ensure that
the operations are performed by qualified engineers.
Issue 02 (2012-07-04)
eSpace UC
Troubleshooting Guide
1 Troubleshooting Overview
Have a basic knowledge of network devices, Windows and Linux operating systems, and
SQL Server and Oracle databases; be capable of using the common operation commands
related to network devices, operating systems, and databases; be capable of
implementing maintenance using operation commands.
Be familiar with the network of the UC service system and physical connections between
onsite devices.
Be familiar with the service process and system structure of the UC, and be skilled in
operating the UC components.
Issue 02 (2012-07-04)
eSpace UC
Troubleshooting Guide
1 Troubleshooting Overview
Services that are affected by the fault, and the scope and impact of the fault
Operations that a user or a maintenance engineer performed before the fault occurred
Measures that have been taken after the fault occurred and the results
Issue 02 (2012-07-04)
eSpace UC
Troubleshooting Guide
1 Troubleshooting Overview
Component layer: Locate the specific component where the fault occurred, for example,
a database.
Module layer: After finding the faulty component, locate the faulty module, for example,
the database listening port.
Symptom
Fault locating
Troubleshooting
Preventive suggestions
Issue 02 (2012-07-04)
eSpace UC
Troubleshooting Guide
1 Troubleshooting Overview
Please...
At...
Come across an
emergency fault
4008302118
View troubleshooting
cases
Come across an
ordinary fault
Issue 02 (2012-07-04)
eSpace UC
Troubleshooting Guide
If a fault cannot be rectified, collect fault information and send it to Huawei technical support.
2.2
If the fault can recur, and the description or screenshots of the configuration and operations
performed before the fault occurs are obtained, the fault can be located and rectified easily.
2.3
Signaling Tracing
Packet Capture
Packets are captured and analyzed to check the correctness. Therefore, packet capture is a
major measure to locate faults.
2.6
Log Collection
Each UC component provides the log function to record system operation and running
information, including fault information.
2.7
This topic describes the common query commands in the Linux operating system, Oracle
database, Unified Gateway, and IAD.
Issue 02 (2012-07-04)
eSpace UC
Troubleshooting Guide
Procedure
Step 1 Go to the installation directory of the eSpace client.
1.
2.
Description
log
config
capture1.cap
ecs.ini
plugin.ini
server.ini
Issue 02 (2012-07-04)
eSpace UC
Troubleshooting Guide
File/Folder Name
Description
system.txt
USBPhone.ini
----End
Prerequisites
The eSpace EMS has been deployed.
Context
The eSpace EMS manages the security, faults, performance, topology, access, and
configurations.
The eSpace EMS can trace the Session Initiation Protocol (SIP) signaling, primary rate access
(PRA) signaling, R2 signaling, Signaling System No.7 (SS7) signaling, and user messages.
Tracing signaling affects the performance of the Unified Gateway. Therefore, when signaling does not
need to be traced, stop the corresponding tracing task in time.
Procedure
Step 1 Log in to the eSpace EMS GUI.
Step 2 Choose Resource > Topology Management from the main menu.
The Topology Management page is displayed.
Step 3 In the topology, select the target NE, click
as shown in Figure 2-1.
The XXX Management window is displayed. In the window name, XXX indicates an NE
name.
Figure 2-1 Topology view
eSpace UC
Troubleshooting Guide
Step 5 Right-click a signaling type (for example, Broadband Signal > SIP), as shown in Figure 2-2.
Figure 2-2 Creating a signaling tracing task
Issue 02 (2012-07-04)
10
eSpace UC
Troubleshooting Guide
Click Lock, set the search criteria (case sensitive), and click Search. Fuzzy query is
supported. The signaling meeting the search criteria is displayed in the window.
----End
Follow-up Procedure
Analyze signaling to locate the fault by referring to 3.4 Signaling Analysis.
The packet filter and recombination tool capfil is obtained, which can be downloaded on
Internet.
Issue 02 (2012-07-04)
11
eSpace UC
Troubleshooting Guide
Step 4 Query the current PC network interface card (NIC) index and description to determine the
NIC used for packet capture.
1.
Open the Local Area Connection Properties dialog box to query the NIC model used,
as shown in Figure 2-5.
2.
Issue 02 (2012-07-04)
Run the dumpcap -D command on the CLI to query the NIC index number, as shown in
Figure 2-6.
12
eSpace UC
Troubleshooting Guide
Description
-i
-w
-b
filesize
files
To obtain the online help of the dumpcap command, run the dumpcap -h command.
----End
Issue 02 (2012-07-04)
13
eSpace UC
Troubleshooting Guide
Reads multiple files in wildcard form and generates a file after filtering
Step 1 Change the file name extension of the captured packets in step 1 to .cap.
Step 2 Save the capfil.exe file and packets in the same path, for example, D:\cap.
Step 3 Open the CLI, and run the cd dir command to go to the packet directory.
In the preceding command, dir specifies the packet path. If the packet path is not on disk C, run the
preceding command, and then enter disk letter:, for example, d: and press Enter.
Step 4 Filter and recombine packets by filtering criteria based on the fault scenario.
The parameters such as time, IP address, and port number in the following commands are examples.
Change them based on the site scenario.
Run the following command to filter all packets. The command contains the fault source
IP address, and fault occurrence start time and end time. The obtained data after filtering
is stored in the out.cap file.
capfil -r *.cap -w out.cap -stime "2011-08-8 10:00:00" -etime "2011-08-8 10:30:00"
-ip "10.166.10.10"
Run the following command to filter packets by port number. Assume that the port
number is the default SIP port number 5060. The data obtained after filtering is stored in
the out2.cap file.
capfil -r *.cap -w out2.cap -udpport 5060
Run the following command to filter packets by IP address. The packets of the IP
addresses in the command are obtained. The obtained data after filtering is stored in the
out3.cap file.
capfil -r *.cap -w out3.cap -ip "10.166.10.10" -ip "10.166.10.11" -ip "10.166.10.12"
To obtain the online help of the capfil command, run the capfil/? command.
----End
Issue 02 (2012-07-04)
14
eSpace UC
Troubleshooting Guide
Context
In UC solution, only the IAD supports remote packet capture,The IAD does not support
remote packet capture on the VLAN. If the VLAN tag is configured for data or the VLAN is
configured for the FE port, remote packet capture cannot be performed.
Procedure
Step 1 Install the IAD packet capture tool recvTool on a PC.
Step 2 Log in to the IAD as the administrator.
This topic describes how to capture the user signaling and media stream on IAD132E(T) port
3.
Step 3 Set the packet export network port to FE1 or FE2 port on the IAD.
TERMINAL(advanced-config)#capture outinterface fe
Step 4 Set the IP address of the packet capture server to the IP address of the PC whe re the IAD
packet capture tool is installed. Use the default port number 58000.
TERMINAL(advanced-config)#capture server ipaddress 192.166.1.200
Step 6 Enable the user media stream capture function on port 3 and set the packet capture direction
to two-way.
TERMINAL(advanced-config)#capture media start direction all userport 3
Step 7 Double-click
Step 8 Click ... and enter the name of the file for storing captured packets, for example, iad1, as
shown in Figure 2-8.
Issue 02 (2012-07-04)
15
eSpace UC
Troubleshooting Guide
server started
192.163.1.40
58000
capture mode:
output interface:
all captured
FE1/2
=======================================================
If the message "WARNING:The capture server can not reach!" is displayed, the connection has not
been established. Check the connection after 30 seconds. If the message is not displayed, the
connection has been established.
When the size of the file for storing captured packets reaches 30 MB, the file is saved automatically,
a new file is generated, and the packet capture continues.
Do not operate the file during packet capture. Otherwise, the file may be incomplete.
Issue 02 (2012-07-04)
16
eSpace UC
Troubleshooting Guide
2.5.3 Wireshark
Wireshark is a tool for capturing and analyzing network packets. Wireshark converts the
binary data streams to text and figures that are easy to understand. Use Wireshark to capture
signaling on a certain port to determine whether the port is faulty.
Tool Introduction
Obtaining Method
Access http://www.wireshark.com and download the Wireshark installation file.
User
Maintenance engineers
Test engineers
Function
Captures packets and analyzes signaling such as SIP, PRA, SS7, and R2.
Function Description
The Wireshark can run in various operating systems, such as the UNIX, Linux, and Windows
operating systems.
The Wireshark provides the following functions:
Issue 02 (2012-07-04)
17
eSpace UC
Troubleshooting Guide
Menu Pane
The menu pane contains the following menus:
File
Contains items to open and merge capture files, save, print, or export capture files in
whole or in part, and to exit the Wireshark.
Edit
Contains items to find a packet, mark one or more packets, and set your preferences
(such as fonts, color, time format, and parsing application), and then save the preferences
as default settings.
View
Controls the display of the captured data, such as time format and color of packets
transmitted using different protocols.
Go
Contains items to go to a specific packet.
Capture
Allows you to set capture parameters, including selecting network adapters, starting and
stopping captures.
Analyze
Allows you to enable or disable protocol dissectors.
Statistics
Contains items to display various statistic windows, including a summary of the packets
that have been captured and displaying protocol hierarchy statistics.
Issue 02 (2012-07-04)
Help
18
eSpace UC
Troubleshooting Guide
Contains items to help users, such as access to some basic help, a list of supported
protocols, and user guides.
Filter Pane
Specifies the filter expression. You can set the filter expression to filter out only the required
packets for analysis. For details about the filter expression usage, see SIP Protocol Analysis.
The Wireshark displays the protocols and types of the packets that can be parsed.
The Wireshark marks the packets whose formats or processes are faulty with colors.
Because the Wireshark is not entirely intelligent, the marks can be used only for reference, not as the
analysis basis. For detailed analysis, view the packet content and analyze the packet based on the
signaling process.
2.Common Operations
Context
The Wireshark can be used only after it is bound to a network adapter. After being installed on
a PC, the Wireshark can capture only the packets passing through this network adapter.
Therefore, before using the Wireshark to capture packets, configure the network to ensure that
packets can be sent to the network adapter to which the Wireshark is bound.
Issue 02 (2012-07-04)
19
eSpace UC
Troubleshooting Guide
Procedure
Step 1 Double-click
Issue 02 (2012-07-04)
20
eSpace UC
Troubleshooting Guide
Main areas on the Wireshark: Capture Options page are described as follows:
Capture
Interface
Specifies the network adapter for capturing packets.
After the Wireshark is installed, the system automatically generates a logical network adapter,
as shown in Figure 2-11. In addition to the logical network adapter, a physical network
adapter is required. During the actual packet capture, select a correct physical network adapter,
especially for a host with multiple network adapters. A physical network adapter will be
displayed in the drop-down list box only after the WinPcap is installed. The network adapter
in this example is only a logical network adapter, not the physical network adapter for
capturing packets.
Capture Filter
Specifies the filter criteria. The Wireshark captures only the packets that comply with
the filter criteria. For example, if Capture Filter is set to host 10.138.5.10, only
packets sent and received by the host whose IP address is 10.138.5.10 will be
captured.
Issue 02 (2012-07-04)
21
eSpace UC
Troubleshooting Guide
Table 2-3 describes the filter criteria categories specified by Capture Filter.
Table 2-3 Filter criteria categories specified by Capture Filter
Filter Criteria Category
Example
host 192.168.0.10
tcp port 80
Capture File(s)
Specifies the path for automatically saving the captured packets as files. Ensure that the
destination hard disk has sufficient free space.
Display Options
Specifies whether to display the real-time capture results during the packet capture.
Issue 02 (2012-07-04)
Select Update list of packets in real time. The packet list is displayed on the
Wireshark main page.
Select Automatic scrolling in live capture. If the captured results exceed one screen,
the results are displayed in automatic scrolling mode.
Deselect Hide capture info dialog. The Captured Packets page shown in Figure
2-12 is displayed during the packet capture, with the real-time information about the
numbers of captured packets of various protocols.
22
eSpace UC
Troubleshooting Guide
Issue 02 (2012-07-04)
23
eSpace UC
Troubleshooting Guide
Issue 02 (2012-07-04)
24
eSpace UC
Troubleshooting Guide
Operator
eq
==
Equal to
ip.addr==10.138.21.5
ip.addr eq 10.138.21.5
ne
!=
Not equal to
!(ip.addr == 10.138.21.5)
!(ip.addr eq 10.138.21.5)
gt
>
Greater than
frame.pkt_len > 10
frame.pkt_len gt 10
lt
<
Smaller than
frame.pkt_len < 128
frame.pkt_len lt 128
ge
>=
le
<=
Logical Operators
The Wireshark can use logical operators to combine multiple filter expressions. For example,
if you want to filter out packets that are transmitted using the GPRS tunneling protocol (GTP)
and through the IP address 10.138.21.5, use the filter expression gtp &&
ip.addr==10.138.21.5. Table 2-5 describes the logical operators used in filter expressions.
Table 2-5 Logical operators used in filter expressions
English
Operator
and
&&
And
ip.addr==10.0.0.5 and
tcp.flags.fin
or
||
Or
ip.addr==10.0.0.5 or
ip.addr==192.1.1.1
not
Not
not llc
Issue 02 (2012-07-04)
25
eSpace UC
Troubleshooting Guide
a.
b.
Issue 02 (2012-07-04)
Select a field, select a relation, and then enter a value in the Value (IPv4 address)
test box, as shown in Figure 2-16.
26
eSpace UC
Troubleshooting Guide
c.
Click OK.
Check whether a filter expression is correct.
If the filter expression is correct, the background color of the Filter text box is green,
as shown in Figure 2-17.
Figure 2-17 Displayed Filter text box if the filter expression is correct
If the filter expression is incorrect, the background color of the Filter text box is dark
pink, as shown in Figure 2-18.
Figure 2-18 Displayed Filter text box if the filter expression is incorrect
2.
ip
icmp
tcp
gtp
gre
http
IP address
ip.addr==10.161.225.1
Source IP address
ip.src==10.161.225.1
Destination IP address
ip.dst==10.161.225.1
Issue 02 (2012-07-04)
27
eSpace UC
Troubleshooting Guide
The Ethernet allows a maximum data frame length of 1,500 bytes and the IEEE 802.3 allows a
maximum data frame length of 1492 bytes. Maximum data frame length at the link layer is called a Max
Transfer Unit (MTU). Most networks have an MTU. If a packet sent from the IP layer is greater in size
than the MTU at the link layer, the packet must be divided into fragments whose sizes are smaller than
the MTU.
Issue 02 (2012-07-04)
28
eSpace UC
Troubleshooting Guide
1.
2.
Figure 2-20 Setting a field as a filter criterion and starting the filtering immediately
The differences between the Prepare a Filter menu and the Apply as Filter menu are as
follows:
Issue 02 (2012-07-04)
After you choose Apply as Filter > Selected, the selected field is set as the filter
criterion directly and the data packets that meet the filter criterion are displayed
immediately.
After you choose Prepare a Filter > Selected, the selected field is displayed in the
Filter text box but no filter is performed. You can modify the filter criterion as
required. After you click Apply, data packets that meet the filter criterion are
displayed, as shown in Figure 2-21.
29
eSpace UC
Troubleshooting Guide
Typical Scenario
1.SIP Protocol Analysis
This topic describes how to use the Wireshark to analyze SIP signaling.
After starting the Wireshark, enter sip in the Filter text box. Then all SIP signaling that passes
through the network adapter is filtered out.
After a signaling record is selected, the protocol layer information about the signaling
record is displayed in the protocol layer description window.
Issue 02 (2012-07-04)
30
eSpace UC
Troubleshooting Guide
Physical layer
The first layer in the protocol layer description window is the physical layer, which
contains Frame Number and Packet Length, as shown in Figure 2-23.
Issue 02 (2012-07-04)
Network layer
31
eSpace UC
Troubleshooting Guide
The third layer in the protocol layer description window is the network layer, which
contains the source IP address (Source), destination IP address (Destination), packet
length (Total length), and checksum (Header checksum), as shown in Figure 2-25.
Figure 2-25 Network layer of the SIP protocol
The length of a packet exceeds the maximum length allowed by a certain device.
Issue 02 (2012-07-04)
32
eSpace UC
Troubleshooting Guide
The network adapters of certain devices may calculate the checksum of the User
Datagram Protocol (UDP) layer. If the checksum is incorrect, the network adapter of
the device may discard the packet.
Application layer
The fifth layer in the protocol layer description window is the application layer, which
contains the SIP protocol details.
The signaling record consists of Request-Line and Message Header. If a message
includes a message body, Message Body is also included, as shown in Figure 2-27.
Figure 2-27 Request messages at the application layer of the SIP protocol
The message header information can be used to locate faults, as shown in Figure 2-28.
Figure 2-28 Message header information
Issue 02 (2012-07-04)
Call-ID
33
eSpace UC
Troubleshooting Guide
Then the signaling records that share the same Call-ID are displayed in the captured
packet list window. The Call-ID that is filtered out is displayed in the Filter text box
on the toolbar, as shown in Figure 2-30.
Figure 2-30 Value of Filter on the toolbar
From
Source address of the request.
To
Logical receiver of the request.
User-Agent
Information about the User Agent Client (UAC) that initiates the request.
If the value of User-Agent is Conf-serv/3GPP, the request is initiated by a personal
computer (PC).
Common Tips
Changing the Time Display Mode
Issue 02 (2012-07-04)
34
eSpace UC
Troubleshooting Guide
The absolute time generated after the gateway GPRS support node (GGSN) users use the
tmf2cap to convert .tmf files to .cap files may be incorrect. You can use the relative time to
view the packet delay information.
Generally, data packets are displayed by relative time in the program, which is the interval
between a subsequent packet and the initial packet.
You can choose View > Time Display Format to change the time display mode.
The Time Display Format menu contains four options, as shown in Figure 2-31.
Seconds Since Previous Captured Packet, which is used for viewing the time delay
between packets.
Issue 02 (2012-07-04)
35
eSpace UC
Troubleshooting Guide
Figure 2-32 Parsed diameter protocol after the diameter format library is loaded
If the HTTP application has been enabled on port 1031 in an office, select the data
packet on port 1031.
2.
Issue 02 (2012-07-04)
36
eSpace UC
Troubleshooting Guide
You must choose Analyze > Decode As and select a protocol each time when you start the
Wireshark to parse a non-standard port application protocol.
3.
Select an application protocol, and then click Apply, as shown in Figure 2-34.
Figure 2-34 Customizing a protocol for parsing the non-standard port application protocol
4.
Click OK.
Issue 02 (2012-07-04)
Use the filter to display the information that you want to save as files separately, and
then click displayed in the Packet Range area.
Click Range, and then enter a number range, for example 1-1038. Then packets
numbered from 1 to 1038 are saved as a file.
37
eSpace UC
Troubleshooting Guide
2.
Enter the name of the result file to be merged, and then click Save.
Select the file to which you will merge the result file, and then click Open.
Issue 02 (2012-07-04)
38
eSpace UC
Troubleshooting Guide
By default, all traffic waveform charts are displayed. After you set the filter criteria in the
filter, only traffic waveform charts that meet the filter criteria are displayed.
Issue 02 (2012-07-04)
39
eSpace UC
Troubleshooting Guide
In the basic packet information, such as all types of packets generated during mobile
phone conversions, the TCP and UDP tab pages are displayed. On the TCP tab page, the
following columns are included: Address A, Port A, Address B, Port B, Bytes, Bytes
A->B, and Bytes A<-B.
On the TCP and UDP tab pages shown in Figure 2-37, packets that have same address
but different port numbers are displayed in different columns but are calculated together.
Choose Statistics > Summary to calculate the total packet bytes. Before calculating the
total packet bytes, ensure that the filter criteria are set.
After the preceding packet length is calculated, subtract 14 bytes (layer 2 information)
and packet encapsulation added to the original packets by GGSN or Serving GPRS
Support Node (SGSN), such as generic routing encapsulation (GRE) or GPRS tunneling
protocol (GTP) encapsulation. The various encapsulation lengths are as follows:
UDP header
8 bytes
IP header
20 bytes
GRE header
4 bytes
Lower part: area for displaying the original code streams for the selected packet
In the Wireshark, you can enter filter criteria in the Filter text box shown in Figure 2-38; the
packets that meet the filter criteria are displayed.
For example, to query the packets that are sent from or to the IP address 10.0.0.1, enter
ip.addr==10.0.0.1 in the Filter text box, and then click Apply. The packets that are sent from
or to the IP address 10.0.0.1 are displayed, as shown Figure 2-38.
Issue 02 (2012-07-04)
40
eSpace UC
Troubleshooting Guide
Use the Wireshark to open the bearer network port captured file in .pcap or .cap format.
2.
Enter (rtp) && (rtp.p_type > 34) or rtpevent in the Filter text box.
3.
Press Enter.
All files that are transferred using RFC 2833 in the captured information are filtered out,
as shown in Figure 2-39.
Issue 02 (2012-07-04)
41
eSpace UC
Troubleshooting Guide
2833 packets use the sampling mode to send a number for multiple times. Numbers are
separated by RTP packets whose Event is TRUE, as shown in Figure 2-40. The
procedure for sending the number 6 is used as an example.
Issue 02 (2012-07-04)
The message "End of Event: False" in the packet parsing area indicates that the
number 6 has not been sent completely.
42
eSpace UC
Troubleshooting Guide
Issue 02 (2012-07-04)
The message "End of Event: True" in the packet parsing area indicates that the
number 6 has been sent to the media stream. Then the number collection process is
complete.
43
eSpace UC
Troubleshooting Guide
Issue 02 (2012-07-04)
44
eSpace UC
Troubleshooting Guide
5.
6.
7.
Click OK.
A page shown in Figure 2-44 is displayed. The captured UDP packets have been
converted to RTP packets. Then perform 1 through 3 to verify that the packet
information has been transmitted to the media stream.
Issue 02 (2012-07-04)
45
eSpace UC
Troubleshooting Guide
Log File
Path
Description
BMU (for
Windows)
bmu.log
Installation
directory\eSpace_UC\eSpac
e_UC_Server\Logs\BMU
bmu.log.* (*
indicates a
number)
Issue 02 (2012-07-04)
46
eSpace UC
Troubleshooting Guide
NE
BMU (for
Linux)
Log File
Path
Description
BMU_error.log
Installation
directory\eSpace_UC\eSpac
e_UC_Server\Logs\BMU
winMax.log
Installation
directory\eSpace_UC\eSpac
e_UC_Server\Logs\BMU
Records information
about the connection
between the BMU and
the winMax charging
system.
eaus.log
Installation
directory\eSpace_UC\eSpac
e_UC_Server\Server\logfile
\updateServer
bmu.log
Installation
directory/eSpace_UC/eSpac
e_UC_Server/Logs/BMU
bmu.log.* (*
indicates a
number)
eServer(for
Windows)
BMU_error.log
Installation
directory/eSpace_UC/eSpac
e_UC_Server/Logs/BMU
winMax.log
Installation
directory/eSpace_UC/eSpac
e_UC_Server/Logs/BMU
Records information
about the connection
between the BMU and
the winMax charging
system.
eAUS.log
Installation
directory/eSpace_UC/eSpac
e_UC_Server/Logs/BMU
eMonitor.log
Installation
directory\eSpace_UC\eSpac
e_UC_Server\Logs\Monitor
Tool
imGserver.debug
Installation
directory\eSpace_UC\eSpac
e_UC_Server\Logs\eServer
imGserver.log
Issue 02 (2012-07-04)
47
eSpace UC
Troubleshooting Guide
NE
Log File
Path
Description
Imserver.debug
Installation
directory\eSpace_UC\eSpac
e_UC_Server\Logs\eServer
eMonitor.log
Installation
directory/eSpace_UC/eSpac
e_UC_Server/Logs/Monitor
Tool
imGserver.debug
Installation
directoryeSpace_UC/eSpac
e_UC_Server/Logs/eServer
Installation
directory/eSpace_UC/eSpac
e_UC_Server/Logs/eServer
Imserver.log
eServer(for
Linux)
imGserver.log
Imserver.debug
Imserver.log
MAA (for
Windows)
MBServer.log
Installation
directory\eSpace_UC\eSpac
e_UC_Server\Server\MAA\
webapps\MBServer\logs
MAA (for
Linux)
MBServer.log
Installation
directory/eSpace_UC/eSpac
e_UC_Server/Logs/MAA
CDRServer
BILLLog_0.txt
Installation
directory\eSpace_UC\eSpac
e_CDR\CDRServer\CDRSe
rverlog
FTPLog_0.txt
Installation
directory\eSpace_UC\eSpac
e_CDR\CDRServer\CDRSe
rverlog
MonitorLog_0.txt
Installation
directory\eSpace_UC\eSpac
e_CDR\CDRServer\CDRSe
rverlog
mmlLog_0.txt
Installation
directory\eSpace_UC\eSpac
e_CDR\CDRServer\CDRSe
rverlog
eSpace
Meeting
server
mcms_0104_*.lo
g (* indicates a
number)
Installation
directory\eSpace_UC\eSpac
e_Meeting\log
eSpace
Meeting
client
mcstub_*1.log (*
indicates a
number)
Installation
directory\eSpace_UC\Enter
Issue 02 (2012-07-04)
48
eSpace UC
Troubleshooting Guide
NE
Log File
Path
Description
prise_UC\cwbin\trace
Path of client logs for
eSpace Meetings that are
accessed from Internet
Explorer:
Installation
directory\program data
folder of the current system
user\CenWave\trace
On the Windows XP
operating system, the
default value of program
data folder of the current
system user for
administrator login is as
follows:
C:\Documents and
Settings\administrator\Appl
ication Data\
On the Windows 7
operating system, the
default value of program
data folder of the current
system user for
administrator login is as
follows:
C:\Users\administrator\App
Data\Local\Temp\
Console
server
Softconsole
Issue 02 (2012-07-04)
CTISRVLog.txt
Installation
directory\eSpace_UC\eSpac
e_Console\Console_Server\
log
CTIServerLog.lo
g
Installation
directory\eSpace_UC\eSpac
e_Console\Console_Server\
log
Records commissioning
information.
Installation
directory\eSpace_UC\eSpac
e_Console\Console_Server\
fr_exception
All.log
Installation
directory\eSpace_UC\eSpac
e_Console\Soft_Console\Lo
g
Records Softconsole
operation and service
information.
sipx.log
Installation
directory\eSpace_UC\eSpac
e_Console\Soft_Console\Lo
Records information
related to the SIP
protocol.
49
eSpace UC
Troubleshooting Guide
NE
Log File
Path
Description
g
eDirectory
N/A
OpenLDAP
N/A
BMU
Copy log files from the path specified in Table 2-6 in 2.6.1 UC Log Files.
eSpace
To obtain eSpace client logs, use the debughelp.bat tool. For details, see
2.3 Fault Information Collection on the eSpace Client.
To obtain eSpace server logs, copy the imGserver.debug, imGserver.log,
Imserver.debug, and Imserver.log files from the paths specified in Table
2-6 in 2.6.1 UC Log Files.
MAA server
Copy log files from the path specified in Table 2-6 in 2.6.1 UC Log Files.
eSpace
Meeting
server and
client
Copy log files from the path specified in Table 2-6 in 2.6.1 UC Log Files.
UMS server
Log in to the UMS web management page, and choose UMS > System
Log Management from the navigation tree on the left.
CDRServer
Copy log files from the path specified in Table 2-6 in 2.6.1 UC Log Files.
Console
system
Copy log files from the path specified in Table 2-6 in 2.6.1 UC Log Files.
Unified
Gateway
IAD
The IAD reports logs to the log server, enabling users to view the logs on
the log server.
The IP phone reports logs to the log server, enabling users to view the logs
on the log server.
For details, see Troubleshooting > Methods of Locating Faults >
Displaying Debugging Logs in the Administrator Guide of the IP phone
in the corresponding model.
Issue 02 (2012-07-04)
50
eSpace UC
Troubleshooting Guide
Command
who
Processes
User processes:
ps
All running processes:
ps aux
Ten processes that have the highest CPU usage:
ps aux |head -1 ;ps aux |sort -rn +2 |head -10
Resource usage
top
Memory information
CPU
cat /proc/cpuinfo
cat /proc/partitions
df
File attributes
ls -l
ifconfig -a
Port information
Issue 02 (2012-07-04)
51
eSpace UC
Troubleshooting Guide
Command
Query Result
Datab
ase
status
SQL> select
INSTANCE_
NAME,
STATUS
from
v$instance;
> lsnrctl
status
LISTENER
Listen
er
status
INSTANCE_NAME
STATUS
---------------- -----------eSpace
OPEN
LISTENER
TNSLSNR for Linux: Version 11.1.0.6.0
- Production
Start Date
Uptime
Trace Level
Security
SNMP
Listener Log File
18-AUG-2011 11:09:47
0 days 8 hr. 21 min. 41 sec
off
ON: Local OS Authentication
OFF
/oracle/diag/tnslsnr/eSpace2/listener/alert/log.xml
Listening Endpoints Summary...
(DESCRIPTION=(ADDRESS=(PROTOCOL=tcp)(HOST=eSpace2)(PORT=15
21)))
Services Summary...
Service "eSpace" has 1 instance(s).
Instance "eSpace", status READY, has 1 handler(s) for this
service...
Service "eSpace_XPT" has 1 instance(s).
Instance "eSpace", status READY, has 1 handler(s) for this
service...
The command completed successfully
Servic
e
name
> tnsping
eSpace
Issue 02 (2012-07-04)
52
eSpace UC
Troubleshooting Guide
Cont
ent
to Be
Quer
ied
Command
Query Result
Data
files
Datab
ase
tables
paces
SQL> select
NAME,
CREATE_B
YTES
/1024/1024||'
M'
FILE_SIZE
from
V$DATAFIL
E;
SQL> select
STATUS,
TABLESPA
CE_NAME
from
DBA_TABL
ESPACES;
NAME
FILE_SIZE
/oracle/oradata/eSpace/system01.dbf
300M
/oracle/oradata/eSpace/sysaux01.dbf
120M
/oracle/oradata/eSpace/undotbs01.dbf
200M
/oracle/oradata/eSpace/users01.dbf
4 rows selected.
5M
TABLESPACE_NAME
--------- -----------------------------ONLINE
SYSTEM
ONLINE
ONLINE
SYSAUX
UNDOTBS1
ONLINE
TEMP
ONLINE
USERS
5 rows selected.
Numb
er of
datab
ase
proce
ss
conne
ctions
SQL> select
count(*)
from
v$process;
Numb
er of
datab
ase
SQL> select
count(*)
from
Issue 02 (2012-07-04)
COUNT(*)
---------23
COUNT(*)
----------
53
eSpace UC
Troubleshooting Guide
Cont
ent
to Be
Quer
ied
Command
Query Result
sessio
n
conne
ctions
v$session;
Numb
er of
concu
rrent
datab
ase
conne
ctions
SQL> select
count(*)
from
v$session
where
status='ACTI
VE';
Maxi
mum
numb
er of
conne
ctions
allow
ed by
the
datab
ase.
SQL> select
value from
v$parameter
where
name='proces
ses';
22
COUNT(*)
---------21
VALUE
-----------------1100
Command
Description
show cliuser
N/A
System
information
Version
information
show version
User
information
(including the
type, status, and
service)
Issue 02 (2012-07-04)
54
eSpace UC
Troubleshooting Guide
Content to Be
Queried
Command
Description
Board status
Trunk
configuration
Trunk circuit
and status
Status of the
PRA trunk link
Call source
information
show callsourceno
N/A
Conference
information
show conference
show pbxgroup
PBX group
information
show subscriber by
pbxgroupno <0-254>
show telephonegroup
groupno 0
show telephonist
telephonegroupno 0
Issue 02 (2012-07-04)
55
eSpace UC
Troubleshooting Guide
Content to Be
Queried
Command
Description
optional. You can query the value range
by pressing Tab.
Trunk bearer
configuration
Issue 02 (2012-07-04)
56
eSpace UC
Troubleshooting Guide
Alarm Analysis
Alarms are important prompt messages for faults or events. Alarms may be generated when
faults occur.The eSpace EMS provides the alarm management function for all NEs in the UC
solution.
3.2
Some faults are caused by poor network connection or network disconnection. You can test
the network connection and quality to rectify the faults.
3.3
Configuration Analysis
When a fault occurs, analyze the current system configurations and check the connections
based on the fault symptom to locate the fault.
3.4
Signaling Analysis
Signaling analysis verifies port signaling and messages. Therefore, signaling analysis is a
major measure to locate faults.
3.5
Log Analysis
Logs record all system operation and running information. Therefore, you can view and
analyze logs to locate faults.
Prerequisites
The eSpace EMS has been deployed.
Issue 02 (2012-07-04)
57
eSpace UC
Troubleshooting Guide
Context
When a fault occurs, check whether any alarms are reported. If alarms are reported, find the
alarms that are relevant to the fault and clear the alarms. In this way, the fault can be rectified.
The priority for rectifying faults depends on the alarm severity.
Critical: global alarms that seriously affect the running of devices, for example, power
supply faults. Critical alarms must be cleared immediately to prevent the system from
breaking down.
Major: board or physical circuit alarms. Major alarms must be cleared immediately to
ensure normal running of services.
Minor: alarms that describe the running status of boards or physical circuits. When a
minor alarm is reported, you must locate the cause to prevent potential problems.
Warning: messages that are displayed, for example, a message indicating that a device
has been restored. Warning alarms do not affect system performance or services;
therefore, no action is required.
The eSpace EMS provides possible causes and alarm processing procedure for each alarm.
Analyze the possible fault cause by referring to the value of Probable cause, and rectify the
fault by referring to the value of Procedure.
Procedure
Step 1 Log in to the eSpace EMS as the administrator.
Step 2 Choose Fault > Current Alarms in the main menu.
The current alarm page is displayed, where you can query and filter alarms by filter criteria,
as shown in Figure 3-1.
Figure 3-1 Alarm page
Issue 02 (2012-07-04)
58
eSpace UC
Troubleshooting Guide
Follow-up Procedure
After the fault is rectified, select the corresponding alarm and click Clear.
Context
Table 3-1 describes the IP bearer network quality.
Issue 02 (2012-07-04)
59
eSpace UC
Troubleshooting Guide
One-Way Delay
(ms)
Jitter (ms)
Good
40
0.1%
10
Poor
100
1%
20
Terrible
400
5%
60
Table 3-2 lists the data service usage that is available based on the IP bearer network quality.
Table 3-2 Data service usage
Network Status
Good
Poor
Terrible
Fax
Transparent
transmission
Available
Unavailable
Unavailable
T.38
Available
Available
Unavailable
Transparent
transmission
Available
Unavailable
Unavailable
Modem
Procedure
1.
2.
3.
Issue 02 (2012-07-04)
If data packets are received from the peer device, the host is properly connected to
the peer device, as shown in Figure 3-3.
60
eSpace UC
Troubleshooting Guide
If the message "Request timed out." is displayed, the host is disconnected from the
peer device.
1.
2.
3.
Description
-a
Displays active TCP connections and TCP and UDP ports monitored by the
computer.
-n
Displays active TCP connections and the IP addresses and port numbers.
-o
The enabled or occupied port numbers are displayed, as shown in Figure 3-4.
Issue 02 (2012-07-04)
61
eSpace UC
Troubleshooting Guide
If the network connection can be pinged, use the telnet command to check the remote server
port.
On the Linux operating system, run the telnet command to check the port.
1.
2.
3.
Issue 02 (2012-07-04)
62
eSpace UC
Troubleshooting Guide
Using the tracert command to check the specific abnormal network connection
On the Linux operating system, run the traceroute x.x.x.x command to check the abnormal network
connection.
If the entire network connection cannot be pinged, use the tracert command to check the
specific abnormal connection.
1.
2.
3.
----End
Check the database address in the BMU configuration file hibernate.cfg.xml, as shown in
Figure 3-7. The file path is as follows:
Issue 02 (2012-07-04)
63
eSpace UC
Troubleshooting Guide
Windows: Installation
directory\eSpace_UC_Server\Server\BMU\webapps\ROOT\WEB-INF\classes\hibern
ate.cfg.xml
Linux: Installation
directory/eSpace_UC_Server/Server/BMU/webapps/ROOT/WEB-INF/classes/hibern
ate.cfg.xml
Check the database address in the eServer configuration file hibernate.cfg.xml. The file path
is as follows:
Windows: Installation
directory\eSpace_UC_Server\Server\eServer\cfg\hibernate.cfg.xml
Linux: Installation
directory/eSpace_UC_Server/Server/eServer/cfg/hibernate.cfg.xml
----End
Check the IP address and port number of the server on the eSpace login page, as shown in
Figure 3-8.
Issue 02 (2012-07-04)
64
eSpace UC
Troubleshooting Guide
Check the IP address and port number of the server in the server.ini file in the eSpace
installation path, for example, Installation directory\eSpace UC\Enterprise eSpace.
[ServerConfig]
Server=Server1
Server1IP=10.166.42.42
Server1Port=8011
Server2IP=0.0.0.0
Server2Port=8011
Compare the IMServer service ID on the GUI with that in the IMServer.cfg.xml file.
1.
2.
3.
Check whether the value of IMServer Service ID is the same as that of GUID in the
IMServer.cfg.xml file, as shown in Figure 3-9.
The IMServer.cfg.xml file path is as follows:
Issue 02 (2012-07-04)
Windows: Installation
directory\eSpace_UC\eSpace_UC_Server\Server\eServer\IMServer\service\cfg\IMSe
rver.cfg.xml
Linux: Installation
directory/eSpace_UC/eSpace_UC_Server/Server/eServer/IMServer/wrapper/cfg/IMS
erver.cfg.xml
65
eSpace UC
Troubleshooting Guide
Compare the default service address with the region service address.
1.
2.
3.
Click the icon corresponding to the IMServer service ID in the Set Service Address
column and check whether the value of Service address of the area is left blank or is
the same as that of Service Default Address shown in Figure 3-9.
----End
Check the SOAP address in the configuration file conf.xml of the eSpace Meeting server.
1.
2.
Use the Notepad to open the conf.xml file and check whether the following data is the
same as the IP address and HTTP port number of the BMU server, as shown in Figure
3-10.
----End
Issue 02 (2012-07-04)
66
eSpace UC
Troubleshooting Guide
1.
2.
3.
Check whether the SoftConsole address book function is enabled, as shown in Figure
3-11. If the function is disabled, enterprise address books on the SoftConsole cannot be
updated.
1.
If the SoftConsole address book function has been enabled, check the parameter settings
marked in red in Figure 3-11.
2.
Click Test.
If the message "Connection failure" is displayed, the preceding parameter settings are
incorrect or the OpenLDAP server is not started. Therefore, users cannot be registered on
the BMU.
----End
Issue 02 (2012-07-04)
67
eSpace UC
Troubleshooting Guide
Description
INVITE
100 Trying
180 Ringing
200 OK
Issue 02 (2012-07-04)
68
eSpace UC
Troubleshooting Guide
Message
Description
ACK
RTP
BYE
ACK
If an error occurs during a call, the signaling contains the corresponding error code, indicating
the error cause.
Table 3-5 Common error codes for the calling party
Error Code
Description
488
486
The called party is busy. Check whether the terminal of the called
party is configured with call transfer or whether the call is
forwarded to a phone in busy state.
403
480
400
500
Description
503
The CPU has reached the threshold and the system limits calls.
403
The trunk is not configured, or the called party does not have the
corresponding call permission.
The INVITE message sent by the calling party contains the information such as the local IP
address, peer IP address, port number, audio or video request, and codec information
supported by the local device, as shown in Figure 3-13.
Issue 02 (2012-07-04)
69
eSpace UC
Troubleshooting Guide
The response sent by the called party contains the information such as the called party IP
address, port number, codec after successful negotiation, which enables the calling and called
party to talk and transmit media streams with each other.
Procedure
Step 1 Use the packet capture tool to capture the call signaling for the fault. For details, see 2.5
Packet Capture.
Step 2 Compare the captured signaling with the signaling in Figure 3-12 to locate the fault.
Step 3 Locate the fault based on the error code.
Step 4 Rectify the fault based on the cause.
----End
Example
Intelligent terminal user A calls eSpace user B. User B picks up the phone after hearing the
ring. Then the call is released, and users A and B hear the busy tone.
1.
Issue 02 (2012-07-04)
70
eSpace UC
Troubleshooting Guide
When the call is established, the gateway sends a BYE message to the called party and
releases the call.
2.
View the 200 OK response sent by the called party. The negotiated codec information is
not found, as shown in Figure 3-15.
If the codec that is supported by both parties is obtained after negotiation, the available
codec information is displayed, for example, iLBC/8000.
3.
View the INVITE message sent by the calling party. The requested codec is DVI4, as
shown in Figure 3-16.
The called party, however, does not support the codec, causing the call failure.
Issue 02 (2012-07-04)
71
eSpace UC
Troubleshooting Guide
4.
Modify the codec supported on the intelligent terminal. The fault is rectified.
Procedure
Step 1 Use the Notepad to open the bmu.log file.
Step 2 Search for the Exception, error, and WARN fields.
The Exception, error, and WARN fields record exception information when a fault occurs,
such as the network exception, database connection exception, and database data writing
exception. Locate and rectify the fault based on these fields, as shown in Figure 3-17.
Issue 02 (2012-07-04)
72
eSpace UC
Troubleshooting Guide
If the bmu.log file does not contain useful information, you can open the bmu.log.* file that is
generated at the time when the fault occurs in view the fault information. In the file name, * is a
number, for example, bmu.log.1. The current log file is named bmu.log, and the files generated
before the current file are named bmu.log.*, whose maximum size is 10 MB.
----End
Procedure
Step 1 Use the Notepad to open the FTPLog_0.txt file.
Step 2 If the file contains the following information, the FTP port of the CDRServer has been
occupied and fails to share CDRs to the CDR management system.
Failed to create listen socket on port 21
----End
Follow-up Procedure
Stop the process that occupies port 21.
Issue 02 (2012-07-04)
73
eSpace UC
Troubleshooting Guide
Procedure
Step 1 Decompress the collected eSpace client information, for example, 2011-8-2
09_25_16.389.zip.
Step 2 Go to the log directory and double-click userlog.log.
The file contains information such as the account, IP address of the eSpace server, and error
logs, as shown in Figure 3-18 and Figure 3-19.
Search for ERROR in the file to query the fault information.
Figure 3-18 Account information
As shown in Figure 3-19, during eSpace login, the local host fails to connect to the eSpace
server whose IP address is 10.166.42.41. The possible cause is that the eSpace server address
is configured incorrectly, or the network is disconnected.
----End
Issue 02 (2012-07-04)
74
eSpace UC
Troubleshooting Guide
4 Login Faults
Login Faults
Background
4.2
4.3
Troubleshooting Examples
4.1 Background
The basic concepts are described as follows:
UC account
UC accounts are created on the BMU via account management. Users must use UC
accounts to log in to the BMU or eSpace Desktop.
UC number
Allocated SIP user numbers whose Device is set to UC on the Unified Gateway.
UC service
When registering a UC account on the BMU, BMU administrator can choose to enable
the UC service or not. Only UC accounts with enabled UC service can be used to log in
to the eSpace Desktop.
Issue 02 (2012-07-04)
75
eSpace UC
Troubleshooting Guide
4 Login Faults
2.
3.
4.
5.
Issue 02 (2012-07-04)
76
eSpace UC
Troubleshooting Guide
4 Login Faults
If the service has been enabled, ensure that port 8011 of the eServer is not blocked by the
firewall.
Possible Causes
The IP address of the database server is changed and therefore the database IP address
configured on the BMU is incorrect.
Procedure
Step 1 Check whether the IP address and port number of the BMU server are the same as those in the
URL.
1.
If yes, go to Step 2.
2.
1.
If yes, go to Step 6.
2.
If no, go to Step 4.
Issue 02 (2012-07-04)
77
eSpace UC
Troubleshooting Guide
4 Login Faults
Change the LDAP address when the OpenLDAP and the database are installed on the same
host. If they are installed on different hosts, do not change the address.
Change the address as follows when the UC version is earlier than Unified Gateway
V100R002C03SPC200.
1.
2.
3.
Change the value of Address Book IP Address to that viewed in Step 2, as shown in
Figure 4-4.
Issue 02 (2012-07-04)
78
eSpace UC
Troubleshooting Guide
4 Login Faults
4.
Click Save.
Step 6 Contact Huawei technical support by referring to 1.5 Huawei Technical Support if the fault
persists.
----End
The static IP address of the database server is recommended to ensure the IP address
stability.
Do not change the IP address of the database server randomly. If the database IP address
is changed, synchronously change the IP address parameter configured on other servers
using the database.
The message "Your account had logged in at other place." is displayed during system
running.
The message "Incorrect UC account or password, or this UC account does not have the
right to use this program." is displayed during login.
Possible Causes
Issue 02 (2012-07-04)
The possible causes for the message "Your account had logged in at other place." are as
follows:
The account has been used to log in to the eSpace on another computer.
The local IP address changes after the computer restarts from standby mode.
79
eSpace UC
Troubleshooting Guide
4 Login Faults
The possible causes for the message "Incorrect UC account or password, or this UC
account does not have the right to use this program." are as follows:
The possible causes for the message "Server login timed out." are as follows:
Procedure
Step 1 Exit the eSpace and re-log in to it.
Step 2 Enter the correct user name and password and re-log in to the eSpace.
Step 3 If the user name and password are correct, contact the administrator to check whether your
account is registered.
Issue 02 (2012-07-04)
80
eSpace UC
Troubleshooting Guide
4 Login Faults
Step 5 Select the correct network from the Server drop-down list box.
Step 6 Obtain the current eSpace IP address from the administrator or other users who can
successfully log in to the eSpace, and compare the correct IP address with that viewed in Step
4.
Step 7 Check whether the local host is properly connected to the eServer.
For the check method, see Pinging the network connection in 3.2 Network Information
Analysis.
If no, go to Step 8.
If yes, go to Step 9.
Issue 02 (2012-07-04)
81
eSpace UC
Troubleshooting Guide
Background
5.2
5.3
Troubleshooting Examples
5.1 Background
The basic UC functions involved in this document are as follows:
IM
Status display
Voice call
File transfer
Contact query
Issue 02 (2012-07-04)
When voice and video call faults occur, check the connection between the eSpace client
and the Unified Gateway. Analyze signaling to locate the faults. For details, see 3.4
Signaling Analysis.
82
eSpace UC
Troubleshooting Guide
When IM, status display, file transfer, contact query, and address book synchronization
faults occur, check the connection between the eSpace client and the eServer, including
the network communication, service startup, and service port availability.
Possible Causes
The network between the local host and the eServer is unstable.
Procedure
Step 1 Verify that the eSpace service process is started.
The verification methods are as follows:
On Windows 2008:
1.
2.
On Linux:
1.
2.
3.
Issue 02 (2012-07-04)
83
eSpace UC
Troubleshooting Guide
The following information indicates that the eSpace service is running. Go to Step 2.
eMonitor is running.
IMServer is running.
IMGServer is running.
The following information indicates that the eSpace service is not running. Run
the ./startAll.sh command to start the service.
eMonitor is not running.
IMServer is not running.
IMGServer is not running.
Step 2 Check whether the local host is properly connected to the eServer.
For the check method, see Pinging the network connection in 3.2 Network Information
Analysis.
If no, go to Step 3.
If yes, go to Step 4.
If yes, go to Step 5.
If no, go to Step 6.
On Windows 2008:
See Configuring Inbound Rules to add port 8011 to the enabled port list.
On Linux:
1.
2.
3.
4.
Issue 02 (2012-07-04)
84
eSpace UC
Troubleshooting Guide
5.
Click Add.
The Add New Allowing Rule page is displayed.
6.
Set parameters on the right based on the description on the left, as shown in Figure 5-3.
Set Destination Port to 8011 and Protocol to UDP.
Issue 02 (2012-07-04)
85
eSpace UC
Troubleshooting Guide
7.
Click Add.
8.
Click Next.
9.
Click Finish.
Step 6 Contact Huawei technical support by referring to 1.5 Huawei Technical Support if the fault
persists.
----End
Possible Causes
The current operating system account has no permission to run the eSpace.
Other operating system accounts but not the administrator may have no permission to
run the eSpace.
Procedure
Step 1 Reinstall the eSpace client.
Issue 02 (2012-07-04)
86
eSpace UC
Troubleshooting Guide
After the reinstallation, try to start the eSpace client. If the fault persists, go to Step 2.
Step 2 Verify that the current operating system account has the permission to run the eSpace.
1.
2.
3.
4.
Go to the upper-level folder of the eSpace.exe file, right-click the Enterprise eSpace
folder, and choose Properties.
The Enterprise eSpace Properties dialog box is displayed.
5.
6.
Select the account that experiences the fault in the Group or User names area.
7.
If Read & execute and Modify are not selected in the Allow column, go to Step 3.
If Read & execute and Modify are selected in the Allow column, go to Step 4.
Issue 02 (2012-07-04)
87
eSpace UC
Troubleshooting Guide
Step 4 Contact Huawei technical support by referring to 1.5 Huawei Technical Support if the fault
persists.
----End
When a called party answers a call, the call is automatically released and the calling
party hears the busy tone.
When a user tries to make a call on the eSpace, the eSpace does not respond.
The message "Sorry. The number you dial does not exist. Try later." is displayed.
Issue 02 (2012-07-04)
88
eSpace UC
Troubleshooting Guide
Possible Causes
The possible cause for automatic call release and busy tone play is as follows:
The called party uses the eSpace to answer the call on a remote desktop. For the
troubleshooting method, see Step 1.
The possible causes for message "Sorry. The number you dial does not exist. Try later."
or "Your call has been restricted." are as follows:
The called number does not meet the calling rules. For the troubleshooting method,
see Step 3.
The called number is not allocated on the Unified Gateway. Log in to the BMU as the
administrator and check whether the called number is deleted. If it is deleted,
re-allocated the number by referring to Configuring User Data on a Unified Gateway.
The network delay is too long, causing the result that the eSpace server cannot
receive call requests.
Procedure
Step 1 Check whether the user uses the eSpace on a remote desktop.
The eSpace used on a remote desktop does not support calls or call conferences.
If yes, use the eSpace on the local host to make calls or connect to call conferences.
If no, go to Step 7.
2.
3.
Check the calling rules and verify that the called number meets the calling rules, as
shown in Figure 5-5.
If Use an outgoing call prefix to dial out in the Calling Rules area is not selected, the
eSpace does not process the called numbers but directly sends them to the Unified
Gateway.
If Use an outgoing call prefix to dial out is selected, the eSpace prefixes the called
numbers of a specified length with the value of add prefix. Therefore, users do not need
to add the prefix when dialing an outer-office number.
Issue 02 (2012-07-04)
89
eSpace UC
Troubleshooting Guide
If no, go to Step 6.
If yes, locate the fault on the Unified Gateway. For details, see "Only One Party Can
Hear the Peer Voice" or "Calling Party and Called Party Cannot Hear Each Other" in
Fault Management > Troubleshooting > Basic Call Faults in the eSpace U1980
Unified Gateway Product Documentation.
Issue 02 (2012-07-04)
90
eSpace UC
Troubleshooting Guide
Possible Causes
The possible causes for noise and electromagnetic interference are as follows:
The built-in speaker and microphone of the portable computer or an outboard sound
box is used.
There are electromagnetic interference sources, for example, mobile phones, around
the host.
The possible causes for intermittent voice and voice jitter are as follows:
The network quality is poor, such as with high packet loss rate, long delay, and large
jitter. For details about quality levels of the IP bearer network, see 3.2 Network
Information Analysis.
Procedure
Step 1 Use a headset to make calls.
Step 2 Disable the microphone enhancing function. To disable the microphone enhancing function of
the Realtek audio card, proceed as follows:
1.
Double-click
Issue 02 (2012-07-04)
91
eSpace UC
Troubleshooting Guide
2.
3.
Issue 02 (2012-07-04)
92
eSpace UC
Troubleshooting Guide
4.
Choose Options > Advanced Controls in the Volume Control dialog box.
5.
6.
Issue 02 (2012-07-04)
93
eSpace UC
Troubleshooting Guide
Step 3 Move the wireless devices, for example, mobile phones, away from the earphone and
microphone.
Step 4 Check whether the local host is properly connected to the Unified Gateway.
For the check method, see Pinging the network connection in 3.2 Network Information
Analysis.
If no, go to Step 5.
If yes, go to Step 6.
Step 5 Set the codec mode occupying less bandwidth with higher priority.
1.
2.
3.
Click the icon next to the IM in the Set Plug-In Parameters column.
The Set Plug-In Parameters page is displayed.
4.
5.
Step 6 Use the eSpace audio check function to check the current input/output audio quality.
1.
Issue 02 (2012-07-04)
94
eSpace UC
Troubleshooting Guide
2.
3.
Click Test under Audio input, speak using the microphone, and check the volume
change, as shown in Figure 5-9.
4.
Click Test under Audio output and check whether the played voice is normal.
Step 7 Contact Huawei technical support by referring to 1.5 Huawei Technical Support if the fault
persists.
----End
Issue 02 (2012-07-04)
95
eSpace UC
Troubleshooting Guide
Possible Causes
The text or picture size exceeds the maximum. Figure 5-10 shows the prompt message
that is displayed.
The text to be sent contains sensitive words, which are displayed as * after it is sent.
Procedure
Step 1 Separate the text to be sent to multiple parts and send them.
Step 2 Replace the sensitive words in the text to be sent with other words.
Step 3 Contact Huawei technical support by referring to 1.5 Huawei Technical Support if the fault
persists.
----End
Issue 02 (2012-07-04)
96
eSpace UC
Troubleshooting Guide
6 License Faults
License Faults
6.2
Troubleshooting Examples
Possible Causes
The ESN in the license file is different from the device ESN.
The license is not a BMU license. For example, when the BMU and Unified Gateway
licenses are applied for together, the license file of the Unified Gateway is loaded by
mistake for the BMU.
Issue 02 (2012-07-04)
97
eSpace UC
Troubleshooting Guide
6 License Faults
Procedure
Step 1 Check the device ESN.
1.
2.
3.
Windows
1.
2.
Use
the
Notepad
to
open
license.dat
in
installation
directoryeSpace_UC/eSpace_UC_Server/Server/BMU/webapps/ROOT/WEB-INF/cl
asses/conf/, and view the ESN.
Linux
1.
2.
Run
the
cat
/root/eSpace_UC/eSpace_UC_Server/Server/BMU/webapps/ROOT/WEB-INF/class
es/conf/license.dat command to view the ESN.
Step 3 Check whether the ESN, as shown in Figure 6-1, in the license.dat file is the same as the ESN
obtained in Step 1.
If yes, go to Step 4.
Step 4 Check whether the license.dat file contains the information marked in red at the upper part in
Figure 6-1.
If no, the license file is not the BMU license file. Apply for the correct license.
Step 5 Contact Huawei technical support by referring to 1.5 Huawei Technical Support if the fault
persists.
----End
Issue 02 (2012-07-04)
98
eSpace UC
Troubleshooting Guide
6 License Faults
Possible Causes
The Unified Gateway ESN is different from the ESN in the license file, so that the
license fails the verification.
The configured device data, such as the number of users and number of trunks, is not
allowed by the license.
The shared directory on the TFTP server does not contain the License.dat file. Therefore,
the corresponding license file cannot be found when the license is loaded on the Unified
Gateway, and the license load fails.
The license to be loaded is a temporary license and has been loaded for 10 times.
The license file version does not match the host software version.
Procedure
Step 1 Verify that the Unified Gateway ESN is the same as the ESN in the license file.
1.
2.
Valid
License SN:
Equipment SN:
DEFAULT
2102351480109700001
3.
Use the Notepad to open the license.dat file and check whether the ESN in the file is the
same as the ESN obtained in the preceding step.
If yes, go to Step 2.
Step 2 Verify that the configured device data, such as the number of users and number of trunks, is
allowed by the license.
Run the show license command in the Config mode of the Unified Gateway.
The License Use Information displayed indicates the data that has been configured.
Check whether the data that has been configured is allowed by the license.
If yes, go to Step 3.
If no, apply for a license based on the data that has been configured.
Step 3 Check whether the TFTP service has been started on the TFTP server and whether the shared
directory contains the License.dat file.
Issue 02 (2012-07-04)
If yes, go to Step 4.
99
eSpace UC
Troubleshooting Guide
6 License Faults
If no, start the TFTP service software and set the directory where the License.dat file is
located as the shared directory.
Step 4 Verify that the TFTP server address is set correctly on the Unified Gateway.
1.
Run the show system information command in the Config mode of the Unified
Gateway.
2.
Check whether the value of Host IP Address is the IP address of the TFTP server.
If yes, go to Step 5.
If no, run the config system hostip x.x.x.x command to change the IP address to that of
the TFTP server.
Step 5 Check whether the license has been loaded for 10 times if the license is a temporary license.
Run the debug debug_pid os_pid_license cmd 2 command in the Debug mode of the
Unified Gateway to check whether the value of Total CB is equal to or greater than 10.
If no, go to Step 6.
Step 6 Contact Huawei technical support by referring to 1.5 Huawei Technical Support if the fault
persists.
----End
Issue 02 (2012-07-04)
100
eSpace UC
Troubleshooting Guide
Background
7.2
7.3
Troubleshooting Examples
7.1 Background
Users use the voice and eSapce Meeting services. The conference resources are provided by
the Unified Gateway, and the conference control function is provided by the eSapce Meeting
server.
2.
Check whether the license and eSpace Meeting server are normal.
If a scheduled conference or an instant conference fails to be held, the possible cause is
that the eSpace Meeting server is not started or the license has expired.
3.
Issue 02 (2012-07-04)
101
eSpace UC
Troubleshooting Guide
Possible Causes
The possible cause of the message indicating that the user has no permission to use the
service is as follows:
The eSpace account has no instant conference permission. For the troubleshooting
method, see Step 1.
The possible causes of the message "Failed to initialize multimedia conference." are as
follows:
The configuration file of the eSapce Meeting server is configured incorrectly. For the
troubleshooting method, see Step 2.
Time on the Unified Gateway is different from that on the BMU and that on the
eSapce Meeting server. For the troubleshooting method, see Step 3.
Procedure
Step 1 Grant the instant conference permission to the eSpace account.
1.
2.
3.
4.
5.
Click Save.
Step 2 Check the SOAP address in the configuration file conf.xml of the eSapce Meeting server.
1.
2.
Use the Notepad to open the conf.xml file and check whether the following data is the
same as the IP address and HTTP port number of the BMU server, as shown in Figure
7-1.
If yes, go to Step 3.
Issue 02 (2012-07-04)
102
eSpace UC
Troubleshooting Guide
Step 3 Check whether the time on the Unified Gateway is the same as that on the BMU and that on
the eSapce Meeting server.
If no, change the time on the Unified Gateway, BMU, and eSapce Meeting server to
ensure that the time difference is within one minute.
If yes, go to Step 4.
Step 4 Contact Huawei technical support by referring to 1.5 Huawei Technical Support if the fault
persists.
----End
Issue 02 (2012-07-04)
103
eSpace UC
Troubleshooting Guide
Background
8.2
8.3
Troubleshooting Examples
8.1 Background
The Console system consists of the following parts:
Console Server
Updates public information on SoftConsoles, such as login, logout, busy state, and idle
state of attendants; enables the administrator to set types.
Network
The Console system communicates with the Unified Gateway to provide basic service and
attendant service functions, and communicates with the BMU to provide service configuration
and call fee query functions. Figure 8-1 shows the connections between the Console Server,
SoftConsole, Unified Gateway, and BMU.
Issue 02 (2012-07-04)
104
eSpace UC
Troubleshooting Guide
An attendant can bind the SoftConsole to a hard terminal (see the dashed line box in Figure
8-1). After the binding relationship is set up, the attendant can use the hard terminal instead of
a headset to answer calls. The SoftConsole provides the call control functions such as calling
out, hooking on, rejecting, holding, and transferring calls.
Main Functions
In addition to the functions of an ordinary phone, the Console system provides the following
functions:
Controls services such as incoming call queuing, call transferring, break-in, and forced
release
Adjusts the incoming call queue and specifies important calls to be answered in
preference
Clicks users in phone books and recent call records to call them
Sets the night service, do-not-disturb (DND) service, wake-up service, and call right
Queries fees
Issue 02 (2012-07-04)
Check the connections between the SoftConsole, Console Server, and Unified
Gateway.
Check whether the attendant account authentication mode on the Unified Gateway is
correctly configured.
105
eSpace UC
Troubleshooting Guide
The agent, incoming call queuing, break-in, and forced release services of an attendant
are faulty.
Check whether the attendant account has been added to the console group.
Check whether the break-in and forced release services have been configured for the
attendant account.
Possible Causes
The multi-call permission has not been granted to the attendant.
Procedure
Step 1 Log in to the BMU as the administrator.
Step 2 Choose UC Account > UC Account List.
Step 3 Select the eSpace account, and click Service configuration.
Step 4 Check whether Multiple Call is selected in the Simple configuration area.
If yes, go to Step 5.
Step 5 Contact Huawei technical support by referring to 1.5 Huawei Technical Support if the fault
persists.
----End
Issue 02 (2012-07-04)
106
eSpace UC
Troubleshooting Guide
9 CDR Faults
CDR Faults
Background
9.2
9.3
Troubleshooting Examples
9.1 Background
The CDR system in eSpace UC solution contains the following components:
CDR pool
CDRs are stored in the CDR pool in the Unified Gateway.
CDRServer
The CDRServer periodically obtains CDR files from the CDR pool, parses them, stores
them on the local disk, and shares them in FTP mode.
BMU
The Business Management Unit (BMU) provides CDR statistics and query.
CDRAgent
Installed on the server of the third-party charging management system, the CDRAgent
obtains CDR files from the CDRServer and provides them for the third-party charging
management software.
Issue 02 (2012-07-04)
107
eSpace UC
Troubleshooting Guide
9 CDR Faults
The CDR obtaining function of the BMU and CDRAgent cannot be enabled at the same time.
Figure 9-1 CDR process
CDR
System
Pr
oc
es
s
Description
BMU
CDR
manage
ment
The CDRServer parses the original CDRs, stores them in a .bill file, and
shares the file in FTP mode to the BMU.
The BMU sends an FTP request to the CDRServer to download the CDR
file.
The BMU parses the CDR file and stores it in the database for users to
query or collect CDR information.
The CDRServer parses the original CDRs, stores them in a .bill file, and
shares the file in FTP mode to a third-party charging management system.
Third-pa
rty
charging
Issue 02 (2012-07-04)
108
eSpace UC
Troubleshooting Guide
9 CDR Faults
When the third-party charging management system fails to query the latest CDRs, check
whether the CDRs have been generated.
If no CDR has been generated, check whether the CDR generation function on the
Unified Gateway is enabled and whether the connection between the Unified Gateway
and the CDRServer is proper.
If the CDRs have been generated, check whether the CDRServer is successfully started
and whether the MML, Bill, and FTP processes on the CDRServer are running properly.
Check whether the CDR file path configured on the FTP server is correct.
Check whether the FTP server user name and password configured on the CDRAgent are
correct.
On the BMU, other services can be used properly, but CDRs cannot be queried.
Possible Causes
The CDR obtaining function is enabled on both the BMU and the CDRAgent.
Procedure
Step 1 Check whether the CDR generation function is enabled on the Unified Gateway.
3.
4.
Issue 02 (2012-07-04)
109
eSpace UC
Troubleshooting Guide
9 CDR Faults
5.
Run the config createbill switch on command to enable the CDR generation function.
6.
Step 2 Make several calls, and then check whether the corresponding CDRs are generated in the
CDR file path.
If yes, check whether the CDRs can be queried on the third-party charging management
system. If the CDRs fail to be queried, go to Step 3.
If no, check the connection between the CDRServer and the Unified Gateway by
referring to Network Information Analysis.
Step 3 Check whether the CDRServer is started on the host where the CDRServer is installed.
For details, see Verifying the CDRServer.
If yes, go to Step 4.
Step 4 Check whether the MML, Bill, and FTP processes on the CDRServer home page are in the
Running state.
If yes, go to Step 5.
Step 5 Check whether the CDR file path configured on the FTP server of the CDRServer is correct.
7.
Issue 02 (2012-07-04)
Select FTP on the CDRServer home page, and click Display, as shown in Figure 9-2.
110
eSpace UC
Troubleshooting Guide
9 CDR Faults
Issue 02 (2012-07-04)
111
eSpace UC
Troubleshooting Guide
9 CDR Faults
9.
Check whether the shared path configured is the CDR file path and whether Read and
Delete on the right are selected.
Step 6 Check whether the CDRAgent is installed and whether the CDR obtaining function is
enabled.
10. Disable the CDR obtaining function of the BMU, make some calls, and check whether
the CDRs in the CDR file path are obtained.
To disable the CDR obtaining function of the BMU, proceed as follows: Choose Functions > CDR
Settings on the BMU and set Interval to the time, for example, Every day00:00, that is several hours
later than the current time to make sure that the BMU does not obtain CDRs during commissioning.
After commissioning, change the value Interval back to the proper value.
If the CDR file does not exist, the CDRAgent has obtained the CDRs. In this case, go to
Step 7.
If the CDR file exists, the CDRAgent has not obtained the CDRs. In this case, go to Step
8.
If the BMU is used, uninstall the CDRAgent and enable the CDR obtaining function of
the BMU.
If the third-party charging management system is used, disable the CDR obtaining
function of the BMU.
Issue 02 (2012-07-04)
112
eSpace UC
Troubleshooting Guide
9 CDR Faults
Step 8 Contact Huawei technical support by referring to Huawei Technical Support if the fault
persists.
----End
Issue 02 (2012-07-04)
113