2-15.OSB2A07 Trunk Data

Course Description
Course Overview
This course discusses the setting of inter-office CCS7 (TUP or ISUP) trunk data
and CAS trunk data, as well as the related maintenance methods.
Course Objectives
After the course is completed, the trainees should be able to
 Understand the setting of CCS7 (TUP or ISUP) trunk data
 Understand the data setting of CAS trunk data
 Use the related maintenance methods

Course OSB2A07 CCS Trunk Data
Issue 1.0 R3V610R003
Section
1 Overview
 Key Points
1. The related hardware
2. The concepts of route, subroute,, office direction, adjacent SP, non-

adjacent SP, route selection source code, and route selection code.
3. The related commands.
Besides correct data setting, the precondition for successful inter-office call
connection also includes the provision of necessary hardware.
1.1 The Related Hardware
The related hardware for trunk data setting includes: the connection between digital
trunk boards from different offices, config data setting of DTF board, as well as the
related signaling boards ( NO7, LPN7, MFC) and their config data setting.
 The connection between digital trunk boards (DTF) from different

offices
 Each DTF board has 2 PCM systems, providing totally 64 circuits.
 E1 trunk cables in use could be classified into two kinds according to their
resistance, namely, 75 and 120, where the 75 co-axial cable is more commonly
used.
 Connection of 75 ƒ¶coaxial cables: There are altogether 64 radio frequency

sockets installed in the trunk motherboard. Every four correspond to one DTF board,
and every two (receiving and transmitting) constitute a system.
OSB2A07-2
Figure 1-1 Sketch map of the connection of 75 ƒ¶ trunk cables
As shown in Figure 1-1, the sending (transmitting) terminal of the radio frequency
head, TXn, and the receiving terminal, RXn, are connected respectively to the
receiving terminal RXm and sending terminal TXm of the remote office via 75 ƒ¶
coaxial cables. Among them, m, n=1~32, TX0 and RX0 correspond to the first system
of the first trunk board, TX1 and RX1 correspond to the second system of the first
trunk board, and so on, TX30 and RX30 correspond to the first system of the
sixteenth trunk board, and TX31 and RX31 correspond to the second system of the
sixteenth trunk board.
 Tips
After the trunk cables are properly connected, the indicator lights of the related PCM
system on both of the DTF boards will all turn off.
Config Data Setting of DTF board
 According to the different signaling system employed and the different user
part of CCS7 used. DTF board could be described as different card types: TUP for
CCS7's telephone user part, ISUP for CCS7's ISDN user part, and DTF for CAS
signaling, etc.
Related signaling boards ( NO7, LPN7, MFC) and their config data
setting
 For CAS signaling, MFC board is needed; for CCS7 TUP signaling, NO7 or
LPN7 board is needed; and for CCS7 ISUP signaling, LPN7 board is needed.
 NO7, MEM, LAP (LPN7, LPV5, LPRA, LPHI) and MFC boards are
uniformly numbered. The card numbers are assigned according to the slot numbers.
(The relation between the card number and the slot number is described in Fig. 1-2.)
OSB2A07-3
 When
the NO7 board
is inserted
where the slot
number is even
(i.e. slot
number 18 and
20), then in the
HW
description
table board number CCS7 link number
the•ystart
timeslot•z for
its HW group should be 16. But LPN7 board does not have such demands.
 Each NO7 board supports 2 links, each LPN7 board supports 4 links, and each
signaling board slot supports 4 links. The link numbers of the CCS7 signaling boards
are defined according to the board number, and , therefore, are also related to the slot
number. Their relations are described in Fig. 1-2. And when NO7 board is plugged in,
only the first two link numbers are valid, the next two are left unused.
B B
0 1 2 3 4
N N
P N N N N N N E M 1 1 M M P
W O O O O O O M P 4 8 2 6 C C W
E E
C D D D D D D A U | | | | 2 2 C
1 1 1
T T
7 1 5 9
5 6 7 8 9
P N N N N N S S M 2 2 3 3 O O P
W O O O O O I I P 4 8 2 6 P P W
C D D D D D G G U | | | | T T C
2 3 3 3
7 1 5 9
OSB2A07-4
Fig. 1-2 The relation of the signaling boards' card numbers, CCS7 link numbers and slot numbers
 Tips
Indicator lights on the signaling boards
A NO7 board provides 3 indicator lights for each of its links. When a link has been
successfully aligned, the three indicator lights related to this link will all turn on; and
when the link is still on the stage of having been initialized, only the first indicator
light will be on, while the other two remain off.
LPN7 provides only one indicator light for each of its links. Which, when turns on,
represents the link is aligned; when flashes, means the link is in the process of
alignment; and when turns off, means the link is not aligned.
MFC board provides 16 indicator lights each representing a signaling channel, the
light will turn on when the signaling channel it represents is seized.
1.2 Related Concepts
The concepts involved in trunk data include route, subroute, trunk group. and for N07
signaling system, we have extra concepts such as office direction, adjacent SP, non-
adjacent SP, route selection source code, and route selection code.
666 888
2# sub-route
3# sub-route
222 777
999
1# sub-route
555
Fig. 1-3 An example of inter-office networking
OSB2A07-5
We will use figure 1-3 to explain the related concepts. Fig.1-3 is a example of inter-
office networking, where the solid line represents the voice path and the dotted line
represents the signaling link path. As we could see, the local office 222 has direct
voice and signaling path connected with offices 555 and 666, and office 555 has
direct voice and signaling connection with offices 999. Office 777 is a STP (Signaling
transfer point), office 222 has direct voice path connected with 888, while the
signaling link between 222 and 888 is transferred by 777.
1.2.1 Office Direction, Adjacent SP and Non-

adjacent SP
When a switch office is directly connected to the local office through voice path using
No7 signaling, it is regarded as an office direction of the local office. All office
directions of a switch office are uniformly numbered, and the numbers assigned are
called the office direction numbers.
In the CCS7 signaling network where the local signaling point (SP) locates, all the
SPs that have either direct signaling paths or direct voice paths connected with the
local SP are the destination signaling points (DSPs) of the local SP. The DSPs can be
grouped into two types, namely, adjacent SPs and non-adjacent SPs, where the former
have direct signaling paths linked with the local SP while the latter only have direct
voice paths and no direct signaling paths linked with the local SP.
Now let's try to find out the office directions, adjacent SPs and non-adjacent SPs of
the local office 222 in the example. From Fig.1-3 we could see that the office
directions of the office 222 include office 555, 666 and 888, and they are given office
direction numbers 1, 2, and 3 respectively; adjacent SPs include office 555, 666 and
777; non-adjacent SP is office 888. As for office 999, voice and signaling between it
and 222 could be transferred by office 555, so in office 222 we do not need to set
voice and signaling data for office 999, all we have to do is define the prefix 999 in
the called number analysis table and assign it with the same attributes as that of
prefix 555.
OSB2A07-6
1.2.2 Route and subroute
If office A has a direct voice path towards office B(regardless of the signaling
systems used), then we say that A has a subroute towards B. And if the local
office has multiple direct voice paths going to different offices, then the local office
have multiple subroutes, and each of them will be assigned with a unique subroute
number.
From this definition we could conclude that when CCS7 signaling is adopted, each
office direction bears a subroute number.
In C&C08 Digital Switching System the concept of subroute is similar to the common
concept of route, which could be classified as direct subroute, bypass subroute and
backbone subroute.
In Fig. 1-3, there is a direct voice path between office 222 and 555, so office 222 has
a subroute towards 555, and in the figure we have assigned this subroute with a
subroute number, 1.
If office 555 has a subroute towards office 666, then office 222 has two subroutes
connecting with 555, one (subroute 1) is directly linked, the other (subroute 2) is
transferred by 666. Both of the two subroutes 1 and 2 could all be grouped into the
route from 222 to 555.
Route: the collection of all subroutes which could go to the appointed office, be the
office an adjacent SP or a non-adjacent SP. The routes going to different offices are
assigned with, and are also represented by different route numbers.
 Attention
1. All routes are uniformly numbered, and so are the subroutes and office directions.
What's more, route number 0 is usually used by intra-office multi-module networking.
2. Subroute is unidirectional, always starting from the local office.
OSB2A07-7
From the above description we could judge that one route can correspond to several
subroutes (5 at most), and one subroute may belong to multiple routes as long as it is
involved in the path towards the specific office.
1.2.3 Route Selection Source Code and Route

Selection Code.
Route selection source code•Fdistinguishes the route strategy from the call source
code point of view.
Route selection code•Fdistinguishes the route strategy from the called prefix point of
view.
Since route selection source code corresponds to call source code, when we need
different route strategy for some local office subscribers, we should give them a
special call source code, then we could give them a special route selection source
code as well.
As for route selection code, it corresponds to called number or prefix, so different

called number could demand different route strategy. In practice, the route selection
code should be assigned according to the networking condition. Table 1-1 shows the
route selection codes, route numbers, and subroute numbers for the networking
illustrated in Fig. 1-3, in which the route selection code for prefix 999 could be
identical with that of prefix 555, since the calls from office 222 to 999 are transferred
by 555.
OSB2A07-8
Table 1-1 The distribution of route selection codes, route numbers, and subroute numbers for the
networking illustrated in Fig. 1-3
Call Route route
source selection Called selection Other Route subroute
code source code prefix codes attributes number number
0 0 555 1 ........... 1 1
0 0 666 2 ........... 2 2
0 0 888 3 ........... 3 3
0 0 999 1 ........... 1 1
1.3 Classification of the Commands
The setting of trunk data involves a lot of commands. For the sake of easy
explanation, we wildivide the commands into different categories and explain them
respectively.
1.3.1 Commonly Used Commands
If CCS7 signaling system is employed, when handling an outgoing call, the switch
will first seize a proper voice channel (i.e. a trunk circuit) for it, then choose a
signaling link. So CCS7 trunk data can be further divided into 2 parts:
 Voice channel data
 Signaling link data
For CAS signaling system, only voice channel data is involved.
1. Voice Channel Data
The voice channel data includes the commands used to define the attributes of the
trunk circuits used for outgoing calls. The sequence of the commands used for setting
up a voice path between the local office and an opposite office are:
1) SET OFI: Set up local office information, defining the local office's type (e.g.
local call/rural call, or toll,urban&rural call, or national toll, or international toll, etc.).
OSB2A07-9
And if the office is to use No.7 signaling, the signaling point code of the local office,
namely the OPC , is also defined here.
2) ADD OFC: Set up the office directions, defining the related attributes of the
opposite office
3) ADD SRT: Set up the subroutes coming to different offices
4) ADD N7/N1TG: Set up the No7 or R2 trunk groups belonging to the subroutes
5) ADD N1TKC/N7TKC: Set up the trunk circuits belonging to the trunk groups
6) ADD RT: Set up the route corresponding to the subroutes
7) ADD RTANA: Set up route analysis, defining the relation between the route and
the caller party, called party, caller category, transmission capability, etc.
Therefore, the setting of voice channel decision is made step by step from choosing a
subroute, to a trunk group, to a trunk circuit and finally to a route, to. A more detailed
description is given below:
1. Before the setting of subroutes, the related office directions have to be defined.
Namely the attributes of the opposite offices, such as opposite office type, opposite
office level, destination signaling point code, etc., have to be defined beforehand.
2. A subroute is composed of trunk groups, which might be distributed in different

modules. Different trunk groups may have different types of circuits, and various line
selecting modes, such as cyclic, minimum and maximum, are available for selecting
trunk groups from a subroute. Multiple trunk circuits of same circuit type can form a
trunk group, and all of them should belong to a same module.
Both CAS trunk data and CCS7 trunk data involve the setting of voice channel. For
CAS trunk data, if no tandem data is involved, only the above procedures have to be
taken. While for CCS7 trunk data, commands used for setting signaling links are also
concerned.
2. Signaling Link Data
 Signaling link data mainly deals with CCS7 signaling links. The commands
setting order should be:
OSB2A07-10
1) SET OFI: Set up local office information, defining the local office's OPC.
2) ADD N7DSP: Set up the MTP destination signaling points (DSPs), defining
the destination signaling points.
3) ADD N7LKS: Set up the MTP linksets, defining the linksets going to adjacent
signaling points, as well as the linkset selection modes adopted.
The linksets to be used are decided by the above two steps.
4) ADD N7RT: Set up MTP route, defining the signaling routes going towards
other signaling points as well as the link selection modes used.
5) ADD N7LNK: Set up MTP link, defining the information about the signaling
links connecting the local office with adjacent offices.
The link to be used for the present call is defined by the above two steps.
1.3.2 Commands not Commonly Used
 ADD N1TDM: Set up tandem information, defining the tandem modes used for
CAS signaling.
 ADD LSND/LRPT/REGSND/REGRPT: Set up CAS signaling conversion.

These commands usually are fed into the switch during exchange deployment stage
by the installation engineers. As the O&M staff, you only have to remember the
correspondence between the line/register signal/command conversion indexes and the
signals.
 ADD TGLD/ADD TGLDIDX: Trunk group load and trunk group load index,
used for outgoing trunk groups to conduct some process such as CLI or CLD number
transformation.
 Some commands concerning analog trunks: Used for defining the attributes of
analog trunk groups. Since analog trunk groups are rarely used now, these commands
will not be introduced in this course.
1.3.3 Other Commands Involved
OSB2A07-11
ADD CALLSRC: Set up call source, defining the route selection source
code.
 ADD TMIDX: Set up time index, defining the time index used for dynamic
routing. Time indexes have default value. When dynamic routing is unnecessary, we
can use the default values.
ADD CNACLD: Set up the call prefix, defining the route selection code.
1.4 Command Query Order
If CCS7 signaling system is employed, when handling an outgoing call, the switch
will first seize a proper voice channel (i.e. a trunk circuit) for it, then choose a
signaling link.
1. Voice Channel Part
The commands in this part is used for selecting a trunk circuit for a specific call. The
decision is made step by step from choosing a route, to choosing a subroute, to a trunk
group, and finally to a trunk circuit.
From the call prefix we could get a route selection, and from the caller's call source
code we could get its route selection source code. These two, together with the class
of the subscriber, the address information indicator and the time, determine the
selection of a route.
The load distribution among trunk circuits is jointly determined by the module
searching queue in the subroute, the group selecting mode preset in the subroute data,
the relative priority level and availability of the trunk group, and the circuit selecting
mode preset in trunk group data. This process is shown in Fig. 1-1.
OSB2A07-12
Route analysis
Route Subroute selection
Trunk module selection
Trunk group selection Circuit selection
Fig. 1-4 Procedure of load distribution among the trunk circuits
In the following is a figure showing the relation between the load distribution
procedure and voice channel data:
Route •]•¨ Route analysis data

•« •«Decide the route
Subroute •]•¨ Route data
•« •«Decide the subroute in the route
•« •«as well as the corresponding opposite
•« •« direction office number
The modules that the •]•¨ Subroute data
subroute scatters in•« •«Decide the modules housing
•« •« the modules
Trunk group •]•¨ Trunk group data
•« •«Decide the trunk groups included
•« •« in the subroute
Trunk circuit •]•¨ Trunk circuit data
•« •«Decide the trunk circuit
Fig. 1-4 the relation between the load distribution procedure and voice channel data tables
OSB2A07-13
2. Signaling Link Part
From the voice channel data, we have got such information as the CICs of the trunk
circuits, the DPC of the office direction, etc. With these parameters, we could find
out, in signaling link data, the signaling link used to carry signaling messages for this
call.
 SET OFI: Set up local office information
 MTP DSP data: Decide the linkset number.
 Use the DPC got from voice channel data to find out the corresponding DPC
index and linkset selection mode. With this code and the lowest four digits of the CIC
of the circuit used to carry the voice of the call, we could decide the linkset number of
the link to be used.
 MTP Linkset data: Decide the link number.
 Use the linkset number we have got from MTP DPC data, to find out the link
selection mode within the linkset. With this code and the lowest four digits of the CIC
of the circuit used to carry the voice of the call, we could decide the number of the
link to be used.
 MTP route data: Decide the priority of the linkset.
 Use the linkset number got from MTP linkset data, to get the priority of this
linkset as well as the index of the corresponding DPC.
 MTP link data•FDefine the attributes of the CCS7 signaling links.
In the following we will use the trunk data from local office 222 to office 555 and 666
(their networking is shown in Fig. 1-3) as an example to explain the detailed process
of trunk data setting. Suppose the SPC (signaling point code) of office 222 is b02000,
that of office 555 is b05000, and that of office 666 is b06000•CCCS7 signaling and
one PCM system (the lower one on the DTF board numbered 3,) are used between
office 222 and 555, while R2 signaling and one PCM system (the upper one on the
DTF board numbered 1.) are used between office 222 and 666. Calls between any two
of them are local area calls.
OSB2A07-14
R2V610R002
Section 2 Preparatory Data
OSB2A07-15
R2V610R002
 Key Points
 Related preparatory data

 Setting of call source and time index
Before the setting of trunk data, the related preparatory data has to be set.
2.1 Set Call Source
1. General
Users and trunk groups share common caller attributes could be categorized into one
call source. And call source data depicts the common attributes.
During the first stage of call process, call source analysis, we get the call source code
of the call through inquiring the ST user data (if the caller is a subscriber) or trunk
group data (if the caller is a trunk circuit).
2. Related Commands
Command Name Command Function

LST CALLSRC Display call source code
ADD CALLSRC Add call source code
MOD CALLSRC Modify call source code
RMV CALLSRC Remove call source code
3. Explanation of the Commands
1) ADD CALLSRC
OSB2A07-16
R2V610R002
The set of subscribers who have the same call attributes can be classified to the same
call source. The classification of call sources is based on the calling subscriber's
attributes. The attributes mainly include the pre-received numbers, the dial number
set, the route selection source code, the failure source code and whether preparing the
number etc.
For example, now we want to add a call source code 0: The pre-received numbers is
1, the dial number set is 0, the route selection source code is 0, the failure source code
is 0, whether to prepare number is 1, the number conversion index is 1 and the calling
address identification is YES. The command would be:
ADD CALLSRC: CSC=0, PRDN=1, P=0, RSSC=0, FSC=0, DCF=YES, DCX=1,

CAI=YES;
Where
•yCSC / CALL SOURCE•z
Necessary parameter, range: {0~ 65535}.
Call source code number.
 Attention 
The maximum value of the call source codes is defined in the common maximum tuple
number table. The call source codes which the subscribers use should not exceed the
maximum value.
•YPRDN / PRERECEIVE NUMBER DIGITS•Z
Optional parameter, range: {0~9}, default value is 1.
•YP / DNSET•Z
The dial number set the call source belonging to.
•YRSSC / ROUTE SELECTION SOURCE•Z
OSB2A07-17
R2V610R002
This parameter is used to distinguish the route strategy according to the call source
code. When we need different route strategy for some local office subscribers, we
should give them a special call source code, then we could give them a special route
selection source code as well.
•YFSC / FAIL SOURCE CODE•Z
It is the failure source code the caller adopts when calling such prefix. One failure
source code could be used by multiple call source codes, but one call source code
could have only one failure source code, namely the users with the same call source
codes should be approached with the same kind of failure process.
•YDCF / NUMBER PREPARE•Z
Optional parameter, range: {YES, NO}, default value is “NO”.
Whether should the called number from callers with this call source code be changed
or not. If the value is “YES” here, the called number will be changed according to the
next parameter DCX.
•YDCX / NUMBER CONVERSION INDEX•Z
Called number conversion index. Effective only when the parameter DCF is “YES”.
•YCAI / DISCRIMINATE CALLER ADDR. NATURE•Z
Optional parameter. Indicating whether should the caller address nature be

discriminated according the caller number.
2.2 Set Time Index
1. General
 We could use time to determine the time index value, which is then used in the
route analysis and hence in routing, so as to fulfill the purpose of dynamic routing. If
OSB2A07-18
R2V610R002
at the moment of calling, the time indexes do not match the route data, routing will
fail. If dynamic routing is unnecessary, we could use the default time index data, in
which index 0 is assigned to all time.
 Attention 
Time indexes should cover all time of a week.
2. Related Commands

LST TMIDX Display time indexes
ADD TMIDX Add time indexes
RMV TMIDX Delete time indexes
1) LST TMIDX
Query the time indexes we have defined.
For example, if we want to query the time covered by time index 0, the command
would be:
LST TMIDX: TMX=0
Where
•yTMX / TIME INDEX•z
Optional parameter, range: {0~ 255}.
If the time index is not specified, all time indexes will be listed.
2) ADD TMIDX
OSB2A07-19
R2V610R002
Add time indexes.

For example, if we want to set two time indexes for Sunday, index 1 for the time
earlier than or equal to 10 o'clock, and index 2 for the time later than 10 o'clock, so as
to achieve different routing strategy for different time segments. The command would
be:
ADD TMIDX•FWD=SUN•CTM=10•CTMX=1•G
ADD TMIDX•FWD=SUN•CTM=24•CTMX=2•G
Where
•yWD / WEEK•z
Necessary parameter, range: {SUN, MON, TUE, WED, THU, FRI, SAT}.
•yTM / HOUR•z
Necessary parameter, range: {1~24}.
It indicates the ending time of each time band, the unit is hour.
The matching of time is based on whether the time when the call is originated is
smaller than or equal to, or larger than the value of TM. For example, if it is Sunday,
and the time field has two values: “10” and “24”. Then, “10” will be selected for
matching if the call is made before or at ten o'clock, and “24” will be selected if the
call is made after ten o'clock.
•yTMX / TIME INDEX•z
If the time index is not specified, all time indexes will be listed.
3) RMV TMIDX
Delete the existing time indexes.
For example, if we want to remove time index before 10:00 on Sunday, the command
would be:
RMV TMIDX:WD=SUN,TM=10;
OSB2A07-20
R2V610R002
Section 3 Voice Channel Data
OSB2A07-21
R2V610R002
 Key Points 
Data setting sequence for trunk voice channel is: subroute, trunk group, trunk circuit,
route, route analysis, and called number.
3.1 Set Local Office Information
1. General
When using CCS7 system, the local office should be defined as a signaling
point in a CCS7 network, the detailed information such as its signaling point code,
which CCS7 network it locates in, is it a STP or not, does it support SCCP or not,
etc., are all defined in local office information. Setting local office information is the
first step in MTP data. Only after this, could other data like MTP DSP data and MTP
linkset data could be set successfully.
2. Related Commands

LST OFI Display local office information
SET OFI Set local office information
1) LST OFI
Check whether the local office information has already been defined.
OSB2A07-22
R2V610R002
This command has no parameters and would return the SPC (signaling point code) of
the local office and NI (network indicator), etc.
2) SET OFI
If the local office information shown for the command LST OFI is improper, we have
to use the command SET OFI to correct it. According to the example shown in Fig. 1-
3, the local office information should be set as:
SET
OFI•FLOT••CMPX•CNN••TRUE•CSN1••NAT•CSN2••NAT•CSN3•
•NAT•CSN4••NAT•CNNC•••gB02000•h•CSPF••TRUE•CLAC•••g7
55•h•CLNC••C12•g86•h•CINS••NONE•CIN2S••NONE•CNNS••SP2
4•CNN2S••NONE•G
Where
•YLOT / LOCAL TYPE•Z
Optional parameter. It indicates the type of the local switch.
Value range: {PBX, CC, CMPX, NATT, INTT, MANT}, and respectively they
represent “PBX”, “LOCAL CALL / RURAL CALL”, “TOLL, URBAN & RURAL
CALL”, “NATIONAL TOLL”, “INTERNATIONAL TOLL”, and “MANUAL TOLL
CALL”.
•YIN / INTERNATIONAL NETWORK VALID•Z,•YIN2 / INTERNATIONAL

RESERVED VALID•Z,•YNN / NATIONAL NETWORK VALID•Z,•YNN2 /
NATIONAL RESERVED VALID•Z
Optional parameter. They indicate the CCS7 signaling networks in which the local SP
is located. Range: {NO, YES}.
•YSN1 / NETWORK 1•Z~•YSN4 / NETWORK 4•Z
Optional parameter. They indicate the sequence of the CCS7 networks to be searched.
Value range: {INT, INT2, NAT, NAT2}, and respectively they represent
“INTERNATIONAL”, “INTERNATIONAL RESERVED”, “NATIONAL”, and
“NATIONAL RESERVED”.
OSB2A07-23
R2V610R002
•YINC / INTERNATIONAL CODE•Z,•YIN2C / INTERNATIONAL

RESERVED CODE•Z,•YNNC / NATIONAL CODE•Z,•YNN2C / NATIONAL
RESERVED CODE•Z
Optional parameter. They indicate the SPC of the local office in the corresponding
networks. The value should be a string.
•YINS / INTERNATIONAL NETWORK STRUCTURE•Z,•YIN2S /

INTERNATIONAL RESERVED STRUCTURE•Z,•YNNS / NATIONAL
NETWORK STRUCTURE•Z,•YNN2S / NATIONAL RESERVED
STRUCTURE•Z
Optional parameter. They indicate the structure of the corresponding networks.
Value range: {NONE, SP24, SP14}, and respectively they represent “NOT USED”,
“24 BITS SIGNALING POINT”, and “14 BITS SIGNALING POINT”.
•YSCCP / PROVIDE SCCP•Z
Optional parameter. It indicates whether the local office could provide SCCP function
or not.
Value range: {NONE, NOLINK, LINK, ALL}, and respectively they represent “NOT
PROVIDED”, “NON-CONNECTION ORIENTED”,“CONNECTION-ORIENTED”,
and „ALL”.
•YTADT / TRANSMISSION ALLOWED DELAY•Z
Optional parameter. It indicates the delay of the switch in call transmission, measured
in seconds. Range: {0~ 254}.
•YERF / ECHO CONTROL•Z
Optional parameter. It indicates whether the switch provides echo suppression

function or not.
Value range: {NONE, IN, OUT, BOTH}, and respectively they represent “NOT
PROVIDED”, “INCOMING CALL”, “OUTGOING CALL”, and “INCOMING AND
OUTGOING CALL”.
•YSPF / SP FUNCTION•Z
OSB2A07-24
R2V610R002
Optional parameter. It indicates whether does this switch has SP ( signaling point )
function or not.
Value range: {NO, YES}, and the default value is “YES”.
•YSTP / STP FUNCTION•Z
Optional parameter. It indicates whether does this switch has STP ( signaling transfer
point ) function or not.
Value range: {NO, YES}.
•YRSF / RESTART FUNCTION•Z
Optional parameter. It indicates whether does this switch has restart function or not.
•YLAC / LOCAL AREA CODE•Z•Z
Optional parameter. It indicates the area code of the location of the switch. The value
is a phone number.
•YLNC / NATION•Z
Optional parameter. It indicates the country code of the location of the switch.
•YGAC / PACKET NETWORK ACCESS CODE•Z
Optional parameter. Range: {YES, NO}. The version presented does not provide the
function of packet network access, so the value here should be "NO".
•YBTVM / CFB TO VOICE MAILBOX•Z,•YNTVM / CFNR TO VOICE

MAILBOX•Z
Optional parameter. They indicate whether the function of “CFB TO VOICE

MAILBOX” or “CFNR TO VOICE MAILBOX” is provided or not. Range: {YES,
NO}.
3.2 Set Office Direction
1. General
OSB2A07-25
R2V610R002
When adding an office direction, we need to know beforehand the following

information about the opposite office: the office type, office level, office attribute,
DPC and network indicator. And after an office direction is successfully added, we
usually assign a subroute to it, as well as the related MTP data.
2. Related Commands

LST OFC Display an office direction
ADD OFC Add an office direction
MOD OFC Modify an office direction
RMV OFC Remove an office direction
1) LST OFC
Query the attributes of the office direction represented by the office direction number.
For example, if we want to query the attributes of office direction 0, the command
could be:
LST OFC•FO=0•CON=“23”, SSR=YES•CSMD=YES, SC=YES;
Where
•yO / OFFICE DIRECTION•z
Optional parameter, range: {0~ 65535}.
If the office direction is not specified, the attributes of all office directions will be
listed.
•yON / OFFICE TITLE•z
Optional parameter. A string of characters.
Name of the office direction.
•ySSR / DISPLAY SUBROUTE•z
OSB2A07-26
R2V610R002
Optional parameter. Range: {YES, NO}, the default value is “NO”.
Whether should the subroutes of the office direction be shown or not.
•ySMD / DISPLAY DSP INDEX•z
Whether should the DPC related to the office direction be shown or not.
•ySC / DISPLAY CONGESTION INFORMATION•z
Whether should the related congestion information be displayed or not.
2) ADD OFC
Add an office direction, assign a direction number, and define the related attributes.
For example, if we want to add an office direction for office 555 (the networking is
shown in Fig.1-3), the command would be:
ADD
OFC•FO=1•CDOT=CMPX•CDOL=SAME•CNI=NAT•CDPC=•gB05000•h•
CON=•gOffice 555•h•CDOA=SPC•G
Where
•yO / OFFICE DIRECTION•z
Necessary parameter, range: {0~65535}.
The serial number assigned to an office direction.
•yDOT / TYPE•z
Necessary parameter, indicates the type of the opposite office compared with the local
office.
Range: {PBX, CC, CMPX, NATT, INTT, MANT}, and they represent “PBX”,
“LOCAL CALL / RURAL CALL”, “TOLL, URBAN & RURAL CALL”,
“NATIONAL CALL”, “INTERNATIONAL TOLL” and “MANUAL TOLL CALL”
respectively.
•yDOL / LEVEL•z
OSB2A07-27
R2V610R002
Necessary parameter, indicates the rank of the opposite office compared with the local
office.
Value range: {HIGH, SAME, LOW}, and respectively they represent “SUPERIOR”,
“PEER” and “INFERIOR” comparative level.
•yNI / NETWORK ID•z
Necessary parameter, indicates the CCS7 signaling network the opposite office is in.
Value range: {INT, INT2, NAT, NAT2}, and they represent “INTERNATIONAL”,
“INTERNATIONAL RESERVED”, “NATIONAL” and “NATIONAL RESERVED”
network respectively.
•yDPC / DPC•z
Necessary parameter, It refers to the signaling point code of the opposite office in
NO. 7 Signaling Network. This value is numbered hexadecimal, namely the
characters can only be '0' to '9' and 'A' to 'F'.
•yON / OFFICE TITLE•z
Optional parameter. The name assigned to the office direction for easy recognition.
The default value is “NONAME_OFFICE”.
•yDOA / ATTRIBUTE•z
Optional parameter. Indicates the physical attribute of the opposite exchange.
Value range: { SPC, CROSS, STEP, MB, MBC, MAN, SRV, PDN, STP, SCP}, and
they represent “SPC OFFICE”, “CROSSBAR OFFICE”, “STEP-BY-STEP
OFFICE”, “VOICE MAILBOX”, “VOICE MAILBOX STATION”, “MANUAL
OFFICE”, “SPECIAL SERVICE STATION”, “PUBLIC DATA NETWORK”,
“SIGNAL TRANSFER POINT EQUIPMENT” and “SERVICE CONTROL POINT
EQUIPMENT” respectively, and the default value is “SPC”,
3.3 Set Subroute
1. General
OSB2A07-28
R2V610R002
When adding a subroute, the office direction the subroute pointing to should
have been defined beforehand. And after a subroute is successfully added, we should
add a trunk group or groups to it.
2. Related Commands

LST SRT Display a subroute
ADD SRT Add a subroute
MOD SRT Modify a subroute
RMV SRT Remove a subroute
1) LST SRT
Before adding a subroute, we could use the command LST SRT to query subroute
data in case the subroute number we are going to use has been assigned to another
subroute. Also the attributes of this subroute could be shown.
The commonly used command would be:
LST SRT•FSR=0•CSRT=YES•CSTG=YES•G
Where
•YSR / SUB-ROUTE NUMBER•Z
Optional parameter, range: {0~ 65535}. If the subroute number is not specified, the
attributes of all subroutes will be listed.
•YSRN / SUB-ROUTE TITLE•Z
Optional parameter. Gives a name to the destination signal point for easy recognition.
•YSRT / DISPLAY ROUTE•Z
Optional parameter, range: {YES, NO}.
OSB2A07-29
R2V610R002
Indicating whether the related route information should also be displayed. The default
value is “NO”.
•YSTG / DISPLAY TRUNK GROUP•Z
Optional parameter, range: {YES, NO}.
Indicating whether the related trunk group information should also be displayed. The
default value is “NO”.
2) ADD SRT
Add a subroute.
In the example given in Fig.1-3, if we want to add a subroute for office 555 and
another for office 666, the commands would be:
 ADD
SRT•FSR=1•CDOM=1•CSRN=•g555•h•CTSM=CYC•CMN1=1•G
 ADD
SRT•FSR=2•CDOM=2•CSRN=•g666•h•CTSM=CYC•CMN1=1•G
Where
•YSR / SUB-ROUTE NUMBER•Z
•YDOM / OFFICE / PEER MODULE•Z
•YSRT / TYPE•Z
Necessary parameter. Indicating the subroute type.
Range: {OFC,MOD}, in which
OFC means “BETWEEN OFFICE”•|•| this subroute is for inter-office

communication;
MOD means “BETWEEN MODULE”•|•| this subroute is for multi-module

networking.
•YSRN / SUB-ROUTE TITLE•Z
OSB2A07-30
R2V610R002
Optional parameter. Indicating the subroute name for easy recognition. Default value:
“NONAME_SUBROUTE”.
•YTSM / GROUP SELECTION•Z
Optional parameter. Indicating the trunk group selection mode within this subroute.
Value range: {CYC, MIN, MAX, RND}, in which the default value is CYC, and:
CYC means RECYCLE•|•|Starting from the group bearing the group number next
to the one selected last time;
MIN means MINIMUM•|•| Always start from the group having the minimum
group number;
MAX means MAXIMUM•|•|Always start with the group having the maximum
group number;
RND means RANDOM•|•| Select one group randomly from all those belong to the
subroute.
•YMN1 / 1ST MODULE•Z
Necessary parameter. Indicating the first module that houses this subroute. Range:
{0~255}, in which 255 means an invalid value.
•YMN2 / 2ND MODULE•Z~•YMN8 / 8TH MODULE•Z
Optional parameter. Indicating the other modules that also houses this subroute.
Value range: {0~255}, in which 255 means an invalid value. The surplus search
modules should be set as “255”. For example, if the subroute is scattered in module 1
and 2 then the values for the eight parameters MN1~MN8 should be “1, 2, 255, 255,
255, 255, 255, 255”, or “2, 1, 255, 255, 255, 255, 255, 255” if you want module 2 to
be searched before module 1.
3.4 Set CCS7 Trunk Group
1. General
OSB2A07-31
R2V610R002
Before adding a trunk group, we should have defined the subroute this trunk
group belongs to. And since in trunk data we could assign call source codes to trunk
groups, if a new call source code is assigned, we need to add this call source code
beforehand. After a trunk group is successfully added, we still have to add trunk
circuits to it.
2. Related Commands

LST TG Display a trunk group
ADD N7TG Add a CCS7 trunk group
MOD N7TG Modify a CCS7 trunk group
RMV TG Remove a trunk group
Modify the relation between the trunk
MOD TGSRT
groups and the subroutes
1) LST TG
Before adding a subroute, we could use the command LST TG to query trunk group
data in case the trunk group number we are going to use has been assigned to another
trunk group. Also the attributes of this trunk group could be shown.
The commonly used command would be:
LST TG•FTG=0•G
Where
•yTG / TRUNK GROUP•z
Optional parameter, range: {0~ 65535}. If the subroute number is not specified, the
attributes of all trunk groups will be listed.
2) ADD N7TG
Add a CCS7 trunk group.
OSB2A07-32
R2V610R002
In the example given in Fig.1-3, if we want to add a CCS7 trunk group for office 555,
the commands would be:
ADD N7TGFMN=1CTG=1CG=INOUTCSRC=1CTGN=“TO
555”•CCSM=CTRL•CNIF=TURE•G
Where
•YMN / MODULE•Z
Necessary parameter. The number of the module housing the trunk group.
•YTG / TRUNK GROUP•Z
•YG / GROUP DIRECTION•Z
Optional parameter.
Value range: {IN, OUT, INOUT}, they represent “INCOMING TRUNK”,

“OUTGOING TRUNK” and “BI-DIRECTIONAL TRUNK” respectively, and the
default value is “INOUT”, as CCS7 trunk groups are usually bi-directional.
•YSRC / SUB-ROUTE NUMBER•Z
•YTGN / TITLE•Z
Optional parameter. Give a name to the trunk group for easy recognition. The default
value: “NONAMENO7TKGRP”.
•YCSC / CALL SOURCE•Z
Optional parameter. Indicates the call source code of the trunk group. Range:
{0~65535}, and the default value is 0.
 Attention 
If the call source code is a new one which has never been used by other trunk groups
or subscribers, then we have to define this call source code before adding the trunk
group.
OSB2A07-33
R2V610R002
•YCT / CIRCUIT TYPE•Z
Optional parameter. Indicates the type of the circuits contained in the trunk group.
Value range: {TUP, ISUP}, and the default value is TUP.
•YCSM / CIRCUIT SELECTION•Z
Optional parameter. Indicates the mode used to select a circuit from a trunk group to
avoid dual seizure from the two offices at both ends of the trunk group.
Value range: {MIN, MAX, CYC, FIFO, CTRL, RNDM}, in which the default value
is “CTRL”, and:
MIN means MINIMUM•|•|Start selecting from the circuit with minimum circuit
number;
MAX means MAXIMUM•|•|Start selecting from the circuit with maximum circuit
number;
CYC means RECYCLE•|•|Start selecting from the circuit next to the one selected
last time;
FIFO means FIRST-IN-FIRST-OUT•|•|Select a circuit based on the first-in first-out

principle, namely the circuit released earliest will be seized first;
CTRL means MASTER / SLAVE•|•|Select a circuit based on FIFO ( for the master
circuits) / LIFO (for the slave circuits) principle;
RNDM means RANDOM•|•| Select a circuit in a random manner.
In general practice, CCS7 often chooses “Master / Slave” circuit selection mode. But
the requirements of the opposite office should be taken into consideration when
choosing the mode.
•YRCN / RETAINED CIRCUIT•Z
Optional parameter. Indicating the circuits reserved for network management. That is,
for an ordinary call, if all the ordinary trunk circuits are busy, routing will be
unsuccessful; while for a priority call, if all the ordinary trunk circuits are busy, if any
of the reserved circuits is idle, it may be selected. Value range: {0~1023}, and the
OSB2A07-34
R2V610R002
default value is 0, since it is often the case that reserving a circuit for network
management is unnecessary.
•YCNSF / LINK TO SATELLITE•Z
Optional parameter. Indicates whether any satellite circuit is connected.
Value range: {”NO”, “YES”}, and the default value is “NO”.
•YSIGT / SIGNALING TYPE•Z
Optional parameter. Indicating the type of the signaling used.
Value range: {NO7, MAILBOX}, and the default value is “NO7”.
•YICR / CALL-IN AUTHORITY•Z,•YOCR / CALL-OUT AUTHORITY•Z
Optional parameters. Call-in and call-out authorities are used to control the call rights
of trunk circuits. Only the permitted types of calls can be transferred through the
circuits.
Value range: {LCO, LC, LCT, NTT, ITT, CCR1~CCR9}, they represent “INTRA-
OFFICE”, “LOCAL”, “LOCAL TOLL”, “NATIONAL TOLL”, “INTERNATIONAL
TOLL”, “CUSTOMER DEFINED CALL RIGHT 1” ~ “CUSTOMER DEFINED
CALL RIGHT 9” respectively, and in default all items are chosen.
 Note
“Customer defined call right 1” ~ “customer defined call right 9” are defined
in•yCUSTOM ATTRIBUTE•zof the Called Number Analysis Table. Therefore, if a
call prefix requires a certain type of customer defined call right, while the related
subscriber or trunk group do not have the corresponding call-in/out rights, the call
will not be put through.
•YDOD2 / DOD2•Z
Optional parameter. Indicates whether or not should a second dial tone be sent to
outgoing calls. Value range: {NO, YES}, and the default value is “NO”, since “YES”
could be chosen only when the switch acts as a PBX, after an extension dials the out-
of-office prefix, a second dial tone could be sent to the extension.
OSB2A07-35
R2V610R002
•YCDR / CLIR•Z
Optional parameter. Indicates whether the caller identity should be displayed or

restrained.
Value range: {INRES, OUTRES}. In which
INRES means incoming CLIR•|•|caller line identity restrained for incoming calls.
Namely, it is used for incoming trunk groups: when an incoming trunk group receives
a caller number unit in which PI (display indicator) is “allowed‟ (allowed to display) ,
while “INRES” has been chosen for the trunk group, then PI for this call will be
changed to “restricted”(not allowed to display).
OUTRES means outgoing CLIR•|•|caller line identity not restrained for outgoing
calls. Namely, it is used for outgoing trunk groups: when an outgoing trunk group
want to sent a call in whose caller number unit PI is “restricted‟, while OUTRES has
been chosen for this trunk group, then PI for this call will be changed to “allowed”.
These two values, INRES and OUTRES, could be chosen independent of one another.
•YIT / INITIAL TONE•Z
Optional parameter. Indicates should the outgoing call listens to the initial tone or not.
Value range: {NO, YES}, and the default value is “NO” since generally no initial
tone need to be sent.
•YITT / INITIAL TONE TYPE•Z
Indicates the initial tone to be used. This parameter is effective only when the
parameter IT is “YES”.
•YABT / ABNORMAL SEND TONE•Z
Optional parameter. Decides whether should tones indicating abnormality be sent or

not when abnormal situations are found in the process of connection.
Value range: {NO, YES}, and the default value is “NO” since usually no abnormal
tone should be sent.
•YABTT / ABNORMAL TONE TYPE•Z
OSB2A07-36
R2V610R002
Indicates the abnormal tone to be used. This parameter is effective only when the
parameter ABT is “YES”.
•YCHS / CHARGING SOURCE CODE•Z
Optional parameter. Indicates the charging source code assigned to this trunk group
used for carrying incoming calls.
Value range: { 0~255}. In which 254 is used in charging data as a universal matching
symbol, so usually it is not assigned to any special trunk group; and 255 means no
charging when a call comes from this trunk group and it is the default value for
parameter CHS.
•YOTCS / OUTGOING TRUNK CHARGING SOURCE•Z
Another kind of charge group number assigned to the No.7 trunk groups used for
carrying outgoing calls, as well as to the CAS's outgoing trunk groups.
Value range: {0~255}, and the default value is “255” since usually the trunk groups
are not charged for carrying outgoing calls.
•YUPP / USE OPPOSITE PULSE•Z
Optional parameter. Value range: {NO, YES}, and the default value is “NO”.
Indicates whether the tariff pulses to or from the opposite office should be used.
 Note 
If the choice is "YES", it is required the cooperation of the offices at both ends of the
trunk group, and means differently for incoming and outgoing trunk groups. For
incoming groups, it means when a call comes in, the local office will sent tariff pulses
onto the trunk circuit carrying the call, and the opposite office should take measures
to received the pulses accordingly; while for outgoing groups, it means when a call
goes out, the local office will wait to receive tariff pulses from the opposite office on
the trunk circuit seized, and the opposite office should sent the tariff pulses needed.
•YCD / CHARGING COMPLAINT•Z
OSB2A07-37
R2V610R002
Indicates whether an extra detailed bill tabbed as complaint bill should be produced
every time the trunk group is charged.
•YCAMA / CAMA•Z
Indicates whether the office at the upper level should perform centralized billing for
the local office or not. And if the choice is “YES” then you'd better set the trunk
group as sending CLI voluntarily (Set parameter CDR as “YES”).
•YNIF / CAN REQUEST CALLER NUMBER•Z
It indicates when a call comes in, could CLI be asked for or not from the opposite
office.
•YNICF / CONNECT WITHOUT CALLER NUMBER•Z
It indicates whether an incoming call should be put through or not when the CLI is
not received.
•YILN / MIN. CALLER LEN•Z
Optional parameter. Value range: {0~15}, and the default value is 7.
•YIPM / CALLER NUMBER PROVIDING•Z
Optional parameter. Indicates when CLI is not included in the signaling messages of
an incoming call which substitutive parameter should be used .
Value range: {TRK, DFT}, they represent “TRUNK LINE ID” and “DEFAULT
NUMBER” respectively. The default value is “TRK”, and if “DFT” is chosen then the
next parameter DI is effective.
•YDI / DEFAULT CALLER NUMBER•Z
Optional parameter. The number used to serve as caller number. The default value of
this parameter is 8888888.
OSB2A07-38
R2V610R002
•YUUGN / CALL BARRING GROUP•Z
Optional parameter. Indicates the call barring group that the trunk group belongs to. It
is used to define call barring.
Value range: {0~65535}, in which 65535 is used when inter-group call is not needed.
•YSIGM / SIGNALING MODE•Z
Optional parameter. Indicating the signaling mode adopted.
Value range: {CHN, ETSI, RU}, they represent “china”, “etsi” and “ru” respectively.
And the default value is “CHN”. This parameter still hasn‟t been put into use.
•YSIGLIN / SIGNALING LINK•Z
Optional parameter, value range: {0~65535}. Used for PRA trunk groups, for other
trunk groups we could left this parameter empty.
•YHTVALUE / OCCUPANCY OVERLENGTH THRESHOLD•Z,•YHLVALUE

/ OCCUPANCY ULTRASHORT THRESHOLD•Z
Optional parameters. Value range: {0~65535}, and the default value is 0.
These two are thresholds indicating that the trunk seizure time is too long or too short.
•YCC / CONTINUITY-CHECK•Z
Optional parameter. Indicates whether conduction check should be made or not before
using a trunk circuit in this group to carry calls.
Value range: {NO, YES}, default value is “NO”, since for CCS7 trunk groups,
usually continuity-check is not performed.
•YDV / TIME DELAY VALUE•Z
Optional parameters, range: {0~1023}, default value are 0.
The time delay (measured in seconds) of the trunk circuit seizure. It is used in CCS7
signaling to decide whether the present call meets the time delay requirements.
•YGTS / GROUP MSG TIMEOUT TO SINGLE•Z
Value range: {NO, YES}, and the default value is “YES” .
OSB2A07-39
R2V610R002
Indicates whether single message should be used when group message proves time
out. when C&C08 is connected to such switches as EWSD or S1240J, this function is
occasionally used.
•YTC / TRANSMISSION CAPABILITY•Z
The transmission capability for ISDN calls.
Value range: {AUDIO, NLDIG, LDIG, AUD31, SNLD, VIDEO}, and they represent
“VOICE SERVICE”, “UNRESTRICTED DIGITAL INFORMATION SERVICE”,
“RESTRICTED DIGITAL INFORMATION SERVICE”, “3.1KHZ AUDIO
SERVICE”, “UNRESTRICTED DIGITAL INFORMATION SERVICE WITH
SIGNAL TONES”, “VIDEO SERVICE” respectively.
•YTM / TRANSMISSION MODE•Z
Optional parameter. Indicates the transmission mode for ISDN calls.
Value range: {PACK, S64K, S128K, S384K, S1530K, S1920K, MULTI}, they
represent “PACKET MODE”, “64KBIT/S”, “128KBIT/S”, “384KBIT/S”,
“1530KBIT/S”, “1920KBIT/S” and “MULTIPLE RATE” respectively. And in
default all items are chosen.
•YCCT / CIC CHANGE TYPE•Z
Optional parameter. CIC is the circuit code used in CCS7 signaling. CIC conversion
is mainly used for trunk self-looping.
Value range: {NOC, INC, DEC}, which mean “NO CHANGE”, “INCREASE”, and
“DECREASE” respectively, and the default value is “NOC”, since only for trunk self-
looping is CIC conversion necessary, for normal CCS7 trunk groups, there need no
change at all.
•YCCV / CIC CHANGE VALUE•Z
Optional parameter. Values used in CIC conversion. For normal CCS7 trunk groups,
the value is "0"; and for the condition of self-looping, values such as 32 or multiples
of 32 are used.
Value range: {0~4095}, and the default value is 0.
OSB2A07-40
R2V610R002
•YPR / PRIORITY•Z
Within a subroute, the highest priority level of a trunk group is level 0. When
selecting a trunk group, the one with highest priority will first be tried, and only when
the trunk groups of higher priority levels are busy, may the trunk groups of lower
priority level be attempted.
•YUL / AVAILABILITY•Z
Describes the times left that a trunk group could be selected. For a specific subroute,
the initial available times is defined here. And each time the group is selected, the
available times would decrease by one until the it is decreased to zero, which means
the group can not be selected any more. When all the trunk groups of a subroute have
zero available times, the trunk groups will be reset to have their initial available times,
i.e. the value set in parameter UL. The purpose of defining availability is to distribute
the traffic according to a given principle among the trunk groups of the subroute.
 Attention 
Priority and availability are meaningful only for the trunk groups belonging to the
same subroute.
•YSVRCTRL / SOFT PARA OF SERVICE CTRL•Z
Optional parameter. Value range: {WAC, SVR / 1~SVR / 15}, which represent
“WIDE AREA CENTREX SERVICE” and “REVERSED SERVICE 1”~
“REVERSED SERVICE 15” respectively. If any of the functions is provided, you
should tick the corresponding item.
•YHES / ECHO CTRL•Z
Optional parameter. Value range: {NINC, OHES, IHES, BHES}, which represent
“NO ECHO CONTROL”, “ECHO CONTROL OF OUTGOING CALL”, “ECHO
OSB2A07-41
R2V610R002
CONTROL OF INCOMING CALL” and “BI-DIRECTIONAL ECHO CONTROL”

respectively, and the default value is “NINC/NO ECHO CONTROL”.
•YOLP / OVERLAP SEND CLD•Z
Optional parameter. Indicates whether the CLD should be send in overlap mode.
Value range: {NO, YES}, and the default value is “NO”.
3) MOD TGSRT
This command is used to change the correspondence relation between trunk groups
and subroutes so as to group a trunk group into a subroute.
For example, we have a trunk group 0 defined in module 1, it used to belong to
subroute 0. If we want to change this relation, and re-group this trunk group into
subroute 1, the command is as follows:
MOD TGSRT: TG=0, SR=1;
 Note
For trunk group with No.7 trunk circuit, it is not allowed to be modified to be part of
sub-route to office direction with different network ID/DPC.
3.5 Set CAS Trunk Group
3.5.1 Set Line/Register Signal/Command

Conversion
1. General
OSB2A07-42
R2V610R002
Before adding a CAS trunk group, we should have defined the line/register
signal/command conversion indexes which will be used when setting CAS trunk
groups.
2. Related Commands

Add/change/delete/display a line
signal report conversion. And line
ADD/MOD/RMV/LST LRPT
signaling transform indexes are
defined by using these commands.
Add/change/delete/display a line
signal send conversion. And line
ADD/MOD/RMV/LST LSND
command transform indexes are
Add/change/delete/display a register
signal report conversion. And
ADD/MOD/RMV/LST REGRPT register signaling conversion
indexes are defined by using these
commands.
Add/change/delete/display a register
signal send conversion. And register
ADD/MOD/RMV/LST REGSND
command conversion indexes are
A group of such commands should be defined beforehand and be executed before

adding a CAS trunk group, so as to provide the switch with the necessary line/register
signaling transform indexes.
These commands usually are fed into the switch during exchange deployment stage
by the installation engineers. As the O&M staff, you only have to remember the
correspondence between the line/register signal/command conversion indexes and the
signals, which are listed in table 3-1.
Table 3-1 correspondence between the signals types and the line/register signal/command conversion
indexes
Line signals Line signal/command conversion indexes Register signa
International line_2
•yID/index•z=0 National MFC
bit
OSB2A07-43
R2V610R002
National line_2 bit •yID/index•z=1 DTMF & DP

Line_1 bit •yID/index•z=2 International MFC
Line_pulse •yID/index•z=3 MFPS:
Note: For each type of line (or register) signals, the indexes for line (or register) signal conversion and
that for line (or register) command conversion are the same.
The following is part of the commands list:
ADD LSND: ID=1, LCMD=SZ ,PCMD=64, P1=1 ,P2=10;
ADD LSND: ID=1, LCMD=SZA ,PCMD=64, P1=13,P2=0 ;
•c•c•c•c
ADD LRPT: ID=1, EVT=LINE_SIG, PARA=0, CRS=IDL , LEVT=SZ ;
ADD LRPT: ID=1, EVT=LINE_SIG, PARA=4, CRS=IDL , LEVT=FR
•c•c•c•c
ADD REGSND: ID=0, CMD=CLD , PARA=1 , RSD=1 ;
ADD REGSND: ID=0, CMD=CLD , PARA=2 , RSD=2 ;
•c•c•c•c
ADD REGRPT: ID=0, RSD=1 , CRS=IWCDN, LEVT=CLD, PARA=1;
ADD REGRPT: ID=0, RSD=2 , CRS=IWCDN, LEVT=CLD, PARA=2;
•c•c•c•c.
3.5.2 Set CAS Trunk Group Data
1. General
Before adding a trunk group, we should have defined the subroute and call
source code this trunk group belongs to.
2. Related Commands
OSB2A07-44
R2V610R002

LST TG Display a trunk group
ADD N1TG Add a R2 trunk group
MOD N1TG Modify a R2 trunk group
RMV TG Remove a trunk group
Modify the relation between the trunk
MOD TGSRT
groups and the subroutes
1) ADD N1TG
When adding CAS trunks, we should add two CAS trunk groups each time, one for
outgoing and one for incoming.
In the example given in Fig.1-3, if we want to add CAS trunk groups for office 666,
the commands would be:
ADD N1TG•FMN=1•CTG=2•CG=IN•CSRC=2•CTGN=•gTO 666
IN•h•CNIF=YES•CNICF=YES•G
ADD N1TG•FMN=1•CTG=3•CG=OUT•CSRC=2•CTGN=•gTO 666

OUT•h•CNIF=YES•CNICF=YES•G
Where parameters•yMN/MODULE NUMBER•Z,•YTG/TRUNK GROUP

NUMBER•Z,•YG/GROUP DIRECTION•z and•ySRC/SUB-ROUTE
NUMBER•zare the necessary parameters. As for the other parameters, which are
optional, we could use their default values if there is no special demands. And since
some of the parameters for CAS trunk groups are similar to those for CCS7 trunk
groups, we will not repeat them here. And in the following it is the introduction to the
parameters different from those used in CCS7 trunk groups.
•YG/GROUP DIRECTION•Z
The group direction for CAS trunk groups would be uni-directional: either
“INCOMING TRUNK” or “OUTGOING TRUNK”.
•YCSM/CIRCUIT SELECTION•Z
OSB2A07-45
R2V610R002
Value range: {MIN, MAX, CYC, FIFO, CTRL, RNDM}, which means
“MINIMUM”, “MAXIMUM”, “RECYCLE”, “FIFO”, “MASTER/SLAVE”, and
“RANDOM” respectively, and the default value is “CYC”.
•YSAT/SIGNAL TYPE•Z
Indicating the signaling system adopted. Value range: {R2, NO5, CHINANO1, TB85,
TB93}, and the default value is R2.
•YLS/LINE SIGNAL•Z
Optional parameter, indicating the line signals adopted. Value range: {LINE_2BIT,
LINE_1BIT, PULSE, NO5}, and the default value is “LINE_2BIT”.
 Note
Remember the correspondence between the line signal types and the line
signaling/command transform indexes?
For “LINE_2BIT”, the corresponding •yLSC/LINE SIGNALING TRANSFORM

INDEX•Zand •YLCM/LINE COMMAND TRANSFORM INDEX•Zshould be 0
(international line_2 bit) or 1 (national line_2 bit);
For “LINE_1BIT”, the corresponding •yLSC•zand•yLCM•zshould be 2;
For “PULSE” , the corresponding •yLSC•zand•yLCM•zshould be 3;
while for “NO5”, parameters •yLSC•zand•yLCM•z are invalid, you can just use
the default value.
•YRS/REGISTER SIGNAL•Z
Optional parameter, indicating the line signals adopted. Value range: {MFC, MFP,
PULSE, NONE, DTMF, AT0_DTMF, AT0_PULSE, MFPS, RSD5, NULL}, and the
default value is “MFC”.
 Note
OSB2A07-46
R2V610R002
1. Remember the correspondence between the register signal types and the
register signaling/command transform indexes?
For “MFC”, the corresponding•yRSSC/RSD SIGNALING CONVERSION

INDEX•Zand •YRSCM/RSD COMMAND CONVERSION INDEX•Zshould be 2
(international MFC) or 0 (national MFC);
for “PULSE” & “DTMF”, the corresponding•yRSSC•Zand

•YRSCM•Zshould be 1;
for “MFPS”, the corresponding•yRSSC•Zand •YRSCM•Zshould be 3;
for “RSD5”, which is the register signal for No.5, , NULL ”,

parameters•yRSSC•Zand •YRSCM•Z are invalid, you can just use the default
value;
while for the other items such as MFP and AT0_DTMF, etc., they are seldom
used.
2. A CAS signaling system is a combination of one of the line signals and one
of register signals mentioned above. However, the combination is not randomly
made, for example, you could not combine a national line signal with an international
register signal. And as for international R2 signaling, there is only one choice: line_2
bit + MFC.
3. If we choose line_2 bit as the line signal, and MFC as the register signal, how
could we decide whether they are national signals or international signals?
If the parameter•yTYPE•zin command ADD OFC for the opposite office at

the other end of the trunk group is“INTERNATIONAL TOLL”, and the parameter
•yLOCAL TYPE•zof the local office in command SET OFI is“INTERNATIONAL
TOLL” too, then we could infer that the international R2 signaling system
(international line_2 bit + international MFC) is adopted, otherwise the national R2
signaling system (national line_2 bit + national MFC) is used.
•yLSC/LINE SIGNALING TRANSFORM INDEX•Z
OSB2A07-47
R2V610R002
Optional parameter. Value range: {0~7}, indicating the line signaling transform
index, and the default value is 0. It could be indexed from the command ADD LRPT.
•YLCM/LINE COMMAND TRANSFORM INDEX•Z
Optional parameter. Indicating the line command transform index, and the default
value is 0. It could be indexed from the command ADD LSND.
•yRSSC/RSD SIGNALING CONVERSION INDEX•Z
Optional parameter. Value range: {0~7}, indicating the register signaling conversion
index, and the default value is 0. It could be indexed from the command ADD
REGRPT.
•YRSCM/RSD COMMAND CONVERSION INDEX•Z
Optional parameter. Value range: {0~7}, indicating the register command transform
index, and the default value is 0. It could be indexed from the command ADD
REGND.
•YIFRC/REQUEST CLI•Z
This parameter is valid only for incoming trunk groups. Optional parameter. Value
range: { NO, YES}, indicating whether the local office should ask for CLI (caller line
identification) from the opposite office, and the default value is NO.
•YRCPS/REQUEST CLI POSITION•z
Optional parameter, and the default value is 0.
This parameter is valid only for incoming trunk groups. When flag•yIFRC•z is
“YES”, parameter•yRCPS•z indicates the position to send the request for CLI. For
example, as we know, for R2 signaling system, the request for CLI is represented by
the signal A5; while in CCS7 system, the same request is represented by the MSU
GRQ. Therefore, when R2 or CCS7 signaling system is adopted, this parameter shows
that after the transmission of how many digits of the called number, should A5 or
GRQ be sent to the opposite office.
•YRCLI/RECEIVE CLI•Z
OSB2A07-48
R2V610R002
This parameter indicates that whether the caller number should be received or
discarded. It is valid only for incoming trunk groups. Value range: {NO, YES}, and
the default value is “YES”.
•YSCLI/SEND CLI•Z
This parameter indicates that whether the caller number should be send or not. This
parameter is valid only for outgoing trunk groups. Value range: {NO, YES}, and the
default value is “YES”.
•YIFSE/REQUEST HES•Z
Optional parameter, It indicates whether the echo suppression information should be

required or not. Value range: {NO, YES}, and the default value is “NO”.
•YRECT/REQUEST CIRCUIT TYPE•Z
•YWOL/WAITING SEIZURE ACK TIME•Z ~•YDBRL/RING BACK TONE

SEND DELAY•Z
These parameters define some timers which are necessary for CAS signaling system,
and usually we just use their default values..
•yPR/PRIORITY•Z
Optional parameter, indicating the priorities of the trunk groups within a same
subroute. Value range: {0~15}, and the default value is 0.
Within a subroute, the highest priority level of a trunk group is level 0. When
selecting a trunk group, the one with highest priority will first be tried, and only when
the trunk groups of higher priority levels are busy, may the trunk group of lower
priority level be attempted.
•YUL/AVAILABILITY•Z
Optional parameter.Value range: {0~255}, and the default value is 0.
It describes the times left that a trunk group could be selected. For a specific subroute,
the initial available times is defined here. And each time the group is selected, the
available times would decrease by one until the it is decreased to zero, which means
OSB2A07-49
R2V610R002
the group can not be selected any more. When all the trunk groups of a subroute have
zero available times, the trunk groups will be reset to have their initial available times,
i.e. the value set in the column of•yavailability•z. The purpose of defining
availability is to distribute the traffic according to a given law among the trunk groups
of the subroute.
•YCT/CIRCUIT TYPE•Z
Optional parameter, indicating the type of the circuits within this trunk group. Value
range: {DT2, DT5, DTT}, and the default value is DT2. (DT2 is for R2 signaling,
DT5 is for No.5 signaling, and DTT supports T1 ports.)
•YSA9/SEND A9 SIGNAL•Z
Optional parameter. Value range: {YES, NO}. This parameter has no use in the
current version, so we could just use its default value, NO.
2) MOD TGSRT
This command is used to change the correspondence relation between trunk groups
and subroutes so as to group a trunk group into a subroute.
For example, we have a trunk group 10 defined in module 1, it used to belong to
subroute 10. If we want to change this relation, and re-group this trunk group into
subroute 1, the command is as follows:
MOD TGSRT: TG=10, SR=1;
3.6 Set CCS7 Trunk Circuit
1. General
Before adding a CCS7 trunk circuit, we should have defined the CCS7 trunk
group this circuit belongs to. And if the trunk board providing the circuit has not been
defined in config data, we have to define it first.
2. Related Commands
OSB2A07-50
R2V610R002

ADD PCMATR Add PCM attribute
LST CIC Display the distribution of CICs
ADD N7TKC Add a CCS7 trunk circuit
DSP N7C Display a CCS7 trunk circuit
MOD N7TKC Modify a CCS7 trunk circuit
RMV TKC Remove a CCS7 trunk circuit
1) ADD PCMATR
Define the attributes of the PCM system used.
Since this version (R3V610R003) supports both E1 and T1 ports, we have to use this
command to declare the port we are going to use. For example, if we want to use the
circuits in the first PCM system (PCM system number 0) of Module 1, we have to
execute the following command beforehand:
ADD PCMATR: MN=1, PN=0, PT=E1;
Where
•yMN/MODULE•z means module number;
•yPN/PCM NUMBER•z indicates the PCM system number;
•yPT/PCM TYPE•z
Necessary parameter. Value range: {E1, T1}. It indicates the port type of the PCM
system we are going to use.
•yLC/LINE CODE•z
•c•c
All the other parameters are optional. And usually we just use their default values.
2) LST CIC
When adding a CCS7 circuit, we should assign it a CIC (Circuit identification code).
So we have to learn beforehand the CICs still unused for the specific adjacent DPC,
as well as the already defined CICs‟ distribution among the SMs, and we could fulfill
the purpose by using the command LST CIC. What‟s more, after adding a CCS7
circuit, we could use the above command to check the result.
OSB2A07-51
R2V610R002
Since there is no parameter for this command, the command is simply:

LST CIC•G
3) ADD N7TKC
For the example of Fig. 1-3, we should use the command as:
ADD N7TKC•FTG=1•CSC=128•CEC=159•CSCIC=0•CSCF=TRUE
Where
Necessary parameter. Indicates the trunk group number this circuit belongs to.
•YSC / START CIRCUIT•Z
Necessary parameter. Value range: {0~65535}, and the default value is 0.
Indicates the physical number of the first circuit we want to add.
 Note
The physical number of a circuit could be derived from the following formula:
Circuit number = DTF board number•~64 + the sequence number of the circuit on
the board
•YEC / END CIRCUIT•Z
Optional parameter. Indicates the number of the last circuit we want to add.
Value range: {0~65535}, and the default value is the same as the start circuit.
As in the example of Fig.1-3, the start circuit would be SC =2•~64•{0=128, and the
end circuit would be EC=2•~64•{31=159.
•YSCIC / START CIC•Z
Necessary parameter. Indicates the CIC number of the first circuit indicated in
parameter SC.
OSB2A07-52
R2V610R002
•YSCF / MASTER ID OF START CIRCUIT•Z
Necessary parameter. Indicates the CIC number of the first circuit indicated in
parameter SC.
Value range: {NO, YES}, which mean “non master” and “master” respectively.
 Attention
Among continuously added circuits, the circuits alternatively become "master" and
"non master".
 Note
For CCS7 signaling system, since all trunk circuits are bi-directional, to prevent dual
seizure from the offices at both ends, we give the master control right over the circuit
to one office, and the office at the other end have non-master or slave control right
over this circuit. Usually we assign the master control rights according to the circuit's
CIC number : if the CIC number is even then its master control right is given to the
office which has larger SPC (Signaling point code), and if the CIC number is odd
then its master control right is given to the office which has smaller SPC.
•YCS / CIRCUIT STATE•Z
Optional parameter. Indicates the state of all the circuits added in this command.
Value range: {UNU, BLK, USE, SOU}, in which
UNU means “unavailable”•|•| For the trunk groups using CCS7 signaling, the
circuit corresponding to timeslot 0 of each PCM system is fixed to be used for
transmitting synchronization signals, therefore its status should be set as "uninstall";
the status of the timeslots used for carrying the signaling links are also "uninstall".
While for the trunk groups using CAS signaling, the circuit corresponding to timeslot
0 of each PCM system is fixed for transmitting synchronization signals and the circuit
OSB2A07-53
R2V610R002
corresponding to timeslot 16 of each PCM system is fixed for transmitting line signals
and synchronization signals, therefore their status should also be set as "uninstall".
USE means “AVAILABLE” •|•| The timeslots used for carrying voice should have
their status as "available".
BLK means “BLOCKING•|•|If a trunk circuit is detected broken, or for some other
reason unable to transfer calls temporarily, to prevent call loss, the status of the
circuit should be set as "Block" so that no calls will be sent onto this circuit.
SOU means “RESOURCE”•|•|effective only for intelligence network (IN), for

ordinary CCS7 TUP/ISUP it is useless.
•YCOF / CALL OBSERVATION•Z
This function is not provided in the present version.
3.7 Set CAS Trunk Circuit
1. General
Before adding a CAS trunk circuit, we should have defined the CAS trunk
group this circuit belongs to. And if the trunk board providing the circuit has not been
defined in config data, we have to define it first.
2. Related Commands

ADD BRD Add board
ADD PCMATR Add PCM attributes
LST PCMATR List PCM attributes
ADD N1TKC Add a CAS trunk circuit
DSP N1C Display a CAS trunk circuit
MOD N1TKC Modify a CAS trunk circuit
RMV TKC Remove a CAS trunk circuit
OSB2A07-54
R2V610R002
1) ADD BRD
Confirm whether the circuit board of the trunk circuit exists. If not, use the command
ADD BRD to add trunk board.
For example, to add a DT board to slot 5 of frame 3 of module 1, the command would
be:
ADD BRD: MN=1, F=3, S=5, BT=DT2;
Return value: 0 indicates success.
Where parameter MN stands for module number, F for frame number, S for slot
number, and BT for board type.
2) ADD PCMATR
Define the attributes of the PCM system used.
Since this version (R3V610R003) supports both E1 and T1 ports, we have to use this
command to declare the port we are going to use. For example, if we want to use the
circuits in the first PCM system (PCM system number 0) of Module 1, we have to
execute the following command beforehand:
ADD PCMATR: MN=1, PN=0, PT=E1;
3) ADD N1TKC
For the example of Fig. 1-3, we should use the command as:
ADD N1TKC•FTG=2•CSC=224•CEC=239•CCS=USE•G
ADD N1TKC•FTG=3•CSC=240•CEC=255•CCS=USE•G
The settings of the parameters in the above commands are similar to those in ADD
N7TKC, so we will not repeat them here. Just to remember that TG stands for trunk
group, SC for start circuit number, EC for end circuit number, and CS for circuit
status.
3.8 Set Route
OSB2A07-55
R2V610R002
1. General
Before adding a route, we should have defined the subroutes it uses. And after
it, we usually add trunk analysis data.
2. Related Commands

LST RT Display the route information
ADD RT Add a route
MOD RT Modify a route
RMV RT Remove a route
1) LST RT
When adding a route, we should check beforehand the route numbers already in use.
If we want to show route 1 and its subroutes, as well as the route analysis related to
route 1, the command would be:
LST RT: R=1, SSR=YES, SRA=YES;
Where
•YR / ROUTE NUMBER•Z
Optional parameter. Value range: {0~ 65535}.
If the route number is not specified, all routes will be listed. You can still choose
whether to list the other information at this time.
•YRN / ROUTE TITLE•Z
Optional parameter. The name assigned to the route for easy recognition.
•YSSR / DISPLAY SUB-ROUTE•Z
Optional parameter. Indicates whether the subroutes should be displayed or not.
OSB2A07-56
R2V610R002
Value range: {YES, NO}, and the default value is “NO”.
•YSRA / DISPLAY ROUTE ANALYSIS•Z
Optional parameter. Indicates whether the route analysis information should be

displayed or not.
Value range: {YES, NO}, and the default value is “NO”.
2) ADD RT
If the route dose not exist, we could use the command ADD RT to add it. For the
example of Fig.1-3, the command would be:
ADD RT•FR=1•CRN=•gTO 555•h•CSR1=1•G
Where
Optional parameter. The name assigned to the route for easy recognition. Default
value: “NONAME_ROUTE”.
•YRT / ROUTE TYPE•Z
Optional parameter. Value range: {NRM, QUE}, the default value is NRM and
NRM means ORDINARY ROUTE•] •]if routing fails, the call will be released;
QUE means QUEUE ROUTE •]•] even if routing fails, it will be queued at the user
side for idle circuit. This function is not provided in the current version of C&C08.
•YSRST / SUB-ROUTE SELECTION MODE•Z
Optional parameter. Value range: {SEQ, PERC}, in which the default value is “SEQ”,
and
SEQ means “SEQUENTIAL SELECTION”•] •]selecting a route starting from the

first one to the last one. That is, if the first one is busy, the second one may be
selected, and so forth;
OSB2A07-57
R2V610R002
PERC means “SELECT BY PERCENTAGE”•]•]selecting a subroute according to

the given respective percentages, so as to make the probability of selecting a specific
subroute follow some rules.
•YPSR1 / PERCENTAGE OF SUB-ROUTE1•Z~•YPSR5 / PERCENTAGE OF

SUB-ROUTE5•Z
Optional parameter. Range: {0~ 100}, and the default value is 0.
Indicates the percentages of load sharing among the five subroutes given in columns
from•ySR1 / 1ST SUB-ROUTE•z to•ySR5 / 5TH SUB-ROUTE•z. The sum of
percentages shall be 100. These values are useful only when the value of
parameter•ySRST / SUB-ROUTE SELECTION MODE•z is “PERC”. For routing
by sequence, these 5 columns are ineffective.
•YSR1 / 1ST SUB-ROUTE•Z
Necessary parameter. Range: {0~ 65535}, and the default value is 0. It indicates the
number of the first subroute belonging to the route.
•YSR2 / 2ND SUB-ROUTE•Z~•YSR5 / 5TH SUB-ROUTE•Z
Optional parameter. Range: {0~ 65535}, and the default value is 0. Indicate the
numbers of the other subroutes also belonging to the route.
Tips 
If there is only one subroute contained in a route, we usually give it a subroute
number which is the same as that of the route number, and then we should put the
number in parameter•ySR1 / 1ST SUB-ROUTE•z, and the other parameters
from•ySR2 / 2ND SUB-ROUTE•zto•ySR5 / 5TH SUB-ROUTE•zshould be set as
"255".
3.9 Set Route Analysis
OSB2A07-58
R2V610R002
1. General
Before adding route analysis data, we have to make sure that the related time
indexes, routing source codes, and the routes used have been defined.
2. Related Commands

LST RTANA Display route analysis
ADD RTANA Add a route analysis
MOD RTANA Modify a route analysis
RMV RTANA Remove a route analysis
1) LST RTANA
Check the route analysis data already defined.
We can choose to display the route analysis data according to a specific route
selection code or a specific route selection source code. If no parameters are given, it
means we want all trunk analysis data to be displayed.
2) ADD RTANA
If we want to add route analysis according to the example shown in Fig. 1-3, the
command would be:
ADD
RTANA•FRSC=1•CRSSC=0•CRUT=ALL•CADI=ALL•CCLRIN=ALL•CTR
AP=ALL•CTMX=0•CR=1•G
Where
•yRSC / ROUTE SELECTION•z
Necessary parameter. The routing attribute code corresponding to the destination code
(called prefix). Value range: {0~ 65535}.
•YRSSC / ROUTE SELECTION SOURCE•Z
OSB2A07-59
R2V610R002
Necessary parameter. The routing attribute code corresponding to a call source. Value
range:
0~ 65535}.
•YRUT / CALLER CATEGORY•Z
Necessary parameter. It means the category of the caller. This parameter indicates that
we could select route according to the category of the caller. For example, we can set
that a user in operator category makes a call during the busy hour, he could select the
reserved route .
Value range: {NRM, PRI, OPR, DAT, TST, ALL}, and respectively they represent
“ORDINARY”, “PRIOR”, “OPERATOR”, “DATA”, “TEST”, and “ALL
CATEGORIES”.
•YADI / ADDRESS INFORMATION•Z
Necessary parameter. Indicates the nature of the called prefix. This parameter
indicates that we could select route according to the called prefix's service attribute.
For example, we can set that international calls select a special route to keep service
quality.
Value range: {INTT, NATT, CITY, ALL}, and respectively they represent
“INTERNATIONAL TOLL”, “NATIONAL TOLL”, “LOCAL CALL”, and “ALL
CATEGORIES”.
•YCLRIN / CALLER ACCESS•Z
Necessary parameter. It indicates whether the caller is an ISDN subscriber or not.

Therefore it means that we could assign ISDN subscribers a special route other than
that of non-ISDN subscribers.
Value range: {ISDN, NONISDN, ALL}, and respectively they represent “ISDN”,
“NON ISDN”, and “ALL CATEGORIES”.
•YTRAP / TRANSMISSION CAPABILITY•Z
Necessary parameter. It indicates the transmission capability for ISDN calls.
OSB2A07-60
R2V610R002
Value range: {VOICE, UNLIMDATA, LIMDATA, AUDIO, SIGDATA, VIDEO,

ALL}, and respectively they represent “VOICE SERVICE”, “UNRESTRICTED
DIGITAL INFORMATION SERVICE”, “RESTRICTED DIGITAL
INFORMATION SERVICE”, “3.1KHZ AUDIO SERVICE”, “NON-LIMITED
DIGITAL SERVICE WITH SIGNAL TONE”, “VIDEO SERVICE” and “ALL
CATEGORIES”.
•YTMX / TIME INDEX•Z
Necessary parameter. It indicates the time index which is obtained through analyzing
the time index table. This parameter indicates that we could select route according to
different time of a day different day of a week.
Value range: {0~255}.
Necessary parameter. Indicates the route number selected according to the five key
columns. Value range: {0~65535}.
In most occasions, we distinguish route numbers only according to the route selection
codes. Therefore, to make the data more clear, usually we assign a same number to
both the route selection code and the route it relates to, for example, route selection
code 1 relates to route number 1, and route selection code 2 relates to route number 2.
•YISUPSL / ISUP AS PRIOR•Z
Optional parameter. It indicates the use of ISUP route.
Value range: {BEST, MUST, NOCHANGE}, in which BEST is the default value,
and
BEST means “PRIOR SELECTION”•|•|ISUP route will firstly be tried to use;
MUST means “NECESSARY”•|•|this call must use an ISUP route; and if ISUP
routes are unavailable, the call will fail;
NOCHANGE means “NO CHANGE”•|•|the routing will be going on as ordinary

without the consideration of ISUP routes..
OSB2A07-61
R2V610R002
3.10 Set Call Prefix
 Add the basic service prefixes which point to this route.
 Up to now we have defined route data and route analysis data. But such data
remains meaningless until there are some call prefixes bounding for this route. Use
the command LST CNACLD we can check the call prefixes already exist, and use the
command ADD CNACLD we could add the new inter-office call prefixes. The
command is used like this:
 ADD
CNACLD•FPFX=K•f555•CCSTP=BASE•CCSA=LC•CRSC=1•CMIDL=7•C
MADL=7•G
 Where parameteryPFXz means “CALL PREFIX”,•yCSTP•z means

“SERVICE CATEGORY”,yCSAz means “ ERVICE
S ATTRIBUTE”,
•yACSAz means “CUSTOM ATTRIBUTE”,yRSCz means “ROUTE
SELECTION CODE”, which should correspond to the newly added route, MIDL
means “MIN.LEN”, MADL means “MAX.LEN”, RCM means “RELEASE MODE”,
etc.
3.11 Collection of the Commands for Voice

Path Setting
3.11.1 Collection of the Commands for No7

Voice Path Setting
SET OFI :; Set local office information (Optional, because we will use this command
in link data setting)
ADD OFC :; Add an office direction
OSB2A07-62
R2V610R002
ADD SRT :; Add subroute
ADD N7TG :; Add No7 trunk group
MOD TGSRT:; Modify the relation between the trunk groups and the subroutes
(Optional)
ADD N7TKC :; Add No7 trunk circuits
ADD RT :; Add route
ADD TMIDX :; Add time index•iOptional•j
The system implies that time index 0 represents all time by default. So if no special
dynamic routing strategy is required(using different route at different time), this step
could be skipped, and time index 0 be used.
ADD RTANA :; Add route analysis
ADD CNACLD :; Add an outgoing call prefix
3.11.2 Collection of the Commands for CAS

Voice Path Setting
SET OFI :; Set local office information
ADD OFC :; Add an office direction
ADD SRT :; Add subroute
ADD N1TG :; Add CAS trunk group
MOD TGSRT:; Modify the relation between the trunk groups and the subroutes
(Optional)
ADD N1TKC :; Add CAS trunk circuits
ADD RT :; Add route
ADD TMIDX :; Add time index•iOptional•j
ADD RTANA :; Add route analysis
ADD CNACLD :; Add an outgoing call prefix
OSB2A07-63
R2V610R002
Section 4 CCS7 Link Data
OSB2A07-64
R2V610R002
To set CAS trunk data, we only need to define the voice path. But CCS7 trunk data is
different, it is composed of two parts, namely, voice channel data and signaling link
data. In this section, we will discuss the data setting for CCS7 signaling links, or the
so-called MTP data.
 Warning
MTP data should be set in the following sequence:
Local Office MTP MTP Link Table

Information MTP DSP Table Linkset
Table Table MTP Route Table
4.1 Set MTP DSP
1. General
The DSPs (destination signaling points ) to be defined here include all the
signaling points in the CCS7 network which are "visible" to the local office.
 Note
A signaling point is described as "visible" to the local signaling point if it is has

signaling links or voice channels directly connected to the local office.
The DSPs outline the topology structure of the local signaling network where
the local exchange signaling locates. DSPs could be divided into adjacent DSPs and
OSB2A07-65
R2V610R002
non-adjacent DSPs according to their comparative positions to the local SP, in which
those which have direct links connecting with the local office are adjacent DSPs and
those who don‟t (namely, those who only have direct voice paths towards the local
office) are the non-adjacent DSPs.
When a SP is added into the CCS7 signaling network where the local office
also locates, if it is “visible”, we have to add it as a DSP of the local office.
2. Related Commands

Display the maximum tuple number
LST MAXT
for CCS7 DSPs
Display the CCS7 DSPs already
LST N7DSP
defined
ADD N7DSP Add a CCS7 DSP
MOD N7DSP Modify a CCS7 DSP
RMV N7DSP Remove a CCS7 DSP
1) LST MAXT
Before adding a MTP DSP, we had better check the maximum tuple number assigned
to the MTP DSP table, so as to avoid defining a DSP index number which exceeds the
maximum value. This command could also be used to check the maximum tuple
numbers for other tables.
The command is used like this:
LST MAXT•FTID=TID160•CTP=SM•CMN=1•G
Where
•YTID / TABLE ID•Z
Optional parameter. Each table in the database which has been defined its maximum
tuple number has a corresponding ID number represented by this parameter. For
example, MTP Data Table is represented by “TID 160”.
OSB2A07-66
R2V610R002
If this parameter is not given, it means to query the maximum tuple number of all
tables that satisfying the other parameters.
•YTP / LOCATION OF THE TABLE•Z
Optional parameter. In the present version only one default choice is provided: SM
(switching module).
•YMN / MODULE•Z
Necessary parameter. Value range: {1~175}. Here an effective number has to be

givens.
2) LST N7DSP
-360Before adding a MTP DSP, we could use the command LST N7DSP to query
the DSPs already defined and the DSP indexes already in use so as to avoid redefining
a same DSP or reusing of a same DSP index number.
This command could be used to show information of all (specified) destination
signaling points or show all links that can reach the specified destination signaling
point, and it can be chosen whether to show the link information that is corresponding
to the DSP.
For example, if we want to show all links that can reach the destination signaling
point with the index 0, the command would be:
LST N7DSP : DPX=0 , SHLINK=YES ;
Where
•YDPX / DSP INDEX•Z
Optional parameter, range: {0~ 65534}. If DPX is not specified, the attributes of all
subroutes will be listed.
•YSHLINK / DISPLAY LINKS OF DSP•Z
Optional parameter. It indicates whether the links that can reach the destination
signaling point should also be displayed or not.
3) ADD N7DSP
If want to add a DSP according to the example shown in Fig.1-3, the command would
be:
OSB2A07-67
R2V610R002
ADD N7DSP•FDPX••0•CDPN•••gTO
555•h•CNPC•••gB05000•h•CNN••TRUE•CSTP••TRUE•CAPF••TR
UE•CLLS••0•G
Where
Necessary parameter, range: {0~ 65534}. If DPX is not specified, the attributes of all
subroutes will be listed.
•YDPN / DSP TITLE•Z
Necessary parameter. Assign a name to the DSP for easy recognition.
•YIPC / INTERNATIONAL CODE•Z,•YIP2C / INTERNATIONAL RESERVED

CODE•Z,•YNPC / NATIONAL CODE•Z,•YNP2C / NATIONAL RESERVED
CODE•Z
Optional parameter. They indicate the SPC of the DSP in the corresponding networks.
The value should be a string.
•YIN / INTERNATIONAL VALID•Z,•YIN2 / INTERNATIONAL RESERVED

VALID•Z,•YNN / NATIONAL VALID•Z,•YNN2 / NATIONAL RESERVED
VALID•Z
Optional parameter. They indicate the CCS7 signaling networks in which this DSP is
located. Range: {NO, YES}.
•YSTP / STP•Z
Optional parameter. It indicates whether the DSP is a STP (signaling transfer point) or
not. Range: {NO, YES}. And the default value is “NO”.
•YAPF / ADJACENT FLAG•Z
Optional parameter. It indicate whether this DSP is an adjacent DSP or not. Range:
{NO, YES}, and the default value is YES.
•YLSS / LINKSET SELECT•Z
OSB2A07-68
R2V610R002
 Indicates how the signaling service load towards one DSP is going to be
shared among the multiple signaling link sets. This column is actually the load
sharing mode mask of the signaling links at the link set level.
 Value range: {0~15}, or 4 bits when counted in binary. The default value for
this column is 4 "0". If there is only 1 linkset, then keep the default value; if 2 linksets
are provided, them we should choose one bit; if there are 3 or 4 linksets, we should
choose 2 bits; if the number of linksets is between 5 and 8, then 3 bits should be
chosen; and if the number of linksets equals to or is larger than 8, then all the 4 bits
have to be chosen. After the choice has been made, we should turn the binary 4 bits
into decimal then put the value here. For example, “0110” in binary is turned to “6” in
decimal.
 Since usually all the links towards the same adjacent DSP are grouped into
one link set, we could use the default value, 0.
4.2 Set MTP Linkset
1. General
Linkset is the collection of links connecting a DSP with the local SP. The
linksets for one DSP have to defined after the definition of the DSP.
2. Related Commands

Display the CCS7 linksets already
LST N7LKS
defined
LST MAXT
for linksets
ADD N7LKS Add a CCS7 linkset
MOD N7LKS Modify a CCS7 linkset
RMV N7LKS Remove a CCS7 linkset
OSB2A07-69
R2V610R002
When adding a MTP linkset, the corresponding adjacent DSP index has to be
specified. So we have to query the existence of this DSP at first. If it does not exist,
we have to define it beforehand.
1) LST N7LKS
Query the linksets already defined.
This command has no parameters. According to the results returned we could define a
new linkset number.
2) LST MAXT
Before adding a MTP linkset, we had better check the maximum tuple number
assigned to the MTP linkset table, so as to avoid defining a linkset number which
exceeds the maximum value.
Where
“TID162” represents the MTP linkset table.
3) ADD N7LKS
According to the example shown in Fig. 1-3, we should add linksets by the following
command:
ADD N7LKS•FLS••0•CLSN•••gTO
555•h•CAPX••0•CLKS••0•G
Where
•YLS / LINKSET•Z
Necessary parameter. It indicates the unique number within the local SP which is
assigned to the linkset.
•YLSN / LINKSET TITLE•Z
Necessary parameter. Assign a name to the linkset for easy recognition.
OSB2A07-70
R2V610R002
•YAPX / ADJACENT DSP INDEX•Z
Necessary parameter. It indicates the index number of the adjacent DSP on the other
end of the linkset. Range: {0~254}.
•YLKS / LINK SELECTION•Z
 Indicates how the signaling service load towards one adjacent DSP is going to
be shared among the multiple signaling links. This column is actually the load sharing
mode mask of the signaling links at the link level.
 Value range: {0~15}, or 4 bits when counted in binary. The default value for
this column is 4 "0". If there is only 1 link, then keep the default value; if 2 links are
provided, them we should choose one bit; if there are 3 or 4 links, we should choose 2
bits; if the number of links is between 5 and 8, then 3 bits should be chosen; and if the
number of links equals to or is larger than 8, then all the 4 bits have to be chosen.
After the choice has been made, we should turn the binary 4 bits into decimal then put
the value here. For example, “0110” in binary is turned to “6” in decimal.
4.3 Set MTP Route
1. General
After defining a MTP DSP, we should add the corresponding MTP route data.
MTP route is the path for sending signaling messages between two SPs. When adding
a MTP route, we have to know beforehand the related linkset number, priority,
signaling point code of the DSP (namely, the DPC), etc. So the related MTP linksets
and MTP DSPs has to be defined adding the MTP route.
2. Related Commands

LST N7RT Display the CCS7 routes already
OSB2A07-71
R2V610R002
defined
LST MAXT
for MTP routes
ADD N7RT Add a CCS7 route
MOD N7RT Modify a CCS7 route
RMV N7RT Remove a CCS7 route
1) LST N7RT
Query the MTP routes already defined.
MTP routes could be queried according to the DSP indexes. If no parameters are
specified, then all MTP routes will be shown.
2) LST MAXT
Before adding a MTP route, we had better check the maximum tuple number assigned
to the MTP route table, so as to avoid defining a MTP route number which exceeds
the maximum value.
Where
“TID161” represents the MTP route table.
3) ADD N7RT
According to the example shown in Fig. 1-3, we should add a MTP route by the
following command:
ADD N7RT•FRN•••gTO 555•h•CLS••0•CPR••0•CDPX••0•G
Where
Necessary parameter. Assign a name to the route for easy recognition.
OSB2A07-72
R2V610R002
Necessary parameter. It indicates the number of the link set via which the new route
could get to the DSP. Range: {0~ 65534}
Optional parameter. It indicates the priority level of such signaling route. For the
signaling routes bound for the same DSP, the difference in their priority level will
result in the signaling routes of higher priority level being used in priority to bear
signaling service, while the signaling routes of lower priority can bear signaling
service only when all the signaling routes of higher priority are unavailable.
Value range: {0~254}, of which 0 is the level of highest priority. Usually all link
routes bear the same priority level, so we could assign "0" priority to all link routes.
Necessary parameter. It indicates the DSP that the signaling route is bound for.
Range: {0~ 65534}.
4.4 Set MTP Link
1. General
MTP links are the physical signaling links which connects different SPs. After
adding the linkset we have to define the MTP links within it.
2. Related Commands

Display the CCS7 links already
LST N7LNK
defined
ADD N7LNK Add a CCS7 link
MOD N7LNK Modify a CCS7 link
RMV N7LNK Remove a CCS7 link
OSB2A07-73
R2V610R002
Before add a MTP link, we have to define the related linkset beforehand.
1) LST N7LNK
Query the MTP links already defined.
MTP links could be queried according to the SM number or linkset number. From the
query results we could learn about the links already in use.
2) LST MAXT
Before adding a MTP link, we had better check the maximum tuple number assigned
to the MTP link table, so as to avoid defining a MTP link number which exceeds the
maximum value.
Where
“TID161” represents the MTP link table.
3) ADD N7LNK
According to the example shown in Fig. 1-3, we should add a MTP link by the
following command:
ADD N7LNK•FMN••1•CLK••12•CLKN•••gTO
555•h•CSDF=SDF1•CNDF=NDF1•CC••144•CLS••0•CSLC••0•CSSLC
••0•G
Where
•YMN / MODULE•Z
Necessary parameter. It indicates the number of the module in which the MTP link is
located. Range: {0~ 175}.
•YLK / LINK NUMBER•Z
Necessary parameter. It indicates the physical number of the signaling link. Each
link's physical number is fixed according to the position of the signaling board and the
link's sequential number on the board, as illustrated in Fig. 1-2. Range: {0~39}.
OSB2A07-74
R2V610R002
•YLKN / LINK TITLE•Z
Necessary parameter. Assign a name to the link for easy recognition.
•YSDF / DIDDT•Z
Necessary parameter. Indicates the device identification of the digital trunk used to
carry the link.
Value range: {SDF1, SDF2, SDF3}, which respectively represent “TUP”, “ISUP” and
“IDT”, and iDT is adopted for RSM networking.
•YNDF / DIDNO7•Z
Necessary parameter. Indicates the device identification of the CCS7 signaling

terminal equipment (signaling board) used.
Value range: {NDF1, NDF2}, which respectively represent “NO7” and “LPN7”.
•YC / CIRCUIT•Z
Necessary parameter. Indicates the physical number of the trunk circuit used to carry
the signaling link, it could be derived using the formula:
Circuit number = DTF board number•~64 + the sequence number of the circuit on
the board
Necessary parameter. Indicates the signaling linkset where this signaling link is
located. Value range: {0~65534}
•YSLC / SLC•Z
Necessary parameter. Indicates the signaling link code (SLC) of the link. Value range:
{0~39
 Note
OSB2A07-75
R2V610R002
SLC is the logic number given to the signaling link within the signaling linkset. It is
used for the uniform management of the signaling link by the offices at both ends of
the signaling link. All the signaling links within a signaling linkset are uniformly
numbered, and the offices at both sides have to give identical code to the same circuit.
•YSSLC / SLC SEND•Z
Necessary parameter. Value range: {0~39}.
This column is designed especially for self-looping. For ordinary inter-office CCS7
trunk data, the value here should be the same as that in•ySIGNALING LINK
CODE•zcolumn; while under self-loop testing environment, the value of such field
should equal the•ySIGNALING LINK CODE•zof another signaling link within the
same signaling linkset, which is in self-loop with this signaling link.
Optional parameter. Indicates the priority level of the signaling links within the
signaling linkset. Those signaling links of higher priority will be used in priority to
bear signaling service, while the links of lower priority can bear signaling service
only when all the links of higher priority are unavailable. that may be used are always
used to bear service.
Value range: {0~254}, of which 0 is the level of highest priority. Usually all links
bear the same priority level, so we could assign "0" priority to all links.
•YSATF / SATELLITE FLAG•Z
Optional parameter. Indicates whether there are any satellite circuits connected.
Value range: {YES, NO}. Usually only the links from an international gateway
exchange may utilize satellite circuits, so for common signaling trunk groups we
could use the default value, "NO".
•YCBT / CONGESTION START•Z
Optional parameter. Indicates that transmission congestion will occur to such

signaling link, when the percentage of occupied transmission buffer zone of such
OSB2A07-76
R2V610R002
signaling link rises to the designated value. In the status of congestion, the signaling
message waiting for transmission on this link might be discarded.
Value range: {1~100}. And the default value is 80.
•YCET / CONGESTION END•Z
Optional parameter. Indicates that transmission congestion will end to such signaling
link, when the percentage of occupied transmission buffer zone of such signaling link
falls to the designated value.
Value range: {1~100}. And the default value is 70.
•YTC / TEST CODE•Z
Optional parameter. Indicates one byte of the testing code used in transmission of the
signaling link testing message (SLTM). In the present system, a string of test code
(repetition of such byte) with the length defined in the•yTESTING CODE
LENGTH•zwill be sent in a SLTM message.
Value range: {00•`FF} ( hexadecimal system input), and the default value is aa.
•YTCL / TEST CODE LENGTH•Z
Optional parameter. Indicates the length of the testing code used in SLTM message.
Value range: {1•`15}, and the default value is 10.
4.5 Collection of the Commands for No7 Link

Setting
SET OFI :; Set up local office information
ADD N7DSP :; Add destination signaling point
ADD N7LKS :; Add CCS7 linkset
ADD N7RT :; Add CCS7 route
ADD N7LNK :; Add CCS7 link
OSB2A07-77
R2V610R002
Section 5 Other Data
OSB2A07-78
R2V610R002
The contents in this section are divided into 2 parts: trunk group load, and added
signal.
5.1 Trunk Group Load
For outgoing trunk groups we can define such parameters as trunk occupation point,
changing the caller or called number before sending, etc. The setting of trunk group
load data includes two parts: first, setting trunk group load, then setting trunk group
load index.
5.1.1 Set Trunk Group Load
1. General
Trunk group load data has to be set before trunk group load index data. But
the number conversion used in trunk group load has to be defined before setting trunk
group load data.
2. Related Commands

ADD DNC Define a number conversion
Display the trunk group load already
LST TGLD
defined
ADD TGLD Add a trunk group load
MOD TGLD Modify a trunk group load
RMV TGLD Remove a trunk group load
OSB2A07-79
R2V610R002
01) ADD DNC

Through using the command LST DNC to query the number conversion already
defined, we could decide whether more number conversions have to be defined or not.
If we want to add a number conversion, for example, change the number prefix from
555 to 444, the number conversion command should be:
ADD
DNC•FDCX=1•CDCT=MOD•CDCP=0•CDCL=3•CND=K•f444•G
Where the parameter DCX represents “CHANGE INDEX”, DCT represents

“CHANGE TYPE”, DCP represents “CHANGE POSITION”, DCL represents
“CHANGE LENGTH”, and ND represents “NEW NUMBER”.
2) LST TGLD
Before adding a trunk group load, we had better query the trunk group loads already
defined.
We could query the trunk group loads according to the SM number and trunk group
load index. If no parameters are specified, the information about all trunk group loads
will return.
3) ADD TGLD
To add a new trunk group load, we should use the following command:
ADD TGLD•FMN=1•CCLI=1•CTOP=7•CRI=0•CEI=1•G
Where
•YMN / MODULE•Z
Necessary parameter. It indicates the number of the module that housing the trunk
group.
•YCLI / BEARER INDEX•Z
Necessary parameter. It indicates the index number of call carrier.
•YTOP / TRUNK OCCUPY POINT•Z
OSB2A07-80
R2V610R002
Necessary parameter. It indicates how many digits of the called number should
receive before the switch should send the trunk occupation signal. Value range:
{0~24}.
 Note
1. Before adding the corresponding trunk group load, the default trunk
occupation point would be the larger value of•yMinimum number length•zof the
called number analysis table and•yLength of number before analysis•zof the call
source table.
2. To decrease useless trunk occupation, usually we assign the trunk occupy

point for local calls the same number as the length for the called number.
•YRI / CALLER CHANGE IDX•Z,•YEI / CALLED CHANGE IDX•Z
Necessary parameters. They indicate the mode of caller / called number change before
the number is sent to the next office. The indexes are defined by using the command
ADD DNC.
Value Range: {0~255}
•YATN / DIRECT NATIONAL ROUTE•Z
Optional parameter. It has nothing to do with CCS7. And for R2 signaling, it is only
used when the local office is an international office. It means if the next office is an
international transit office of the destination country, then we should set•yATV•zas
“YES”, otherwise it is always “NO”.
•YIHE / IN HES•Z
Optional parameter. Indicating whether the incoming call echo suppressors have been
installed or not. Value range: {NO, YES}.
OSB2A07-81
R2V610R002
5.1.2 Set Trunk Group Load Index
1. General
To make the trunk group load data effective, we have to define trunk group
load indexes. But the trunk group and call source code also have to be defined
beforehand.
2. Related Commands

Display the trunk group load index
LST TGLDIDX
already defined
ADD TGLDIDX Add a trunk group load index
MOD TGLDIDX Modify a trunk group load index
RMV TGLDIDX Remove a trunk group load index
01) LST TGLDIDX

Through using this command, we could decide whether the trunk group load index we
need has been defined or not.
Trunk group load index could be queried according to trunk group number and call
source code, etc.
2) ADD TGLDIDX
If we want to add a trunk group load index 1 for trunk group 0, call source code 0,
dial number set 0, call prefix 555, the command should be:
ADD TGLDIDX•FTG=1•CCSC=0•CDS=0•CCP=K•f555•CCLI=0•G
Where
OSB2A07-82
R2V610R002
Necessary parameter. It indicates the serial number of the outgoing trunk group.
Value range: {0~ 65535}.
Necessary parameter. It refers to the call source code of the calling party such as the
user or the incoming trunk.
Value range: {0~0, 65535}
•YP / DNSET•Z
Necessary parameter. It refers to the dial number set that the called number belongs
to.
Value range: {0~4}.
•YPFX / CALL PREFIX•Z
Necessary parameter. It indicates the prefix of the called number.
•YCLI / BEARER INDEX•Z
Necessary parameter. It acts as an index to inquire the trunk group load data, and from
what we have discussed above we could see that it could be assigned with different
values according to the trunk group number, the call source code of the caller, as well
as the dial number set and call prefix of the called number.
5.2 Added Signal
Added signals are used to regulate some parameters of CAS and CCS7 signaling for
the proper signaling cooperation with the opposite office. Suppose in the example of
Fig. 1-3, it is required that office 222 send CLD to office 555 automatically, then in
office 222 we have to set added signal data.
1. General
OSB2A07-83
R2V610R002
To set added signal for a call prefix, we have to define the prefix as well as the
related call source code beforehand.
2. Related Commands

Display the added signal already
LST AUSSIG
defined
ADD AUSSIG Add an added signal
MOD AUSSIG Modify an added signal
RMV AUSSIG Remove an added signal
1) ADD AUSSIG
If in the example of Fig. 1-3, it is required that office 222 send CLD to office 555
automatically, then the command would be:
ADD
AUSSIG•FPFX=K•f555•CP=0•CCSC=0•CSA6=TRUE•CSA6P=3•CSRD=T
RUE•G
Where
•YPFX / CALL PREFIX•Z
Optional parameter. It indicates the prefix of the called number.
•YP / DNSET•Z
Optional parameter. It refers to the dial number set that the called number belongs to.
Value range: {0~ 4}, and the default value is 0.
Necessary parameter. It refers to the call source code of the calling party such as the
user or the incoming trunk.
Value range: {0~ 65535}.
OSB2A07-84
R2V610R002
•YSA6 / REQ CALLER NUMBER•Z
Optional parameter. Value range: {NO, YES}, and the default value is NO.
It indicates when receiving a incoming call whether "CLI request" message (in CCS7
signaling this message is GRQ and in R2 signaling this message is A5 )should be sent
to the opposite office so as to ask for caller number and type.
In the example of Fig. 1-3, local office 222 is set to automatically send CLI to office
555, therefore, when office 222 transfers a incoming call towards office 555(a tandem
call) it should ask for CLI, and this column should be set as "YES".
•YSA6P / REQ CALLER POSITION•Z
Optional parameter. It indicates how many digits of the called number should receive
before the switch should send the CLI request. Value Range: {0~15}.
This column is effective only when the parameter•ySA6•z is "YES", and only for
CAS signaling. For CCS7 signaling this column is useless, but it should be
given a valid number such as 3.
•YSRD / SEND CALLER NUMBER•Z
Optional parameter. It indicates whether CLI should be sent to the opposite office
automatically or not.
Value range: {YES, NO}, and the default value is NO.
•YRDTF / TRANSLATE CALLER NUMBER•Z
Optional parameter. Value range: {YES, NO}, and the default value is NO.
It indicates whether the CLD should be translated or not during the signaling
cooperation. For example, when A calls for B, if B has registered call forwarding and
transfers the call to C, then if C asks for CLI, usually the caller number of A is sent,
but if•yRDTF•z is "YES", then the caller number of B will be sent.
•YSDD / SEND ORIGINAL CALLED•Z
Optional parameter. Value range: {YES, NO}, and the default value is NO.
OSB2A07-85
R2V610R002
The called number may got changed during call connection. This parameter indicates
whether the original called number (before transform) should be sent to the opposite
office.
•YERF / EMERGENCY CALL EXCEL•Z
Optional parameter. It indicates whether it is necessary to check the related call rights
for this call. If this flag is “YES”, it means that this call is an “emergency call” and it
will be tried to put through with no consideration of the call rights; but if the flag is
“NO”, the related call rights will be checked beforehand.
Value range: {YES, NO}, and the default value is NO.
•YMIS / MINCODE OCCUPY TK•Z
Optional parameter.
Value range: {YES, NO}, and the default value is NO. If it is “YES”, it means that
trunk occupation will not happen until the switch has received the minimum length of
called number as defined in the Called Number Analysis Table.
5.3 Tandem Information
1. General
A tandem/transit call connection is made up of an incoming trunk group and

an outgoing trunk group. Before adding CAS trunk transit, the CAS incoming trunk
groups and CAS outgoing trunk groups used must be defined firstly.
2. Related Commands

LST N1TDM Display CAS trunk tandem
ADD N1TDM Add CAS trunk tandem
MOD N1TDM Modify CAS trunk tandem
RMV N1TDM Remove CAS trunk tandem
OSB2A07-86
R2V610R002
01) ADD N1TDM

For example, if we want to add CAS trunk transit, with incoming trunk group 1,
outgoing trunk group 2, transit mode "extension", and extension bit length 3, then the
command would be:
ADD N1TDM: IGN=1, OGN=2, TM=PRL, PP=3;

Where
•YIGN/INCOMING TRUNK GROUP•Z
Necessary parameter. The trunk group number of the incoming trunk. Value
range: {0~ 65535}.
•YOGN/OUTGOING TRUNK GROUP•Z
Necessary parameter. The trunk group number of the outgoing trunk. Value
range: {0~ 65535}.
•YTM/TANDEM MODE•Z
Necessary parameter, indicating the tandem mode adopted. Value range:

{NONE, PRL, RES, TRAN}, which represent “no tandem”, “prolong”, “resend” and
“transfer” respectively•C and:
Prolong•| After receiving enough message from the incoming trunk to

determine the route office direction, connect an outgoing trunk circuit with the
incoming trunk circuit, and transfer the rest of the message on the newly setup
connection. It is an end-to-end mode;
Resend•| After receiving enough message from the incoming trunk to

determine the route office direction, connect an outgoing trunk circuit with the
incoming trunk circuit, and transfer all the message from the beginning on the newly
setup connection. It is an end-to-end mode;
OSB2A07-87
R2V610R002
Transfer•|store and transfer the register signaling received from an incoming

trunk circuit onto the outgoing trunk.
•yPP/PROLONG LENGTH•Z
Optional parameter. Value range: {0~ 24}. Effective only for the "Prolong"
mode. It indicates that in the prolong mode how many digits of a number should be
received before the connection of an outgoing trunk with the incoming trunk would
happen.
OSB2A07-88
R2V610R002
Section 6
OSB2A07-89
R2V610R002
Related Maintenance
6.1 Trunk Data Setting Criteria
 Trunk data, either the voice channel part or the signaling link part, should be set in
sequence. For voice channel data part, usually we define the office direction first, then
the subroutes, trunk groups, trunk circuits, route and route analysis data are set in
order. While for MTP data should be set in the order as shown in the following figure:
Local Office MTP MTP Link Data

Information MTP DSP Data Linkset
Data MTP Route Data
 To delete or modify the data for a DSP, office direction, you should take the
following steps: first deactivate all the signaling links towards this DSP, so that the
DSP becomes unreachable, then delete or modify the related data, and finally
reactivate the signaling links.
 To delete a subroute, the trunk groups belonging to it have to be deleted

beforehand, and the routes using this subroute also have to change their data
beforehand so as to no longer use the subroute.
 To delete a trunk group, the trunk circuits belonging to it have to be deleted

beforehand. And after the deletion, the trunk group load indexes relating to it are also
deleted.
6.2 Maintenance of CCS7 Trunk System
In the maintain subsystem, such functions using GUI as tracing in real time the CCS7
information, administering CCS7 link, inquiring CCS7 state, setting CCS7 pseudo
OSB2A07-90
R2V610R002
message, etc. are provided. And in the MML system, the corresponding MML
commands are also provided.
6.2.1 NO.7 Signaling Tracing
1. Functional description
Trace the sending, receiving and handling of MTP, TUP and ISUP
information of one NO.7 link. Layer 2 and Layer 3 information of MTP can be traced,
and a certain filtering mechanism is provided to sort out the information that you want
to observe. A certain size of memory buffer is provided to store and look over
messages.
The system also provide online explanation of the CCS7 messages. Select a
message in the tracing window with the mouse, then press the “Enter” key or double-
click the message with your mouse, a detailed explanation of the message will appear.
The function of NO.7 signaling trace is a very important tool for locating
faults and check data during the equipment installation and routine maintenance.
01) ACT N7STRAC•FActivate NO7 tracing

The procedure of using this command should be like this:
a. Display all CCS7 links so as to choose a link to trace:
The command to be used: LST N7LNK
b. Activate the link tracing for link No.4 of switching module 1, and check the TUP
and ISUP messages.
c. The command is used like this:
ACT N7STRAC•FMN=1•CLNK=4•CMSG=TUP-1 &ISUP-1•G
OSB2A07-91
R2V610R002
In which parameter•yMN•z means the switch module number,•yLNK•z

means the link number,•yMSG•z means message type, we can choose TUP or ISUP
or all of them,•yCIC•z means the CIC code of a trunk circuit, using it we can
choose to trace the messages for one specific circuit.
2) STP TRAC•FStop all NO7 tracing
This command will stop all trace commands running in the current workstation,
including subscriber trace, No.7 trace, trunk trace, and port signaling etc.
 Attention 
1. A workstation can only stop traces started by itself.
2. This command will stop ALL trace commands, it could not work on a specific
link. So be careful when using it.
6.2.2 NO.7 Signaling Link Management
Provides active, deactive, management inhibit, and uninhibited functions. The

returned information indicates whether the execution of the command is a success or a
failure.
When a link is in an unstable status, on fearing that the calls carried by it may
be unable to arrive at the other side safely, we could use "inhibit" to prevent calls
from using this link. And at the same time we could use "NO7 signal trace" to observe
the messages (such as SLTM and SLTA) carried by the link to locate the problem.
When the link returns to normal function, we could "uninhibited" the link.
2. Example of Usage
1) ACT N7LNK•FActivate a NO7 link

For example, if we want to activate the 4th link of SM1, the command would be:
ACT N7LNK•FMN••1•CLNK••4•G
OSB2A07-92
R2V610R002
In which•yMN•z means SM number,•yLNK•z means the link number.
2) DEA N7LNK•FDeactivate a NO7 link

3) INH N7LNK•FInhibit a NO7 link
4) UIH N7LNK•FUninhibit a NO7 link
6.2.3 MTP Pseudo Message
 The function can generate MTP level two pseudo messages and provide them
for the switch whose ability to recognize and handle such messages can thus be
verified.
 Warning
The function is designed only for debugging and testing personnel. The normal
operation of the switch will be affected if fatal messages are input.
6.2.4 Query the Related States in NO7
 The function can be used to inquire the link state, destination state, route state
of CCS7.
2. Example of Usage
1) DSP N7LNK•FQuery a NO7 link state

2) DSP N7DPC•FQuery a NO7 DPC state
3) DSP N7RT•FQuery a NO7 route state
6.2.5 NO7 Signaling Circuit Operation
OSB2A07-93
R2V610R002
Provides operation of TUP and ISUP circuits, including reset circuit, stop
reset, block circuit, stop block, open circuit, stop open, continuity test, stop continuity
test, inquiry system, reset board, inquire circuit state. The function can operate either
on a single circuit or on a group of circuits, but 32 circuits at most can be operated at
the same time.
2. Example of Usage
1) DSP N7C•FQuery a NO7 trunk circuit

2) RST N7C•FReset a NO7 trunk circuit
3) STP N7C•FStop resetting a NO7 trunk circuit
4) BLK N7C•FBlock a NO7 trunk circuit
5) SBL N7C•FStop blocking a NO7 trunk circuit
6) UBL N7C•FUnblock a NO7 trunk circuit
7) SUL N7C•FStop unblocking a NO7 trunk circuit
8) STR N7COT•FStart a NO7 trunk circuit continuity test
9) STP N7COT•FStop a NO7 trunk circuit continuity test
6.2.6 Display Links According to DPC
MTP links are used to carry the messages between two SPs. Usually when
TUP or ISUP calls could not be successful, we could use this function to check the
state of all MTP links coming to the specific DSP.
2. Example of Usage
1) DSP N7DLNK•F Display links according to DPC

For example, if we want to query the state of all links connecting to the DSP whose
DPC in the national network is “022222”, the command would be:
DSP N7DLNKFNETIDCNCDPCCODE=”222222”G
Where•yNETID•z is the network indicator, and•yDPCCODE•z is the DPC.
OSB2A07-94
R2V610R002
6.3 Maintenance of CAS Trunk System
MML commands for maintaining CAS trunk system are also provided.
6.3.1 CAS Signaling Tracing
In some conditions, the status changes of the channel associated trunk circuit
and the signals sent on trunk circuits should be traced. By tracing the real-time
connection process of trunks, the cause of connection failure can be found and the
problems can be solved timely. This operation can be used to trace multiple trunk
circuits, with maximum of 32. This command can only trace channel associated
digital trunk.
1) ACT N1STRAC•FActivate CAS DT tracing

For example, to trace the channel associated digital trunk with channel number of 129
in module 1, the command is as follows:
ACT N1STRAC: MN=1, CHNO=129;
To trace the channel associated digital trunk with channel numbers from 129 to 159 in
module 1, the command is as follows:
ACT N1STRAC: MN=1, CHNO=129&&159;
Return value: 0 indicates success.
In the command, MN stands for module number, and CHNO for channel number.
2) STP TRAC•FStop all tracing
This command will stop all trace commands running in the current workstation.
OSB2A07-95
R2V610R002
6.3.2 CAS Circuit Management
Provides various operations on the CAS circuits, including circuit query,

blocking, unblocking, and reset, etc. And the command could either operate on a
single circuit, or on a group of circuits.
2. Example of Usage
1) DSP N1C •FDisplay circuit state

When find out if the circuit is in normal state, if it is usable or if it has been properly
blocked or reset according to the commands from the maintenance persons, you need
to check the states of the circuits, in order to find and solve problems. The states of
single or multiple circuits can be checked, or you can check the circuits with the given
state.
For example, if we want to display channel 64 of module 1, the corresponding MML
command is as follows:
DSP N1C: MN=1, CDT=BSN, BDID=DSL, BSN=64;
2) RST N1C •FReset circuits
In some conditions, a channel associated trunk circuit can not recover automatically
since it might be in an unavailable state, and this channel associated trunk circuit
should be reset to recover to start status.
For example, if we want to reset the channel associated trunk channel with channel
number 129 in module 1, the command is as follows:
RST N1C: MN=1, CDT=BSN, BDID=DT2, BSN=129;
Where
•yCDT/CODING TYPE•z
Necessary parameter. Value range: {BSN, PSN, TELCODE}, which stand for
“CHANNEL NUMBER”, “PORT NUMBER”, and “TELEPHONE NUMBER”
respectively.
•yBDID/BSN DEVICE TYPE•z
OSB2A07-96
R2V610R002
Optional parameter. Value range: {ASL, DSL, DT2, PRA, PHI, DTMF, MFC, CT0,
ETS, DMC, DTR, SPT, DIU, IDT, V5DSL, V5PRA, V5PHI, DIN, COCK, DT5,
DTT, RSD5}. And in this example we choose “DT2”.
•yBSN/CHANNEL NUMBER•z
Optional parameter. Value range: {0~6687}.
3) BLK N1C •FBlock circuits
When a channel associated trunk circuit is unavailable, if this channel associated
trunk circuit is selected during calls, the calls will not be connected since the channel
associated trunk is unavailable. To avoid such a condition, the unavailable channel
associated trunk circuits are usually blocked, to ensure that this circuit will not be
selected again. Wait until this circuit recovers to normal condition, then unblock it.
For example, if we want to block the channel associated trunk circuits with channel
numbers from 128 to 159 in module 1.
The command is as follows:
BLK N1C: MN=1, CDT=BSN, BDID=DT2, BSN=128&&159;
4) UBL N1C •FUnblock circuits
The blocked circuits should be unblocked when the blocked channel associated trunk
circuit recovers to be available, so that it can be selected by calls, avoiding waste of
channel associated trunk resources.
For example, if we want to unblock the channel associated trunk circuit with channel
number 129 in module 1, the command is as follows:
UBL N1C: MN=1, CDT=BSN, BDID=DT2, BSN=129;
6.4 Dynamic Call Trace
The function is used to trace the real time connect process of user or CCS7 /
CAS trunk circuit. It is used to trace subscriber's realtime connection process to find
out the reason of connection failure. The function is very useful for advanced
subscribers who know the exchange connection mechanism. You can trace the
concurrent connection of the specified, related and the third party subscriber or trunk.
OSB2A07-97
R2V610R002
2. Example of Usage
1) ACT CALLTRAC•FActivate Call Trace

This command is used to trace subscriber's realtime connection process to find out the
reason of connection failure. The function is very useful for advanced subscribers
who know the exchange connection mechanism. You can trace the concurrent
connection of the specified, related and the third party subscriber or trunk.
For example, if we want to track the connection state of the local subscriber circuit
with phone number 8888800, the command would be:
ACT CALLTRAC: MN=1, CDT=TELCODE, LOC=LOCAL, DN=K'8888800 ;
Where
•yMN•zmeans module number;
•YCDT/CODING TYPE•Z
Necessary parameter. Indicating the code we use to specify the user or trunk circuit
we want to trace. Value range: {BSN, USN, TELCODE}, which represent “channel
number”, “subscriber internal code” and “telephone number”.
•yUID/SUBSCRIBER TYPE•Z
Optional parameter. Value range: {WIRED, V5, ETS, DMC}.
•yUSN/SUBSCRIBER INTERNAL CODE•Z
•yPFXS/DNSET•Z
•yDN/TELEPHONE NUMBER•Z
Optional parameter.
•yDID/DEVICE TYPE•z
Optional parameter. Value range: {ASL, DSL, PRA, PHI}.
•yLOC/TYPE•Z
Optional parameter. Value range: {LOCAL, AN}.
•yBSN/CHANNEL NUMBER•Z
2) ACT TKTRAC•F Activate Trunk Trace
OSB2A07-98
R2V610R002
This command is used to trace trunk's realtime connection process to find out the
reason of connection failure. The function is very useful for advanced subscribers
who know the exchange connection mechanism. You can trace the concurrent
connection of the specified, related and the third party subscriber or trunk.
For example, if we want to activate the trunk trace of channel 4 in module 1, the
command would be:
ACT TKTRAC: MN=1, DID=TK, BSN=4;
Where
•yMN/MODULE•z
Necessary parameter.
•yDID/DEVICE TYPE•Z
Necessary parameter. Value range: {DT, TUP, ISUP, ETS, DMC}.
•yBSN/CHANNEL NUMBER•z
Necessary parameter. Value range: {0~65535}.
6.5 Assigned Trunk Line Call
Special trunk line call is an important tool for the maintenance of trunk system. It
could make the voice channel to be carried on a fixed trunk circuit, either a CCS7
trunk circuit or a CAS outgoing trunk circuit.
The realization of special line call involves three steps:
1. Use the command MOD ST to change the•yUTP/SUBSCRIBER TYPE•zof

the caller into "TEST";
e.g., MOD ST: D=K'222002, UTP=TST;
2. Use the command ADD CNACLD to add a call prefix “*66*”, and define
its•yCSTP/SERVICE CATEGORY•zas "NEW/SUPPLEMENTARY
SERVICE",•yCSA/SERVICE ATTRIBUTE•zas "SPL/ASSIGNED TRUNK LINE
CALL",•yMIN.LEN/MINIMUM NUMBER LENGTH •zas “4”, and•yMAX.LEN
/ MAXIMUM NUMBER LENGTH•zas "24";
OSB2A07-99
R2V610R002
namely,
ADD CNACLD: PFX=K'*66*, CSTP=NEW, CSA=SPL, MIDL=4,

MADL=24;
3. Dial *66*MN*A*TTTT#PQRABCD# (e.g. *66*01*0*0003#222 0001#),

where 'MN' is the module number, requiring two digits; 'A' is the indicator, requiring
one digit, and the value range being {0~2}, in which 0 represents inter-office trunk
circuit, 1 represents iDT circuit, and 2 representing OPT circuit; 'TTTT' is the circuit
number appointed (namely, the special line), requiring four digits; 'PQRABCD' is the
called number; and the second '#' means the end of dialing.
OSB2A07-100
R2V610R002
Append
OSB2A07-101
R2V610R002
ix The Difference Between ISUP Trunk Data and

TUP Trunk Data
The data setting procedure mentioned in the above two sections applies for both TUP
data and ISUP data. In summary, the differences in setting ISUP trunk and TUP trunk
lie in the following points:
1. Difference in hardware
For ISUP, the signaling board used have to be LPN7, NO7 board do not
support ISUP; while for TUP, both LPN7 board and NO7 board could be used.
2. Difference in data
(a) For ISUP, the “card type” of the DTF board used have to be set as “ISUP”,
while that for TUP has to be “TUP”.
(b) In NO7 trunk group data (for example, in the command ADD
N7TG),yCT/Circuit Typezfor ISUP should be “ISUP”, while that for TUP should
be “TUP”;
(c) In NO7 link data (for example, in the command ADD

N7LNK),•ySDF/DIDDTzfor ISUP should be “ISUP”, while that for TUP should
be “TUP”.
OSB2A07-102
Summary
OSB2A07-103
This course introduces the setting of inter-office trunk data using CCS7 signaling, as
well as the maintenance methods.
Trunk data, either the voice channel data or the MTP link data, has to be set
sequentially.
OSB2A07-104
Exercises
OSB2A07-105
On-class Exercises
3. The load distribution among trunk circuits is jointly determined by the module
searching queue in the subroute, the group selecting mode preset in the subroute data,
the relative priority level and availability of the trunk group, and the circuit selecting
mode preset in trunk group data. Please look at the following picture and tell which
command corresponds to the process listed in each block, as well as the function of
each command.
Route analysis
Route Subroute selection
Trunk module selection
Trunk group selection Circuit selection
4. The numbering of C&C08 data has 4 modes: over the whole network ,between
two offices, over the office, and within the module. Please tell the numbering mode
used by route number, subroute number, trunk group number, office direction
number, trunk circuit number, CIC, DPC, DSP index, linkset number, link number
and SLC.
After-class Exercises
1. When theyCircuit typezfor a trunk group is “TUP” or “ISUP” and

theyCircuit selection modezis “Master / slave”, then which principle should we
follow when setting the•yMaster•zflags of the corresponding trunk circuits? And
OSB2A07-106
should CIC be coded from 0? What does it mean when the•yStatus•zof a trunk
circuit is labeled as “Uninstall”?
Hands-on Exercises
1. Add a CCS7 office direction, and enable the subscribers in both offices to
make successful inter-office calls.
2. Use “dynamic call trace” to follow the complete process of a inter-office call
connection, find out the trunk circuit used to carry the voice.
3. Set data so that CLI is voluntarily sent during CCS7 inter-office call
connection.
Tips: Use added signal data.
4. Trace the messages transferred on a signaling link.
5. Perform special line call, and trace the call connection to check whether the
appointed circuit is used.
6. Query the status of the circuits of a trunk group.
7. Inhibit a trunk circuit, observe the phenomenon, and them uninhibit it.
8. Deactivate a trunk circuit, observe the phenomenon, and them activate it.
9. Perform NO7 state query: Query the state of a signaling link, that of a DSP, as
well as that of a route
10. Query a link's state by DPC.
11. Add a DSP .
OSB2A07-107
Key to Exercises
OSB2A07-108
Keys to After-class Exercises
12. The•yMaster•zflag assigned to the same circuit by the two offices at

both sides should be different, namely if we give its master control right to one
office, then the office at the other end should be given slave control right over
this circuit. Usually we assign the master control rights according to the circuit's
CIC number : if the CIC number is even then its master control right is given to
the office which has larger SPC (Signaling point code), and if the CIC number is
odd then its master control right is given to the office which has smaller SPC.
It is not necessary for CICs to start from 0. They are acceptable as long as
the CICs assigned to a circuit by both sides are equal and within the value range
of {0•`212 -1}.
The circuit corresponding to timeslot 0 of each PCM system is fixed to be

used for transmitting synchronization signal, therefore its status should be set as
“uninstall”.
OSB2A07-109
Contents
cx
Course Description
1
Course Overview
1
Course Objectives
1
Section 1 Overview
2
1.1 The Related Hardware

2
1.2 Related Concepts

6
1.2.1 Office Direction, Adjacent SP and

NOn-adjacent SP
6
1.2.2 Route and subroute

7
1.2.3 Route Selection Source Code and

Route Selection Code.
9
cxi
1.3 Classification of the Commands

10
1.3.1 Commonly Used Commands

10
1.3.2 Commands not Commonly Used

12
1.3.3 Other Commands Involved

13
1.4 Command Query Order

13
Section 2 Preparatory Data

17
2.1 Set Call Source

17
2.2 Set Time Index

20
Section 3 Voice Channel Data

23
cxii
3.1 Set Local Office Information

23
3.2 Set Office Direction

27
3.3 Set Subroute

31
3.4 Set CCS7 Trunk Group

34
3.5 Set CAS Trunk Group

48
3.5.1 Set Line/Register Signal/Command

Conversion
48
3.5.2 Set CAS Trunk Group Data

50
3.6 Set CCS7 Trunk Circuit

57
3.7 Set CAS Trunk Circuit

62
cxiii
3.8 Set Route

63
3.9 Set Route Analysis

67
3.10 Set Call Prefix

70
3.11 Collection of the Commands for Voice

Path Setting
71
3.11.1 Collection of the Commands for No7

Voice Path Setting
71
3.11.2 Collection of the Commands for CAS

Voice Path Setting
71
Section 4 CCS7 Link Data

73
4.1 Set MTP DSP

73
cxiv
4.2 Set MTP Linkset

78
4.3 Set MTP Route

80
4.4 Set MTP Link

82
4.5 Collection of the Commands for No7 Link

Setting
87
Section 5 Other Data

88
5.1 Trunk Group Load

88
5.1.1 Set Trunk Group Load

88
5.1.2 Set Trunk Group Load Index

91
5.2 Added Signal

93
cxv
5.3 Tandem Information

96
Section 6 Related Maintenance

99
6.1 Trunk Data Setting Criteria

99
6.2 Maintenance of CCS7 Trunk System

99
6.2.1 NO.7 Signaling Tracing

100
6.2.2 NO.7 Signaling Link Management

101
6.2.3 MTP Pseudo Message

102
6.2.4 Query the Related States in NO7

102
6.2.5 NO7 Signaling Circuit Operation

103
cxvi
6.2.6 Display Links According to DPC

103
6.3 Maintenance of CAS Trunk System

104
6.3.1 CAS Signaling Tracing

104
6.3.2 CAS Circuit Management

105
6.4 Dynamic Call Trace

107
6.5 Special Line Call

109
Appendix The Difference Between ISUP

Trunk Data and TUP Trunk Data
111
Summary
112
Exercises
113
cxvii
Key to Exercises
116
cxviii
Course OSW0111 Primary User Data
Issue 1.0 OVSV610R003
OSB2A03- 119
Course OSW0111 Primary User Data
Issue 1.0 OVSV610R003
Course OSB2A07
OSB2A03- 120

2-15.OSB2A07 Trunk Data

Uploaded by

Document Information

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

2-15.OSB2A07 Trunk Data

Uploaded by

Copyright:

Available Formats

Course Description

After the course is completed, the trainees should be able to

 Understand the setting of CCS7 (TUP or ISUP) trunk data

 Understand the data setting of CAS trunk data

 Use the related maintenance methods

1. The related hardware

2. The concepts of route, subroute,, office direction, adjacent SP, non-

3. The related commands.

1.1 The Related Hardware

 The connection between digital trunk boards (DTF) from different

 Each DTF board has 2 PCM systems, providing totally 64 circuits.

 Connection of 75 ƒ¶coaxial cables: There are altogether 64 radio frequency

Figure 1-1 Sketch map of the connection of 75 ƒ¶ trunk cables

Config Data Setting of DTF board

Indicator lights on the signaling boards

1.2 Related Concepts

Fig. 1-3 An example of inter-office networking

1.2.1 Office Direction, Adjacent SP and Non-

1.2.2 Route and subroute

2. Subroute is unidirectional, always starting from the local office.

1.2.3 Route Selection Source Code and Route

As for route selection code, it corresponds to called number or prefix, so different

1.3 Classification of the Commands

1.3.1 Commonly Used Commands

 Voice channel data

 Signaling link data

For CAS signaling system, only voice channel data is involved.

1. Voice Channel Data

3) ADD SRT: Set up the subroutes coming to different offices

6) ADD RT: Set up the route corresponding to the subroutes

2. A subroute is composed of trunk groups, which might be distributed in different

2. Signaling Link Data

The linksets to be used are decided by the above two steps.

1.3.2 Commands not Commonly Used

 ADD LSND/LRPT/REGSND/REGRPT: Set up CAS signaling conversion.

1.3.3 Other Commands Involved

1.4 Command Query Order

1. Voice Channel Part

Route Subroute selection

Trunk module selection

Trunk group selection Circuit selection

Fig. 1-4 Procedure of load distribution among the trunk circuits

Route •]•¨ Route analysis data

2. Signaling Link Part

 SET OFI: Set up local office information

 MTP DSP data: Decide the linkset number.

 MTP Linkset data: Decide the link number.

 MTP route data: Decide the priority of the linkset.

 MTP link data•FDefine the attributes of the CCS7 signaling links.

Section 2 Preparatory Data

 Related preparatory data

2.1 Set Call Source

Command Name Command Function

3. Explanation of the Commands

ADD CALLSRC: CSC=0, PRDN=1, P=0, RSSC=0, FSC=0, DCF=YES, DCX=1,

•yCSC / CALL SOURCE•z

Necessary parameter, range: {0~ 65535}.

Call source code number.

•YPRDN / PRERECEIVE NUMBER DIGITS•Z

Optional parameter, range: {0~9}, default value is 1.

Optional parameter, range: {0~4}, default value is 0.

The dial number set the call source belonging to.

•YRSSC / ROUTE SELECTION SOURCE•Z

Optional parameter, range: {0~65535}, default value is 0.