Professional Documents
Culture Documents
Maintenance Manual-Troubleshooting Volume
Maintenance Manual-Troubleshooting Volume
1-1
1.1 Requirements for Maintenance Personnel ............................................. 1-1
1.2 Troubleshooting Procedures .................................................................. 1-2
1.2.1 Fault Information Collection-Collecting as Much Original
Information of a Fault as Possible ........................................................... 1-2
1.2.2 Fault Judgment-Determining the Scope and Type of a Fault ........ 1-3
1.2.3 Fault Location-Finding out the Specific Cause of a Fault .............. 1-4
1.2.4 Fault Removing-Removing a Fault and Restoring the System
by Suitable Methods or Steps ................................................................. 1-4
1.3 Basic Methods ........................................................................................ 1-4
1.3.1 Analyzing Original Information ....................................................... 1-4
1.3.2 Analyzing Alarm Information .......................................................... 1-5
1.3.3 Analyzing Indicator Status ............................................................. 1-6
1.3.4 Making Calls to Test ...................................................................... 1-9
1.3.5 Using Apparatus & Meter ............................................................... 1-9
1.3.6 Analyzing Traffic Statistics ............................................................. 1-10
1.3.7 Tracing Connection and Signaling ................................................. 1-11
1.3.8 Testing and Looping Back ............................................................. 1-12
1.3.9 Comparing and Replacing ............................................................. 1-13
1.3.10 Switching over and Resetting ...................................................... 1-14
1.3.11 Contacting Technical Support Engineers ..................................... 1-15
Chapter 2 Subscriber System ......................................................................... 2-1
2.1 Overview ................................................................................................ 2-1
2.1.1 Common Faults.............................................................................. 2-1
2.1.2 Common Fault Causes .................................................................. 2-2
2.2 Background Knowledge ......................................................................... 2-4
2.2.1 Basic Calls ..................................................................................... 2-4
2.2.2 Requirements................................................................................. 2-6
2.3 Fault Location ......................................................................................... 2-8
2.3.1 No Feed for the Telephone ............................................................ 2-8
2.3.2 Abnormal Ringing .......................................................................... 2-10
2.3.3 Abnormal Call-in ............................................................................ 2-14
2.3.4 Abnormal Call-out .......................................................................... 2-16
2.3.5 Abnormal Connection .................................................................... 2-20
2.3.6 Abnormal Conversation ................................................................. 2-20
2.3.7 Subscribers of a Half or an Entire Frame Getting Faulty ............... 2-27
2.3.8 Intra-Module Traffic Totally Blocked .............................................. 2-30
2.3.9 Inter-Module Traffic Totally Blocked .............................................. 2-32
2.3.10 Global Traffic Totally Blocked ...................................................... 2-33
2.3.11 Abnormal Intra-Module Connection ............................................. 2-36
2.3.12 Abnormal Inter-Module Connection ............................................. 2-40
2.3.13 Abnormal Inter-Office Connection................................................ 2-44
Chapter 3 Trunk & Signaling System ............................................................. 3-1
3.1 Overview ................................................................................................ 3-1
3.1.1 Common Faults.............................................................................. 3-1
3.1.2 Common Fault Causes .................................................................. 3-2
3.2 Background Knowledge ......................................................................... 3-3
3.2.1 No. 7 Signaling ............................................................................... 3-3
3.2.2 Channel Associated Signaling ....................................................... 3-6
3.3 Fault Location ......................................................................................... 3-9
3.3.1 Abnormal No. 7 Trunk Circuit......................................................... 3-9
3.3.2 Abnormal No. 7 Trunk Circuit Maintenance ................................... 3-14
3.3.3 Abnormal No. 7 Signaling Link ....................................................... 3-14
3.3.4 Abnormal No. 7 Signaling Interworking (between Offices) ............ 3-19
3.3.5 Abnormal Channel Associated Signaling ....................................... 3-23
3.3.6 Abnormal PRA Trunk Circuit .......................................................... 3-23
3.3.7 Abnormal DSS1 Signaling Link (PRA Trunk) ................................. 3-26
3.3.8 Abnormal DSS1 Signaling Interworking (PRA Trunk) .................... 3-28
Chapter 4 Charging & Bill System ................................................................. 4-1
4.1 Overview ................................................................................................ 4-1
4.1.1 Common Faults.............................................................................. 4-1
4.1.2 Common Fault Causes .................................................................. 4-2
4.2 Background Knowledge ......................................................................... 4-3
4.2.1 Charging Modes ............................................................................. 4-3
4.2.2 Bill Generation & Storage .............................................................. 4-5
4.3 Fault Location ......................................................................................... 4-7
4.3.1 Bills Lost ......................................................................................... 4-7
4.3.2 Repeated Bills ................................................................................ 4-9
4.3.3 Crossing Bills ................................................................................. 4-11
4.3.4 Error Bills ....................................................................................... 4-12
4.3.5 Alarm Bills ...................................................................................... 4-14
4.3.6 Extra-Short-Conversation-Time Bills .............................................. 4-15
4.3.7 Extra-Long-Conversation-Time Bills .............................................. 4-17
4.3.8 Abnormal Bill Fetching ................................................................... 4-19
4.3.9 Abnormal Bill Backup ..................................................................... 4-22
4.3.10 Abnormal Format Conversion ...................................................... 4-24
4.3.11 Cannot Send Bills to iGateway Bill ............................................... 4-25
Chapter 5 Main Control System ..................................................................... 5-1
5.1 Overview ................................................................................................ 5-1
5.1.1 Common Faults.............................................................................. 5-1
5.1.2 Common Fault Causes .................................................................. 5-1
5.2 Background Knowledge ......................................................................... 5-3
5.2.1 C&C08 Switch Structure ................................................................ 5-3
5.2.2 AM/CM Communication Control Structure ..................................... 5-5
5.2.3 Inter-SM Link .................................................................................. 5-6
5.2.4 Inter-RSM Link ............................................................................... 5-7
5.3 Fault Location ......................................................................................... 5-8
5.3.1 CPU Overload ................................................................................ 5-8
5.3.2 Call Blocked ................................................................................... 5-11
5.3.3 Abnormal Module Loading ............................................................. 5-13
5.3.4 Abnormal Board Loading ............................................................... 5-16
5.3.5 Abnormal Board Switchover .......................................................... 5-20
Chapter 6 Clock System .................................................................................. 6-1
6.1 Overview ................................................................................................ 6-1
6.1.1 Common Faults.............................................................................. 6-1
6.1.2 Common Fault Causes .................................................................. 6-2
6.2 Background Knowledge ......................................................................... 6-3
6.2.1 Flow Direction of AM/CM Internal Clock Signals ........................... 6-3
6.2.2 Flow Direction of AM->SM Clock Signals ...................................... 6-4
6.2.3 Flow Direction of AM->RSM Clock Signals .................................... 6-4
6.2.4 Flow Direction of SM Internal Clock Signals .................................. 6-5
6.3 Fault Location ......................................................................................... 6-5
6.3.1 Impact on Subscriber System ........................................................ 6-5
6.3.2 Impact on Trunk System ................................................................ 6-7
6.3.3 Impact on Main Control System ..................................................... 6-9
6.3.4 AM/CM Clock Signal Test .............................................................. 6-10
6.3.5 SM Clock Signal Test..................................................................... 6-15
6.3.6 Test of Part HW Clock Signals ....................................................... 6-18
Chapter 7 Terminal System ............................................................................ 7-1
7.1 Overview ................................................................................................ 7-1
7.1.1 Common Faults.............................................................................. 7-1
7.1.2 Common Fault Causes .................................................................. 7-2
7.2 Background Knowledge ......................................................................... 7-3
7.2.1 Communication Architecture .......................................................... 7-3
7.2.2 BAM Service Processes ................................................................ 7-5
7.2.3 BAM Software Directories .............................................................. 7-7
7.2.4 Terms ............................................................................................. 7-9
7.3 Fault Location ......................................................................................... 7-9
7.3.1 LAN Switch Fault ........................................................................... 7-9
7.3.2 Network Adapter Fault ................................................................... 7-10
7.3.3 Hard Disk Fault .............................................................................. 7-11
7.3.4 Starting up Emergency Workstation .............................................. 7-11
7.3.5 BAM Virus Prevention & Clearing .................................................. 7-11
7.3.6 About Anti-Virus Software .............................................................. 7-16
Chapter 8 Alarm System ................................................................................. 8-1
8.1 Overview ................................................................................................ 8-1
8.1.1 Common Faults.............................................................................. 8-1
8.1.2 Common Fault Causes .................................................................. 8-2
8.2 Background Knowledge ......................................................................... 8-3
8.2.1 Connection of the Alarm Box ......................................................... 8-3
8.2.2 Connection of Rack’s Row & Column Alarm Indicators ................. 8-3
8.2.3 About ALM & AMD ......................................................................... 8-4
8.2.4 Alarm Box & DIP Switches ............................................................. 8-4
8.3 Fault Location ......................................................................................... 8-4
8.3.1 Alarm Box Fault ............................................................................. 8-4
8.3.2 Rack’s Row & Column Alarm Indicators Fault ............................... 8-6
8.3.3 Alarm Console Fault ...................................................................... 8-8
Chapter 9 Centrex Console ............................................................................. 9-1
9.1 Overview ................................................................................................ 9-1
9.1.1 Common Faults.............................................................................. 9-1
9.1.2 Common Fault Causes .................................................................. 9-2
9.2 Background Knowledge ......................................................................... 9-3
9.2.1 Console-Switch Connection Mode ................................................. 9-3
9.2.2 CTX ................................................................................................ 9-4
9.3 Fault Location ......................................................................................... 9-6
9.3.1 Abnormal Console-Switch Communication.................................... 9-6
9.3.2 Logon Failure ................................................................................. 9-9
9.3.3 Abnormal Call Function.................................................................. 9-10
9.3.4 Abnormal Basic Attendant Function ............................................... 9-13
9.3.5 Abnormal Data Maintenance Function ........................................... 9-18
9.3.6 Abnormal Bill Management Function ............................................. 9-20
Chapter 10 Intelligent Network Service ......................................................... 10-1
10.1 Overview .............................................................................................. 10-1
10.1.1 Common Faults ............................................................................ 10-1
10.1.2 Common Faults Causes .............................................................. 10-2
10.1.3 Basic Principles for Fault Locating troubleshooting ..................... 10-4
10.2 Background Knowledge ....................................................................... 10-4
10.2.1 Architecture of Intelligent Network ............................................... 10-4
10.2.2 Typical Intelligent Call Flow ......................................................... 10-7
10.3 Fault Location ....................................................................................... 10-8
10.3.1 Incapacity for Triggering the Intelligent Service (without IDP
Message) ................................................................................................ 10-8
10.3.2 Incapacity for Triggering the Intelligent Service (with IDP
Message) ................................................................................................ 10-10
10.3.3 Resource Application Fault .......................................................... 10-17
10.3.4 Abnormal Tone Playing upon Inadequate Balance ...................... 10-19
10.3.5 Abnormal Number Receiving ....................................................... 10-21
10.3.6 Hearing Busy Tone after Consecutive Calls ................................ 10-23
10.3.7 Connection Fault .......................................................................... 10-24
10.3.8 Change of Called Number ........................................................... 10-28
10.3.9 No Charge.................................................................................... 10-29
10.3.10 Abnormal Bill (Charging Error) ................................................... 10-31
10.3.11 Reply Signaling Error ................................................................. 10-32
10.3.12 Error in Sending CFL Message .................................................. 10-33
Appendix A Acronyms and Abbreviations .................................................... A-1
Index .................................................................................................................
HUAWEI
OVSV610R103
BOM 31033189
Huawei Technologies Co., Ltd. provides customers with comprehensive technical support
and service. Please feel free to contact our local office or company headquarters.
Website: http://www.huawei.com
Email: [email protected]
Trademarks
All other trademarks and trade names mentioned in this manual are the property of
their respective holders.
Notice
The information in this manual is subject to change without notice. Every effort has
been made in the preparation of this manual to ensure accuracy of the contents, but
all statements, information, and recommendations in this manual do not constitute
the warranty of any kind, express or implied.
Release Notes
The product version that corresponds to the manual is C&C08 Digital SPC Switching
System OVSV610R103.
Related Manuals
The following manuals provide more information about the C&C08 Digital SPC
Switching System.
Manual Content
It consists of two volumes. The Troubleshooting
Volume details on how to locate and process
common faults in the C&C08 Digital SPC
C&C08 Digital SPC Switching
Switching System, while the Routine
System Maintenance Manual
Maintenance Volume offers operational methods
and maintenance suggestions for routine
maintenance and special maintenance.
C&C08 Digital SPC Switching It is used for assisting the users in data
System Operation Manual configurations and typical applications.
It provides information for the system installation,
C&C08 Digital SPC Switching
including the installation of the cabinets, cables,
System Installation Manual
power system and various boards.
Organization
Chapter 2 Subscriber System discusses how to locate and process the faults
occurred to a single subscriber and to subscribers over an extensive area.
Chapter 3 Trunk & Signaling System covers fault location methods related to No. 7
signaling, Channel Associated Signaling and PRA trunk.
Chapter 4 Charging & Bill System focuses on the location of common faults occurred
to the host charging and online charging.
Chapter 5 Main Control System is devoted to common faults occurred to the main
control system in the respects of CPU overload, module loading, board loading and
board switchover.
Chapter 6 Clock System tells impacts on the subscriber system, trunk system and
main control system in the case of clock faults. It also gives methods to measure clock
signals.
Chapter 8 Alarm System treats fault location and processing related to alarm box,
rack's row & column alarm indicators and alarm console.
Chapter 9 Centrex Console gives fault location and processing related to Centrex
console.
Chapter 10 Intelligent Network Service turns to the fault location and processing
related to intelligent network services in the case that C&C08 Digital SPC Switching
System serves as the Service Switching Point (SSP).
Intended Audience
I. Keyboard operation
Format Description
Press the key with key name expressed with a pointed
<Key>
bracket, e.g. <Enter>, <Tab>, <Backspace>, or<A>.
Press the keys concurrently; e.g. <Ctrl+Alt+A>means the
<Key1+Key2>
three keys should be pressed concurrently.
Press the keys in turn, e.g. <Alt, A>means the two keys
<Key1, Key2>
should be pressed in turn.
Action Description
III. Symbols
Eye-catching symbols are also used in this document to highlight the points worthy of
special attention during the operation. They are defined as follows:
Table of Contents
i
Maintenance Manual – Troubleshooting Volume
C&C08 Digital SPC Switching System Table of Contents
ii
Maintenance Manual – Troubleshooting Volume
C&C08 Digital SPC Switching System Table of Contents
iii
Maintenance Manual – Troubleshooting Volume
C&C08 Digital SPC Switching System Table of Contents
iv
Maintenance Manual – Troubleshooting Volume
C&C08 Digital SPC Switching System Table of Contents
v
Maintenance Manual – Troubleshooting Volume Chapter 1 Troubleshooting Procedures and
C&C08 Digital SPC Switching System Basic Methods
C&C08 Digital SPC Switching System can maintain a normal and stable operation
after careful commissioning by the technicians at its initial installation stage. The
switching system may not run normally, however, due to some reasons such as the
influences of external environment on the system, aging and damage of some
components, or incorrect operations in maintenance. At this stage, the technical
maintenance personnel should be able to correctly analyze, locate and eliminate the
faults, to recover the system quickly.
This chapter offers some basic ideas of fault location and troubleshooting methods.
To locate and eliminate faults quickly and in time, the maintenance personnel should
be equipped with professional skills, operational specifications and psychological
competence. They are expected to:
z Have a good knowledge of the working principles of the C&C08 Switching
System, especially, the internal voice channel, signaling, switching and charging
flow. They should be familiar with various signaling protocol standards.
z Master basic maintenance operations.
The maintenance personnel are required to be familiar with basic operations of the
background maintenance and related meters, such as alarm querying, background
tracing, board switching over and meter using.
They are expected to keep studying the operation manual & maintenance manual and
try to have as many practices as possible, so as to be skillful in their operations.
z Be familiar with the office maintained.
The maintenance personnel should have a clear picture of the office to be maintained,
including its networking, signaling mode, software version, performance in the past
and the equipment layout in the equipment room. In addition, it is also necessary to
study and maintain the engineering documentation whenever possible.
z Collect and save site data.
Before troubleshooting, the maintenance personnel are required to collect and save
the site data. Data collection is an activity of great importance, because the data,
which is useful for finding out fault causes, may get damaged inevitably during
1-1
Maintenance Manual – Troubleshooting Volume Chapter 1 Troubleshooting Procedures and
C&C08 Digital SPC Switching System Basic Methods
troubleshooting. In some cases, the true fault cause remains unavailable due to lack
of data, even when the switch restores to normal, leaving a hidden trouble for both
the telecom operator and the vendor.
The data to be collected and saved on site include the system alarm, office data
configurations, various tracing records and board swapping data, as well as the
operation logs. In addition, the maintenance personnel are also required to record
every step of the troubleshooting process. All these data is quite helpful for the
analysis of accident causes or as a reference for similar troubleshooting in the future.
I. Essential
To locate a fault, you will first collect its related information. There are four sources to
collect the information:
z Fault complaint from the subscriber or customer center
z Fault notification from the maintenance personnel of the adjacent offices
z Alarm output of the switch's alarm system
z Routine maintenance or abnormality found during the scout
With the enlargement of network scale, the switch networking has become more and
more complex. Any internal or external factor may bring negative consequences on
the normal running of a switch, so, fault causes are becoming more and more
confusing. At the same time, it becomes more difficult to locate the faults.
II. Practical
Although there are different kinds of faults, they seldom occur simultaneously. That is,
at a specified time point, only one or some of them occurs. Thus it is possible to
locate a fault by the exclusive method.
1-2
Maintenance Manual – Troubleshooting Volume Chapter 1 Troubleshooting Procedures and
C&C08 Digital SPC Switching System Basic Methods
In the initial stage of fault processing, the collection of original information shall help
locate a fault, and improve the efficiency of fault processing, reduce the possibility of
error operation, thus making the subscriber more satisfied.
III. Suggestions
After collecting the information of a fault, you will judge its scope and type.
The determining of the fault scope is to find the direction of fault processing, that is,
where the specific cause of the fault may be and how to find it out.
In the switching system, the fault scope refers to the area where the fault occurs. It
often is a certain module of the switching system. So, this manual offers
troubleshooting methods through the following nine functional modules. You are
expected to locate a fault to one of the following modules.
z Subscriber system
z Trunk and signaling system
z Charging and bill system
z Main control system
z Clock system
z Terminal system
z Alarm system
z Centrex console
z Intelligent network
The judgment of the type of a fault is to find the method to analyze and solve the fault.
The faults are classified according to different methods, which are discussed in the
subsequent chapters.
1-3
Maintenance Manual – Troubleshooting Volume Chapter 1 Troubleshooting Procedures and
C&C08 Digital SPC Switching System Basic Methods
For the mostly used fault judgment methods, refer to 1.3 Basic Methods.
The fault location is to exclude impossible causes and find the right ones from many
possible causes.
The accurate and fast location not only improves the troubleshooting efficiency but
avoids some accidents caused by error operation. It provides key instructions and
references for the fault processing methods.
The section 1.3 Basic Methods offers some basic methods for fault judgment and
location.
Fault removing is to remove a fault and restore the system by suitable methods or
steps such as checking lines, replacing boards, modifying configuration data,
switching over boards, or resetting boards.
Through analyzing the original information of a fault, you can judge the fault scope,
specify the fault type, or even locate the fault directly.
[Case]
Engineer: Would you please tell me what the problem is? Can’t you hear the sound,
or can’t call out, or call in?
Subscriber: The problem is, when I call the telephone, the call can be connected, but
the telephone won’t ring. I have tried it with my mobile phone in my home, but the
telephone doesn't work either. Once I pick up the telephone, all I heard is the dialing
tone. Would you please tell me what the cause is?
Engineer: It is possible that the Call Forwarding Unconditional service has been
registered on your telephone. You may try to cancel it yourself, that is to dial “#57#”. If
it doesn’t work, please contact me again, ok?
1-4
Maintenance Manual – Troubleshooting Volume Chapter 1 Troubleshooting Procedures and
C&C08 Digital SPC Switching System Basic Methods
The result is that the subscriber had solved the problem himself or herself.
[Comment]
In the above case, the engineer first judged whether it was the “Call out” problem or
“Call in” problem. After the subscriber told him or her that once he or she picked up
the phone, all he or she heard was the dialing tone, the engineer was able to locate
the cause. Thus, it is obvious that original information is much helpful for the location
and solving of the fault.
The original information analysis can be used not only in the processing of
subscriber fault, but of other faults, especially trunk fault. It is because the trunk need
cooperate with the transmission system and there is signal interworking. In such a
case, the collection of original information plays a key role in the fault processing. The
original information includes whether the transmission is normal, whether the data of
the peer office has been modified, whether the definition of some signaling
parameters has been changed, and so on.
Alarm information is output from the switch's alarm system, indicated usually
through sound, light, Light Emitting Diode (LED) and screen output. The screen
output includes the detailed description of the abnormality, possible causes and
restoration suggestions. It involves the hardware, link, trunk, billing, Central
Processing Unit (CPU) loading ratio, and so on.
Through analyzing the alarm information, you can find the specified section or cause
of a fault, or even locate the fault directly. It is one of the main methods for fault
analysis.
[Case]
The alarm box sent a critical alarm (emergency alarm in the following figure) of Local
Optical Interface Board (OPT) fault, and the alarm console displayed the relative
information of “OPT card fault”, as shown in Figure 1-1.
1-5
Maintenance Manual – Troubleshooting Volume Chapter 1 Troubleshooting Procedures and
C&C08 Digital SPC Switching System Basic Methods
Figure 1-1 Alarm information output from the switch's alarm console
With the above information, the engineer had located the fault.
[Comment]
The method of analyzing alarm information is direct and accurate, and is one of the
mostly used methods.
Each board of the C&C08 switch has its running and status indicators, or even the
function or feature indicators. These indicators indicate the working status of the
corresponding boards, circuits, links, optical paths, nodes and active-standby mode.
Through analyzing the indicator status, you can find probable fault section or cause
quickly and get information for the next processing. You still need analyze the alarm
information because the information indicated by the indicators is inadequate.
[Case]
Take the E1 Digital Trunk Board (DTF) board as an example. Table 1-1 shows the
meanings of the indicators on the DTF board.
z If “LOS1” turns on, it indicates that the first E1 of the board loses the
synchronization with the corresponding E1 of the peer end and the board is
unable to receive the E1 signals from the peer end. It may be the fault of physical
channel or single pass.
z If “SLP2” turns on, the bit error rate between the second E1 of the board and the
corresponding E1 of the peer end is a bit great. It may be caused by the great
transmission decay or the bad clock synchronization performance.
You can get information from other indicators in the same way.
1-6
Maintenance Manual – Troubleshooting Volume Chapter 1 Troubleshooting Procedures and
C&C08 Digital SPC Switching System Basic Methods
Indicat Normal
Color Description Meaning
or status
1. Flashes fast: The board is
powered on for initialization.
2. Flashes slowly: The board is
working normally. Flashes
RUN Red Run Indicator
3.ON: The board is not working slowly
normally.
4.OFF: The board is not working
normally.
Channel 1
Frame ON: Frame remote alarm
RRA1 Green Remote OFF
Alarm OFF: Working normally
Indicator
Channel 1
Multi-frame ON: Multi-frame remote alarm
RMA1 Green Remote OFF
Alarm OFF: Working normally
Indicator
1-7
Maintenance Manual – Troubleshooting Volume Chapter 1 Troubleshooting Procedures and
C&C08 Digital SPC Switching System Basic Methods
Indicat Normal
Color Description Meaning
or status
Channel 1
Loss of ON: Loss of Signal
LOS1 Green OFF
Signal OFF: Working normally
Indicator
Channel 1
Signal ON: Non-reception of signals
RCL1 Green OFF
Unreceived OFF: Working normally
Indicator
Digital Signal
Process ON: DSP fault
DSP Green OFF
(DSP) fault OFF: Working normally
indicator
Channel 2
Frame ON: Frame remote alarm
RRA2 Green Remote OFF
Alarm OFF: Working normally
Indicator
Channel 2
Multi-frame ON: Multi-frame remote alarm
RMA2 Green Remote OFF
Alarm OFF: Working normally
Indicator
Channel 2
Loss of ON: Loss of Signal
LOS2 Green OFF
Signal OFF: Working normally
Indicator
Channel 2
Signal ON: Non-reception of signals
RCL2 Green OFF
Unreceived OFF: Working normally
Indicator
[Comment]
You are expected to be familiar with the indicator meanings so as to respond quickly
in case of a fault.
1-8
Maintenance Manual – Troubleshooting Volume Chapter 1 Troubleshooting Procedures and
C&C08 Digital SPC Switching System Basic Methods
Through making a call, you can judge whether the call processing function and
relative modules of the switch are normal. This method is often used to judge whether
the subscriber external line, switching network, trunk system, or billing system, and so
on, is normal.
[Cases]
Case I: One subscriber complained that there was no feedback on his or her
telephone. In order to find whether the subscriber external line was short circuited or
broken, the maintenance engineer called the telephone of the subscriber. The
subscriber heard the ring back tone and it meant that there was no short circuit in the
external line.
Case II: One subscriber complained that the voice volume of his or her telephone was
quite low, but the result of the line test was normal. In order to check whether there
was a problem at the switch side, the maintenance engineer connected a phone to
the subscriber line on the distribution frame and made a call. The voice volume was
normal and it meant that there was no problem at the switch side.
[Comment]
This method is a mostly used one in the routine maintenance. It is often used along
with the dynamic connection trace. It is also used to test various functions of the
switching system (such as call processing, calling line identification presentation and
billing).
The apparatus and meter reflect the fault nature with visual and quantified data. They
are often used in the external line analysis, power test, signaling analysis, wave
analysis and error bit detection, and so on.
[Cases]
Case I: The Calling Line Identification Presentation (CLIP) function of most of the
subscribers of a frame was faulted. To judge the effect of the Secondary Power
Supply Board (PWX) on the CLIP, the maintenance engineer used an oscilloscope
to analyze the waveform of the ringing current output from the PWX board. It was
found that there ware lots of “burrs”. Obviously, the “burrs” (harmonic wave voltage)
had affected the normal Frequency Shift Keying (FSK) transmission, thus causing the
abnormality of the CLIP function.
1-9
Maintenance Manual – Troubleshooting Volume Chapter 1 Troubleshooting Procedures and
C&C08 Digital SPC Switching System Basic Methods
Transfer Part (MTP), Telephone User Part (TUP), and so on. The analyzer can also
locate a link fault and test the bit error rate of a link.
[Comment]
The call completion rate is a key index of the switching system, because it affects
directly the income of the carriers and is a significant element of the core competitive
power of the carriers.
However, there are many possible causes affecting the call completion rate, and they
are hard to be detected. Through analyzing traffic statistics data, you can find the
main causes generating call loss in time and prevent them from occurrence.
[Cases]
An operator had created a task to make statistics on the traffic of the incoming trunk
groups of all office directions at an end office. The statistical report showed that most
of the call loss was caused by internal congestion: there ware more than ten failed
calls caused by congestion per 500 calls or so (in one hour), which dramatically
affected the call completing rate.
However, there ware many causes for internal congestion, such as switching
equipment congestion, temporary error, signaling error, network fault or no available
resources. Then, what was the specific cause leading to the trunk group congestion?
To solve the problem, the operator created a task to make statistics on the global call
failure causes. The statistical report showed that the sum of the times of “No
inter-module circuit” and that of “No available circuits” was almost equal to the
number of failed calls caused by internal congestions of the incoming trunk groups of
all office directions. So it can be judged that “No reachable or available circuit” was
the primary cause of the internal congestion.
Then, what call had no reachable circuit? The operator traced the No. 7 link of one
office direction. After observing the switch’s returning the Switching Equipment
Congestion (SEC) message for many times, the operator found that congestion
occurred when there were calls to the remote module X of the local office. So it was
known that “the module itself or the iDT circuit to the module X might get faulty”.
The operator checked the iDT circuit status in the direction of “Module X -> Center
module”, and found six idle PCMs among its eight ones; then checked the iDT circuit
status in the direction of “Center module -> Module X”, and found seven idle PCMs.
Thus, the problem was located: when the incoming trunk call seized the seventh PCM
of the center module (the PCM was in the self-loop), the problem of “no reachable or
1-10
Maintenance Manual – Troubleshooting Volume Chapter 1 Troubleshooting Procedures and
C&C08 Digital SPC Switching System Basic Methods
available circuit” was presented by the internal call loss of the local office in the traffic
statistics.
[Comment]
The traffic statistics analysis is often used along with the signaling trace, signaling
analysis, and so on, and it plays an important role to locate the abnormality of
inter-office signaling interworking, trunk parameter setting error, and so on. You are
strongly suggested to master it.
The connection and signaling trace is applied in locating the failure causes of call
connection and inter-office signaling interworking, and so on. The trace result helps to
find the cause of call failure directly and locate the problem or to get information for
the subsequent analysis.
[Case]
One customer complained that there were a great number of Circuit Group
Congestion (CGC) messages during the interconnection between a C&C08 switch
and X switch of the superior tandem office, which reduced the call completing rate.
The operator queried both links and circuits at the local office and found that they
were normal. The parameters of signaling point code, Circuit Identification Code CIC
code, Signaling Link Selection Code SLS code, and so on, were also correct. Finally,
the operator traced the No. 7 signaling of two links to the switch X on the
maintenance console.
After the observation, the operator found that there were a great number of CGC,
Clear Forward (CLF) and RLF messages in the second link. After the further
observation, the operator found that there were more than twenty incoming Initial
Address (IAI) messages before the CGC message and the interval between two IAI
messages is 7 ms, and the two IAI messages had the same contents. The trace result
is as follows:
upper lever office IAI ......(22 consecutive IAIs) IAI IAI CLF CLF ......
locall office IAI IAI CGC RLF CGC RLF ......
Obviously, it is incorrect.
After the analysis, the operator found that, in case of abnormality, the called number
in the IAI message was not in the local number segment table. Then the operator
1-11
Maintenance Manual – Troubleshooting Volume Chapter 1 Troubleshooting Procedures and
C&C08 Digital SPC Switching System Basic Methods
checked the called number analysis table and found that the numbers in the table
was unable to be forwarded to the local office. For example, the number segment
starting with “555” was “5551000~5551255”, and the corresponding prefix in the
called number analysis table was “5551”, while the called number in the IAI message
from the superior office was “5553123”. It was analyzed by the local office, then sent
to the switch X of the superior office in the outgoing route of Prefix 5. After the called
number analysis, the switch X returns the call to the local office, and so forth. One
circuit was seized on each sending of an IAI message. So there were CGC
messages.
Final location: the called number analysis of the superior office was not detailed
enough, which caused the cycle sending of the IAI message.
[Comment]
The connection and signaling trace is able to locate the fault cause accurately and
provide valuable information. It is one of the widely used method in the routine
maintenance and fault processing.
The loop back is to perform the self-sending and self-receiving (self-loop) to one
transmission device or channel by the hardware or software method. It also judges
the normality of transmission device, transmission channel, service status and
signaling interworking, and so on. It is to check whether the hardware equipment is
normal and software parameter setting is correct. It is one of the widely used methods
to locate the transmission problem and judge the correctness of trunk parameter
setting.
[Cases]
Case I: One subscriber complained that the voice volume of his or her telephone was
quite low. An engineer started the telephone test program, and found that the
subscriber loop resistance reached 2.6 kilohm, much greater than the standard. So,
the conclusion was drawn that “the great subscriber loop resistance was the direct
cause of the low voice volume of the telephone”.
Case II: The switch and transmission networking of one office is shown in Figure 1-3.
There were a great number of frame sliding alarms for the E1 channel from the local
office to the opposite office, which greatly affected the conversation quality. To check
1-12
Maintenance Manual – Troubleshooting Volume Chapter 1 Troubleshooting Procedures and
C&C08 Digital SPC Switching System Basic Methods
whether it was the fault of the switching system or the fault of the transmission system,
an operator performed the loop back segment by segment at the points of 1, 2, 3 and
4, as shown in Figure 1-3, for the local switch and the opposite switch, and compared
the results of each loop back. In this way, the operator specified the position where
the fault occurred and took the corresponding methods to remove it.
1 2 3 4
[Comment]
The test and loop back methods are usually employed along with the location of a
transmission fault. The loop back can be classified into hardware loop back and
software loop back. The operation of software loop back is simple and flexible, but its
reliability is not as good as the hardware loop back. In addition, the trunk self-loop is
also often used to judge whether the parameters of local office and the outgoing route
data are set correctly during the office deployment and trunk expansion.
Note:
The software loop back should be cancelled after the execution, but the maintenance
personnel often forget to cancel it, which is going to affect the normal running of the
switch. So the maintenance personnel are strongly suggested to record each
operation step so as to avoid the possible negative consequence.
1-13
Maintenance Manual – Troubleshooting Volume Chapter 1 Troubleshooting Procedures and
C&C08 Digital SPC Switching System Basic Methods
checks the change of the working status to find the fault range or faulty component. It
is usually used in the case that the fault range is complicated.
[Case]
There were four E1 channels from one office to Office X, and the status of one of
them was displayed as “Hardware blocking peer end”. An operator queried the E1 by
using the DSP E1CH command and the E1 was normal. Then the operator used the
following steps to locate and processing the fault:
1) Performed the hardware loop back for the local and peer offices on the E1
position in the Digital Distribution Frame (DDF), and the results were normal.
2) Performed the self-loop for the software of the local office, and the result was
normal.
3) Replaced the E1 by a normal E1 at the switch side on the DDF, and the switch
showed: the original faulted E1 had become normal, while the original normal
E1s become faulted. Thus there was no hardware fault in the switch.
4) Replaced the E1 by a normal E1 at the network side on the DDF, and the switch
showed: the original faulted E1 kept faulted, and the original normal E1s kept
normal. Thus the problem occurred to the DDF.
5) Performed measurement and comparison, and found that the resistance of the
E1 system was greater than that of other normal E1 systems.
The cause was that the welding of E1 radio frequency socket on the DDF was not
good. After the re-welding, the E1 recovered to normal.
[Comment]
In the actual fault location, various methods are used together. In the above example,
the methods of loop back, replacing, test and comparison are all used. It is obvious
that mastering various methods is quite helpful for the fault processing.
Note:
It should be pointed out that the replacing has a certain degree of risk, for example,
after a short-circuited board is inserted to a normal frame, the frame may become
faulted. So, cautions should be taken when replacing a component so as to avoid a
new fault.
Switching-over the device is to manually switch over the devices which work in the
active-standby mode, that is to forward the services from the active device to the
1-14
Maintenance Manual – Troubleshooting Volume Chapter 1 Troubleshooting Procedures and
C&C08 Digital SPC Switching System Basic Methods
standby device. After the switching-over, the operator compares the running status of
the device to check whether the active device or the active-standby relationship is
normal or not.
Resetting is to manually restart the whole switching device or some parts of it. It is
used to judge the software bugs, such as whether the software running is confused or
not, whether the program becomes abnormal or not. This method is the last method
for the fault processing.
The switching-over and resetting cannot find a specific fault cause. Due to the
randomness of software running, the fault may be not able to reoccur after the
switching-over or resetting, thus it is difficult to know the real fault and solve the
problem. So, this method is just an emergency method, applicable only in the
emergent situation.
Note:
Back up the data of the main control boards before switching over them so as to
avoid the loss of bills and system data.
The switching-over and resetting are quite restricted and are not recommended to
use because resetting often interrupts system service, even makes the system down
due to the error operation, which will bring severe negative consequences to the
routine running of a switch.
For any problem which is hard to solve in the routine maintenance or fault processing,
you can contact the technical support engineers in your city through telephone, fax or
Email or just contact directly the Huawei customer service center. When you tell a
fault to an engineer, provide the following information:
z Detailed name of the switch office
z Linkman and telephone
z Time of fault occurring
z Detailed description of the fault
z Host software version of the switch
z Actions performed and the results
z Problem level
We shall arrange our engineers to process your problems.
1-15
Maintenance Manual – Troubleshooting Volume Chapter 1 Troubleshooting Procedures and
C&C08 Digital SPC Switching System Basic Methods
In addition, you can get the latest technical documents from our technical support
website: http://support.huawei.com.
1-16
Maintenance Manual – Troubleshooting Volume
C&C08 Digital SPC Switching System Chapter 2 Subscriber System
2.1 Overview
This chapter discusses how to locate the common faults related to the subscriber
system and offers simple troubleshooting instructions. For related details of switch
operations, refer to the instructions and suggestions in C&C08 Digital SPC Switching
System Operation Manual.
Table 2-1 lists the common faults that may occur in the subscriber system.
Table 2-1 Common faults that may occur in the subscriber system
Abnormal No ringing, false ringing and ringing not stopped after hooking
ringing off
Only a Abnormal Cannot call-in, call released when hooking off, only a ringing is
single call-in given.
subscriber Abnormal No dial tone, the dial tone cannot be stopped, and the busy
is faulty. call-out tone is given after hooking off.
Subscribers of
a half or an No feed for the telephone, cannot call-in, no dial tone, loud
entire frame conversation noise
get faulty.
Subscribers
over an Inter-office trunks have been totally blocked. In this case, the
Global traffic
extensive switch cannot process any incoming or outgoing calls. Or calls
totally blocked
area are between modules cannot be established.
faulty.
Subscribers of Switching Module (SM), Remote Switching
Inter-module
Module (RSM) or other modules fail to make calls to
traffic totally
subscribers of other modules, that is, inter-module connection
blocked
fails.
2-1
Maintenance Manual – Troubleshooting Volume
C&C08 Digital SPC Switching System Chapter 2 Subscriber System
Abnormal
Subscribers Unidirectional call, cannot talk to each other, call released in the
intra-module
over an conversation process
connection
extensive
area are Abnormal
Long connection time, unidirectional call, cannot talk to each
faulty. inter-module
other, call released in the conversation process
connection
Abnormal
Long connection time, unidirectional call, cannot talk to each
inter-office
other, call released in the conversation process
connection
Table 2-2 lists the common fault causes that may occur in the subscriber system.
Table 2-2 Common fault causes that may occur in the subscriber system
The Analog Subscriber Line No feed for the telephone, abnormal ringing,
Board (ASL) is faulty. conversation noise, too low conversation voice
No dial tone, the dial tone cannot be stopped,
The Dual Tone Number
and the busy tone is heard given after hooking
Receiving & Drive Board (DRV)
off. Usually subscribers of a half frame shall be
is faulty.
Switch affected.
hardware
The Secondary Power Supply No ringing, loud conversation noise, affecting
fault
Board (PWX) is faulty. subscribers of an entire frame usually
The Node Communication No dial tone, cannot call-in, affecting subscribers
Board (NOD) is faulty. of a half or an entire frame usually
The Signal Tone Board (SIG) is No dial tone, affecting subscribers of an entire
faulty. module usually
2-2
Maintenance Manual – Troubleshooting Volume
C&C08 Digital SPC Switching System Chapter 2 Subscriber System
2-3
Maintenance Manual – Troubleshooting Volume
C&C08 Digital SPC Switching System Chapter 2 Subscriber System
Figure 2-1 shows a networking application of the C&C08 Digital SPC Switching
System.
40.96 Mbit/s E1
SM ASL
DSL
AM/CM E1/STM E1
RSM ASL
DSL
E1/STM
SPM Other exchange
E1/STM ASL
SPM V5 DSL
E1/STM ASL
SPM RSA
DSL
The following text discusses the call flows in different networking modes.
2-4
Maintenance Manual – Troubleshooting Volume
C&C08 Digital SPC Switching System Chapter 2 Subscriber System
I. Intra-SM call
Call type: an intra-module call, whose calling party and called party are in an SM.
z Speech channel: Calling party -> ASL -> DRV -> BNET -> DRV -> ASL -> Called
party.
z Calling party's signaling channel: Calling party -> ASL -> DRV -> NOD -> MPU.
z Signal tone channel: SIG -> BNET -> DRV -> ASL -> Calling party.
Call type: a trunk tandem call, whose calling party is in Switch 1 and called party is in
Switch 2.
The local switch may be a tandem switch, toll switch, or gateway switch.
z Speech channel: Switch 1 -> Channel -> ET16 or STM-1 Transit Unit Board
(STU) -> QSI -> SNU -> CNU -> SNU -> QSI -> ET16 or STU -> Channel ->
Switch 2.
z No. 7 inter-office signaling channel (incoming): Originating switch -> Signaling
link -> ET16 or STU -> QSI -> SNU -> CNU -> SNU -> QSI -> Multi-HW Interface
Board (MHI) -> CPC -> Service Processing Board (SPC).
z MFC inter-office signaling channel (incoming): Originating switch -> Channel ->
ET16 or STU -> QSI -> SNU -> CNU -> SNU -> QSI -> MHI -> Shared Resource
Board (SRC) -> MHI -> QSI -> FSN -> BAC -> FSN -> SPC.
Call type: an inter-module call, whose calling party is in an SM and called party is in
another SM.
z Speech channel: Calling party -> ASL -> DRV -> BNET -> OPT -> Optics fibers
-> OBC -> QSI -> SNU -> CNU -> SNU -> QSI -> OBC -> Optics fibers -> OPT
-> BNET -> DRV -> ASL -> Called party.
z Inter-module signaling channel: MPU#1 -> LPMC2 -> BNET -> OPT -> Optics
fibers -> OBC -> QSI -> FSN -> BAC -> FSN -> QSI -> OBC -> Optics fibers ->
OPT -> BNET -> LPMC2 -> MPU#2.
Call type: an outgoing call, whose calling party is in an SM and called party is in other
switching office.
z Speech channel: Calling party -> ASL -> DRV -> BNET -> OPT -> Optics fibers
-> OBC -> QSI -> SNU -> CNU -> SNU -> QSI -> ET16 or STU -> Channel ->
Opposite office.
2-5
Maintenance Manual – Troubleshooting Volume
C&C08 Digital SPC Switching System Chapter 2 Subscriber System
z Inter-module signaling channel: MPU -> LPMC2 -> BNET -> OPT -> Optics
fibers -> OBC -> QSI -> FSN -> BAC -> FSN -> SPC.
Call type: an inter-module call, whose calling party is in an RSM and called party is in
an SM.
z Speech channel: Calling party -> ASL -> DRV -> BNET -> DTF -> Channel ->
ET16 or STU -> QSI -> SNU -> CNU -> SNU -> QSI -> OBC -> Optics fibers ->
OPT -> BNET -> DRV -> ASL -> Called party.
z Inter-module signaling channel: MPU#1 -> LPMC2 -> BNET -> DTF -> Channel
-> ET16 or STU -> QSI -> FSN -> BAC -> FSN -> QSI -> OBC -> Optics fibers ->
OPT -> BNET -> LPMC2 -> MPU#2.
Call type: an outgoing call, whose calling party is in an RSM and called party is in
other switching office.
z Speech channel: Calling party -> ASL -> DRV -> BNET -> DTF -> Channel ->
ET16 or STU -> QSI -> SNU -> CNU -> SNU -> QSI -> ET16 or STU -> Opposite
office.
z Inter-module signaling channel: MPU -> LPMC2 -> BNET -> DTF -> Channel ->
ET16 or STU -> QSI -> FSN -> BAC -> FSN -> SPC.
Note:
The thorough understanding of all call flows does great help to the analysis and
location of problems.
2.2.2 Requirements
I. Subscriber lines
2-6
Maintenance Manual – Troubleshooting Volume
C&C08 Digital SPC Switching System Chapter 2 Subscriber System
Note:
The off-hook direct current (dc) resistance of the telephone should be no more than
350 ohm.
1) Ringing current
The ringing current source is 25±3 Hz sinusoidal wave. The harmonic distortion
should be less than or equal to 10% and the valid output voltage is 75±15 Hz.
An interrupted ringing of five seconds is applied to the ringing, that is, ringing for one
second and no ringing for four seconds. The allowed deviation of the make-or-break
time is no more than 10%. When the distinctive ringing is required for Centrex
console (CTX) or party-line telephones, another ringing mode is used, that is, ringing
for 0.3 second, no ringing for 0.4 second, ringing for 0.3 second and no ringing for
four seconds.
2) Signal tone
z The signal source is 450±25 Hz or 950±50 Hz sinusoidal wave and the harmonic
distortion should be less than or equal to 10%. When necessary, the signal
source may be 1400±50 Hz or 1800±50 Hz and the harmonic distortion less than
or equal to 5%.
z When the connected signal is sent to frequency-division or time-division circuits,
its absolute power level is −10±3 dBm or −20±3 dBm measured at the zero
relative level point as per the types of the signal tone. The howler tone is in a
range of 0 to 25 dBm.
z The allowed deviation of the make-or-break time of individual signal tones should
be no more than ±10%.
1) The time to monitor the hook-off but no dialing is 10 seconds (applicable to both
dial & push button telephone).
2) The time that the originating end office monitors inter-digit no dialing is 20
seconds.
3) Ringing timer: 60 seconds for local calls, 90 seconds for toll calls and 120
seconds for international calls.
2-7
Maintenance Manual – Troubleshooting Volume
C&C08 Digital SPC Switching System Chapter 2 Subscriber System
Note:
Different countries may vary from one another. The analysis in the following text is
based on the data here.
I. Detailed description
There is no dial tone after a user hooks off, or the working or line indicator lamp on
the telephone is OFF.
Seria
Fault causes Remarks
l No.
External lines are
1 The subscriber loop circuit is open.
broken.
2-8
Maintenance Manual – Troubleshooting Volume
C&C08 Digital SPC Switching System Chapter 2 Subscriber System
Type the STR RTSTI command on the maintenance console, select "Loop test" in the
[Test type] field and tick "Resistance" in the [Loop test option] field. Then specify other
related parameters and press <F9> to run this test program. With reference to the test
result, the following qualitative judgement can be made.
z If Rab<300 ohm, the external line may be short-circuited. In this case, check or
directly repair the external line.
z If Rab>20 kilohm, the external line may be broken. In this case, check or directly
repair the external line.
Note:
To judge whether the subscriber loop or ring circuit is short-circuited in a short time,
just call the subscriber. If there is ring back tone, the external line is not short-circuited.
If there is busy tone, the external line may be short-circuited or there is other fault.
If there is no feed or the feed voltage is too low, change the subscriber port or directly
change the ASL.
3) Judge whether it is the external line fault or switch's circuit fault.
Isolate the subscriber external line on the distribution frame and test the subscriber
Wire A and Wire B at the switch side by a testing telephone or a universal meter.
z If there is dial tone or the voltage is –48 V, the switch's circuit is normal.
z Otherwise, check the ASL and the subscriber line, for example, replacing the
ASL or checking the continuity of the subscriber line by use of a universal meter.
4) Judge whether there is swinging cross.
Swinging cross causes no feed for the telephone because in this case Wire A and
Wire B have the same potential. After excluding other possible causes, therefore,
judge whether there is a swinging cross fault by measuring Wire A-ground potential
and Wire B-ground potential. If Wire A-ground potential is equal to Wire B-ground
potential and is not zero, it is likely that there is a swinging cross fault.
5) Judge whether the subscriber telephone is faulty
Telephone fault often causes no feed. To check whether a telephone is faulty, replace
the telephone or measure Wire A-Wire B voltage at the subscriber side by using a
universal meter. Generally, check it at the beginning or end of a fault processing.
2-9
Maintenance Manual – Troubleshooting Volume
C&C08 Digital SPC Switching System Chapter 2 Subscriber System
IV. Suggestions
Among all causes, the faults of external lines and the ASL take a great proportion.
Therefore, it is helpful to regularly test subscriber circuits and the ASL, to know the
circuits' running parameters and the ASL's running situation in time. This helps
prevention and fast clearing of such faults.
I. Detailed description
Seria
Fault causes Remarks
l No.
The PWX is faulty and as The subscriber frame has no ringing source
1 a result no ringing is available, which causes no ringing for the
output. subscribers of the frame.
The subscriber circuit on
the ASL is faulty and so There will be no ringing for the corresponding
2
the ringing cannot be sent subscriber.
out.
The subscriber has not cancelled the
supplementary service Call Forwarding
Supplementary services
3 Unconditionally (CFU). So all incoming calls
are improperly set.
are forwarded and this telephone does not
ring.
The ringing circuit of the
4 Null
telephone is faulty.
2-10
Maintenance Manual – Troubleshooting Volume
C&C08 Digital SPC Switching System Chapter 2 Subscriber System
Normal
Indicator Color Description Meaning
status
1) Flashes slowly: The
Running communication is normal. Flashes
RUN Red status
2) Flashes fast: The slowly
indicator
communication is abnormal.
Working 1) ON: The ringing current
status output is normal.
VA0 Green indicator of ON
ringing 2) OFF: The ringing current
current output is abnormal.
If the VAO indicator is OFF, it means that the PWX has no output of ringing current. In
this case, check whether the switches on the board are in ON position or directly
change the PWX.
In general, two PWXes have been configured for each subscriber frame to achieve
mutual-aid power supply. If there is no ringing current in the frame, it means that both
PWXes are faulty.
2) Judge whether the subscriber port on the ASL is faulty.
Type the STR RTSTI command on the maintenance console, select "Analog circuit
test" in the [Test type] field and tick "Ring" & "Ring current voltage" in the [Circuit test
2-11
Maintenance Manual – Troubleshooting Volume
C&C08 Digital SPC Switching System Chapter 2 Subscriber System
option] field. Then specify other related parameters and press <F9> to run this test
program. With reference to the test result, the following judgement can be made.
z If the ringing function is abnormal, change the subscriber port or directly change
the ASL.
z If the ringing current voltage is much lower than 75 V (for example, 20 V), check
the PWX or directly change the ASL.
3) Check the settings of the subscriber's supplementary services.
Type the LST DN command on the maintenance console and set the [Display user
authority] field to YES. Then specify other related parameters and press <F9> to run
the command.
Method 1: Connect Wire A and Wire B to a testing telephone on the distribution frame
to simulate a call. If the testing telephone rings, it indicates that the subscriber
telephone is faulty.
Method 2: Type the SET TSTTEL command on the maintenance console and type
the number of the telephone to be tested. Then specify other related parameters and
press <F9> to start the test. Afterwards, type the STR TSTTEL command and select
"Send the ringing" in the [Test options] field. Press <F9> to start the test program.
If the returned result is normal, it means that the subscriber loop circuit is connected
and has no fault. In this case, the subscriber should change his or her telephone.
Serial
Fault causes Remarks
No.
The subscriber circuit on the
ASL is faulty. The ringing relay This fault may lead to false or long
1
has been abnormally started or it ringing.
cannot be released after startup.
2-12
Maintenance Manual – Troubleshooting Volume
C&C08 Digital SPC Switching System Chapter 2 Subscriber System
Otherwise, check out the quality of the system's power waveform. Generally, use an
oscillograph to observe the voltage waveform of the power supply and analyze the
harmonic components. The harmonic component may cause the ringing control circuit
on the ASL to start up when interfered by wrong signals, consequently leading to false
ringing.
2) Contact technical support engineers
If the problem has not been cleared yet, or you are not confident enough in your
judgement, contact technical support engineers in time.
VI. Locating the fault "Ringing not stopped after hooking off"
The primary reason is that the subscriber loop resistance is too large, that is, the
change of the loop resistance is beyond the switch's sensitivity monitoring range
when the called party hooks off. So, the switch fails to detect the off-hook and
considers that the called party is still idle and keeps on sending ringing. You can
measure the subscriber loop resistance on the maintenance console.
Type the STR RTSTI command on the maintenance console, select "Loop test" in the
[Test type] field and tick "Resistance" in the [Loop test option] field. Then specify other
related parameters and press <F9> to run this test program. With reference to the test
result, the following qualitative judgement can be known.
If Rab is far more than 1,800 ohm, the subscriber loop resistance is beyond the
standard value.
Such a fault is usually found in rural area. In general, it is cleared by changing the
external lines, increasing the diameter of the external lines, or using an ASL with
better remote feed capability, and so on.
VII. Suggestions
It is recommended to regularly test subscriber circuits, the ASL, the PWX, and so on,
so as to discover or prevent such faults in time.
2-13
Maintenance Manual – Troubleshooting Volume
C&C08 Digital SPC Switching System Chapter 2 Subscriber System
I. Detailed description
Abnormal call-in refers to the case that occurs to the called party after the calling
party finishes the dialing and before the called party picks up the phone. It includes
the following three cases.
z A subscriber cannot receive any incoming call (Cannot call in). In this case, the
calling party hears busy tone at all time when he or she attempts to call the
subscriber.
z A call is released when the called party hooks off. In this case, when there is an
incoming call, the called party hears the ringing but the call is released when he
or she hooks off. Afterwards, both the calling and called parties hear busy tone.
z Only a ringing is given. In this case, when there is an incoming call, only a
ringing is given to the called. Then the circuit restores and the calling party hears
busy tone.
Seria
Fault causes Remarks
l No.
This fault causes the called party to be always in
External lines are
1 busy status, and consequently, no incoming call
short-circuited.
can be made to the subscriber.
If the Do-Not-Disturb service has not been
cancelled, Call Forwarding has been set to a
Supplementary
vacant number, or the destination number of the
2 services are improperly
call forwarding doesn't have enough rights, the
set.
calling party will hear busy tone when he or she
attempts to make a call to the subscriber.
The system can properly process the off-hook
The circuit on the ASL
3 signal, but soon the circuit restores, which leads
is faulty.
to the failure of the call set-up.
2-14
Maintenance Manual – Troubleshooting Volume
C&C08 Digital SPC Switching System Chapter 2 Subscriber System
Among them, the release reason is a great help to the fault locating. For instance, in
the case that the calling party hears busy tone when he or she calls a subscriber, and
the system gives the release reason "Called party has registered Do-Not-Disturb", at
this time, the fault cause is obvious.
2) Judge whether the external line meets the standard quality requirement.
Type the STR RTSTI command on the maintenance console, select "Loop test" in the
[Test type] field and tick "Resistance" & "Capacitance" in the [Loop test option] field.
Then specify other related parameters and press <F9> to run this test program. With
reference to the test result, the following qualitative judgement can be made.
z If Rab<300 ohm, the external line may be short circuited, which leads to the fault
of "Cannot call in".
z If Ra or Rb is smaller than 20 kilohm, the Wire A-ground or Wire B-ground
insulation performance may deteriorate, which leads to the fault that only a
ringing is given.
z If 5 kilohm<Rab<7 kilohm, the inter-wire insulation performance may deteriorate,
which leads to the fault that only a ringing is given.
z If Ca or Cb is greater than 0.7 µF, the Wire A-ground or Wire B-ground insulation
performance may deteriorate, which leads to the fault that only a ringing is given.
z If Cab>0.7 µF, the inter-wire insulation performance may deteriorate, which leads
to the fault that only a ringing is given.
In all the above cases, the further checking and processing of the external lines are
required.
3) Check the settings of the subscriber's supplementary services.
Type the LST DN command on the maintenance console and set the [Display user
authority] field to YES. Then specify other related parameters and press <F9> to carry
out the command.
Method: change the suspected ASL by a spare one and make comparative analysis.
2-15
Maintenance Manual – Troubleshooting Volume
C&C08 Digital SPC Switching System Chapter 2 Subscriber System
IV. Suggestions
It is recommended to regularly test subscriber circuits, the ASL, the PWX, and so on,
so as to discover and prevent such faults in time. Besides, instructions on the proper
use of supplementary services are also recommended to be offered to subscribers.
I. Detailed description
Abnormal call-out refers to the case that the calling party cannot make a call after he
or she hooks off. It includes the following three cases.
z There is no dial tone (but with feed) after the calling party hooks off.
z The dial tone cannot be stopped, that is, the dialing is invalid.
z There is busy tone after the calling party hooks off.
Serial
Fault causes Remarks
No.
The ASL is The ASL fails to receive the subscriber's off-hook
1
faulty. signal, leading to no dial tone for the telephone.
2-16
Maintenance Manual – Troubleshooting Volume
C&C08 Digital SPC Switching System Chapter 2 Subscriber System
Serial
Fault causes Remarks
No.
The NOD is a communication bridge between the
MPU and individual boards and also is a
communication node when transferring the subscriber
line signaling. When the two NOD cables from a
subscriber frame are connected to the NOD, there
shall be no dial tone for the subscribers of the entire
frame, or the "Cannot call in" fault occurs once the
The NOD is NOD fails. In addition, all boards in the subscriber
5
faulty. frame cannot finish the registration on the
maintenance console.
When only a NOD cable from a subscriber frame is
connected to the NOD, there are usually such faults
as increasing call loss, slow call connection, or much
more times of no dial tone after hooking off, once the
NOD fails.
1) Judge whether there is only a single faulty subscriber or many faulty subscribers
over an extensive area.
In the case of a single faulty subscriber, refer to steps 2), 3) and 4). In another case,
refer to steps 5), 6) and 7).
2) Check whether the subscriber data has been configured.
Method 1: Type the LST DN command on the maintenance console and specify the
[Telephone number] field to the number of the faulty subscriber. Then specify other
related parameters and press <F9> to carry out the command. With reference to the
result, the following judgement can be made.
2-17
Maintenance Manual – Troubleshooting Volume
C&C08 Digital SPC Switching System Chapter 2 Subscriber System
If the message "Invalid subscriber number" is given, there is surely no dial tone for
the telephone after the calling party hooks off. In this case, reconfigure the subscriber
data.
Method 2: Type the STR RTSTI command on the maintenance console, select
"Analog circuit test" in the [Test type] field and tick "Dial tone" in the [Circuit test option]
field. Then specify other related parameters and press <F9> to run this test program.
With the test result, judgement can be made. If the ASL is faulty, change it by another
one.
4) Judge whether the BNET has the exchange error.
The exchange error generally occurs in a specific timeslot invariably. So it is easy to
find the fault again. To clear this fault, start the dynamic connection tracing on the
maintenance console with the faulty subscriber as the object. If the fault occurs to a
fixed timeslot, it indicates that the BNET has the exchange error. At this time, reset or
change the BNET.
5) Judge whether the SIG is faulty.
Type the SWP BRD command on the maintenance console, specify the module
number and select "SIG" in the [Card type] field, and press <F9> to carry out the
command. If the fault disappears after the switchover, it indicates that the SIG is faulty.
At this time, replace the SIG.
6) Judge whether the DRV and NOD are faulty.
In general, whether a board is faulty can be known by observing its indicators. If no
judgment can be made, use the following method.
Method: change the suspected DRV (NOD) by a spare one and make comparison
analysis.
7) Check whether the HW and NOD cables are faulty.
In general, the failure of HW and NOD cables is caused by poor connector contact,
broken wires or cables, and so on, which usually leads to no dial tone for subscribers
of a half frame. To locate such faults, check out the cable connection or take
measurements by a universal meter.
2-18
Maintenance Manual – Troubleshooting Volume
C&C08 Digital SPC Switching System Chapter 2 Subscriber System
IV. Possible causes for the fault that the dial tone cannot be stopped
Serial
Fault causes Remarks
No.
The ASL fails to receive the subscriber's off-hook
1 The ASL is faulty. signal, leading to the fault that the dial tone
cannot be stopped.
The DRV offers functions such as dual-tone
number receiving, subscriber line signaling
transfer and HW cable signal driving, and so on,
usually configured in pairs in the subscriber
frame. When one fails and the mutual-aid function
has not been normally in service, the other DRV
2 The DRV is faulty.
cannot normally process Dual Tone Multi
Frequency (DTMF) signals, which causes the fault
that the dial tone cannot be stopped. In general,
subscribers of a half frame are affected. In a
severe situation, subscribers of an entire frame
will be affected.
VI. Locating the fault that the busy tone is given after hooking off
The fault is possibly caused by the situation that the system has no number receiving
resources. To clear such a fault, therefore, just change the DRV so to judge whether it
is faulty.
2-19
Maintenance Manual – Troubleshooting Volume
C&C08 Digital SPC Switching System Chapter 2 Subscriber System
VII. Suggestions
In most cases, the abnormal call-out is caused by the errors of the switching system.
Therefore, it is recommended to regularly check the ASL, DRV and other boards to
know the equipment's working status in time.
I. Detailed description
Abnormal connection refers to the case that occurs to the calling party after the
calling party finishes the dialing and before the called party picks up the phone. It
includes the following three cases.
z The intra-module connection is abnormal. In this case, when a subscriber makes
an intra-module call, such faults occur as no ring back tone, busy tone given in
connection, long connection time, unidirectional call, cannot talk to each other, or
call released in the conversation process.
z The inter-module connection is abnormal. In this case, when a subscriber makes
an inter-module call, such faults occur as no ring back tone, busy tone given in
connection, long connection time, unidirectional call, cannot talk to each other,
call released in the conversation process or Internet access disconnected.
z The outgoing call connection is abnormal. In this case, when a subscriber makes
an outgoing call, such faults occur as no ring back tone, busy tone given in
connection, long connection time, unidirectional call, cannot talk to each other,
call released in the conversation process or Internet access disconnected.
Abnormal connection is the result of the exceptions that occur to the switch's call
processing software, connection control circuits, signaling links, trunk circuits, and so
on. In general, it affects many subscribers. To locate the faults, refer to Sections
2.3.11, 2.3.12 and 2.3.13.
I. Detailed description
The fault refers to all the exceptions that occur to the conversation process, including
the following cases.
z Loud conversation noise, for example, "rustling" noise, alternating current (ac)
noise that occurs in the conversation process.
2-20
Maintenance Manual – Troubleshooting Volume
C&C08 Digital SPC Switching System Chapter 2 Subscriber System
z Too low or too loud conversation voice, that is, the conversation volume does not
conform to relevant standards (for example, 30 ~ 40 dB in China).
z Cross-talk, that is, unexpected third-party voice occurring in the conversation
process.
Serial
Fault causes Remarks
No.
It is a common reason that introduces conversation
noise. The deterioration of inter-wire insulation
External lines
1 performance usually introduces the "rustling" noise
are faulty.
and that of Wire A-ground or Wire B-ground
insulation performance introduces ac noise.
The ASL is It is primarily caused by the aging of the components
2
faulty. or devices on the board.
The ground The high frequency switch power has a wide use in
5 resistance is too the switch's power system. To secure the normal
large. working of the switch, a significant prerequisite is to
screen out the high frequency signals generated in its
working process. In the case of too large ground
resistance, the high frequency power will introduce
loud noise to the conversation.
2-21
Maintenance Manual – Troubleshooting Volume
C&C08 Digital SPC Switching System Chapter 2 Subscriber System
Serial
Fault causes Remarks
No.
It affects all subscribers of the frame.
Abnormal matching of clock signals, caused by
HW cables are different length of HW cables, improper binding and
7
faulty. different loads carried by HW cables, will introduce
conversation noises to the subscribers of the entire
frame.
The telephone is It is a common reason that introduces conversation
8
faulty. noise and generally affects only a single subscriber.
1) Judge whether there is only a single faulty subscriber or many faulty subscribers
over an extensive area.
This is a key step to locate the conversation noise fault. If there is only a single faulty
subscriber, refer to steps 2), 3) and 4). In another case, refer to steps 5), 6) and 7).
2) Judge whether the subscriber telephone is faulty.
Connect Wire A and Wire B to a testing telephone on the distribution frame to test. If
the conversation is normal, it indicates that the subscriber telephone is faulty. If there
is noise, carry out the following procedures.
3) Judge whether the external line insulation performance has deteriorated.
Method 1: Isolate the subscriber external line on the distribution frame and test Wire A
and Wire B at the switch side by a testing telephone. If the conversation is normal, it
indicates that the subscriber external lines have poor insulation. If noise still exists,
judge whether the ASL is faulty.
Method 2: Type the STR RTSTI command on the maintenance console, select "Loop
test" in the [Test type] field and tick "Resistance" & "Capacitance" in the [Loop test
option] field. Then specify other related parameters and press <F9> to run this test
program. With reference to the test result, the following qualitative judgement can be
made.
z If Ra or Rb is smaller than 20 kilohm, the Wire A-ground or Wire B-ground
insulation performance may deteriorate, which may introduce ac noise.
z If 5 kilohm<Rab<7 kilohm, the inter-wire insulation performance may deteriorate,
which may introduce "rustling" noise.
z If Ca or Cb is larger than 0.7 µF, the Wire A-ground or Wire B-ground insulation
performance may deteriorate, which may introduce ac noise.
z If Cab>0.7 µF, the inter-wire insulation performance may deteriorate, which may
introduce "rustling" noise.
2-22
Maintenance Manual – Troubleshooting Volume
C&C08 Digital SPC Switching System Chapter 2 Subscriber System
In all the above cases, the further checking and processing of the external line are
required.
4) Judge whether the subscriber port on the ASL is faulty.
Change the suspected ASL by a spare one and make comparison analysis.
5) Judge whether the transmission system is faulty.
If the conversation noise occurs to outgoing calls or inter-module calls which are
through external transmission system, contact the transmission equipment's
maintenance staff and check whether there are such exceptions as error bits,
intermittent bit error bursts and pointer adjustment. Or check the transmission related
alarm information through the switch's alarm system and indicators of related trunk
boards to help determine whether the transmission system is faulty.
Besides, dirty tail wires of optics fibers or poor contact of radio-frequency head may
also introduce conversation noise because many Optical Distribution Frames (ODFs)
and DDFs have been used to transfer Optics fibers and E1 coaxial cables. Therefore,
it is necessary to check the transfer points or transfer equipment of the transmission
lines.
z The cleanness of tail Optics fibers can be judged by observation or by measuring
the optical power. In general, if the optical power is far less than the normal
optical power, for example, 3 dB, it is necessary to clean the tail Optics fibers.
z Generally, it is difficult to find through observation whether the radio-frequency
head or base is in poor contact situation. So, the change of radio-frequency head
or base or sectional loop-back may be used.
If exceptions have occurred to the transmission related boards in the switch (for
example, QSI, OBC, OPT, STU or ET16), noise may be introduced to inter-module
calls and outgoing calls. In this case, use the following ways to locate the faults.
z Change the suspected board by a spare one and make comparison analysis.
z Test the signals output by the board by a bit error tester and judge whether the
bit error rate exceeds the requirements.
6) Test the voltage waveform of the power supply.
Test the voltage waveform of the faulty module's power supply by an oscillograph and
analyze its harmonic components. If there is severe wave distortion, check the high
frequency switch power system and the switch's grounding.
First, measure the ground resistance by a ground resistance meter. If it is larger than
the specified value, for example, 1 ohm in China, make an all-around check of the
grounding system, including ground wires, grounding point, grounding network.
If the ground resistance meets the standards of relevant countries, check the dc of the
high frequency switch power system. Just switch off the high frequency switch power
system and use the accumulator battery to independently supply power for the switch.
2-23
Maintenance Manual – Troubleshooting Volume
C&C08 Digital SPC Switching System Chapter 2 Subscriber System
Check out whether there is conversation noise. If there is no noise, it indicates that
the high frequency switch power system is faulty and should be repaired.
7) Test the waveform of the clock signal.
The degradation of clock signals is also a common reason that introduces
conversation noise. To test clock signals, the following three parts should be carried
out: 1) Testing signals of the external clock source; 2) Testing clock signals output by
the CKS, BNET and other boards in the switch; 3) Testing clock signals of subscriber
HW cables. With reference to the results, carry out the following measures
accordingly.
z If the signals output by the external clock source are abnormal, clear the fault
that occurs to the external clock source.
z If the external clock source is normal but the clock signals output by the CKS are
abnormal, switch over the CKS or change it.
z If the clock signals output by the CKS are normal but those output by the BNET
are abnormal, switch over the BNET or change it after confirming that the
transmission system is normal (including QSI, OBC, OPT, ET16).
z If the clock signals output by the BNET are normal and those output by
subscriber HW cables are abnormal, check the length, binding and appearance
of the two HW cables of the subscriber frame. If the fault has not been located
yet, use new HW cables to check it out.
2-24
Maintenance Manual – Troubleshooting Volume
C&C08 Digital SPC Switching System Chapter 2 Subscriber System
Note:
z Displayed on the oscillograph, the degradation of clock signals is expressed by the
severe distortion of Transistor-Transistor Logic (TTL) level of 2 Mbit/s and 8 kHz
signals (zigzag edge, insufficient amplitude, much more burr interference when
superimposed).
Wrong
Right
Sliding
2M
FCK(8k)
Wrong
IV. Possible causes for too low or too loud conversation voice
Serial
Fault causes Remarks
No.
The line loop
It is a common reason that causes too low
1 resistance is too
conversation voice.
large.
The faults may be the aging of components or
devices, faulty components, or improper gain
2 The ASL is faulty.
control, which may cause too loud conversation
voice.
2-25
Maintenance Manual – Troubleshooting Volume
C&C08 Digital SPC Switching System Chapter 2 Subscriber System
Type the STR RTSTI command on the maintenance console, select "Loop test" in the
[Test type] field and tick "Resistance" in the [Loop test option] field. Then specify other
related parameters and press <F9> to run this test program. With reference to the test
result, the following qualitative judgement can be known.
The loop resistance is too large if it is far more than 1,800 ohm. To solve the problem,
use one of the following two methods.
Method 2: Repair or change the subscriber external line to lower the loop resistance.
2) Judge whether the ASL is faulty.
If no problem has been found in the subscriber external line, check whether the ASL
is faulty.
Connect the subscriber Wire A and Wire B to a testing telephone on the distribution
frame to test. If the conversation is normal, it indicates that the ASL has no fault.
Otherwise, change the ASL.
3) Judge whether the subscriber telephone is faulty.
Use a normal telephone to replace the original one and check out the change of the
conversation quality.
Cross-talk is primarily introduced by line faults. To locate the fault, analyze specific
fault phenomena and make judgment. The table below lists the ways to analyze the
fault causes.
Serial
Fault causes Remarks
No.
Insulation between different subscriber lines has
Insulation damage
been damaged, causing conduction between each
1 occurs to
other. In this case, the cross-talk voice is relatively
subscriber lines.
husky and has an impure tone.
2-26
Maintenance Manual – Troubleshooting Volume
C&C08 Digital SPC Switching System Chapter 2 Subscriber System
VII. Suggestions
I. Detailed description
When subscribers of a half or an entire frame get faulty, the following failures are
possible.
z No feed for the telephone
z Cannot call in
z No dial tone
z Loud conversation noise
Serial
Fault causes Remarks
No.
The fuse on the
When the fuses F1 and F2 have been completed
backplane of the
1 blown, there shall be no feed for the subscribers
subscriber frame is
of the entire frame.
blown out.
The backplane of
It usually cause faults such as cannot call-in or
2 the subscriber frame
loud conversation noise.
is faulty.
The DRV offers functions such as dual-tone
number receiving, subscriber line signaling
transfer and HW cable signal driving, and so on,
usually configured in pairs in the subscriber
frame. When one fails and the mutual-aid function
3 The DRV is faulty.
has not been normally in service, there will be
such faults as cannot call-in or no dial tone for
subscribers of a half frame. In a severe situation,
even subscribers of the entire frame shall be
affected.
2-27
Maintenance Manual – Troubleshooting Volume
C&C08 Digital SPC Switching System Chapter 2 Subscriber System
Serial
Fault causes Remarks
No.
The NOD is a communication bridge between the
host and individual boards and also is a
communication node when transferring the
subscriber line signaling.
When the two NOD cables from a subscriber
frame are connected to the NOD, there will be no
dial tone for the subscribers of the entire frame, or
the "Cannot call-in" fault occurs once the NOD
4 The NOD is faulty.
fails. In addition, all boards in the subscriber
frame cannot finish the registration on the
maintenance console.
When only a NOD cable from a subscriber frame
is connected to the NOD, there are usually such
faults as increasing call loss, slow call connection,
or much more times of no dial tone after hooking
off, once the NOD fails.
1) Check whether the power supply circuit of the subscriber frame is normal.
Check whether the fuses F1 and F2 on the backplane of the subscriber frame have
been blown out, or use a universal meter to check whether they have a voltage of
–48 V.
If the fuses have been blown out, change them in accordance with operation
procedures.
2) Check whether the backplane has been broken down, electrically burned or
blown out.
2-28
Maintenance Manual – Troubleshooting Volume
C&C08 Digital SPC Switching System Chapter 2 Subscriber System
When there is no feed for subscribers over an extensive area, it is usually caused by
lightning stroke or over-voltage. To clear the fault, carefully check whether the
backplane has been broken down, electrically burned or blown out.
Indicat Colo
Description Meaning Normal status
or r
Power
ON when the power supply
VCC Red supply ON
is normal.
indicator
Running
ON for one second and OFF
Gree indicator of
NOD0 for another second when in Flashes
n Master node
normal running status.
#0
Running
ON for one second and OFF
Gree indicator of
NOD1 for another second when in Flashes
n Master node
normal running status.
#1
Running
ON for one second and OFF
Gree indicator of
NOD2 for another second when in Flashes
n Master node
normal running status.
#2
Running
ON for one second and OFF
Gree indicator of
NOD3 for another second when in Flashes
n Master node
normal running status.
#3
Method 2: Replace the suspected NOD by a spare one and check out the change.
3) Check whether the NOD cables are faulty.
Broken NOD cables and poor contact are common reasons that cause the fault
"Cannot call-in". Use the ways below to check the NOD cables.
z Carefully check whether there is obvious loose connector connection or broken
cables.
z Use new NOD cables to replace the ones of the subscriber frame and check out
the change.
2-29
Maintenance Manual – Troubleshooting Volume
C&C08 Digital SPC Switching System Chapter 2 Subscriber System
VII. Suggestions
I. Detailed description
When the fault "Intra-module traffic totally blocked" occurs, all the subscribers in a
local module, for example, SM and RSM, cannot make a call, that is, intra-module
connection fails.
2-30
Maintenance Manual – Troubleshooting Volume
C&C08 Digital SPC Switching System Chapter 2 Subscriber System
Serial
Fault causes Remarks
No.
When there is a sudden traffic increase which
The CPU of the fails the CPU processing capability, the module
1
MPU is overloaded. can no longer process any call, consequently,
leading to the traffic being totally blocked.
1) Check whether the power supply system of the switching module is faulty.
Power supply fault is the common reason that causes the fault "Intra-module traffic
totally blocked". To clear the fault, therefore, first check whether the power supply
system of the switching module is faulty or abnormal.
The switch's nominal voltage is -48 V and the allowed voltage range is -40 V ≤ U ≤
-57 V. To check it out, the following ways may be used.
z Check whether the power supply boards PWS, PWC and PWX have -48 V input.
z Measure the bus voltage by a universal meter and check whether the voltage is
in the range of -40 V ≤ U ≤ -57 V.
If such faults occur to the power supply system as power failure, low-voltage or
over-voltage, check or repair the power system of the switching module.
2) Adopt proper measures to restore the system.
If the power system is working normally, the fault is surely caused by some inner
reasons. In this case, carefully observe the MPU indicators. If the RUN indicator is
always ON or always OFF, it indicates that the MPU is faulty or working abnormally.
At this time, try to backup as many bills as possible and reset the main control frame
2-31
Maintenance Manual – Troubleshooting Volume
C&C08 Digital SPC Switching System Chapter 2 Subscriber System
of the switching module, or switch off the power of the main control frame then switch
on.
3) Contact technical support engineers.
Whatever the inner reasons are, save all alarm information and contact technical
support engineers in time.
IV. Suggestions
The occurrence of area busy traffic is a common reason that leads to this fault. To
clear the fault, therefore, it is necessary to regularly monitor and measure traffic, to
find the primary reasons that cause busy traffic and apply preventive procedures
accordingly.
I. Detailed description
Blocked inter-module traffic refers to the case that subscribers or trunks of some
modules fail to make calls to other modules, that is, inter-module connection fails (but
intra-module calls are normal). The following cases are included.
z Traffic between SM and AM/CM has been totally blocked.
z Traffic between RSM and AM/CM has been totally blocked.
Serial
Fault causes Remarks
No.
It will cause the traffic between SM and AM/CM or
1 The QSI is faulty.
between RSM and AM/CM to be totally blocked.
2-32
Maintenance Manual – Troubleshooting Volume
C&C08 Digital SPC Switching System Chapter 2 Subscriber System
IV. Suggestions
The transmission faults and board damages are common reasons that cause the
intra-module traffic blocked. To prevent the fault, it is recommended to regularly
examine the transmission equipment and view alarm information so as to know or find
abnormal situations in time.
I. Detailed description
When the global traffic has been totally blocked, it is of a catastrophic failure of the
switch. It may be represented in the following two cases.
2-33
Maintenance Manual – Troubleshooting Volume
C&C08 Digital SPC Switching System Chapter 2 Subscriber System
z Inter-office trunks have been totally blocked. In this case, the switch cannot
process any incoming or outgoing calls.
z Inter-module traffic has been totally blocked. In this case, calls between modules,
which may be SM or SPM connected through AM/CM, cannot be established.
Serial
Fault causes Remarks
No.
It may cause all inter-office trunks to be out of
1 The SPC is faulty.
service, and consequently to be totally blocked.
The switch's nominal voltage is –48 V and the allowed voltage range is -40 V ≤ U ≤
-57 V. To check it out, use the following ways.
z Check whether the power supply boards PWS, PWC and PWX have an input of
–48 V.
Huawei Technologies Proprietary
2-34
Maintenance Manual – Troubleshooting Volume
C&C08 Digital SPC Switching System Chapter 2 Subscriber System
z Measure the bus voltage by a universal meter and check whether the voltage is
in the range of -40 V ≤ U ≤ -57 V.
If such faults occur to the power system as power failure, low-voltage or over-voltage,
check or repair the switch's power system.
2) Check whether the transmission network is working normally.
The fault "Global traffic totally blocked" is a catastrophic failure for a switch. To
prevent any mis-operation, check whether the transmission network is normal
(primarily to check whether the transmission network has been interrupted) after
ensuring that there is no power fault. Use the following ways.
z Observe the indicators on the boards ET16, STU, and so on. If the "FAIL" alarm
occurs to all inter-office trunk boards, the transmission network may be totally
interrupted.
z View the alarm information on the alarm panel and find whether there is any
critical transmission interruption alarm and the alarmed trunk office direction.
z Contact the transmission maintenance staff in time to know the running situation
of the transmission network.
If it is the transmission network that has caused the fault, the switch maintenance staff
should cooperate with the transmission service department to clear faults and restore
the system.
3) Judge whether the SPC, CDP and Communication Control Module (CCM) frame
are working normally.
If both power system and transmission network are working normally, it is surely the
switch's inner reasons that cause the global traffic totally blocked. The SPC, CDP or
CCM frame may get faulty. Use the following ways to check it out.
z Carefully observe the indicators on the active CDP, SPC, FSN and BAC to know
their running status. If the indicator "RUN" flashes quickly or is always OFF and
the indicator "FAIL" always ON, the board may be abnormal or get faulty.
z Carefully analyze the alarm information on the alarm panel and check whether
there is any software or hardware alarm of system level, for example, CPU
overload or switchover failed.
4) Adopt proper measures to restore the system.
If above faults or exceptions occur, it indicates that the switch's AM/CM has failed to
work normally. In this case, use the following measures to restore the system.
z Backup the system data, which is an essential operation, including the following
contents.
Bills: Use the RST BILPOL command to update charging meters & statistical
meters and use the STR BILIF command to fetch bills.
2-35
Maintenance Manual – Troubleshooting Volume
C&C08 Digital SPC Switching System Chapter 2 Subscriber System
BAM database and registry (BAM stands for Background Administration Module):
User the BKP DB command.
z Switch over the control boards Administration Processor Board (AMP), SPC, and
so on, to eliminate possible hardware or software faults. Type the SWP BRD
command on the maintenance console. Type the module number of the AM in
the [Module] field and select "MPU" or "SPC" in the [Card type] field. After
confirmation, press <F9> to carry out the command.
z Perform leveled reset. Type the RST EX command on the maintenance console.
Type the module number of the AM in the [Module] field and select an option in
the [Reset level] field. After confirmation, press <F9> to carry out the command.
z Switch off the power to reset AM/CM. If the fault has not been cleared yet after
the switchover and leveled reset, switch off the AM/CM power and then restart it.
When restarting the AM/CM frames, follow the sequence: Clock Module (CKM)
-> CCM -> Central Processing Module (CPM) -> Central Switch NET Frame
(CNET) -> Line Interface Module (LIM) frames -> Specialized Resource Module
(SRM) frames -> Service Processing Module (SPM) frames. Besides, start the
"Exchange" process to view the loading process because no more than two
frames can be simultaneously loaded.
5) Contact technical support engineers.
Whatever the inner reasons are, save all alarm information and contact technical
support engineers in time.
IV. Suggestions
The bursty traffic is a common reason that leads to the fault "Global traffic totally
blocked". To clear the fault, regularly monitor and measure traffic, to find the primary
reasons that cause busy traffic and apply preventive procedures accordingly.
I. Detailed description
This fault refers to the call exceptions that occur to SM, RSM or other modules when
their subscribers make intra-module calls, in the duration after the calling party
finishes the dialing and before the called party hooks off. The following cases are
possible.
z There are unidirectional calls. In this case, after the called party hooks off, the
calling hears the called party but the called party cannot hear the calling party, or
conversely. Such a call is a unidirectional call.
z Both the calling and called parties cannot talk to each other. In this case, after
the called party hooks off, both the calling and called parties hear nothing and
cannot talk to each other.
Huawei Technologies Proprietary
2-36
Maintenance Manual – Troubleshooting Volume
C&C08 Digital SPC Switching System Chapter 2 Subscriber System
z The call is released in the conversation process. In this case, after the called
party hooks off, both parties can talk to each other, but then the circuit
automatically restores when no party hooks on, and consequently, both parties
hear busy tone.
Serial
Fault causes Remarks
No.
The failure of the 2-wire/4-wire conversion circuit
1 The ASL is faulty.
on the ASL easily leads to unidirectional calls.
The DRV transfers both subscriber line signaling
and HW signals. Once it gets faulty, there will be
2 The DRV is faulty.
the fault "Unidirectional call" or "Call released in
the conversation process".
Connect Wire A and Wire B of the complaint subscriber to a testing telephone on the
distribution frame to simulate a call. If the conversation is normal, then the telephone
is faulty.
2) Judge whether the ASL is faulty.
2-37
Maintenance Manual – Troubleshooting Volume
C&C08 Digital SPC Switching System Chapter 2 Subscriber System
In the case that a subscriber complains the fault "Unidirectional call" when making
calls to some particular numbers, find the ASL according to the particular numbers
and check whether the board is faulty.
Method 1: Change the ASL by a spare one and call the particular numbers. Check out
the changes and you can find that whether the ASL is faulty.
Method 2: For 32-channel subscriber frame, use the speech channel continuity check
function to locate the fault.
Originate a call and hold it. Then type the CHK TELPATH command on the
maintenance console. Specify the module number & loop module which is the number
of the switching module, and select "Path self-loop circuit" in the [Operation type] field
& "User time slot" in the [Loop path type] field. Afterwards, specify other parameters in
accordance with actual situations and press <F9> to carry out the command. If the
message "Continuity check of the speech channel failed" is returned, it means that
the ASL is faulty.
Finally, select "Recovery path self-loop circuit" in the [Operation type] field to cancel
the self-loop on the speech channel. The settings of other parameters keep the same
as those described above.
3) Judge whether the DRV is faulty.
Replace the suspected DRV by a spare one and check out the change.
4) Judge whether the BNET is faulty.
For the fault "Unidirectional call" in other forms, for example, the fault only occurring
to a fixed timeslot, the timeslot seizure situation of the BNET may be viewed to help
locate the fault.
Find the HW number of the faulty subscriber and let the calling party originate calls
continuously to find the timeslot that the fault "Unidirectional call" occurs to.
Judgement can be made with reference to the following text.
z If such a faulty timeslot has been found, switch over the BNET and let the calling
party originate calls continuously once more to check whether the fault
"Unidirectional call" occurs to the corresponding timeslot. If not, it indicates that
the BNET is faulty and it is necessary to change it. If the fault still occurs, check
HW cables with reference to Step 5).
z If there is no such a faulty timeslot or there are several faulty timeslots, check the
module's clock system with reference to Step 6).
Huawei Technologies Proprietary
2-38
Maintenance Manual – Troubleshooting Volume
C&C08 Digital SPC Switching System Chapter 2 Subscriber System
Method 1: Observe the indicators on the NOD panel and check whether the
corresponding master node is in normal running status. The meanings of the
indicators are given below.
2-39
Maintenance Manual – Troubleshooting Volume
C&C08 Digital SPC Switching System Chapter 2 Subscriber System
Indicat
Color Description Meaning Normal status
or
Power supply ON when the power supply
VCC Red ON
indicator is normal.
Running ON for one second and
indicator of OFF for another second
NOD0 Green Flashes
Master node when in normal running
#0 status.
Running ON for one second and
indicator of OFF for another second
NOD1 Green Flashes
Master node when in normal running
#1 status.
Method 2: Replace the suspected NOD by a spare one and check out the change.
VI. Suggestions
Abnormal intra-module connection occurs mostly when the BNET is faulty. Therefore,
maintenance staff are recommended to have a good knowledge of timeslot observing
and clock signal testing to help clear the fault effectively.
I. Detailed description
2-40
Maintenance Manual – Troubleshooting Volume
C&C08 Digital SPC Switching System Chapter 2 Subscriber System
z The connection time is long. In this case, after the calling party finishes the
dialing, it is a long time later that the first ring back tone is given. Sometimes the
connection cannot be established.
z There are unidirectional calls. In this case, after the called party hooks off, the
calling party hears the called party but the called party cannot hear the calling
party, or conversely. Such a call is a unidirectional call.
z Both the calling and called parties cannot talk to each other. In this case, after
the called party hooks off, both the calling and called parties hear nothing and
cannot talk to each other.
z The call is released in the conversation process. In this case, after the called
party hooks off, both parties can talk to each other, but then the circuit
automatically restores when no party hooks on, and consequently, both parties
hear busy tone.
Serial
Fault causes Remarks
No.
Once the trunk or transmission boards are
The trunk and
faulty, there may be such faults as
transmission boards such
1 transmission bit error or unsteady clock
as OSI, OBC, ET16, STU,
phase-lock, consequently leading to
OPT and DTF, are faulty.
abnormal inter-module connection.
2-41
Maintenance Manual – Troubleshooting Volume
C&C08 Digital SPC Switching System Chapter 2 Subscriber System
1) Check whether the transmission bit error rate meets the requirement.
For inter-module signaling links, the transmission Bit Error Rate (BER) should be
smaller than the order 10-6. When the requirement has not been met, inter-module
signaling communication and processing may become abnormal and consequently
the connection time becomes long. Check out the following BERs.
z The output BER of the boards OPT, OLE, DTF, and so on, in SMs, RSMs or
other modules
z The output BER of the boards QSI, OBC, ET16, STU, and so on, in AM/CM
z The BER of external transmission system
Carry out the above tests by using 2 Mbit/s bit error tester, E10 meter, optical power
meter, optical time-domain analyzer, or other instrument. In addition, the sectional
loop-back may be used to check the BER of external transmission system.
Note:
To carry out the above tests, a complete & thorough plan is necessary and proper
backup procedures should be applied to reduce or avoid the speech channel
interruption time.
Note:
The board to be changed must be in active-standby or load-sharing mode. Otherwise,
the inter-module communication may be interrupted.
2-42
Maintenance Manual – Troubleshooting Volume
C&C08 Digital SPC Switching System Chapter 2 Subscriber System
If the problem has not been cleared yet, or you are not confident enough in your
judgement, contact technical support engineers in time.
Check whether the boards MC2, LPMC2, NO7, LPN7, and so on, are normal and
whether the data of inter-module signaling links has been correctly configured. Such
faults usually occur in the case of new deployment and so this manual gives no
details about them.
2-43
Maintenance Manual – Troubleshooting Volume
C&C08 Digital SPC Switching System Chapter 2 Subscriber System
When such a fault occurs to inter-module calls, first check whether it occurs to
intra-module calls. If it is, refer to relevant text in Section 2.3.11.
2) Check whether there are such exceptions that have occurred to the transmission
system as error bits, slip codes or pointer adjustment.
If the intra-module connection is normal, the fault is primarily caused by abnormal
clock synchronization between the module and the upper-level module.
z For SMs, use a bit error tester to measure the BER of inter-module optical
signals to ensure that the BERs of both directions are smaller than the order 10-7.
Otherwise, check the fiber channels (cleanness of tail optics fibers, optical
channel's attenuation decibel, and so on). Or directly change the boards OPT,
OBC, and so on, without interrupting the system or when short-time interruption
is allowed.
z For RSMs, observer the indicators of the boards DTF, ET16, STU, and so on, or
query them on the maintenance console to know their working status. Besides,
use a 2 Mbit/s bit error tester to test the PCM system's BER to ensure that the
BERs of both directions are smaller than the order 10-7. Otherwise, directly
change the boards DTF, ET16, STU, and so on, without interrupting the system
or when short-time interruption is allowed. Or check whether there are such
exceptions that have occurred to the transmission system as error bits, slip
codes or pointer adjustment. If there are, contact the transmission service
department.
In addition, sectional loop-back or channel change may be used to check whether the
transmission system is abnormal or faulty.
VII. Suggestions
To know the system's running situations and clear faults in time, it is recommended to
carefully carry out routine examination of the switching system and view the alarm
information in time. As a result, the system can run more steadily and reliably.
Abnormal inter-office connection has a close relationship with the trunk and signaling
system. This section only briefly introduces the fault locating and analysis process.
For details, refer to Chapter 3 Trunk & Signaling System.
2-44
Maintenance Manual – Troubleshooting Volume
C&C08 Digital SPC Switching System Chapter 2 Subscriber System
I. Detailed description
Abnormal inter-office connection here refers to the call exceptions that occur to
outgoing or incoming trunk calls in the SPM trunk networking mode (but the
intra-module connection is normal). The following cases are possible.
z The connection time is long. In this case, after the calling party finishes the
dialing, it is a long time later that the first ring back tone is given. Sometimes the
connection cannot be established.
z There are unidirectional calls. In this case, after the called party hooks off, the
calling party can hear the called party but the called party cannot hear the calling
party, or conversely. Such a call is a unidirectional call.
z Both the calling and called parties cannot talk to each other. In this case, after
the called party hooks off, both the calling and called parties hear nothing and
cannot talk to each other.
z The call is released in the conversation process. In this case, after the called
party hooks off, both parties can talk to each other, but then the circuit
automatically restores when no party hooks on, and consequently, both parties
hear busy tone.
Serial
Fault causes Remarks
No.
Transmission bit error has a severest impact on the
call connection and may introduce all exceptions that
The transmission
1 occur to inter-office connection. In addition, the cross
system is faulty.
connection of transmission lines is a common reason
that causes the fault "Unidirectional call".
When the clock system is abnormal, the inter-office
signaling interworking may be in disorder or the
The clock
2 exchange error may occur, consequently leading to
system is faulty.
such faults "Unidirectional call", "Call released in the
conversation process" or "Long conversation time".
Such faults may occur as unmatched CIC,
The inter-office unmatched IAI or IAM, unequally distributed signaling
signaling link loads or inconsistent definition of trunk timer
3
interworking is parameters, consequently leading to such faults
abnormal. "Cannot talk to each other", "Call released in the
conversation process" or "Long conversation time".
2-45
Maintenance Manual – Troubleshooting Volume
C&C08 Digital SPC Switching System Chapter 2 Subscriber System
To ease the fault location, first judge whether the intra-module and inter-module
connection are normal. If they are normal, carry out Step 2). If not, refer to Sections
2.3.11 and 2.3.12.
2) Check whether there are such exceptions that occur to the transmission system
as error bits, slip codes or pointer adjustment.
The failure of the transmission system is a common reason that causes abnormal
inter-office connection. The maintenance staff can make judgement and locate the
faults by using the following methods.
z Check whether the indicator "FAIL" on the boards ET16, STU, and so on, is OFF.
If it is ON, there are error bits or slip codes.
z Type the DSP E1CH command on the maintenance console and type frame
number & slot number to query the running situation of the corresponding E1
channel.
z Test the BER of the E1 channel by a 2 Mbit/s bit error tester.
z Change the boards by new ones and check the changes.
z Locate the fault by the sectional loop-back method.
3) Check whether the clock system is normal.
If the intra-module and inter-module connection are normal, the clock synchronization
with the opposite office may be abnormal.
z If the switch uses the clock supplied by Building Integrated Timing Supply (BITS),
check whether the BITS equipment is normal.
z If the switch extracts clock from the trunk, check the transmission system.
4) Check whether the inter-office signaling interworking is normal.
Abnormal inter-office signaling interworking usually causes abnormal inter-office
connection.
z Because Telephone User Part (TUP) or ISDN User Part (ISUP) CICs of C&C08
switch include Timeslot 16 but those of the switches of some vendors do not
include Timeslot 16, errors may occur when routing to the timeslots after
Timeslot 16, consequently leading to the fault "Cannot talk to each other".
z In the case of multiple signaling links, the loads carried by the signaling links of
an office direction may be unequal due to error data configuration. Thus,
overload or congestion may occur to a signaling link, consequently leading to the
faults "Long connection time" or "Call released in the conversation process".
To locate and process these faults, refer to Chapter 3 Trunk & Signaling System.
IV. Suggestions
2-46
Maintenance Manual – Troubleshooting Volume
C&C08 Digital SPC Switching System Chapter 3 Trunk & Signaling System
3.1 Overview
The C&C08 Digital SPC Switching System has a modular hierarchical structure and
flexible trunk networking. It offers abundant signaling interfaces, supports several
kinds of signaling protocols such as R2, No. 7, No. 5 and Digital Subscriber Signaling
No. 1 (DSS1) and supports the automatic identification of 24-bit and 14-bit signaling
point coding. It has Signaling Point (SP) and integrated Signaling Transfer Point (STP)
functions.
Table 3-1 lists the common faults that may occur in the trunk and signaling system.
Table 3-1 Common faults that may occur in the trunk and signaling system
The PRA trunk circuit is The circuit is displayed as such abnormal status as
abnormal. faulty, blocked, or not activated.
3-1
Maintenance Manual – Troubleshooting Volume
C&C08 Digital SPC Switching System Chapter 3 Trunk & Signaling System
Table 3-2 lists the common fault causes that may occur in the trunk and signaling
system.
Table 3-2 Common fault causes that may occur in the trunk and signaling system
3-2
Maintenance Manual – Troubleshooting Volume
C&C08 Digital SPC Switching System Chapter 3 Trunk & Signaling System
It is used to exclusively identify a trunk circuit between two switches. Its length is
twelve bits. It only occurs in the TUP or ISUP message signaling unit. Therefore, one
office direction can have 212=4096 trunk circuits at most.
In two switches interconnected through No. 7 signaling, only when the CICs of the
same trunk circuit are identical, can the two switches be successfully interconnected.
It is used to route the signaling links between two switches, so as to fulfill the load
sharing. Its length is four bits. Therefore, one office direction can have 24=16 link
selection solutions.
3-3
Maintenance Manual – Troubleshooting Volume
C&C08 Digital SPC Switching System Chapter 3 Trunk & Signaling System
For the TUP or ISUP message, SLS is the lower four bits of the CIC of the
corresponding message signaling unit. For the MTP message, its value is the
Signaling Link Code (SLC) of the corresponding link.
It is used to identify the signaling links between two switches. Its length is four bits.
Therefore, one office direction can have 24=16 signaling links at most.
In two switches interconnected through No. 7 signaling, only when the SLCs of the
same signaling link are identical, can the two switches be successfully interconnected.
The function of the SLC is similar to that of the CIC.
In the TUP, the IAM (or IAI) is the first message sent when the call is established.
Generally it includes all information that is necessary for the next switching office to
determine the route for the establishment of the call, for example, caller category,
charging attribute and called number. Besides, the IAI includes caller line
identification information. The coding format of the IAM or IAI is shown in Figure 3-1.
Standby
IAI
Charging Original Calling Additional Subscriber Closed subscriber National First indicator
infomation caller address line indetify routing info information group information application octets
Note:
In the ISUP, there is only IAM message, the function of which is similar to that of the
IAI in the TUP.
3-4
Maintenance Manual – Troubleshooting Volume
C&C08 Digital SPC Switching System Chapter 3 Trunk & Signaling System
The initial location is a process that must be undergone before the link enters the
service usage status. It is used for the link alignment during the initial activation of the
link or the recovery of the link when the link is faulty. The initial location function is
fulfilled by the Status Field (SF) in the Link Status Signal Unit (LSSU). The six kinds of
status of the LSSU are shown in the following table:
SPA SPB
Idle Idle
LSSU(SIO)
LSSU(SIO)
Not aligned Not aligned
LSSU(SIN)
Normal Normal
acceptance acceptance
cycle cycle
FISU
Entering Entering
MSU
service service
usage usage
3-5
Maintenance Manual – Troubleshooting Volume
C&C08 Digital SPC Switching System Chapter 3 Trunk & Signaling System
I. Overview
The C&C08 CAS system features powerful functions and good adaptability. At present,
it provides the R2 Signaling and No. 5 signaling, both of which measure up to the ITU
Telecommunications Union - Telecommunications Sector (ITU-T) recommendations
and European Telecommunications Standards Institute (ETSI) standards. It’s special
feature is its adaptability and compatibility. It is adaptable to most of the national
standards of various countries by data configuration.
The SM CAS system provides full-set functions of R2 and No. 5. The R2 signaling
provides 2-bit line signaling, 1-bit line signaling, pulse line signaling, as well as
register signaling of the MFC, Multi-frequency Pulse (MFPS), DTMF, decimal pulse.
The No. 5 signaling provides the standard dual frequency (2VF) line signaling and
MFP register signal. Any of them can be configured based on the service
requirements. The functional modules in the C&C08 switching system is as shown in
Figure 3-3, where the DTF deals with line signals as well as decimal pulse register
signals; and the MFC or DTR or RSD5 with rest register signals. The receiving and
sending of physical signals are performed by the DTF, DTR, MFC or RSD5, while the
signaling flow processing is performed by the MPU in the SM. The signaling
processing in SMs is independent from one another.
AM/CM
MPU(R2,NO5)
SM
SM
SM
DTF MFC/DTR/RSD5
3-6
Maintenance Manual – Troubleshooting Volume
C&C08 Digital SPC Switching System Chapter 3 Trunk & Signaling System
The SPM processes services and protocols. The ET16 provides 16 E1s externally
and each E1 provides R2 signaling interface or No. 5 signaling interface according to
different configurations. The ET16 processes the line signal of R2 signaling and the
SRC processes the register signal of R2 signaling, including MFC, MFPS & DTMF.
The communication between the SRC and SPC is transferred through the AMP. The
ET16 processes both line signal and register signal of No. 5 signal independently,
without need of other boards, as shown in Figure 3-4.
AM/CM
SPC(R2,NO5)
SPM
SPM
SPM
ET16 SRC(R2)/ET16(NO5)
IV. R2 signaling
In the SM CAS system, the DTF provides the digital trunk interface and line signal
identification of the R2 signaling. Each DTF provides two PCM systems of 60 circuits
in total. The line signal is identified through detecting the TS16 of the PCM system.
The MFC identifies and sends the multi-frequency signals in the speech channels and
each MFC processes 32 channels simultaneously. The access of the R2 signaling is
as shown in Figure 3-5.
3-7
Maintenance Manual – Troubleshooting Volume
C&C08 Digital SPC Switching System Chapter 3 Trunk & Signaling System
DTF
Voice path
MFC/DTR
NOD
Bus
In the SPM CAS system, the ET16 provides the digital trunk interface and line signal
identification of the R2 signaling. The E1 interface TS16, which is configured as R2
signaling, is used to send and receive R2 signaling line signal or decimal number
pulse signal. The SRC processes different types of the R2 signaling register signal
through the terminal configuration, including MFC, MFPS and DTMF. SRC channels
are allocated dynamically in the call and are connected with the ET16 timeslots
through the NCC. It then sends and receives R2 multi-frequency signal through the
speech channel. The access of the R2 signaling is as shown in Figure 3-6.
ET16
Speech channel
SRC
Active SPC
The C&C08 R2 signaling system serve as both international and national signaling at
the same time, in automatic or semiautomatic modes.
V. No. 5 signaling
In the SM CAS system, the DTF provides the digital trunk interface and line signal
identification of the No. 5 signaling. Each DTF provides two PCM systems of 60
circuits in total. The line signal is identified through detecting the two audio signals in
3-8
Maintenance Manual – Troubleshooting Volume
C&C08 Digital SPC Switching System Chapter 3 Trunk & Signaling System
speech channel. The RSD5 identifies & sends the multi-frequency signals in the
speech channels and each MFC processes 32 channels simultaneously. The access
of the No. 5 signaling is as shown in Figure 3-7.
DTF
Speech channel
RSD5
NOD
Bus
In the SPM CAS system, the digital trunk interface of the No. 5 signaling is provided
by the ET16. Both line signal and register signal of the No. 5 signaling are inband
audio signals, which are transmitted in the speech channel. The ET16 processes the
line signal and register signal of the No. 5 signaling at the same time.
I. Detailed description
When the No. 7 trunk circuit is queried, the system displays the following abnormal
status:
z Faulty. When the Destination Point Code (DPC) is unreachable or the PCM
system gets faulty, the circuit enters this status if it is not blocked.
z Available blocking. It indicates that the opposite circuit has already been blocked.
In this status, you can originate outgoing calls, but the circuit will not receive
incoming calls.
z Unavailable blocking. It indicates that the local circuit has been blocked (the
opposite end or the local end is blocked). In this status, outgoing calls are barred,
but the incoming calls can be received.
3-9
Maintenance Manual – Troubleshooting Volume
C&C08 Digital SPC Switching System Chapter 3 Trunk & Signaling System
z Unknown. After the circuit or the circuit group to where the circuit belongs has
originated the reset message (Reset Circuit (RSC) and Circuit Group Reset
(GRS)), the circuit enters this status.
z Not installed. It indicates that the data of this trunk circuit has not been
configured yet.
Serial
Fault causes Remarks
No.
There is a transmission
1
interruption or error bit. The circuit may enter such abnormal
Trunk boards such as ET16, statuses as "Faulty".
2
STU, DTF are faulty.
When trunk circuit data is not configured,
the circuit may enter the "Not installed"
Data is not configured or the status.
3
configuration is wrong. When DPC data is not configured or the
configuration is wrong, the circuit may
enter the "Faulty" status.
CPU overload causes the The circuit may enter the "Available
4
congestion control. blocking" status.
3-10
Maintenance Manual – Troubleshooting Volume
C&C08 Digital SPC Switching System Chapter 3 Trunk & Signaling System
z Observe the panel indicators of such boards as ET16, STU and DTF and check
whether in the PCM system there are such alarms as frame out-of-sync., slip
code and Cyclic Redundancy Check (CRC) error.
z Type the DSP E1CH command on the maintenance console to display the
information of the specified E1 channel. Then type the corresponding frame
number and slot number as well as other related parameters. Press <F9> to
carry out the query command and check whether in the PCM system there are
such alarms as frame out-of-sync., slip code and CRC error according to the
results sent back.
z Use the bit error tester and PCM analyzer to measure the BER of the E1 channel
(it should be less than the order 10-6).
2) Check whether the trunk boards are faulty or abnormal.
z In the C&C08 Maintenance Tool Navigator on the maintenance console, select
[Config/hardware configuration status panel]. Open the configuration status
interface and observe whether the status of such boards as ET16, STU and DTF
in the related module is normal.
z Use the DSP BRD command to query the online running status of the boards.
If the boards are in faulty, then the problem can be solved through software resetting
(RST BRD), hardware resetting and change of boards.
3) Check whether the destination signaling point is reachable.
In the C&C08 Maintenance Tool Navigator on the maintenance console, select [No. 7
signaling/No.7 signaling relative state query]. Open the dialog box "No.7 signaling
relative state query" and select "destination point status" from the "query type". Then
type the corresponding module number and DPC index number and click <OK> to
carry out the test command.
If the returned value is "NULL", it indicates that the destination signaling is reachable.
If other values are returned, it indicates that the destination signaling point is
unreachable. In this case, take the following measures.
z Check whether the DPC data configuration of the office direction is correct. The
pertinent query commands include LST OFC which is to query the office
direction information, and LST N7DSP which is to query the destination signaling
point.
z Check whether the signaling link is faulty. The option [No.7 signaling/No.7
signaling relative state query] in the C&C08 Maintenance Tool Navigator on the
maintenance console can be used to perform the query.
4) Take other methods.
If the causes of the fault are complicated and the fault cannot be located through the
above methods, perform sectional loop-back to locate the fault step by step.
The methods of the loop-back include hardware loop-back and software loop-back,
and the directions of the loop-back include local loop-back and remote loop-back.
3-11
Maintenance Manual – Troubleshooting Volume
C&C08 Digital SPC Switching System Chapter 3 Trunk & Signaling System
3-12
Maintenance Manual – Troubleshooting Volume
C&C08 Digital SPC Switching System Chapter 3 Trunk & Signaling System
The direct cause of the "unknown" status of the circuit is that the switch has sent
reset message (RSC, GRS) to the circuit or the circuit group to which the circuit
belongs. If the circuit remains in the "unknown" status, it indicates that the switch has
not received the acknowledgement message Release Guard (RLG) or Circuit Group
Reset Acknowledgement (GRA) from the opposite office and keeps sending reset
messages. Therefore, the essence of fault locating is to find the cause that makes the
switch keep sending RSC or GRS messages.
1) Check whether signaling links are faulty.
When signaling links are congested or the error rate becomes too high, the signaling
messages may be lost. After sending the reset message, the originating office may be
unable to receive the acknowledgement message RLG or GRA from the opposite
office, which resultantly makes the trunk circuit enter the "unknown" status. In this
case, the system generates alarms, according to which the running status of the
signaling links can be known. Or use the LST N7LNK command to query the status of
the MTP link.
Generally, when the signaling links recover to the normal status, the fault can be
removed. If the fault cannot be removed even though the signaling links become
normal, that is, the trunks are "suspended", then trunk circuits respectively
corresponding to the local office and the opposite office must be reset manually.
2) Check whether the inter-office CICs match each other.
CIC is a key parameter for the interconnection between the TUP and the ISUP. Only
when the CIC of one switch remains strictly consistent with that of another switch, can
the trunk circuit keeps normal. As different manufacturers have different
understandings and definitions of CIC, the CIC of one may not match that of the other
during the interconnection of their switches.
The unmatched CIC results in errors in the acknowledgement message sent back by
the opposite office when the abnormal circuit need be reset. Consequently, the
originating office keeps sending circuit or circuit group reset messages and the trunk
circuit enters the "unknown status". In this case, negotiation with the opposite office is
needed to ensure the consistence of the CICs.
The major cause of the status "circuit not installed" is that the data of the concerned
trunk circuits has not been configured. Therefore, the circuit will become normal after
the addition of the data and normal interconnection with the opposite office.
3-13
Maintenance Manual – Troubleshooting Volume
C&C08 Digital SPC Switching System Chapter 3 Trunk & Signaling System
For the configuration of the trunk data, refer to the relevant procedures for configuring
the office data.
VII. Suggestions
An effective method to learn the running status of the trunk system is to frequently
check the alarm system and timely learn the alarm information.
I. Detailed description
Abnormal trunk circuit maintenance means that the circuit status is displayed as
"faulty" or "unknown" if it is queried, during such maintenance operations as blocking,
unblocking or resetting the trunk circuit through the man-machine commands, when
the system does not respond or prompts that the operation times out.
When the originating office is carrying out a command to block, unblock or reset a
circuit, it sends to the opposite office the corresponding blocking, unblocking (remote
end) or resetting circuit messages. If the originating office has not received expected
acknowledgement messages from the opposite office, it will prompt "no response" or
"timed-out". As in this case the circuit status is "faulty" or "unknown", the fault can be
located with reference to the relevant procedures in 3.3.1 Abnormal No. 7 Trunk
Circuit. The concrete location process will not be introduced here.
I. Detailed description
3-14
Maintenance Manual – Troubleshooting Volume
C&C08 Digital SPC Switching System Chapter 3 Trunk & Signaling System
Serial
Fault causes Remarks
No.
Transmission interruption may make the link
broken.
Transmission intermittent bursting, error bit
in transmission and poor contact of trunk
There is a transmission cable, and so on, may raise the error rate of
1
fault. the link and increase the times of message
retransmission between switches. When the
case reaches to a serious degree, the link
performs initial location frequently. This can
make the link congested or unstable.
3-15
Maintenance Manual – Troubleshooting Volume
C&C08 Digital SPC Switching System Chapter 3 Trunk & Signaling System
Self-loop methods include hardware self-loop and software self-loop, and the
directions of self-loop include local self-loop and remote self-loop. The commonly
used software self-loop commands are briefly introduced as follows:
z ET16 self-loop test command STR E16LOPT
z STU self-loop test command STR STUSLP
z CPC link self-loop test command STR LNKTST
When No. 7 signaling link undergoes the self-loop test, judgments can be made
through the following methods, if you don't want to modify any self-loop parameter
such as CIC, SLC and DPC.
z If the signaling point is normal, the link can normally be located at the second
layer, and the link location will be displayed as normal after the self-loop. As
such parameters as CIC, SLC and DPC do not match, however, the link will be
broken again because it cannot pass the third-layer test, and it enters the initial
location process again. In the link status, these are shown as "bursting
intermittently once every one minute" cyclically.
z If the signaling point is abnormal, the link will be "always broken" after the
self-loop.
3-16
Maintenance Manual – Troubleshooting Volume
C&C08 Digital SPC Switching System Chapter 3 Trunk & Signaling System
will increase. When the case reaches a serious degree, the link may lose the location
and perform location again. This makes the running of the link unstable. Use the
following two methods to check whether the BER is over-high.
z Observational measurement: It means to observe whether error bit indicators of
switch trunk boards and transmission equipment are ON.
z Quantitative measurement: It means to use instruments such as bit error tester
and PCM analyzer to test the E1 channel, so as to obtain the accurate value of
the BER.
2) Check whether related boards in the switch are abnormal or faulty.
Check the running status of such boards as protocol processing boards, trunk boards
and NET boards that are related to the signaling links.
z For the SPM, there are SNU, QSI, MHI, ET16, STU, CPC, and so on.
z For switching modules, there are DTF, BNET, LPN7 and NO7, and so on.
Generally, when these boards get abnormal or faulty, abnormities of other signaling
links or trunk circuits will occur, and comprehensive analysis can be made
accordingly.
Besides, carry out the DSP BRD command query the status of a specific board. If
necessary, such methods as switchover, resetting or change of boards can be used
for the location if the system operation allows.
3) Check whether the MTP link data is correct.
The SLC and DPC are important parameters during the interconnection between
signaling links. When the DPC configuration is wrong or the SLC does not match the
opposite end, the link cannot pass the third-layer MTP service test. That is, the link
cannot carry signaling services. In this case, the system will perform initial location to
the link again. As the data configuration is wrong, the above process will repeat again
and again and the link cannot run normally. As a result, the link becomes unstable.
The setting of the DPC can be known through the network layout, while the SLC must
be set through negotiation between the two offices concerned.
If the local end is required to match the SLC of the opposite end, the C&C08 switch
offers the setting "send SLC" to fulfill the change of the SLC, so as to ensure that the
local end matches the SLC of the opposite end. The modification command is MOD
N7LNK.
The cause for the blocking of the link is that the local end has received the LSSU or
SIPO message sent by the remote end, which makes the processing of the message
above the third layer impossible.
There are two possible causes that make the remote end send the message:
3-17
Maintenance Manual – Troubleshooting Volume
C&C08 Digital SPC Switching System Chapter 3 Trunk & Signaling System
z The remote processor is faulty and the system automatically sends the SIPO
message.
z The link blocking command has been carried out manually at the remote end and
the system sends the SIPO message through carrying out the man-machine
command.
In this case, contact the opposite end to find the actual cause of the broken link, so as
to restore the link as soon as possible.
When the link is congested, the system will report the fault through the alarm system.
Generally, you can query the alarm information to find the preliminary cause and get
appropriate proposals according to the given recovery advice. Besides, you can use
the following procedures to locate the blocked links.
1) Check whether the transmission network is working normally.
Such abnormities as transmission intermittent bursting and error bit raise the BER of
the link and increase the times of message retransmission between switches. This
increases the time delay of message transmission and makes the link congested.
When the case reaches a serious degree, the link frequently performs switchover and
switchback. As a result, the link becomes unstable and congested.
To know the running status of the transmission system, use the following methods.
z Observe the indicators of such boards as ET16, STU and DTF.
z Use such instruments as bit error tester and PCM analyzer to perform bit error
test on relevant channels.
z Contact the transmission service department to learn the running state of the
transmission system.
2) Check whether related boards in the switch are abnormal or faulty.
Check the running status of such boards as protocol processing boards, trunk boards
and NET boards that are related to the signaling links:
z For the SPM, there are SNU, QSI, MHI, ET16, STU, CPC, and so on.
z For independent switching modules such as TSM and UTM, there are DTF,
BNET, LPN7 and NO7, and so on.
Generally, when these boards get abnormal or faulty, abnormities in other signaling
links or trunk circuits will occur, and comprehensive analysis can be made
accordingly.
Besides, use the DSP BRD command to query the status of a specific board. If
necessary, such methods as switchover, resetting or change of boards can be used
for the location if the system operation allows.
3) Check whether the signaling network is running normally.
3-18
Maintenance Manual – Troubleshooting Volume
C&C08 Digital SPC Switching System Chapter 3 Trunk & Signaling System
When the signaling network gets faulty, one of the protective measures is to switch
over the faulty signaling links. If the signaling load between two offices is relatively
large, some signaling links may be overloaded and consequently congested after the
switchover. In this case, generally there will be other link faults such as link broken or
blocked. Therefore, analyze comprehensively the running situation of the signaling
network, especially the STP .
4) Check whether the data configuration is correct.
If in the switch database, the "link set selection code" and the "link selection code" are
the same, it will be impossible to select some of the signaling links in normal situation.
This makes the load of the signaling links to an office uneven. When the link traffic
increases, links with heavy load will be congested.
In order to fulfill the load sharing among signaling links, "1" in the link set selection
mask and that in the link selection mask should be misaligned during the
configuration of the MTP link data. For example, if the link set selection mask is
"0001", then Bit 0 in the link selection mask cannot be set to "1". If the link set
selection mask is "1001", then Bit 0 and Bit 3 in the link selection mask cannot be set
to "1". The rest can be deduced by analogy.
VII. Suggestions
As the signaling link faults are closely related to the transmission quality, close
attention should be paid to the routine maintenance of the transmission equipment.
When a fault occurs, contact the transmission service department for solution.
I. Detailed description
Serial
Fault causes Remarks
No.
1 CIC does not match. It is a common fault cause.
3-19
Maintenance Manual – Troubleshooting Volume
C&C08 Digital SPC Switching System Chapter 3 Trunk & Signaling System
Serial
Fault causes Remarks
No.
The data includes "Can request caller
The setting of the data number", "Whether to request caller
2 related to the caller number", "Connecting without or with
number is inappropriate. invalid caller number", "CLI provision
mode", and "Default number".
3-20
Maintenance Manual – Troubleshooting Volume
C&C08 Digital SPC Switching System Chapter 3 Trunk & Signaling System
3-21
Maintenance Manual – Troubleshooting Volume
C&C08 Digital SPC Switching System Chapter 3 Trunk & Signaling System
1) The called party rings but the speech channel cannot be connected.
Cause: The signaling link is normal, but the CICs of the two switches do not match.
2) CID cannot be fulfilled.
Cause: "Can request caller number" and "Request caller number" have not been set
to "yes" in the trunk group data table.
3) The CID is abnormal.
Cause: The caller number, caller category or caller address attribute sent by the
opposite office are incorrect.
4) Call Failure (CFL) message is sent after the sending of the IAI (or IAM).
Possible causes include:
z The setting of charging data is wrong, and Bit 1 of the software parameter Call
testing parameter 1 is set to "0". That is, connection will not be performed if the
charging data is wrong.
z The supplementary service "call forwarding on no reply" is set for the called, and
the call forwarding fails. As a result, the opposite switch does not send any
message, and the local end sends the CFL message after the waiting times out.
5) The switch sends the CFL message on receipt of the IAI (or IAM) message.
Possible causes include:
z The switch has received a wrong called number, or the length of the called
number is incorrect.
z The prefix data configuration of the local office is incorrect.
3-22
Maintenance Manual – Troubleshooting Volume
C&C08 Digital SPC Switching System Chapter 3 Trunk & Signaling System
z The opposite office has not sent the original called number during the call
forwarding.
z There are errors in the contents of the IAI (or IAM) message. For example, such
parameters as caller category and channel ID are wrong.
V. Suggestions
No. 7 signaling interworking is complicated. It is not only related to the setting of data
and software parameters, but also the understanding and processing mode of the
signaling protocols by the switching equipments of different vendors. Therefore, to
resolve this kind of problem, you are required to
z be familiar with No. 7 signaling program and the basic signaling flow.
z master the meanings of the parameters in the relevant data tables and the
relations between the tables.
z master the application of such analysis tools as "dynamic connecting tracing"
and "No.7 signaling tracing".
z contact the maintenance personnel of the opposite office in time.
Note:
Faults of channel associated signaling are similar to the faults of No. 7 signaling, and
the procedures and methods for locating or eliminating the faults are also alike. Refer
to the methods and procedures for processing No. 7 signaling faults.
Mastery of the signaling programs and basic signaling flows is the base for rapid and
correct location of signaling interworking faults. The maintenance engineers should
enrich their knowledge and accumulate experiences so as to improve the technical
ability.
z If the problem still has not been located yet, or you are not confident enough in
your judgment, or you think it is necessary to modify the software parameter
table, contact technical support engineers in time.
I. Detailed description
When the PRA trunk circuit is queried, the system may display the following abnormal
status:
3-23
Maintenance Manual – Troubleshooting Volume
C&C08 Digital SPC Switching System Chapter 3 Trunk & Signaling System
z Faulty. When the PCM system gets faulty, the circuits will enter this status if they
have not been blocked. fault
z Blocked. When the manual blocking command is carried out to the circuit or the
E1 port that includes the circuit, the circuit will enter this status. blocked
z Not activated. It indicates that after the board is configured or the E1 ported is
added, the board has not been activated. not activated
Serial
Fault causes Remarks
No.
There is a transmission
1
interruption, or error bits. The circuit may enter such kinds
Such trunk boards as ET16, STU, of abnormal statuses as "faulty".
2
DTF are faulty.
3-24
Maintenance Manual – Troubleshooting Volume
C&C08 Digital SPC Switching System Chapter 3 Trunk & Signaling System
z Use a bit error tester and PCM analyzer to measure the BER of the E1 channel
(it should be less than the order 10-6).
3) Check whether the trunk boards are faulty or abnormal.
z In the C&C08 Maintenance Tool Navigator on the maintenance console, select
[Config/hardware configuration status panel], and observe whether the status of
such boards as ET16, STU and DTF in the related modules is normal.
z Use the DSP BRD command to query the online running status of the boards.
If the boards are faulty, the problem can be solved through software resetting (RST
BRD), hardware resetting and change of boards.
4) Use other methods.
If the causes of the fault are complicated and the fault cannot be located through the
above methods, perform sectional loop-back on the trunk to locate the fault step by
step.
The methods of the loop-back include hardware loop-back and software loop-back,
and the directions of the loop-back include local loop-back and remote loop-back.
Select a concrete method according to the actual situation, and the details of the
methods will not be discussed here.
When the manual blocking command is carried out to the circuit or the E1 port that
includes the circuit, the circuit enters this status.
z First use the UBL N1C command to try unblocking. If the attempt is unsuccessful,
reset the circuit (RST N1C) to solve the problem.
z If the circuit becomes "faulty" after the unblocking, locate or eliminate the fault
with reference to the methods introduced in the "Circuit faulty location".
z If the circuit becomes "not activated" after the unblocking, locate or eliminate the
fault with reference to the methods introduced in the "Location of circuit not
activated".
Use the MNT BRD command to activate the corresponding DTF or ET16. If the circuit
becomes "faulty" after it is activated, locate or eliminate the fault with reference to the
methods introduced in the "Circuit faulty location".
VI. Suggestions
Frequent routine check and timely learning of the alarm information are effective
methods to learn the running status of the trunk system and eliminate the faults in
time.
3-25
Maintenance Manual – Troubleshooting Volume
C&C08 Digital SPC Switching System Chapter 3 Trunk & Signaling System
I. Detailed description
Serial
Fault causes Remarks
No.
There is a transmission
1 The link may be broken.
fault.
3-26
Maintenance Manual – Troubleshooting Volume
C&C08 Digital SPC Switching System Chapter 3 Trunk & Signaling System
The interruption of the transmission system is a common cause of the broken link.
The key to judge whether the transmission system is interrupted is to check whether
the corresponding E1 channel has out-of-frame alarms.
IV. Suggestions
z Frequently check the equipments and master the running status of the switch in
time.
z Observe relevant principles when configuring or modifying data.
3-27
Maintenance Manual – Troubleshooting Volume
C&C08 Digital SPC Switching System Chapter 3 Trunk & Signaling System
I. Detailed description
Note:
CCB refers to the call processing module (software module) in the C&C08 switch.
2) Whether the real caller number or the default caller number should be sent
For incoming PRA trunks, the system will determine whether to send the real caller
number or default caller number to the CCB according to the network detection flag
on the DSS1 link. The network detection flag (only valid for the incoming PRA trunk)
is described as follows:
3-28
Maintenance Manual – Troubleshooting Volume
C&C08 Digital SPC Switching System Chapter 3 Trunk & Signaling System
The following text describes Bit 10 of the software parameter Call internal parameter
3 (P51).
z When the network detection flag is set to "no", only national numbers will be
transparently transmitted to the CCB. If complete caller numbers need be
transparently transmitted, then not only the network detection flag must be set to
"no", but Bit 10 of Call internal parameter 3 must be set to "0". The modification
command is MOD PRA.
z When the network detection flag is set to "yes", Bit 10 of Call internal parameter
is invalid.
For the default caller number of the PRA trunk group, if the DDI service is unavailable,
the called number will have the area code, which may make the connection
unsuccessful.
The function is suitable to the case that the gateway interconnected with a C&C08
switch does not support overlap sending. During the application of the function, pay
attention to the following points.
z The function can only send the number after the complete number has been
received (that is, judge whether the received number has reached the maximum
3-29
Maintenance Manual – Troubleshooting Volume
C&C08 Digital SPC Switching System Chapter 3 Trunk & Signaling System
number length), or after the timer times out. Therefore, it recommended that the
maximum number length be set to the same as the actual number length so that
the connection speed will not be affected.
z If the actual number length is shorter than the maximum number length, there
will be a delay of five seconds when the number is being sent. Therefore, unless
it is necessary it is recommended that the function of PRA group code sending
be cancelled. The function is controlled by Bit 6 of Call testing parameter 3 (P55),
the default value of which is "1", that is, not to start.
The problem can be solved through the modification of Bit 11 of Call internal
parameter 3 (P51) to "0". The modification command is MOD SFP.
VI. The call-in authority, call-out authority and charging of the PRA trunk
1) The call-in authority and call-out authority of the PRA trunk are fulfilled through
the call-in authority and call-out authority of the default caller number of the PRA
trunk group. In addition, it should be pointed out that the call-in authority refers to
the incoming authority of the PRA trunk, while the call-out authority refers to the
outgoing authority of the PRA trunk.
2) The charging of the PRA trunk group is fulfilled through the charging attributes of
the default caller number of the PRA trunk group.
In the PRA trunk, one DSS1 link can control four PCM ports at most. In order to
identify B channels on different PCM ports, the concept "PCM interface identifier" is
introduced. The identifier is transmitted through the SETUP signal.
2) Setting PCM interface identifier
The two parties should set the parameter to the same value through negotiation.
3-30
Maintenance Manual – Troubleshooting Volume
C&C08 Digital SPC Switching System Chapter 3 Trunk & Signaling System
Note:
It is not safe to use one DSS1 to control several PCMs. Generally this mode is not
advisable, because:
z If one side of the PRA trunk has been configured with the PCM data while the
other side has not, or the interface identifier at one side is inconsistent with that at
the other side, the call cannot be connected.
z If the PCM system to which the DSS1 link belongs is interrupted, all PCMs
controlled by the link will also be interrupted.
z In actual application, not all switches (digital switches) support interface identifiers.
3-31
Maintenance Manual – Troubleshooting Volume
C&C08 Digital SPC Switching System Chapter 4 Charging & Bill System
4.1 Overview
Charging & bill system is a significant part of a switch and has a close relationship
with key indexes such as business income, cost control and customer satisfaction. It
plays a decisive role in the routine maintenance. This chapter discusses the common
faults that may occur to host charging and online charging.
Table 4-1 lists the common faults that may occur to the charging and bill system.
Table 4-1 Common faults that may occur to the charging and bill system
4-1
Maintenance Manual – Troubleshooting Volume
C&C08 Digital SPC Switching System Chapter 4 Charging & Bill System
Table 4-2 lists the common fault causes that may occur to the charging and bill
system.
Table 4-2 Common fault causes that may occur to the charging and bill system
Local Area Network (LAN) Abnormal bill fetching, BAM fails to send bills to
Hardware communication is abnormal. iGateway Bill
fault Bills lost, repeated bills, error bills,
The MPU or SPC is faulty.
extra-long-conversation-time bills
The MPU or SPC has been
Repeated bills, extra-long-conversation-time bills
abnormally switched over.
4-2
Maintenance Manual – Troubleshooting Volume
C&C08 Digital SPC Switching System Chapter 4 Charging & Bill System
C&C08 Digital SPC Switching System offers the following charging modes.
It is applied to calls between ordinary subscribers of a local office in the case that the
calling party is charged. The key data fields are given below.
z Caller charging source code
It is the calling party's "Charging source code" in the subscriber data table. To query it,
carry out the LST ST command.
z Called charging source code
4-3
Maintenance Manual – Troubleshooting Volume
C&C08 Digital SPC Switching System Chapter 4 Charging & Bill System
It is the called party's "Charging source code" in the subscriber data table. To query it,
carry out the LST ST command.
It is used to charge the called party. The key data field is given below.
z Called charging source code
It is the called party's "Charging source code" in the subscriber data table. To query it,
carry out the LST ST command.
It is applied to calls between Centrex intra-group subscribers. The key data field is
given below.
z Centrex group number
It is the calling party's "Centrex group number" in the subscriber data table. To query it,
carry out the LST ST command.
It is applied in the case that subscribers of a local office use supplementary services.
The key data field is given below.
z Charging source code
It is the calling party's "Charging source code" in the subscriber data table. To query it,
carry out the LST ST command.
4-4
Maintenance Manual – Troubleshooting Volume
C&C08 Digital SPC Switching System Chapter 4 Charging & Bill System
Called charging source code: It is the destination subscriber's "Charging source code"
in the subscriber data table or the outgoing trunk's "Charging source code" in the
outgoing trunk group data table. To query it, carry out the LST ST or LST TG
command.
z Destination code charging with key data fields given below.
Charging selection code: It is the call prefix's "Charging selection code" in the called
number analysis table. To query it, carry out the LST CNACLD command.
Caller charging source code: It is the "Trunk charging source code" in the incoming
trunk group data table. To query it, carry out the LST TG command.
There are two charging modes for outgoing trunk charging in a local office. One is
intra-office group charging which does not distinguish destination codes. The other is
destination code charging (charging case indexing) which distinguishes destination
codes.
z Intra-office group charging with key data fields given below.
Caller charging source code: It is the outgoing trunk's "Charging source code" in the
outgoing trunk group data table. To query it, carry out the LST TG command.
Called charging source code: It is the outgoing trunk's "Charging source code" in the
outgoing trunk group data table. To query it, carry out the LST TG command.
z Destination code charging with key data fields given below.
Charging selection code: It is the call prefix's "Charging selection code" in the called
number analysis table. To query it, carry out the LST CNACLD command.
Caller charging source code: It is the "Trunk charging source code" in the outgoing
trunk group data table. To query it, carry out the LST TG command.
I. Overview
The modules such as SM, RSM, SPM, independently achieve the host charging. In
the C&C08 Digital SPC Switching System, the bill processing process undergoes four
steps, as shown in Figure 4-1.
4-5
Maintenance Manual – Troubleshooting Volume
C&C08 Digital SPC Switching System Chapter 4 Charging & Bill System
MPU board
① ③ AM/CM ③ ④
Host bill pool BAM
SPC board
① ③ BAM ④
Host bill pool
II. Steps
Step 1: When a call finishes, the switch first saves its charging information to the bill
buffer area in the MPU or SPC of the corresponding module. The buffer area
comprises three parts.
z Host bill pool
It saves all bills to be sent to the BAM and all the detailed bills.
z Centrex bill pool
It saves all bills to be sent to the Centrex console. For Centrex subscribers who
require the immediate charging function, their bills are saved not only in the host bill
pool but also in the Centrex bill pool.
z Software meter
It records meter counts of meters and statistical meters. In the meter charging mode,
the charging information accumulates in the corresponding user or trunk meter.
Step 2: The switch regularly or immediately updates the host meters, converts meter
counts of all user & trunk meters to bills and saves them to the host bill pool.
Step 3: The switch regularly or immediately fetches the bills in all host bill pools,
sends them to the BAM and saves them in files. At the same time, it sends the meter
counts to the BAM database and adds them to corresponding accumulated meters.
The storage paths are as follows.
z D:\Bill\Bill\YYYYMMDDHH.bil
It saves all normal and alarm bills of the day. The file name is the combination of the
date & time, and the filename extension is "bil".
z D:\Bill\Bill\YYYYMMDDHH.flt
4-6
Maintenance Manual – Troubleshooting Volume
C&C08 Digital SPC Switching System Chapter 4 Charging & Bill System
It saves all bills of failed calls of the day and has a close relationship with traffic
statistics. The filename extension is "flt".
z D:\Bill\Bill\YYYYMMDDHH.err
It saves all error bills of the day. The filename extension is "err".
z E:\BillBack\Backup\YYYYMMDDmmm.bil
It saves backed-up bills. When fetching original bills, the system automatically backs
up them to this directory. The file name is the combination of year, month, day and
module number.
z E:\BillSorter
It saves picked-up bills. When fetching bills, the system also saves bills to specified
picking-up directories according to operators' settings.
z D:\Bill\Centrex
Generally, for Centrex subscribers who require the immediate charging function, their
bills are sent to the Centrex console directly from the Centrex bill buffer area. In
particular case, for example, Centrex bill pool overflowing or the communication
between the switch host and the console blocked, the switch will back up Centrex bills
to D:\Bill\Centrex on the BAM.
Step 4: The switch backs up bill files to storage media on fixed days of every month,
for example, compact disks (CD) or tapes, and sends them to the billing center. If the
billing center cannot identify the bill format, the switch will convert it.
I. Detailed description
When the BAM fetches bills, bills of a continuous time are found unavailable. The
following two cases are possible.
z The bill files cannot be generated on the BAM.
z The charging time in the bill file is not continuous, that is, the charging
information of a certain continuous time has lost.
Seria
Fault causes Remarks
l No.
The BAM hard disk has These two faults may disable bills to be
1
insufficient space. written into the BAM. They should be cleared
4-7
Maintenance Manual – Troubleshooting Volume
C&C08 Digital SPC Switching System Chapter 4 Charging & Bill System
Seria
Fault causes Remarks
l No.
The BAM hard disk is in time. Otherwise, the host bill pool may
2 overflow, leading to loss of bills.
damaged.
If the bill process has logged off and has not
The bill process restarted for a long time, bills in the MPU or
3
abnormally logs off. SPC may overflow, consequently leading to
loss of bills.
There is running firewall or These faults may cause the bill process to
4
anti-virus software. abnormally log off when the BAM is fetching
5 There are viruses. bills, consequently leading to loss of bills.
Note:
When you clean up the hard disk space, it is recommended to use external storage
devices, for example, magneto optical (disk) (MO), to back up the data in case of a
deletion of valid bill data.
4-8
Maintenance Manual – Troubleshooting Volume
C&C08 Digital SPC Switching System Chapter 4 Charging & Bill System
To check whether there is such a fault, view the alarm console to find whether there is
an alarm that the bill process has abnormally logged off.
4) Judge which reason causes the bill process to abnormally log off.
Common reasons are as follows.
z The firewall or anti-virus software is running. In this case, these nonstandard
software conflicts with the BAM service process to a great extent, which may
cause multiple service processes including the bill process to abnormally log off,
consequently leading to such faults as bills lost or repeated bills. Thus, the
security of the charging system cannot be ensured. Therefore, we strongly
recommend you not to install nonstandard software including the above software
on your BAM.
z There are viruses. For virus clearing and other processing measures, refer to the
section "BAM Virus Prevention & Clearing" in Chapter 7 Terminal System.
IV. Suggestions
I. Detailed description
The charging information of the same serial number (with identical contents) repeats
in bill files, causing repeated charging. Thus, there are repeated bills.
Serial
Fault causes Remarks
No.
In this case, the control pointers of the bill
pool may have not been backed up or not
completely backed up. As a result, the fetch
The MPU (or SPC) is pointer of the bill pool of the active MPU is
1
abnormally switched over. not consistent with that of the standby MPU
after a switchover. The standby MPU will
re-send fetched bills, thus causing repeated
bills.
The bill process restarts It may cause the loss of the bill serial
2 when the BAM fetches number. When the BAM re-fetches bills,
bills. there will be repeated bills.
4-9
Maintenance Manual – Troubleshooting Volume
C&C08 Digital SPC Switching System Chapter 4 Charging & Bill System
Serial
Fault causes Remarks
No.
Insufficient virtual memory
3 causes the BAM to
automatically restart. These faults may cause the bill process to
abnormally restart when the BAM is
There is running firewall fetching bills, consequently leading to
4
or anti-virus software. repeated bills.
To check the fault, find whether there is an MPU switchover alarm in the
corresponding module. In this case, repeated bills will occur to the same module and
there may be a lot of such bills.
2) Check whether the BAM alarms that the bill process has abnormally logged off.
If the bill process has abnormally logged off when the BAM fetches bills, it is possible
that the serial number of the latest fetched bill has not been saved to the database.
When the BAM reboots the bill process, there will be repeated bills.
To check whether there is such a fault, view the alarm console to find whether the
BAM alarms that the bill process has abnormally logged off. The alarm time is the
time that the first repeated bill occurs.
3) Judge which reason causes the bill process to abnormally log off.
Common reasons are as follows.
z Insufficient virtual memory causes the BAM to automatically restart. For instance,
the virtual memory of Windows 2000 Server has been set to a value smaller than
the recommended 267 MB. In this case, the virtual memory may be insufficient.
To resolve it, modify the value to a one slightly larger than the recommended
value, for example, 300 MB.
z The firewall or anti-virus software is running. In this case, these nonstandard
software conflicts with the BAM service process to a great extent, which may
cause multiple service processes including the bill process to abnormally log off,
consequently leading to such faults as bills lost or repeated bills. Thus, the
4-10
Maintenance Manual – Troubleshooting Volume
C&C08 Digital SPC Switching System Chapter 4 Charging & Bill System
IV. Suggestions
I. Detailed description
Adjacent bills (with different serial numbers) of a calling party have discontinuous
charging time. The time overlaps with adjacent charging time. That is, the start or end
charging time of a bill is in the charging duration of another bill.
Serial
Fault causes Remarks
No.
The way to get the When the system charges the incoming trunk,
calling number of the there may be crossing bills if the incoming
1
incoming trunk is trunk sends the same calling number or the
different. trunk group uses a default calling number.
1) Check the way to get the calling number of an incoming trunk call.
When the system charges the incoming trunk, there may be crossing bills if the
incoming trunk sends the same calling number or the trunk group uses a default
calling number.
In this case, to process crossing bills and avoid call charges disputes, use proper
measures according to actual situations, for example, adjusting trunk data or
negotiating with the opposite office to determine the sending of the calling number.
4-11
Maintenance Manual – Troubleshooting Volume
C&C08 Digital SPC Switching System Chapter 4 Charging & Bill System
IV. Suggestions
I. Detailed description
Error bills refer to the bill files on the BAM whose filename extension is ".err".
Possible reasons are as follows.
z Extra long conversation time
z Error bill check sum, for example, erroneous bytes, abrupt bytes, and cut-off
bills.
Serial
Fault causes Remarks
No.
The conversation The switch will generate a charging alarm and
1
time is extra long. error bill.
There is
inter-module
2 It may cause abnormal meter counts.
communication bit
error.
4-12
Maintenance Manual – Troubleshooting Volume
C&C08 Digital SPC Switching System Chapter 4 Charging & Bill System
For instance, the meter counts are 1000 more than the normal value. It is possible
that a high bit of the meter has been set to 1 (210=1024).
3) Judge whether the MPU (or SPC) is faulty.
It is necessary to check the MPU (or SPC) when there are such exceptions as
incomplete calling or called number, abnormal conversation duration, all-zero bill,
abnormal charging meter counts. To locate the fault, switch over or change the MPU
(or SPC).
Note:
Before the switchover, it is required to update meters, fetch bills, back up
supplementary service data and service data in the ISP, and so on. Otherwise, bills or
data may be lost, or the running of the system will be in a state of confusion after the
switchover.
For instance, if the position for the MFC trunk to send A6 is set to "3", for a call whose
calling number is of three digits like "1xx", the A6 is of no use and the bill will have no
calling number. It is because the call has already been established and charged when
A6 is being sent out. The calling number will be "000". To resolve it, modify the
position to send A6 or the minimum number length in the called number analysis
table.
4-13
Maintenance Manual – Troubleshooting Volume
C&C08 Digital SPC Switching System Chapter 4 Charging & Bill System
For signaling interworking details, refer to Chapter 3 Trunk & Signaling System.
5) Contact technical support engineers.
If the problem has not been cleared yet, or you are not confident enough in your
judgement, contact technical support engineers in time.
IV. Suggestions
Through analysis of the reasons that cause error bills, it is known that the
inter-module communication fault takes a great proportion. To reduce error bills,
therefore, it is an effective way to keep inter-module communication links in good
conditions.
I. Detailed description
Alarm bills are abnormal bills caused by error charging data configuration, for
example, charging case not defined or the tariff or rate is zero. In this case, the
system will generate both an alarm bill and a charging alarm. It has the following
features.
z The switch saves such a bill as a normal bill but the record type is "Alarm".
z It records each call in the detailed bill format but cannot distinguish metering
bills.
When such a fault occurs, check the charging data configuration with reference to
related manuals or view the history maintenance records by querying the database
operation log, so as to restore the system. Make an on-site test to spare no chance of
an error after modifying the charging data.
2) Convert alarm bills.
When there is no charging data, the switch will generate normal bill files on the BAM
as well as alarms. These bills can be queried through bill browsing but cannot be
offline processed. Only through special processing can they be converted into
ordinary bills.
In such a case, if you fail to effectively process the alarm bills, contact technical
support engineers in time.
4-14
Maintenance Manual – Troubleshooting Volume
C&C08 Digital SPC Switching System Chapter 4 Charging & Bill System
III. Suggestions
z Carefulness and prudence is required to modify the charging data and on-site
test must be made after the modification to spare no chance of an error.
z Process the charging alarms as soon as they occur.
I. Detailed description
Serial
Fault causes Remarks
No.
It mainly refers to poor line insulation. When there is
an incoming call, the ringing current makes the
circuit conductive and thus the called party is
External lines are
1 wrongly considered having given an answer. When
faulty.
the ringing stops, the circuit restores and thus the
called party is wrongly considered having hooked
on.
The subscriber Due to the changes of external environment or inner
2 telephone is factors, the telephone automatically and frequently
faulty. redials.
When faulty, the ASL generates pulse signals
automatically, leading to false dialing and
3 The ASL is faulty.
consecutive extra-short-conversation-time bills. In
such bills, the called number is usually "1xx".
The called
terminal is an The called terminal may be a fax machine, answer
4
automatic answer phone, automatic answering telephone set.
back device.
Such faults as cross-connected lines or unmatched
Interconnection CICs may cause unidirectional charging.
of inter-office
5 Improper inter-office signaling interworking may
trunks becomes
abnormal. cause charging signals to be sent out when the
opposite office gives the voice announcement.
4-15
Maintenance Manual – Troubleshooting Volume
C&C08 Digital SPC Switching System Chapter 4 Charging & Bill System
Carry out test commands on the maintenance console to test whether called external
lines are faulty. For detailed operation instructions, refer to 2.3.3 Abnormal Call-in in
Chapter 2 Subscriber System.
4-16
Maintenance Manual – Troubleshooting Volume
C&C08 Digital SPC Switching System Chapter 4 Charging & Bill System
5) Check whether the called terminal is an automatic answer back device, for
example, facsimile machine, answer phone.
If the called terminal is an automatic answer back device and when a call fails, the
caller may reckon that the line is faulty or a wrong number has been dialed, and he or
she may repeatedly redial the called number, thus resulting in consecutive
extra-short-conversation-time bills.
6) Check whether the interconnection of inter-office trunks is abnormal.
Two cases are possible.
z Unidirectional inter-office calls will be charged and thus
extra-short-conversation-time bills generated. It may be caused by cross
connected trunk lines or unmatched CICs.
z Due to improper inter-office signaling interworking, unexpected charging signals
may have been received. In this case, it is necessary for the opposite office to
check its signaling data configuration. In the local office, connection or signaling
tracing may be used to check it out.
IV. Suggestions
To analyze bills and find the distribution probability of calling and called numbers in
bills is a significant method to locate the fault.
I. Detailed description
Serial
Fault causes Remarks
No.
The MPU (or SPC) It may cause abnormal switchover between
1
hardware is faulty. the active and standby MPUs (or SPCs).
Thus, data may have not been completely
The MPU (or SPC) is backed up and call connection state cannot
2 abnormally switched be normally released after the switchover.
over. As a result, extra-long-conversation-time
bills are generated.
4-17
Maintenance Manual – Troubleshooting Volume
C&C08 Digital SPC Switching System Chapter 4 Charging & Bill System
Serial
Fault causes Remarks
No.
It may cause the loss of connection state
The MPU (or SPC) data and abnormal release of a call.
3
memory bar is faulty. Consequently, extra-long-conversation-time
bills are generated.
In the case of calling party controlled circuit
The calling party connection, extra-long-conversation-time
4
abnormally hooks on. bills may be generated when the calling
party has abnormally hooked on.
Note:
Complaint bills refer to the normal bills with the complaint flag being YES.
In some particular cases, for example, the called office fails to normally send the
called on-hook signal, signal loss due to exceptions occurred to signaling links, if the
4-18
Maintenance Manual – Troubleshooting Volume
C&C08 Digital SPC Switching System Chapter 4 Charging & Bill System
calling party has not normally hooked on, the originating switch may consider that the
calling party is always in conversation and charge him or her.
4) Check whether the MPU (or SPC) has been normally switched over.
The MPU (or SPC) switchover in the following cases may cause
extra-long-conversation-time bills.
z Hardware fault occurs to the active MPU (or SPC).
z The time between two switchovers is too short, for example, shorter than thirty
minutes.
z Switchover is carried out in the bill fetching process.
The above cases may cause incomplete backup of the active and standby MPU (or
SPC) data. Thus the call connection state data of the active MPU (or SPC) may be
inconsistent with that of the standby MPU (or SPC) after the switchover. As a result,
some calls cannot be normally released (released until expiry of the system timer)
and extra-long-conversation-time bills are generated.
Except the first case, maintenance staff should strictly observe the switchover
operation procedures in case of any charging fault.
5) Judge whether the memory bar of the MPU (or SPC) is faulty.
Because all charging information is saved into the memory of the MPU (or SPC),
extra-long-conversation-time bills may be generated once the memory gets faulty.
Contact technical support engineers in time when there is any suspicion of memory
fault because the fault has a tremendous impact on the charging.
IV. Suggestions
Before switching over the MPU (or SPC), it is mandatory to update meters, back up
system data, and so on. Frequent switchover is prohibited because it may cause bill
loss or exceptions, leading to great loss of call charges.
I. Detailed description
The following two cases are possible when the BAM cannot normally fetch bills
z The BAM cannot fetch bills. When the BAM is fetching bills, the system prompts
"Operation timed out". In this case, after querying the bill buffer information, you
will find that the value of the fetch pointer remains unchanged.
z The bill fetching time is long, that is, the rate at which the host sends bills to the
BAM is much lower than the normal rate.
4-19
Maintenance Manual – Troubleshooting Volume
C&C08 Digital SPC Switching System Chapter 4 Charging & Bill System
Serial
Fault causes Remarks
No.
The BAM-host
Such faults may occur as "Cannot fetch bills" or
1 communication is
"Long bill fetching time".
abnormal.
The inter-module
Generally, it affects only a single module's bill
2 communication is
fetching.
abnormal.
Too large alarm files, history bill files or
The disk space is database operation log occupy a large amount
3
insufficient. of the hard disk space, and consequently the
space is insufficient.
4-20
Maintenance Manual – Troubleshooting Volume
C&C08 Digital SPC Switching System Chapter 4 Charging & Bill System
If the hard disk space is found insufficient, back up data or directly clean it up
according to actual situations.
5) Check whether there is running firewall or anti-virus software on the BAM.
If there is running firewall or anti-virus software on the BAM, it is possible that when
the bill process is to access a bill file, the firewall or anti-virus software is examining it,
and consequently the bill process fails to read the bill file.
In case of any unexpected behavior and charges loss, we strongly recommend you
not to install or run such software on your BAM. If it is necessary to find and clear
viruses, refer to the section "BAM Virus Prevention & Clearing" in Chapter 7 Terminal
System.
6) Check whether the bill process is working normally.
Once the bill process is working abnormally or logs off abnormally, the BAM will fail to
normally fetch bills. To locate the fault, restart the bill process or the BAM server.
Remember to back up data before restarting the BAM.
7) Check whether Centrex subscribers' bills have been processed first.
Because the BAM first processes Centrex subscribers' bills then ordinary subscribers'
bills, time-out situation is possible when the BAM processes ordinary subscribers'
bills.
For instance, an SM has 100 Centrex groups. In this case, it may take twenty minutes
or so for the BAM to process Centrex bills. Only after it can the BAM normally fetches
ordinary bills.
8) Judge whether the BAM is running normally.
If the BAM still fails to fetch bills after the above measures, it is possible that
exceptions have occurred to the BAM, for example, virus infection and file damage. In
this case, contact technical support engineers in time or use an emergency
workstation if the situation is urgent.
4-21
Maintenance Manual – Troubleshooting Volume
C&C08 Digital SPC Switching System Chapter 4 Charging & Bill System
V. Suggestions
z Do not install or run nonstandard software on the BAM, for example, firewall or
anti-virus software.
z Regularly check the BAM hard disk space, especially when the BAM restarts due
to exceptions.
z Process the charging alarms as soon as they occur.
I. Detailed description
Exceptions occur when the bill process automatically backs up bills, leading to
backup failure.
Serial
Fault causes Remarks
No.
The BAM disk is
1 The BAM will fail to read or write bill files.
faulty.
4-22
Maintenance Manual – Troubleshooting Volume
C&C08 Digital SPC Switching System Chapter 4 Charging & Bill System
Serial
Fault causes Remarks
No.
The bill files are
3 The BAM will fail to read bill files.
damaged.
Because normal bill files and backup bill files are saved to different directories on the
BAM, it is necessary to consider the following aspects when the bill backup is
abnormal.
1) Check whether the BAM disk is faulty.
If the BAM gives the alarm "Hard disk read-write fault", change the faulty hard disk.
For matters needing attention and instructions when changing BAM hard disk, refer to
7.3.3 Hard Disk Fault in Chapter 7 Terminal System.
2) Check whether the BAM disk has sufficient space.
If the BAM gives the alarm "Insufficient hard disk space", it indicates that the space in
the bill backup sub-directory has been used up and no file can be written into it. At
this time,
z First back up valid bill files to external storage media (for example, MO).
z Then delete outdated bill files in the backup sub-directory.
Note:
Generally, the bill backup sub-directory is E:\BillBack\Backup, which is specified
during the installation of the BAM server software.
In case of any unexpected behavior and charges loss, we strongly recommend you
not to install or run such software on your BAM. If it is necessary to find and clear
viruses, refer to the section "BAM Virus Prevention & Clearing" in Chapter 7 Terminal
System.
4-23
Maintenance Manual – Troubleshooting Volume
C&C08 Digital SPC Switching System Chapter 4 Charging & Bill System
If the bill file cannot be recovered, contact technical support engineers in time.
IV. Suggestions
z Use external storage devices, for example, MO, to copy bill files in time to save
as much space in the backup sub-directory as possible.
z Do not install or run nonstandard software on the BAM, for example, firewall or
anti-virus software.
I. Detailed description
Serial
Fault causes Remarks
No.
The setting of
Only the bill format output by iGateway Bill meets the
the conversion
1 billing center's requirements can the conversion be
mode is
successful.
incorrect.
When installing the conversion software, select
The setting of
options according to the number of bytes of each bill
the bill
2 and the number of meters of the metering bill. If the
parameters is
options have been incorrectly selected, the
incorrect.
conversion will fail.
4-24
Maintenance Manual – Troubleshooting Volume
C&C08 Digital SPC Switching System Chapter 4 Charging & Bill System
IV. Suggestions
It is a complicated and difficult job to set the format conversion on the iGateway Bill.
Contact Huawei Technologies to customize the final bill format in the case of
particular requirements.
I. Detailed description
It refers to the case that original bills cannot be sent from the BAM to the iGateway
Bill, which fails iGateway Bill to carry out related jobs.
Serial
Fault causes Remarks
No.
Network adapters, network cables or
1 The network is blocked.
HUB may get faulty.
Because Transmission Control
Protocol (TCP)/IP is used between
The set IP address or gateway the iGateway Bill and BAM, the
2
of the iGateway Bill is wrong. network parameters must be correctly
set and the communication between
them must be ensured.
4-25
Maintenance Manual – Troubleshooting Volume
C&C08 Digital SPC Switching System Chapter 4 Charging & Bill System
As for the processing of BAM network adapter faults, refer to Chapter 7 Terminal
System.
2) Check whether the network setting of iGateway Bill is correct.
z Check whether the iGateway Bill's IP address, gateway and other network
parameters have been correctly set. The gateway should be BAM's IP address,
which should belong to the same network interface segment as the iGateway
Bill's IP address.
z Open the configuration file on the iGateway Bill and check the configuration item
"Connect the BAM local address" which is used to connect the BAM. If it has not
been set or has not been correctly set, set it to the IP address of the first network
adapter of the iGateway Bill. Then save it to the registry and restart the iGateway
Bill.
3) Check whether bill bytes in the iGateway Bill have been correctly set.
4) Check whether BAM settings are correct.
If the fault has not been located yet, check whether "BillServer" in [SendBill] in the file
"D:\CC08\128bam.ini" on the BAM server has been set to the IP address of the
iGateway Bill. If not, set it.
IV. Suggestions
Refer to iGateway Bill User Manual to ensure that all parameters have been correctly
set.
4-26
Maintenance Manual – Troubleshooting Volume
C&C08 Digital SPC Switching System Chapter 5 Main Control System
5.1 Overview
The main control system is a collective name of boards and host software that fulfill
the functions of management, control and connection in the switch. It is the core part
for fulfilling the switch services and so any fault in it directly affects the switch services.
This chapter introduces the fault processing related to the main control system from
the point of view of routine maintenance and operation of the switch.
Table 5-1 lists the common faults that may occur in the main control system.
Table 5-1 Common faults that may occur in the main control system
Maintenance Call loss increases, call completing rate decreases, the traffic of
the global office is blocked, the traffic of the whole module is
Call blocked blocked, and so on, due to causes of the main control system
such as insufficient resource, inappropriate configuration and
faulty control boards.
Abnormal
The module cannot be loaded or the link is broken after the
module
loading.
loading
Table 5-2 lists the common fault causes that may occur in the main control system.
5-1
Maintenance Manual – Troubleshooting Volume
C&C08 Digital SPC Switching System Chapter 5 Main Control System
Table 5-2 Common fault causes that may occur in the main control system
5-2
Maintenance Manual – Troubleshooting Volume
C&C08 Digital SPC Switching System Chapter 5 Main Control System
The entire C&C08 switching system comprises the following parts: AM, CM, SPM,
SRM and SM, as shown in 0.
V.24/V.35
Enthernet LAN
FAM/CM BAM
SPM/SRM
OFL E1 WS WS
SDH
SM RSM
SM
FAM manages the inter-module call connections of the whole system. For any
connection between SMs or SPMs, the message has to be transferred through the
FAM. It controls and manages switching in real time and provides the central
database for global number location, trunk line hunting and resource management.
The FAM also provides interfaces between the main processor of the switch and
maintenance operation terminals (which are part of the CM). In such cases they are
called FAM/CM or AM for short.
BAM provides interconnection of the switching system and the open network system
in the client-server mode by directly connecting the FAM through Ethernet interface.
Hence, the BAM has the pivotal role of connecting the C&C08 switch and the
computer network.
5-3
Maintenance Manual – Troubleshooting Volume
C&C08 Digital SPC Switching System Chapter 5 Main Control System
The maintenance-oriented BAM manages, maintains and monitors the host system of
the switch, which is also called the terminal system. The BAM is a server (hardware),
installed with terminal system software. It works on Windows 2000 Server, providing
Graphic User Interface (GUI) and Man Machine Interface (MMI) operating interfaces
for easy operation and to ensure perfect functioning of the network. It is the
Operations and Maintenance center of the C&C08 switching system.
SPM is a part of the AM/CM. It uses the external interfaces on the AM/CM. It
implements almost all the functions of the SM utilizing the central database and the
Shared Resource Module. A single SPM module has a higher processing &
integrating capability than an SM. It supports the networking mode of large capacity
trunk circuits. In addition, it processes services related to the PCM, such as CCS7
signaling, CAS signaling, V5 signaling, PRA or Packet Handling Interface (PHI)
signaling.
The SPM can be directly connected with the BAM through 10 Mbit/s or 100 Mbit/s
TCP/IP interface.
SRM provides all kinds of resources to the SPM for processing of services, such as
signal tone, DTMF receiver, multi-frequency compelled transceiver, and
tele-conferencing, caller number display. The resources from the SRM are shared by
all the SPMs in the switch and not limited to a specific SPM.
SM, similar to the SPM, is also the core of the C&C08 Digital SPC Switching System.
It performs such functions as distributed database management, distributed resource
management, call processing and maintenance operations.
5-4
Maintenance Manual – Troubleshooting Volume
C&C08 Digital SPC Switching System Chapter 5 Main Control System
The AM/CM internal communication control link system uses the CCM as the
switching center. It comprises the CCM frame, interface frame, main control frame,
SPM frame, and so on. The composition of the system is shown in Figure 5-2.
BAM
Serial 10Mbit/s
port Terminal 10Mbit/s
Alarm box LAN SWITCH CKM
group
10Mbit/s 10Mbit/s
Serial
port
CPM
CDB
CDP CDP
ALM AMP
#0 #3
Serial
SPM SPM port
0 11 HDLC
NCC CCM
HDLC #0
CCM
CNU CNU
#1
#0 #7
Serial
port QSI
HDLC LIM
LIM LIM
#0
#1 #12
OBC E16 STU
40.96Mbit/s E1 E1 STM-1
All boards that directly communicate with the CCM (for example, SPC, BCC, QSI,
MHI) occupy their independent module numbers.
Boards that do not directly communicate with the CCM, such as the CPC in the SPM
for processing protocols, SRC and Special Tone Board (SPD) in the resource frame
5-5
Maintenance Manual – Troubleshooting Volume
C&C08 Digital SPC Switching System Chapter 5 Main Control System
and ET16, STU and OBC in the interface frame have no module numbers. They
function as the slave nodes of the upper-level boards and communicate with the
external equipment. For example, the CPC functions as the slave node of the BCC
and communicates with the external equipment through the BCC. The ET16, STU
and OBC, and so on, function as the slave nodes of the QSI and communicate with
the external equipment through the QSI. The SRC, SPD and so on, function as the
slave nodes of the MHI and communicate with the external equipment through the
MHI.
There are two 40.96 Mbit/s optical channels between each SM and the AM/CM. They
are connected to the 40.96 Mbit/s optical interfaces of the two OBCs in the same
interface frame of the AM/CM. As the SM optical channels can work in the
active-standby mode and load-sharing mode, the two SM optical channels can also
be connected with OBCs in two modes. In the active-standby mode, the two optical
channels correspond to the optical interfaces of the active-standby OBCs. In the
load-sharing mode, they are connected to the optical interfaces of two active OBCs,
and the standby OBCs need not be inserted. Figure 5-3 shows the connection
relation of inter-SM links working in the active-standby mode.
CCM #0 CCM #1
OBC #0 OBC #1
Extracting Extracting
link HW link HW
NET NET
5-6
Maintenance Manual – Troubleshooting Volume
C&C08 Digital SPC Switching System Chapter 5 Main Control System
Each 40.96 Mbit/s optical channel includes one HW of 2 Mbit/s used for link
communication. Parts of the time slots of the HW are used for the inter-SM link
communication. The HWs of 2 Mbit/s connected to one interface frame are extracted
on the OBCs and connected to the QSIs in the frame.
When the SMs work in the active-standby mode, the link timeslots in the two planes
are allocated to the 2 Mbit/s HWs extracted from the same OBC. The channels of the
first half frame form Plane 0, while the channels of the second half frame form Plane
1. When the SMs work in the load-sharing mode, the link timeslots of the two planes
are allocated to two active OBCs. The first half frame of the 2 Mbit/s HW extracted
from OBC#0 is Plane 0, while the second half frame of the 2 Mbit/s HW extracted
from OBC#2 is Plane 1.
Figure 5-4 shows the connection mode of the physical inter-RSM High-level Data Link
Control (HDLC) links. As shown in the figure, each RSM has two physical HDLC links.
One is connected to CCM #0, while the other is connected to CCM #1. They are
symmetrical between two link communication planes. The establishment of each
physical link is based on the network switching of the ET16 and the QSI, so as to
fulfill the semi-permanent connection of the link communication time slots. The
switching of the time slots is performed according to the RSM link configuration data
at the background.
5-7
Maintenance Manual – Troubleshooting Volume
C&C08 Digital SPC Switching System Chapter 5 Main Control System
CCM #0 CCM #1
ET16 ET16
E1 E1 E1 E1
I. Detailed description
CPU overload is a serious fault of the switch. It is shown in the following aspects:
z The CPU occupation ratio of the module exceeds 75%. Here the module refers
to AM/CM, SPM, SM and RSM, and so on.
z Large amount of calls of the whole switch or a module (for example, SM, RSM or
SPM) congests and the call completing rate decreases sharply.
5-8
Maintenance Manual – Troubleshooting Volume
C&C08 Digital SPC Switching System Chapter 5 Main Control System
Serial
Fault causes Remarks
No.
Too large system traffic due to such factors as
The traffic is too
1 system capacity, network layout, subscriber increase
large.
and holiday is a common cause of CPU overload.
For example, when the board running status
sometimes is normal and sometimes abnormal
There is too much
because of external causes or the improper setting
2 system alarm
of the alarm parameters is error, the switch may
information.
generate large amounts of alarms and result in the
CPU overload.
5-9
Maintenance Manual – Troubleshooting Volume
C&C08 Digital SPC Switching System Chapter 5 Main Control System
trunk circuit. If the occupation ratio of the trunk circuit exceeds 70%, it indicates
that the inter-office traffic volume is considerably large.
z Query the change of the host bill pool. Type the LST BILPOL command on the
maintenance console, type the corresponding module number, and carry out the
command for several times. Compare the changes of the storage pointer. If the
difference value is large, it indicates that the traffic volume at this time is
considerably large.
Generally the observation is a major method to find the CPU overload caused by
large traffic volume.
2) Check whether the system has too much alarm information.
Too much alarm information occupies large amounts of CPU resources and results in
CPU overload. There are two major causes.
z The setting of the alarm parameters is inappropriate. For example, some
lower-level event alarms have not been shielded, and consequently the system
may generate many alarms under the influence of external environments.
The solution to this problem is to properly shield some low-level and event alarms
through the setting of the alarm parameters, so as to reduce the information quantity.
z The running status of some boards sometimes is good and sometimes bad. For
example, the unstable performance of the transmission system may result in the
repeated locating of the signaling links, which in turn causes the generation of
large amounts of alarms and CPU overload.
Generally, the causes and locations of the alarms can be known through viewing the
alarm information. If the system has adopted backup measures, a board can be
plugged out temporarily and recovered after the faults are eliminated.
3) Check whether the system data configuration is proper.
The improper setting of some call processing data may affect the performance of the
switch. Therefore, when CPU overload occurs frequently, check the following data.
z Pre-receive number digits
Generally, in order to reduce the burden of the CPU, except that the pre-receive
number digits of the call source used in the Centrex group should be set to 1, the
other pre-receive number digits should be set to a value greater than 1, for example,
3.
z Trunk seizure point
Like the pre-receive number digits, if the trunk seizure point is over-short, not only the
occupation rate of the CPU will increase greatly, but also the call loss will increase
and the call completing rate decrease. The setting of the trunk seizure point should
take into consideration the relation between the Quality of Service (QoS) and
processing performance of the switch. For example, the trunk seizure point of the
5-10
Maintenance Manual – Troubleshooting Volume
C&C08 Digital SPC Switching System Chapter 5 Main Control System
local call can be set to seven or eight digits, and that of the toll call can be set to 6~10
digits.
z Trunk timer threshold
The overlong trunk timer threshold may increase the circuit release time or the waiting
time. If the timer threshold is over short, a circuit may be released too early and the
call may fail. Thus, the time that the switch uses the CPU for occupation processing
and failure processing will increase greatly. When the inter-office traffic volume
increases, CPU overload is likely to occur.
IV. Suggestions
CPU overload is a serious fault of the switch. It is quite likely to cause the "avalanche"
effect and threats the safe operation of the switch. To prevent the CPU overload, take
the following measures.
z Perform routine check frequently and carefully and view the alarm information at
regular time intervals, so as to learn the running status of the switch in time.
z Clean the garbage data in time to reduce invalid processing times.
z Use the default parameters of the switch as possible as it can be.
z Keep records, especially during the modification of key data. This can increase
the speed of fault locating and avoid blind locating.
I. Detailed description
Call blocked is an important form of the fault or abnormity of the main control system.
It is shown when large amounts of calls or connections are faulty or abnormal. The
following cases are possible.
z The traffic of the global office is completely blocked.
z Inter-module traffic is completely blocked.
z Intra-module traffic is completely blocked.
z Of all causes of call loss obtained through traffic statistics, the causes related to
the main control system increase sharply or keep accounting for a high ratio.
Serial Fault
Remarks
No. causes
The control When the control boards such as BCC, NCC, QSI, MPU
1 board is and SPC get faulty, complete blocking will occur or the call
faulty. loss may increase.
5-11
Maintenance Manual – Troubleshooting Volume
C&C08 Digital SPC Switching System Chapter 5 Main Control System
Serial Fault
Remarks
No. causes
The switching network comprises the BNET and the
The control circuits. When the switching is blocked because of
switching the damage of the BNET timeslots or the chaotic switching
2
network is control logic, the call loss will increase greatly. Besides,
faulty. such connection faults as unidirectional call and call
disconnection often occur.
The locating of the fault "call blocked" has already been introduced in the chapter 2
"Subscriber System" in the manual and therefore is omitted here.
IV. Suggestions
To prevent the call blocked fault, take the following three measures.
z Check the equipment frequently and view the alarm information at regular
intervals so as to learn the running status of the equipment in time and find the
incipient fault as early as possible.
z Enhance the traffic statistics, find the major causes of call loss and adopt
appropriate technical or management measures, so as to provide a base for the
network layout in the next step.
z Enhance the routine maintenance and management of the switch database, be
cautious to the modification of key data and keep records. This can increase the
speed of fault locating and avoid blind locating.
5-12
Maintenance Manual – Troubleshooting Volume
C&C08 Digital SPC Switching System Chapter 5 Main Control System
I. Detailed description
Abnormal module loading refers to the abnormities during the loading of the MPU
when such modules as SM and RSM are being restarted because they are turned off
or reset. These abnormities include:
z The module cannot be loaded. That is, the programs or data cannot be loaded to
the MPU through the BAM.
z The link is broken after the loading. The module can be loaded; but after the
loading is finished, the link between the loaded module and the AM/CM cannot
be established normally, and the inter-module communication is interrupted.
Serial
Fault causes Remarks
No.
The DIP switch of the MPU determines such
The Dual-In-line Pin
parameters as module type and communication
1 (DIP) switch of the
rate. It is easily to neglect the DIP setting and
MPU is incorrect.
make it unable to load the module.
Transmission boards are communication bridges
Transmission boards
for the loading of the module. Faults in
such as QSI, OBC,
2 transmission boards such as optical interface
STU, ET16, OPT and
impairment and bit error are common causes
DTF are faulty.
that make it unable to load the module.
5-13
Maintenance Manual – Troubleshooting Volume
C&C08 Digital SPC Switching System Chapter 5 Main Control System
Serial
Fault causes Remarks
No.
Such abnormities as error bit, intermittent
The external bursting and pointer adjustment in the external
7 transmission system is transmission system will affect the loading of the
faulty. RSM module. For example, the loading cannot
be performed or time out.
1) Check whether the setting of the DIP switch of the MPU is correct.
If the module cannot be loaded because of the replacement of the MPU, first check
whether the DIP switch of the MPU falls in line with the networking application of the
module.
The DIP switch of the MPU is shown in Figure 5-5 (with CB38MPU version as the
example). It is necessary to check communication bandwidth, loading mode and
module type, and so on, so as to ensure that the situation on the site is consistent
with the system configuration. For concrete setting modes, refer to Board Manual.
OFF ON
SW1
Combining SW1 and SW2 to select module communication bandwidth
SW2
SW3 Select matching impedance of DT board OFF:75 ohm; ON:120 ohm
SW4 Select the communication rate of NOD and DT boardsOFF: low baud rate ON: high baud rate
SW5 Data writable
SW6 Program writable
SW7 Select the communication mode of NOD and DT boards : OFF: Fixed length communication
SW8 Combining SW8, SW11 and SW12 to select loading mode ON: Variable length communication
SW9 Reserved
SW10 OFF: Active/Standby ON: Load Sharing
SW11 Combining SW8, SW11 and SW12 to select loading mode
SW12 Combining SW8, SW11 and SW12 to select loading mode
5-14
Maintenance Manual – Troubleshooting Volume
C&C08 Digital SPC Switching System Chapter 5 Main Control System
IV. Locating the fault that the link is broken after the loading
The common cause for the broken link after the loading of the module is that the
software version that the MPU is loaded from the BAM does not match the hardware
version (Basic Input/Output System (BIOS)) of the MPU. That is, the software is
incompatible with the hardware.
In this case, query the software and hardware matching relation table of the board
and check it out. After it is confirmed that the table is correct, select the correct host
software or use the matching MPU to replace the old one.
5-15
Maintenance Manual – Troubleshooting Volume
C&C08 Digital SPC Switching System Chapter 5 Main Control System
V. Suggestions
Of all the faults that cause abnormal module loading, the faults of the transmission
system accounts for a large proportion. Therefore, it is recommended that the
maintenance personnel strengthen their communication with the transmission service
department, so as to improve the ability to rapidly eliminate faults.
I. Detailed description
Abnormities that occur when the programs or data are loaded to the board through
the BAM include:
z The board cannot be loaded. That is, the board cannot be loaded with the
programs or data through the BAM.
z The loading times out. That is, during the loading of a board, such information as
"time-out", "error frame", "refuse" or "retry" occurs and resultantly the board
cannot be loaded.
z The loading is repeated. That is, the board can be loaded. The loading is
repeated after the board is loaded for the first time, which makes it unable to
start the board. Such boards may be AMP, CDP, NCC or SPC.
z The versions do not match. That is, after the board is loaded, the current running
software version is inconsistent with or does not match the host version at the
BAM.
Serial
Fault causes Remarks
No.
If the connector of the network cable is loosely
plugged, the making of the network cable does not
conform to the regulations, or the network adapter
The communication
or the LAN Switch is faulty, then the
1 with the BAM is
communication between the BAM and the switch
faulty.
or between the BAM and the workstation will be
interrupted or become abnormal. In this case, the
board loading may be abnormal.
5-16
Maintenance Manual – Troubleshooting Volume
C&C08 Digital SPC Switching System Chapter 5 Main Control System
Serial
Fault causes Remarks
No.
As the server in the client-server system, the BAM
must run corresponding server software to ensure
that the communication between the foreground
and the background is normal. This server
The BAM software comprises one process manager and nine
application process service processes. Generally they run
2
has not been automatically or start when the BAM is started.
started.
If these processes stop or become abnormal due
to misoperation or other causes, the BAM will be
unable to communicate with the switch and the
board will be unable to be loaded.
The AMP is the bridge for the communication
between the BAM and the switch. Its faults will
3 The AMP is faulty. make the loading of other boards abnormal, for
example, they cannot be loaded or the loading
times out.
The HDLC link is important to the intra-switch
communication. It is the bridge for the
communication between the AMP and other
frames.
The clock is As the HDLC adopts the PCM coding mode, when
4
abnormal. the clock of the switch gets abnormal (for example,
the clock source or clock cable gets faulty), the
HDLC communication will become chaotic. As a
result, the loading of the board cannot be
performed, or is repeated or times out.
III. Locating the fault that the board cannot be loaded or the loading times out
5-17
Maintenance Manual – Troubleshooting Volume
C&C08 Digital SPC Switching System Chapter 5 Main Control System
the management is incomplete, or the software version does not match the hardware
version. To resolve the problem, load this kind of management board again. The
upper-level management boards of common boards include:
z BCC, which is the upper-level management board of the CPC
z QSI of ET16 and STU
z MHI of SPD and SRC
3) Check whether the BAM process starts.
The prerequisite for the normal loading of programs and data to the board from the
BAM is that the BAM software must work normally. This means that the following two
conditions must be met:
z The service process of the SQL Server starts.
z All BAM processes, namely, Warn, DataMan, Bill, Maintain, Test, Stats, Man
Machine Language (MML), Exchange, Perfmon and BillSorter, start.
If the above server processes have not started or their running is abnormal, run the
Windows 2000 Server logout system or restart the operating system.
4) Check whether the communication with the BAM is normal.
The BAM has two network adapters. They are connected to two LANs through two
LAN Switches or HUBs. One LAN is in the switch, while the other is the enterprise
LAN or Wide Area Network (WAN). Therefore, carry out the Ping command to check
the communication status of the BAM, which include:
z The communication between the BAM and the switch
If there is a response after pinging the IP address of each of such boards as AMP,
CDP and SPC on the BAM, it indicates that the communication between the BAM and
the switch is normal. If there is no response after pinging the IP address of some
board (standby board, for example), check whether the connection of corresponding
network cables is normal, for example, whether the cables fall out, are loosely
plugged or in poor contact.
Note:
The IP address of a board is "172.20.the number of the frame where the board
resides.the number of the slot where the board resides". For example, the IP address
of the AMP in Slot 3 of the main control frame is 172.20.1.3; that of the SPC in Slot 5
of Frame 20 is 172.20.20.5. The rest can be deduced by analogy.
z The communication between the BAM and the enterprise LAN or WAN
If there is a response after pinging the IP address of the BAM on a computer at the
enterprise side, it indicates that the communication between the BAM and the
5-18
Maintenance Manual – Troubleshooting Volume
C&C08 Digital SPC Switching System Chapter 5 Main Control System
When the switch clock gets abnormal (for example, the clock source or clock cable
gets faulty), the HDLC communication will become chaotic and the board will be
unable to be loaded. Check the following two parts.
z Check whether the clock cable is loosely plugged or is impaired, and so on.
z Use an oscillograph to measure the clock signals output from such boards as
CKS and CKD. If such cases occur that the waveform is distorted, the phase
relation is chaotic or part of the differential signal is lost, it indicates that the clock
signals are abnormal. In this case, check the clock system.
6) Check whether the AMP starts normally.
The AMP forms the communication bridge for the loading of all other boards. If it
cannot be loaded or is in abnormal status (the loading of it is incomplete), other
boards cannot be loaded.
If the fault has not been located yet, check whether the AMP is faulty. As the AMP
forms the control center of the whole switch, be cautious during the operation of the
AMP. First, switch over the boards. If the fault still exists after the switchover, reset or
restart the AMP.
1) Check whether the hardware version of the board to be loaded matches the
software version in the BAM.
If the hardware version of the board does not match the software version, the board
will be unable to work normally and will automatically reset repeatedly.
In this case, query the software and hardware matching relation table of the board
and check it out. After it is confirmed that the table is correct, select the correct host
software or use the matching board to replace the old one.
2) Check whether the clock of the switch is normal.
The HDLC link is important to the intra-switch communication. It is the bridge for the
communication between the AMP and other frames. As the HDLC adopts the PCM
coding mode, strict requirements have been made to the switch clock.
When the switch clock gets abnormal (for example, the clock source or clock cable
gets faulty), the HDLC communication will become chaotic and the board may be
loaded repeatedly. Check the following two parts.
5-19
Maintenance Manual – Troubleshooting Volume
C&C08 Digital SPC Switching System Chapter 5 Main Control System
z Check whether the clock cable is loosely plugged or is impaired, and so on.
z Use an oscillograph to measure the clock signals output from such boards as
CKS and CKD. If such cases occur that the waveform is distorted, the phase
relation is chaotic or differential signals have lost positive or negative signals, it
indicates that the clock signals are abnormal. In this case, check the clock
system.
If a board keeps requesting loading for more than five minutes and the BAM still does
not respond, the board will be loaded from the flash memory. As the programs and
data in the flash memory may be different from those in the BAM at present, it is
possible that the software version in the foreground is different from that in the
background.
Therefore, during the operation, load boards according to the following operation
regulations.
z Observe the order when loading and turning on the frames in the AM/CM: CPM
→CKM, CCM→CNET→LIMs→SRMs→SPMs
z Load two frames at the same time.
z Reset the CDP board in the CPM frame if to load it separately.
VI. Suggestions
The BAM is an important part for system maintenance, data management, bill
management, alarm management, and so on. Therefore, to reduce board loading
faults, enhance the routine maintenance and management of the BAM.
I. Detailed description
Switchover is often used to check whether the active board is working normally. It is a
common method for fault locating. The common faults related to board switchover
include:
z The switchover cannot be performed or times out. That is, the system refuses to
carry out the board switchover command.
z The active board is abnormal after the switchover. That is, after the switchover,
the status of the standby board cannot be changed to active, or the active and
standby boards reset at the same time.
z Other boards are affected after the switchover. For example, after such main
control boards as MPU and AMP are switched over, other boards are reset or
become abnormal.
5-20
Maintenance Manual – Troubleshooting Volume
C&C08 Digital SPC Switching System Chapter 5 Main Control System
Note:
When the system gets abnormal or faulty, the running the active board is often
unstable and uncertain. Consequently the switchover may cause some unexpected
results. Before a switchover, therefore, back up bills and important data in case of any
exception.
Serial
Fault causes Remarks
No.
During the switchover, check the data of the
active and standby boards. When their types
The type of the active
are inconsistent or do not match (for example,
board is inconsistent
their mailbox addresses are different), errors
1 with or does not match
will occur in the check. As a result, the
that of the standby
switchover gets abnormal, for example, the
board.
status of the active board is abnormal, or other
boards are reset after the switchover.
5-21
Maintenance Manual – Troubleshooting Volume
C&C08 Digital SPC Switching System Chapter 5 Main Control System
III. Locating the fault that the switchover cannot be performed or the
switchover times out
In the C&C08 Maintenance Tool Navigator on the maintenance console, select the
option [Config/Hardware configuration state panel]. Double click to open the hardware
configuration panel interface. Then select the corresponding module and frame, find
the boards that need be switched over and view the color of the boards. If the status
is "standby board abnormal", "faulty", "to be activated", "ready" or "isolated", and so
on, the boards cannot be switched over.
2) Check whether the board allows manual switchover.
There are two cases:
z For the board in the AM/CM, if the active-standby group attribute of the board is
"switchover allowed" and the switchover mode is "manual", the active and
standby boards can be switched over. If the active-standby group attribute of the
board is "switchover prohibited" or the switchover mode is "automatic", the active
and standby boards cannot be switched over manually.
To query the attributes of the board in the AM/CM, type the LST BRD command on
the maintenance console. Then type such information as the module number, frame
number and slot number of the board to be queried as well as other parameters.
Press <F9> to run the query program, then judge whether the switchover of the board
is allowed.
z For the MPU board in the independent switching module, when the Emergency
Action Board (EMA) is offline or faulty, the manual switchover of the MPU is not
allowed either.
3) Check other cases in which the switchover is not allowed.
In special cases such as large traffic volume, high CPU occupation rate, execution of
timing task and data backup, the system will reject the switchover so as to ensure the
safe operation of the switch. If the switchover is performed in a forced way, serious
results will occur, such as bill loss, conversation interruption and resetting of both
active and standby boards. Therefore, be cautious about the switchover under this
circumstance.
IV. Locating the fault that the active-standby boards are abnormal or other
boards are affected after the switchover
5-22
Maintenance Manual – Troubleshooting Volume
C&C08 Digital SPC Switching System Chapter 5 Main Control System
As the control boards such as MPU and SPC are the control center of the system or
module, observe the following three principles when switching over these boards.
z Carry out backup operations, for example, updating charging meters, extracting
bills, backing up supplementary service data and Internet Service Provider (ISP)
data. Otherwise, after the switchover, bills or data may be lost, even the
operation of the system may be chaotic. As a result, some boards (including the
boards switched over) become abnormal or are reset.
z Check the current operation status of the system to avoid the switchover in the
case of high CPU occupation rate caused by such factors as large traffic volume,
execution of timing task of traffic statistics and data backup. This is because the
switchover under this circumstance increases the burden of the CPU, adds
uncertain factors to the operation of the system and causes switchover failure or
other abnormities.
z The time interval between two switchovers should not be too short (an interval of
more than 30 minutes is advisable). Because during the switchover, the system
will perform smooth processing to the data of the active-standby boards, which
needs about 20 minutes. If another switchover is performed during this period,
serious results such as bill loss, data confusion and system restart will occur.
2) Check whether the type of the active board is consistent with that of the standby
board.
During the switchover, check the data of the active and standby boards. When their
types are inconsistent or do not match (for example, their mailbox addresses may be
different), errors will occur in the check. As a result, the switchover gets abnormal, for
example, the status of the active board is abnormal, or other boards reset after the
switchover.
V. Suggestions
Switchover is riskful. Carry out backup operations to avoid or reduce possible loss.
5-23
Maintenance Manual – Troubleshooting Volume
C&C08 Digital SPC Switching System Chapter 6 Clock System
6.1 Overview
It is the discrete pulses, obtained after information has undergone the PCM coding,
that are transferred in the digital network. Therefore, in the case that clock
frequencies or phases of any two pieces of digital switching equipment are
inconsistent, or digital bit streams have phase drift or jitter in the transmission process,
overflow or underflow (sliding damage) is possible in the buffer memory of a digital
switching system. It may consequently cause system running confusion.
In the C&C08 Digital SPC Switching System, correct clock is the prerequisite and
base of the normal running of the switching, connection, signaling system,
inter-module communication & other functional modules. Once the clock system is
faulty, it may affect subscribers over an extensive area or of a global office.
Table 6-1 lists the common faults that may occur to the clock system.
Table 6-1 Common faults that may occur to the clock system
Impact on
semi-permanent Interrupted semi-permanent connection
connections
Impact on trunk
Slip frames or increasing BER
Impact on the circuits
trunk system Impact on signaling Broken links, frequent link switchover, signaling load
links congestion
6-1
Maintenance Manual – Troubleshooting Volume
C&C08 Digital SPC Switching System Chapter 6 Clock System
Impact on board
Frequent board switchover
running
Table 6-2 lists the common fault causes that may occur to the clock system.
Table 6-2 Common fault causes that may occur to the clock system
6-2
Maintenance Manual – Troubleshooting Volume
C&C08 Digital SPC Switching System Chapter 6 Clock System
In AM/CM interface frames, the QSIs receive clock signals and output them to
individual boards. Different from that, the clock signals in other AM/CM frames apply
the bus structure. The connection position of clock lines in the SPM frame keeps the
same as that in the CPM frame, which will not be discussed here. The clock of the
SRM frame is from the MHI. Each clock line contains one send-receive clock (8 MHz,
8 kHz). The structure will not be discussed here.
Figure 6-1 gives the flow direction of AM/CM internal clock signals.
6-3
Maintenance Manual – Troubleshooting Volume
C&C08 Digital SPC Switching System Chapter 6 Clock System
CPM CCM
A C B F B B F
M D C S A A S
P P P N C C N
S S
LIM N N
Q U U
S
I 16.384MHz
8KHz
8KHz or
2.048MHz
E
T S O M
1 T B H
6 U C I
8KHz
8.192MHz
SRM
S S
P R
D C
The flow direction of clock signals from the AM to the SM: AM (through OBC (or RBC))
-> Fiber optics -> SM (or RSM) (through OPT (or OLE)), where OPT (or OLE) sends
clock signals to the BNET.
Of them, the clock signals from the OPT to the BNET include OPT8k, OPT2M and
OPT4M.
The flow direction of clock signals from the AM to the RSM: AM (through ET16 (or
STU)) -> Transmission system -> RSM (through DTF), where the DTF sends clock
signals to the BNET.
The clock signals output by the DTF include 8 kHz differential clock, including DT8k0+,
DT8k0, DT8k1+ and DT8k1-.
6-4
Maintenance Manual – Troubleshooting Volume
C&C08 Digital SPC Switching System Chapter 6 Clock System
The distribution of clock signals in the SM is the same as that in the RSM. The
following text gives the flow direction of SM internal clock signals.
It is the BNET that directly supplies clock signals for the boards in the SM main
control frame. For the boards in other frames, it is the CKV of the BNET that supplies
clock signals. Having been driven by the CKV, clock signals are sent to the boards in
the interface frames through external HW clock cables, as shown in Figure 6-2 below.
BNET
N S M M M M A T
O I P E F C L C
D G U M C 2 M I
I. Detailed description
Once the clock system is faulty, the following cases may occur to the subscriber
system.
z Conversation noise, unidirectional call, call released in the conversation process
z Difficult Internet dial-up, frequent disconnection, slow browsing speed
z The failure that a fax machine cannot receive or send fax
z Interrupted semi-permanent connection
Refer to Table 6-2 Common fault causes that may occur to the clock system.
6-5
Maintenance Manual – Troubleshooting Volume
C&C08 Digital SPC Switching System Chapter 6 Clock System
In the SM networking mode, the faulty part may be "DTF -> External transmission
system -> RSP".
z If intra-module or inter-module connection is abnormal, the following cases are
possible according to different networking modes.
In the case of an SM, the faulty part of the clock system may be "CKD -> Clock lines
-> QSI -> OBC or RBC -> Fiber optics -> OPT or OLE -> BNET -> CKV".
In the case of an RSM, the faulty part of the clock system may be "CKD -> Clock lines
-> QSI -> ET16 or STU -> External transmission system -> DTF -> Clock lines ->
BNET -> CKV".
z If inter-office connection or calls of an entire switch are abnormal, the faulty part
of the clock system may be "External clock source -> CKS -> CKD".
3) Query the working state of the clock source and the clock board.
Select [Device management/Clock management] on C&C08 Command Navigator on
the maintenance console and select related commands. Or type the following
commands on the MML operating interface to query the working state of related clock.
z Use the DSP CKSSRC command to query the working state of external clock
source.
6-6
Maintenance Manual – Troubleshooting Volume
C&C08 Digital SPC Switching System Chapter 6 Clock System
z Use the DSP CKS command to query the working state of the AM/CM clock
board.
4) Check the distribution of the clock lines.
Check whether the related clock lines or HW cables are broken or in poor contact or
too close to interference sources, for example, fan, Uninterruptable Power Supply
(UPS), computers, wireless equipment.
5) Check the working state of related clock transmission boards.
Two cases are possible.
z For related boards in active-standby working mode, for example, CKS, CKD,
SNU, QSI, OBC, OPT, BNET, switch over them to check whether the active
boards are faulty.
The switchover command is SWP BRD and related operation procedures should be
strictly observed, for example, to back up bills before the switchover, to switch over
boards when the traffic intensity is low.
z For related boards in load-sharing working mode, for example, DTF, ET16, STU,
OBC or OPT, unplug or change the possibly faulty board. If the fault has been
cleared, it indicates that the unplugged or changed board has been faulty.
6) Measure by instruments for precision locating.
For further locating, instruments (for example, oscillograph) can be used to measure
the switch's clock signals point by point from the end point to the origin point
according to the flow direction of clock signals. Compare the waveforms of clock
signals at different points and thus the faulty point can be found.
IV. Suggestions
z Do not put clock signal lines close to interference sources, for example, fan, UPS,
computers, wireless equipment, in case of any exceptions such as wave
distortion of clock signals.
z Regularly test clocks to know the running state of the clock system.
I. Detailed description
Once the clock system is faulty, the following cases may occur to the trunk and
signaling system.
z Exceptions occur to trunk circuits such as slip frames or increasing BER, causing
such faults as inter-office calls mis-routing, conversation noise, call released in
the conversation process.
6-7
Maintenance Manual – Troubleshooting Volume
C&C08 Digital SPC Switching System Chapter 6 Clock System
z Such exceptions or faults occur to signaling links as broken links, frequent link
switchover, signaling load congestion, which fail inter-office calls.
Refer to Table 6-2 Common fault causes that may occur to the clock system.
Type the DSP CKS command on the MML operating interface and type the frame
number & slot number of the active CKS. Then specify other related parameters and
press <F9> to carry out the command. Judgement can be made with reference to the
returned results.
For instance, if the switch traces BITS clock in actual situation, the working state
should be "Tracing mode", the access mode "2M0 access", and the phase-lock mode
"PDH". Similarly, judgement can be made in other cases.
2) Query the working state of the clock source and the clock board.
Select [Device management/Clock management] on C&C08 Command Navigator on
the maintenance console and select related commands. Or type the following
commands on the MML operating interface to query the working state of related clock.
z Use the DSP CKSSRC command to query the working state of external clock
source.
z Use the DSP CKS command to query the working state of the AM/CM clock
board.
3) Check the distribution of the clock lines.
Check whether the related clock lines or HW cables are broken or in poor contact or
too close to interference sources, for example, fan, UPS, computers, wireless
equipment.
4) Check the working state of related clock transmission boards.
Two cases are possible.
z For related boards in the active-standby working mode, for example, CKS, CKD,
SNU, QSI, OBC, OPT, BNET, switch over them to check whether the active
boards are faulty.
The switchover command is SWP BRD and related operation procedures should be
strictly observed, for example, to back up bills before the switchover, to switch over
boards when the traffic intensity is low.
6-8
Maintenance Manual – Troubleshooting Volume
C&C08 Digital SPC Switching System Chapter 6 Clock System
z For related boards in the load-sharing working mode, for example, DTF, ET16,
STU, OBC or OPT, unplug or change the possibly faulty board. If the fault has
been cleared, it indicates that the unplugged or changed board has been faulty.
5) Measure by instruments for precision locating.
For further locating, instruments (for example, oscillograph) can be used to measure
the switch's clock signals point by point from the end point to the origin point
according to the flow direction of clock signals. Compare the waveforms of clock
signals at different points and thus the faulty point can be found.
IV. Suggestions
z Do not put clock signal lines close to interference sources, for example, fan, UPS,
computers, wireless equipment, in case of any exceptions such as wave
distortion of clock signals.
z Regularly test clocks to know the running state of the clock system.
I. Detailed description
For the main control system, clock primarily affects its inter-module communication,
board loading and board running. Common faults are given below.
z The inter-module communication is interrupted, for example, broken links.
z The BAM fails to fetch the bills of a module or the bill fetching times out.
z A board cannot be loaded, or has been repeatedly loaded, or the loading times
out.
z In the running process, frequent switchover occurs to some active-standby
boards, for example, the SPC.
Refer to Table 6-2 Common fault causes that may occur to the clock system.
1) Query the working state of the clock source and the clock board.
Select [Device management/Clock management] on C&C08 Command Navigator on
the maintenance console and select related commands. Or type the following
commands on the MML operating interface to query the working state of related clock.
z Use the DSP CKSSRC command to query the working state of external clock
source.
6-9
Maintenance Manual – Troubleshooting Volume
C&C08 Digital SPC Switching System Chapter 6 Clock System
z Use the DSP CKS command to query the working state of the AM/CM clock
board.
2) Check the distribution of the clock lines.
Check whether the related clock lines or HW cables are broken or in poor contact or
too close to interference sources, for example, fan, UPS, computers, wireless
equipment.
3) Check the working state of related clock transmission boards.
Two cases are possible.
z For related boards in the active-standby working mode, for example, CKS, CKD,
SNU, QSI, OBC, OPT, BNET, switch over them to check whether the active
boards are faulty.
The switchover command is SWP BRD and related operation procedures should be
strictly observed, for example, to back up bills before the switchover, to switch over
boards when the traffic intensity is low.
z For related boards in the load-sharing working mode, for example, DTF, ET16,
STU, OBC or OPT, unplug or change the possibly faulty board. If the fault has
been cleared, it indicates that the unplugged or changed board has been faulty.
4) Measure by instruments for precision locating.
For further locating, instruments (for example, oscillograph) can be used to measure
the switch's clock signals point by point from the end point to the origin point
according to the flow direction of clock signals. Compare the waveforms of clock
signals at different points and thus the faulty point can be found.
IV. Suggestions
z Do not put clock signal lines close to interference sources, for example, fan, UPS,
computers, wireless equipment, in case of any exceptions such as wave
distortion of clock signals.
z Regularly test clocks to know the running state of the clock system.
6-10
Maintenance Manual – Troubleshooting Volume
C&C08 Digital SPC Switching System Chapter 6 Clock System
3) Grounding point: GND in Figure 6-3 is recommended. The coaxial shielding layer
in the clock frame may also be used.
4) Requirement: ±4×10-7 for Stratum-2 clock and ±4.6×10-6 for Stratum-3 clock.
PIN 1 GND
R8k1+ R8k1-
PIN8
1) Instrument: oscillograph
2) Test point: input clock signals C2M0, C2M1, F8k0 and F8k1 in Figure 6-5 and
Figure 6-6.
3) Grounding point: GNDs in Figure 6-5 are recommended.
4) Method & requirement: Check whether there are clock signals and observe the
phase relation between 2 MHz and 8 kHz signals to find whether there are clock
6-11
Maintenance Manual – Troubleshooting Volume
C&C08 Digital SPC Switching System Chapter 6 Clock System
faults caused by poor contact of clock lines. Figure 6-4 gives the clock signals
output by the clock frame to other frames.
Figure 6-4 Clock signals output by the clock frame to other frames
The following table gives the meanings of tLP and tCK. Similar to frame #2, frame #3
has differential 2 MHz signals on the left and differential 8 kHz signals on the right.
The grounding points may be screw caps of the hot pluggable sockets on the
backplane, or the middle pins of rows 22, 23, 24 in Figure 6-6.
Nam
Meaning MIN MAX Unit
e
Width of frame synchronization
tLP 244 − ns
header
48 JB68 or JB77
1
JB69 or JB78
CLK0 10 F8K0-
C2M0+ F8K0+
C2M0-
CLK1 13
F8K1-
C2M1+
F8K1+
C2M1-
18
GND
Figure 6-5 Clock input test points on the backplane of frame #2 (SNU)
6-12
Maintenance Manual – Troubleshooting Volume
C&C08 Digital SPC Switching System Chapter 6 Clock System
15
JB103 (or JB106)
CLK0
CLK1
21
22
23
24
Figure 6-6 Wiring diagram on the backplane of frame #3 (CNU) for clock input
Note:
On the backplane of the 128-SM central switching network frame, there are two screw
caps of the hot pluggable sockets. The upper one is GND and the lower one is +5 V.
1) Instrument: oscillograph
2) Test point: as shown in Figure 6-7.
3) Grounding point: GNDs in Figure 6-9 are recommended. Screw caps of the hot
pluggable sockets on the backplane of the CCM frame may also be used.
4) Method & requirement: Check whether there are clock signals and observe the
phase relation between 2 MHz and 8 kHz signals to find whether there are clock
faults caused by poor contact of clock lines.
6-13
Maintenance Manual – Troubleshooting Volume
C&C08 Digital SPC Switching System Chapter 6 Clock System
CLK0 15 F8K0-
C2M0+ F8K0+
C2M0-
CLK1 18
F8K1-
C2M1+
F8K1+
C2M1-
25
GND
1) Instrument: oscillograph
2) Test point: It is as shown in Figure 6-8. CLK0 is on the eighth row and CLK1 the
eleventh row. The 2 MHz differential signals are on the left and the 8 kHz
differential signals on the right. The active and standby QSIs share these same
clock signals. Therefore, when the clock lines are connected to the active boards,
test points are the corresponding connecting points on the standby board.
3) Grounding point: GNDs of the middle line in Figure 6-8 are recommended. Screw
caps of the hot pluggable sockets on the backplane of the interface frame may
also be used.
4) Method & requirement: Check whether there are clock signals and observe the
phase relation between 2 MHz and 8 kHz signals.
6-14
Maintenance Manual – Troubleshooting Volume
C&C08 Digital SPC Switching System Chapter 6 Clock System
QSI
1
2
3
4
5
6
C2M0+ 7
8 F8K0-
C2M0- 9 F8K0+
10
11 F8K1-
C2M1+ 12 F8K1+
C2M1-
GND
1) Instrument: oscillograph
2) Test point: It is as shown in Figure 6-9. The first test point is DT8k0- or DT8k1-
on the switching network board. The second test point is CK2M- of the 2 MHz
signal of the MC2.
3) Grounding point: GND in Figure 6-9 or screw caps of the hot pluggable sockets
on the backplane of the main control frame of an SM.
4) Method & requirement: With DT8k as the trigger source, the waveform of the
2 MHz signal CK2M of MC2 should have no sliding, allowing a jitter within 100 ns.
The DT8k extracted by a different DTF is different and both pulse & square wave
are possible. The phase relation between DT8k and the 2 MHz signal CK2M is
uncertain. As long as locked, the DT8k waveform will have no sliding and it will
be safe, as shown in Figure 6-10.
6-15
Maintenance Manual – Troubleshooting Volume
C&C08 Digital SPC Switching System Chapter 6 Clock System
DT8K0-
64 ○ ○ ○ ○
DT8K1-
65 ○ ○ ○ ○
27 ○ ○ ○ CK2M
29 ○ ○ ○ FOD
CK2M-
73 ○ ○ ○ ○
32 ○ ○ ○ GND
○ ○ ○ ○
DT8K-
CK2M
1) Instrument: oscillograph
2) Test point: It is as shown in Figure 6-11. The first test point is OPT2M of the
2 MHz signal input by the OPT. The second test point is CK2M of the 2 MHz
signal of the MC2.
3) Grounding point: GND in Figure 6-11 or screw caps of the hot pluggable sockets
on the backplane of the main control frame of an SM.
4) Method & requirement: With OPT2M as the trigger source, the CK2M waveform
should have no sliding. Compared with OPT2M, CK2M can have a fixed time
delay t (t<50 ns) but its waveform should be steady, allowing a jitter within 5 ns,
as shown in Figure 6-12.
6-16
Maintenance Manual – Troubleshooting Volume
C&C08 Digital SPC Switching System Chapter 6 Clock System
27 ○ ○ ○ CK2M
t <50nS
OPT2M
CK2M
1) Instrument: oscillograph
2) Test point: It is as shown in Figure 6-13. The first test point is the 2 MHz signal
CK2M of the MC2. The second test point is the 8 kHz signal FOD. The third test
point is the 4 MHz signal /CK4M of the MFC (or NO7). The fourth and fifth test
points are the two different 8 kHz signals FSX and /F0 of the SIG. These five
signals are output by the switching network. Figure 6-14 shows the signal output
sequence.
3) Grounding point: GNDs in Figure 6-13 or screw caps of the hot pluggable
sockets on the backplane of the main control frame of an SM.
4) Method: Use a dual-channel oscillograph to observe two signals at a time. Use
the signal of a lower frequency as the trigger source and adjust the trigger level,
time & amplitude to observe the phase relations between different signals.
5) Requirement: The phase relations between different signals are as shown in
Figure 6-14. The jitter should be no more than 5 ns.
6-17
Maintenance Manual – Troubleshooting Volume
C&C08 Digital SPC Switching System Chapter 6 Clock System
4 /F0 4 /F0
5 FSX
27 CK2M
13 /CK4M
29 FOD 15 CK2M
30 GND 17 GND
32 GND
Only the test of HW clock signals of the DRV and DTF is discussed here.
1) Instrument: oscillograph
2) Test point: It is as shown in Figure 6-15 and Figure 6-16.
3) Grounding point: They are screw caps of the hot pluggable sockets on the
backplane.
4) Method & requirement: The 8 kHz frame header signal of the HW to be tested
(generally on the same board) will be taken as the reference. As per test points,
connect the 8 kHz frame header signal and the HW to be tested. Select 8 kHz as
the trigger source and the signal change at HW timeslots can be seen.
6-18
Maintenance Manual – Troubleshooting Volume
C&C08 Digital SPC Switching System Chapter 6 Clock System
2
UHW1 UHW1
3
UHW0 UHW0
4 DHW12
DHW11
5
DHW01 DHW02
6
2M 2M
8
8K 8K
UHW0+ 8
UHW0-
9
UHW1+ UHW1-
10
DHW0+ DHW0-
11
DHW1+ DHW1-
15
FSX+(8K) FSX-
DT8K+ 16
DT8K-
6-19
Maintenance Manual – Troubleshooting Volume
C&C08 Digital SPC Switching System Chapter 7 Terminal System
7.1 Overview
The inner structure of the terminal system applies the client-server model and the
core is the BAM. The BAM is the server in the client-server architecture. It connects
with the switch and individual service stations through two different local area
networks, and thus is a bridge for man-machine communication.
Table 7-1 lists the common faults that may occur to the terminal system.
Table 7-1 Common faults that may occur to the terminal system
7-1
Maintenance Manual – Troubleshooting Volume
C&C08 Digital SPC Switching System Chapter 7 Terminal System
Table 7-2 lists the common fault causes that may occur to the terminal system.
Table 7-2 Common fault causes that may occur to the terminal system
7-2
Maintenance Manual – Troubleshooting Volume
C&C08 Digital SPC Switching System Chapter 7 Terminal System
The communication architecture of the terminal system comprises the BAM, LAN
Switch or HUB, and individual workstations, as shown in Figure 7-1.
7-3
Maintenance Manual – Troubleshooting Volume
C&C08 Digital SPC Switching System Chapter 7 Terminal System
……
Ethernet
LAN Switch
Running software:
172.20.200.200 Hardware requirements:
Windows NT Server 4.0
NT Service Pack 5 CPU: Pentium II 300 MHz,one or more
IE 4.01 SP1
Memory: >= 128 MB, 256 MB recommended
MS SQL Server 7.0
DAO Hard disk: >= 4.3 GB
C&C08 switch BAM s/w
Network adapter: 2 or more
BAM
以以以
LAN Switch
Running software:
Hardware requirements:
Win98/Win95
CPU: Pentium II 300 MHz 。。。
IE 4.01 SP1
Memory: >= 32 MB
DAO
C&C08 switch client s/w Hard disk: >= 100 MB
Workstation Network adapter: 1 Workstation Workstation
Note:
The BAM & WS hardware requirement vary with the host version.
As shown in the above figure, the BAM connects two subnets, client terminal and the
host, through TCP/IP. That is, the server exchanges data with the host through a LAN
Switch and connects multiple workstations through another LAN Switch (in star
connection mode), which may be maintenance console, data management console or
alarm console.
Because the system foreground communicates with the background through TCP/IP,
the BAM server should have two network adapters. The two adapters have different
IP addresses and are connected to the 100 Mbit/s network interfaces of the two LAN
Switches. Thus, they are in different subnets. One adapter is for the
foreground-background communication and its IP address is set to 172.20.200.200.
This subnet is closed and external users cannot directly visit it. The other one is for
7-4
Maintenance Manual – Troubleshooting Volume
C&C08 Digital SPC Switching System Chapter 7 Terminal System
the communication to workstations (service stations) and its IP address can be set in
accordance with the requirements of the enterprise network. This subnet is open and
can be connected to the LAN or WAN.
The entire BAM service system has twelve processes, as shown in Figure 7-2.
Perfmon process
Warn process
Dataman process
Bill process
Billsorter process
Test process
Stats process
DataCom process
Trap process
DBLIB
Database
7-5
Maintenance Manual – Troubleshooting Volume
C&C08 Digital SPC Switching System Chapter 7 Terminal System
Each part is relatively independent of the others and thus it eases the system
debugging & maintenance. The service stations are independently running at the
same time. Once one fails, other service stations can still work normally.
Each process has a shared memory which stores the received data packets from
other processes and thus connects all independent processes. For each process,
there is a special thread at the bottom layer to receive data frames from other
processes. Each process uses independent threads to send information to other
processes. Each sending thread corresponds to a process. Therefore, the bottom
communication mode of each process frame applies a receiving thread and multiple
7-6
Maintenance Manual – Troubleshooting Volume
C&C08 Digital SPC Switching System Chapter 7 Terminal System
I. Software environment
D:\Mssql7--For MS_SQL_Server7.0
Besides, available Drives E and F, and so on, should be configured on the system. To
minimize the impact on the terminal system caused by unknown factors, do not install
other applications or software on the server.
The following text bases on the supposition that the above default settings are used
during the installation.
After the successful installation of the server software, the system has created the
following directories. In these directories, the program and part data of the terminal
system are stored. The directory structure is given below.
The terminal system server's data directories store the daily running data.
7-7
Maintenance Manual – Troubleshooting Volume
C&C08 Digital SPC Switching System Chapter 7 Terminal System
After the server program is in service, the system will generate data configuration files
Db_?.dat (? is a wildcard) according to configuration commands. Do not delete the
files in this directory.
V. NT system folder
The terminal system's client configuration file is in the root directory of Windows 2000
Server.
The program will create the following directories according to the configured values in
the registry in the running process of the terminal system server software.
D:\Bill--Storing bills
Do not delete these directories at random because what they store are running data
and backed-up files.
7-8
Maintenance Manual – Troubleshooting Volume
C&C08 Digital SPC Switching System Chapter 7 Terminal System
7.2.4 Terms
I. LAN Switch
In the networking, many LAN Switches are used and one of them is used as a
standby LAN Switch, which is not in service generally. Once a working LAN Switch
gets faulty, the standby LAN Switch will replace it and restore the network
communication in a short time.
BAM hard disks apply the redundancy & fault-tolerant technique of "Redundant Array
of Independent Disks 5 (RAID5) + Hot Spare" and a disk-striping strategy with a
special check disk. Data has been striped across multiple disks to improve read-write
performance. The check data is also stored in multiple disks, instead of a special
check disk. Once a disk gets faulty, the controller can recover or regenerate the lost
data from existing disks. RAID5 requires at least three disks. The effective availability
ratio of the disk space is (N-1)/N, where N is the number of disks in the disk array.
Three or four LAN Switches are used to achieve the BAM-host and BAM-client
communication. One of them is for cold backup and not in service in general
situations. Once a working LAN Switch gets faulty (network communication becomes
faulty and LAN Switch indicators are abnormal), the standby one can be used to
replace it and thus the communication can be restored in a very short time.
7-9
Maintenance Manual – Troubleshooting Volume
C&C08 Digital SPC Switching System Chapter 7 Terminal System
2) Supply power for the standby LAN Switch and then it becomes the working LAN
Switch.
3) Change the faulty LAN Switch and use the new LAN Switch as a standby one.
Once a network adapter used for the BAM-host or BAM-client connection is faulty (the
network adapter indicators are abnormal and the network has been blocked), use the
standby network adapter to restore the communication with reference to the following
steps.
1) In normal situations, only two network adapters can be seen. The other one has
no driver program. Of the two network adapters, one is for the connection to the
LAN formed by maintenance clients and the other to the LAN formed by host
boards. Through its IP address, the one connected with the host can be
recognized because the IP address of the network adapter connected to the host
is permanently 172.20.200.200. To get the IP address of a network adapter,
carry out the command "ipconfig" or click Protocols tab on the network
configuration interface. Click <Add…> button on the network configuration
interface to install the driver program for another network adapter.
2) Then an interface pops up which gives Windows-supplied driver programs. If the
type of the network adapter is given in the list, select it and click <OK>. If the
driver program is unavailable, click <Have Disk…>.
3) In this case, the driver program is generally installed from a floppy disk. Insert
the network adapter's driver disk, specify the directory, for example, "A:\", and
click <OK>.
4) Select a correct type of the driver program. Click <OK> and Windows 2000
Server will install the driver program onto the system from the floppy disk.
5) After the successful installation, a message and network adapter diagnostic tool
may be given. Click <Close>. The system will install all searched network
adapters of the same type onto the system.
6) Delete the faulty adapter.
7) Configure protocol for the newly added adapter. Click Protocol tab on the
network configuration interface. Select TCP/IP protocol and click <Properties…>
button to configure IP address for the adapter. If it is the network adapter
connected to the host that gets faulty, select the newly added adapter in the
adapter pull-down list and set the IP Address & Subnet Mask to original values. If
it is the network adapter connected to the client that gets faulty, suppose the
originally configured IP address is 129.9.9.100 and the subnet mask 255.255.0.0.
Then the IP address and subnet mask of the newly added network adapter are
129.9.9.100 and 255.255.0.0 respectively. Click <OK> to complete the
configuration.
7-10
Maintenance Manual – Troubleshooting Volume
C&C08 Digital SPC Switching System Chapter 7 Terminal System
8) Click <Close> to complete the protocol configuration. Then, the system prompts
to restart the computer to enable the configuration.
9) Unplug the network cable connected to the faulty network adapter and insert it to
the interface on the standby network adapter. Thus, the network adapter fault is
recovered.
BAM hard disks apply the "RAID5 + Hot Spare" redundancy & fault-tolerant technique
and a disk-striping strategy with a special check disk. Data has been striped across
multiple disks to improve read-write performance. The check data is also stored in
multiple disks, instead of a special check disk. Once a disk gets faulty, the controller
can recover or regenerate the lost data from existing disks. RAID5 requires at least
three disks. The effective availability ratio of the disk space is (N-1)/N, where N is the
number of disks in the disk array. Generally, the BAM has four hard disks.
When a BAM hard disk is faulty (hard disk indicator is abnormal), unplug the faulty
disk and insert a new disk with same capacity. The system will automatically check
the data and generate data on the new disk. Thus, the hard disk fault is recovered.
Note:
z It may take twenty to thirty minutes to check and regenerate the data of a hard
disk of 9 GB. In order not to affect the BAM system, it should be carried out when
the BAM system is idle, for example, 23:00 ~ 01:00 in the night.
z It is necessary to check whether the used BAM hard disk has used the "RAID5 +
Hot Spare" redundancy and fault-tolerant technique.
When the BAM server fails to work normally due to hardware failure or other reasons,
start up an emergency workstation with reference to Appendix C Emergency WS in
C&C08 Digital SPC Switching System Operation Manual - Routine Operation Volume.
The switch's BAM operating system is Windows 2000 Server and its database is SQL
Server.
7-11
Maintenance Manual – Troubleshooting Volume
C&C08 Digital SPC Switching System Chapter 7 Terminal System
Note:
Because anti-virus program may cause unexpected disaster to the system, it is
necessary to consider the safety operation specifications in the worst case that the
operating system totally fails. Carry out the following operating procedures in the strict
sequence except the specially noted points.
When running an anti-virus program on the BAM, it is required to stop the BAM
software.
Thus, the connection from the BAM to both the switch and maintenance terminal is
disconnected. In this case, no maintenance operations can be carried out and the
console will fail to work.In order not to interrupt BAM services, use an emergency
workstation to replace the BAM when an anti-virus program is running on the BAM. In
this case, there are the following advantages and disadvantages.
z Advantages: 1) Maintenance operations can be carried out through the
maintenance terminals. 2) The console can still be in service and can send bills
to the background once the bill pool is full, causing no loss of bills (there is a
small probability that the bill pool is full), when an anti-virus program is running
on the BAM.
z Disadvantages: 1) It will take time & workforce to prepare an emergency
workstation. 2) It is necessary to use the Bam & BillData databases of the
emergency workstation to replace BAM's Bam & BillData databases when
switching back to the BAM, if engineers have configured data on the
maintenance terminal, has modified data on the console, or the switch has sent
bills when an anti-virus program is running on the BAM.
Maintenance staff should have a thorough consideration of the advantages &
disadvantages of using an emergency workstation and also the actual situations, for
example, traffic density, maintenance & console situations, before making a decision.
1) Update the host meters of all modules and fetch all bills. On the client operating
interface, carry out the RST BILPOL command, then STR BILIF to fetch bills at
once.
2) Copy all unsettled bills in the bill file directory to both MOs and a computer
without virus.
7-12
Maintenance Manual – Troubleshooting Volume
C&C08 Digital SPC Switching System Chapter 7 Terminal System
Carry out the BKP DB command to backup accumulated meters database & BAM
database. Copy the backed-up database to both MOs and a computer without virus.
Copy all files in the directory where the switch host's loading files are stored, for
example, D:\data, to both MOs and a computer without virus.
The backed-up BAM database and accumulated meters database can be used to
basically recover the BAM once problems occur during the running of an anti-virus
program on the BAM. If to recover the BAM to the original state before the running of
the anti-virus program, back up other databases. Thus, other databases can also be
recovered once problems occur during the running of the anti-virus program.
1) Run the SQL Server tool QUERY ANALYZER and carry out the following
statements with the traffic statistics database as an example.
USE master
GO
sp_dropdevice tempdumpdev
GO
2) Replace "Stats" in the above statements by "Test" to back up the test database.
3) Copy the backed-up database to both MOs and a computer without virus.
If not to use the emergency workstation, skip this step. If to use it, refer to the
following operations.
7-13
Maintenance Manual – Troubleshooting Volume
C&C08 Digital SPC Switching System Chapter 7 Terminal System
If not to use the emergency workstation, skip this step. If to use it, refer to the
following operations.
1) If the emergency workstation is just to prevent the overflowing of the bill pool, it
can be used when BAM fails to restore after it has no communication with the
switch for six hours.
2) Start the emergency workstation with reference to the section 7.3.4 Starting up
Emergency Workstation.
3) Carry out the SET CONSOLE command to set the console interface switch to
OFF and not to run the console set data.
7-14
Maintenance Manual – Troubleshooting Volume
C&C08 Digital SPC Switching System Chapter 7 Terminal System
Note:
After the emergency workstation is in service, it is recommended not to configure data
or fetch bills. It is because after switching back to the BAM, it is necessary to use the
emergency workstation's Bam & accumulated meters databases to recover BAM's
Bam & accumulated meters databases if there have been data configuration or bill
fetching operations. Besides, the backup and recover operations are relatively
complicated.
X. Clearing virus
1) Scan BAM's hard disks in accordance with the instructions of the anti-virus
program. If any virus has been found, clear it and then restart the computer.
2) If some virus in the master boot sector cannot be cleared, use a clean starter
disk (for example, DOS floppy disk or Windows 9X optical disks) to start the
computer, then carry out the FDISK/MBR command to rewrite the master boot
sector codes.
3) After virus clearing, uninstall the anti-virus program because it may conflict with
BAM service station programs and cause the BAM software to run abnormally.
4) Select [Control Panel/Services], set the startup mode of "BAMSERVICE" to
"Automatic" and start it.
To ensure the virus clearing has no impact on the BAM software, it is necessary to
charge, fetch or query bills and carry out related operation & maintenance tests.
In the worst case that the BAM is down due to virus infection, instead of being down
in the virus clearing process, there is a small probability of data loss. At this time, refer
to C&C08 Digital SPC Switching System, Installation Manual - Volume 2 to reinstall
the BAM and recover the data before the failure.
Note:
When reinstalling the BAM, do not use Win 98 Fdisk command to format the hard
disks because it will format the hard disks to the FAT32 format, which is
unrecognizable for WinNT and thus WinNT cannot be installed. Do use WinNT
installation disk to format the hard disks in the installation process. For specific
instructions, refer to WinNT installation.
7-15
Maintenance Manual – Troubleshooting Volume
C&C08 Digital SPC Switching System Chapter 7 Terminal System
I. Special attention
The anti-virus software can clear most viruses from the files and the files can still be
used after the virus clearing. For some viruses, however, the anti-virus software can
only find them but fail to clear them. In this case, the anti-virus software may directly
delete the infected file, or isolate the infected file, that is, rename this file and save it
to other directory. It is also possible that the anti-virus software damages the infected
files and causes these files unavailable. Therefore, pay special attention to the
following points in the virus clearing process.
1) Configure the anti-virus software to provide only the virus-finding function
With a consideration of above risks, general anti-virus software can supply only the
virus-finding function. That is, the anti-virus software only scans files, reports viruses,
if any, but does not clear the viruses or modify the suspected files. As for how to
configure the anti-virus software to provide only virus-finding function, refer to its
instructions & online help.
2) Close the real-time guard function
Because some anti-virus software has the real-time virus guard function, it may have
cleared viruses in the virus finding process but users just want to find viruses instead
of clearing them. Therefore, it is necessary to disable this function in the virus finding
process. As for how to close the anti-virus software's real-time guard function, refer to
its instructions & online help.
1) General anti-virus software provides the function to make DOS starter disk,
which only identifies FAT partitions generally. If there are vendors who can
provide software which can identify New Technology File System (NTFS)
partitions, give priority to their products.
2) Download the latest virus database or virus engine patch from the supplier's
web-site to find and clear viruses. If the old anti-virus software is used, some
virus variants or new viruses may be unrecognizable. Not download patches
from non-supplier's web-site in case of some viruses in the patches.
3) In the running process, the anti-virus software may store some temporary files to
its installation directory or \TEMP directory in the partition of the system directory
of Windows 2000 Server. If there are many infected files for processing, the
generated temporary files may occupy some disk space. After virus finding and
clearing, uninstall the anti-virus software. If the temporary files have not been
totally deleted, find them and delete them.
7-16
Maintenance Manual – Troubleshooting Volume
C&C08 Digital SPC Switching System Chapter 8 Alarm System
8.1 Overview
The switch's alarm system includes alarm detection, alarm processing and alarm
output. It detects all software and hardware exceptions or faults that occur in the
switch's running process, gives audio and visual alarms through alarm indicators or
alarm box, or displays alarms on the alarm console, after the processing of
maintenance software. It is a significant inspection part in the switch routine
maintenance.
The alarm system comprises the Alarm Interface Board (ALM), Alarm Drive Board
(AMD), Environment & Power Monitoring Board (ESC), BAM, alarm indicators,
alarm box and alarm console. Its software primarily has the host alarm processing
module and BAM alarm processing module.
Table 8-1 lists the common faults that may occur to the alarm system.
Table 8-1 Common faults that may occur to the alarm system
No alarm data
The system sends no alarm information to the alarm console.
Alarm reported
console Abnormal The alarm information cannot automatically refresh or
refreshing refreshes at a very low speed.
8-1
Maintenance Manual – Troubleshooting Volume
C&C08 Digital SPC Switching System Chapter 8 Alarm System
Table 8-2 lists the common fault causes that may occur to the alarm system.
Table 8-2 Common fault causes that may occur to the alarm system
The DIP switches on Rack's row & column indicators give no display or
Hardware the AMD have been wrong display. The communication between the AMD
causes incorrectly set. and the host becomes abnormal.
8-2
Maintenance Manual – Troubleshooting Volume
C&C08 Digital SPC Switching System Chapter 8 Alarm System
B RS-232
TCP/IP
Switch A Alarm box
Frames
8-3
Maintenance Manual – Troubleshooting Volume
C&C08 Digital SPC Switching System Chapter 8 Alarm System
I. Detailed description
Serial
Fault causes Remarks
No.
It causes the failure of operations on the
1 Push buttons are damaged.
control panel.
Too much alarm information
2 causes the alarm box out of Null
service.
8-4
Maintenance Manual – Troubleshooting Volume
C&C08 Digital SPC Switching System Chapter 8 Alarm System
Serial
Fault causes Remarks
No.
Serial ports have been
6 Null
damaged.
The field “Sending to alarm
The alarm box and alarm console display
7 box flag” has been set to
different information.
NO.
The field “Sending to NM
8 Null
flag” has been set to NO.
1) Check whether the DIP switches of the alarm box have been correctly set.
2) Check whether the BAM's or emergency workstation's communication gateway
is working normally.
Figure 8-1 shows the connection of the alarm box. In actual applications, an
emergency workstation may replace the BAM to lighten its load.
The alarm box is connected to the BAM through the serial port RS-232, which is
connected to the switch through TCP/IP. The switch alarm information is processed
by the BAM and then transferred to the alarm box. Only with the communication
gateway protocol in running can the BAM transmit alarm information to the alarm
box in real time.
To observe the real-time communication between the BAM and the alarm box, view
the monitoring window "BAM communication gateway" on the BAM or emergency
workstation. When the communication gets abnormal, close the gateway
communication program and restart it.
3) Check whether the alarm box and BAM/emergency workstation share the same
ground.
8-5
Maintenance Manual – Troubleshooting Volume
C&C08 Digital SPC Switching System Chapter 8 Alarm System
The alarm box and BAM/emergency workstation must share the same ground. Thus,
when the former is far away from the latter, the quality of the serial port
communication through up-low level between them can be ensured, and external
interference can be effectively defended. Check
z whether all devices are grounded.
z whether the grounding cables of the devices are connected to the same
grounding network.
4) Check whether the serial ports are faulty.
If the fault has still not been located, check whether the serial ports of the devices
are damaged.
Both the alarm box and BAM have two or more serial ports. So change the serial
port to check whether the original one is faulty.
z For the alarm box, reset the DIP switches after changing the serial port.
z For the BAM or emergency workstation, close the original conversion
connection and create a new one in the window "BAM communication
gateway" after changing the serial port.
When the alarm parameters “Sending to alarm box flag” and “Sending to NM flag”
have been set to NO, the same alarm information will not be simultaneously sent to
the alarm box and alarm console. Thus, they will display different alarm information.
Use the following way to clear the fault.
z Type the LST ALMCFG command on the maintenance console. Specify the
number of the alarm whose display is inconsistent and press <F9> to carry out
the command. The querying result will be given.
z Type the MOD ALMCFG command on the maintenance console. Specify the
number of the alarm to be modified, set the fields “Sending to alarm box flag” &
“Sending to NM flag” to YES, specify other parameters and press <F9> to carry
out the command.
VI. Suggestions
I. Detailed description
The common row & column alarm indicators faults are given below.
8-6
Maintenance Manual – Troubleshooting Volume
C&C08 Digital SPC Switching System Chapter 8 Alarm System
z There is no display. When the equipment in a rack is faulty, the rack's row &
column indicators give no indication.
z The display is wrong. When the equipment in a rack is faulty, the rack indicated
by the row & column indicators is not the actual faulty one.
Serial
Fault causes Remarks
No.
The DIP switches on the AMD have Row & column indicators give no
1
been incorrectly set. indication or give wrong indication.
8-7
Maintenance Manual – Troubleshooting Volume
C&C08 Digital SPC Switching System Chapter 8 Alarm System
3) Check whether the DIP switches on the AMD have been correctly set.
4) Check whether the ALM and emergency serial port line are faulty.
As shown in Figure 8-2, the AMD receives alarm signals and drives the rack's row &
column alarm indicators through two ways.
z Fan & power alarm signals are directly sent to the AMD.
z Other alarm signals are sent to the AMD through the ALM and emergency
serial port lines.
Therefore, when fan & power alarms can be normally reported but other alarms
cannot, check the ALM and emergency serial port lines. Change the ALM and
examine the emergency serial port lines by a multi-meter.
5) Check whether the AMD is faulty.
If the fault has not been located yet through the above measures, change the AMD
to check whether it is faulty. After the change, set the DIP switches of the new AMD.
IV. Suggestions
To ensure a rack's row & column alarm indicators work normally, the frame position
data, AMD parameter configuration and AMD DIP switches setting must be correct.
Therefore, do not modify these data at random in case of any abnormal display.
I. Detailed description
Serial
Fault causes Remarks
No.
The field “Sending to BAM The system sends no related alarm
1
flag” has been set to NO. information to the alarm console.
8-8
Maintenance Manual – Troubleshooting Volume
C&C08 Digital SPC Switching System Chapter 8 Alarm System
Wrong data configuration is a primary reason that causes alarm console fault. Take
the following methods to clear the fault.
z Type the LST ALMCFG command on the maintenance console. Type the
number of the related alarm and press <F9> to carry out the command.
z Type the MOD ALMCFG command on the maintenance console. Specify the
number of the alarm to be modified, set the fields “Sending to BAM flag” &
“Sending to NM flag” to YES, specify other parameters and press <F9> to carry
out the command.
IV. Suggestions
8-9
Maintenance Manual – Troubleshooting Volume
C&C08 Digital SPC Switching System Chapter 9 Centrex Console
9.1 Overview
The Centrex console is a computer in nature. In it the Centrex Console Plug-in Card
(CTX) is inserted. It is connected to the digital port of the DSL in the switch through
twisted pairs with the adoption of the 2B+D technique. Through the console terminal
software the Centrex console exchanges information with the switch so as to fulfill
specific functions.
Besides the basic attendant function, the Centrex console fulfills such management
functions as subscriber data setting, bill management, traffic statistics and
subscriber line test.
Table 9-1 lists the common faults that may occur to the Centrex console.
Table 9-1 Common faults that may occur to the Centrex console
The logon is abnormal. The console cannot be connected to the host (switch).
The call function is
The ring cannot work, or the call cannot be received.
abnormal.
The incoming call cannot be held or forwarded;
functions such as monitoring, insertion or forced
Centrex The basic attendant
disconnection cannot be fulfilled; the wake-up function
console function is abnormal.
cannot be set or cannot be set continuously; the night
service function is abnormal.
9-1
Maintenance Manual – Troubleshooting Volume
C&C08 Digital SPC Switching System Chapter 9 Centrex Console
Table 9-2 lists the common fault causes that may occur to the Centrex console.
Table 9-2 Common fault causes that may occur to the Centrex console
There is external
electromagnetic
interference.
The console is not reliably
grounded.
The sound blaster function
The external sound box cannot ring upon an
in the file "centrex.ini" has
incoming call.
not been started.
9-2
Maintenance Manual – Troubleshooting Volume
C&C08 Digital SPC Switching System Chapter 9 Centrex Console
The Centrex console is a common computer. In it the CTX is inserted. It adopts the
2B+D technique and is connected to the switch through the U interface of the ISDN
so as to fulfill the remote access of the console. By using this channel the Centrex
console establishes the message channel between the console terminal software
and the switch software, and fulfills such functions as attendant transfer, subscriber
data setting and bill management.
The hardware configuration of the Centrex console comprises one CTX, one
earphone, one Personal Computer (PC) (Pentium 166 or above, with the memory of
at least 16 MB). Its software configuration includes Windows 95 or Windows 98 and
specialized console software.
9-3
Maintenance Manual – Troubleshooting Volume
C&C08 Digital SPC Switching System Chapter 9 Centrex Console
Figure 9-1 shows the connection between the Centrex console and the switch. The
DSL is in an ordinary subscriber slot of the switch, while the CTX is in the Industry
Standard Architecture (ISA) slot (C802CTX) or PCI slot (C803CTX) of the PC. The
DSL is connected with the CTX through ordinary telephone twisted pairs.
2B+D
DSL CTX
Centrexconsole
C&C08
Figure 9-1 Connection between the Centrex console and the switch
9.2.2 CTX
I. C802CTX
On the panel of the C802CTX, there are three jacks XP1, XP2 and XP3 as well as
one indicator, as shown in Figure 9-2. Their meanings are:
z XP1: It is the subscriber line jack.
z XP2: It is the console earphone jack.
z XP3: It is the console earphone jack of another B channel and is not used at
present.
z Indicator: It indicates circuit status. When the circuit is activated, the indicator
flashes quickly; when the circuit is not activated, the indicator flashes once
every second.
Indicator
XP3
XP2
XP1
9-4
Maintenance Manual – Troubleshooting Volume
C&C08 Digital SPC Switching System Chapter 9 Centrex Console
Note:
z On the C802CTX there are three jumper switches XS1, XS2 and XS3. They are
used to set the mailbox addresses. Generally the three switches must be set to
"OFF".
z The field "C803CTX or not" in the file "centrex.ini" in the directory C:\Windows
should be set to "0".
II. C803CTX
On the panel of the C803CTX, there are three jacks and one indicator, as shown in
Figure 9-3. Their meanings are as follows:
z EARPHONE: It indicates the earphone jack.
z RECEIVER: It indicates the telephone receiver jack.
z LINE: It indicates the telephone line jack.
z RUN: It indicates the running indicator. When the indicator flashes slowly (ON
for one second and OFF for one second), it indicates that the running of the
board is normal, but the U interface is not activated. If the indicator flashes
quickly (ON for 1/4 second and OFF for 1/4 second), it means that the running
of the board is normal and the U interface is activated.
RUN
EARPHONE
RECEIVER
LINE
9-5
Maintenance Manual – Troubleshooting Volume
C&C08 Digital SPC Switching System Chapter 9 Centrex Console
Note:
z On the C803CTX there are three jumper switches XS1, XS2 and XS3. They are
used to set the mailbox addresses. Generally the three switches must be set to
OFF, or should jump to PIN2 and PIN3.
z The field "C803CTX or not" in the file "centrex.ini" in the directory C:\Windows
should be set to "1".
I. Detailed description
The abnormal communication between the console and the switch is mainly shown
as the deactivation of the U interface. For example:
z Fault alarm for the U interface that corresponds to the DSL of the switch occurs,
and the indicator of the U interface is OFF. fault
z The console is faulty. For example, in the console status bar, there is such
information as "The communication layer is not in the multi-frame established
status", "The U interface is not in the activated status", "Bit error occurs on the
line", "Bit error occurs at the local end", "Bit error occurs in the remote end".
z During its application the console pops up the dialog box to prompt such
information as "The console is connecting with the host".
z The status of the CTX indicator is abnormal (the indicator flashes slowly or is
OFF).
Seria
Fault causes Remarks
l No.
1 The DSL is faulty. It mainly refers to physical impairment, for
example, the impairment of the port because
2 The CTX is faulty. of external factors such as lightning stroke
and over-voltage.
The line is faulty (for Short circuit and open circuit may make the
example, short circuit, communication impossible.
3 open circuit, leakage, Leakage and inter-wire insulation deterioration
inter-wire insulation may make the communication unstable
deterioration). (sometimes activated sometimes deactivated).
9-6
Maintenance Manual – Troubleshooting Volume
C&C08 Digital SPC Switching System Chapter 9 Centrex Console
Seria
Fault causes Remarks
l No.
The loop resistance is too
high (for example, the line
4
is too long or the line
width is too small.) It may make the communication unstable.
There is external
5 electromagnetic
interference.
The console is not It may make the communication unstable or
6
reliably grounded. impossible.
Besides, simple methods can be used for auxiliary judgements. For example, test
"Network Terminal 1 (NT1) + digital telephone" or "Terminal Adapter (TA) + analog
telephone" at the console. If the telephone works normally, it indicates that the
subscriber line is normal.
2) Check whether the loop resistance of the subscriber line is too high.
The major fault that occurs when the loop resistance of the subscriber line is too
high is the unstable communication between the console and the switch. Generally
it is recommended that the loop resistance be lower than 1,100 ohm, that is, the Rab
in the above test results should be 300 ohm < Rab < 1,100 ohm.
When the external line is too long, the communication between the console and the
switch will be abnormal. Use ordinary copper-core twisted pairs as an example. The
advisable cable length is:
9-7
Maintenance Manual – Troubleshooting Volume
C&C08 Digital SPC Switching System Chapter 9 Centrex Console
If not, ground the shell of the computer or the earth wire in the attaching plug. The
smaller the grounding resistance is, the better. It is recommended that the grounding
resistance be smaller than 10 ohm.
4) Check whether the DSL is faulty.
If the fault still cannot be located, check whether the DSL is faulty.
Method: Replace the DSL that may be faulty with a standby board, then carry out
comparative analysis.
5) Check whether the CTX is faulty.
Replace the CTX of the console. Pay attention to the type of the CTX, the setting of
the DIP switch on the card as well as the setting of the file "centrex.ini" in the
Windows directory of the computer. For the detailed information, refer to 9.2.2
CTX.
6) Check whether there is electromagnetic interference source near the
subscriber eternal line.
The console is connected to the switch through the adoption of the 2B+D technique,
and it is digital signals that are transmitted on the line. Therefore, the subscriber line
connecting the console with the switch is relatively sensitive to external
electromagnetic interference, which generally will cause bit error on the line and
make the communication unstable.
If the console often prompts bit error information, check whether near the line there
is powerful electromagnetic interference source, such as large power wireless
device or UPS, besides checking whether the subscriber line is normal.
IV. Suggestions
Enhance the maintenance of the line, test the subscriber line at regular time
intervals and ensure that the console computer is reliably grounded.
9-8
Maintenance Manual – Troubleshooting Volume
C&C08 Digital SPC Switching System Chapter 9 Centrex Console
I. Detailed description
After the Centrex console starts, the logon dialog box appears. Type the password
to log on. Five minutes later, the message "The system timed out and had no
response" pops up in the upper right corner of the computer.
Seria
Fault causes Remarks
l No.
The communication between the console and the
The U interface is
1 switch is abnormal and resultantly operators
deactivated.
cannot log on to the console.
The DSL is In actual application, such case may occur that the
2
abnormal. console cannot communicate with the switch
The CTX is though the U interface is activated, that is, the
3 so-called "port suspension".
abnormal.
The data If the type of the port to which the console
4 configuration of the corresponds is non-DCN port, the console will be
switch is wrong. unable to interconnect with the switch.
Type the LST DN command on the maintenance console, type the telephone
number of the console and other parameters, and press <F9> to run the query
program. In the result that the system has returned,
z If the "device type = DID_DCN" and "subscriber type = attendant", it indicates
that the data configuration is correct.
z If the result is different, modify the data configuration of the console in the
database.
3) Check whether the port of the DSL or CTX is suspended.
9-9
Maintenance Manual – Troubleshooting Volume
C&C08 Digital SPC Switching System Chapter 9 Centrex Console
"Port suspension" on the DSL or CTX is another common cause that makes the
console unable to log on to the switch. Use the following methods to locate the fault.
z On the maintenance console of the switch maintenance terminal, type the RST
BRD command to reset the DSL that is connected to the console.
z Reset the CTX on the console interface, or restart the console.
IV. Suggestions
Prepare a CTX of the same type on the console so as to replace the used CTX in
time when it gets faulty.
I. Detailed description
The abnormal call function of the console is mainly shown as abnormal call-in. For
example:
z The ring does not work. That is, when there is an incoming call on the console,
the computer speaker or the external sound box does not ring.
z The incoming call cannot be received. That is, when there is an incoming call
on the console, the operator cannot answer it by pressing the hotkey.
Serial
Fault causes Remarks
No.
It mainly indicates that the console does not
The console software
support the sound blaster. As a result, the
1 version does not support
external sound box cannot ring upon an
the function.
incoming call.
9-10
Maintenance Manual – Troubleshooting Volume
C&C08 Digital SPC Switching System Chapter 9 Centrex Console
Serial
Fault causes Remarks
No.
The console window has
6
not been activated.
The "answer" hotkey of the
console has not been set,
7
or the setting has been The "answer" hotkey cannot work and the
modified. resultantly the call cannot be received.
III. Locating the fault that the ring does not work
Therefore, if the computer speaker or the sound box is expected to ring, the left
button should be selected, that is, be set to "√".
3) Check whether the sound blaster and the sound box are normal.
Check the parts of the sound box such as the power switch, volume knob and cable
to ensure that the sound box is normal. Then use Windows software to test the
sound blaster and sound box, for example, play CD or audio files.
9-11
Maintenance Manual – Troubleshooting Volume
C&C08 Digital SPC Switching System Chapter 9 Centrex Console
IV. Locating the fault that the incoming call cannot be received
The fault means that when there is an incoming call on the console, the operator
cannot answer it by pressing the hotkey. Use the following methods to locate the
fault.
1) Check whether the console window is activated.
Only when the console window is in the activated status, can the "answer" hotkey be
used to answer the hotkey.
If the console window has not been activated, the border line at the outmost side of
the console is gray. In this case, the user can click to activate the window.
2) Check the setting of the "answer" hotkey of the console.
Two cases may occur:
z The hotkey has not been set. In this case, the menu or tool bar to which the
hotkey corresponds is gray. In this status the operator cannot or has no
authority to perform the operation
z The setting of the hotkey is modified. As a result, the operator cannot perform
the operation by pressing the normal hotkey.
The method to query or modify the setting of the hotkey is as follows:
In this case, exit or uninstall the non-console software so as to ensure the stable
operation of the console.
9-12
Maintenance Manual – Troubleshooting Volume
C&C08 Digital SPC Switching System Chapter 9 Centrex Console
V. Suggestions
It is recommended to use the default hotkey setting. If the setting of the hotkey need
be modified, keep records and hand over them in time.
I. Detailed description
The fault that the basic attendant function of the console is abnormal is primarily
presented in the following aspects:
z The incoming call cannot be held or forwarded.
z Such functions as monitoring, insertion and forced disconnection cannot be
fulfilled.
z The wake-up function cannot be set or cannot be set continuously.
z The night service function is abnormal, and the incoming call cannot be
forwarded to the specified telephone.
Serial
Fault causes Remarks
No.
The authorities such as
insertion, monitoring and
1 forced disconnection have
not been enabled in the file The console will be unable to fulfill such
"centrex.ini". functions as insertion, monitoring and
forced disconnection.
The category of the called
2 party is not "ordinary"
subscriber.
9-13
Maintenance Manual – Troubleshooting Volume
C&C08 Digital SPC Switching System Chapter 9 Centrex Console
Serial
Fault causes Remarks
No.
The setting of the night
7 service number of the
console is incorrect.
III. Locating the fault that the incoming call cannot be held or forwarded
IV. Locating the fault that such functions as monitoring, insertion and
forced disconnection cannot be fulfilled
1) Check whether the authorities for these functions of the console are enabled.
9-14
Maintenance Manual – Troubleshooting Volume
C&C08 Digital SPC Switching System Chapter 9 Centrex Console
Check whether in the console configuration file "centrex.ini" the authorities for such
functions as monitoring, insertion and forced disconnection are enabled. The format
is:
Allow monitoring = 0
Allow insertion = 1
In the above setting, if the value is set to 0, it indicates that the function is prohibited;
if the value is set to 1, it indicates that the function is allowed. Therefore, the above
parameter values can be set to 1 according to the actual situation. Then restart the
console.
2) Check the attributes of the relevant subscribers.
The subscriber category of the console is "attendant". Generally, the console can
only monitor, intrude or forcedly disconnect intra-group subscribers of the "ordinary"
category. If these operations cannot be performed to some subscribers, use the LST
ST command to view the category of these subscribers.
V. Locating the fault that the wake-up function cannot be set or cannot be
set continuously
Check the setting of the authority of the service-enjoying subscriber. Only when the
service-enjoying subscribers meet two conditions, can the console set the wake-up
function for them. The conditions are:
z The supplementary service authority for the "Alarm Service (ALS)" is valid.
z The console's control of the supplementary service ALS is valid.
The method to query the subscribe attributes is as follows:
On the maintenance console, type the LST ST command and the telephone number
to be queried. Set the parameter "display console authority control" to "yes", type
other parameters, and press <F9> to carry out the command.
If the subscriber does not meet the above two conditions, use the MOD ST
command to modify them.
1) Check the setting of the internal parameters of the switch.
z In some standards, the "do-not-disturb" service and "wake-up" service are two
supplementary services that conflict with each other. They cannot be used at
the same time. Therefore, if the console first sets the "do-no-disturb" service for
the telephone, then sets the "wake-up service", the system will prompt that
supplementary services conflict with each other. As a result, the wake-up
service cannot be set.
z The method to query the configured value of the parameter is as follows:
9-15
Maintenance Manual – Troubleshooting Volume
C&C08 Digital SPC Switching System Chapter 9 Centrex Console
On the maintenance console, type the LST SFP command, set the "parameter" to
"P51 (Call internal parameter 3)", type other parameters, and press <F9> to carry
out the command.
z If it is confirmed that "do-not-disturb" service and "wake-up" service need be
set at the same time, modify Bit 8 of Call internal parameter 3 to 0. The method
is as follows:
On the maintenance console, type the MOD SFP command, set the "parameter" to
"P51 (Call internal parameter 3)", and type "FEFF" for the "value". Then type other
parameters and press <F9> to carry out the command.
Note:
z The meaning of Bit 8 of Call internal parameter 3: the value 1 indicates that the
supplementary services conflict with each other; 0 indicates that they do not
conflict. The default value of the switch is "1".
z The rule for defining the bits is from lower bits to higher bits, that is, from right to
left; the corresponding bits are Bit 0 to Bit 15.
When the number of waken subscribers in a module exceeds the above restriction,
the console is unable to set the wake-up function continuously.
z The method to query the configured values of the parameters are as follows:
On the maintenance console, type the LST MDU command and the module number
to be queried. Set the parameter "display module parameters" to "yes", type other
parameters, and press <F9> to carry out the command.
z To increase the number of subscribers that are allowed to set the wake-up
functions at the same time, modify the two parameters "maximum number of
wake-ups" and "maximum number of waken subscribers". The method is as
follows:
On the maintenance console, type the MOD SMP command. Type the module
number to be modified, and set "parameter" to "P9 (maximum number of waken
subscribers)". Type other parameters and press <F9> to carry out the command.
9-16
Maintenance Manual – Troubleshooting Volume
C&C08 Digital SPC Switching System Chapter 9 Centrex Console
Note:
Do not modify the module parameters of the switch arbitrarily except that there is a
special requirement, because the modification will affect the call processing
performance of the switch.
VI. Locating the fault that the night service function is abnormal
Dial the telephone number of the console. If the console rings, answers the call and
forwards it normally, it indicates that the communication between the console and
the switch is normal. Otherwise, refer to the procedures in 9.3.1 Abnormal
Console-Switch Communication for processing.
3) Check the data configuration of the PBX subscriber group in the switch.
In order to fulfill the traffic sharing among multiple consoles, configure the consoles
of the same Centrex group in the same PBX group to fulfill cyclic line hunting. Only
when call consoles get offline, can the night service forwarding be fulfilled.
The subscribers in the PBX subscriber group can only include the subscriber
numbers of the consoles that need fulfill traffic sharing, but cannot include other
subscribers, such as hotel interface message processor. Otherwise, after all
consoles are closed, the incoming calls will be routed to these subscribers, and
consequently the night service function will become abnormal.
The procedures to view the data configuration of the PBX subscribers are as
follows:
z Carry out the LST CXCON command to obtain the "PBX indicating number" of
the corresponding console.
z Carry out the LST PBX command to query PBX subscribers, and type the
above PBX indicating number to query the relevant subscriber configuration.
If there are non-console subscribers in the PBX subscriber group, remove them, or
use another PBX subscribe group instead.
9-17
Maintenance Manual – Troubleshooting Volume
C&C08 Digital SPC Switching System Chapter 9 Centrex Console
VII. Suggestions
z Maintain the console configuration file "centrex.ini" in a good status, and set its
attribute to read-only, so as to ensure that its content will not be modified
arbitrarily.
z Strengthen the management of the switch database, back up the data
frequently and keep records of the operations, so as to avoid the unexpected
modification that makes it unable to restore the data.
I. Detailed description
The fault that the data management function of the console is abnormal is mainly
presented in the following aspects:
z The call-in and call-out authorities of the subscriber cannot be set.
z The supplementary service authority of the subscriber cannot be set.
z The charging mode of the subscriber cannot be set.
z The charging status (normal or owing charge) of the subscriber cannot be
modified.
z The long number and short number table of the Centrex group cannot be
maintained.
Serial
Fault causes Remarks
No.
The communication
between the console The maintenance information of the console
1
and the switch is cannot be correctly transmitted to the switch.
abnormal.
The console authority in The authorities include the console call-in
2 the subscriber data has authority, call-out authority and supplementary
not been enabled. service authority.
If the DataMan or Exchange process in the
BAM server process is suspended, the BAM
The BAM service
3 will be unable to receive the logon message
process is abnormal.
from the console. As a result, the console is
unable to modify the subscriber data.
9-18
Maintenance Manual – Troubleshooting Volume
C&C08 Digital SPC Switching System Chapter 9 Centrex Console
1) Check whether the communication between the console and the switch is
normal.
Dial the telephone number of the console. If the console can ring, answer the call
and forward it normally, it indicates that the communication between the console and
the switch is normal. Otherwise, refer to the procedures in 9.3.1 Abnormal
Console-Switch Communication for processing.
2) Check whether the relevant console authority in the subscriber data has been
enabled.
The ability of the console to perform data maintenance for the subscribers in the
group depends on whether the relevant service authorities of the subscriber are
allowed to be under the control of the console. These authorities include console
call-in authority, console call-out authority and console supplementary service
authority.
z The method to query the console authority in the subscriber configuration is as
follows:
On the maintenance console, type the LST ST command and the subscriber
number to be queried. Set the parameter "Display console authority control" to "yes",
type other relevant parameters, and press <F9> to carry out the command.
z The method to modify the console authority in the subscriber configuration is as
follows:
On the maintenance console, type the MOD ST command and the subscriber
number to be modified. Select the corresponding console authority, type other
parameters, and press <F9> to carry out the command.
3) Check whether the BAM service process is running normally.
Check whether the DataMan or Exchange process in the BAM service process is
closed or suspended, and so on. If the running is abnormal, restart the BAM service
process with reference to the BAM operating instruction, or restart the BAM server.
Take care to back up the bills and system data, and so on, during the operation.
4) Check whether the module data configuration is wrong.
If in the module data the parameter "BAM installed" is set to "yes" while in fact it is
not, the console will be unable to query the BAM and consequently unable to log on
to the host to operate the maintenance data.
5) Query the BAM configuration information of the module.
On the maintenance console, type the LST MDU command and the module number
to be queried. Set the parameter "Display other parameters" to "yes", specify other
relevant parameters, and press <F9> to query the information.
9-19
Maintenance Manual – Troubleshooting Volume
C&C08 Digital SPC Switching System Chapter 9 Centrex Console
z If a module such as RSM is configured with wrong BAM data, use the following
method to modify the configuration.
On the maintenance console, type the MOD SM2 command and the corresponding
module number. Set the parameter "BAM installed" to "yes", specify other relevant
parameters, and press <F9> to carry out the command.
IV. Suggestions
During the data configuration, use the default parameters of the switch as possible
as it can be. Do not modify the data arbitrarily. Otherwise, unexpected results may
occur.
I. Detailed description
The fault that the bill management function of the console is abnormal is mainly
presented in the following aspects:
z The bill fetching is abnormal. For example, the console cannot fetch bills from
the system or fails to fetch some bills.
z The intra-group subscriber charging is abnormal, that is, the intra-group calls
are charged.
z The immediate bills cannot be printed.
Serial
Fault causes Remarks
No.
For example, the BER is too high, or the
The communication
communication is interrupted. As a result,
1 between the console and
the time for fetching bills is often too long or
the switch is abnormal.
the console cannot fetch bills.
9-20
Maintenance Manual – Troubleshooting Volume
C&C08 Digital SPC Switching System Chapter 9 Centrex Console
Serial
Fault causes Remarks
No.
When there are several consoles, only one
Several consoles have
5 can have the authority to fetch bills.
the authority to fetch bills.
Otherwise, the bill fetching will be confused.
1) Check whether the console is unlocked or the user name for the logon has the
authority.
If the console prompts that "You have no authority" during the bill fetching, check
whether the console is unlocked, or the user name for the logon has the authority to
fetch bills. If not, use appropriate user name to log on to the console again.
2) Check whether the communication between the console and the switch is
normal.
Dial the telephone number of the console. If the console can ring, answer the call
and forward it normally, it indicates that the communication between the console and
the switch is normal. Otherwise, refer to the procedures in 9.3.1 Abnormal
Console-Switch Communication for processing.
3) Check whether the setting of the console parameters is correct.
If the option "Fetch Ticket Automatically" has not been selected, the console will not
fetch bills at regular time intervals.
9-21
Maintenance Manual – Troubleshooting Volume
C&C08 Digital SPC Switching System Chapter 9 Centrex Console
To solve the problem, select the option and set the time interval to 10 minutes
(suggested value).
4) Check whether the Centrex data configuration is correct.
z Query the setting of the field "send ticket to console" in the data of the Centrex
group to which the console belongs.
On the maintenance console, type the LST CXGRP command and the
corresponding Centrex group number. Specify other relevant parameters and press
<F9> to carry out the command. Generally, the field "send ticket to console" should
be set to "detailed ticket and meter table".
z The method to modify the setting of the field "send ticket to console" in the
Centrex group data is as follows.
On the maintenance console, type the MOD CXGRP command and the
corresponding Centrex group number. Set the field "send ticket to console" to
desired option, specify other relevant parameters, and press <F9> to carry out the
command.
5) Check whether the configuration of the Centrex subscriber charging data is
correct.
In normal status, the charging category of the Centrex subscribers whose bills are
sent to the bill console should be "immediate subscriber table". To query the
configuration, carry out the LST ST command; to modify it, carry out the MOD ST
command. The details are not introduced here.
6) Check whether other consoles or hotel interface messages have the authority
to fetch bills.
In order to ensure the uniqueness and completeness of the bills, when several
consoles are in the same Centrex group, generally only one should be set to have
the authority to fetch bills, while other consoles should not. Otherwise, confusion will
occur when the authorized console fetches bills.
To check it, refer to Step 3) and view the setting interfaces of the consoles. Make
sure that only one console has been set to fetch bills at regular intervals.
7) Check whether the bill pointer file of the BAM is normal.
When the BAM software is reinstalled, or the system is infected with a virus, it is
possible that the bill pointer file "pool.csn" in D:\bill\Centrex\ on the BAM hard disk is
impaired, which makes the console's bill fetching time out.
In this case, delete the file and fetch bills again on the console. The BAM will
automatically generate a new bill pointer file "pool.csn".
8) Contact technical support engineers.
If the fault still cannot be located, or you are not confident of your judgements,
contact technical support engineers in time.
9-22
Maintenance Manual – Troubleshooting Volume
C&C08 Digital SPC Switching System Chapter 9 Centrex Console
IV. Locating the fault that the intra-group subscriber charging is abnormal
The fault that the intra-group subscriber charging is abnormal is caused by the
inappropriate setting of the charging data of the console.
In the charging formula, when "tariff" is 0, it indicates that the tariff table must be
queried and the tariff should be determined according to the actual prefix in the
table.
Therefore, if the charging is not to be performed, in the charging formula, both "start
times" and "normal times" should be set to 0, or the "discount" should be set to 0.
On the maintenance console, type the LST ST command and the subscriber
number to be queried. Set the parameter "display charging attributes" to "yes",
specify other parameters, and press <F9> to carry out the command.
If the charging category of the subscriber is not "immediately sending to printer", use
the MOD ST command to modify it.
3) Check whether the file "Mbox.dll" exists.
Sometimes, the above setting is correct, and immediate bills can be seen on the
immediate bill page on the console, but they cannot be printed. In this case, check
whether the window "immediate charging operation record" exists when there are
immediate bills. If not, check whether the file "Mbox.dll" exists in the Centrex
directory or Windows directory. If the file does not exist, it indicates that it has been
deleted by mistake, and the console should be reinstalled.
4) Check whether the printer is faulty.
If no error is found in the above check, check whether the printer can print normally.
9-23
Maintenance Manual – Troubleshooting Volume
C&C08 Digital SPC Switching System Chapter 9 Centrex Console
VI. Suggestions
9-24
Maintenance Manual – Troubleshooting Volume
C&C08 Digital SPC Switching System Chapter 10 Intelligent Network Service
10.1 Overview
In the intelligent network hierarchy, C&C08 Digital SPC Switching System serves as
the Service Switching Point (SSP) and mainly fulfills the service switching function.
This chapter mainly deals with the locating and eliminating of the faults related to the
SSP in the intelligent network. As for the concepts and knowledge such as Service
Control Point (SCP), Signaling Transfer Point (STP) and Service Management Point
(SMP), refer to relevant specialized manuals.
Besides, Except for the case that special explanation is presented, in this chapter the
problems about the SSP are also applicable to the Source Service Access Point
(SSAP) networking.
Table 10-1 lists the common faults that may occur in the intelligent network.
Table 10-1 Common faults that may occur to the intelligent network
When the balance is When the balance of the subscriber's card is inadequate,
Abnormal
inadequate, the the SSP cannot play the prompt tone that the balance is
service
prompt tone sent is inadequate. Instead, it sends to the subscriber busy tone,
abnormal. no tone or the tone prompting no authority to make a call.
The number
The SSP does not receive a number, or "automatically"
receiving is
receives a number.
abnormal.
Continuous call
When the called party is busy or the call ends, the
cannot be
subscriber cannot dial the number continuously.
performed.
10-1
Maintenance Manual – Troubleshooting Volume
C&C08 Digital SPC Switching System Chapter 10 Intelligent Network Service
Table 10-2 lists the common fault causes that may occur in the intelligent network.
Table 10-2 Common fault causes that may occur to the intelligent network
10-2
Maintenance Manual – Troubleshooting Volume
C&C08 Digital SPC Switching System Chapter 10 Intelligent Network Service
The CICs of the inter-office signaling do The SSP does not receive the
not match. number.
10-3
Maintenance Manual – Troubleshooting Volume
C&C08 Digital SPC Switching System Chapter 10 Intelligent Network Service
Because of the peculiarity of the intelligent network, observe the following principles
during the locating of the faults related to the SSP.
I. Judging whether the fault is at the switch side, or on the intelligent service
platform
The TCAP signaling records the complete information of the interaction between the
SSP and SCP. It is a powerful tool for the analysis of the faults in the intelligent
network. Therefore, during the locating of the fault, first trace the TCAP messages to
judge whether the fault is at the switch side or on the intelligent service platform.
The SSP is generally in the tandem office. Its incoming and outgoing trunks may
adopt such signaling systems as TUP, ISUP and Channel Associated Signaling.
When the intelligent call is abnormal, trace the corresponding inter-office signals to
find out whether the cause of the fault is in the SSP or other offices.
If the SSP is in the end office, while the subscriber dialing the intelligent service is in
the local office, perform dynamic connection tracing to analyze whether the
connection process is normal.
If it is found that the fault is in the SSP, first check the SSP data configuration with a
definite purpose. Only perform it to the data that may be related to the fault. Before
the check, has a good knowledge of the function of each data item, the relation
between data and the functions of the key parameters.
If the fault is related to the hardware, check whether it is the faulty hardware that
causes the fault. For this purpose, perform such operations as isolating, switching
over, resetting and replacing the boards.
A standard IN usually comprises such parts as SSP, SCP, STP, Intelligent Peripheral
(IP), Service Management System (SMS) and Service Creation Environment (SCE),
as shown in Figure 10-1.
Huawei Technologies Proprietary
10-4
Maintenance Manual – Troubleshooting Volume
C&C08 Digital SPC Switching System Chapter 10 Intelligent Network Service
SCE
SMS Database
SCP
No.7
No.7
IP STP
No.7 No.7
SSP
Switch PABX
User terminal
I. SSP
The SSP connects the PSTN and ISDN with the IN. It detects intelligent service
requests and communicates with the SCP; responds to the SCP requests and allows
the service logic in the SCP to control call processing.
II. SCP
The SCP, which is the core unit of the IN, saves user data and service logic. It
engages in receiving the query information sent from the SSP, querying database and
coding. In the meantime, it starts different service logics, based on the call events
reported by the SSP and sends call control instructions according to the service logic
to the corresponding SSP to guide its next action. Thus it realizes intelligent calls of
various kinds. All the service control functions available within an IN are centralized in
the SCP, while the SCP and the SSP communicate according to the standard IN
interface protocol.
III. STP
The STP is actually a component of the signaling system No. 7 network, which
transfers signaling messages from one signaling link to another. The STP in an IN
bridges the signal communication between the SSP and SCP by transferring No. 7
signaling.
10-5
Maintenance Manual – Troubleshooting Volume
C&C08 Digital SPC Switching System Chapter 10 Intelligent Network Service
IV. IP
V. SMS
The SMS consists of the SMP and its client Service Management Access Point
(SMAP). The SMAP is the operating interface of the SMP. The SMP engages in the
management of service lifecycle, such as storing service data, loading service,
activating service, providing the interface to type user service data. For example, data
such as "free number" and "query password" should be filled in for the 800 service. It
also has Network Management functions (security, performance, configuration and
account management), providing the IN with service-related network management. In
addition, the SMP has to provide the billing center with the interface for transmitting
bills reported by various SSPs through the SCP. All the bills are sorted at the billing
center, distributing the expenses among various operators.
VI. SCE
The SCE is used to generate the data and logic of a Value-Added Service (VAS),
using an editing generator and a simulation test environment. The editing generator is
a graphic editor, which draws the flow chart and defines service related contents,
such as database and voice, before generating them into files, which are to be
downloaded into the simulation environment, for simulating tests. The files will be
loaded into true running environment, if tested to be error-free. The node is relatively
independent and is usually not connected with other equipment, while it is connected
only with the SMP during service extension (when service files are sent to the SMP).
10-6
Maintenance Manual – Troubleshooting Volume
C&C08 Digital SPC Switching System Chapter 10 Intelligent Network Service
LS TM SSP SCP TM LS
IAI
Initial DP
Request report BCSM event
Connect to resource
ACM
P&C (Language select)
ANN
Collected user information
Connect
IAM
ACM
ANC
CLF
Event Report BCSM
(caller hookon)
Figure 10-2 Signaling flow for dialing the 300 service through the TUP
I. Call-in stage
For the intelligent service that needs secondary number receiving, the call-in stage
refers to the stage after the SSP has received the intelligent prefix and before the
SCP has sent the Connect to Resource (CTR). In the signaling flow chart of the 300
service as shown in Figure 10-1, the call-in stage refers to the period after the SSP
has received the Initial Address Message with Additional Information (IAI) and before
the SCP has sent the CTR.
For the intelligent service that only needs one-stage dialing, as there is no intelligent
interaction stage, the call-in stage refers to the period after the SSP has received the
intelligent prefixes and before the SPC has sent the Applying Charging (AC).
10-7
Maintenance Manual – Troubleshooting Volume
C&C08 Digital SPC Switching System Chapter 10 Intelligent Network Service
The interaction stage refers to the stage when the user interacts with the intelligent
peripherals. This stage is after the SCP has sent the CTR and before the SCP has
sent the Disconnect Forward Connection (DFC). In the stage, the SCP sends one
PA/PC operation to indicate the user to play the tone and receive the number.
The connection stage refers to the stage after the SCP has sent the AC and Connect
and before the called party replies. In the stage, the SSP analyzes the number,
selects a route and connects the call to the destination number.
The conversation stage refers to the stage after the called party replies and before
one party of the call hooks on. In this stage, the SSP monitors the call. It prompts the
subscriber before the balance is used up and ends the call after the balance is used
up.
V. Release stage
The release stage refers to the period after one part of the call hooks on until the SCP
sends Release Call. In this stage, the charging information will be reported. Besides,
the release cause value of the operation Release Call determines the signaling that
the SSP sends to the originating office.
I. Detailed description
The incapacity for triggering the intelligent service indicates that after dialing the
access code, the subscriber hears nothing, neither busy tone nor empty number tone,
and consequently the intelligent call cannot continue.
The following text will deal with the fault locating process in the case that "the SSP
does not report the IDP message".
10-8
Maintenance Manual – Troubleshooting Volume
C&C08 Digital SPC Switching System Chapter 10 Intelligent Network Service
Serial
Fault causes Remarks
No.
The service category
configuration of the Take care to differentiate "intelligent service"
1
intelligent service from "special access code".
prefix is wrong.
The number change is For example, the setting for changing number,
2
wrong. deleting number and inserting number is wrong.
The abnormal process for triggering an intelligent service should at least undergo the
procedures as "number analysis→service key analysis→SCP addressing→INAP
message coding→INAP message sending". As the SSP cannot find the IDP message,
it indicates that the fault is in the first three procedures.
1) Check whether the switch has received the call.
For the intelligent call originated by the incoming trunk, trace its signaling to check
whether the SSP has received the intelligent call. If not, check whether the inter-office
signaling interworking is normal.
2) Check whether the configuration of the service category of the intelligent service
prefixes is correct.
Type the LST CNACLD command to query whether the configurations of service
categories of intelligent prefixes are correct. Refer to the following table for the
common configuration methods:
10-9
Maintenance Manual – Troubleshooting Volume
C&C08 Digital SPC Switching System Chapter 10 Intelligent Network Service
modes, such as "prefix special processing", "caller number analysis", "special number
change" and "number change in the call source". According to these number change
data, the operator can analyze whether the number after the change is the correct
intelligent access code.
4) Check the service configuration data.
z Check the configuration data of the access code (LST ACCODE). Note that the
"database start position" is "0"
z Check the Trigger Detection Point (TDP) configuration (LST TDPCFG) and the
SCP configuration (LST SCPCFG).
When the switch judges that the prefix is an intelligent service prefix, it queries the
access code table to obtain the access code. Then it queries the TDP configuration
table with the access code to obtain the service key. Further, it queries the SCP
configuration table with the service key to obtain the SCP number. During the
querying of the data, check the completeness of the data according to the above
inter-table relations.
5) Check the system data configuration.
z Check the SCP address configuration (LST SCPADR). If it is SSP networking,
the SCP signaling point code is the signaling point code of the Signaling Access
Unit (SAU). If it is SSAP networking, the SCP signaling point code is the default
signaling point code of the local office.
z Check the SSP address configuration (LST SSPADR). The DPC address in the
SSP address table should be the signaling point code of the local office.
z Check the SCCP configuration (LST SCCPDPC/SCCPSSN).
IV. Suggestions
The fault is mainly caused by incorrect data configuration. Therefore, during the
operation of the SSP, it is recommended to enhance the database management to
avoid misoperation and unauthorized operation.
10.3.2 Incapacity for Triggering the Intelligent Service (with IDP Message)
I. Detailed description
The incapacity for triggering the intelligent service indicates that after dialing the
access code, the subscriber hears nothing, busy tone or empty number tone, and
consequently the intelligent call cannot continue.
The following text will deal with the fault locating process in the case that "the SSP
reports the IDP message".
When the TCAP message is traced on the maintenance console, the IDP message
can be seen, but the TCAP message including the RRBE and CTR operations cannot
10-10
Maintenance Manual – Troubleshooting Volume
C&C08 Digital SPC Switching System Chapter 10 Intelligent Network Service
be received. In this case, the SSP cannot communicate with the SCP. Through a
further analysis of the TCAP message, the above case can be further divided as
follows:
z The SSP cannot receive the response from the SCP.
Through the tracing of the TCAP message, it can be seen that the SSP sends
TC_INVOKE_REQ, TC_BEGIN_REQ and TC_U_ABORT_REQ, but the SCP does
not respond.
z The SSP receives the TC_P_ABORT.
Through the tracing of the TCAP, it can be seen that the SSP sends
TC_INVOKE_REQ and TC_BEGIN_REQ, and receives the TC_P_ABORT.
z The SSP receives the TC_NOTICE.
Through the tracing of the TCAP, it can be seen that the SSP sends
TC_INVOKE_REQ and TC_BEGIN_REQ, and receives TC_NOTICE.
z The SSP does not send TC_BEGIN_REQ.
Through the tracing of the TCAP message, it can be seen that the SSP sends the
TC_INVOKE_REQ, but does not send the TC_BEGIN_REQ.
Seri
al Fault causes Remarks
No.
For example, the configuration of the
The system data
1 SSP/SCP address and SCCP subsystem is
configuration is wrong.
wrong.
The communication
4 between the SMCP and the For example, the network gets faulty.
SSAP is interrupted.
The SMCP/SSAP dialog
That is, the SSAP dialog number is
5 number configuration is
inconsistent with the SMCP dialog number.
wrong.
III. Locating the fault that the SSP cannot receive the response from the SCP
1) Make the preliminary locating according to the influence range of the fault.
10-11
Maintenance Manual – Troubleshooting Volume
C&C08 Digital SPC Switching System Chapter 10 Intelligent Network Service
When a fault occurs, it indicates that the communication between the SSP and the
SCP is abnormal. Then process the fault according to the following principles:
z If the fault influences all subscribers, refer to Steps 4), 5) and 6).
z If only the subscribers of some modules are influenced, refer to Steps 2) and 6).
z If the fault only influences some subscribers randomly, refer to Steps 3) and 6).
The relation between the influence range of the fault and the possible cause is shown
in the following table:
Some subscribers
The SCP processor is overloaded, or the configuration of
are influenced
the dialog number is wrong.
randomly.
Besides, if several SCPs are configured for the service, check whether the fault is
caused by an abnormal SCP.
4) Judge whether the fault is an SSP fault or an SCP fault.
The case is applicable to "SSP+SAU+SCP" networking.
In the C&C08 Maintenance Tool Navigator on the maintenance console, select the
option [Intelligent/SCCP tracing]. Start the SCCP message tracing, and observe
whether the SSP has sent the TCAP message to link. Then, the following judgements
can be made:
z If the SSP has already sent the message to the link but the SCP does not
respond, it indicates that the fault is in the SCP. Invite the maintenance
personnel of the intelligent network to help locate the fault.
z If the SSP has not sent the message to the link but the connection between the
SSP and the SCP is normal, it indicates that the fault is in the SSP. In this case,
Huawei Technologies Proprietary
10-12
Maintenance Manual – Troubleshooting Volume
C&C08 Digital SPC Switching System Chapter 10 Intelligent Network Service
check the system data configuration of the SSP with reference to the methods
introduced in 10.3.1 Incapacity for Triggering the Intelligent Service (without
IDP Message).
5) Judge whether the fault is an SSAP fault or an SMCP fault.
The case is applicable to "SSAP+SMCP" networking.
The status of the communication between the SPC (MEM) and the SMCP can be
checked through the hardware configuration state panel and the diagram of the
equipment panel status. In this way, the following judgements can be made:
z If the communication between the SCP and the SMCP is normal, invite the
maintenance personnel of the intelligent network to help locate the fault.
z If the communication is abnormal, it indicates that the fault occurs in the SSAP. It
can be recovered through the switching over, resetting or replacing of the SPC or
MEM.
Note:
z For the SPC, if its panel indicator "FAIL" is OFF, it indicates that the
communication with the SMCP is normal.
z For the MEM, if its panel indicator "NET" flashes slowly, it indicates that its
communication with the SMCP is normal. If the indicator flashes quickly with
"tickling" resetting sound, it indicates that its communication with the SMCP is
abnormal.
The common errors that occur in the dialog number configuration are as follows:
z For the SM without the MEM, the MEM has not been configured (ADD
MEMCFG), or the dialog number range has not been configured (SET
MDUDLG).
z The module has not been reset after the dialog number is configured.
z The operator does not understand the relation between the SPM and the SMC,
and has configured a dialog number for each SPM.
z The dialog number at the SSAP side is inconsistent with that at the SMCP side.
10-13
Maintenance Manual – Troubleshooting Volume
C&C08 Digital SPC Switching System Chapter 10 Intelligent Network Service
O&M #1169
------------
1 0 4095
2 096 8191
3 8192 12287
4 49508 49509
10 12288 14435
(Result number = 5)
------------------
(Result number = 2)
In the above report, check the following points with special care:
z The dialog of each SM is configured with a dialog number, which corresponds to
a module configuration on the SMAP.
z Each SPM should be configured with a dialog number on the SSP, and the
dialog numbers of several SPMs that are bound to the same SMC should be
10-14
Maintenance Manual – Troubleshooting Volume
C&C08 Digital SPC Switching System Chapter 10 Intelligent Network Service
IV. Locating the fault that the SSP receives the TC_P_ABORT
This fault is similar to the fault that the SSP cannot receive the response from the
SCP. The operator should also determine the range of the fault and whether it is an
SSP fault or an SCP fault. Refer to the description in the previous section for the
concrete methods.
1) Eliminate the fault that the local end of the SSP has given up the conversation.
Huawei Technologies Proprietary
10-15
Maintenance Manual – Troubleshooting Volume
C&C08 Digital SPC Switching System Chapter 10 Intelligent Network Service
For the networking mode "SSP+SAU+SCP", if through the MTP message tracing it is
found that the message has not been sent to the link, it indicates that the
TCAP/SCCP layer at the local end has given up the conversation. This case is
generally caused by inappropriate data configurations. According to the cause of the
TC_P_ABORT, check the following data configurations:
z DPC of the SCCP signaling point (LST SCCPDPC)
z SCCP subsystem (LST SCCPSSN)
z SCP physical address (LST SCPADR)
z SSP physical address (LST SSPADR)
For the networking mode "SSAP+SMCP", check such data as the SCP physical
address, SSP physical address and dialog number.
2) Eliminate the fault that the remote end of the SSP has given up the conversation.
z For the SSP, the fault is generally caused by the SAU data configuration error, or
by the inconsistency between the SAU data and SCP data.
z For the SSAP, the fault is generally caused by the inconsistency between the
SMCP and the SSAP. If the fault is irrelevant to the SSP/SSAP, invite the
maintenance personnel to help locate it.
TC_NOTICE is used to report that the SCCP network service is unavailable. To know
the cause for the unavailability of the SCCP network service, view the cause
parameter of the dialog primitive. The common causes of the fault are as follows:
z MTP fault: It indicates that the SAU is unreachable. Check the signaling link to
the SAU.
z MTP congestion: It indicates that the MTP link is overloaded. Adjust the signaling
load of the MTP link.
z No authority: Generally it is because the data configuration is wrong. Check
whether the SCCP subsystem is configured. The command is LST SCCPSSN.
VI. Locating the fault that the SSP does not send the TC_BEGIN_REQ
The fault is mainly caused by the inconsistency between the FAM data and BAM
data.
1) Find the module that gets faulty.
Query the alarm information of the alarm subsystem to find the module that gets faulty.
Take special care to check whether switchover has occurred in these modules.
2) Reset the data configuration.
z Use the MOD SCPADR command to reset the data in the SCP physical address
description.
z Use the MOD SSPADR command to reset the data in the SSP physical address
description.
Huawei Technologies Proprietary
10-16
Maintenance Manual – Troubleshooting Volume
C&C08 Digital SPC Switching System Chapter 10 Intelligent Network Service
VII. Suggestions
The fault is mainly caused by incorrect data configuration. Therefore, during the
operation of the SSP, it is recommended to enhance the database management to
avoid misoperation and unauthorized operation.
I. Detailed description
During the service flow, the subscriber suddenly hears busy tone. Through the TCAP
message tracing, it can be seen that the SCP sends PC operation, the SSP reports
TC_U_ERROR, and the cause value is "resource unavailable".
Serial
Fault causes Remarks
No.
The resource data These data includes SSP specialized resource
1 configuration is capability, inter-module resource search and
wrong. voice code index.
For the SM, the board may be DIN or SPT.
The board gets faulty
2 For the SPM, the board concerned may be SPD
or is not activated.
or SRC.
If the resource application fails when a voice is being played, locate the fault
according to Step 3); otherwise, start locating from Step 1).
1) Check whether the resource configuration data is correct.
The basic resource configuration data of the SSP includes:
z SSP specialized resource capability
10-17
Maintenance Manual – Troubleshooting Volume
C&C08 Digital SPC Switching System Chapter 10 Intelligent Network Service
For example, "0x01B80003" stands for 300 services, its voice code is 003, and the
voice is to be played in Mandarine and English. The corresponding voice file codes
on the board are 01800003 and 01400003 respectively.
Specified indicators for individual languages are given below (xx part using the
hexadecimal system):
12 ------ Russian
14 ------ Spanish
51 ------ Arabic
58 ------ Indonesian
10-18
Maintenance Manual – Troubleshooting Volume
C&C08 Digital SPC Switching System Chapter 10 Intelligent Network Service
59------- Malaysian
5E-------Tamil
5F-------German
60------- kirghizian
61------- Azerbaijan
62--------Thailand
FA ------ Chinese
FB ------ English
IV. Suggestions
Traffic statistics tasks of the intelligent resource can help learn the utilization of the
intelligent resources. If the resource is unavailable during the traffic peak, evaluate
the necessary amount of intelligent resource according to the intelligent traffic volume
of the local office, so as to determine whether it is necessary to add intelligent
resources.
I. Detailed description
The fault of abnormal tone playing upon inadequate balance is mainly shown in the
following two aspects:
z When the balance is inadequate before the conversation, the SSP cannot send
the prompt tone that "the balance is inadequate" to the subscriber, and the
subscriber hears the busy tone immediately.
z When the balance is inadequate during the conversation, the SSP cannot play
the prompt tone at the last minute, that is, it cannot prompt the caller and called
party in the three-party service mode.
II. Locating the fault that the tone playing is abnormal before the
conversation
When the balance is inadequate, the normal SCP-SSP interaction flow is as follows:
SCP sends the CONNECT operation; the SSP finds that the balance is inadequate
and reports "TC_U_ERROR", and the cause indicator is 2; according to the cause
reported by the SSP, the SCP learns that the balance is inadequate, and then it sends
PA to let the SSP play the prompt tone that the balance is inadequate.
10-19
Maintenance Manual – Troubleshooting Volume
C&C08 Digital SPC Switching System Chapter 10 Intelligent Network Service
III. Locating the fault that the tone playing is abnormal during the
conversation
The SSP plays the prompt tone at the last minute according to the call monitoring
regulations in the AC operation. Among them, the parameter of the call monitoring
regulates such information as the time for advance alarm and the voice code of the
record announcement. As the prompt tone is played through the three-party service
mode, the conference resource need be applied for. If in the service charging
attributes of the SSP the "prompt tone time" is configured, the time for advance alarm
should be the value configured on the SSP. If on the SSP the "prompt tone time" is
not configured, or the configured value is "0", the time for advance alarm should be
the call monitoring time in the AC.
1) Check whether the contents of the AC message are correct.
Start the TCAP message tracing and view whether the call monitoring is set in the AC
message and whether the parameter of the call monitoring is correct. Then adopt the
following measures.
If the call monitoring is not set, it is normal that the subscriber does not hear the
prompt tone at the last minute. View the voice code in the call monitoring and check
whether the voice file corresponding to the voice code is loaded on the SSP. If the
voice file is not loaded, the prompt tone at the last minute cannot be played.
2) Check whether the SSP is configured with the conference resource.
z For the SM, the conference resource is on the BNET and the data configuration
need not be performed.
z For the SPM, the conference resource is on the SRC in the shared-resource
frame. The data configuration need be performed. Use the LST SRCCFG
command to query the configuration and the ADD SRCCFG command to add
the configuration.
10-20
Maintenance Manual – Troubleshooting Volume
C&C08 Digital SPC Switching System Chapter 10 Intelligent Network Service
I. Detailed description
Abnormal number receiving belongs to the faults that occur in the interaction stage.
Through the TCAP message tracing it can be seen that the fault can be divided into
two cases:
z The SSP cannot receive the number. In the interaction stage, the SCP has
already sent the PA/PC operation. Whatever number the subscriber dials,
however, the SSP does not report the number receiving result.
z The SSP "automatically" receives the number. In the interaction stage, the SCP
has sent the PA/PC operation. When the subscriber listens to the prompt tone,
he or she does not perform any operation, but the SSP prompts that the input is
wrong, or the SSP automatically selects a specific service function.
Serial
Fault causes Remarks
No.
The dial mode of the telephone is the
1
pulse mode.
III. Locating the fault that the SSP cannot receive the number
There are many causes that may make the SSP unable to receive a number. If there
is a problem in any of the procedures from the telephone to the SSP number receiver,
the SSP may be unable to receive a number. Therefore, the range of the fault should
be included in the analysis of problem.
1) Check whether the subscriber telephone adopts the pulse dialing mode.
In the two-stage number receiving, the intelligent service adopts the dual-tone
number receiving mode. If the subscriber telephone adopts the pulse dialing mode,
the SSP will be unable to receive the number.
10-21
Maintenance Manual – Troubleshooting Volume
C&C08 Digital SPC Switching System Chapter 10 Intelligent Network Service
When a subscriber complains that he or she cannot dial a number, therefore, check
whether the dial mode of the subscriber telephone is the dual-tone mode.
2) Check whether there are cross-connected wires in the incoming trunk and
whether the CICs of the inter-office signaling match.
Cross-connected wires in the transmission line and inconsistent CICs of inter-office
signaling will result in voice channel misconnection, that is, the phenomenon that the
voice channel is obstructed. Consequently, when the intelligent call is originated by
the incoming trunk, the SSP will be unable to receive the number.
Under this circumstance, check whether the above two cases occur.
3) Check whether a fault occurs in the HW cabling.
The SSP number receiver is connected to the SRC or DTR through the HW cable.
Therefore, when the HW cable is broken, in poor contact or its data configuration is
wrong, the SSP will be unable to receive a number.
The occupation of the HW time slots can be observed through the continuous dial test,
so as to check whether the fault is related to the HW cabling.
4) Check whether the SRC or DTR is faulty.
In the SM, the SSP uses the DRV (the software configuration is the DIN) of the
resource frame to receive numbers. In the SPM, the SSP uses the SRC in the shared
resource frame to receive numbers.
Test, reset or replace the boards to check whether the fault is related to the above
boards.
IV. Locating the fault that the SSP "automatically" receives the number
As the SSP receives the number through the dual-tone mode, during the PC
operation, the tone playing and the number receiving are performed at the same time.
If the voice file includes dual-tone information, the number receiver will mis-receive
the number. This is the so-called "automatic" number receiving.
1) Check whether the mis-receiving time fixedly corresponds to a specific point of a
voice announcement.
If the voice file includes dual-tone information, each time the dual-tone information is
being played, the SSP may receive number automatically. The probability of the
occurrence of the fault is related to the impedance of the telephone. If the subscriber
uses the hand-free function, or dials through the PBX, the probability will increase.
If during the dial test it is found that "automatic" number receiving occurs invariably
when a segment of a voice announcement is being played, proceed to Step 2).
2) Replace the faulty voice file.
10-22
Maintenance Manual – Troubleshooting Volume
C&C08 Digital SPC Switching System Chapter 10 Intelligent Network Service
Start the TCAP message tracing, view the code of the faulty voice or the description
of the voice files to find the voice file to which the voice announcement corresponds.
Then replace the faulty voice announcement with a new voice announcement. Load
the new voice announcement and perform the dial test again. If the fault is eliminated,
it indicates that the voice file includes dual-tone information.
For example, the voice code 0x01B80003 corresponds to the voice files 01800003
(Chinese) and 01400003 (English). If the fault occurs during the playing of the
Chinese voice, copy a voice announcement in the subdirectory D:\data\voice of the
BAM and rename it as 01800003.001. Then load the new voice announcement. After
the loading, perform the dial test again and observe whether the fault disappears.
If it is confirmed that the fault exists in the voice, record the voice file again, or
perform wave filtering for the original voice file.
V. Suggestions
The number receiving fault should be analyzed and eliminated step by step according
to the fault range.
I. Detailed description
During the process of the intelligent call, when the called party is busy, does not
respond or the call ends, the system prompts the subscriber to continue dialing (that
is, consecutive call). After several consecutive calls, the SSP disconnects and the
caller hears busy tone.
From the point of the view of the TCAP signaling, the fault belongs to abnormalties in
the connection stage. That is, it occurs after the SCP has sent the DFC. In this stage,
the SCP may have already sent such operation messages as RRBE, AC and
CONNECT.
Serial
Fault causes Remarks
No.
The SCP service does not
1
support.
After several consecutive calls the
Consecutive calls are subscriber will hear busy tone.
2 restricted by the SSP
maximum analysis times.
10-23
Maintenance Manual – Troubleshooting Volume
C&C08 Digital SPC Switching System Chapter 10 Intelligent Network Service
For example, for the Universal Card Service (UCS), the maximum times of
consecutive calls can be set on the SMAP. When the number of consecutive calls
reach the set value, the system will prompt that the maximum times of consecutive
calls is reached, then disconnects and sends busy tone to the subscriber.
IV. Suggestions
First analyze the TCAP signaling to check whether the fault is caused by the SSP or
by the SCP. For the fault caused by the SSP, analyze the call with the help of
signaling tracing.
I. Detailed description
Connection fault refers to the abnormal connection of the intelligent call during the
connection stage. The fault is mainly presented in the following four aspects:
z The caller hears busy tone after dialing the called number.
z The caller hears nothing after dialing the called number.
z The caller hears the tone prompting "no authority to call" or the alike prompt tone
after dialing the called number.
z The call is disconnected after the called telephone rings for 18 seconds, that is,
the called telephone only rings for three to four times.
Through the TCAP message, it can be seen that all the above faults occur after the
SCP has sent the DFC. In this stage, the SCP may have already sent such operation
messages as RRBE, AC and CONNECT.
10-24
Maintenance Manual – Troubleshooting Volume
C&C08 Digital SPC Switching System Chapter 10 Intelligent Network Service
Seria
Fault causes Remarks
l No.
1 The balance is inadequate.
III. Locating the fault that the caller hears busy tone after dialing the called
number
10-25
Maintenance Manual – Troubleshooting Volume
C&C08 Digital SPC Switching System Chapter 10 Intelligent Network Service
If the TCAP message tracing shows that the SSP has disconnected after receiving
the CONNECT operation, there may be several kinds of causes. For example, the
balance is inadequate, or the call has reported abnormal cause value. In this case,
the possible causes should be excluded one by one. That is, during the locating of the
fault, the possible causes can be excluded gradually according to the range of the
fault. To check whether the balance is inadequate, query the balance or call with
another card. For the abnormal circuit release by the SSP, analyze the features of the
call, so as to check whether all calls cannot be connected, or part of the numbers
cannot be connected, or the call cannot be connected due to specific call release
cause value.
4) Analyze one-stage dialing service.
For one-stage dialing service (for example, 17909), type the LST CNACLD command
to query the service category of the prefix. If it is "special access code", the SSP will
receive and send numbers at the same time, so as to increase the connection speed.
In the following cases, however, the subscriber will hear busy tone during the call:
z If the subscriber presses "#" when dialing the number, he or she will hear busy
tone immediately.
z If the intelligent call need be connected through the PRA trunk, as some PRA
trunk interfaces do not support the mode of receiving and sending number at the
same time, the intelligent call originated by the subscriber cannot be connected,
and resultantly the SSP sends busy tone to the caller. The method to deal with
the problem is as follows:
Type the LST SFP command on the maintenance console to query the value of Call
testing parameter 3 (Parameter 55). If the parameter is set to "FFFF", modify Bit 6 of
the parameter to "0", that is, "FFBF". Type the command: MOD SFP: ID=P55,
VAL="FFBF".
IV. Locating the fault that the caller hears nothing after dialing the called
number
1) Check whether there are cross-connected wires in the trunk if the call is
connected.
Start TCAP message tracing to perform signaling tracing. If the caller hears nothing
after the call is connected, he or she will hook on at once. In this case, the SSP
should report DP7.
z If the SSP can report DP7, it indicates that the call is connected. In this case,
check whether there are cross-connected wires.
z If the SSP is unable to report DP7, it indicates that the call is not connected.
Then refer to Step 2).
2) Check whether there is error in the number analysis data if the call is not
connected.
10-26
Maintenance Manual – Troubleshooting Volume
C&C08 Digital SPC Switching System Chapter 10 Intelligent Network Service
If the number that the subscriber dialed is incomplete, 20 seconds later, the SSP will
report DP4 and prompt the caller that the number is incomplete. The problem that the
caller hears nothing is because the switch considers the number is incomplete and
waits for receiving number till it times out. In this case, check the number analysis
data to see whether there is an error.
After the SCP sends CONNECT, the switch performs number analysis and route
selection. The whole process is protected through time-out processing by the timer.
Generally, it is impossible that the subscriber hears nothing for a long time. When
hearing nothing, the subscriber can wait for a while and record the waiting time.
V. Locating the fault that the caller hears the prompt tone (no authority to call)
after dialing the caller number
During the intelligent call, the cause that the SSP plays the prompt tone "no authority
to call" is that the SCP cannot find the charging data of the intelligent call. This fault
can be located in the following two ways:
1) Start the TCAP message tracing and check whether the caller and called
numbers reported by the SSP are correct.
View whether the caller number in the IDP message is correct. If not, check whether
the caller number that the SSP has received from the opposite office is correct and
the number change is performed. View the number receiving result of the PC that
corresponds to the typed called number and check whether the called number is
correct. If the result is inconsistent with the number typed by the subscriber, it is
possible that the DTMF of the subscriber telephone does not conform to the
regulations, or the number receiver in the SSP is faulty. In any of the two cases,
number receiving error will also occur for other numbers.
2) Check whether the SCP charging data is correct.
If the caller and called numbers reported by the SSP are correct, contact maintenance
engineers to check whether the SCP charging data on the SMAP is correct.
VI. Locating the fault that the call is disconnected after 18 seconds of ringing
If in the service the RRBE is configured with DP6, the SSP will report DP6 and at the
same time start a timer to monitor the no-reply time when there is no response to the
call. If in the service the RRBE is configured with no-reply time, the SSP will set the
timer according to the no-reply time. If it is not, the SSP will set the timer to 18
seconds.
That the SSP disconnects a call after 18-second ringing generally is because the SSP
adopts the default timer (18 seconds). To adjust the no-reply time, modify the value of
the timer.
10-27
Maintenance Manual – Troubleshooting Volume
C&C08 Digital SPC Switching System Chapter 10 Intelligent Network Service
Type the MOD REALTIMER command on the maintenance console and type the
following parameters:
PID=79, TIMER GROUP=1, INDEX=0, VALUE=X (it is the value of the timer to be
modified, and its unit is "second").
Note:
Without absolute certainty, do not use this command to modify the value of the host
timer. If it is necessary to modify the value, contact technical support engineers in
time.
VII. Suggestions
The key to analyze this kind of problems is to first perform TCAP message tracing to
judge whether the faults are caused by the SSP or the SCP. Then according to the
result of the judgement, analyze TCAP signaling or contact maintenance engineers
for treatment.
I. Detailed description
The SSP connection number is inconsistent with the called number that the
subscriber has dialed, for example, a certain prefix is added to the called number.
Generally, the SSP performs the connection according to the destination number sent
by the SCP. Under some special circumstances, however, the SSP can perform the
connection flexibly without following the exact command sent by the SCP. It can
automatically add the area code of the office where the caller resides before the
called number. Generally, the problem that the SSP automatically adds a prefix to a
called number is due to the following cause.
When the SSP is processing the services of several areas, if the area code of the
caller is inconsistent with the area code of the office where the SSP resides, and if the
called number has no area code, the SSP will automatically add the area code of the
office where the caller resides before the called number.
10-28
Maintenance Manual – Troubleshooting Volume
C&C08 Digital SPC Switching System Chapter 10 Intelligent Network Service
For example, an SSP is in Shenzhen (a Chinese city) whose area code is 0755, and
the 200 service of Guangzhou (another Chinese city) is also converged to Shenzhen
for processing. When the subscriber 020-87651234 in Guangzhou dials the
subscriber 77771234 in the same city, he or she dials 77771234 directly without
dialing the area code of Guangzhou before the called number. As the SSP is in
Shenzhen, if it analyzes 77771234 directly, the call will be connected to the
subscriber 77771234 in Shenzhen. This will result in a wrong call or call failure. To
avoid this case, the SSP will automatically add the area code 020 before the called
number.
10.3.9 No Charge
I. Detailed description
When an intelligent call ends, the SSP does not generate a bill or does not send the
bill information to the SCP or the billing center.
Serial
Fault causes Remarks
No.
The bills have not The SSP will not send bills to the SCP and the
1
been fetched. billing center.
The AC is lost or the
2 parameter setting is The SSP will not generate bills.
wrong.
For example, bills will not be generated for zero
The charge is
charge, and there will be no charge when the
restricted by the
3 conversation duration is shorter than the
setting of the SSP
minimum conversation duration. As a result, the
charge parameter.
SSP will not generate bills.
1) Check whether the bills have been fetched from the host.
Carry out the LST BILPOL command to query the bill buffer of the host, view the
changes of pointers in the bill pool and check whether the bill have been fetched.
2) Check whether the SCP has sent the AC operation.
In the aspect of charge, the SCP determines whether to charge, the charging
category and charge-related information, while the SSP is responsible for the
concrete record. When the SCP starts an AC operation, the result of the operation is
that the SCP sends an AC information stream, that is, request the SSP to generate an
10-29
Maintenance Manual – Troubleshooting Volume
C&C08 Digital SPC Switching System Chapter 10 Intelligent Network Service
account record. At this time, the SSP receives and analyzes the AC request, and
begins to charge according to the request. When a charging operation of the SSP
ends, the SSP offers the SCP an "Apply Charge Report" and sends the charging
results to the SCP.
According to the above charging flow, start the TCAP message tracing on the
maintenance console to check whether the SCP has sent the AC operation and view
whether the AC parameter is correct.
z If the SCP has not sent the AC operation, check whether the SCP is running
normally.
z If the AC parameter is incorrect, check the operation of the signaling network, for
example, whether switchover is performed frequently.
3) Check whether the conversation belongs to the case "no charge when the
conversation duration is shorter than one second".
Carry out the LST SFP command to query the setting of "SSP parameter 1".
z Bit 11 of SSP parameter 1 controls whether to charge the conversation whose
duration is shorter than one second. Its default value is 1, which indicates "no
charge when the conversation duration is shorter than one second".
z Bit 10 of SSP parameter 1 controls whether to generate bills for zero charge. Its
default value is 1, which indicates that "bills will not be generated for zero
charge".
If the conversation duration is shorter than one second, by default the charge is 0,
and no bill will be generated.
4) Check whether the conversation duration is shorter than the minimum charging
duration.
As the Ministry of Information Industry in China has stipulated that "no charge should
be performed for the conversation whose duration is shorter than six seconds", the
SSP has added the support for this stipulation. When operators configure charging
category and other data, it is allowed to configure the minimum conversation duration.
If the conversation duration of a call is shorter than the minimum conversation
duration, it is possible that bills are not generated.
z Start the TCAP message tracing on the maintenance console and view the
charging category in the AC message.
z According to the charging category, use the LST CHGCLS command to query
the minimum charging duration of the charging category on the SSP.
z Check whether the conversation duration is shorter than the minimum charging
duration. If yes, check whether the SSP generates bills in case of zero charge.
For concrete methods, refer to Step 3).
10-30
Maintenance Manual – Troubleshooting Volume
C&C08 Digital SPC Switching System Chapter 10 Intelligent Network Service
IV. Suggestions
Flexible application of the TCAP message tracing is a common method to locate the
faults related to charging.
I. Detailed description
Seria
Fault causes Remarks
l No.
The AC parameters include the information of the
The parameters in caller and called numbers. If they are wrong,
1
the AC are wrong. apparently the bills will become abnormal and
charging errors will occur.
If there are caller and called numbers in the AC message, when generating bills, the
SSP adopts the caller and called numbers sent in the AC. If there is no caller or called
in the AC message, the SSP adopts the default caller and called numbers.
2) Check the data in the SSP that is related to the call.
If there is no caller or called number in the AC message, check the number change
data related to the intelligent call in the SSP and analyze how the caller and called
numbers in the bill are obtained.
The commands commonly used include LST DNC, which is to query the number
change, MOD DNC, which is to modify the number change attribute, LST SPDNC,
10-31
Maintenance Manual – Troubleshooting Volume
C&C08 Digital SPC Switching System Chapter 10 Intelligent Network Service
which is to query special number change, and MOD SPDNC, which is to modify
special number change attribute.
3) Contact maintenance engineers.
If the fault still cannot be located, contact maintenance engineers for analysis and
treatment.
IV. Suggestions
Flexible application of the TCAP message tracing is a common method to locate the
faults related to charging.
I. Detailed description
During the connection process of an incoming intelligent call, the SSP sends back the
reply signaling to the originating office when the call is still not set up, which results in
charging error in the originating office. The fault may be as follows.
The call is disconnected immediately after the reply. That is, after the called party in
the local office replies, the local office sends reply signaling to the originating office
(the call is charged), but the caller hears busy tone at once.
Serial
Fault causes Remarks
No.
The SSP resource is As a result, the call will be disconnected
1
unavailable. immediately after the reply.
III. Locating the fault that the call is disconnected immediately after the reply
The fault that the call is disconnected immediately after the called party replies is
generally caused the failure of SSP resource application.
After receiving the first PA/PC operation, the SSP will send reply signaling to the
originating office, and at the same time apply for resources. If the resource application
fails, the SSP will report the failure to the SCP. As a result, the SCP will send back
"Release Call", the call will be released, and the caller in the originated office will be
charged.
In this case, first perform TCAP message tracing to check whether the signaling flow
is similar to the correct service flow mentioned above. If yes, analyze the cause that
10-32
Maintenance Manual – Troubleshooting Volume
C&C08 Digital SPC Switching System Chapter 10 Intelligent Network Service
makes the resource unavailable. For the details of the treatment, refer to 10.3.3
Resource Application Fault.
IV. Suggestions
After the one-stage dialing service starts, perform dial test to such cases as
inadequate balance and no authority to call, so as check whether the function "Send
ACM tone playing" can be fulfilled normally.
I. Detailed description
Serial
Fault causes Remarks
No.
As the SSP cannot correctly report the cause value of
The working of the connection failure, the cause value of the Release
1 the SCP is Call that the SCP sends to the SSP is "normal call
abnormal. clearing". As a result, the SSP sends the CFL message
to the originating office.
If the SSP transfers the CFL message from the
2 Other causes lower-level office, then the problem is in the lower-level
office.
For different causes of call release, different calculation methods are used in the call
completion rate statistics. If the SSP sends the CFL message to the originating office
by mistake, statistics of the call completion rate of the local office will be affected. As a
result, the call completion rate will decrease.
1) Check whether the CFL message is generated by the SSP.
In the C&C08 Maintenance Tool Navigator on the maintenance console, select the
option [No. 7 signaling/ No. 7 signaling tracing]. Select "Save tracing message" to
trace the SSP incoming and outgoing signaling link message. Then use the signaling
analysis software Analysis to analyze the call through which the SSP sends the CFL
10-33
Maintenance Manual – Troubleshooting Volume
C&C08 Digital SPC Switching System Chapter 10 Intelligent Network Service
In cases such as fault occurs in the route selection, the called party does not reply or
is busy, the SSP should check whether the correct cause value is reported when
reporting the DP event. This is because in these cases, the SCP will transmit the
cause values directly to the SSP when it sends the Release Call.
In the C&C08 Maintenance Tool Navigator on the maintenance console, select the
option [Intelligent/TCAP message tracing]. Then type the relevant information and
start the message tracing. Perform telephone analog dial test, analyze the
corresponding TCAP signaling and check whether the CFL message is caused by the
SCP. If yes, contact maintenance engineers for treatment.
3) Contact technical support engineers.
If the fault still cannot be loaded or you are not confident of your judgement, contact
technical support engineers timely.
IV. Suggestions
Proficient use of such maintenance tools as No. 7 signaling tracing and TCAP
signaling tracing is an effective method to locate the fault that the SSP sends the CFL
message by mistake.
10-34
Maintenance Manual – Troubleshooting Volume
C&C08 Digital SPC Switching System Appendix A Acronyms and Abbreviations
A
AC Alternating Current
ALM Alarm Interface Board
ALS Alarm Service
AM Administration Module
AMD Alarm Drive Board
AMP Administration Processor Board
ASL Analog Subscriber Line Board
B
BAC Bus Administration & Configuration Board
BAM Back Administration Module
BCC Bus Control Cell Board
BER Bit Error Rate
BIOS Basic Input/Output System
BITS Building Integrated Timing Supply
BLO Blocking Signal
BNET B-type Network Switching Board
BSN Backward Sequence Number
C
CAS Channel Associated Signaling
CCB Central Control Database
CCM Communication Control Module
CCS Common Channel Signaling
CD Compact Disk
CDP Concurrent Development Process Board
CFB Call Forwarding Busy
CFL Call Failure Signal
CFU Call Forwarding Unconditional
CGC Circuit Group Congestion Signal
CIC Circuit Identification Code
A-1
Maintenance Manual – Troubleshooting Volume
C&C08 Digital SPC Switching System Appendix A Acronyms and Abbreviations
A-2
Maintenance Manual – Troubleshooting Volume
C&C08 Digital SPC Switching System Appendix A Acronyms and Abbreviations
A-3
Maintenance Manual – Troubleshooting Volume
C&C08 Digital SPC Switching System Appendix A Acronyms and Abbreviations
IN Intelligent Network
INAP Intelligent Network Application Protocol
IP Internet Protocol
ISA Industry Standard Architecture
ISDN Integrated Services Digital Network
ISP Internet Service Provider
ISUP ISDN User Part
International Telecommunication Union -
ITU-T
Telecommunication Standardization Sector
L
LAN Local Area Network
LED Light Emitting Diode
LIM Line Interface Module
LPMC2 Inter-Module Communication Processing Board
LPN7 Common Channel Signaling Processing Board
LPRA PRA Protocol Processing Board
LSSU Link Status Signal Unit
M
MC2 Inter-Module Communication Board
MEM Memory Board
MFC Multi-Frequency Compelled Board
MFPS Multi-Frequency Pulse
MGB Maintenance Oriented Group Blocking Message
MHI Multi-HW Interface Board
MMI Man Machine Interface
MML Man Machine Language
MO Magneto Optical (disk)
MPU Main Processor Unit Board
MS Microsoft
MTP Message Transfer Part
N
NCC Network Communication Control Board
NET NET Card
NM Network Management
A-4
Maintenance Manual – Troubleshooting Volume
C&C08 Digital SPC Switching System Appendix A Acronyms and Abbreviations
A-5
Maintenance Manual – Troubleshooting Volume
C&C08 Digital SPC Switching System Appendix A Acronyms and Abbreviations
A-6
Maintenance Manual – Troubleshooting Volume
C&C08 Digital SPC Switching System Appendix A Acronyms and Abbreviations
ST Segment Type
STM-1 SDH Transport Module -1
STP Signaling Transfer Point
STU STM-1 Transit Unit Board
T
TA Terminal Adapter
TCAP Transaction Capabilities Application Part
TCP Transmission Control Protocol
TDP Trigger Detection Point
TSM Trunk Switch Module
TTL Transistor-Transistor Logic
TUP Telephone User Part
U
UCS Universal Card Service
UPS Uninterrupted Power Supply
UTM User & Trunk Module
V
VAS Value-Added Service
W
WAN Wide Area Network
WS Work Station
A-7
Maintenance Manual – Troubleshooting Volume
C&C08 Digital SPC Switching System Index
Index
i-1
Maintenance Manual – Troubleshooting Volume
C&C08 Digital SPC Switching System Index
i-2
Maintenance Manual – Troubleshooting Volume
C&C08 Digital SPC Switching System Index
i-3
Maintenance Manual – Troubleshooting Volume
C&C08 Digital SPC Switching System Index
J SCP, 10-4
signaling link code, 3-3
judging the transmission system, 2-19
signaling link initial location, 3-4
S self-ringing, 2-9
subscriber fault, 2-24
SCE, 10-5
unidirectional call, 2-32
i-4
Maintenance Manual – Troubleshooting Volume
C&C08 Digital SPC Switching System Index
supplementary service data backup, 2-31 DSS1 signaling link broken, 3-23
switch networking application, 2-3 DSS1 signaling link interworking abnormal, 3-25
switching system structure, 5-2 DSS1 signaling link unestablished, 3-23
No. 7 Signaling Interworking abnormal, 3-17
T No.7 circuit available blocking, 3-8
terminal system communication structure, 7-2 No.7 circuit unavailable blocking, 3-8
BAM virus prevention & clearing, 7-10 No.7 link block, 3-13
testing power voltage waveform, 2-20 PRA trunk circuit fault, 3-21
too much alarm information, 5-9 PRA trunk circuit not activated, 3-21
i.
i-5