Problemas Fiberhome

AN5516-06
Optical Line Terminal Equipment
Troubleshooting Guide
Version: A
Code: MN000000815
FiberHome Telecommunication Technologies Co., Ltd.
May 2011
Thank you for choosing our products.
We appreciate your business. Your satisfaction is our
goal. We will provide you with comprehensive technical
support and after-sales service. Please contact your
local sales representative, service representative or
distributor for any help needed at the contact information
shown below.
Fiberhome Telecommunication Technologies Co., Ltd.
Address: No. 5 Dongxin Rd., Hongshan Dist., Wuhan, China

Zip code: 430073
Tel: +86 27 8769 1549
Fax: +86 27 8769 1755
Website: http://www.fiberhomegroup.com
Legal Notice
 
  
  
 
TM TM
are trademarks of FiberHome Telecommunication Technologies Co., Ltd.

(Hereinafter referred to as FiberHome)
All brand names and product names used in this document are used for
identification purposes only and are trademarks or registered trademarks
of their respective holders.
All rights reserved

No part of this document (including the electronic version) may be
reproduced or transmitted in any form or by any means without prior
written permission from FiberHome.
Information in this document is subject to change without notice.
Preface
Related Documentation
Document Description
AN5516-06 Optical Line Introduces the retrieval method, contents, releasing,
Terminal Equipment reading approach, and suggestion feedback method for
Documentation Guide the complete manual set for the AN5516-06.
Introduces the AN5516-06's network location, functional
features, hardware structure, FTTx application model,
AN5516-06 Optical Line
equipment configuration, network management system
Terminal Equipment Product
and technical specifications. It is the foundation of the
Description
complete manual set. The other manuals extend and
enrich the concepts introduced in the Product Description.
Introduces the key features supported by the AN5516-06,
including GPON / EPON access, GPON / EPON terminal
management, VLAN, broadcast, voice and safety; and
Terminal Equipment Feature
introduces these functions in details in terms of definition,
Description
characteristic, specification, principle description,
references and so on.
Introduces the appearance, structure, functions, technical
specifications, and usage method for the AN5516-06’s
Terminal Equipment Hardware
cabinet, PDP, subrack, cards, cables and wires, facilitating
Description
users’ mastery of the hardware features of the equipment.
Introduces the overall installation and verifying procedure
from unpacking inspection to power-on examination after
the equipment is delivered on site, and provides reference
Terminal Equipment Installation
information (e.g. safety principles and wiring scheme of a
Guide
variety of interfaces) to guide users to install the
equipment.
I
Document Description
Introduces the method for configuring the EPON services
supported by the equipment via ANM2000 Network
AN5516-06 Optical Line Management System, such as basic configuration, voice
Terminal Equipment EPON service configuration, data service configuration, multicast
Configuration Guide service configuration, and software upgrading
configuration, to guide users on start-up for various
services and software upgrading.
Introduces the shortcut menu for every card of the
AN5516-06 inside ANM2000 Network Management
System, including the function, parameter explanation,
Terminal Equipment GUI
precautions and configuration example of every command
Reference
in the shortcut menu of each card, to help users master
the operation of the AN5516-06 inside ANM2000.
Introduces the operation procedures of replacing the
AN5516-06 Optical Line AN5516-06’s components, including preparations,
Terminal Equipment Component precautions, early operations, operation process and
Replacement subsequent operations, so as to guide users with the
completion of component replacement on the hardware.
AN5516-06 Optical Line Introduces routine maintenance operations of the
Terminal Equipment Routine AN5516-06, including remote maintenance and on-site
Maintenance maintenance.
Introduces the AN5516-06’s alarm information and event
reference, including alarm / event names, alarm / event
Terminal Equipment Alarm and
levels, possible reasons, effects on the system, and
Event Reference
processing procedure.
Introduces the fault processing principles and methods of
fault diagnosis and locating for the AN5516-06. Also
discusses the typical fault cases of various services. If the
Terminal Equipment
trouble is too complicated to process, users can refer to
Troubleshooting Guide
FiberHome for technical support according to the
instructions in this document.
AN5516-06 Optical Line Introduces the AN5516-06 installation and cable
Terminal Equipment Quick connection and layout using diagrams to guide a quick
Installation Guide installation for users.
II
Version
Version Description
Initial version.
A
This manual is for the AN5516-06 equipment (V1.0).
Intended Readers
This manual is intended for the following readers:
 Planning and designing engineers
 Commissioning engineers
 Operation and maintenance engineers
To utilize this manual, these prerequisite skills are necessary:
 EPON technology
 GPON technology
 Multicast technology
 NGN voice technology
 Ethernet switch technology
 Computer network technology
III
Conventions
Terminology Conventions
Terminology Convention
AN5516-06 FiberHome AN5516-06 Optical Line Terminal Equipment
FiberHome e-Fim ANM2000 Broadband Access Network
ANM2000
Management System
EC4B 4×EPON-C Interface Card (type B)
EC8B 8×EPON-C Interface Card (type B)
GC4B 4×GPON-B Interface Card (type B)
GC8B 8×GPON-C Interface Card (type B)
C155A 1×STM-1 Optical Interface Card (CES Mode)
CE1B 32×E1 Optical Interface Card (CES mode) (type B)
PUBA Public Card (type A)
HSWA Core Switch Card (EPON) (card No.: 2.115.334)
HU1A 4×GE +1×10GE Optical Interface Uplink Card
HU2A 2×GE +2×10GE Optical Interface Uplink Card
GU6F 6×GE Optical Interface Uplink Card
CIO Common Interface Card
PWR Power Supply Card
FAN Fan Control Card
Symbol Conventions
Symbol Convention Description
Note Important features or operation guide.
Possible injury to persons or systems, or cause traffic

Caution
interruption or loss.
Warning May cause severe bodily injuries.
IV
Contents
Preface .................................................................................................................... I
Related Documentation...................................................................... I
Version……. ..................................................................................... III
Intended Readers ............................................................................ III
Conventions ..................................................................................... IV
1 General ........................................................................................................ 1-1
1.1 Requirement for Maintenance Engineers ....................................... 1-2

1.1.1 Theoretical Knowledge .................................................... 1-2
1.1.2 Equipment Composition and Network.............................. 1-2
1.1.3 Equipment Operation ....................................................... 1-2
1.1.4 Tool.................................................................................. 1-3
1.1.5 Instrument ........................................................................ 1-3
1.2 Principle of Troubleshooting ........................................................... 1-3
1.3 General Flow of Troubleshooting ................................................... 1-4
1.3.1 Collecting and Recording Faults ...................................... 1-5
1.3.2 Excluding External Factors .............................................. 1-6
1.3.3 Troubleshooting and Isolation .......................................... 1-7
1.3.4 Contacting FiberHome for Technical Support .................. 1-7
1.3.5 Observing Equipment Operation Status ........................... 1-8
1.4 Routine Methods of Fault Analysis and Isolation............................ 1-9
1.4.1 General ............................................................................ 1-9
1.4.2 Instrument Test .............................................................. 1-10
1.4.3 Status Indicator Analysis ................................................ 1-11
1.4.4 Alarm Analysis ............................................................... 1-11
1.4.5 Log Inspection ............................................................... 1-12
1.4.6 Performance Analysis .................................................... 1-12
1.4.7 Loopback Test................................................................ 1-13
1.4.8 Comparison / Substitution .............................................. 1-13
1.4.9 Configuration Data Analysis ........................................... 1-14
1.4.10 Signal Tracing ................................................................ 1-14
1.5 How to Obtain Technical Support ................................................. 1-15
2 Troubleshooting of System Common Faults................................................. 2-1
2.1 Card Fault ...................................................................................... 2-2

2.2 All Indicators Are Extinguished after Power up .............................. 2-3
2.3 LOS Indicator of ONU Is Illuminated .............................................. 2-4
2.4 REG Indicator of ONU Is Abnormal ................................................ 2-6
2.5 ONU Network Management Connection Failure ............................ 2-8
2.6 Network Interface Indicator Is Extinguished ................................... 2-9
2.7 Equipment Management IP Address Ping Timeout ...................... 2-10
2.8 Abnormal Link Between Equipment and Switch........................... 2-13
2.9 Link to Network Management Database Failed ........................... 2-15
3 Troubleshooting of Data Service Faults........................................................ 3-1
3.1 Background Knowledge ................................................................. 3-2

3.2 Troubleshooting Flow ..................................................................... 3-3
3.2.1 Troubleshooting Data Service Interruption of All Users.... 3-4
3.2.2 Troubleshooting Data Service Interruption of an Individual
User ................................................................................. 3-8
3.3 Troubleshooting of Common Faults ............................................. 3-11
3.3.1 Windows Operating System Prompts a 678 Error ......... 3-11
3.3.2 Windows Operating System Prompts 691 Error ............ 3-12
4 Troubleshooting of Voice Service Faults ...................................................... 4-1

4.2.1 Troubleshooting Voice Service of All Users ..................... 4-4
4.2.2 Troubleshooting Voice Service of One User .................... 4-7
4.3 Troubleshooting Common Faults ................................................. 4-11
4.3.1 Busy Tone or No Tone after Picking Up the Telephone .. 4-11
4.3.2 Dial Tone Cannot Be Cut Off After Dialing ..................... 4-12
4.3.3 Busy Tone after Calling Dial ........................................... 4-13
4.3.4 A One-way Call Fault when User Calls .......................... 4-14
4.3.5 Intra-system Users Disconnected .................................. 4-15
4.3.6 The Dialed Number Does Not Exist ............................... 4-16
4.3.7 No Dial Tone When Picking Up Telephone .................... 4-16
4.3.8 Excessive Noise During Calls ........................................ 4-18
4.3.9 Echo in Calls .................................................................. 4-20
4.3.10 Abnormal Interruption in Long-Term Calling .................. 4-21
4.3.11 Abnormal Ring Back Tone ............................................. 4-22
4.3.12 Abnormal Three-Party Service....................................... 4-23
4.3.13 Fax Service Fault ........................................................... 4-24
5 Troubleshooting Multicast Service Faults ..................................................... 5-1

5.2.1 Checking STB Status ....................................................... 5-4
5.2.2 Checking VLAN Configuration ......................................... 5-4
5.2.3 Checking Configuration of Multicast Proxy IP .................. 5-6
5.2.4 Checking Multicast Template and Port Configuration ...... 5-7
5.2.5 Checking Bandwidth Configuration .................................. 5-9
5.2.6 Checking ONU Service Configuration............................ 5-10
5.3 Troubleshooting Common Faults ................................................. 5-13
5.3.1 Failure to Go Online....................................................... 5-13
5.3.2 Failure to Watch a Multicast Program ............................ 5-15
5.3.3 Failure to Watch a Program Even After Successfully
Accessing the Program.................................................. 5-16
6 Fault Cases .................................................................................................. 6-1
6.1 System Fault Case ......................................................................... 6-2

6.1.1 A “651”, “619”, or “31” Fault Is Reported During ONU
Connection ...................................................................... 6-2
6.1.2 Endpoint Frequent Restart Fault ...................................... 6-3
6.1.3 Working Mode Inconsistency Between Uplink Port of
Equipment and Upper Layer Equipment Causes Physical
Connection Fault.............................................................. 6-4
6.1.4 EPON Broadband Users Over a Large Area of An OLT Have
Faults ............................................................................... 6-5
6.2 Voice Service Fault Case ............................................................... 6-6
6.2.1 Gateway Address Error Causes Fault of Voice Service ... 6-6
6.2.2 Voice Encoding Inconsistency Causes Abnormal Operation
When User Is Called ........................................................ 6-6
6.2.3 DNS Configuration Error Causes Connection Failure of
External SIP Terminal Voice Service ................................ 6-8
6.2.4 Multiple Media Gateways Cause One-way Call
Phenomenon ................................................................... 6-9
6.2.5 Intelligent Telephone Has Faults in Long Distance Call . 6-12
6.2.6 Noises Occur During Calls ............................................. 6-13
6.2.7 Multiple Users of an AN5006-07 ONU Cannot Make Calls
Simultaneously .............................................................. 6-15
6.2.8 Digitmap Configuration Error Causes Toll Call Failure ... 6-17
6.2.9 Users of AN5006-20 ONU Cannot Hear Opposite Party 6-18
6.2.10 AN5006-04 ONU Displays Wrong Incoming Call Time .. 6-20
6.2.11 Incorrect DSP Profile Parameter Configuration Causes Card
Swiping Failure on POS Machine .................................. 6-23
6.3 Fax Service Fault Case ................................................................ 6-24
6.3.1 Dial Mode Setting Error Causes Fax Service Fault........ 6-24
6.3.2 Incorrect Uplink Port Mode Configuration Causes
Connection Failure in Fax Service ................................. 6-25
6.4 Other Service Case ...................................................................... 6-26
6.4.1 ONU Network Access Fails to Be Reported ................... 6-26
6.4.2 Configuration of Received Commands Buffer Area on
Gathering Server Has Faults ......................................... 6-27
Appendix A Signaling Tracing Instruction ..........................................................A-1
A.1 Overview ........................................................................................A-1

A.1.1 Definition ..........................................................................A-1
A.1.2 Applicable Situation .........................................................A-1
A.1.3 Operation Flow ................................................................A-2
A.1.4 Enabling / Disabling Signal Tracing .................................A-3
A.1.5 Signal Trace Window .......................................................A-5
A.2 H.248 Signaling Flow Analysis .......................................................A-7
A.2.1 MG Registers to MGC .....................................................A-7
A.2.2 MG Logs out Actively .......................................................A-9
A.2.3 Take Endpoint out of Service .........................................A-10
A.2.4 Restore Endpoint to Service .......................................... A-11
A.2.5 Establish a Normal Call .................................................A-12
A.2.6 NOC First Party Release ...............................................A-21
A.3 SIP Signaling Flow Analysis .........................................................A-27
A.3.1 SIP User Terminal Registration ......................................A-27
A.3.2 SIP User Terminal Logout ..............................................A-31
A.3.3 Establish a Normal Call .................................................A-33
A.3.4 Perform a Normal Call Release .....................................A-40
A.3.5 Call Released when the Called Party Busy ...................A-43
Appendix B Abbreviations.................................................................................B-1
Figures
Figure 1-1 General Flow of Troubleshooting of the AN5516-06 ...................... 1-4

Figure 1-2 The Technical Support Flow ........................................................... 1-8
Figure 2 -1 The Attributes Configuration of the Uplink Interface ..................... 2-14
Figure 2-2 Link Failed.................................................................................... 2-15
Figure 2-3 The SQL Editor ............................................................................ 2-16
Figure 2-4 The SQL Editor Server / Database Dropdown Menu ................... 2-17
Figure 2-5 The ol_anmxx Window ................................................................. 2-18
Figure 3-1 Typical Network of the AN5516-06 Data Service ........................... 3-2
Figure 3-2 Troubleshooting Flow for Data Service Interruption ....................... 3-3
Figure 3-3 Viewing / modifying the Uplink Port Properties .............................. 3-5
Figure 3-4 The Screen for checking the ONU registration status .................... 3-6
Figure 3-5 OLT MAC Address List ................................................................... 3-9
Figure 3-6 OLT MAC Address List ................................................................. 3-10
Figure 4-1 The AN5516-06 Voice Service Network ......................................... 4-2
Figure 4-2 Troubleshooting Flow of Voice Service Interruption ....................... 4-3
Figure 4-3 Configure the Local End Service VLAN Data ................................. 4-5
Figure 4-4 Configuring the NGN Uplink Interface ............................................ 4-6
Figure 4-5 NGN Uplink User’s Data Configuration (Applying H.248 Protocol) 4-9
Figure 4-6 NGN Uplink User’s Data Configuration (Applying SIP Protocol) .... 4-9
Figure 4-7 Configure Softswitch Intercommunication Template (RTP
Resource)…. ................................................................................ 4-10
Figure 4-8 Configure Softswitch Intercommunication Template (DigitMap
Timer)…. ...................................................................................... 4-10
Figure 4-9 The NGN Heartbeat Parameters .................................................. 4-12
Figure 4-10 Display the Status of MGC Registration Server ........................... 4-17
Figure 4-11 Display the NGN User’s Port Status............................................. 4-18
Figure 4-12 Turn on the Silence Suppression ................................................. 4-19
Figure 4-13 Activating the Echo Suppression ................................................. 4-21
Figure 4-14 The Port Service Configuration (Fax Mode) ................................. 4-25
Figure 4-15 Packet Interval ............................................................................. 4-26
Figure 5-1 Multicast Service Network .............................................................. 5-2
Figure 5-2 Troubleshooting Flow of the Multicast Fault ................................... 5-3
Figure 5-3 The Local End Service VLAN......................................................... 5-5
Figure 5-4 The Multicast VLAN ....................................................................... 5-5
Figure 5-5 Multicast Proxy IP address ............................................................. 5-6
Figure 5-6 The Multicast Template Configuration ............................................ 5-7
Figure 5-7 The Group Parameters Configuration ............................................ 5-8
Figure 5-8 The Port Parameters Configuration ............................................... 5-8
Figure 5-9 Configuration of Total Bandwidth of the Uplink Interface ................ 5-9
Figure 5-10 ONU Multicast Service Configuration (Taking FTTH Type as an
Example) ...................................................................................... 5-11
Figure 5-11 ONU Multicast Service Configuration (Taking FTTB Type as an
Example) ...................................................................................... 5-12
Figure 6-1 The ONU Voice Encoding and Decoding Configuration ................. 6-7
Figure 6-2 Analyzing the faulty packet .......................................................... 6-10
Figure 6-3 The results of Ping commands ..................................................... 6-11
Figure 6-4 Configuring the SilenceSp item ................................................... 6-14
Figure 6-5 Configuring the caller ID display mode ........................................ 6-21
Tables
Table 1-1 Relationship of the AN5516-06 Services and Main Peripheral

Equipment ...................................................................................... 1-6
Table 1-2 The Process and Routing Methods of Fault Analysis and Isolation 1-9
Table 1-3 Instrument Operating Instructions ................................................ 1-10
Table 3-1 Related Alarms of the HU1A Card .................................................. 3-5
Table 4-1 Main Parameters and Influences ................................................... 4-8
Table 5-1 The Multicast Service Modes using the AN5516-06 ....................... 5-2
1 General
This chapter introduces the requirements for maintenance engineers, principles of

troubleshooting, flow of troubleshooting, routine methods of fault analysis and
technical support available to the maintenance staff using the AN5516-06.
This chapter mainly contains the following items:
Requirement for Maintenance Engineers
Principle of Troubleshooting
General Flow of Troubleshooting
Routine Methods of Fault Analysis and Isolation
How to Obtain Technical Support
Version: A 1-1
AN5516-06 Optical Line Terminal Equipment Troubleshooting Guide
1.1 Requirement for Maintenance Engineers
1.1.1 Theoretical Knowledge
Maintenance engineers should be familiar with the following theoretical knowledge:
 Ethernet protocols;
 Related protocols of multicast service;
 Theory of voice service;
 Fundamental principles of EPON / GPON technologies;
 MGCP, H.248 and SIP protocols;
 PBX technologies and softswitching technologies.
1.1.2 Equipment Composition and Network
Maintenance engineers should understand the system composition, service

network and data status of the equipment, specifically as follows:
 Hardware configuration of the AN5516-06;
 Functions of each card and interface of the AN5516-06;
 Network of the AN5516-06;
 Physical connection of internal and external cables of the AN5516-06;
 Network data planning and configuration of the AN5516-06.
1.1.3 Equipment Operation
Maintenance engineers should be knowledgeable of the following basic operations:
 Basic operation of equipment such as part replacement, cleaning etc.;
 Daily operation of the ANM2000 network management system;
 Basic operation of a computer.
1-2 Version A
1 General
1.1.4 Tool
Maintenance engineers should know how to use the following tools to work on the
equipment hardware when troubleshooting:
Screwdrivers, strippers, diagonal pliers, network cable pliers and optical

attenuators.
1.1.5 Instrument
Maintenance engineers should know how to use the following instruments to check
each parameter of the equipment during troubleshooting:
Multimeters, optical power meters, error code analyzers and network cable testers.
1.2 Principle of Troubleshooting

Key principles to comply with in troubleshooting are as follows:
 Accurately record the fault symptom and collect related information.
Collect fault information; ascertain possible isolation and type of the fault
through observing alarms, performance monitoring data, signal tracing and
logs in the network management system.
 Consult involved site personnel in the fault isolation to collect helpful

information for discovering the reason for the fault.
For example: has someone modified the data, replaced a part, perform the
wrong operation or has there been a power interruption or lightning strike.
 In the event of a severe and urgent fault, contact FiberHome or its local office
for technical support while collecting fault symptoms.
Details on how to contact support staff are given in Section 1.5 How to Obtain
Technical Support.
 Strictly follow related rules and flow for hardware operation and data collection
in troubleshooting to avoid exacerbating the faults.
Version A 1-3
1.3 General Flow of Troubleshooting

General flow of troubleshooting of the AN5516-06 is shown in Figure 1-1.
Figure 1-1 General Flow of Troubleshooting of the AN5516-06
The above flow describes the isolation and troubleshooting of non-urgent faults.
For severe and urgent faults, contact Customer Service Department of FiberHome
or its local office promptly for technical support. Instruction on how to contact the
Customer Service Department is described in Section 1.5 How to Obtain Technical
Support.
1-4 Version A
1 General
1.3.1 Collecting and Recording Faults
Collecting and recording fault information is a prerequisite of fault analysis and

troubleshooting. Maintenance personnel should collect and record fault information
promptly when a fault occurs.
Background information
Main sources of fault information:
 Users’ fault complaints;
 Fault discovered in routine maintenance;
 Alarms on the network management system.
Process
The process for collecting and recording related fault information is as follows:
1. Record the time the fault occurred.
2. Record the detailed fault symptoms.
3. Record any ongoing operations when the fault occurred.
4. Record the status of all equipment indicators, alarms on the network

management system, logs and performance monitoring statistics.
5. Record the network management system and software and hardware versions
of the cards of the faulty equipment.
Version A 1-5
1.3.2 Excluding External Factors
After collecting and recording the detailed fault information, the peripheral
equipment of the AN5516-06 should be inspected to ensure the fault is not arising
from the peripheral equipment. If it is caused by the peripheral equipment, notify
related maintenance personnel for troubleshooting.
Background knowledge
When the equipment fails, it may be caused by peripheral equipment.
 A fault in the softswitch platform may cause a loss of voice services;
 A fault of the BRAS may cause a fault of data services;
 A fault of a peripheral router or switch may cause an interruption of all

services.
The relationships between the AN5516-06 services and main peripheral equipment
are shown in Table 1-1.
Table 1-1 Relationship of the AN5516-06 Services and Main Peripheral Equipment
Service Type Main Peripheral Equipment

IPTV service IPTV server, router, Ethernet switch, ONU, STB, TV
VoIP service Softswitch platform, ONU, telephone, router, Ethernet switch
Data service BRAS, router, Ethernet switch, ONU, HG, PC
SDH equipment, E1 equipment (such as base station, E1 Private Line
TDM service
Service), clock source device, ONU
CATV service CATV signal source, multiplexer, TV
Process
1. Use routine methods for fault analysis and isolation to determine whether the
fault is caused by peripheral equipment or not. Routine methods for fault
analysis and isolation are shown in Section 1.4 Routine Methods of Fault
Analysis and Isolation.
2. Determine the fault isolation by querying the operational status of the

peripheral equipment.
1-6 Version A
1 General
1.3.3 Troubleshooting and Isolation
Fault isolation and troubleshooting methods focus on analyzing and locating the
cause of the fault and then troubleshooting to determine a solution.
The following principles should be followed in course of fault isolation:
 Inspect whether the external cables of the equipment are securely connected
or not, then inspect indicator LEDs;
 Check the general operational status of the equipment, and then query the
status of each card using the network management system.
Process
1. Ascertain the fault type through related information.
2. Determine if the fault is a service fault of some users or of all users though the
fault symptoms, indicator LED status analysis and alarm analysis.
3. Apply routine methods of fault analysis and isolation to discover and analyze
the reason for the fault. Details of routine methods for fault analysis and
isolation are shown in Section 1.4 Routine Methods of Fault Analysis and
Isolation.
1.3.4 Contacting FiberHome for Technical Support
If maintenance personnel are unable to eliminate the fault after collecting fault
information, isolating the fault and troubleshooting, contact the Customer Service
Department of FiberHome or the local office promptly for technical support. Details
on how to contact support staff are given in Section 1.5 How to Obtain Technical
Support.
Technical support flow is shown in Figure 1-2:
Version A 1-7
Telephone service
Dial the service telephone Contact the Customer Service Technical engineer provides
number to seek for Center of FiberHome or the local remote services
technical support office
Site
service
Technical engineer
troubleshoots the fault on site
Figure 1-2 The Technical Support Flow
1.3.5 Observing Equipment Operation Status
After eliminating the fault, observe equipment operation for a period to confirm
whether the equipment has recovered.
Process
1. Observe whether equipment alarm is eliminated or not. Refer to the
AN5516-06 Optical Line Terminal Alarm and Event Reference for alarm
inquiry.
2. Observe whether indicator LEDs are normal or not. Refer to the AN5516-06
Optical Line Terminal Equipment Hardware Description for details.
3. Check whether the hardware status information of the card is normal through
the Getting Information command of the network management system.
4. Inspect the performance monitoring statistics of each system and check if

each statistic parameter is within the normal range using the network
management system.
1-8 Version A
1 General
1.4 Routine Methods of Fault Analysis and

Isolation
1.4.1 General
The routine methods of fault analysis and isolation include: instrument test,
indicator LED status analysis, alarm analysis, signal tracing, log inspection,
performance analysis, loopback tests, comparison/substitution, configuration data
analysis and status call-back.
The process and routing methods of fault analysis and isolation are shown in Table
1-2.
Table 1-2 The Process and Routing Methods of Fault Analysis and Isolation
Fault Analysis and Isolation

Routine Methods Backup Methods
Process
Instrument test
Eliminate equipment peripheral Status indicator analysis
Alarm analysis
factors Comparison/Substitution
Loopback test
Alarm analysis Performance analysis,
Ascertain fault type Status indicator analysis configuration data
Status call-back analysis
Alarm analysis
Status indicator analysis
Isolation and troubleshooting
Determine the fault scope Status call-back Performance analysis

Configuration data analysis
Comparison/Substitution
Alarm analysis
Status call-back
Discover the detailed Configuration data analysis Performance analysis,
reason for a fault Comparison/Substitution log inspection
Loopback test
Signal tracing (voice service)
Instrument test (system fault)
Version A 1-9
Fault Analysis and Isolation

Routine Methods Backup Methods
Process
Alarm analysis
Operation observation —
Status call-back
Performance analysis
1.4.2 Instrument Test
Purpose
Instrument tests require using related instruments to test equipment parameters

and ascertain fault causes through comparison with normal values.
Instruments in common use are shown in Table 1-3.
Table 1-3 Instrument Operating Instructions
Item Purpose
To measure voltage and current of the power
Multimeter
system.
Optical power meter To measure optical power of PON interface.
Network cable tester To measure the communication of network cables.
Error code analyzer To test the transmission link.
1-10 Version A
1 General
1.4.3 Status Indicator Analysis
Definition
The AN5516-06 has operation indicator LEDs and status indicator LEDs. These
indicator LEDs directly reflect the operating status of each card, link and optical
path as well as their active and standby status. These indicators are important for
fault analysis and isolation.
Purpose
An indicator analysis is used to quickly approximate the fault isolation or cause
before the next treatment step. Through observing the status of the indicator LEDs
on the cabinet, subracks and cards, maintenance staff can initially ascertain and
isolate a fault. Information provided by indicators is often insufficient, so it is often
used together with alarm analysis.
Related information
Refer to the AN5516-06 Optical Line Terminal Equipment Hardware Description for
details about indicator LEDs.
1.4.4 Alarm Analysis
Definition
Alarms are informative messages of different faults and events during system
operation. When the equipment fails, the system will report one or more alarm
messages to the network management system. Users can retrieve the current
alarms, historical alarms and the time an alarm occurred using the ANM2000
network management system.
Purpose
Alarm information analysis is one of the essential operations in fault analysis and
isolation.
Related information
Refer to the AN5516-06 Optical Line Terminal Alarm and Event Reference for
details concerning alarm messages.
Version A 1-11
1.4.5 Log Inspection
Definition
The network management system of the AN5516-06 supports inspection of

command logs and registration logs. In the command log, users can view the
configuration data, the configuration time and command execution results; in the
registration log, users can view the registration name, IP address, registration time
and whether a registration was successful or not.
Purpose
A fault may be caused by mistakes made by maintenance personnel in course of

data planning and configuration. In order to localize this type of fault quickly,
maintenance personnel must view the system log and analyze historical
configuration data.
1.4.6 Performance Analysis
Definition
Performance analysis means to analyze the equipment data and specifications

collected in the performance statistics, so as to isolate the fault. With the
performance statistics, users can monitor the equipment operation process, and
collect the essential parameters in the equipment operation.
Purpose
Through data acquisition and analysis, maintenance personnel can be supplied

with ample and complete operational data. Performance analysis provides a
powerful means of diagnosing faults.
1-12 Version A
1 General
1.4.7 Loopback Test
Definition
Loopback tests use hardware or software methods to verify the operational status
of the equipment or a transmission channel by transmitting and receiving a known
signal or data pattern.
Purpose
The purpose of a loopback test is to confirm the operational status of the

associated hardware or equipment and of the software parameters settings by
judging whether the channel is performing normally during the test. The loopback
test is one of the most common ways for determining transmission problems and
relay parameter settings.
1.4.8 Comparison / Substitution
Purpose
 Comparison involves the comparative analysis of faulty parts or symptoms

with the normal parts or symptoms, to discover differences, and then localize
the problem. The comparison method is usually applicable for a simple fault.
 Substitution involves replacing a possibly faulty part with a normal part (such
as a card, an optical fiber), and then comparing the equipment operation
before and after the substitution, so as to determine fault scope or isolation.
Refer to the AN5516-06 Optical Line Terminal Equipment Component
Replacement for details.
Version A 1-13
1.4.9 Configuration Data Analysis
Definition
Configuration data analysis entails analyzing the fault cause by viewing and
analyzing current data configuration.
Purpose
When the fault has been localized to the system analyzing the current configuration
data of the equipment can lead to identification of a configuration error.
1.4.10 Signal Tracing
Definition
Signal tracing can track and save on a real time basis the voice service signaling
interaction flow between the equipment and softswitch platform.
Purpose
Maintenance personnel often can directly know the cause of a call failure by
reviewing the signal trace, and thus provide valuable suggestions for subsequent
analysis and troubleshooting.
For details, please see Appendix A.
1-14 Version A
1 General
1.5 How to Obtain Technical Support

Maintenance Engineers can seek technical support from FiberHome or FiberHome
local offices when they are unable to correct a fault in a timely manner at the
contact shown below.
Contact:
 Tel: +86 27 8769 1549
 Fax: +86 27 8769 1755
 Website: http://www.fiberhomegroup.com
 For contact information for the various FiberHome local offices, visit the
website.
Version A 1-15
2 Troubleshooting of System Common
Faults
This chapter introduces system fault troubleshooting of the AN5516-06. The

system faults include equipment hardware faults, system faults and network
management faults etc.
This chapter covers the following items:
Card Fault
All Indicators Are Extinguished after Power up
LOS Indicator of ONU Is Illuminated
REG Indicator of ONU Is Abnormal
ONU Network Management Connection Failure
Network Interface Indicator Is Extinguished
Equipment Management IP Address Ping Timeout
Abnormal Link Between Equipment and Switch
Link to Network Management Database Failed
Version A 2-1
2.1 Card Fault

Symptom
Symptoms of a card fault are mainly divided into the following types:
 The working indicator LED of a card is extinguished and the alarm indicator is
illuminated;
 Indicator remains extinguished after turn-up of the card;
 Services carried by the card are interrupted;
 The active-standby communication between the card and its peer is

interrupted. The services are normal but configuration commands cannot be
issued;
 The card program cannot be started in a normal way.
Fault analysis
Main causes for a card fault may include the following:
 Component or subcard damage;
 Arbitrary removal and/or insertion of the card;
 Serial port connected on the card.
Troubleshooting procedure
1. Restart the card
Check whether there is serial port connection on the card or not, remove it if it
exists. Remove and insert the card to restart it. If the fault does not disappear
after several seconds, go to Step 2.
2. Replace the card
 If the equipment has a standby card, replace the card, refer to the
AN5516-06 Optical Line Terminal Equipment Component Replacement
for details.
 If it has no standby card, contact FiberHome for support.
2-2 Version A
2 Troubleshooting of System Common Faults
2.2 All Indicators Are Extinguished after Power

up
Symptom
All indicators on the equipment are extinguished after power up.
Fault analysis
Possible causes are shown as follows:
 Fault of the power system.
 Incorrect connection of the power cables.
1. Check the power system in the equipment room, contact related maintenance
personnel for repair if it has failed;
2. Turn off the first cabinet of each row and the PDP. Check that the power
connections from the first cabinet of each row to the PDP and from the PDP to
the subracks are corrected; check that the cable connections are secure. If not,
reconnect the power cable. Refer to the AN5516-06 Optical Line Terminal
Equipment Installation Guide for details.
Version A 2-3
2.3 LOS Indicator of ONU Is Illuminated

Symptom
The LOS indicator on the ONU is illuminated.
Fault analysis
The LOS indicator on the ONU being illuminated indicates that the ONU is not
receiving the optical signal or the received optical power is too low. The possible
causes are shown below:
 Incorrect connection of the optical fibers;
 The received optical power is too low;
 A fault of the AN5516-06, for example, a fault of the EPON interface card.
 A fault of the ONU equipment.
Caution:
The laser beam at the optical interface and fiber connector can injure
your eyes! Never look directly into the optical interface and fiber
connector.
1. Check whether the ONU equipment operates normally and has abnormal
alarms. If the ONU equipment has faults, please replace it. Refer to
AN5516-06 Optical Line Terminal Equipment Component Replacement for
operation procedures.
Go to Step 2 if the fault is not resolved.
2. Check the connection of the optical fibers.
 If the fiber jumper is not connected correctly, remove it and reinsert it;
 If the fiber is broken, replace with a good fiber jumper.
2-4 Version A
3. Connect the fiber to the optical power meter and the ONU respectively and
measure the received optical power at the ONU. In general, LOS being
illuminated indicates the optical power is too low (standard limit of received
optical power of ONU: -24dBm to -8dBm). The solution for low optical power is
shown below:
 If the fiber profile is dirty, clean with non-woven lens tissue dampened with
a small amount of alcohol, and then reinsert the fiber into PON port.
 If the fiber profile is not smooth, replace it with a good fiber jumper.
 If the bend radius of the fiber is too small, increase the bend radius.
 If there are too many optical splitter cascades, reduce the number.
4. Check whether the interface card is present and whether it has abnormal
alarms or not. If the interface card fails, replace it and refer to the AN5516-06
Optical Line Terminal Equipment Component Replacement for details.
5. Contact FiberHome if the above steps do not work.
Version A 2-5
2.4 REG Indicator of ONU Is Abnormal

Symptom
REG indicator on the ONU blinks or goes out.
Fault analysis
If the REG indicator on the ONU blinks or goes out, it indicates registration of the
ONU with the OLT has failed. Possible causes are shown below:
 The ONU uplink fiber is loose or broken.
 The optical power is abnormal.
Note:
The optical link of the optical access system is very sensitive. Even a
slightly dirty optical connector or non-aligned adapter will cause
excessive loss.
 The AN5516-06 is failed, such as EPON interface card.
 If the REG indicator of the ONU is abnormal and LOS indicator is illuminated,
go to Steps 1 to 5;
 If the REG indicator of the ONU is abnormal and LOS indicator is extinguished,
go to Steps 3 to 5.
Caution:
connector.
1. Check the connection of the optical fiber.
 If the fiber jumper is not connected correctly, remove it and reinsert it;
2-6 Version A
 If the fiber is broken, replace with a good fiber jumper.
2. Check the fiber profile of the fiber jumper connector.
 If the fiber profile is dirty, clean with non-woven lens tissue dampened with
a small amount of alcohol, and then reinsert the fiber into PON port.
 If the fiber profile is not smooth, replace it with a good fiber jumper.
3. Connect the fiber to the optical power meter and the ONU respectively and
measure the received optical power of ONU to determine whether it is within
standard limit (standard limit of received optical power of ONU: -24dBm ~
-8dBm), if within the limit, it indicates that the optical power is normal; if not,
treat as follows:
 If the optical power is too high, add an optical attenuator on the path for
recovery;
 If the optical power is too low, check the path and recover the optical
power.
4. Check whether the interface card is present and whether it has abnormal
alarms or not. If the interface card fails, replace it and refer to the AN5516-06
Optical Line Terminal Equipment Component Replacement for details.
5. Check whether the ONU can be normally authorized. If no, check whether the
current ONU authorization mode is correct, and check whether the MAC
address and the SN logical number of the ONU are in the authorization white
list.
 If the ONU authorization mode configuration is incorrect, re-configure the

authorization mode according to the planning data.
 If the MAC address or the SN logical number of the ONU is not in the
authorization white list, add it to the white list and deliver the configuration
to the equipment.
Version A 2-7
2.5 ONU Network Management Connection

Failure
Symptom
The AN5516-06 runs normally, the ONU status indicator on network management
is grey.
Fault analysis
 Fiber at the PON interface or at the ONU side is loose or broken;
 Optical power is abnormal;
 ONU equipment fails.
Caution:
connector.
 If the fiber at the PON interface or at the ONU side is loose, broken or the
optical power is abnormal, refer to Section 2.3 LOS Indicator of ONU Is
Illuminated for details.
 Contact FiberHome if the ONU is failed.
2-8 Version A
2.6 Network Interface Indicator Is Extinguished

Symptom
The Ethernet link indicator of the AN5516-06 is extinguished.
Fault analysis
Possible causes include a bad network cable connection or an equipment

hardware failure;
1. Check peripheral equipment of the AN5516-06, and notify related

maintenance personnel for troubleshooting if it has failed; otherwise, go to
Step 2.
2. Check network cable connection, remove and reinsert the cable. Go to Step 3
if it does not work.
3. Use a network cable tester to check the cable. Replace the cable if it is not
good.
Version A 2-9
2.7 Equipment Management IP Address Ping

Timeout
Symptom
A Ping of the network management computer IP adress fails to respond and times
out.
Fault analysis
Possible causes are shown below:
 A peripheral router or switch fails;
 A physical connection fault;
 An equipment management VLAN and IP configuration error;
 An IP address configuration error of the network management computer.
1. Confirm whether the peripheral router or switch has failed. Notify related
maintenance personnel for troubleshooting if a failure has occurred; otherwise,
go to Step 2.
2. Check the link from the network management computer to the equipment
section by section.
 If the link is OK, go to Step 3;
 If the link fails, it may be a network cable connection fault or a network

card fault in general; check the network cable connection and operation of
the network card; if the network cable connection has failed or the network
card has failed, replace the network cable connection or the network card.
Otherwise, go to Step 5.
3. Check the equipment management VLAN configuration, and make corrections

if it is incorrect.
Related operations are shown below:
2-10 Version A
1) Log into the command line network management, enter cd service at the
command prompt Admin# in the configuration mode, click Enter to
access the configuration management VLAN and command list of service.
Refer to the AN5516-06 Optical Line Terminal Equipment Configuration
Guide for details on how to log into the command line network
management and enter the configuration mode.
2) In the service directory, enter the show manage vlan all command to
verify the settings of the management VLAN are identical with those
planned; details of command execution are shown below:
Example 1: the uplink interface 19:2 is set to management VLAN in the

untagged mode; the VLAN ID of the management VLAN is 4000; the
management IP is 10.26.1.1; the mask is 255.255.0.0.
Return message from the network management system is shown below:
VLAN ID: 4000
Name: manage
IP Address: 10.26.1.1/16
Gateway: 10.26.1.254
Mac address: 00:00:00:00:00:11
Tagged Ports:
Untagged Ports: 19:2
Example 2: the uplink interface 19:2 is set to management VLAN in the

tagged mode; the VLAN ID of the management VLAN is 4001; the
management IP is 10.26.2.1; the mask is 255.255.0.0.
Return message from the network management is shown below:
VLAN ID: 4001
Name: manage
IP Address: 10.26.2.1/16
Gateway: 10.26.1.254
Mac address: 00:00:00:00:00:11
Tagged Ports: 19:2
Untagged Ports:
Version A 2-11
Commands for modifying the management VLAN and IP on the command

line interface network management system are shown below:
Command
set manage vlan name <name> vid <vid> inputport [<portlist>|outbandport]
[untagged|tagged]
set manage vlan name <name> ip <A.B.C.D/M> {<A.B.C.D>}*1
4. Perform the fault analysis and troubleshooting according to the port mode of
the management VLAN.
 If the port of the management VLAN is in the untagged mode, check the
IP configuration of the network management system computer and correct
the IP address if it is incorrect.
 If the port of the management VLAN is in the tagged mode, follow the
steps below.
1) Check whether the switch is connected with the correct uplink

interface and VLAN of the switch is configured correctly or not. Here,
it requires that the data package sent from the switch to the uplink
port of the equipment carries the tag of the management VLAN; for
data package sent to the PC is untagged.
Note：
According to the Example 2 above, the port of the switch connected with
the uplink interface shall be set to the VLAN 4001 in the mode of tag.
The port of the switch connected with the PC should be set to the VLAN
4001 in the mode of untag.
2) Check IP configuration of the network management system computer

and correct the IP if it is incorrect.
2-12 Version A
2.8 Abnormal Link Between Equipment and

Switch
Symptom
The link between a GE optical interface of the AN5516-06 uplink card and the
switch is abnormal.
Fault analysis
 A bad fiber connection;
 An error in the interface mode configuration;
 Unmatched optical module types.
1. Check the connection of the optical fibers.
 If the fiber jumper is not connected correctly, pull it out and insert again;
 If the fiber is broken, replace it with a good fiber jumper.
Go to Step 2 if the fault is not solved.
2. Check the attributes configuration of uplink interface, for example, whether the
port is enabled or not, whether port auto negotiation and port operating mode
are identical with configuration of the connected switch or not.
Operation steps of checking the attributes configuration of uplink interface are

shown below:
1) Log into the network management system, right-click the HU1A → Config
→ Uplink port properties of the faulty OLT system.
2) Click , read the equipment configuration as shown in Figure 2 -1.
Version A 2-13
Figure 2 -1 The Attributes Configuration of the Uplink Interface
3. If the attributes configuration of the uplink interface is not identical with that of
the connected switch, make corrections. If identical, go to Step 4.
Operation steps of modifying the attributes configuration of uplink interface are

shown below:
1) Log in the network management system, right-click the HU1A → Config

→ Uplink port properties in the faulty OLT system as shown in Figure
2 -1.
2) If the port is not enabled, enable the corresponding uplink port.
3) Correct each parameter on the interface to make it identical with that of

the connected switch.
4) After correction, click button to apply the configuration to the

equipment.
4. Check whether the types of the optical modules at the equipment side and the
switch side are identical or not. The uplink card of the AN5516-06 will be
configured with a multimode optical module. If not identical, replace and make
them identical.
2-14 Version A
2.9 Link to Network Management Database

Failed
Symptom
When starting the ANM2000, the user does not enter the login window and sees a
prompt of Get data from anserver failed! as shown in Figure 2-2.
Figure 2-2 Link Failed
Fault analysis
The user of the ANM2000 network management system must access the database
when starting the ANM2000. The user has been created before installing the
network management system. Deleting this user may cause the above fault.
1. Check the database link with an SQL Editor.
Detail operation is shown below:
1) In the operating system, click Start → All Programs → Informix → SQL

Editor3.01 to open the window as shown in Figure 2-3.
Version A 2-15
Figure 2-3 The SQL Editor
2) Click the dropdown menu in the window and check database link. If the
database tree can be expanded and can display sub databases, the link is
OK. If the database tree cannot be expanded, the link is abnormal. Check
the installation and configuration of the database. The normal database
link is shown in Figure 2-4.
2-16 Version A
Figure 2-4 The SQL Editor Server / Database Dropdown Menu
2. If it is found that the user anm2000 is not added when checking the operating
system users, add the user into informix-admin group in the operating system.
3. In the operating system, click Start → All Programs → Informix dynamic

server 9.40 → ol_anmxx to open the window as shown in Figure 2-5.
Version A 2-17
Figure 2-5 The ol_anmxx Window
4. After the prompt in the DOS screen, enter the d:\aems\md\andb directory and
input dbaccess and b grant.sql, and then press Enter.
5. Log into the network management system again and the symptom will
disappear.
2-18 Version A
3 Troubleshooting of Data Service
Faults
This chapter introduces troubleshooting data service faults of the AN5516-06,

which includes the following:
Background Knowledge
Troubleshooting Flow
Troubleshooting of Common Faults
Version A 3-1
3.1 Background Knowledge

The typical data service application network diagram for the AN5116-06 is
illustrated in Figure 3-1.
Figure 3-1 Typical Network of the AN5516-06 Data Service
The data service application network is described as follows:
In the data service application network, the AN5516-06 is connected with the
remote ONUs through a splitter and the ONUs are connected with subscribers’
computers directly or through family gateways to provide data services. The
subscribers access the Internet using the PPPoE protocol.
3-2 Version A
3 Troubleshooting of Data Service Faults
3.2 Troubleshooting Flow

Troubleshooting of data service faults is shown in Figure 3-2.
Start Start
Check status of peripheral

Check status of peripheral equipment
equipment
Check ONU status

Check OLT uplink link
Check network cable connection

between ONU and PC network card
Check ONU registration status
Check communication between
GPON interface and PC
Check communication status
inside GPON system
Check VLAN ID of uplink card
Confirm BRAS service data

status Confirm BRAS service data
status
End End
A) Data service interruption of all B) Data service interruption of an individual

subscribers subscriber
Figure 3-2 Troubleshooting Flow for Data Service Interruption
Version A 3-3
3.2.1 Troubleshooting Data Service Interruption of All Users
3.2.1.1 Checking Status of Peripheral Equipment
Analysis and troubleshooting
First determine whether the interruption of all data services is arising from
peripheral equipment or not through consulting maintenance personnel.
Main peripheral equipment of data service is shown as follows:
 Ethernet switches;
 Routers;
 BRAS equipment.
3.2.1.2 Checking OLT Uplink
The method for viewing uplink status of the AN5516-06 is shown below:
1. Ascertain the status of the uplink by viewing the uplink card alarms in the
network management system. Related alarms of the HU1A card of the
AN5516-06 are shown in Table 3-1.
Note：
Refer to the AN5516-06 Optical Line Terminal Equipment Alarm and

Event Reference for causes and troubleshooting methods of different
alarms.
3-4 Version A
Table 3-1 Related Alarms of the HU1A Card
Alarms of HU1A Card Alarm Level Alarm Type

Card hot-insertion alarm Urgent alarm Equipment alarm
Optical interface LOS Urgent alarm Communication alarm
Uplink / downlink CRC error
Secondary alarm Service quality alarm
cross threshold alarm
Port connection failure alarm Prompt Communication alarm
2. Check whether properties configuration of the uplink card port is identical with
that of the connected switch. Check the port type, the port enabled / disabled
status, port auto-negotiation status, port rate and port work mode etc.
 If the configuration is not identical, correct it on the AN5516-06 or the

switch;
 If the configuration is identical, go to Section 3.2.1.3.
Access method
 The method for viewing / modifying the uplink port properties is shown below.
Operation Access Method

View / modify the uplink port Click the HU1A card in the Object Tree pane and select
properties Config → Uplink Port Properties in the shortcut menu.
 The network management system window for viewing / modifying the uplink
port properties is shown in Figure 3-3.
Figure 3-3 Viewing / modifying the Uplink Port Properties
Version A 3-5
3.2.1.3 Checking Registration Status of ONU
Check whether the ONU registration is successful or not on the network

management system.
 If not successful, it is often due to the optical path fault. Check the fiber
connection and received optical power at the ONU.
 If successful, go to 3.2.1.4.
Access method
 The method for checking the ONU registration status is shown below:

Check the ONU registration
Click the EC4B card in the Object Tree pane.
status
 The network management system screen for checking the ONU registration
status is shown in Figure 3-4. If the REG indicator in the legend is solid green,
it indicates a successful registration. If the REG indicator is grey, it indicates a
failed registration.
Figure 3-4 The Screen for checking the ONU registration status
3-6 Version A
3.2.1.4 Checking Internal Communication Status of EPON System
The method for checking the internal communication status of the EPON system is
shown below:
1. Select one cable interface from the uplink card of the AN5516-06; use a
network cable to connect it to one test laptop or PC.
2. Select one remote side ONU and connect it to one test laptop or PC using a
network cable.
3. Add one service VLAN in the service VLAN configuration screen in the
untagged mode; the VLAN ID should be same as that of the ONU in Step 2.
Refer to related sections in the AN5516-06 Optical Line Terminal Equipment
Configuration Guide for details on how to configure the service VLAN.
4. Set the local computer and the remote computer on one network segment for
mutual Ping test.
 If they can Ping each other, Ethernet communication is normal in the

EPON system. Then go to 3.2.1.5.
 If not, contact FiberHome for troubleshooting.
3.2.1.5 Confirming Status of BRAS Service Data
Use a test laptop connected to the uplink interface (to test the PC configured in Step
4 of 3.2.1.4) for PPPoE connection test.
 If a prompt of 678 error appears, the uplink link must be faulty. Maintenance
personnel for the upper BRAS equipment should be notified for inspection to
confirm whether the service data is normal or not.
 If it connects successfully, it indicates that the faulty of peripheral equipment is

excluded. Contact FiberHome for troubleshooting.
Version A 3-7
3.2.2 Troubleshooting Data Service Interruption of an
Individual User
First determine whether the data service faulty of an individual user is caused by
peripheral equipment or not by questioning the maintenance personnel of the
Main peripheral equipment of data service is shown as follows:
 Routers;
 BRAS equipment.
3.2.2.2 Checking Connection between ONU and PC
Check whether the ONU port can normally learn the MAC address of user’s PC or
not. For specific operations refer to Section 6.3.2 of AN5116-06 Optical Line
Terminal Equipment GUI Reference.
 If the ONU cannot learn the MAC address of the user’s PC, it may be caused
by a connection fault between the user’s PC and the ONU. Correct the
connection fault between the PC and the ONU.
 If the ONU can learn the MAC address of user’s PC, the connection between
user’s PC and ONU is OK. Go to Section 3.2.2.3 for troubleshooting.
3-8 Version A
3.2.2.3 Checking Communication between EPON / GPON
Interface Card and PC
In the OLT MAC address list, check that the PC network card MAC address and the
VLAN tag learned by the EPON / GPON interface card are correct or not, to
determine whether the communication between the interrupted PC and the EPON /
GPON interface card is good or not.
 If the corresponding EPON / GPON interface card can learn the network card
MAC adress of the user’s PC, and the VLAN ID is the service VLAN ID of the
user, it indicates that communication between the EPON / GPON interface
card and the PC is good. Go to Section 3.2.2.4 for troubleshooting;
 If the corresponding EPON / GPON interface card cannot learn the network
card MAC adress of user’s PC, contact FiberHome for troubleshooting.
Access method
 The method for checking the MAC address list learned by OLT is shown
below:

Right-click the HSWA card in the Object Tree pane, and
OLT MAC address list select Get Information → OLT Mac Addr Table from the
shortcut menu.
 Figure 3-5 illustrates the screen of MAC addresses and corresponding service
VLAN tags of the users learned by the EPON / GPON interface card.
Figure 3-5 OLT MAC Address List
Version A 3-9
3.2.2.4 Checking VLAN ID in Uplink Card

In the OLT MAC address list, check whether the uplink card has obtained the VLAN
ID distributed to the user or not.
 In the OLT MAC address list, if the uplink card slot has no corresponding
user’s service VLAN ID, it indicates that the upstream equipment has not
configured this VLAN ID, so you have to contact related maintenance
personnel for resolution.
 In the OLT MAC address list, if the uplink card slot has corresponding user’s
VLAN ID, go to 3.2.2.5 for troubleshooting.
Access method
 The method for checking the VLAN ID on the uplink card is shown below:

Right-click the HSWA card in the Object Tree pane,
OLT MAC address list and select Get Information → OLT Mac Addr Table
from the shortcut menu.
 To check the VLAN ID on the uplink card, refer to Figure 3-6.
Figure 3-6 OLT MAC Address List
3.2.2.5 Confirming Status of BRAS Service Data

Connect the computer to the uplink interface, complete connection setting in the
operating system and conduct PPPoE connection test.
 If a prompt of 678 error appears, the uplink must be faulty. Maintenance

personnel for the upstream BRAS equipment should be notified to confirm
whether the service data is normal or not.
 If it connects successfully, it indicates the fault must be caused by the EPON /

GPON system. Contact FiberHome for troubleshooting.
3-10 Version A
3.3 Troubleshooting of Common Faults
3.3.1 Windows Operating System Prompts a 678 Error
Symptom
The Windows operating system issues a 678 error when connecting a user
terminal with PPPoE.
Fault analysis
The prompt of 678 error indicates no response from the remote computer;
fault analysis and isolation are shown as follows:
 In the event an individual user encounters the problem the possible

causes are as follows:
 Error in the configuration data on the ONU;
 Error in the user data on the BRAS.
 In the event that all users of the equipment encounter the problem the
possible causes are as follows:
 Uplink interface link failure;
 Optical path from OLT to ONU failure;
 BRAS failure.
Refer to Section 3.2.1 Troubleshooting Data Service Interruption of All Users and
3.2.2 Troubleshooting Data Service Interruption of One User for details.
Version A 3-11
3.3.2 Windows Operating System Prompts 691 Error
Symptom
The Windows operating system issues a 691 error while connecting a user terminal
with PPPoE.
Fault analysis
Possible causes are shown as follows:
 Computer hardware failure.
 Incorrect user’s name or code;
 The BRAS has bound the user’s name with VLAN, port or MAC address
binding.
1. Check the computer hardware.
2. Check the user’s name and code provided by the user, use correct user’s
name and code for verification.
3. Check whether the user’s status on BRAS is bound or not and notify BRAS
maintenance personnel for troubleshooting.
3-12 Version A
4 Troubleshooting of Voice Service
Faults
This chapter introduces how to troubleshoot voice service faults of the AN5516-06,
which includes the following:
Troubleshooting of Common Faults
Version A 4-1

The AN5516-06 voice service network is shown in Figure 4-1.
Figure 4-1 The AN5516-06 Voice Service Network
In the voice service application network, the AN5516-06 is connected with the
ONUs through a splitter. The ONUs provides an RJ-11 port for the telephone
connection. The ONU compresses and encodes the voice signal to implement
analog to digital conversion, and then transfers the voice data to the IP network
through OLT in the form of IP data package. The call control for voice services is
finished by the softswitch equipment.
4-2 Version A
4 Troubleshooting of Voice Service Faults
A) Service interruption of all users B) Service interruption of one user
Figure 4-2 Troubleshooting Flow of Voice Service Interruption
Version A 4-3
4.2.1 Troubleshooting Voice Service of All Users
When all users’ voice service is interrupted, question maintenance personnel of

peripheral equipment to initially determine whether the fault is caused by the
Main peripheral equipment involved in voice service is shown below:
 Routers;
 Softswitch platform equipment.
4.2.1.2 Checking OLT Uplink
The OLT voice uplink bears all ONU voice media flows and signal flows under the
OLT. The status of the OLT uplink should be checked after troubleshooting
Refer to Step 2 of Section 3.2.1 for details of checking and troubleshooting the
uplink of the AN5516-06.
4-4 Version A
4.2.1.3 Checking Local End Service VLAN Data
Check the local end service VLAN data configuration, which is to check whether
the configuration of the following parameters is identical with the planning data:
starting VLAN ID / VLAN ID end, and TAG / UNTAG, Interface NO.
 If the configuration is incorrect, correct according to the planning data;
 If the configuration is correct, go to 4.2.1.4 for troubleshooting.
Access method
 Method for checking the local end service VLAN data is shown as follows:

Right-click the HSWA card in the Object Tree pane,
Configure the local end service select Config → Local VLAN from the shortcut menu,
VLAN data and then click the Local End Service VLAN tab in the
window that appears.
 The screen for configuring and checking the local end service VLAN data is
shown in Figure 4-3.
Figure 4-3 Configure the Local End Service VLAN Data
Version A 4-5
4.2.1.4 Checking Configuration of NGN Uplink Interface
An MGC IP address configuration error will cause communication failure between

the equipment and the MGC. To test the link status of the equipment and MGC,
maintenance personnel can connect a PC through the uplink interface, and then
Ping the MGC IP address from the PC to check the connectivity of the equipment
and the MGC. This same test can check if the connection is losing packets.
For some softswitch platforms, if the heartbeat is not activated for a long time, the
ONU will lose communication with the softswitch platform, so that the voice service
is interrupted.
Check configuration of the NGN uplink interface. The configuration mainly includes
protocol type, MGC IP address and heartbeat switch.
 If the configuration is incorrect, correct according to the planning data;
 If the configuration is correct, contact FiberHome for troubleshooting.
Access method
 Method for checking the NGN uplink interface data is shown below:

Right-click the HSWA card in the Object Tree pane and select
NGN uplink interface Config → Voice Config → NGN Interface from the shortcut
menu.
 The screen for configuring NGN uplink interface data is shown in Figure 4-4.
Figure 4-4 Configuring the NGN Uplink Interface
4-6 Version A
4.2.2 Troubleshooting Voice Service of One User
When the voice service of an individual user is interrupted, question maintenance

personnel of the peripheral equipment to initially ascertain whether it is caused by
Main peripheral equipment involved in voice service is shown below:
 Softswitch platform equipment;
 ONUs;
 Telephones.
4.2.2.2 Checking Connection of Subscriber Lines
Check whether the subscriber line is electrically short-circuited or open at the ONU
side, and whether the wiring scheme is correct.
 If the subscriber line fails, notify the maintenance personnel for inspection and
repair;
 If the subscriber line is OK, follow Section 4.2.2.3 for troubleshooting.
4.2.2.3 Checking ONU Status
Check the registration and authorization of the ONU. Refer to Section 3.2.1.3 for
details.
 If the ONU is not legally registered or authorized, refer to Section 3.2.1.3

Checking the Registration Status of the ONU for troubleshooting;
 If the ONU is legally registered and authorized, refer to Section 4.2.2.4 for
troubleshooting.
Version A 4-7
4.2.2.4 Checking Related Configuration of Voice Service

For voice service fault of an individual user, check related data configuration of
voice service after troubleshooting the subscriber line and the ONU.
 If the data configuration is incorrect, correct data on the network management

system;
 If the data configuration is correct, refer to Section 4.2.2.5 for troubleshooting.
Parameters to be checked and influences are shown in Table 4-1.
Table 4-1 Main Parameters and Influences
Main parameters Influences

ONU public
A configuration error will cause an unavailable connection of the ONU
network IP, mask,
and the MGC.
gateway
Endpoint domain
A configuration error will cause a registration failure of the gateway.
name
ONU protocol port A configuration error will cause a registration failure of the gateway.
Endpoint user’s
A configuration error will cause a registration failure of the port.
name
The parameter must be configured when using H.248 protocol. A
configuration error will cause a busy tone after dialing fault. After the
RTP template is configured, it should be bound to the ONU and the
RTP tag format
parameter will take effect. If it is bound incorrectly or not bound, the
configured RTP is invalid. Refer to AN5516-06 Optical Line Terminal
Equipment GUI Reference for details.
The parameter must be configured when using SIP protocol. A
Digit map
configuration error will cause a busy tone after dialing fault.
DigitMap timer A configuration error will cause abnormal reception of the platform, so
duration the call cannot be connected.
The parameter must be configured when using SIP protocol. The user
SIP telephone
cannot use the telephone if it is not correctly configured.
SIP protocol
The parameter must be configured when using SIP protocol. The user
attested user’s
cannot use the telephone if it is not correctly configured.
name
SIP protocol The parameter must be configured when using SIP protocol. The user
attested code cannot use the telephone if it is not correctly configured.
4-8 Version A
Access method
 The method for checking parameters such as ONU Public IP, ONU Public IP
Subnet, ONU Public IP Gateway, Endpoint Domain Name / SIP, ONU
Protocol Port No. and Endpoint User is shown as follows:

Configure NGN uplink
Config → Voice Config → NGN Configuration from the shortcut
user’s data
menu.
 Check parameters such as ONU Public IP, ONU Public IP Subnet, ONU
Public IP Gateway, Endpoint Domain Name / SIP, ONU Protocol Port No.
and Endpoint User. The screen is shown in Figure 4-5 and Figure 4-6.
Figure 4-5 NGN Uplink User’s Data Configuration (Applying H.248 Protocol)
Figure 4-6 NGN Uplink User’s Data Configuration (Applying SIP Protocol)
 The method for checking intercommunication parameter template of the

softswitch platform using the network management system is shown below:

Configure softswitch Right-click the system in the Object Tree pane and select Config →
intercommunication Profile Definition →Softswitch Parameters Profile from the
template shortcut menu.
 The screen for checking the configuration of RTP resource tag format is shown
in Figure 4-7.
Version A 4-9
Figure 4-7 Configure Softswitch Intercommunication Template (RTP Resource)
 The screen for checking the configuration of DigitMap timer is shown in Figure
4-8.
Figure 4-8 Configure Softswitch Intercommunication Template (DigitMap Timer)
4.2.2.5 Confirming Service Data of SoftSwitch Platform
Ask the maintenance personnel of the core network to determine whether the data
configuration of softswitch platform equipment is correct. Number analysis error on
the MGC and abnormal user’s data on HSS/SDC will influence individual user’s
service.
 If the upstream softswitch platform has failed, notify the maintenance

personnel for troubleshooting;
 If the upstream softswitch platform has not failed, contact FiberHome for
troubleshooting.
4-10 Version A
4.3 Troubleshooting Common Faults
4.3.1 Busy Tone or No Tone after Picking Up the Telephone
Symptom
The user hears a busy tone or no tone after picking up the telephone receiver and
there is no dial tone.
Fault analysis
 Error in the heartbeat mechanism settings.
If heartbeat timeout is set to 0, the ONU will send a port registration message
when sending a heartbeat command. This will cause the endpoint status reset.
Then the user will hear a busy tone after picking up the telephone.
 A configuration error of the equipment endpoint domain name will result in

unsuccessful registration on the softswitch platform.
 The endpoint user’s port name is not identical with that on the softswitch
platform.
1. Check the heartbeat mechanism settings. The heartbeat time-out should, in

general, be set to 3.
The access method is shown below:

Right-click the HSWA card in the Object Tree pane and
Display heartbeat parameter select Config → Voice Config →Keep Alive from the
shortcut menu.
The operation screen is shown in Figure 4-9.
Version A 4-11
Figure 4-9 The NGN Heartbeat Parameters
2. Check the domain name of the equipment endpoint and configuration of the
port domain name. See Section 4.2.2.4 for details.
3. Contact FiberHome if the above steps do not work,
4.3.2 Dial Tone Cannot Be Cut Off After Dialing
Symptom
The dial tone cannot be cut off after dialing.
Fault analysis
 The telephone dial mode is set to pulse dialing while the ONU voice port only
supports DTMF dialing;
 There is an extension on this line that has not been hung up.
1. Check the telephone dialing mode. The telephone often has a two-option
switch key. The P of the switch key indicates pulse dialing; and the T indicates
DTMF dialing. If the switch is at the option P, switch it to the option T.
2. Check all telephones (including extensions) of this line. All the telephones
should be hung up again and then used for dialing.
4-12 Version A
4.3.3 Busy Tone after Calling Dial
Symptom
A dial tone can be heard when picking up the telephone. But after dialing a phone
number, a busy tone is heard though the called number is not busy.
Fault analysis
 A configuration error of RTP resource;
 An incorrect configuration of the DigitMap timer, long timer and short timer;
 A telephone number configuration error in the service configuration of the

FTTH-type ONU;
 A DigitMap configuration error when using SIP protocol.
1. Check the configuration of the fixed part of the RTP resource, long and short
dialing timers. Also check that the telephone number configured on the
FTTH–type ONU is identical with that on the platform. If the configurations are
not identical, make corrections. See Section 4.2.2.4 for details.
2. When using SIP protocol, check that the dialing rules in the DigitMap are
identical with the practical rules; if not, make corrections. See Section 4.2.2.4
for details.
Version A 4-13
4.3.4 A One-way Call Fault when User Calls
Symptom
Only one side of the telephone can hear the voice of the other side after the
connection is made.
Fault analysis
 A network IP conflict;
 A media server end configuration error;
 A line fault;
 A telephone fault.
1. Conduct packet capture analysis at the uplink interface, check the RTP flow.
 Go to Step 3 if the RTP flow is bidirectional;
 If the RTP flows are unidirectional, check whether the valid IP address of
the equipment conflicts with the IP address of other equipment. The MAC
address associated with the IP address can be viewed at the softswitch
platform end. Check whether it is identical with actual MAC address of the
equipment. If the MAC addresses are not identical, it indicates that the IP
address of the equipment conflicts with other equipment. Modify the IP
address, if the fault is not eliminated afterwards, go to Step 2.
2. Troubleshooting unidirectional RTP flow
 The equipment only sends media flows but does not receive media flows.
Contact the maintenance personnel of the platform to view and determine

whether the media server filtered the data flow.
 The equipment only receives media flows but does not send media flows.
 Conduct mirroring packet capture at the uplink interface and view

whether the equipment sends RTP packets or not. If it sends RTP
packets and does not receive any response, contact the related party
to find out the causes;
4-14 Version A
 If the subscriber can Ping the far end, but the far end equipment does
not send media flows, check whether the far end platform changes
the RTP mode into transmit mode;
 If the far end platform is in transmit mode and the equipment still does
not send media flows, contact FiberHome for troubleshooting.
3. A line fault or telephone fault
Substitute a known good telephone for the suspected one.
 If the voice service recovers after substitution, the telephone must be

faulty, replace the faulty telephone with the good one.
 If the voice service is still abnormal, it may be caused by cross or

electrical short-circuit of the external subscriber line. Contact related
maintenance personnel for troubleshooting.
4. Contact FiberHome for troubleshooting if the above steps do not work.
4.3.5 Intra-system Users Disconnected
Symptom
There is a dial tone after the voice user picks up the telephone. But the ONU fails to
get connect with another user in the AN5516-06 system.
Fault analysis
 An incorrectly configured number of the dialed ONU;
 The ONU has not successfully registered with the PUBA card;
 An ONU fault.
1. Check whether the dialed number is assigned to the expected ONU. If the
number is not assigned or is incorrectly configured, reconfigure the ONU.
Refer to the AN5516-06 Optical Line Terminal Equipment Configuration Guide
for details.
2. If the ONU fails or cannot be registered with the PUBA card (the REG LED on
the ONU keeps blinking or blacks out), contact FiberHome for troubleshooting.
Version A 4-15
4.3.6 The Dialed Number Does Not Exist
Symptom
When calling a normal subscriber telephone, the caller receives a prompt of “The
number you have dialed does not exist.”
Fault analysis
The softswitch platform has not configured the user’s number.
Ask maintenance personnel of the softswitch platform to configure the user.
4.3.7 No Dial Tone When Picking Up Telephone
Symptom
No dial tone when the user picks up the telephone.
Fault analysis
 The user’s telephone is damaged;
 The cable connection of POTS port is incorrect;
 Communication of the MGC and the ONU is interrupted;
 A voice configuration error.
1. Check the telephone.
 If the telephone has failed, replace it;
 If the telephone is OK, go to the next step.
2. Check the cable connection at the POTS port.
4-16 Version A
 If the cable connection is abnormal, ask the external line maintenance

personnel to perform the normal connecting operation;
 If the cable connection is OK, go to Step 3.
3. Determine whether communication of the MGC and the ONU is normal by

checking the registration of the ONU with the MGC and the NGN user’s port
status.
 If MGC registration is not successful or the port status is abnormal, check

the configuration of the NGN uplink interface and the uplink user’s data.
 If the ONU has registered successfully and the port status is normal, go to
the next step for troubleshooting.
The method for checking the MGC and port status is shown below:

Right-click the HSWA card in the Object Tree pane, select
Display the status of MGC
Get Information → NGN Status from the shortcut menu,
registration server
and click the MGC/Registrar Server Status tab.
Right-click the HSWA card in the Object Tree pane, select
Display NGN user’s port status Get Information → NGN Status from the shortcut menu,
and click the NGN User Port Status tab.
The operation screen is shown in Figure 4-10 and Figure 4-11.
Figure 4-10 Display the Status of MGC Registration Server
Version A 4-17
Figure 4-11 Display the NGN User’s Port Status
4. Check the voice service configuration. Refer to Section 4.2.2 Troubleshooting

Voice Service of One User for details.
5. Contact FiberHome for troubleshooting if the above steps do not work.
4.3.8 Excessive Noise During Calls
Symptom
There is too much noise when the user is calling.
Fault analysis
 A telephone failure;
 Silence suppression algorithm is set in the ONU POTS port properties. This
generates the packet jitter which can increase the noise levels;
 Bad protective earth ground cable. This causes current noise.
1. Check the telephone and replace it to see whether the fault is eliminated or not.
If there is still too much noise, go to Step 2.
2. Turn off the silence suppression and check whether the fault is eliminated. If
there is still too much noise, go to Step 3.
4-18 Version A
The method for turning off the silence suppression is shown as follows:

Click the EC8B card in the Object Tree pane, and then
Turn off the silence right-click the ONU AN5006-04[1], select Config → Port
suppression Service Config in the shortcut menu, then click Voice Config
tab in the window that appears.
Figure 4-12 Turn on the Silence Suppression
3. As for the corridor type ONU, check the earth grounding of the power supply.
Version A 4-19
4.3.9 Echo in Calls
Symptom
The user hears his or her own voice after a few seconds’ delay when calling.
Fault analysis
The echo suppression function of the equipment is not activated.
Activate the echo suppression function of the ONU on the network management
system.
The method for configuring the echo suppression is shown below:

Activate echo suppression right-click the ONU AN5006-04[1], select Config → Port
(taking AN5006-04 for example) Service Config in the shortcut menu, then click Voice
Config tab in the window that appears.
4-20 Version A
Figure 4-13 Activating the Echo Suppression
4.3.10 Abnormal Interruption in Long-Term Calling
Symptom
The call is automatically and regularly interrupted after establishing normal

communication for a period.
Fault analysis
Heartbeat settings of the MG and the MGC are not identical.
Version A 4-21
Modify the heartbeat settings of the ONU (MG) and make them identical with that
of the MGC. Refer to 4.3.1 Busy Tone or No Tone after Picking Up the Telephone
for details.
4.3.11 Abnormal Ring Back Tone
Symptom
No ring back tone is heard or it is abnormal. The calling goes on normally after the
called party picks up the telephone.
Fault analysis
 A user’s telephone failure;
 The external line is failed;
 The signal coordination of the ONU and the MGC is abnormal.
1. Replace the faulty telephone with a good telephone and go to Step 2 if the fault
is not resolved.
2. Test the telephone at the equipment port. If the ring back tone at equipment
port is normal, the external line is failed. Check whether the external line is
electrically short-circuited or incorrectly connected.
 If the external line has failed, contact related maintenance personnel for
troubleshooting;
 If it is OK, go to Step 3.
3. Conduct mirroring packet capture at the uplink interface and check whether
the platform sends the ring back tone signal.
 If the platform does not send the ring back tone signal, contact the related
softswitch platform personnel for troubleshooting;
 If the platform sends the ring back tone signal, contact FiberHome for
troubleshooting.
4-22 Version A
4.3.12 Abnormal Three-Party Service
Symptom
 Symptom 1: the two-way calling can be established. There is no dial tone after
the caller sends a flash hook signal to establish a three-party calling;
 Symptom 2: two-way calling can be established. There is a dial tone after the
caller sends a flash hook signal to establish a three-party calling. But no
response is received after dialing;
 Symptom 3: The three-party calling can be established. But if the caller only
needs to talk with one party, he or she cannot switch between the two called
parties after sending a flash hook signal and dialing the 2 key.
Fault analysis
 The OLT equipment does not report the flash-hook event to the platform
correctly;
 The softswitch platform does not send dialing plan and dial tone after the OLT
equipment reports the flash-hook event.
Capture packets at the uplink interface and analyze signal flow in the three-party
calling.
 In Symptom 1, the OLT equipment does not report the flash-hook event to the
softswitch platform; it is the fault of ONU equipment. Contact FiberHome;
 In Symptom 2, the OLT equipment reports the flash-hook event but the
softswitch platform does not send dialing plan and dial tone. This is a fault of
the softswitch platform. Contact related softswitch platform personnel for
repair;
 In Symptom 3, the ONU equipment does not report or the softswitch platform
does not response correctly after the calling party sends the flash hook signal
and dials the 2 key. Contact related personnel for repair.
Version A 4-23
4.3.13 Fax Service Fault
Symptom
In faxing, the calling dials and starts sending a fax after the called party is ringing.
But the called party fails to receive the fax. The fax machine displays a received
failed warning.
Fault analysis
 A voice service failure;
 The fax modes of both parties are different: transparent fax mode (T.30) and
T.38 respectively;
 VBD can be enabled or disabled in T.30 mode. VBD is enabled by default.

T.30 only supports G711A/U encode mode;
 T.38 mode supports G711A/U, G.723 and G.729 encode mode.
 The intervals of VBD sending / receiving packets are different.
1. Set up a voice call and check if it is OK.
 If the voice call fails, refer to related chapter for troubleshooting and basic
voice service provisioning;
 If it is OK, go to Step 2.
2. Check the fax mode of both parties.
 If the modes are not identical, correct it;
 If the modes are identical, go to Step 3.
The method to configure the fax mode is shown as follows:

right-click the ONU AN5006-04[1], select Config → Port
Port service configuration
Service Config in the shortcut menu, then click Voice Config
tab in the window that appears.
4-24 Version A
Figure 4-14 The Port Service Configuration (Fax Mode)
3. Check VBD receiving / sending packet interval.
Conduct mirroring packet capture at the uplink interface. View whether the
encode mode of media flow and packet interval are identical with the
equipment, especially note the remote end media packet interval. If the fax
machine switches to T.30 mode and the receiving interval of the remote
equipment changes, VBD mode of the equipment should be enabled to be
consistent.
Version A 4-25
Caution:
In the T.30 mode, packet interval of the Huawei softswitch platform is

20 ms and that of Bell is 10 ms. To achieve communication between
Huawei and Bell, VBD mode of the AN5516-06 should be enabled.
And the packet intervals should be set as 10ms and 20 ms
correspondingly.
The VBD mode configuration method is shown below:

Right-click the system in the Object Tree pane and select
Configure packet interval Config → Profile Definition →Softswitch Parameters
Profile from the shortcut menu.
The operation interface is shown in Figure 4-15.
Figure 4-15 Packet Interval
4-26 Version A
5 Troubleshooting Multicast Service
Faults
This chapter introduces troubleshooting multicast service fault of the AN5516-06. It

includes the following contents:
Troubleshooting Common Faults
Version A 5-1

Multicast service network of the AN5516-06 is shown in Figure 5-1.
Figure 5-1 Multicast Service Network
There are multiple modes for delivering multicast service using the AN5516-06
system can, as shown in Table 5-1.
Table 5-1 The Multicast Service Modes using the AN5516-06
Multicast service Card and ONU work mode

mode Core switch card PON interface card ONU
IGMP Proxy-proxy Proxy Proxy Snooping
IGMP Proxy-snooping Proxy None Snooping
IGMP Snooping Snooping None (broadcast) Snooping
Controllable multicast Proxy Proxy None, transfer based
on the rules
IGMP Disable Disable Disable Snooping
5-2 Version A
5 Troubleshooting of Multicast Service Faults

The AN5516-06 provides multicast services in five modes. This section uses the
controllable mode as an example. Troubleshooting of multicast fault in other modes
can follow this same troubleshooting procedure.
Troubleshooting flow for multicast service interruption is shown in Figure 5-2.
Figure 5-2 Troubleshooting Flow of the Multicast Fault
Version A 5-3
5.2.1 Checking STB Status
Check the user’s STB and localize the fault by substituting a known good STB.
 If the STB status is abnormal, repair or replace the STB;
 If the STB status is normal, follow the instruction in Section 5.2.2.
5.2.2 Checking VLAN Configuration
Check whether the configuration of user’s service VLAN ID and multicast VLAN ID
are identical with the planning data. The multicast VLAN ID should be within the
service VLAN ID scope.
 If the configuration is incorrect, correct it using the network management

system;
 If the configuration is correct, follow Section 5.2.3 for troubleshooting.
Access method
 The method for checking the local end service VLAN data is shown as follows:

Configure the local end
Config → Local VLAN, and then click the Local End Service
service VLAN data
VLAN tab.
 The screen for checking the local end service VLAN is shown in Figure 5-3.
5-4 Version A
Figure 5-3 The Local End Service VLAN
 The method for checking the multicast VLAN data is shown below:

Configure multicast
Config → IGMP Config → Multicast VLAN from the shortcut
VLAN
menu.
 The screen for checking multicast VLAN data is shown in Figure 5-4.
Figure 5-4 The Multicast VLAN
Version A 5-5
5.2.3 Checking Configuration of Multicast Proxy IP
When the core switch card works under proxy mode, check the proxy IP address of
the core switch card. The multicast proxy IP address and the IP address of the
upstream equipment should be on the same network segment.
 If the configuration is incorrect, correct it using the network management

system;
 If the configuration is OK, follow Section 5.2.4 for troubleshooting.
Access method
 The method for checking the service multicast proxy IP address is shown
below:

Configure multicast
Config → IGMP Config → IGMP Proxy IP from the shortcut
proxy IP address
menu.
 The screen for checking service multicast proxy IP address is shown in Figure
5-5.
Figure 5-5 Multicast Proxy IP address
5-6 Version A
5.2.4 Checking Multicast Template and Port Configuration
Check the settings of the following main parameters. If the settings are incorrect,
make corrections; if the settings are correct, follow section 5.2.5 for
troubleshooting.
 The multicast group IP address and the corresponding authority settings;
 The preview duration and controllable multicast times;
 The port bandwidth configuration of the ONU and the maximum number of
online groups.
Access method
 The method for checking the multicast template and port configuration is
shown below:

Configure multicast Right-click the HSWA card in the Object Tree pane and select
template and related Config → IGMP Config → IGMP Profile and Port from the
parameters shortcut menu.
 The screen for checking the multicast template and port configuration is shown
in Figure 5-6, Figure 5-7 and Figure 5-8. The main parameters are shown in
the red frame.
Figure 5-6 The Multicast Template Configuration
Version A 5-7
Figure 5-7 The Group Parameters Configuration
Figure 5-8 The Port Parameters Configuration
5-8 Version A
5.2.5 Checking Bandwidth Configuration
Check the uplink interface bandwidth configurations. These must be greater than
the program bandwidth. Otherwise, the program cannot be supported.
 If the configured bandwidth is too low, make corrections;
 If the configured bandwidth is OK, follow Section 5.2.6 for troubleshooting.
Access method
 The method for checking the uplink bandwidth is shown below:

Right-click the HSWA card in the Object Tree pane and
Configure the maximum
select Config → IGMP Config → IGMP Cascade Ports from
multicast bandwidth of the
the shortcut menu. Then click the Max. Uplink IGMP
uplink interface
Bandwidth tab.
 The interface for checking the uplink interface bandwidth is shown in Figure
5-9.
Figure 5-9 Configuration of Total Bandwidth of the Uplink Interface
Version A 5-9
5.2.6 Checking ONU Service Configuration
Check the VLAN mode, VLAN ID and VLAN configuration on the ONU. If it is
incorrect, make corrections; if it is Ok and the fault still cannot be troubleshot
through the above flow, contact FiberHome for troubleshooting.
Treatment of the system to VLAN tags is shown below:
 For FTTB Type ONU, the VLAN mode should be transparent, and a VLAN ID
of HG is translated into a multicast VLAN ID;
 For FTTH Type ONU, the VLAN mode is TAG; the ONU adds a multicast
VLAN ID.
Access method
 The method for checking the ONU multicast service configuration is shown as
follows:

In the Object Tree pane, right-click the EC4B card to display all
ONU messages of the EC4B card in the right pane, right-click the
ONU service
object ONU and select Config → Port Service Config from the
configuration
shortcut menu. Then select the Data Port Config tab. In the tab,
click the Add button.
 The screen for checking the ONU multicast service is shown in Figure 5-10
and Figure 5-11.
5-10 Version A
Figure 5-10 ONU Multicast Service Configuration (Taking FTTH Type as an Example)
Version A 5-11
Figure 5-11 ONU Multicast Service Configuration (Taking FTTB Type as an Example)
5-12 Version A
5.3 Troubleshooting Common Faults
5.3.1 Failure to Go Online
Symptom
The user cannot get online.
Fault analysis
 The ONU has faults.
 The PC or STB of the user has faults.
 This multicast program has not been configured or the group VLAN
configuration is faulty.
 In the controllable mode, this user has no watching authority.
 In the controllable mode, this user has the watching authority, but the viewing
time and number of times that the user views the program cross the threshold.
 In the controllable mode, the configuration of the ONU port group multicast
bandwidth is not reasonable.
1. Check whether the ONU operates normally.
 If yes, go to Step 2 to check the PC or STB of the user;
 If no, check and repair the ONU or replace it.
2. Check whether the PC or STB of the user operates normally.
 If yes, go to Step 3;
 If no, check and repair the PC or STB of the user.
3. Check whether this multicast program is configured, and whether the VLAN of
the multicast uplink protocol message is consistent with the VLAN of this
multicast stream.
Version A 5-13
 If this multicast program is not configured, check whether the VLAN of this
multicast stream is consistent with the multicast global VLAN. Only when
the two VLANs are consistent can the multicast path be established.
 If the multicast program is configured, check whether the multicast uplink

protocol message is consistent with the VLAN of this multicast stream.
Only when the two VLANs are consistent can the multicast path be
established.
4. If the AN5516-06 equipment is in the controllable mode, check the multicast

configuration data and to see whether the user has the watching authority.
5. If the AN5516-06 equipment is in the controllable mode and the user has the
preview authority, please use the multicast log command to check the viewing
time and the number of times that the user previews the program.
 Within the reset period of subscriber preview authority, check whether the
viewing time that the user previews the program crosses the threshold. If
yes, the user can no longer watch the programs.
 Within the reset period of subscriber preview authority, check whether the
number of times that the user previews the program crosses the threshold.
If yes, the user cannot watch the programs.
 Within the reset period of subscriber preview authority, if neither the

viewing time and the number of times that the user previews the program
crosses the threshold, check whether the interval between this time and
last time that the user previews the program. If the interval is shorter than
the preview interval threshold, the user cannot watch the program.
6. If the AN5516-06 equipment is in the controllable mode, check whether the

ONU port multicast bandwidth configuration is reasonable. If the ONU port
multicast stream bandwidth plus the joining message bandwidth is larger than
the ONU port multicast bandwidth, the user cannot watch the program.
5-14 Version A
5.3.2 Failure to Watch a Multicast Program
Symptom
The user cannot watch the multicast program.
Fault analysis
 The multicast user cannot get online.
 The configuration or status of the multicast server is abnormal.
 The PON interface card operates abnormally.
 The PC of the user is abnormal.
 The IP address of the VLC video software is different from the network card IP
address.
1. Check whether the multicast user is online.
 If the multicast user is not online, follow the troubleshooting procedures in

Section 5.3.1
 If the multicast user is online, go to Step 2.
2. Mirror the multicast stream of the uplink port to the idle uplink port, then
perform the packet capture to check whether the multicast stream reaches the
uplink port.
 If the multicast stream does not reach the uplink port, check the
configuration and status of the multicast server.
 If the multicast stream reaches the uplink port, go to Step 3.
3. Mirror the multicast stream of the PON interface to the debug port (FE port) on
the PON interface card, then perform the packet capture to check whether the
multicast stream reaches the PON interface.
 If the multicast stream does not reach the PON interface, check whether
the PON interface card works normally.
 If the multicast stream reaches the PON interface, go to Step 4.
Version A 5-15
4. Check whether the multicast stream reaches the user port. If the user uses
video software such as VLC to view the program, you can check whether the
multicast stream reaches the user port by performing packet capture at the PC
side.
 If the multicast stream does not reach the user port, check whether the PC
of the user is normal.
 If the multicast stream reaches the user port. Check whether the IP
address of the VLC video software is consistent with the network card IP
address.
5.3.3 Failure to Watch a Program Even After Successfully
Accessing the Program
Symptom
The user is online but fails to watch a program.
Fault analysis
 The uplink port works abnormally.
 The VLAN configuration of the local end is different from that of the upper layer
router.
 The multicast packet suppression function is enabled on the uplink port.
 The video server does not transmit the video streams normally.
 The TTL value of the program is smaller than the number of hops from the
video server to the user.
1. Check whether the uplink port works normally and see whether the LNK
indicator LED is illuminated or blinking quickly.
2. Check whether the local end VLAN configuration of the uplink port is correct.
 If the upper layer router receives the messages with the designated VLAN
ID, check whether the VLAN configuration of the uplink port local end is
consistent with that of the upper layer router.
5-16 Version A
 If the upper layer router receives the messages without a designated

VLAN ID, check whether the attribute of the uplink port local end VLAN is
untag.
3. Check whether the multicast packet suppression function is disabled on the

uplink port. When starting the multicast service, you should disable the
multicast packet suppression function of the uplink port
4. Check whether the video server transmits the video streams normally. Make
sure that the video server operates normally.
5. Check whether the TTL value of the program is appropriate. This value should
be larger than the number of hops from the video server to the user.
Version A 5-17
6 Fault Cases
This chapter introduces how to troubleshoot typical faults and is organized as

follows:
System Fault Case
Voice Service Fault Case
Fax Service Fault Case
Other Fault Case
Version A 6-1
6.1 System Fault Case
6.1.1 A “651”, “619”, or “31” Fault Is Reported During ONU
Connection
Symptom
A “651”, “619”, or “31” fault is reported when the user of an ONU is dialing. The
dial-up can be successful after multiple attempts. And no off-line occurs after the
user gets online.
Fault analysis
 The optical power between the OLT and the ONU is abnormal;
 The ONU has hardware faults;
 The packet transmitting delay of the splitter in the uplink direction is overlong.
1. Ping the remote ONU. The Ping operation is normal and no packet loss
occurs.
2. Measure the optical power and the optical power is normal. We initially
determine that the ONU has hardware faults and replace the ONU. The fault is
not eliminated.
3. Analyze the PPPoE dialing process with the packet capture software, and we
find that the BAS server cannot receive the PPPoE dialing packet transmitted
from the user in a timely manner, so the BAS server transmits the PADT
termination signaling packet to the user. Based on the above analysis, we
confirm that the cause of the fault is the overlong packet transmitting delay of
the splitter in the uplink direction.
4. After replacing the optical splitter, the service is restored.
6-2 Version A
6 Fault cases
6.1.2 Endpoint Frequent Restart Fault
Symptom
The voice service is started by using the H.248 protocol. Somehow, the user
cannot dial, and cannot hear the dial tone but the current noise after off-hook. After
several minutes, the user is able to dial. Then the dialing switches frequently
between the normal and abnormal statuses.
Fault analysis
The IP address the ONU equipment is identical with the IP address other
equipment.
1. Via the packet capture analysis, we find the on-hook and off-hook signaling of
the ONU equipment A that connects with the user is normal in the former
period. In the later period, it begins to transmit the cold boot registration
packets to the platform repeatedly.
2. Analyze the records in the packets, and we find that equipment B that has the
same IP address as equipment A transmitted the cold boot registration packet
to the platform, which modified the ARP address table of the platform. Since
then, for any request received from equipment A, the platform replies to
equipment B. Since equipment A cannot receive any response from the
platform, it then transmits a 900 service recovery message to the platform. And
the platform continues to reply this message to equipment B. So equipment A
determines that the platform is not in service and starts to send the 901 cold
boot signaling to the platform. Because no response can be received,
equipment A transmits the cold boot registration packets to the platform
repeatedly.
3. Change the IP address of either equipment A or equipment B, and the fault is

eliminated.
Version A 6-3
6.1.3 Working Mode Inconsistency Between Uplink Port of
Equipment and Upper Layer Equipment Causes
Physical Connection Fault
Symptom
The uplink port of the AN5516-06 is connected to the upper layer equipment via an
LC/PC fiber. The uplink card’s panel indicator LED LINK2 is extinguished.
Fault analysis
The working mode of the AN5516-06’s uplink port is inconsistent with that of the
upper layer equipment.
1. Disable the auto-negotiation function of the SFP1 on the HU1A card via the
ANM2000, and the panel indicator LED LINK2 becomes illuminated
immediately.
2. Access the device directory and execute the following command:
show port 19:2
The system shows that the link status is up
3. Set the rate of uplink port to 1000Mbps without Auto Negotiation function
enabled and the connection becomes normal. The fault is eliminated.
Summary
The port of upper layer switch supports the rate of 1Gb/s; and the uplink port of the
AN5516-06 supports 10G and 1G. The default mode for the uplink port rate is
auto-negotiation; and the rate of the upper layer switch port is in the forced mode.
The two modes are not consistent, so the connection fails.
6-4 Version A
6 Fault cases
6.1.4 EPON Broadband Users Over a Large Area of An OLT
Have Faults
Symptom
A set of AN5516-06 equipment has about 2000 broadband users. Packet loss over
a large area, long delay and slow downloading occur in the Internet service.
Fault analysis
 The AN5516-06 has faults;
 The convergence layer equipment (e.g., the BAS) has faults.
1. Check whether the equipment has so many broadband users that the
bandwidth becomes insufficient, which results in network congestion and
packet loss. By analyzing the one-month traffic statistics via the BAS, we find
that the maximum bandwidth is 591M. So the bandwidth insufficiency is
excluded from the fault causes.
2. Modify the route of the broadband user, set the users to private line users, and
distribute fixed IP addresses for the users. The services of users pass through
the SR instead of the BAS. Then the services become normal.
3. Ping the BAS from the broadband user, and we find the delay is normal, no
packet loss occurs. When we Ping the broadband user from the BAS, packet
loss occurs.
4. Check the OLT’s uplink port that is connected to the BAS, and the status of the
uplink port is normal.
5. Check the MAC address learning status, and we find no loop.
6. Check the BAS configuration data, which is found normal.
7. Replace the BAS optical module. Then the fault is eliminated.
Version A 6-5
6.2 Voice Service Fault Case
6.2.1 Gateway Address Error Causes Fault of Voice Service
Symptom
The voice service of an ONU connected to the AN5516-06 equipment has failed.
The IP address of the gateway is 10.32.160.2.
Fault analysis
The ONU gateway configuration data is incorrect.
1. Enable the signal tracing function, and we find that the ONU returns a 510
UNKOWN ENDPOINT message when MGC (IP address: 10.0.55.2) is
auditing the ONU (IP address: 10.32.160.2).
2. The ONU returns a normal message after using a test IP address to replace its
original IP address, and subscriber’s calling is also OK.
3. The packet analysis indicates a space character was added after the original
gateway IP address “10.32.160.2” during configuration.
4. After deleting the space character following the gateway IP address

“10.32.160.2”, the ONU voice subscriber can call normally. The fault is
eliminated.
6.2.2 Voice Encoding Inconsistency Causes Abnormal
Operation When User Is Called
Symptom
A voice subscriber using an ONU connected to the AN5516-06 can call normally.
But the user often fails to have normal conversation when he / she is called, and
hears busy tone after off-hook.
6-6 Version A
6 Fault cases
Fault analysis
The voice encoding method of the softswitch platform is different from that of the
ONU.
1. Enable the signaling tracing function, and we find that the voice encoding
method of the softswitch platform is different from that of the ONU. The voice
encoding standard of the softswitch platform is G.711A and that of the ONU is
G.711U.
2. Change the voice encoding method of the ONU to G.711A. Continuously dial
and test the telephone for ten times and verify the user is connected after
picking up the telephone. The fault is eliminated. Figure 6-1 shows the
configuration GUI.
Figure 6-1 The ONU Voice Encoding and Decoding Configuration
Version A 6-7
6.2.3 DNS Configuration Error Causes Connection Failure
of External SIP Terminal Voice Service
Symptom
At a port of an ONU connected to the AN5516-06, a user started the video

telephone service and uses the SIP protocol. But the video telephone cannot
access the server after the configuration is completed.
Fault analysis
 The service configuration has errors;
 The uplink equipment has faults;
 The SIP terminal has faults.
1. No fault after checking the service configuration data.
2. In order to eliminate the uplink side problem, connect a laptop at the idle port
of the uplink card, change the port configuration to untag mode, and add the
port to the video telephone service VLAN.
3. Use the laptop to Ping the uplink switch and its gateway, and both the
operations are successful. We can determine that the uplink side is OK. The
fault may occur at the section between the OLT and the ONU, or between the
ONU and the SIP terminal.
4. Substitute a laptop for the SIP terminal and test if the laptop can Ping the
laptop connected with the uplink card, and if it can Ping the IP or gateway of
the uplink switch. And the results of both tests are yes. The above analysis
indicates a problem on the SIP terminal.
5. After asking the SIP terminal vendor to verify the SIP terminal configuration it
is found that the DNS configuration is incorrect. The video telephone service is
normal after SIP terminal vendor changes the DNS configuration.
6-8 Version A
6 Fault cases
6.2.4 Multiple Media Gateways Cause One-way Call
Phenomenon
Symptom
Start the voice service on the FTTN ONU connected to the AN5516-06. When
using a common telephone to call the cell phone, the telephone user often fails to
hear the voice of the cell phone user, but the cell phone user can hear the
telephone user.
Fault analysis
The media gateway is faulty.
1. Perform the packet capture operation on the ONU uplink port.
 Connect the serial port line to the Console interface of the HSWA card;
 Access the device directory via a terminal emulation software package

(e.g., Hyper Terminal), input the commands such as set mirror to 19:1
and set mirror add 19:4. Then use the network cable to connect the
mirror port and the laptop; and perform the packet capture operation on
the ONU uplink port to analyze the data.
2. When analyzing the faulty packet, we find that four remote media gateway IP
addresses are available when the RTP stream is established: 10.62.11.2,
10.62.11.6, 10.62.11.14, and 10.62.11.10, as shown in Figure 6-2.
Version A 6-9
Figure 6-2 Analyzing the faulty packet
3. When the route uses the media gateway whose IP address is 10.62.11.2 or
10.62.11.10, the voice service is normal. When the route uses the media
gateway whose IP address is 10.62.11.6 or 10.62.11.14, the one-way call
phenomenon occurs. If we Ping the four IP addresses from the equipment, the
IP addresses 10.62.11.2 and 10.62.11.10 give responses normally, and the IP
addresses 10.62.11.6 and 10.62.11.14 do not reply, as shown in Figure 6-3.
6-10 Version A
6 Fault cases
Figure 6-3 The results of Ping commands
4. We can determine the two media gateways whose IP addresses are

10.62.11.6 and 10.62.11.14 have not transmitted the media streams, so the
one-way call phenomenon occurs. Contact the maintenance personnel of the
softswitch equipment to modify the configuration data. After modification, the
problem is resolved.
Version A 6-11
6.2.5 Intelligent Telephone Has Faults in Long Distance Call
Symptom
When the AN5006-15 intelligent public telephone is connected with a 600m

subscriber line, the user can call and be called normally. When the telephone is
connected with a 1500m subscriber line, the user can only be called, and cannot
make calls.
Fault analysis
 The resistance value is inappropriate;
 The gain value is inappropriate;
 The echo suppression is enabled.
1. Perform the packet capture operation on the AN5516-06, and confirm that the
number is reported. When the subscriber line is 600m, the calling is normal,
and when the subscriber line is 1500m, the calling has faults. So we can
initially determine the fault is caused by the attenuation of power, which is the
result of the increase in the length of the subscriber line.
2. Restore the RTP stream, and we find that when the subscriber line is 600m,
the number is fully reported; and when the subscriber line is 1500m, the
number cannot be fully reported.
3. Check the POTS resistance value. If the POTS resistance value is

inappropriate, the reflection signal will be so strong that the DSP number
reporting will be interfered. Modify the resistance value from 600Ω to 680Ω,
and the fault is eliminated.
6-12 Version A
6 Fault cases
6.2.6 Noises Occur During Calls
Symptom
During the call, the called party hears the sharp noises but the calling party cannot
hear the noises.
Fault analysis
 The line is in poor quality;
 The ONU has faults;
 The mute function is enabled.
1. Check the quality of the line, and no problem is found.
2. Check the operation status of the ONU, and no problem is found.
3. When a user of this ONU calls the urban telephone numbers starting with a
certain number segment, the called party hears the noises; when the user calls
other urban telephone numbers, the called party hears no noise.
4. With further test, we find that all numbers of the same business building where
the number segment belongs to have the noise problem. So we can determine
that the ONU and the network access equipment of the business building do
not match in service configuration.
5. After performing several packet capture operations, we have not found packet
loss and other problems during the call.
6. Check the configuration of the SilenceSp item in the ONU voice service port
configuration GUI, and cancel the selection on the SilenceSp item, as shown
in Figure 6-4.
Version A 6-13
Figure 6-4 Configuring the SilenceSp item
7. After the parameter is modified, perform the test for several times. The noises
no longer appear and the fault is eliminated.
6-14 Version A
6 Fault cases
6.2.7 Multiple Users of an AN5006-07 ONU Cannot Make
Calls Simultaneously
Symptom
Some users of an AN5006-07 ONU have an unstable voice service. Sometimes

they can make calls normally; sometimes they cannot.
Fault analysis
Configuration error of the RTP resource name.
1. Check the ONU of these users via the ANM2000, and we find that they share
one ONU. Check the configuration data of the ONU, and no problem is found.
2. Check the telephone communication states of the users in the NGN RTP
Resource GUI of the corresponding ONU.
 It never occurs that any two or more telephones have been in the
communication state at the same time.
 No matter which telephone is online, the corresponding RTP Resource

Name is always RTP/0.
 When no telephone of this ONU is online, the user can call and be called
normally. But when one telephone of this ONU is online, all the other
telephones cannot be used, and their users can only hear the busy tone
either as the calling party or as the called party.
3. Check the configuration data of the softswitch equipment, and we find that the
RTP resource name RTP/1 is missing in the RTP resource item. Add RTP/1
and the voice services of the users become normal. The trouble is removed.
Version A 6-15
Summary
The AN5006-07 ONU has 16 ports, so its corresponding softswitch equipment

should configure 16 RTP resources (RTP/0 to RTP/15 by convention). The
telephones in communication will extract the RTP resources according to the using
sequence; that is, the first telephone in communication extracts RTP/0, the second
telephone in communication extracts RTP/1, and so on.
Among the 16 telephones, the first telephone that is used should extract the RTP/0
resource. As long as this telephone is in communication, the RTP/0 resource will
not be released, and the second telephone that is used should search for the
RTP/1 resource. If the RTP/1 is missing in the softswitch platform, the situation that
one online telephone prevents other telephones calling or being called.
6-16 Version A
6 Fault cases
6.2.8 Digitmap Configuration Error Causes Toll Call Failure
Symptom
In a project, the voice service is started by using the SIP protocol. The users of this
project cannot make toll calls to the telephone numbers staring with the area code
0660.
Fault analysis
The digitmap configuration is faulty.
1. Use a test user to call 0660-3363130 and perform the packet capture operation.
2. By analyzing the packet capture data, we find that the reported area code is 066.
So we determine that the incomplete reported area code causes the dialing failure.
The reported area code is related to the digitmap configuration.
3. The on-site maintenance engineers check the digitmap configuration and find
out it is 06【36】【38】xxxsxxxx. So the users can only make toll calls to the
telephone numbers staring with the area code 0663 or 0668. They cannot call
the telephone numbers whose area code is 0660.
4. Modify the digitmap configuration to 06【36】【038】xxxsxxxx. The fault is

eliminated. Now users can make toll calls to the telephone numbers staring
with the area code 0660.
Version A 6-17
6.2.9 Users of AN5006-20 ONU Cannot Hear Opposite Party
Symptom
The AN5516-06 has been expanded and a set of AN5006-20 equipment is added.
The voice service is started by using the SIP H.248 protocol. All users of the
AN5006-20 cannot hear the opposite part either as the called party or the calling
party. The opposite party can hear the user of the AN5006-20.
Fault analysis
The VLAN configuration of the voice service has faults.
1. Perform the packet capture operations on the AN5006-20 uplink port

respectively when the user is the calling party and the called party. We find the
H.248 uplink signaling normal, and the VLAN ID of the signaling is 21.
2. Check the H.248 downlink signaling, and find it normal. The downlink signaling
has no VLAN.
3. Check and find the VLAN ID of the RTP uplink unicast stream is 21, and the
downlink unicast stream has no VLAN. The destination MAC address is the
MAC address of the MCU card’s CPU.
4. Check whether the RTP stream intercommunication message of the MCU

card’s CPU and the DSP exists. The RTP data message whose source MAC
address is the CPU MAC address and destination MAC address is the DSP
MAC address, which means that the RTP stream message cannot be
transmitted from the CPU of the MCU card to the DSP chip. Thus the
messages are converted to unknown messages and are multicasted to the
uplink port.
6-18 Version A
6 Fault cases
5. By analyzing the packet capture data, we find that an RTP stream whose
source IP address and destination IP address are identical is transmitted
repeatedly. The source MAC address is replaced by the CPU MAC address of
the MCU card; the destination M AC address is replaced by the DSP MAC
address of the MCU card. (The DSP MAC address of the AN5006-20’s MCU
card is the CPU MAC address plus 1.) We can capture the RTP forwarded to
the DSP from the CPU at the uplink port, it means that the downlink RTP
stream cannot be forwarded from the CPU to the DSP. So they become
unknown packets and are broadcasted by the switch chip to the uplink port.
6. View the FDB address table of the AN5516-06’s core switch card, and find that
the voice service VLAN ID learnt by the uplink card is 4088, which means that
the upper layer equipment transmits the Untag data packets.
7. Modify the voice service VLAN configuration of the upper layer equipment, and
the fault is eliminated.
Summary
For the AN5006-20 ONU, the signaling streams are only processed by the CPU of
the MCU card, and the RTP streams need be processed by the DSP chip of the
MCU card.
The downlink signaling has configured the default VLAN 4088, and the signaling
can reach the CPU of the MCU card, so the signaling can intercommunicate with
the softswitch platform. But the RTP stream has configured the default VLAN 4088,
which is inconsistent with the RTP stream ID 21, so the RTP stream will not be
forwarded to the DSP of the MCU card. That is why no sound can be heard from
the downlink direction. And the RTP streams cannot find the destination, so they
are forwarded as the unknown packets and are broadcasted to the uplink port by
the switching chip.
Version A 6-19
6.2.10 AN5006-04 ONU Displays Wrong Incoming Call Time
Symptom
The AN5006-04 ONU uses the SIP protocol to interconnect with the softswitch
equipment of a company. Set the telephone time to Beijing time, e.g., 14:48 in May
the 13th. And when the telephone receives a call, the time displayed changes to
12:05 in February the 7th. Replace the telephone and the error persists.
Fault analysis
 The voice signaling flow cannot be established;
 OLT system time displaying has faults;
 The caller ID display configuration of the ONU is different from that of the
softswitch platform.
1. Enter the admin directory of the core switch card and issue the show time
command. We find that the time of the OLT system is correct.
2. By analyzing the packet capture data, we find that under the SIP protocol, the
voice signaling flow is normally established. We also find that the caller ID
display signaling transmitted from the platform has time signals, and the ONU
transmits the time signals to the telephone. So when the telephone receives
the incoming call, the time displayed changes to the time of the caller ID
display signaling.
3. Check the configuration status of the caller ID display mode. Log in the ONU
and use the codec command to check the configuration. The default
displaying mode of the ONU is FSK, which is different from that of the
softswitch platform. Now we find the cause of the fault.
4. Change the caller ID display mode of the ONU with the following method:
 Modify the caller ID display mode via the CLI NMS, and save the
modification to validate the modification.
6-20 Version A
6 Fault cases
 Modify the caller ID display mode via the ANM2000, and deliver the
modification to the equipment.
1) Log into the ANM2000, right-click the system in the Object Tree pane,
and select Config → Profile Definition → Softswitch Parameters
Profile from the shortcut menu that appears.
2) In the Softswitch Parameters Profile window that appears, change

the CallerIDmode of the softswitch interconnection profile binding to
the ONU to DTMF. (The default setting is FSK.) And use the default
setting for the other items. Then deliver the configuration to the
equipment, as shown in Figure 6-5.
Figure 6-5 Configuring the caller ID display mode
Version A 6-21
5. Check and find that the incoming call time of the telephone can be normally
displayed. The fault is eliminated.
Summary
 When the caller ID display mode of the ONU is configured as FSK, it will send
both the telephone number and the time signals transmitted from the
softswitch platform to the telephone. The time signals transmitted from the
softswitch platform are inconsistent with the time of the telephone. So when
the telephone receives a call, the time displayed by the telephone is the time
transmitted from the softswitch platform, and the time configured on the
telephone is changed.
 When the caller ID display mode of the ONU is configured as DTMF, it will
send only the telephone number transmitted from the softswitch platform to the
telephone. Under this mode, the time displaying configured on the telephone
will not be changed.
6-22 Version A
6 Fault cases
6.2.11 Incorrect DSP Profile Parameter Configuration Causes
Card Swiping Failure on POS Machine
Symptom
Both the data service and the normal voice service of the ONU are normal, but the
POS machine does not operate normally.
Fault analysis
 The software version of the ONU is incorrect;
 The earth ground cable of the equipment is not well grounded.
 The server number of the POS machine is incorrectly configured.
 DSP profile configuration is incorrect.
1. Log in the ONU and check its software version. The software version is
correct.
2. Check the grounding of the equipment. The grounding has no problem.
3. Configure the server number of the POS machine, and the POS machine
cannot connect to the server. After canceling the configuration, the POS
machine still fails to connect to the server.
4. Check the DSP profile, and find a parameter of the new profile is different from
that of the default DSP profile. The DSP profile usually uses the default profile
otherwise required.
5. Modify the DSP profile binding configuration. Change the binding profile to the
default profile. Then the POS machine can connect to the server and the card
swiping becomes successful. The fault is eliminated.
Version A 6-23
6.3 Fax Service Fault Case
6.3.1 Dial Mode Setting Error Causes Fax Service Fault
Symptom
When the user makes a call on the fax machine, the softswitch platform sends out
a warning tone for a dialing mistake and it cannot send a fax. But using the same
port as an ordinary telephone port, the user can both call and be called normally.
Fault analysis
The dialing mode of the fax machine is faulty.
1. After performing a capture packet test at the uplink port, it is discovered that
the displayed caller ID of the fax machine is longer than that of the ordinary
telephone.
2. Check the dialing mode of the fax machine and find that the dial mode of fax is
pulse dialing mode. Under normal condition it should use the DTMF dialing
mode.
3. Correct the dialing mode to the DTMF dialing mode on the fax machine to
eliminate the fault.
6-24 Version A
6 Fault cases
6.3.2 Incorrect Uplink Port Mode Configuration Causes
Connection Failure in Fax Service
Symptom
An ONU is connected to the AN5516-06. The users of the ONU have normal voice
services but fail to send or receive faxes.
Fault analysis
 The fax service parameter configuration has faults;
 The protocol converter has faults;
 The working mode of the uplink port is different from that of the switch.
1. Check the fax service parameter configuration of the ONU. The Fax Mode is
Transparent. The configuration is correct.
2. Perform the packet capture operation of the fax service on the AN5516-06’s
uplink port. By analyzing the data, we find that when the media gateway server
replies to the AN5516-06, a 6％ packet loss occurs. So we isolate the fault
between the AN5516-06 and the upper layer network.
3. Connect two PCs at both ends of the protocol converter respectively. Perform
the Ping operation to the other PC on both PCs and find no packet loss. So the
fault does not occur at the transmission channel between the AN5516-06 and
the switch.
4. Check and find the port working mode of the switch is auto negotiation. Check
and find the uplink port working mode of the AN5516-06 is 100Mbps and
Full-Duplex without enabled Auto Negotiation function. The working modes
of the two sets of equipment do not match.
5. Enable the auto negotiation function of the AN5516-06’s uplink port. Check
and find the fax service becomes normal. The fault is eliminated.
Version A 6-25
6.4 Other Service Case
6.4.1 ONU Network Access Fails to Be Reported
Symptom
Users can log in the ANM2000 via the client side. The operation on the ANM2000
is normal; users can query the equipment status; the alarms are reported in a
timely manner. When the ONU accesses the network, the OLT can authorize the
ONU, but the network access of some ONUs cannot be reported and recorded in
the log.
Fault analysis
 The process of the ANM2000 has faults;
 The polling interval of the ANM2000 is not reasonable.
1. The ANM2000 operates normally, and the status and alarms can be reported
in a timely manner. So we perform the packet capture operation of the ONUs
with network access report failure on the gathering server, application server
and the interface server. And we find the ONU network access information on
both the gathering server and the application server. No ONU network access
information is found on the interface server. We initially determine that the
anserver or the anmws process has faults.
2. Put userdump.exe under the root directory of any disk on the local computer.
Run the cmd command and access the directory of userdump.exe. Input
userdump <process name>, and press Enter. E.g.,
. An anserver.dmp file will be generated

under the corresponding directory. This operation backs up the memory data
of anserver.
6-26 Version A
6 Fault cases
3. By analyzing the ANserver.dmp file, we find that the polling of the ANM2000
is too frequent. So we modify the heartbeat interval item in the md.ini file
under the D:\AEMS\md\ini directory of the gathering server. The original value
30s is modified to 600s.
4. After restarting the ANM2000 services, the ONU network access can be
reported normally.
Summary
Because the equipment polling interval of the ANM2000 background is too short,
too much polling data waits to be processed by the background program. So the
ONU network access request cannot have immediate response, and the fault
occurs. By increasing the heartbeat interval when there are many ONUs, the
normal system reporting can be guaranteed, and the reporting operation does not
interfere with the normal processing of other commands.
6.4.2 Configuration of Received Commands Buffer Area on
Gathering Server Has Faults
Symptom
Users can log in the ANM2000 via the client side normally; but the new alarms
cannot be reported. The ANM2000 shows that the OLT status is status unknown;
the data of all the ANM2000 users in the User Data Check GUI are all displayed as
Unauth in DB, Auth in Device. And the equipment user data is blank.
Fault analysis
 The gathering server has faults;
 Configuration of the gathering server’s buffer area is not reasonable.
1. Telnet to the AN5516-06, and we find an ONU connected to the line card.
Version A 6-27
2. The ANM2000 cannot gather the equipment status and the alarms. This
indicates the communication interruption between the ANM2000 and the
equipment. Check the gathering server by visiting the gathering server via the
remote desktop function.
3. Put userdump.exe under the root directory of any disk on the local computer.
Run the cmd command and access the directory of userdump.exe. Input
userdump <process name>, and press Enter. E.g.,
. An admaems.dmp file will be generated
under the corresponding directory. This operation backs up the memory data
of admaems.
4. By analyzing the admaems.dmp file, we find that the buffer area for receiving
commands from the background ANSERVER service on the Manager server
is too small. When the data volume in the buffer area crosses the threshold,
the excessive data are discarded. So we modify the parameter in the
configuration file of the Manager server as follows:
ANSERVERRECVBUFFERLEN = 1048576, so as to guarantee that the
memory reading / writing is normal when multiple systems are used.
5. Disable Anm2000 Daemon Service. (The daemon process that is responsible

for monitoring the ANM2000 services. The disabled ANM2000 services will be
started by the daemon process automatically.)
6. Restart the Manager service to validate the modified data.
7. Start the Anm2000 Daemon Service process.
6-28 Version A
Appendix A Signaling Tracing
Instruction
A.1 Overview
A.1.1 Definition
Signaling tracing refers to the operation of tracing specified signaling links when
faults occur in commissioning, provisioning and servicing. Via querying the
contents of the signaling tracing, the maintenance engineers of the project analyze
whether the transmitted or received signaling is correct, thus further find out the
errors in signaling interworking. This operation facilitates the maintenance and
operation personnel to find out, isolate and resolve the problem.
A.1.2 Applicable Situation
The ANM2000 system provides the signaling tracing function of the H.248, MGCP,
and SIP signaling.
Version A B-1
A.1.3 Operation Flow
Start
Enable the signaling tracing

function
Start tracing
End tracing
Check and analyze the

signaling tracing result
Disable the signaling tracing

function
End
Figure A- 1 Flow chart of signaling tracing operation
A-2 Version A
Appendix A Signaling Tracing Instruction
A.1.4 Enabling / Disabling Signal Tracing
Command function
This command is used to enable or disable the signaling tracing function.
Note:
Enabling the signaling tracing function does not affect the user services.
Since the signaling tracing operation occupies the system memory, you
should turn off the signal tracing switch after the signaling tracing
operation is completed, so as to prevent impacting the equipment
performance.
Command access
In the ANM2000 GUI, right-click the HSWA card in the Object Tree pane, and
select Config → Signal Trace from the shortcut menu to open the Signal Trace
window.
Parameter description
Name Meaning Value Range Attribute Configuration Method

Source or destination IP address
of the data packet. Double-click the blank
The data packet whose source or under this item to input
IP — Compulsory
destination IP address is this IP the IP address of the
address will be transmitted to the data packet.
network management server.
The layer 4 source port number
of the data packet.
Double-click to input the
The data packet whose source
L4 Src. Port No. 1 to 65534 Compulsory layer 4 source port
port number is this port number
number.
will be transmitted to the network
management server.
The layer 4 destination port
number of the data packet.
Double-click to input the
The data packet whose
L4 Dst. Port No. 1 to 65534 Compulsory layer 4 destination port
destination port number is this
number.
port number will be transmitted to
the network management server.
Signal tracing enabling switch. Click the pulldown
Enable Status The options include Enable and — Compulsory menu to select an
Disable. enabling status.
Version A A-3
Configuration example
Perform the tracing operation of the signaling packet whose source and destination
port numbers are both 2944 and destination IP address is 192.168.1.1 on the
AN5516-06.
1. Access the ANM2000 GUI, right-click the HSWA card in the Object Tree pane,
and select Config → Signal Trace from the shortcut menu to open the Signal
Trace window.
2. Click the button, input 1 in the Please Input the Rows For Add dialog
box that appears to add one entry.
3. Configure the parameters in turn.
4. Click the button to deliver the configuration to the equipment, as shown in

Figure A-2.
Figure A- 2 The Signal Trace dialog box
A-4 Version A
A.1.5 Signal Trace Window
Access the ANM2000 GUI, click Configuration → Signal Trace in the main menu
and open the Signal Trace window, as shown in Figure A-3.
Menu bar
Toolbar
Pane
Status
bar
Figure A- 3 The Signal Trace window
Menu bar
Menu Option Function

Opens the signaling tracing document saved under the
Open
designated directory.
File Saves the signaling tracing document to the designated
Save
directory.
Exit Quits the Signal Trace window.
Begin Starts the signaling tracing.
Stop Stops the signaling tracing.
Auto Save Configures the automatic saving function of the signaling
Operation
Option tracing document.
Summary
Configures the related parameters of the summary view.
View Option
Version A A-5
Toolbar
Button Function
Opens the signaling tracing document saved under the
designated directory.
Saves the signaling tracing document to the designated
directory.
Starts the signaling tracing.
Ends the signaling tracing.

Configures the automatic saving function of the signaling
tracing document.
Configures the related parameters of the summary view.
Quits the Signal Trace window.
Pane
Area Parameter Description

Serial Number The number of the signaling packet.
The time when the signaling packet is received by the network
Receive Time
management server.
Upper
Source IP The source IP address of the transmitting signaling packet.
pane
Destination IP The destination IP address of the transmitting signaling packet.
Protocol Type Protocol type of the signaling packet.
Summary The summary of the contents in the signaling packet.
Lower
— Displays the original code stream of the signaling packet.
pane
Status bar
Displays the information of the signaling tracing status.
A-6 Version A
A.2 H.248 Signaling Flow Analysis
A.2.1 MG Registers to MGC
The MG (IP address 132.108.95.20) registers to the MGC (IP address

132.108.95.1).
1. The MG sends the ServiceChange message to the MGC for registration.

Below is the signal tracing example:
MEGACO/1 [132.108.95.20]:2944.
// The protocol type is H.248; the version is 1; the IP address of the MG is
132.108.95.20; the protocol port number is 2944.
Transaction=1{Context=-
// The transaction number is 1, the context encapsulated in the transaction is
blank.
{ServiceChange=ROOT{Services{Method=Restart, Reason="902
Warm Boot",Version=1}}}}
// TerminationID of the ServcieChange message is Root. (It means the
ServcieChange command applies to the entire gateway.) The
ServcieChangeMethod is Restart. The ServiceChangeReason is 902. (902
stands for hot start; 901 stands for cold start.)
2. The MGC sends the Reply message informing the success of registration
back to the MG. Below is the signal tracing example:
Version A A-7
[132.108.95.1]:2944.
// The IP address of the MGC is 132.108.95.1, the protocol port number is
2944.
P=1{C=-{SC=ROOT{SV{AD=2944}}}}.
// The MGC receives the registration message from the MG, and replies the
MG with the Reply message informing the success of registration.
3. The MGC sends the Modify message to the MG, asking the MG to check the
off-hook of all users. Below is the signal tracing example:
T=53{C=-
blank.
{MF=a2{E=1{al/of}}}}.
// The MGC sends the Modify message to the MG to check the off-hook of
user a2.
T=54{C=-
blank.
{MF=a1{E=1{al/of}}}}.
// The MGC sends the Modify message to the MG to check the off-hook of
user a1.
4. The MG responds to the Reply message. Below is the signal tracing example:
MEGACO/1 [132.108.95.20]:2944.
Reply=53{Context=-{Modify=a2}}
// The MG responds to the Reply message for checking the off-hook of user
a2.
MEGACO/1 [132.108.95.20]:2944.
Reply=54{Context=-{Modify=a1}}
// The MG responds to the Reply message for checking the off-hook of user
a1.
A-8 Version A
A.2.2 MG Logs out Actively
The MG (IP address 132.108.95.20) applies to the MGC (IP address 132.108.95.1)
for logout actively.
1. The MG sends the ServiceChange message to the MGC for logout. Below is
the signal tracing example:
MEGACO/1 [132.108.95.20]:2944.
blank.
{ServiceChange=ROOT{Services{Method=Forced, Reason="908 MG
Impending Failure"}}}}
// TerminationID of the ServcieChange message is Root. (It means the
ServcieChange command applies to the entire gateway.) The
ServcieChangeMethod is Forced. The ServiceChangeReason is 908 (the
MG will have faults).
2. The MGC sends the Reply message informing the success of logout back to
the MG. Below is the signal tracing example:
[132.108.95.1]:2944.
2944.
P=48{C=-{SC=a1{SV{AD=132.108.95.1}}}}
// The MGC receives the logout message from the MG, and replies the MG
with the Reply message informing the success of logout.
Version A A-9
A.2.3 Take Endpoint out of Service
Take the user a1 of the MG (IP address 132.108.95.20) out of service. The IP
address of the MGC is 132.108.95.1.
1. The MG sends the ServiceChange message to the MGC for logout. Below is
MEGACO/1 [132.108.95.20]:2944.
blank.
{ServiceChange=a1{Services{Method=Graceful, Reason="905
Termination taken out of service"}}}}
// TerminationID of the ServcieChange message is a1. The
ServcieChangeMethod is Graceful. (It means that user a1 will be removed
from service after the preset ServiceChangeDelay time. And Forced means
that user a1 will be removed from service immediately.) The
ServiceChangeReason is 905 (the endpoint is removed from service).
2. The MGC replies with a Reply message. Below is the signal tracing example:
[132.108.95.1]:2944.
2944.
P=11{C= - {SC=a1{SV{AD=132.108.95.1}}}}
// The MGC receives the message requesting taking the endpoint out of
service from the MG, and replies the MG with a Reply message.
A-10 Version A
A.2.4 Restore Endpoint to Service
Restore the user a1 of the MG (IP address 132.108.95.20) to service. The IP

address of the MGC is 132.108.95.1.
1. The MG sends the ServiceChange message to the MGC for registration.

MEGACO/1 [132.108.95.20]:2944.
blank.
{ServiceChange=a1{Services{Method=Restart, Reason="900
Service Restored"}}}}
// TerminationID of the ServcieChange message is a1. The
ServcieChangeMethod is Restart. The ServiceChangeReason is 900
(service restoration).
2. The MGC replies the MG with a Reply message. Below is the signal tracing
example:
[132.108.95.1]:2944.
2944.
P=28{C=-{SC=a1{SV{AD=132.108.95.1}}}}
// The MGC receives the message requesting restoring the endpoint to service
from the MG, and replies the MG with a Reply message.
Version A A-11
A.2.5 Establish a Normal Call
Establish a normal call between user a2 of MG1 (IP address 132.108.95.20) and
user a1 of MG2 (IP address 132.108.95.30). The IP address of the MGC is
132.108.95.1.
1. MG1 detects the off-hook of User1 and reports the off-hook to the MGC via a
Notify message. Below is the signal tracing example:
MEGACO/1 [132.108.95.20]:2944.
// The protocol type is H.248; the version is 1; the IP address of MG1 is
Transaction=11{Context= -
blank.
{Notify=a2{ObservedEvents=1{20000101T00024105:al/of{init=
False}}}}}
// TerminationID in the Notify message is a2. MG1 (gateway of user a2)
detects the off-hook of user a2 and reports it to the MGC.
A-12 Version A
2. The MGC replies MG1 with a Reply message. Below is the signal tracing
example:
[132.108.95.1]:2944.
2944.
P=11{C=-{N=a2}}
// The MGC’s response to the Notify message.
3. The MGC sends a Modify message to MG1. Below is the signal tracing
example:
T=63{C= -
blank.
{MF=a2{E=1{al/on,dd/ce{DigitMap=dialplan0}},SG{cg/dt},DM=
dialplan0{xxxxxxxx}}}}
// TerminationID in the Modify message is a2. The MGC checks the on-hook
(al/on) and the digit collection completion (dd/ce) events. The MGC sends the
digit map (Digitmap) which is xxxxxxxx to MG1 and requests MG1 to play the
dial tone.
4. MG1 replies the MGC with a Reply message. Below is the signal tracing
example:
MEGACO/1
[132.108.95.20]:2944.Reply=63{Context=-{Modify=a2}}
// MG1’s response to the Modify message transmitted from MGC.
5. Below is the signal tracing example: User1 of MG1 dials a number. After MG1
completes the digit collection, it matches the number with the digit map
delivered by the MGC. MG1 reports the number dialed by User1 and the result
of matching to the MGC with a Notify message.
MEGACO/1 [132.108.95.20]:2944.
Version A A-13
Transaction=12{Context= -
blank.
{Notify=a2{ObservedEvents=1{20000101T00024631:dd/ce{ds="8
8880001", Meth=UM}}}..}.}
// User1 of MG1 dials the number 88880001. The MG1 performs the digit
collection according to the digit map delivered by the MGC and determine that
the dialed number perfectly matches the digit map (Meth=UM). MG1 reports
the number dialed by User1 and the result of matching to the MGC with a
Notify message.
example:
[132.108.95.1]:2944.P=12{C=-{N=a2}}
// The MGC’s response to the Notify message transmitted from MG1.
7. The MGC sends an Add message to MG1. Below is the signal tracing
example:
T=64{C=$
// The transaction number is 64. The MGC requests MG1 to create a new
context. Since the context is indefinite, $ is used here.
{A=a2,
// Add user a2 to the new context.
A=${M{L{.v=0.c=IN IP4 $.m=audio $ RTP/AVP

8.a=ptime:20},O{MO=RC,nt/jit=40}}}}}
A-14 Version A
// Add RTP termination of user a2 to the new context. The new RTP
termination is a temporary termination. Since the descriptor of RTP termination
is not settled, $ is used here. v=0 means the SDP protocol version is 0. c=IN
IP4 $ indicates the related information of the RTP termination: The related
network identifier is Internet; the related address type is IPv4; $ means that the
local IP address is unknown currently. m=audio $ RTP/AVP 8 indicates the
media description recommended by the MGC for the new RTP termination.
audio means the media type of the RTP termination is audio; $ means the
media port number of the RTP termination is unknown currently; RTP/AVP is
the transport layer protocol, whose value is related to the address type in the
“c=” field. For IPv4, most of the media traffic streams are transmitted by
RTP/UDP. The following two types of protocols have been defined: RTP/AVP
denotes RTP used under the RTP Profile for Audio and Video Conferences
with Minimal Control running over UDP; udp denotes an unspecified protocol
running over UDP. As to the RTP Profile for Audio and Video Conferences with
Minimal Control, 8 stands for the media payload type. It means that G.711A is
recommended as the RTP stream compression encoding format by the MGC.
a=ptime:20 means the length of time in milliseconds represented by the
media in a packet is 20ms. MO=RC means the RTP mode is ReceiveOnly.
The maximum jitter buffer (nt/jit) is 40ms.
Note:
The mapping correspondences between the RTP payload type number

and the encoding format defined by the H.248 protocol are: G.711U=0;
G.726=2; G.723=4, G.723.1=4; G.711A=8; G.729=18, G.729A=18.
8. MG1 distributes resources for the RTP, and replies the MGC with a Reply
message. Below is the signal tracing example:
MEGACO/1 [132.108.95.20]:2944.
Reply=64{Context=1
// The transaction number is 64. MG1 creates a new context; and the context
ID is 1.
{Add=a2, ...Add=RTP/0
// Confirm that user a2 and its RTP termination is added to the context.
Version A A-15
{Media{.Local{.v=0..c=IN IP4 132.108.95.20..m=audio 4010

RTP/AVP 8..a=ptime:20..}}}}}
// Media descriptor, which indicates that the IP address of the RTP is
132.108.95.20, the RTP port number is 4010, and the compression encoding
mode is G.711A.
9. The MGC sends an Add message to MG2 to create a new context on MG2.
[132.108.95.1]:2944.
2944.
T=65{C=$
// The transaction number is 65. The MGC requests MG2 to create a new
context, which is identified by $.
{A=a1
// Add user a1 in the new context.
{M{O{MO=SR}},
// RTP mode of User2 is configured as SendReceive (MO=SR).
E=1{al/of},
// The MGC detects the off-hook of user a1 (al/of).
A=${M{L{.v=0.c=IN IP4 $.m=audio $ RTP/AVP 8.a=ptime:20..},

// The RTP termination descriptor of user a1. See Step 7 for details.
R{.v=0.c=IN IP4 132.108.95.20.m=audio 4010 RTP/AVP

8.a=ptime:20..},
// The RTP termination descriptor of user a2 (the remote end of user a1). See
Step 7 for details.
O{MO=SR,nt/jit=40}}}}}
// The RTP mode of user a1 is SendReceive, the maximum jitter buffer (nt/jit)
is 40ms.
example:
A-16 Version A
MEGACO/1 [132.108.95.30]:2944.
Reply=65{Context=2
// MG2 replies to the MGC with a Reply message and creates a context,
whose ID is 2.
{Add=a1,...Add=RTP/1{....Media{.Local{.v=0..c=IN IP4
132.108.95.30..m=audio 4000 RTP/AVP 8..a=ptime:20..}}}}}.
// Add user a1 and its RTP to the newly created context 2. The IP address of
RTP is 132.108.95.30; the RTP port number is 4000; and the compression
encoding mode is G.711A.
example:
[132.108.95.1]:2944.
2944.
T=66{C=2
// The transaction number is 66. The ID of the context encapsulated in the
transaction is 2.
{MF=a1{SG{al/ri}}}.
// The MGC sends a Modify message to MG2, requesting MG2 to send the
ring tone to the called party a1 (al/ri).
example:
MEGACO/1
[132.108.95.30]:2944.Reply=66{..Context=2{Modify=a1}.}.
// MG2’s response to the Modify message.
example:
[132.108.95.1]:2944.
Version A A-17

2944.
T=67{C=1
transaction is 1.
{MF=a2{SG{cg/rt}},MF=RTP/0{M{R{.v=0.c=IN IP4
132.108.95.30.m=audio 4000 RTP/AVP 8.a=ptime:20..}}}}}.
// The MGC sends a Modify message to MG1, requesting user a2 to play the
ring back tone as well as report the to MGC that the RTP IP address of user a1
is 132.108.95.30, the RTP port number of user a1 is 4000; and the
compression encoding mode of user a1 is G.711A.
example:
MEGACO/1 [132.108.95.20]:2944.
Reply=67{Context=1
transaction is 1.
{Modify=a2,...Modify=RTP/0{Media{.Local{.v=0..c=IN IP4
132.108.95.20..m=audio 4010 RTP/AVP 8..a=ptime:20..}}}}}
// TerminationID of the Modify message is a2, and the RTP termination
description information of user a2.
15. MG2 detects the off-hook of user a1 and reports the off-hook event to the
MGC with a Notify message. Below is the signal tracing example:
MEGACO/1 [132.108.95.30]:2944.
Transaction=13{Context=2
transaction is 2.
A-18 Version A
{Notify=a1{ObservedEvents=1{20000101T00025542:al/of{init=
False}}}..}.}
// TerminationID of the Notify message is a1. MG2 (gateway of user a1)
detects the off-hook of user a1.
example:
[132.108.95.1]:2944.P=13{C=2{N=a1}}.
example:
T=68{C=2
transaction is 2.
{MF=a1{E=1{al/on,al/fl},SG{}}}}.
// The MGC sends a Modify message to MG2 (gateway of user a1),
requesting MG2 to check the on-hook (al/on) and hook-flash (al/fl) events of
user a1 as well as stop user a1’s ringing (SG{}).
example:
MEGACO/1
[132.108.95.30]:2944.Reply=68{Context=2{.Modify=a1}}
example:
[132.108.95.1]:2944.
2944.
T=69{C=1
transaction is 1.
Version A A-19
{MF=a2{E=1{al/on},SG{}},MF=RTP/0{M{O{MO=SR}}}}}.
// The MGC sends Modify message to MG1 (gateway of user a2), requesting
MG1 to check the on-hook (al/on) event of user a2, stop user a1’s ring back
tone (SG{}), and set the RTP mode of user a2 to SendReceive (MO=SR).
20. MG1 replies the MGC with a Reply message. A normal call is established
between User1 and User2. Below is the signal tracing example:
MEGACO/1
[132.108.95.20]:2944.Reply=69{Context=1{Modify=a2,Modify=
RTP/0}}
A-20 Version A
A.2.6 NOC First Party Release
The call established between user a1 of MG1 (IP address 132.108.95.20) and user
a2 of MG2 (IP address 132.108.95.30) is released. The IP address of the MGC is
132.108.95.1.
1. MG1 detects the off-hook of user a1 and reports the off-hook event to the
MEGACO/1 [132.108.95.20]:2944.
transaction is 5.
{Notify=a1{ObservedEvents=1{20000101T06255847:al/on{init=
False}}}}}
// MG1 (gateway of user a1) sends a Notify message to the MGC, reporting
the on-hook (al/on) event of user a1.
example:
[132.108.95.1]:2944.
Version A A-21

2944.
P=30{C=5{N=a1}}.
example:
T=45{C=6
transaction is 6.
{MF=a2{SG{cg/bt}}}}
// The MGC sends a Modify message to MG2 (gateway of user a2),
requesting MG2 to play the busy tone (cg/bt) to user a2.
example:
MEGACO/1 [132.108.95.30]:2944.
Reply=45{Context=6{Modify=a2}}
// The transaction number is 45. MG2’s response to the Modify message.
5. The MGC sends a Subtract message to MG1, releasing user a1 and its RTP.
[132.108.95.1]:2944.
2944.
T=46{C=5
transaction is 5.
{S=a1,S=RTP/4}}
A-22 Version A
// The MGC sends a Subtract message to MG1 to delete user a1 and its RTP
from context 5.
6. MG1 replies the MGC with a Reply message, releases the resources, and
reports the media stream statistics of calling to the MGC. Below is the signal
tracing example:
MEGACO/1 [132.108.95.20]:2944.
Reply=46{Context=5
transaction is 5.
{Subtract=a1{Statistics{amet/cpc=0,amet/pcslr=0}},
// MG1 replies to the Subtract message. It releases user a1 and reports the
statistics of user a1 to the MGC. The current pulse count (cpc) is 0; the pulse
count since last report (pcslr) is 0.
Subtract=RTP/4{Statistics{nt/or=183065, nt/os=172000,
rtp/delay=0, rtp/jit=13, rtp/pl=0, rtp/pr=1169,
rtp/ps=1075}}}}
// MG1 replies to the Subtract message. It releases the RTP of user a1 and
reports the RTP statistics of user a1 to the MGC. The received byte number is
183065 (nt/or=183065); the transmitted byte number is 172000
(nt/os=172000); the average delay is 0 (rtp/delay=0); the jitter is 13ms
(rtp/jit=13); the packet loss rate is 0 (rtp/pl=0); the received packet number is
1169 (rtp/pr=1169) and the transmitted packet number is 1075 (rtp/ps=1075).
example:
[132.108.95.1]:2944.
2944.
T=47{C=-
blank.
Version A A-23
{MF=a1{E=1{al/of}}}}
// The MGC sends a Modify message to MG1, requesting MG1 to check the
off-hook event (al/of) of user a1.
example:
MEGACO/1
9. MG2 detects the on-hook of user a2 and reports the on-hook event to the
MEGACO/1 [132.108.95.30]:2944.
transaction is 6.
{Notify=a2{ObservedEvents=1{20000101T06260445:al/on{init=
False}}}}}
// MG2 (gateway of user a2) sends a Notify message to the MGC, reporting
the on-hook (al/on) event of user a2.
example:
[132.108.95.1]:2944.P=31{C=6{N=a2}}
11. The MGC sends a Subtract message to MG2, releasing user a2 and its RTP.
[132.108.95.1]:2944.
2944.
A-24 Version A
T=48{C=6
transaction is 6.
{S=a2,S=RTP/5}}
// The MGC sends a Subtract message to MG2 to delete user a2 and its RTP
from context 6.
12. MG2 replies the MGC with a Reply message, releases the resources, and
reports the media stream statistics of calling to the MGC. Below is the signal
tracing example:
MEGACO/1 [132.108.95.30]:2944.
Reply=48{Context=6
transaction is 6.
{Subtract=a2{Statistics{amet/cpc=0, amet/pcslr=0}},
// MG2 replies to the Subtract message. It releases user a2 and reports the
statistics of user a2 to the MGC. The current pulse count (cpc) is 0; the pulse
count since last report (pcslr) is 0.
Subtract=RTP/5{Statistics{nt/or=151360, nt/os=237946,
rtp/delay=0, rtp/jit=7, rtp/pl=0, rtp/pr=946,
rtp/ps=1513}}}}
// MG2 replies to the Subtract message. It releases the RTP of user a2 and
reports the RTP statistics of user a2 to the MGC. The received byte number is
151360 (nt/or=151360); the transmitted byte number is 237946
(nt/os=237946); the average delay is 0 (rtp/delay=0); the jitter is 7ms
(rtp/jit=7); the packet loss rate is 0 (rtp/pl=0); the received packet number is
946 (rtp/pr=946) and the transmitted packet number is 1513 (rtp/ps=1513).
example:
[132.108.95.1]:2944.
Version A A-25

2944.
T=49{C=-
blank.
{MF=a2{E=1{al/of}}}}
// The MGC sends a Modify message to MG2, requesting MG2 to check the
off-hook event (al/of) of user a2.
example:
MEGACO/1
A-26 Version A
A.3 SIP Signaling Flow Analysis
A.3.1 SIP User Terminal Registration
SIP user1 (telephone number 77770001) registers to the proxy server (IP address
132.108.95.1).
1. Before the first call attempt, SIP user1 should send the Register registration
request to the proxy server. Below is the signal tracing example:
REGISTER sip:132.108.95.1 SIP/2.0..

// Start line of the registration request. It means that the SIP user is initiating a
registration to the proxy server whose IP address is 132.108.95.1. The SIP
version number is 2.0.
From:<sip:77770001@132.108.95.1>;
tag=10095010-505f6c84-13c4-386d43b7-7951437d-386d43b7..
// The “From” header field. This field indicates the logical identity of the initiator
of the request. The above field shows that the request message is initiated by
the SIP user1 (telephone number 77770001) of the proxy server (IP address
132.108.95.1).
To: <sip:77770001@132.108.95.1>..
// The “To” header field. This field shows address to receive the request
message. Here it refers to the IP address of the proxy server.
Call-ID:
1009c068-505f6c84-13c4-386d43b7-2e101815-386d43b7..
Version A A-27
// The “Call-ID” header field. This field is a globally unique identifier identifying
a particular invitation.
CSeq: 5 REGISTER..
// The “CSeq” header field. This field is used to match a response to the
request it references. It consists of a sequence number and a method. The
“CSeq” header field serves to order transactions within a dialog, to provide a
means to uniquely identify transactions, and to differentiate between new
requests and request retransmissions.
Via: SIP/2.0/UDP132.108.95.80:5060;
branch=z9hG4bK-386d476a-6adef794-6dcf9c84..
// The “Via” header field indicates the path taken by the request so far and
indicates the path that should be followed in routing responses. SIP/2.0/UDP
indicates the transmission protocol: The protocol is SIP, the version is 2.0, the
transport layer is UDP, and the IP address of the SIP user that sends the
request message is 132.108.95.80.
Max-Forwards: 70..
// The “Max-Forwards” header field. This field serves to limit the number of
hops a request can transit on the way to its destination. The default value is
70.
Supported: 100rel,replaces,timer..
// The “Supported” header field enumerates all the extensions supported by
the UA. If empty, it means that no extensions are supported.
Contact: <sip:77770001@132.108.95.80:5060>..
// The “Contact” header field. In a registration request, this field specifies the
location reachable from the user. Here it means that the SIP user’s current IP
address is 132.108.95.80 and the telephone number is 77770001.
Expires: 3600..
// The “Expires” header field gives the relative time after which the message (or
content) expires. Here it means this registration request will expire after 3600
seconds.
Content-Length: 0........
// The “Content-Length” header field. This field means the length of the
message body is 0. This field has no dialog description.
A-28 Version A
2. The proxy server sends a response message 100 Trying to SIP user1. The
message means that the proxy server is processing the request. Below is the
signal tracing example:
SIP/2.0 100 Trying..

// Start line of the 100 Trying message.
Via: SIP/2.0/UDP
132.108.95.80:5060;branch=z9hG4bK-386d476a-6adef794-6dcf9
c84..
// The “Via” header field. Here 132.108.95.80 is the IP address of the SIP user
that sends the request message.
From:<sip:77770001@132.108.95.1>;tag=10095010-505f6c84-13
c4-386d43b7-7951437d-386d43b7..
// The “From” header field. This field indicates the logical identity of the initiator
of the request.
To: <sip:77770001@132.108.95.1>..
message.
Call-ID:
1009c068-505f6c84-13c4-386d43b7-2e101815-386d43b7..
// The “Call-ID” header field. This field uniquely identifies the invitation sent
from SIP user1, and it is globally unique.
CSeq: 5 REGISTER..
// The “CSeq” header field, which is used to match a response to the request it
references.
Content-Length: 0........
request’s message body is 0.
3. The proxy server sends a response message 200 OK to SIP user1, which
means the registration is successful. Below is the signal tracing example:
SIP/2.0 200 OK..

// Start line of the 200 OK message.
Version A A-29
Via: SIP/2.0/UDP
132.108.95.80:5060;branch=z9hG4bK-386d476a-6adef794-6dcf9
c84..
// The “Via” header field. Here 132.108.95.80 is the IP address of the SIP user
that sends the request message.
From:<sip:77770001@132.108.95.1>;tag=10095010-505f6c84-13
c4-386d43b7-7951437d-386d43b7..
// The “From” header field. This field contains the logical identifier of the
request initiator.
To:<sip:77770001@132.108.95.1>;tag=1282621041031-81290607
5..
message.
Call-ID:
1009c068-505f6c84-13c4-386d43b7-2e101815-386d43b7..
// The “Call-ID” header field. This field uniquely identifies the invitation sent
from SIP user1, and it is globally unique.
CSeq: 5 REGISTER..
// The “CSeq” header field, which is used to match a response to the request it
references.
Contact:
<sip:77770001@132.108.95.80:5060>;expires=3600;q=1.0..
// The “Contact” header field. In a registration request, this field specifies the
location reachable from the user.
Content-Length: 0.....
request’s message body is 0.
A-30 Version A
A.3.2 SIP User Terminal Logout
SIP user1 (telephone number 77770001) applies to the proxy server (IP address
132.108.95.1) for logout.
1. SIP user1 sends a Register message to the proxy server requesting logout. In
the logout message, the “Expires” header field is 0. Below is the signal tracing
example:
REGISTER sip:132.108.95.1 SIP/2.0..From:

<sip:77770001@132.108.95.1>;tag=10095010-505f6c84-13c4-38
6d43b7-7951437d-386d43b7..To:
<sip:77770001@132.108.95.1>..Call-ID:
1009c068-505f6c84-13c4-386d43b7-2e101815-386d43b7..CSeq: 4
REGISTER..Via: SIP/2.0/UDP
132.108.95.80:5060;branch=z9hG4bK-386d4757-6adeabf0-6b4d1
12f..Max-Forwards: 70..Supported:
100rel,replaces,timer..Contact:
<sip:77770001@132.108.95.80:5060>..Expires:
0..Content-Length: 0........
Version A A-31
SIP/2.0 100 Trying..Via: SIP/2.0/UDP

12f..From:
<sip:77770001@132.108.95.1>;tag=10095010-505f6c84-13c4-38
6d43b7-7951437d-386d43b7..To:
<sip:77770001@132.108.95.1>..Call-ID:
1009c068-505f6c84-13c4-386d43b7-2e101815-386d43b7..CSeq: 4
REGISTER..Server: Brekeke OnDO SIP Server
(rev.172)..Content-Length: 0....H...
3. The proxy server sends a response message 200 OK to SIP user1, and clears
the data related to SIP user1 in the database. Below is the signal tracing
example:
SIP/2.0 200 OK..Via: SIP/2.0/UDP

12f..From:
<sip:77770001@132.108.95.1>;tag=10095010-505f6c84-13c4-38
6d43b7-7951437d-386d43b7..To:
<sip:77770001@132.108.95.1>;tag=1282621021671-931396014..
Call-ID:
1009c068-505f6c84-13c4-386d43b7-2e101815-386d43b7..CSeq: 4
REGISTER..Contact:
<sip:77770001@132.108.95.80:5060>;expires=0;q=1.0..Server:
Brekeke OnDO SIP Server (rev.172)..Content-Length: 0.....
A-32 Version A
A.3.3 Establish a Normal Call
Establish a normal call between SIP user1 (telephone number 77770002) and SIP
user2 (telephone number 77770001) of the proxy server (IP address
132.108.95.1).
1. The SIP user1 initiates an Invite request to the proxy server. The “Allow” field
of the request message lists the supporting methods of the SIP user terminal,
including Invite, ACK and Cancel; the “Content-Type” header field identifies
the media type of the message body transmitted to the opposite party. Below is
Version A A-33
INVITE sip:77770001@132.108.95.1 SIP/2.0..From:

<sip:77770002@132.108.95.1>;tag=10097110-505f6c84-13c4-38
6d48df-eef7cc7-386d48df..To:
<sip:77770001@132.108.95.1>..Call-ID:
1009af80-505f6c84-13c4-386d48df-23f0cd46-386d48df@132.108
.95.1..CSeq: 1 INVITE..Via: SIP/2.0/UDP
132.108.95.80:5060;branch=z9hG4bK-386d48df-6ae4a798-1ead2
944..Allow:
INVITE,ACK,CANCEL,BYE,REGISTER,REFER,NOTIFY,PRACK,CANCEL,
SUBSCRIBE,OPTIONS,INFO,UPDATE..Max-Forwards: 70..Supported:
<sip:77770002@132.108.95.80:5060>..Content-Type:
application/SDP..Content-Length: 226....v=0..o=77770002
946686175 946686175 IN IP4 132.108.95.80..s=-..c=IN IP4
132.108.95.80..t=0 0..m=audio 4010 RTP/AVP 8 0 18
4..a=rtpmap:8 PCMA/8000..a=rtpmap:0 PCMU/8000..a=rtpmap:18
G729/8000..a=rtpmap:4 G723/8000..a=ptime:20..*b..

944..From:
<sip:77770002@132.108.95.1>;tag=10097110-505f6c84-13c4-38
<sip:77770001@132.108.95.1>..Call-ID:
1009af80-505f6c84-13c4-386d48df-23f0cd46-386d48df@132.108
.95.1..CSeq: 1 INVITE..Server: Brekeke OnDO SIP Server
(rev.172)..Content-Length: 0....7[..
3. After confirming the SIP user1 has passed the authentication, the proxy server
forwards the Invite request to the terminal user indicated by the “To” header
field of the Invite message. Below is the signal tracing example:
A-34 Version A
INVITE sip:77770001@132.108.95.80:5060 SIP/2.0..From:

<sip:77770002@132.108.95.1>;tag=10097110-505f6c84-13c4-38
<sip:77770001@132.108.95.1:5060>..Call-ID:
1009af80-505f6c84-13c4-386d48df-23f0cd46-386d48df@132.108
132.108.95.1:5060;rport;branch=z9hG4bKccd69d69154f8bac.1.
.Via: SIP/2.0/UDP
944..Allow:
<sip:77770002@132.108.95.1:5060>..Record-Route:
<sip:132.108.95.1:5060;lr>..Content-Type:
application/sdp..Content-Length: 226....v=0..o=77770002
946686175 946686175 IN IP4 132.108.95.80..s=-..c=IN IP4
132.108.95.80..t=0 0..m=audio 4010 RTP/AVP 8 0 18
G729/8000..a=rtpmap:4 G723/8000..a=ptime:20......
4. The SIP user2 sends a response message 100 Trying to the proxy server.
SIP/2.0 100 Trying..From:

<sip:77770002@132.108.95.1>;tag=10097110-505f6c84-13c4-38
<sip:77770001@132.108.95.1:5060>..Call-ID:
1009af80-505f6c84-13c4-386d48df-23f0cd46-386d48df@132.108
132.108.95.1:5060;rport=5060;branch=z9hG4bKccd69d69154f8b
ac.1..Via: SIP/2.0/UDP
944.. Supported: 100rel,replaces,timer..Contact:
<sip:77770001@132.108.95.80:5060>..Content-Length:
0....>T..
5. The SIP user2 rings and sends the ringing message 180 Ringing to the proxy
server. Below is the signal tracing example:
Version A A-35
SIP/2.0 180 Ringing..From:

<sip:77770002@132.108.95.1>;tag=10097110-505f6c84-13c4-38
<sip:77770001@132.108.95.1:5060>;tag=10097950-505f6c84-13
c4-386d48df-2c64722-386d48df..Call-ID:
1009af80-505f6c84-13c4-386d48df-23f0cd46-386d48df@132.108
944..Supported: 100rel,replaces,timer..Contact:
<sip:77770001@132.108.95.80:5060>..Record-Route:
<sip:132.108.95.1:5060;lr>..Content-Length: 0........
6. The proxy server forwards the ringing message to SIP user1. Below is the
SIP/2.0 180 Ringing..From:

<sip:77770002@132.108.95.1>;tag=10097110-505f6c84-13c4-38
<sip:77770001@132.108.95.1>;tag=10097950-505f6c84-13c4-38
6d48df-2c64722-386d48df..Call-ID:
1009af80-505f6c84-13c4-386d48df-23f0cd46-386d48df@132.108
<sip:77770001@132.108.95.1:5060>..Record-Route:
7. The SIP user2 picks up the telephone and sends a response message 200 OK
indicating the success of connection to the proxy server. SDP description is
included in the message. Below is the signal tracing example:
A-36 Version A
SIP/2.0 200 OK..From:

<sip:77770002@132.108.95.1>;tag=10097110-505f6c84-13c4-38
<sip:77770001@132.108.95.1:5060>;tag=10097950-505f6c84-13
c4-386d48df-2c64722-386d48df..Call-ID:
1009af80-505f6c84-13c4-386d48df-23f0cd46-386d48df@132.108
.95.1..CSeq: 1 INVITE..Allow:
SUBSCRIBE,OPTIONS,INFO,UPDATE..Via: SIP/2.0/UDP
<sip:77770001@132.108.95.80:5060>..Record-Route:
946686176 946686176 IN IP4 132.108.95.80..s=-..c=IN IP4
132.108.95.80..t=0 0..m=audio 4000 RTP/AVP 8 0 18
G729/8000..a=rtpmap:4
G723/8000..a=ptime:20..a=sendrecv...d..
8. The proxy server forwards the connection success message to SIP user1.
Version A A-37

<sip:77770002@132.108.95.1>;tag=10097110-505f6c84-13c4-38
<sip:77770001@132.108.95.1>;tag=10097950-505f6c84-13c4-38
6d48df-2c64722-386d48df..Call-ID:
1009af80-505f6c84-13c4-386d48df-23f0cd46-386d48df@132.108
.95.1..CSeq: 1 INVITE..Allow:
SUBSCRIBE,OPTIONS,INFO,UPDATE..Via: SIP/2.0/UDP
<sip:77770001@132.108.95.1:5060>..Record-Route:
946686176 946686176 IN IP4 132.108.95.80..s=-..c=IN IP4
132.108.95.80..t=0 0..m=audio 4000 RTP/AVP 8 0 18
G729/8000..a=rtpmap:4
G723/8000..a=ptime:20..a=sendrecv..;...
9. After the SIP user1 receives the connection success message, it sends an
ACK acknowledgement message to the proxy server. Below is the signal
tracing example:
ACK sip:77770001@132.108.95.1:5060 SIP/2.0..From:

<sip:77770002@132.108.95.1>;tag=10097110-505f6c84-13c4-38
<sip:77770001@132.108.95.1>;tag=10097950-505f6c84-13c4-38
6d48df-2c64722-386d48df..Call-ID:
1009af80-505f6c84-13c4-386d48df-23f0cd46-386d48df@132.108
.95.1..CSeq: 1 ACK..Via: SIP/2.0/UDP
132.108.95.80:5060;branch=z9hG4bK-386d48e1-6ae4b05e-5f47e
4cc..Max-Forwards: 70..Contact:
<sip:77770002@132.108.95.80:5060>..Route:
<sip:132.108.95.1:5060;lr>..Content-Length: 0....D...
10. The proxy server forwards the ACK acknowledgement message to SIP user2.
A-38 Version A
ACK sip:77770001@132.108.95.80:5060 SIP/2.0..From:

<sip:77770002@132.108.95.1>;tag=10097110-505f6c84-13c4-38
<sip:77770001@132.108.95.1:5060>;tag=10097950-505f6c84-13
c4-386d48df-2c64722-386d48df..Call-ID:
1009af80-505f6c84-13c4-386d48df-23f0cd46-386d48df@132.108
132.108.95.1:5060;rport;branch=z9hG4bKfcdef8b04d989bac.1.
.Via: SIP/2.0/UDP
132.108.95.80:5060;branch=z9hG4bK-386d48e1-6ae4b05e-5f47e
4cc..Max-Forwards: 69..Contact:
<sip:77770002@132.108.95.1:5060>..Record-Route:
11. The communication connection is established between the calling and called
users. A normal dialog starts.
Version A A-39
A.3.4 Perform a Normal Call Release
The SIP user1 (telephone number 77770002) hooks on and releases the
connection.
1. After the dialog is ended, the calling party SIP user1 hooks on and sends a
Bye message to the proxy server. Below is the signal tracing example:
BYE sip:77770001@132.108.95.1:5060 SIP/2.0..From:

<sip:77770002@132.108.95.1>;tag=10097110-505f6c84-13c4-38
<sip:77770001@132.108.95.1>;tag=10097950-505f6c84-13c4-38
6d48df-2c64722-386d48df..Call-ID:
1009af80-505f6c84-13c4-386d48df-23f0cd46-386d48df@132.108
.95.1..CSeq: 2 BYE..Via: SIP/2.0/UDP
132.108.95.80:5060;branch=z9hG4bK-386d48e2-6ae4b61c-35766
4e0..Max-Forwards: 70..Supported:
100rel,replaces,timer..Route:
<sip:132.108.95.1:5060;lr>..Content-Length: 0....P...
2. The proxy server transmits the Bye message to the called party SIP user2.
A-40 Version A
BYE sip:77770001@132.108.95.80:5060 SIP/2.0..From:

<sip:77770002@132.108.95.1>;tag=10097110-505f6c84-13c4-38
<sip:77770001@132.108.95.1:5060>;tag=10097950-505f6c84-13
c4-386d48df-2c64722-386d48df..Call-ID:
1009af80-505f6c84-13c4-386d48df-23f0cd46-386d48df@132.108
132.108.95.1:5060;rport;branch=z9hG4bK954f3aac5d14dbac.1.
.Via: SIP/2.0/UDP
4e0..Max-Forwards: 69..Supported:
100rel,replaces,timer..Record-Route:
3. SIP user2 sends a response message 200 OK to the proxy server confirming
the on-hook. Below is the signal tracing example:

<sip:77770002@132.108.95.1>;tag=10097110-505f6c84-13c4-38
<sip:77770001@132.108.95.1:5060>;tag=10097950-505f6c84-13
c4-386d48df-2c64722-386d48df..Call-ID:
1009af80-505f6c84-13c4-386d48df-23f0cd46-386d48df@132.108
132.108.95.1:5060;rport=5060;branch=z9hG4bK954f3aac5d14db
4e0..Supported: 100rel,replaces,timer..Content-Length:
0.....E..
4. The proxy server forwards the response message to SIP user1. Below is the
Version A A-41

<sip:77770002@132.108.95.1>;tag=10097110-505f6c84-13c4-38
<sip:77770001@132.108.95.1>;tag=10097950-505f6c84-13c4-38
6d48df-2c64722-386d48df..Call-ID:
1009af80-505f6c84-13c4-386d48df-23f0cd46-386d48df@132.108
4e0..Supported: 100rel,replaces,timer..Content-Length:
0.....]..
A-42 Version A
A.3.5 Call Released when the Called Party Busy
SIP user1 (telephone number 77770001) of the proxy server (IP address
132.108.95.1) calls SIP user2 (telephone number 77770002). Since SIP user2 is
busy, SIP user1 releases the connection.
1. The SIP user1 initiates an Invite request to the proxy server. SIP user1
(77770001@132.108.95.1) of the proxy server (IP address 132.108.95.1) calls
SIP user2 (77770002@132.108.95.1). Below is the signal tracing example:
INVITE sip:77770002@132.108.95.1 SIP/2.0..From:

<sip:77770001@132.108.95.1>;tag=10097950-505f6c84-13c4-38
6d450f-248cde39-386d450f..To:
<sip:77770002@132.108.95.1>..Call-ID:
10098f00-505f6c84-13c4-386d450f-5756a230-386d450f@132.108
132.108.95.80:5060;branch=z9hG4bK-386d450f-6ad5c37a-168c6
2ce..Allow:
<sip:77770001@132.108.95.80:5060>..Content-Type:
946685199 946685199 IN IP4 132.108.95.80..s=-..c=IN IP4
132.108.95.80..t=0 0..m=audio 4000 RTP/AVP 8 0 18
Version A A-43
2. The proxy server sends a response message 100 Trying to SIP user1
indicating that the request is in process. Below is the signal tracing example:

2ce..From:
<sip:77770001@132.108.95.1>;tag=10097950-505f6c84-13c4-38
6d450f-248cde39-386d450f..To:
<sip:77770002@132.108.95.1>..Call-ID:
10098f00-505f6c84-13c4-386d450f-5756a230-386d450f@132.108
.95.1..CSeq: 1 INVITE..Server: Brekeke OnDO SIP Server
(rev.172)..Content-Length: 0........
3. After receiving the request message, the proxy server forwards the Invite
request message to SIP user2. Below is the signal tracing example:
INVITE sip:77770002@132.108.95.80:5060 SIP/2.0..From:

<sip:77770001@132.108.95.1>;tag=10097950-505f6c84-13c4-38
6d450f-248cde39-386d450f..To:
<sip:77770002@132.108.95.1:5060>..Call-ID:
10098f00-505f6c84-13c4-386d450f-5756a230-386d450f@132.108
132.108.95.1:5060;rport;branch=z9hG4bKf527779acf7c6bac.1.
.Via: SIP/2.0/UDP
2ce..Allow:
<sip:77770001@132.108.95.1:5060>..Record-Route:
946685199 946685199 IN IP4 132.108.95.80..s=-..c=IN IP4
132.108.95.80..t=0 0..m=audio 4000 RTP/AVP 8 0 18
4. The calling request message is sent to SIP user2. The called party is busy, so
SIP user2 transmits a called party busy message 486 Busy Here to the proxy
server. Below is the signal tracing example:
A-44 Version A
SIP/2.0 486 Busy Here..From:

<sip:77770001@132.108.95.1>;tag=10097950-505f6c84-13c4-38
6d450f-248cde39-386d450f..To:
<sip:77770002@132.108.95.1:5060>;tag=10097ab0-505f6c84-13
c4-386d450f-5b608f4c-386d450f..Call-ID:
10098f00-505f6c84-13c4-386d450f-5756a230-386d450f@132.108
132.108.95.1:5060;rport=5060;branch=z9hG4bKf527779acf7c6b
2ce..Supported: 100rel,replaces,timer..Content-Length:
0....X...
5. The proxy server forwards the called party busy response to SIP user1. Below
is the signal tracing example:
SIP/2.0 486 Busy Here..From:

<sip:77770001@132.108.95.1>;tag=10097950-505f6c84-13c4-38
6d450f-248cde39-386d450f..To:
<sip:77770002@132.108.95.1>;tag=10097ab0-505f6c84-13c4-38
6d450f-5b608f4c-386d450f..Call-ID:
10098f00-505f6c84-13c4-386d450f-5756a230-386d450f@132.108
2ce..Supported: 100rel,replaces,timer..Content-Length:
0....uB..
6. After SIP user1 receives the message, it sends an ACK acknowledgement

message to the proxy server. Below is the signal tracing example:
ACK sip:77770002@132.108.95.1 SIP/2.0..From:

<sip:77770001@132.108.95.1>;tag=10097950-505f6c84-13c4-38
6d450f-248cde39-386d450f..To:
<sip:77770002@132.108.95.1>;tag=10097ab0-505f6c84-13c4-38
6d450f-5b608f4c-386d450f..Call-ID:
10098f00-505f6c84-13c4-386d450f-5756a230-386d450f@132.108
2ce..Max-Forwards: 70..Contact:
<sip:77770001@132.108.95.80:5060>..Content-Length:
0....J...
Version A A-45
7. The proxy server forwards the ACK acknowledgement message to SIP user2,
and this call is released. Below is the signal tracing example:
ACK sip:77770002@132.108.95.80:5060 SIP/2.0..From:

<sip:77770001@132.108.95.1>;tag=10097950-505f6c84-13c4-38
6d450f-248cde39-386d450f..To:
<sip:77770002@132.108.95.1:5060>;tag=10097ab0-505f6c84-13
c4-386d450f-5b608f4c-386d450f..Call-ID:
10098f00-505f6c84-13c4-386d450f-5756a230-386d450f@132.108
132.108.95.1:5060;rport;branch=z9hG4bKf527779acf7c6bac.1.
.Via: SIP/2.0/UDP
2ce..Max-Forwards: 69..Contact:
<sip:77770001@132.108.95.1:5060>..Record-Route:
<sip:132.108.95.1:5060;lr>..Content-Length: 0....e...
A-46 Version A
Appendix B Abbreviations
BRAS Broadband Remote Access Serve
FE Fast Ethernet
GE Gigabit Ethernet
IAD Integrated Access Device
IP Internet Protocol
MGC Media Gateway Controller
MGCP Media Gateway Control Protocol
ONU Optical Network Unit
OLT Optical Line Terminal
PON Passive Optical Network
PPPoE PPP over Ethernet
RTP Real time Transport Protocol
STB Set Top Box
VLAN Virtual LAN
Version A B-1
Product Documentation Customer Satisfaction Survey
Thank you for reading and using the product documentation provided by FiberHome. Please take a
moment to complete this survey. Your answers will help us to improve the documentation and better
suit your needs. Your responses will be confidential and given serious consideration. The personal
information requested is used for no other purposes than to respond to your feedback.
Name
Phone Number
Email Address
Company
To help us better understand your needs, please focus your answers on a single documentation or a
complete documentation set.
Documentation Name
Code and Version
Usage of the product documentation:

1. How often do you use the documentation?
 Frequently  Rarely  Never  Other (please specify)
2. When do you use the documentation?

 in starting up a project  in installing the product  in daily maintenance  in
troubleshooting  Other (please specify)
3. What is the percentage of the operations on the product for which you can get instruction from the
documentation?
 100%  80%  50%  0%  Other (please specify)
4. Are you satisfied with the promptness with which we update the documentation?
 Satisfied  Unsatisfied (your advice)
5. Which documentation form do you prefer?

 Print edition  Electronic edition  Other (please specify)
Quality of the product documentation:
1. Is the information organized and presented clearly?

 Very  Somewhat  Not at all (your advice)
2. How do you like the language style of the documentation?

 Good  Normal  Poor (please specify)
3. Are any contents in the documentation inconsistent with the product?

4. Is the information complete in the documentation?
 Yes
 No (please specify)
5. Are the product working principles and the relevant technologies covered in the documentation
sufficient for you to get known and use the product?
 Yes
 No (please specify)
6. Can you successfully implement a task following the operation steps given in the documentation?
 Yes (please give an example)
 No (please specify the reason)
7. Which parts of the documentation are you satisfied with?
8. Which parts of the documentation are you unsatisfied with? Why?
9. What is your opinion on the Figures in the documentation?
 Beautiful  Unbeautiful (your advice)
 Practical  Unpractical (your advice)
10. What is your opinion on the layout of the documentation?
 Beautiful  Unbeautiful (your advice)
11. Thinking of the documentations you have ever read offered by other companies, how would you
compare our documentation to them?
Product documentations from other companies:
Satisfied (please specify)
Unsatisfied (please specify)
12. Additional comments about our documentation or suggestions on how we can improve:
Thank you for your assistance. Please fax or send the completed survey to us at the contact information
included in the documentation. If you have any questions or concerns about this survey please email at
edit@fiberhome.com.cn.

Problemas Fiberhome

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

Problemas Fiberhome

Uploaded by

Copyright:

Available Formats

AN5516-06

Optical Line Terminal Equipment

FiberHome Telecommunication Technologies Co., Ltd.

We appreciate your business. Your satisfaction is our

goal. We will provide you with comprehensive technical

support and after-sales service. Please contact your

local sales representative, service representative or

distributor for any help needed at the contact information

Fiberhome Telecommunication Technologies Co., Ltd.

Address: No. 5 Dongxin Rd., Hongshan Dist., Wuhan, China

are trademarks of FiberHome Telecommunication Technologies Co., Ltd.

All rights reserved

This manual is intended for the following readers:

 Planning and designing engineers

 Operation and maintenance engineers

To utilize this manual, these prerequisite skills are necessary:

 NGN voice technology

 Ethernet switch technology

 Computer network technology

Symbol Convention Description

Note Important features or operation guide.

Possible injury to persons or systems, or cause traffic

Warning May cause severe bodily injuries.

1 General ........................................................................................................ 1-1

1.1 Requirement for Maintenance Engineers ....................................... 1-2

2 Troubleshooting of System Common Faults................................................. 2-1

2.1 Card Fault ...................................................................................... 2-2

3 Troubleshooting of Data Service Faults........................................................ 3-1

3.1 Background Knowledge ................................................................. 3-2

4 Troubleshooting of Voice Service Faults ...................................................... 4-1

4.1 Background Knowledge ................................................................. 4-2

5 Troubleshooting Multicast Service Faults ..................................................... 5-1

5.1 Background Knowledge ................................................................. 5-2

6 Fault Cases .................................................................................................. 6-1

6.1 System Fault Case ......................................................................... 6-2

Appendix A Signaling Tracing Instruction ..........................................................A-1

A.1 Overview ........................................................................................A-1

Figure 1-1 General Flow of Troubleshooting of the AN5516-06 ...................... 1-4

Table 1-1 Relationship of the AN5516-06 Services and Main Peripheral

This chapter introduces the requirements for maintenance engineers, principles of

This chapter mainly contains the following items:

Requirement for Maintenance Engineers

General Flow of Troubleshooting

Routine Methods of Fault Analysis and Isolation

How to Obtain Technical Support

1.1 Requirement for Maintenance Engineers

1.1.1 Theoretical Knowledge

Maintenance engineers should be familiar with the following theoretical knowledge:

 Related protocols of multicast service;

 Theory of voice service;

 Fundamental principles of EPON / GPON technologies;

 MGCP, H.248 and SIP protocols;

 PBX technologies and softswitching technologies.

1.1.2 Equipment Composition and Network

Maintenance engineers should understand the system composition, service

 Hardware configuration of the AN5516-06;

 Functions of each card and interface of the AN5516-06;

 Network of the AN5516-06;

 Physical connection of internal and external cables of the AN5516-06;

 Network data planning and configuration of the AN5516-06.

1.1.3 Equipment Operation

Maintenance engineers should be knowledgeable of the following basic operations:

 Basic operation of equipment such as part replacement, cleaning etc.;