Topic On R003 PRA Configuration and Fault-20030122-B

C&C08 Digital SPC
Document code Product name Switching System

Target readers Huawei Engineers/Partner Engineers Product version OVSV610R103
Edited by Fixed network technical support department Document version V1.0
Topic on R003 PRA Configuration and

Fault
Drafted by: Meng Qingxiao Date: 2002-01-10
Reviewed by: Lvxiaochao Date: 2003-01-22
Reviewed by: Date:
Approved by: Huangyong Date: 2005-03-23
Huawei Technologies Co, Ltd

All Rights Reserved
Confidentiality Level:
Topic on R003 PRA Configuration and Fault Internal Use Only
Revision Records
Date Revised version Description Author
2002-01-10 V1.0 Draft Meng Qingxiao
Huawei Confidential. No disclosure without permission.

Contents
Chapter 1 Introduction to PRA........................................................................................................ 1

1.1 Explanation of PRA Data Concepts...................................................................................... 1
1.2 PRA Call Flow....................................................................................................................... 3
1.3 PRA Data Setting Sequence ................................................................................................ 4
Chapter 2 PRA Application and Other Precautions...................................................................... 6
2.1 Inter-module Data Setting of PRA Trunk .............................................................................. 6
2.2 Precautions on the Control of Multiple PCMs by one PRA Link........................................... 6
2.2.1 Data Setting Method .................................................................................................. 6
2.2.2 Usage of Network Check Identifier When One PRA Link Controls Multiple PCMs ... 7
2.3 How Does the PRA Conduct Number Conversion ............................................................... 7
Chapter 3 PRA Data Configuration................................................................................................. 9
3.1 Adding an Office ................................................................................................................... 9
3.2 Adding Sub-route .................................................................................................................. 9
3.3 Adding Routing Table ........................................................................................................... 9
3.4 Adding Route Analysis........................................................................................................ 10
3.5 Adding a Service Prefix ...................................................................................................... 10
3.6 Adding a Number Segment ................................................................................................ 11
3.7 Adding ISDN Data .............................................................................................................. 11
3.8 Adding a PRA Subscriber ................................................................................................... 11
3.9 Adding a PRA Link.............................................................................................................. 12
3.10 Adding PRA Trunk Group ................................................................................................. 13
3.11 Adding PRA Trunk Circuit................................................................................................. 14
Chapter 4 Fault Handling............................................................................................................... 15
4.1 PRA Trunk Circuit Fault ...................................................................................................... 15
4.2 PRA Signaling Link Fault (PRA Trunk) ............................................................................... 16
4.3 PRA Signaling Cooperation Fault (PRA Trunk).................................................................. 19
4.3.1 Whether the Called Number Includes the Area Code:............................................. 20
4.3.2 The Called Number Cannot Send the Ringback Tone:............................................ 21
4.3.3 Incoming/Outgoing Call Authority and Charging of PRA: ........................................ 21
4.3.4 One PRA Link Controls Multiple PCMs:................................................................... 21
Chapter 5 Network Fault Cases of PRA ....................................................................................... 23
Chapter 6 Data Configuration Differences between Versions ................................................... 29
6.1 PRA Data Differences between 32-SM Switch and 128-SM Switch .................................. 29
6.2 1283K Old Versions - 3007SP1, 3008, 4011 and 5001 ..................................................... 29

Key words:
PRA Signaling,PRA configure, ISDN Signaling
Summary:
This document introduce PRA signaling dataconfigure and fault handling.
List of abbreviations:
Abbreviations Full spelling

PRA Primary Rate Access
Reference list:

Chapter 1 Introduction to PRA
1.1 Explanation of PRA Data Concepts

What is PRA?
PRA refers to Primary Rate Access, which means network access at the rate of 2Mb.
PRI refers to Primary Rate Interface, i.e., 30B + D. In the actual application of C&C08
switching system, PRA is PRI. They are the same. Within the range of ISDN, It is
more appropriate to call 30B + D as PRI.
C&C08 ISDN PRA structure
ISDN
ISDN call
呼叫控制 control
Host MPU
NOD MB
MB
NOD
MB
LL MB 通信
Transmissi communication
PRA PP
传输系统
on system PRA Q.921
Q.921
RR
AA HDLC
HDLC
Figure 1-1 PRA structure
The 30B+D interface unit is mainly composed of two parts: Interface circuit board and
protocol processing board. The interface circuit board mainly implements the function
of PRI, including extraction of synchronous clock, CRC error check and transparent
transmission of D channel, etc. The protocol processing board processes Digital
Subscriber Signaling No. 1 (DSS1) of the Link Layer and Network Layer transmitted
via D channel. Furthermore, they should communicate with the main processor
respectively in order to achieve the circuit switching and call control. Set the PRA
and LAPPRA as example, its structure is as shown in Figure 1-1.
The existing structure of the DTM board is used for the PRA board hardware, and the
I.431 protocol defined for the Physical Layer and the I.604 protocol used for PRA
maintenance serve as the Physical Layer protocols. I.431 basically inherits the
specifications of PCM PRA in ITU-T Recommendation G.703. The point-to-point
cabling is adopted between the primary group and terminal. The interface is not
configured with the activating and deactivating functions. The equipment at both sides
of the interface is always in the activated state.
2003-01-15 Huawei Confidential. No disclosure without permission. Page 1 of 34

The protocol processor chip used within the protocol processing board (LAPPRA) can
simultaneously process four HDLC channels. At present, one 30B+D HDLC link can
correspond to one or multiple PCM lines. The CB03LPRA7 board can support
dual-CPU, but a board software above Version B200 is needed. In this case, one
LAPPRA have two processor chips, so it can process a maximum of eight HDLC links.
The software of this board runs in an independent operating system. The bottom layer
processes HDLC transmitting/receiving, L2 processes Q.921 protocol, L3 processes
Q.931 protocol, management of entities,MPU mailbox communication , etc.
What is DSS1?
DSS1 refers to Digital Subscriber Signaling No.1, including network DSS1 and user
DSS1. In one PCM, generally TS16 is used to transfer DSS1, and the other 30
timeslots serve as B channels. The call connection process is the same as that of
common digital subscribers. The DSS1 signaling is used for the PRA.
What are the concepts of U, N and C and the meaning of N<->N message during
PRA port signaling trace?
U stands for User, i.e., common DSL, V5DSL subscribers and PRA subscribers, N
stands for the ISDN control layer, which is the intermediate call control layer between
U and C, and C stands for the core control layer for call processing of the switch.
There can only be message containing U and N or message containing N and C,
there will absolutely be no message directly including U and C across N.
N<->N refers to the internal display function added for the convenience of fault
location within the switch. It can be used to print out call reference state, subscriber
data, timer timeout, etc.
What is the subscriber mode and trunk mode of PRA interconnection?
With respect to the ISDN principle, PRI is the subscriber access mode, so the PRI
should be regarded as a subscriber. For C&C08 switches before Version R02, the
PRI is also implemented in the subscriber mode. However, with the rapid
development of data communications in recent years, the PRI in the subscriber mode
exposes many limitations: Firstly, if multiple PRIs are interconnected in the same
office, the concept of Private Branch Exchange (PBX) should be used. Use a
subscriber as the indicating number and other subscribers as the non-indicating
numbers, so the data turns very complicated. Secondly, with the rising of the
data communication products level within the network hierarchy , it do not merely
serve as communication terminals accessing the telecom networks, but can occupy
the position of tandem office as well, for example, IP telephone access gateway.
However, most data communication products are not carrier class products, they
cannot provide Signaling System No. 7 (SS7), Thus, if CC08 switch is to be
interconnected with such data communication products using PRI subscriber mode, it
definitely cannot meet the basic services requirements. For example, the
interconnected party is an IP access gateway, so all toll calls should be connected
with the IP gateway in the tandem mode. Considering that the PRI number is fixed in
the subscriber mode, then the C&C08 switch cannot send the toll calls to the IP
gateway. Based on the above mentioned situations, C&C08 switches above Version
R03 also provide the trunk PRI. In the trunk PRI mode, the PRI is regarded as a
trunk and is not regarded as a subscriber any more, so the original subscriber
features have faded out. Thus, the original routing flow can be inherited (the PRA
PBX function is removed), so the data is simple and explicit. Of course, for version
R03 or higher versions , we do not just adopt the mode of “subscriber mode” + “trunk
mode”, but have changed the setting considerations of the whole PRI data.

1.2 PRA Call Flow

For C&C08 switches above Version R03, the routing concept in trunk data is
“borrowed”, regardless of the trunk mode or subscriber mode. After the route
selection code is obtained, the route data processing mode is basically the same as
that NO. 1/No. 7 trunk. In the subscriber mode, the prefix of the PRA subscriber in the
Called analysis table should be set as “Local office” and the PRA subscriber data
indicates the route selection code. In the trunk mode, the prefix of the PRA subscriber
in the Called analysis table should be set as “Local office” and the called number
analysis data indicates the route selection code. Please note, the PRA subscriber
data should be configured, regardless of the trunk mode or subscriber mode. The
host should process the corresponding call authority and new service authority and
also should point out the route selection code in the subscriber mode.
PRA serves as the called party in the subscriber mode
Based on the called number, we know the call is a local call through the called
number analysis. Search the Number segment table and obtain the subscriber index
so as to further obtain the subscriber logic sequence number. Query the PRA
subscriber data table to obtain the PRA subscriber data (including the route selection
code). Conduct the processing of the corresponding authority of the subscriber.
According to the call source code of the calling number, query the call source table to
obtain the route selection source code.
Based on the route selection code and the route selection source code, query Route
analysis->Route->Sub-route->Sub-route/trunk group-->Trunk group->Trunk circuit to
obtain the trunk circuit number.
Convert the selected trunk circuit number into B channel number and send it to the
end peer via the signaling link.
PRA serves as the called party in the trunk mode
Based on the called number, we know the call is a local call through the called
number analysis, so as to obtain the route selection code.
According to the call source code of the calling number, query the call source table to
obtain the route selection source code.
Based on the route selection code and the route selection source code, query Route
analysis->Route->Sub-route->Sub-route/trunk group-->Trunk group->Trunk circuit to
obtain the trunk circuit number. According to the default calling number in the Trunk
group table, find the corresponding PRA subscriber data in the PRA subscriber data
table and conduct the processing of the corresponding authority of the subscriber.
PRA serves as the calling party
Firstly, the user terminal sends the SETUP message to the network and the host finds
the signaling link number of the signaling according to the reported SETUP signaling.
Determine the calling number and routing trunk group. Normally, when the network
check flag is set as “No” and a PRA link controls a PCM, if the SETUP message from
the user terminal does not include the calling number, the trunk group controlled by
this signaling link will serve as the routing trunk group and the default calling number
of this trunk group will serve as the calling number of this call. Based on the calling
number, obtain the PRA subscriber data and conduct the corresponding authority
processing. If the SETUP message includes the calling number, then no matter
whether the calling number is correct or not, this number will serve as the calling

number and also the trunk group controlled by this signaling link will serve as the
routing trunk group.
Transmit the calling number obtained in the above step transparently and query the
PRA subscriber data according to the default number index of the trunk to obtain the
data of call source, charging source, call authority and new service authority.
Based on the routing trunk group number, query the data of this trunk group in the
Trunk group table to obtain the circuit selection mode, such as the maximum value,
minimum value, cycle, etc.
According to a selected idle circuit, the DSS1 circuit number is converted into B
channel indicator and sent to the peer party via Call_proceding signaling.
1.3 PRA Data Setting Sequence

Overview
The physical data of PRA is the basis of PRA configuration. However, the really
complicated part is the logical data of the PRA. The logical data of the PRA has a
wide coverage, including route data, subscriber data , trunk data, etc. If we only give
a brief explanation, the user possibly cannot understand it very well, so we provide
relevant figures and tables to illustrate these concepts and their operation methods.
The purpose of setting such hierarchy of the PRA data is to maintain the consistency
and security of the database. C&C 08 MML has effectively prevented hidden
troubles upon the database caused by misoperations, enhanced the data relevance,
so that the operations are not in chaos any more (but in perfect sequence) and the
data redundancy is also reduced greatly.
With such data relevance, the user sometimes may feel that there are too many
constraints upon data operations. However, if you understand the hierarchy of the
PRA data (even though you do not understand the PRA concept clearly ), you only
have to follow our operation instructions and the PRA data operation principles, then
you will feel that the data operations are very easy and there is no the feeling of
constraint any more.
Hierarchy and Operation Principle of PRA Data
The following graphic shows the relationship among PRA data:

Trunk circuit
Trunk group
Subscriber
Call source Prefix analysis PRA signaling link
number
Number
Route analy sis ISDN index
segment
Route
Sub-route
Office
Figure 1-2 PRA data reference relationship
The blocks in the figure stand for the data setting contents, the connection lines stand
for a kind of reference relationship and the data under a connection is referred by the
data above the connection line. For example, to serve as the route data, the data
should serve as the sub-route data; to serve the trunk group data, the data should
serve as the subscriber number data, sub-route data and PRA signaling link data.
However, to serve as the subscriber data, the data should also first serve as the
number segment data, ISDN index data and route analysis data, and so on. In the
above figure, one point is to be mentioned; the reference relationship between the
call source and number segment. The key item of number initial set is referred by the
call source. For the simplicity of the above figure, the relationship among them is not
marked.
At present, these block diagrams are classified as follows:
Route data: Office, sub-route, route and route analysis
Subscriber data: Call source, prefix analysis, number segment, ISDN index and
subscriber number
Trunk data: PRA signaling link, trunk group and trunk circuit
According to the above-mentioned invoking relationship, we can obtain the PRA data
setting sequence. Since the route data is in the bottom layer and is referred to by the
subscriber data and trunk data, then the route data should be configured firstly.
Secondly, configure the subscriber data. The subscriber data involves many aspects,
including call source, basic prefix analysis, routing information, etc. Finally, configure
the trunk data, since it is in the topmost layer in the whole hierarchy. The
above-mentioned is the operation principle of adding new data, i.e., the data at the
lower layers should be configured first.

Chapter 2 PRA Application and Other Precautions
2.1 Inter-module Data Setting of PRA Trunk

Although the setting method of the PRA trunk route is similar to that of common trunk,
special attention is needed in some cases, for example, the inter-module data setting
of the PRA trunk. For common trunk route, we configure the inter-module trunk data
as follows: Firstly, add a new sub-route, fill in the first and second searching modules,
set the trunk group selection mode as “Cycle”; secondly, in the route data, set the
sub-route as “Sequential selection”, fill in the first sub-route; finally and then add a
new trunk group (the trunk group of each module is included under this sub-route);
finally, configure other data to implement the inter-module trunk function. However,
the practices show that this method is not applicable in the PRA mode. In the PRA
mode, one sub-route cannot manage the trunk groups in multiple modules. If we
configure data according to the above-mentioned common method, the following
phenomena may occur: 1). If the first incoming call is allocated to the trunk of a
module, then all subsequent incoming calls will be allocated to this module in
preference. 2). If the PRA trunk in this module is full or the trunk is disconnected, the
new incoming calls will be allocated to another module. 3). Once the calls are sent to
another module, even if the transmission of the first module is recovered or the trunk
is idle, the host will not allocate the calls to the first module, but to the second module
until the trunk of the second module is full or trunk transmission fails. Thus, it will lead
to unbalanced traffic. Obviously, such mode cannot meet the inter-module
requirements.
The correct inter-module PRA trunk data setting method is as follows:
Add several new sub-routes so that each module where the PRA trunk is located has
one sub-route. Add new route data, select sub-routes according to the percentage
and fill in the sub-routes such as the first and second sub-routes. Thus, the traffic is
allocated in the sub-route layer in average and the defects of the inter-module trunk
group layer are removed.
2.2 Precautions on the Control of Multiple PCMs by one PRA

Link
2.2.1 Data Setting Method
For a PRA link to control multiple PCMs, the circuit numbers of the interconnected
parties should be confirmed. As CIC identifier is used for SS7 trunk, then B
channel number is used as the identifier in the PRA trunk. However, the B channel
number ranges from 1 to 31. To identify B channels in different PCMs, the concept of
PCM interface identifier is introduced. Both parties negotiate consistent interface
identifier, then the interface identifier and B channel number are transferred to the
peer party via the SETUP signaling. Thus, a unique circuit can be identified. The
interface identifier is added to the PCM physical attribute data (ADD PCMATR). The
equipment number in this command refers to the circuit number of Timeslot 0 of the
PRA, and the signaling link number is consistent with that in the PRA signaling link
table. The interface identifier is the conventional value of the interconnected parties,
so the interface identifiers of both parties are the same. CRC4 is not supported for the
time being, so it should be set as “No”. The specific principles are as follows:
A. In the trunk circuit table, each PCM serves as a trunk group, and a PRA link
controls a maximum of four PCM5 trunk groups, i.e., five PCMs.
B. In the PRA signaling link table, “locate” the signaling link to Timeslot 16 of one
PCM.
C. Add PCM physical attributes and use the interface identifier to identify each PCM
(the interconnected parties should have the same identifier).
Note:
It is not safe for one PRA link to control multiple PCMs, because if the PCM where link is located is
interrupted, the whole office will be blocked. Furthermore, in actual application, the interconnected party
(data product) always can guarantee that each PCM provides a PRA link. In addition, not all switches
(data products) support interface identifier. Therefore, please do not use this function unless necessary.
2.2.2 Usage of Network Check Identifier When One PRA Link Controls
Multiple PCMs
If one PRA controls multiple PCMs, each PCM has different calling numbers. In this
case, if the setup message sent by the end peer via the PRA link includes the calling
number, how should we select the trunk group corresponding to the calling number?
The host processing process is as follows: The network check whether the identifier is
set as “Yes”, if the SETUP message from the user terminal does not include the
calling number, the processing is the same as that when the network check identifier
is set as “No”; if the SETUP message includes the calling number, it conducts
subscriber number analysis of the calling number. If this number does not correspond
to the PRA subscriber, the processing is the same as that when the network check
identifier is set as “No”, otherwise we can obtain the route selection code (CODE_1)
corresponding to this number in the PRA subscriber data table. Select the default
calling number of the first trunk group controlled by this signaling link to conduct
subscriber number analysis, so as to obtain another route selection code (CODE_2).
If CODE_1=CODE_2, this calling number is valid and this trunk group serves as the
routing trunk group. If CODE1<>CODE2, select the default calling number of the
second trunk group controlled by this signaling link to conduct subscriber number
analysis, so as to obtain CODE_2. Please conduct the same processing as the
above-mentioned. If all trunk groups controlled by this signaling link do not meet the
conditions, the processing is the same as that when the network check identifier is set
as “No”.
2.3 How Does the PRA Conduct Number Conversion

For a PRA subscriber to conduct the called number conversion, the common number
conversion can be used, i.e., implemented by executing the command of ADD
PFXPRO. However, the ISDN also provides a called number conversion method:
Using the called number conversion index of ADD ISDNDAT to implement the
conversion (For outgoing call, the called number conversion index of the ISDNDAT
takes effect only after the PRA subscriber has set DDI new service authority). If the
PRA subscriber wants to implement the calling number conversion index, the
common number conversion also can be used. However, the ISDN also provides a
calling number conversion method: using the number conversion index of ADD

PRALNK to implement the conversion. However, it is recommended that the common

number conversion be used so that the data can be normalized and consistent.

Chapter 3 PRA Data Configuration
3.1 Adding an Office

Role: Setting a PRA office so as to point to the PRA
Command position: Office data configuration/office/
Command: ADD OFC: O=0, DOT=CMPX, DOL=LOW, NI=NAT, DPC=“aaaaaa”,
ON=“999pra”, DOA=SPC;
New office
Office number: 10 (virtual PRA office)
Type of peer office: Toll, local and rural calls integrated into one
Level of peer office: Lower level
Network ID: National
Destination signaling point code: aaaaaa (defining PRA signaling point)
Office name: 999pra
Attributes of peer office: Program-controlled office
3.2 Adding Sub-route

Role: Setting PRA sub-route.
Command position: Office data configuration/trunk route/sub-route
ADD SRT: SR=10, DOM=10, SRT=OFC, SRN=“999pra”, MN1=1;
Add sub-route
Sub-route number: 10
Office number/Peer module number: 10 (virtual PRA office number)
Rub-route type: Inter-office sub-route
Sub-route name: 999pra
Trunk group selection mode: Cyclic
The first searching module: 1
Default values are used for all the others
3.3 Adding Routing Table

Role: Setting PRA route.

Command position: Office data configuration/trunk route/route

ADD RT: R=10, RN=“999pra”, RT=NRM, SRST=SEQ, SR1=10;
Add route
Route number: 999pra
Route type: Common route
Sub-route selection mode: Sequential selection
The first sub-route: 10
3.4 Adding Route Analysis

Role: Setting PRA route analysis
Command position: Office data configuration Table/trunk route/analyzing data
ADD RTANA: RSC=10, RSSC=0, RUT=ALL, ADI=ALL, CLRIN=ALL, TRAP=ALL,
TMX=0, R=10;
Add route analysis
Route selection code: 10
Route selection source code: 0
Type of calling subscriber: All types
Address information indicator: All types (depends upon the on-site requirements of
the equipment buyer)
Calling number access: All types
Transmission capability: All types
Time index: 0
Route number: 10
3.5 Adding a Service Prefix

Role: Setting a PRA subscriber service prefix
Command position: Office data configuration/number analysis/basic service prefix
Command: ADD CNACLD: P=0, PFX='999, CSTP=BASE, CSA=LC, RSC=10,
MIDL=3, MADL=7;
Add a service prefix
Number initial set: 0
Call prefix: 999 (Default call prefix of PRA subscriber)
Service type: Basic service
Service attributes: Local

Minimum number length: 7
Maximum number length: 7
3.6 Adding a Number Segment

Role: Setting default number segment of PRA subscriber.
Command position: Subscriber management/number segment management
Command: ADD NASEG: P=0, BEG=K'9990000, END='9990009, INDX=0;
Add a number segment,
Number initial set: 0
Start number: 9990000
End number: 9990009
Subscriber start index: 0
3.7 Adding ISDN Data

Role: Setting ISDN data for the convenience of the access of PRA (30B+D)
Command position: Subscriber management/ISDN management /ISDN data
Command: ADD ISDNDAT: ID=1, CMF=TRUE, BCN=30;
Add ISDN data
ISDN index: 1
Circuit access: Yes
Maximum number of B channels: 30
Default values are used for all the following parameters
3.8 Adding a PRA Subscriber

Role: Setting a PRA subscriber for the access of PRA via the subscriber
Command position: Subscriber management/PRA subscriber
ADD PRA: D=K'9990000, RSC=10, ISDN=1, MN=1, RCS=0, NS=DDI-1—CLIP-1;
Add a PRA subscriber
Subscriber number: 9990000 (multiple subscriber numbers can be added, and each
PRA trunk group defines a subscriber number)
ISDN index: 1
Module number: 1
Charging source code: 0
New service authority: Direct dial-in, calling line identification presentation
Where:
(1) The subscriber number is a real number.
(2) Route selection code: The route selection code of the PRA subscriber should be
consistent with that obtained from the called number analysis.
(3) ISDN index: Corresponding to 30B + D;
(4) Module number: The number of the module where this number is located should
be consistent with the module number corresponding to the following PRATG (this is
its difference from C&C08 switch. Please pay attention during the deployment of
128-SM switch).
(5) Charging source code: Corresponding to the corresponding charging data, please
note that the PRA implements charging via the charging source code here. The
charging source code in the PRATG is useless.
(6) Incoming and outgoing call authority: Please note that its difference from SS7
trunk is that the incoming call authority controls the outgoing PRA calls and the
outgoing call authority controls the incoming PRA calls. The incoming/outgoing call
authority in the PRATG is useless.
(7) New service authority: Direct Dialing-In (DDI) right and Calling Line Identification
Presentation (CLIP)
(8) Number initial set: It should be the same as that of the PRA subscriber number.
(9) Other parameters are useless, so just use the default values.
Note: Of course, when adding the PRA subscriber, like other subscribers, please add
number segment in the Number segment table, and also the subscriber number
should be legal.
3.9 Adding a PRA Link

Role: Setting PRA link.
Command position: Subscriber management/ISDN management/PRA link
Command: ADD PRALNK: MN=1, SLN=64, SCN=336;
Add a PRA link
Module number: 1
Signaling link number: 64 (determined according to the location of the LAPRA board
on site)
Signaling circuit number: 336 (determined according to the PRA circuit board number
on site, the link occupies 16 timeslots)
Where:

(1) Module number: Fill in according to the actual situations.

(2) Signaling link number: for SM, if the LPRA board is configured with a single CPU,
there are four optional links; if the LPRA board is configured with two CPUs, there are
eight optional links. For SPM, configure any one of the 16 links.
(3) Circuit number: the 16 timeslots of the corresponding PCM.
(4) When the network check ID is set as “No”: transparent transmission of the real
calling number; if the network check ID is set as “Yes”, the calling number is changed
to the default PRA number corresponding to the selected trunk group.
Calling number conversion index: If a PRA subscriber wants to implement the calling
number conversion index, the common number conversion can still be used. However,
the ISDN also provides a calling number conversion means, i.e., implementing the
conversion via the number conversion index of ADD PRALNK. Please note if the
length of the sent calling number is not of fixed length, (i.e., the number possibly is of
7 digits or eight digits), then both the methods cannot be used. In this case, set the
network check ID as “Yes” and we can use the default PRA number. In case when the
incoming trunks in two directions shares the outgoing PRA, if the lengths of the
calling numbers sent by the two incoming trunks are not equal (for example, one
number is of 7 digits and the other is of 8 digits), but it is still required that the PRA
should transmit the real calling number transparently, just set the network check ID as
“No”.
(5) Other parameters are useless, so just use the default values.
3.10 Adding PRA Trunk Group

Role: Adding PRA trunk group
Command position: Office data configuration/trunk route/PRA trunk group
Command: ADD TGPRA: TG=10, SRC=10, MN=1, SIGL=64, DI=K'9990000,
TGN=“999pra”, ILN=7;
Add PRA trunk group
Trunk group number: 10
Sub-route number: 10
Module number: 1
Signaling link: 64
Default number: 9990000 (each trunk group defines a default number)
Trunk group name: 999pra
The minimum length of the calling number: 7
Where:
(1) Trunk group number: Fill in according to the actual situations.
(2) Sub-route number: Belongs to sub-route
(3) Module number: Please note that the module number should be consistent with
the module number corresponding to the default PRA number, otherwise the call
cannot be connected and the system will prompt that the subscriber number you

dialed has been changed or the number is not available. (This is its difference from
C&C08 switch. Please pay attention during the deployment of 128-SM switch).
(4) Default number: The PRA number configured before, other ASL or DSL subscriber
number should not be used.
(5) Signaling type: For SM, either the network signaling or user signaling can be used,
but the end peer connected with it should not be the same (if the peer equipment is a
router or an access server, the local PRA should be at the network side). For SPM,
only the network signaling can be used. For V5PRA, also the network signaling
should be used.
(6) Trunk group service control software parameter: As for the item of tone sending by
the router, it will be used only when the peer equipment is CISCO router and the user
requires this item (at present, only China Netcom uses this item. If this item is to be
used, please consult with relevant personnel in the R&D Department).
(7) For other parameters, please use default values.
3.11 Adding PRA Trunk Circuit

Role: Defining PRA trunk circuit
Command position: Office data configuration/trunk route/trunk circuit PRA trunk circuit
Command: ADD PRATKC: MN=1, TG=10, SC=320, EC=383, CS=USE;
Add PRA trunk circuit
Module number: 1
Trunk group number: 10
Start circuit number: 320 (corresponding to PRA circuit board on site)
End circuit number: 383
Trunk circuit status: Available
During data setting this time, only the PRA data setting of one module is made. Other
data setting methods are the same as the above-mentioned.

Chapter 4 Fault Handling

PRA faults can be divided into three types: PRA trunk circuit fault (belong to hardware
fault), PRA signaling link fault and PRA signaling cooperation fault.
4.1 PRA Trunk Circuit Fault

1. Fault description
Query PRA trunk circuit and the system shows the following abnormal state:
Fault: This board has already been configured as PRA, but the board is not inserted
or the board has failed or E1 line is not inserted or wrongly inserted. This state means
that this port is not physically synchronized or the port does not work normally.
Blocked: The port including this circuit is blocked or this circuit is been manually
blocked.
Not activated: It indicates that the board has been configured or the E1 of the E16
has been added, but the board is not activated.
Busy semi-permanent: It indicates that semi-permanent connection has been
configured for this circuit.
2. Possible fault cause
Serial No. Fault cause Remarks
1 Transmission interruption, bit error
2 E1 line is not connected or wrongly connected It may lead to exceptions such as circuit “fault”.
3 Trunk boards such as E16, STU and DTM fail
4 The circuit is blocked. The port including this circuit is blocked or this circuit
is been manually blocked. For PRA, there is no such
saying as local blocking or peer blocking. It just refers
5 The port is blocked. to the blocking of the circuit of the local office. The
abnormal “blocking” may occur.
The DTM board is configured but is not
6
activated.
Probably the circuit is not activated.
E1 of the E16 board is added, but the board is
7
not activated.
The semi-permanent connection has been Probably the “semi-permanent busy” state has l
8
configured for this circuit. occurred to the circuit.
3. Fault location
Query of PRA circuit:
For PRA circuit query, if the DTM board is concerned, just right click to query. For E16
board, we can only use the command of DSP N1C (this command is also used for the
DTM board): MN=3, CDT=BSN, BDID=PRA, BSN=352&&383. Enter the
corresponding Module Number (MN). Select channel number for CDT code type,
select PRA for BDID channel type and enter the corresponding circuit number for
BSN channel number. Conduct the following location according to the query result:
(1) Circuit “fault” location

Please judge according to the following sequence:

In the navigation tree of C & C 08 commands in the Maintenance Console, select
[Equipment Management/Board Management/Query Board Status] or directly enter
the command of DSP BRD and enter the corresponding module number, frame
number and slot number in the auxiliary command entry window, and then press
<F9> to query the status of the board.
Check whether the E1 line is connected correctly and whether the “receiving” and
“transmitting” lines are connected correctly.
Observe the panel indicators of the boards such as E16, STU and DTM and judge
whether the PCM system generates the alarms such as out-of-frame and slip code.
Enter the E1 channel query command of DSP E1CH and enter the corresponding
module number, frame number and slot number in the auxiliary command entry
window, and then press <F9> to run this query command, and then judge whether the
PCM system generates the alarms such as out-of-frame and slip code according to
the returned results of the system.
If the fault cause is very complicated and cannot be located by the above method,
please adopt the trunk loopback segment-by-segment to locate the fault scope
gradually. The loopback method can be divided into hardware loopback and software
loopback and the loopback direction includes local loopback and remote loopback.
For the specific operation method, please select according to the actual situations
and no detailed discussion will be made here.
(2) Circuit “blocking” location
This state must be caused by manual blocking of the circuit and port. Just use the
command of UBL N1C to open the circuit. After being activated, the circuit “fault”
occurs, please make fault location according to the method in Step (1).
(3) Fault location for “not activated” circuit
Use the command of MNT BRD to activate the corresponding DTM board or E16
board. After being activated, if circuit “fault” occurs, locate the according to the
method in Step (1).
(4) Fault location for “semi-permanent busy” circuit
Check semi-permanent data: Whether this circuit has been configured with
semi-permanent connection. Check whether the service needs the semi-permanent
connection. If not, just delete the semi-permanent data.
4. Maintenance recommendation
Check whether the alarm system generates the following alarms: “Fault: DTM digital
trunk PCM fault and “event: E16 E1 out-of-frame”. To understand the alarm
information of the system in time is the effective means to know the running state of
the trunk system.
4.2 PRA Signaling Link Fault (PRA Trunk)

Link interruption: At the beginning the link works normally, but the link is interrupted
due to other reasons.

Link not established: After the link data is added, the link cannot be established
normally.
2. Possible fault cause
Serial No. Fault cause Remarks
1 Transmission fault Link interruption due to transmission interruption
Fault of trunk boards such as E16, STU and
2
DTM
Fault of protocol processing boards such as It will possibly lead to link interruption and link
3
CPC, NO7 and LPN7 establishment failure.
Fault of boards such as SNU, QSI, MHI and
4
BNET
5 The CPC board is not activated after it is added
The E16 board is not activated after the E1 is
6
added.
It will possibly lead to link establishment failure.
The LPRA board is not activated after it is
7
added.
8 The DTM board is not activated after it is added.
If both sides of the link are not configured as “User”
at one side and “Network” at the other side, the link
9 Improper data configuration establishment may fail. The SPM only supports
“Network”, and improper data configuration may
lead to link establishment failure.
3. Fault location
PRA link state view method:
For SM, right click the LPRA board in the hardware configuration state panel to view
the link state or right click the PRA board and select “Attributes” to check whether the
link is activated.
For SPM, right click the CPC board and view “Attributes” to check whether the service
is normal.
Fault location upon “link establishment failure”:
Please locate the fault according to the following sequence:
Check whether the CPC, LPRA, PRA and E16 boards work normally.
First, check whether the CPC, LPRA, PRA and E16 boards work normally. View the
hardware configuration state panel to check whether the boards work normally. We
can also select [Equipment Management/Board Management/Query Board State] in
the C&C08 command navigation tree in the Maintenance Console or directly enter the
command of DSP BRD, the corresponding module number, frame number and slot
number in the auxiliary command entry window and press the <F9> key to run the
command to query whether the board fails.
Check of CPC board:
For this board, we can conduct CPC link self-loop test (STR LNKTST: FN=20, SN=13,
LN=0) and then judge according to the result. If the following prompt appears: “Fault
occurs to the segment between the CPC and MHI operation recommendations:
1. Please check whether the HW line from the MHI to the CPC board is connected
correctly. 2. Please check whether the HW configuration of the CPC board is correct”.
In this case, check the HW from the CPC to the MHI, the HW could be wrongly
configured or the physical connection faulty . If the following prompt appears: “Fault
occurs to the segment between the CNET and E16/STU/ATU Operation

recommendations: 1. Please check whether the fiber connection between the QSI
board of the frame where the E16/STU/ATU board is located and the CNET board is
normal; 2. Please check whether the working mode of the corresponding E1 is normal;
3. Check the DIP switches on the E16/STU/ATU board; 4. Check the QSL board of
the interface frame where the E16/STU/ATU board is located and the backplane”. In
this case, generally faults might occur between the E1 physical line of the E16
board and the end peer. Please check the physical connection to see whether the
receiving and transmitting lines are connected correctly.
In addition, please activate this board after it is added.
Checking the LPRA board:
Firstly, check whether the working state of the LPRA board in the Hardware
configuration status panel is normal. If it is not normal, please check whether the
board configuration is correct and whether the board type is CBxxLAP7 or
CBxxLAPA7. Please activate the board after it is added.
Check of the PRA:
Check whether the board works normally. Check whether the front LOS indicator of
the port is “Off” and whether other indicators are “On” (such as remote alarm
indicator). The board is in normal state only when all indicators of the port are off. In
this case, the circuit state is idle. If it is not idle, please refer to the location method of
PRA circuit state fault. Please activate the board after it is added.
Checking the E16 board: We can use the command of displaying the state of all E1
ports (DSP E1CH: F=4, SN=18). Check whether the E1 ports are normal. If not,
please refer to the location method of PRA circuit fault. We can also use the
command of DSP N1C to check whether the circuit is idle. Do not forget to activate
the E16 board after adding SPME1.
Check whether both ends are configured as “Network” at one side and “User” at the
other end (whether they are configured correctly). Please note that SPM can only be
configured as “Network”.
Check whether the data at the end peer is correct. Whether one end of the end peer
is configured as “Network” and the other end is configured as “User” during
interconnection with our equipment. If a PBX is used at the end peer, usually it only
supports “User” and also the gateway also serves as “User” only.
If the above steps are correct, but the link is still not established correctly, try to reset
the E1 ports (RST E1) or reset the DTM board. If the link is still not established, the
fault could be complicated, please contact with the R & D Department.
Location of “link interruption” fault:
“link interruption” means: the link has been working normally but suddenly it
enters into faulty state. Usually it is caused by transmission fault. If only the port
recovers, the link will recover automatically. However, occasionally the fault cannot be
recovered due to the cooperation fault of both ends. Please first check whether the
port has recovered. For the detailed method, refer to the location method of PRA
circuit fault. After the port is recovered, if the link is not recovered yet, please reset the
E1 port or DTM board.
4. Maintenance recommendations
Check whether the alarm system generates the following alarms: “Fault: DTM digital
trunk PCM fault and “event: E16 E1 out-of-frame”. Link interruption will occur if these

two types of alarms exceed 6 seconds. To understand the alarm information of the
system in time is the effective means to know the run state of the trunk system.
4.3 PRA Signaling Cooperation Fault (PRA Trunk)

For the signaling fault handling, please first collect the port signaling trace file of the
PRA. Open “C&C08 Service Maintenance System”——>Open “Maintenance”
——>Open “Trace”——>Open “Port Signaling Trace”.
Where: Select PRA for the “Signaling Type”, select whether to save or not at the lower
left corner and enter the port number corresponding to the PRA.
The common PRA signaling cooperation faults are as follows:
Faults related to the calling number (including whether the calling number is included,
whose calling number is included and whether the calling number includes the area
code).
Whether the called number includes the area code
Number sending in whole group.
The called number cannot send the ringback tone.
Incoming/outgoing call authority and charging fault of PRA
How many PCMs do one PRA link control?
2. Fault analysis and solution
Faults Related to the Calling Number:
(1) Whether the calling number is included
During an outgoing PRA call, the calling number will be sent onlyafter the CLIP
service of the default number corresponding to the trunk group has been activated ,
otherwise the calling number will not be sent.
For incoming PRA calls, all the calling numbers will be sent to the CCB.
(2) Including the real calling number or default calling number
During a PRA incoming call, the system will judge whether to send the real calling
number or the default calling number according to the network check ID on the PRA
link.
The description of the network check ID (it only functions for incoming calls) is as
follows:
Network Check whether the sent calling Calling number sent Check which subscriber data
check ID number is legal. to the CCB (authority, charging, etc.)
Check the data sending the calling
Yes The calling number is legal. Sent calling number
number
Check the subscriber data of the
Yes The calling number is illegal. Default calling number
default calling number
Yes The calling number is not sent. Default calling number
No No check will be conducted. Sent calling number

The so-called “legal” means:

“If the calling number sent by the end peer is not a PRA subscriber number, it is illegal,
otherwise, we can obtain the route selection code (CODE_1) of this number in the
PRA subscriber data table. Use the default calling number of the first trunk group
controlled by this signaling link to conduct subscriber number analysis and we can
obtain another route selection code (CODE_2). If CODE_1=CODE_2, this calling
number is “Legal/valid” and this trunk group serves as the routing trunk group. If
CODE1! =CODE2, select the default calling number of the second trunk group
controlled by this signaling link to conduct subscriber number analysis, so as to obtain
CODE_2. Please conduct the same processing as the above-mentioned. If all trunk
groups controlled by this signaling link (one PRA signaling link controls a maximum of
five trunk groups) do not meet the conditions, then the calling number is illegal”.
In addition, when the network check ID is set as “No”, only national numbers will be
transmitted to the CCB transparently. To transmit all/ the calling numbers
transparently, set the network check ID as “No” and also set the internal parameter:
3-BIT10 of CCB as “0”. When the network check ID of the PRA signaling link is set as
“Yes”, the internal parameter of 3-BIT10 of CCB does not function).
(3) Whether the calling number includes the area code
For an incoming PRA call, according to the software parameters, if BIT3 of internal
call parameter 3 is set as “1”, the calling number sent to the CCB will include the area
code; if it is set as “0”, no change will happen.
When the PRA outgoing is set as “Local office” or “local, if BIT8 of call test parameter
3 is set as “1”, the sent calling number will include the area code; if it is set as “O”, no
change will happen.
4.3.1 Whether the Called Number Includes the Area Code:
For the default number of the PRA trunk, if there is not DDI service and the called
number includes the area code, the call connection may fail. Therefore, please set the
DDI new service of the default number of the PRA trunk group.
Number sending in whole group:
This function is applicable to the case in which the gateway interconnected with the
C&C08 switch does not support overlapped sending. After all the called numbers sent
by the CCB are received, the called numbers are sent to the end peer at a time.
Application of the function (targeting at 5004 and 5008): Modify the software
parameter (call test parameter 3: BIT6) as “0”, and the function can be used. (In
addition, this problem can be solved, by applying the following patches: 5004
and 5008).
Precautions on the application of this function:
With respect to this function, a called number will be sent out only after the called
number is received completely or the timer is timeout. However, the number
completeness judgment is based on whether the number has reached the maximum
number length. Therefore, the prefix method will affect the connection time. It is
recommendable to ensure that the maximum number length is consistent with the
actual number length so, it will not affect the call connection time, otherwise there
will be a 5-second delay if the actual number length is less than the maximum
number length. Therefore, cancel the whole group sending function of the PRA
unless necessary (this function will not be used by default).

4.3.2 The Called Number Cannot Send the Ringback Tone:
To remove this fault, modify the software parameter (the call internal parameter 3:
BIT11) as “0” for the calling number to send the ringback tone.
4.3.3 Incoming/Outgoing Call Authority and Charging of PRA:
The incoming/outgoing call authority of the PRA is implemented via the

incoming/outgoing call authority of the default number of the PRA trunk group.
Specifically, the incoming call authority of the PRA refers to the outgoing call authority
of the PRA, while the outgoing call authority of the PRA refers to the incoming call
authority of the PRA.
The charging of the PRA trunk group is also implemented via the charging attributes
of the default number of the PRA trunk group.
4.3.4 One PRA Link Controls Multiple PCMs:
The meaning of one PRA link controlling multiple PCMs is that the circuit of a PRA
link is only on one E1 port, but multiple E1s of the local module can share the link. At
present, the maximum number of E1s is 4. For one PRA link to control multiple PCMs,
the circuit number of the interconnected parties should be confirmed. The CIC
identifier is used for SS7 trunk, while B channel number is used as the identifier in the
PRA trunk. However, the B channel number ranges from 1 to 31. To identify B
channels in different PCMs, the concept of PCM interface identifier is defined. As
both parties negotiate consistent interface identifier, the interface identifier and B
channel number are transferred to the peer party via the SETUP signaling. Thus, a
unique circuit can be identified.. The interface identifier is added to the PCM physical
attribute data (ADD PCMATR). The equipment number in this command refers to the
circuit number of Timeslot 0 of the PRA, and the signaling link number is consistent
with that in the PRA signaling link table. The interface identifier is the conventional
value of the interconnected parties, so the interface identifiers of both parties are the
same. CRC4 is not supported for the time being, so it should be set as “No”. The
specific principles are as follows:
A. For the PRA trunk routing, a PRA includes a maximum of five trunk groups and
each trunk group includes a maximum of one PCM or partial circuits in one PCM, but
a PRA link manages a maximum of four PCMs.
B. In the PRA signaling link table, “locate” the signaling link to Timeslot 16 of one
PCM.
C. Add PCM physical attributes and use the interface identifier to identify each PCM
(the interconnected parties should have the same identifier).
Note:
It is not safe for one PRA link to control multiple PCMs. If one PRA side is configured with the PCM data
while the other side is not configured with the data or the interface identifiers of the two sides are not
consistent, the call connection will fail. If the PCM where link is located is interrupted, the whole office
will be blocked. Furthermore, in actual application, the interconnected party (data product) always can
guarantee that each PCM provides a PRA link. In addition, not all switches (data products) support
interface identifier. Therefore, please do not use this function unless necessary
4. Maintenance recommendation

Refer to the above-mentioned fault analysis and solution.

Chapter 5 Network Fault Cases of PRA

1. [Fault Description]
Why does the PRA link establishment fail?
The possible causes are as follows:
(1) E1 physical line fault leads to link establishment failure. Check whether there is
any E1 equipment fault alarm. Sometimes the E1 equipment state is normal, but
actually the male and female connectors of the two PCM lines are connected
inversely.
(2) Check whether the signaling board is LPRA board (normally its number is 7).
Sometimes a LAP board of other type is wrongly inserted into the slot of the LPRA
board, the link indicator also can “locate” the board. However, this is only a
misleading appearance. Check the link state and you will find that it is not activated.
(3) Whether the software of the LAP board is correct.
(4) Whether one end of the PRA link is set as “User” and the other end is set as
“Network”.
(5) While configuring SM or SPM module PRA boards ( LPRA and CPC_PRA
respectively), the operator only adds the equipment, but does not execute the
activation command, leading to a faulty port state.
The call cannot be connected. The called ISDN network does not send the “SETUP”
message to the called PRA subscriber and the calling party hears the prompt tone of
“no available circuit”
The main reason is that the dynamic table of the PRA link is not updated on time.
Since some dynamic tables related to the trunk of Version 5004 have the function of
delayed refresh, it affects the online setting of the PRA link table. Thus, the contents
of the PRA link dynamic table are not correct so that the call cannot be connected
when the PRA number serves as either the calling number or the called parties. If the
PRA link has been configured and established, but the call cannot be connected, the
customer service personnel can use the command of MOD PRALNK to fill in an
existing PRA link number at will and set it on line.
Another reason is that the route number of the PRA trunk is inconsistent with the
route selection code of the default number, so as to result in circuit selection error.
The call cannot be connected. The called ISDN network has sent the “SETUP”
message to the called PRA subscriber, but the called PRA subscriber does not
respond.
The main reason is that at present the operator uses the method of one link
controlling one PCM, but one piece of record of the PRA PCM physical attribute table
is added by mistake. Thus, the communication protocols between the network and
the user are not consistent. The information unit of CHANNEL IDENTIFICATION from
the network to the user includes an extra interface ID byte and the user releases the
message. The release reason is “invalid information unit”. The solution is to delete the

PRA circuit first, delete the PRA PCM physical attribute record and finally to add the
PRA circuit.
Another reason is that the called number from the PRA network to the PRA
subscriber includes the area code, so the called subscriber cannot be identified. The
solution is to add the DDI authority to the default subscriber of the PRA port.
If the PRA subscriber serves as the calling party, it hears the prompt of “No available
circuit” when it hooks off and dials the called number.
The main reason for the hook-off fault of the calling party is that the link table is not
refreshed dynamically. If the PRA link has been configured and established, but the
call cannot be connected, the customer service personnel can use the command of
MOD PRALNK to fill in an existing PRA link number at will and set it on line.
When the calling party dials the called party, it hears the prompt that “the number you
dialed has been changed”.
The PRA default number is only valid for the local module. Other modules need their
own default numbers. The inter-module implementation is impossible, that is to say,
the module number added during PRA trunk group configuration should be consistent
with that corresponding to the default PRA number, otherwise the call cannot be
connected and the system will prompt that the number you dialed has been changed
or this number is not available. (This is its difference from C&C08 switch. Please pay
attention during the upgrading of 128-SM switch).
The main reason is that the operator has configured the CLIP mode in the PRA trunk
group table as “trunk line ID” (actually it should be configured as “Default Number”.
Another reason is that the default number in the PRA trunk group is a false number or
the trunk group and the default PRA number are not in the same module or the
number does not exist at all.
During the test before deployment in Shanghai, we found the following fault led to call
connection failure!
(1) Networking environment:
05I SSP (SSP switch in local intelligent network of Version 20000803 pack) + Huawei
IPPhone gateway: Two gateways are used and only one switch is used. The two PRA
systems of one DTM board of the switch respectively serve as the outgoing trunk and
incoming trunk.
(2) Phenomenon
The call connection is normal between the calling switch and gateway, but the
following phenomena occur to the outgoing call from the called gateway to the switch:
U->>N SETUP
N->>C SETUP
C-) N CallProcceding
N->>U CallProcceding
C->>N Release Complete, Cause: CV_UNKOWN
N->>U DISCONNECT, Cause: CV_NORMAL

[Case Analysis]
The cause value of CCB disconnection of the call (ppr_992.012, Port 992) with the
called number of 19000004 (local office) is 68, but program does not show
“CV_UNKNOW” but shows “there is no inter-module path (CV_NO_IPATH)”. We
doubt that the office data configuration is not correct. However, for the call (Port 960)
with the called number of 2119000004 (local), the called number in the incoming call
is sent completely, but after the CCB sends the SETUP_ACK message to the network,
it does not return any message to the network. After eight seconds, the calling line is
cleared. Later, the reason is located: Module 12 (a new module without being put into
service) is not configured with proper route to the AM/CM module. Note: This
phenomenon only occurs to 32-SM switch, since a 128-SM switch does not need the
configuration of route to the AM/CM module.
For the IP service of an office in Shenzhen, the PRA trunk is used for interconnection
with Cisco gateway. It is found that the PRA cannot send the calling number to the
end peer. The user complained that the “CLIP/identification override” authority of the
PRA subscriber had been modified in the background, but it still did not work. Later
the LPRA reported the link disconnection message.
[Case Analysis]
After the analysis of the PRA port signaling, it is found that the “CLIP/identification
override” authority of the PRA subscriber is not set successfully, because the number
initial set of the PRA subscriber number is 1, not 0. However, when executing the
command of MOD PRA, the user does not specify the number initial set (default value:
0). For the link disconnection fault, since there is no PCM alarm, it indicates that the
Physical Layer is normal. At present, PT500 is still being used to monitor L2
messages so as to record the possible link disconnections at any moment.
8. Voice delay occurs to the dialing of 17930 over S1240 via the IP front-end
processor in an Office in Beijing
[Fault Description]:
The S1240 is interconnected with the front-end processor via TUP (17930 is a
CISCO gateway). The dialing of 17930 over the S1240 is forwarded to the gateway
via the front-end processor, but there is a 5-second delay between receiving the IAI
message from the S1240 and returning the ACM message. Tracing the PRI signaling,
it is found that there is not a long duration from the SETUP (first C to N) to the
connection establishment (CONNECT) for messages over the gateway. Therefore,
the 5-second delay should come from the CCB processing. So, the problem is:
Why there is such a delay?. Similarly, 171 calls from the S1240 can be connected
rapidly. Comparing the messages, we find there is no difference. With respect to data,
there is also no special features , the messages are just sent to different ports.
Both, the maximum and minimum number lengths of “171” are 3 digits, and both, the
maximum and minimum number lengths of 17930 are 5 digits. Both of them are local
basic services, as well as other related supplementary signaling and number
initial processing modes are the same. At present bit5 of call test parameter 3 is
modified as “0”, since the gateway does not support variable-length number receiving.
When dialing 17931 + Toll area code + Phone number, the called number is sent to
the gateway at a time after timeout. Still , I do not think there is any conflict, since
17930 is of equal length. As for message tracing, since one bit is not set correctly
after the peer party sends the IAI message over one link, it leads to the
retransmission of GRQ. However, the GRQ retransmission time is later than IAI

message by five seconds. Therefore, this GRQ sending and GSM returning process
can be neglected.
[Case Analysis]:
Carefully check the called analysis table, it is found that there is and additional
prefix corresponding to 17930000 besides the prefix of 17930. The maximum
matching mode is adopted for the called analysis table of our switch. After receiving
the 17930 prefix, when the table finds that there are two pieces of records which can
match the table, it will continue the waiting and will match the prefix of 17930 only
after number sending timeout (five seconds). Consult with the customer service
personnel, and the prefix of 1793000 is useless. Ask the customer service personnel
to delete the prefix, and the fault was removed at last.
9. Fault of an office in Meizhou (Guangdong province)
[Fault Description]:
Question 1: A local subscriber of the IP front-end processor in an office in Meizhou
conducts one-stage call (17911). After hearing the ringback tone, if the peer
subscriber does not hook off, the connection will be cleared after 18 seconds. Tracing
the PRA port signaling, it is found that the switch firstly clears the connection. The
disconnection reason is: “normal call disconnection”. The contents of the signaling
tracing part are as follows: Note: 90 indicate normal call disconnection ...... Do not
trigger the intelligent service, configure a prefix to establish the call connection
directly via the gateway, this fault does not exist any more. Please help to analyze
and locate the fault.
Question 2: The gateway is interconnected with the PRA of a C&C08 switch and the
C&C08 switch is interconnected with China Telecom equipment via NO1 signaling.
The gateway originates a call to a China Telecom subscriber via the C&C08 switch,
the China Telecom equipment returns A4. The reason of the RELEASE message for
C->N of the PRA is “remote equipment congestion”, but reason of the
DISCONNECT message for N->U is “normal, not specified”. Why are the reasons are
different? What is the message resulting from conversion of SS7 signaling when the
reason of the DISCONNECT message is “normal, not specified”?
[Case Analysis]:
1. This duration complies with national standard. The specific national standard is
as follows: Technical Specifications of China IN Equipment SSP (YDN 047-1997) P32:
"8.7 Monitoring of Long Time No Reply and Forwarding of Busy Signals by SSP:
b...When monitoring the “long time no reply”, after the SSP is connected with the
called subscriber and receives the signal of “called subscriber idle”, the time on no
reply is 18 seconds. After 18 seconds, it will report called subscriber reply to the SCP,
get preparation for receiving an SCP command and connect the call to a new
destination address according to the command. "If it is unnecessary to connect the
call to a new destination address, the SCP will request to disconnect the call directly.
It is recommended that a proper explanation be made to the equipment buyer not to
modify the standard duration. To modify the duration as a value other than the
national standard, please get the written confirmation of the equipment buyer,
otherwise unnecessary conflict or inconsistent understanding may occur in the future.
After getting the written confirmation of the equipment buyer, use the command of
ACT AMDEBUG to set the no reply duration of the intelligent service. The specific
method is as follows: Set the no reply duration as 60 seconds, enter “Module number
0xff 0x1f 0x3C", 0x3C stands for no reply duration in hexadecimal notation with the
unit of second. It can also be set as other durations.

2. Cause analysis: The reason for C->N RELEASE message is “Remote

equipment congestion”. This cause value is not a value specified in the protocol, but a
cause value internally defined. Therefore, when it arrives at the ISDN, it is modified as
the cause value of “normal, not specified” which the protocol can identify and as CFL
when being converted into SS7.
10. Number sending delay of the IP front-end processor in a data office in Guangdong
province (C&C08B switch)
[Fault Description]
Tracing the PRA signaling of the IP front-end processor in a data office in Guangdong
province, it is found that during one call the C->N SETUP signaling is sent two times
and the N->U SETUP signaling is sent for one times. The specific contents are as
follows: Networking mode: 130GSM---->CC08---->3COM gateway A 130GSM
subscriber dials 17911 and the call is routed via the IP front-end processor. The
signaling sent from the IP front-end processor to the 3COM gateway: C->N SETUP
N->C SETUP_ACK N<>N ERROR_STATE N<>N CR_TIME_OUT N<>N
CALL_PRESENT N<-C SETUP N->C SETUP_ACK N<>N CALL_PRESENT U<-N
SETUP U->N CALL_PROCEEDING N->C CALL_PROCEEDING... Where, the C->N
SETUP signaling is sent two times. Only the number type is inconsistent every
time the signaling is sent twice: The number in the signaling sent for the first time is a
national number, while that for the second time is a subscriber number. The interval
between the signaling sent for two times is five seconds so that the connection time is
delayed. In addition, the re-analysis of this call is conducted during the number
initial processing. We do not know whether it is related to the sending of the C->N
SETUP signaling for two times. If it is, why is the interval 5 seconds; if it is not, what
are the reason and solution?
[Case Analysis]:
The reason is that the function of “delay called number sending in whole group of
PRA” of the front-end processor has been opened (since the peer gateway needs
complete number transmission). Timeout occurs five seconds after the PRA receives
the last number, the system assumes that the number receiving is completed and
simulates the CC to resend the called number. Adjust the duration of the timer to be a
bit shorter, such as 1 second. The specific method is as follows:
a) Use the command of MOD SFP to modify BIT5 of “call test parameter 3” as "0". (If
this software parameter is set as “0”, it indicates the function of “delay called number
sending in whole group of PRA” has been opened.)
b) Duration adjustment: Use the command of ACT AMDEBUG to modify the number
receiving timeout duration. Fill in the following parameters in turn: Module number,
0x16 (PRA process number), 0xab, 0xa5, 0x5a, 0x41 (65 in decimal
notation—designating timeout name), 0x04, duration (two lower bits), duration (two
higher bits). Where, for the duration (Unit: second), we should use the hexadecimal
notation to represent the numerical values in decimal notation, for example, use
"0x20" (two lower bits) and "0x01" (two higher bits) to represent the duration of “120
seconds” in decimal notation. It is set as five seconds by default.
11. Shanghai Netcom
[Fault Description]: Handle the fault that some IP calls in Beijing could not be
connected. Tracing the signaling of a call, it was found that the call was disconnected
at the local end. Through careful check, it was found that the calling number sent by
this call was 17910000 and there was also such a subscriber in Shanghai, and
furthermore, the PRA number corresponding to the selected trunk group was also

17910000 and the data configured in the PRALNK was as follows: The network check
ID was set as 1.
[Case Analysis]: Modify the PRA subscriber number at the local end as another one
or let the end peer send a different calling number.
12. Shanghai Netcom
[Fault Description]: Two PRA links could not be established. Checking DSP E1, there
was no out-of-frame or remote alarm and the display was normal. Tracing the
signaling, it was found that the messages from the CISCO gateway was confusing
and also the message tracing on the CISCO access Server showed that the local end
did not return the RR frame
[Case Analysis]: Check the physical connection line of the PCM and check whether
the male and female connectors of the two PCMs are connected correctly.
13 Taiyuan, Shanxi province
[Fault Description]: The peer end of the PRA is connected to a Nortel PBX and the
real calling number cannot be transmitted transparently. In this case, the network
check ID is set as “No”.
[Case Analysis]: Internal CCB parameter 3 (BIT10) = 1: Only when the code number
is “National number” will the transparent transmission be conducted (set in
specifications). In this case, the calling number type from the Nortel PBX is
“Unknown”, so the default PRA number serves as the calling number. Internal CCB
parameter 3 (BIT10) = 0: The transparent transmission will be conducted, regardless
of the number type. Therefore, modify the CCB parameter 3 (BIT10) as 0, the real
calling number can be shown.

Chapter 6 Data Configuration Differences between

Versions
6.1 PRA Data Differences between 32-SM Switch and 128-SM

Switch
1. Command: ADD PRATG
ADD PRATG: TG=1, SRC=1, MN=1, SIGL=1, DI=K'163, SIGT=NET,
SVRCTRL=WAC-1;
Please pay attention to the following points:
(1) Module number: Please note that the module number should be consistent with
that corresponding to the default PRA number, otherwise call disconnection may
occur and the system will prompt that the number you dialed has been changed or
the number is not available. (This is its difference from C&C08B switch (inter-module
application can be applied), so please pay attention during the deployment of the
128-SM switch).
(2) Signaling type: For the SM, either the signaling type of “Network” or “User” is
applicable, but the signaling type at the peer end should be different (for example, if
the peer equipment is a router and access Server, then the PRA signaling type at the
local end should be “Network”). For SPM, the signaling type should only be “Network”
is correct. For V5PRA, the signaling type should also be “Network”.
(3) Trunk group service control software parameter: If the 32-SM switch is configured
with Wide Area CENTREX (WAC) service, please note that the 128-SM switch is not
configured with this service.
2. Command: ADD PRALNK
ADD PRALNK: MN=1, SLN=1, SCN=1, NCF=FALSE;
(1) Signaling link number: For SM: when the LPRA board has a single CPU, there are
four links, (select any one of the front four links of the board). When the LPRA board
has two CPUs, there are eight links (select any one of the front eight links of the
board). For SPM: configure any one of the sixteen links of the board).
(2) If the 32-SM switch is configured with the backup signaling link number and
backup signaling circuit number, please pay attention to the upgrading to 128-SM
switch since the two items are not available.
(3) If the 32-SM switch is configured with the circuit type (including PRA and V5PRA),
please pay attention to the upgrading to 128-SM switch since the item is not available,
i.e., only the PRA can be configured. To configure the V5PRA, please use the
dedicated command of ADD V5PRA.
6.2 1283K Old Versions - 3007SP1, 3008, 4011 and 5001

1. Command: ADD PRATG

There is no module number in 3K old versions, and there is only the network ID. In
the 3007SP1, 3008, 4011 and 5001, the network ID is modified as module number.

Topic On R003 PRA Configuration and Fault-20030122-B

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Topic On R003 PRA Configuration and Fault-20030122-B

Uploaded by

Copyright:

Available Formats

C&C08 Digital SPC

Document code Product name Switching System

Edited by Fixed network technical support department Document version V1.0

Topic on R003 PRA Configuration and

Drafted by: Meng Qingxiao Date: 2002-01-10

Reviewed by: Lvxiaochao Date: 2003-01-22

Reviewed by: Date:

Approved by: Huangyong Date: 2005-03-23

Huawei Technologies Co, Ltd

2002-01-10 V1.0 Draft Meng Qingxiao

Huawei Confidential. No disclosure without permission.

Chapter 1 Introduction to PRA........................................................................................................ 1

Huawei Confidential. No disclosure without permission.

Abbreviations Full spelling

Huawei Confidential. No disclosure without permission.

Chapter 1 Introduction to PRA

1.1 Explanation of PRA Data Concepts

Figure 1-1 PRA structure

2003-01-15 Huawei Confidential. No disclosure without permission. Page 1 of 34

2003-01-15 Huawei Confidential. No disclosure without permission. Page 2 of 34

1.2 PRA Call Flow

2003-01-15 Huawei Confidential. No disclosure without permission. Page 3 of 34

1.3 PRA Data Setting Sequence

2003-01-15 Huawei Confidential. No disclosure without permission. Page 4 of 34

Figure 1-2 PRA data reference relationship

2003-01-15 Huawei Confidential. No disclosure without permission. Page 5 of 34

Chapter 2 PRA Application and Other Precautions

2.1 Inter-module Data Setting of PRA Trunk

2.2 Precautions on the Control of Multiple PCMs by one PRA

2.2.1 Data Setting Method

2.3 How Does the PRA Conduct Number Conversion

2003-01-15 Huawei Confidential. No disclosure without permission. Page 7 of 34

PRALNK to implement the conversion. However, it is recommended that the common

2003-01-15 Huawei Confidential. No disclosure without permission. Page 8 of 34

Chapter 3 PRA Data Configuration

3.1 Adding an Office

3.2 Adding Sub-route

3.3 Adding Routing Table

2003-01-15 Huawei Confidential. No disclosure without permission. Page 9 of 34

Command position: Office data configuration/trunk route/route

3.4 Adding Route Analysis

3.5 Adding a Service Prefix

Route selection code: 10

3.6 Adding a Number Segment

3.7 Adding ISDN Data

3.8 Adding a PRA Subscriber

3.9 Adding a PRA Link

2003-01-15 Huawei Confidential. No disclosure without permission. Page 12 of 34

(1) Module number: Fill in according to the actual situations.

3.10 Adding PRA Trunk Group

2003-01-15 Huawei Confidential. No disclosure without permission. Page 13 of 34

3.11 Adding PRA Trunk Circuit

2003-01-15 Huawei Confidential. No disclosure without permission. Page 14 of 34

Chapter 4 Fault Handling

4.1 PRA Trunk Circuit Fault

2003-01-15 Huawei Confidential. No disclosure without permission. Page 15 of 34

Please judge according to the following sequence:

4.2 PRA Signaling Link Fault (PRA Trunk)

2003-01-15 Huawei Confidential. No disclosure without permission. Page 16 of 34

2003-01-15 Huawei Confidential. No disclosure without permission. Page 17 of 34

2003-01-15 Huawei Confidential. No disclosure without permission. Page 18 of 34

4.3 PRA Signaling Cooperation Fault (PRA Trunk)

2003-01-15 Huawei Confidential. No disclosure without permission. Page 19 of 34