You are on page 1of 254

Administration of the Inter-Exchange Circuit Network

Siemens

Administration of the Inter-Exchange


Circuit Network

Contents
1
1.1
1.2
1.3
2
2.1
2.2
2.3
2.4
2.5
2.6
2.7
3
3.1
3.2
3.3
4
4.1
4.2
4.3
4.4
5
5.1
5.2
5.3
5.4

Database Objects of the Inter-Exchange Circuit Network


Definition
Assigning the Database Objects to MML Commands
Command Sequence for Creation and Cancellation of Inter-Exchange
Circuit Connections
CP Digit Translators
Administration of the Called Party Address CdPA Digit Translation
Intercept Handling
Administration of the Traffic Type Digit Translation
Administration of Code Block Points for Call Gapping and Percentage
Call Blocking
Administration of Code Block Point Groups for Call Rate Reduction
(Leaky Bucket)
Administration of Traffic Discrimination Digits and Country Code
Administration of the Calling Party Address CgPA Digit Translation (ADN Screening)
Destination Areas
Destination Areas with Fixed Alternative Routing (FAR)
Destination Areas with Repeated Digit Translation
Destination Areas with Optimized Dynamic Routing (ODR)
Routes
Standard Routing
Changing the Hunting Sequence
Rerouting
Routes Formed by Trunk Group Clusters
Trunk Groups
Functionality
MML Commands
Important GCOS Values
Overload Control

SN2073EU01SN_0002
2002 Siemens AG

3
4
6
8
11
12
34
38
40
44
52
54
61
64
70
78
95
96
106
108
112
121
122
124
128
138

Siemens

5.5
6
6.1
6.2
6.3
6.4
7
7.1
7.2
7.3
7.4
8

Administration of the Inter-Exchange Circuit Network

Further Values of Trunk Groups


Trunks
Functionality and MML Commands
Self-Supervision and Operational Status of Digital Trunks
Nailed-up Connection
CCS No 7 Trunk Testing
Administration of Selective Trunk Reservation
Functionality
MML Commands for Trunk Reservation
Traffic-oriented Example
Code-oriented Example
Administration of the Carrier Access Code CAC Dependent Routing in
Deregulated Networks
8.1
Input Format for Dialing Information with CAC
8.2
Possibilities for Carrier Selection
8.3
MML Commands for CAC Administration
8.4
CAC Administration on Subscriber Level
8.5
Application of the CAC in the Digit Translation
8.6
Example
9
Flexible Routing via PA
10
Administration of Announcement Groups and Lines
10.1 Function
10.2 Access to an Announcement Unit
10.3 MML Commands
11
Testing of the Basic Routing Function
12
Exercise
13
Solutions

140
145
146
150
154
158
161
162
164
168
170
173
176
178
180
182
184
194
199
209
210
212
218
223
229
239

SN2073EU01SN_0002
2002 Siemens AG

Administration of the Inter-Exchange Circuit Network

Siemens

Database Objects of the Inter-Exchange


Circuit Network

SN2073EU01SN_0002
2002 Siemens AG

Siemens

1.1

Administration of the Inter-Exchange Circuit Network

Definition

The objective of administration of the user channel network (which is referred to in


the official documentation as routing database administration, is to convert
received dialing information into the equipment number of a time slot on a PCM
carrier which has to be used for the outgoing connection. This procedure is based on
the network architecture and the network parameters (signaling, numbering
diagrams, etc.).
l

CODE - DESTINATION AREA


The dialing information (CODE) is seen as an input for routing. In the first step, it is
evaluated and the result is the determination of to the destination area in the
network to be addressed.

DESTINATION AREA - ROUTE


Because there are several possibilities for reaching the destination area depending
on the network configuration, one must select a route. There are usually routes to
the terminating nodes which go directly without diversions over other nodes. These
routes are called direct routes and are the first choice. There are also routes which
are assigned if the first choice route does not have free PCM time slot capacity.
These routes are referred to as alternative or overflow routes.

ROUTE - TRUNKGROUP
A route is defined both by the destination area to which it leads and by the physical
PCM time slots through which the user information may be transmitted to the
destination area. The PCM time slots are arranged in groups for administrative
reasons; to make them easier to assign to routes and to make it easier to
administrate common attributes of these time slots. These PCM time slot groups
are called trunk groups.

TRUNKGROUP - TRUNK
As already described, a trunk group is an administrative group of PCM time slots
to a neighboring node. These PCM time slots are called trunks.

SN2073EU01SN_0002
2002 Siemens AG

Siemens

Administration of the Inter-Exchange Circuit Network

SIEMENS

D 900

D 900

SIEMENS

Code

Trunk
group

... 30 31
0 1 2

...

30
3

Trunks

Trunk
group

SIEMENS

D 900

SIEMENS

D 900

Route
Route

Trunks

Destination
Area
D 900

SIEMENS

D 900

SIEMENS

e.g. further
routing
SIEMENS

D 900

SIEMENS

D 900

Fig. 1 Basic routing objects

SN2073EU01SN_0002
2002 Siemens AG

Siemens

1.2

Administration of the Inter-Exchange Circuit Network

Assigning the Database Objects to


MML Commands

In digit translation, dialing information (CODE) received from the periphery is in the
simplest case, directly converted to a destination area. The allocation of CODE
and destination area is made with the command CR CPT.

The destination area data contains all destination-specific information. The destination area is created with the command CR DEST.

Several routes can be allocated to one destination area. A route is a trunk group
which can be used to make a connection to a specific destination area. Due to its
destination-specific application, the trunk group can be assigned destinationspecific parameters. A route is created with the command CR ROUTE and links a
destination area with a trunk group.

A trunk group is a group of PCM time slots. The group as a whole can be allocated
specific features such as signaling type, barring, etc.
A trunk group is created with the command CR TGRP. A trunk group can be used
to reach several destinations, i.e. it can be used by several routes with different
destinations.

A trunk is the definition of the PCM time slot and the allocation to a trunk group.
A trunk is created with the command CR TRUNK.

SN2073EU01SN_0002
2002 Siemens AG

Siemens

Administration of the Inter-Exchange Circuit Network

Code
Digit Translation

CR CPT

from other
digit translator
results

CR DEST

Destination

......
Route

Route
from other
routes

CR ROUTE

from other
routes

Trunkgroup

Trunkgroup

......
Trunk

CR TRUNK

......
Trunk

Trunk

Timeslot

CR TGRP

Trunk

Timeslot

Fig. 2 Routing base objects and the corresponding MML commands

SN2073EU01SN_0002
2002 Siemens AG

Siemens

1.3

Administration of the Inter-Exchange Circuit Network

Command Sequence for Creation and


Cancellation of Inter-Exchange Circuit
Connections

SN2073EU01SN_0002
2002 Siemens AG

Siemens

Administration of the Inter-Exchange Circuit Network

Creation of a new inter-exchange connection:


Destination
CR DEST
l Creation
l

Creation

Trunk groups

CR TGRP

Creation

Trunks

CR TRUNK

Creation

Routes

CR ROUTE

Creation

Code point

CR CPT

Creation

Zone point

CR ZOPT

Cancelation of an inter-exchange connection:


l

Cancelation

Zone point

CAN ZOPT

Cancelation

Code point

CAN CPT

Cancelation

Route

CAN ROUTE

Cancelation

Destination

CAN DEST

Blocking

Trunks

ENTR TRDAT

Cancelation

Trunks

CAN TRUNK

Cancelation

Trunk group

CAN TGRP

Fig. 3 MML command sequence

SN2073EU01SN_0002
2002 Siemens AG

Siemens

10

Administration of the Inter-Exchange Circuit Network

SN2073EU01SN_0002
2002 Siemens AG

Administration of the Inter-Exchange Circuit Network

Siemens

CP Digit Translators

SN2073EU01SN_0002
2002 Siemens AG

11

Siemens

2.1

Administration of the Inter-Exchange Circuit Network

Administration of the Called Party Address CdPA


Digit Translation

The digit translator evaluates for each call set up the digits (called party address
CdPA) received from:
l

a subscriber

incoming/bothway trunk

an IN service control point SCP

The evaluation may lead to:


1. a standard routing case (accessing a trunk for outgoing traffic)
2. a subscriber (terminating traffic)
3. an access of an IN SCP
4. an intercept
In other words, the digit translator translates a digit combination into a call
handling order. Therefore so called code points CPT have to be set up with the
MML command CR CPT.
Result of the digit translator

Meaning

DEST=<destination area name>

CdPA leads to a destination via standard routing

INCEPT= e.g. UNOBDEn

CdPA requires intercept handling. (Codes, for


example, that are cancelled in a way that they
should now lead to a special announcement or
tone)

TRATYP=CPTDN

CdPA leads to a directory number of a subscriber


or a PABX connected to the own exchange

TRATYP=

CdPA contains the number of an intelligent


network service -> EWSD starts an interrogation
at the IN Service Control Point determined by the
name identifier (leads to a so called IN-TRIGGER
created with CR INTRIG)

IN <name of the IN-service>

TIP
All codes for which no (more) CPT was created have the standard result NOT
CONNECTED and are handled by the standard intercept UNOBDE0.

12

SN2073EU01SN_0002
2002 Siemens AG

Siemens

Administration of the Inter-Exchange Circuit Network

SIEMENS

SIEMENS

IN
SCP

partner
exchange

Digits

Digit translation
Traffic to
intercept
handling

Outgoing
traffic and
announcements

Intercept
handling

Setup Signaling
connection to
the SCP

Routing

Tone

to subscriber
or PABX

IN traffic

Setup
connection to
subscriber
or PABX

Announcement
CCS7 connection

Trunk connection

SIEMENS

Beep

SIEMENS

IN
SCP

partner
exchange

DAS
OCANEQ

Fig. 4 Functionality of the digit translator

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

SN2073EU01SN_0002
2002 Siemens AG

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

13

Siemens

2.1.1

Administration of the Inter-Exchange Circuit Network

General Structure of the CdPA Digit Translator in the CP

The translation of digits is carried out by the LTG and the CP. The LTG performs a
so-called digit pre-analysis (not discussed in this subsection). The main translating
process is done by the CP. This is where all the necessary digits that are delivered
by the LTG are translated and the respective result is accessed.
The CP digit translator has a tree structure. This tree is made up of the so-called digit
translator blocks which are linked up with each other. Each block contains 16 digit
translator elements representing the digits 0 to F. Each block evaluates one digit.
One of these blocks is defined as entry block (block 0). This is where the translation
of all digit combinations begins. The other blocks the digits run through during translation are filled and linked by the CP whenever a new code point is created by MML.
For each received CdPA the digit translation starts in the entry block always, i.e. the
first digit is used to access the according field in the entry block.
Then next digit is translated by branching to the block linked with the first digit. The
index to this next block is written in the block element which was accessed by the first
digit. Inside a block the digit to be translated is used as an index for finding the
respective element. If, for example, the first digit is "0", the element 0 in the entry
block will be accessed, if the second digit is "1", the element 1 in the block linked with
the element 0 of the entry block will ,be accessed, etc..
Each block element contains a translation result. The initial result value is "not
connected". With setting up the digit translator (CR CPT) the result is:
1. an index for a destination area or an index for intercept handling etc. (final result)
2. "come again with digits" and an index to a further translation block, if there are
still other digits to be analyzed (intermediate result)

14

SN2073EU01SN_0002
2002 Siemens AG

Siemens

Administration of the Inter-Exchange Circuit Network

Setup example:
The digit combination 089 is supposed to lead to the destination MUNICH. It is the
first digit combination that is set up as a CODE POINT in this digit translator.
1. In the entry block (block 0) the element 0 is correspondingly assigned to the
digit "0". As result "come again with digit" is entered. Now a new block is
searched for in the database (all elements contain "not connected") and the new
block's index entered in element 0 of block 0. As this setup is the first one to be
administered, block 1 would be assigned as the new block for evaluation of the
second digit for codes starting with 0.
2. In this block1 the result "come again with digit" is entered in the element 8. Now
a new block (block 2 in our case) is searched for in the database and the new
block's index is also entered in the element 8 of block 1. This new block 2 will be
used for evaluation of the third digit for codes starting with 08.
3. In this block 2 the result "DEST=MUNICH" (destination area has to be set up
before) is entered in the element 9.

Layout of Digit Translator DITDA after creation of the first CPT (089)
CODE
(first digits
of CdPA)

Entry block (0)


for evaluation of
first digit

Block (1)
for evaluation of
second digit if
first digit = 0

evaluate next digit

not connected

not connected

not connected

not connected

not connected

not connected

not connected

not connected

not connected

not connected

...

2
3

not connected

...
...

DEST=MUNICH

...
...

Link to
destination
table (DEADA)

not connected
0 connected
not
not connected
0
not connected
not connected
1 connected
not
1 not connected
not connected
2 connected
not
2 not connected
3 not connected
3 not connected

0
not
connected of
All other blocks
(3...n)
0
1 not connected
not connected
DITDA are still2 unused
0
not connected
not connected
1 not connected
3

not connected
2

1 not connected
not connected

2 not connected
not connected
3

not connected
9

E
F

evaluate next digit

not connected

...

Block (2)
for evaluation of
third digit if
first digit = 0 &
second digit =8

...
. . .. .. .
. .. .. .

not connected
9
not connected

not connected

...
... ...
. . .. . .
...
9

E
F

not connected

not connected
9

E
F

not connected

Tip
If code points are already set up, the system simply
assigns the next available unused block.
Therefore the block numbering has no significance
during the evaluation of the CdPA.

E
F

Fig. 5 Example of the digit translator's structure after creation of one CPT (089 for DEST=MUNICH)

SN2073EU01SN_0002
2002 Siemens AG

15

Siemens

Administration of the Inter-Exchange Circuit Network

2.1.2

Extended Code Points

The digit translation provides the possibility to create ambiguous code points too.
For example one code point can be created with the digits 089 and a second code
point with the digits 0891
1. All dialed digit combinations 089 plus at least one digit more unequal 1lead to the
destination allocated to the CODE=089.
2. All digit combinations 0891 plus optional further digits lead to the destination
allocated to the CODE=0891.
Example:
1. CR CPT: CODE=089, DEST=MUNICH;
Three digit translator blocks are linked as usual. The element 9 in the last block
points to the destination MUNICH.
2. CR CPT: CODE=0891, DEST=EXCEPTION;
A further digit translator block is linked to the digit translator element, which has
pointed before to the destination MUNICH.
The result outgoing traffic to DEST = MUNICH remains in this element as a kind
of preliminary result.
In the new block all elements except for the element 1 (0891) contain the result
not connected and the element 1 contains the result DEST=EXCEPTION.
If the call processing finds such an element with the result not connected the
call processing takes as the result the Destination MUNICH (standard case),
which was found in the element 9 of the previous block.
Dialing Examples:
089

The system expects one digit more, otherwise the call is released

0890
0892

The system goes to the destination MUNICH, which was found in element 9 in
the block for the third digit

0893
....
0899
0891

16

The system goes to the destination EXCEPTION

SN2073EU01SN_0002
2002 Siemens AG

Siemens

Administration of the Inter-Exchange Circuit Network

CODE
Block for
first digit
(entry block 0)

Block for
first digit=0

evaluate next digit

e.g. not connected

e.g. not connected

e.g. not connected

e.g. not connected

e.g. not connected

e.g. not connected

e.g. not connected

e.g. not connected

...

...

Block for
first digit=0 &
second digit=8

...

CR CPT:CODE=089,
DEST=MUNICH;
CR CPT:CODE=0891,
DEST=EXCEPTION;

E
F

evaluate next digit

...
...

Block for first digit=0


second digit=8
third digit =9

e.g.not connected

Not connected

e.g. not connected

Destination
EXCEPTION

e.g. not connected

Not connected

e.g. not connected

Not connected

to MUNICH
to EXCEPTION
to MUNICH
to MUNICH

E
F

...

Destination
MUNICH
evatuate next digit

...
...

...

Not connected

Not connected

Not connected

to MUNICH

to MUNICH

to MUNICH

Fig. 6 Extended code points

WARNING
Never create the CODE with exactly the number of digits you expect to be
dialed, if you plan to create an extension later on. The system expects at least
one digit more to be dialed.

SN2073EU01SN_0002
2002 Siemens AG

17

Siemens

2.1.3

Administration of the Inter-Exchange Circuit Network

Code Points Depending on ORIG1, MFCAT, LAC or ZDIG

The following information can be evaluated in the digit translator in addition to the
code received as CdPA:
l

Originating Mark 1: ORIG1 value of a incoming/bothway trunk group, a subscriber


or a PABX administered in the database of the own exchange.
The ORIG1 value cannot be signaled between exchanges.

MFC-Category: MFCAT of a subscriber


The MFCAT value can be signaled between exchanges.

Local area code:


a) LAC value of an incoming/bothway trunk group, a subscriber or PBX
administered in the database of the own exchange.
b) LAC as part of the CdPA
A LAC can only be evaluated if before it was set up with ENTR AREACODE

Language digit: ZDIG for operator traffic


The ZDIG value can be signaled between exchanges.

These information units are internally treated in the digit translator as additional digits
chained into the CdPA. The position of the chain-in can be specified in the MML
command CR CPT, otherwise they are chained-in at the end of the code point
determined with the CR CPT.
Exception: The LAC is chained-in as early as possible. If e.g. a CPT with the code
226 with evaluation of the LAC should be set up, the LAC evaluation takes place in
the following way:
l

If no other CPT (starting with 2) without LAC evaluation is already set up, the LAC
evaluation will be chained-in after the first digit.

If e.g. a CPT 238 without LAC evaluation is already set up, the LAC evaluation will
be chained-in after the second digit

WARNING
The LAC of the calling party address CgPA transmitted by inter exchange signaling
cannot be evaluated in the digit translator (it can only be used for A-side specific
zoning).

18

SN2073EU01SN_0002
2002 Siemens AG

Administration of the Inter-Exchange Circuit Network

Siemens

Special Identifiers in the Digittranslator


Originating Mark 1 (ORIG1)

Originating mark assigned to a trunk


group or a subscriber

MFC Category (MFCAT)

Subscriber category

Local Area Code (LAC)

Local area code assigned to a trunk


group/a subscriber or received as
part of the CdPA

Z- Digit (ZDIG)

Language digit for operator traffic

Fig. 7 Special identifiers in the digit translator

TIP
1. It is also possible to determine for specific code points that A-subscriber
blockings (e.g. account suspension or screening list) are not evaluated, what is
very important for the CPT leading to the emergency services.
Theses code points must be created with the TRATYP=NBARCPT.
Restrictions:
- max. 15 digits long code
- no special positioning of ORIG1, MFCAT...
2. It depends on the positioning of ORIG1, MFCAT... whether later further CPT with
similar codes can be created without ORIG1, MFCAT...:
Example:
a) CRCPT: CODE=0872, ORIG1=10, DEST=AAA;
b) CR CPT: CODE=0873, DEST=BBB;
Second command is accepted because the ORIG1 is requested after 0872
and not already after 087.
a) CRCPT: CODE=0972, ORIG1=10-2, DEST=CCC;
b) CRCPT: CODE=0973, DEST=DDD;
Second command is rejected, because already after 09 the ORIG1 is
requested in the digit translator.

SN2073EU01SN_0002
2002 Siemens AG

19

Siemens

2.1.3.1

Administration of the Inter-Exchange Circuit Network

Originating Mark 1 in the Digit Translator

A code point in the digit translator with Originating Mark 1 is set up using the command CR CPT: CODE=..., ORIG1=...,...;. The ORIG1 parameter contains two information units: ORIG1= a-b.
a: The Originating Mark 1 covers a value range of 0...3839.
b: The position of the Originating Mark indicates after which digit the ORIG1 is translated
In the digit translator the ORIG1 is translated in the same way as normal digits. For
this purpose the hexadecimal value of the ORIG1 is used:
ORIG1=0..3839: H'000...H'EFF
The three half-byte positions are now translated in one digit translator block each in
the same way as dialing information, i.e. beginning with the highest-order half-byte, .
Example:
The MML command CR CPT:CODE=0.., ORIG1=20-1,...; was entered.
The first digit "0" is translated in the entry block.
As the ORIG1 needs to be translated after the first digit (ORIG1=20-1) the next three
blocks are used for the origination.
Because ORIG1=20 results in H014, it is translated in the following way:
1. The 0 is translated in the block for the first part of the ORIG1 translation
2. The 1 is translated in the second block
3. The 4 in the last block.
After the origination translation has been completed the translation of the digits
continues.

TIP
If no ORIG1 is assigned to a trunk group or subscriber, connections from these
sources can be arranged by entering ORIG1=0.
If for a particular code the ORIG1=0 is not set up but at least one other ORIG1,
connections requested from A-sides without this ORIG1 will be rejected.

TIP
If a CODE was set up with Originating Mark1 (e.g. CODE=089, ORIG1=20-1) and if
you then try to set up a CODE with the same first digit or digits without Originating
Mark1 (e.g. CODE=001) the command is rejected, because an Originating Mark1
block already exists after the first digit. (The number of same first digits is dependent
on the position of the Originating Mark1.)

20

SN2073EU01SN_0002
2002 Siemens AG

Siemens

Administration of the Inter-Exchange Circuit Network

Block for
first digit
(entry block 0)

Block for
ORIG1 second part
Block for
first digit=0
ORIG1=H'0..

CODE
0

evaluate ORIG1
1st part

result

e.g. not connected

evaluate ORIG1
3 rd part

e.g. not connected

result

e.g. not connected

result

e.g. not connected

result

result

...

...

...

Block for
first digit=0
ORIG1=H'01.

Block for
first digit=0

Block for
ORIG1 first
part

evaluate ORIG1
2 nd part

result

e.g. not connected

result

e.g. not connected

result

e.g. not connected

result

evaluate digits

block for
ORIG1 third
part

continue
with digits

...

e.g. not connected

...
...

Fig. 8 The digit translator's structure for CODE=0.., ORIG1=20-1,....


+

SN2073EU01SN_0002
2002 Siemens AG

21

Siemens

Administration of the Inter-Exchange Circuit Network

A typical case in which the ORIG1 may be used in the digit translator are emergency
service numbers. Depending on the caller's origin (=city section) calls are routed to
the nearest police station although all callers dial the same number (110).

22

SN2073EU01SN_0002
2002 Siemens AG

Siemens

Administration of the Inter-Exchange Circuit Network

Example: CPT with ORIG1

Exchange

City section A

LAC=089

dials 110

DEST=POLA

Police
city section A

DN= 445566
ORIG1=5

City section B
dials 110
DEST=POLB

Police
city section B

DN= 556677
ORIG1= 10

CR CPT

CODE =
DEST =
ORIG1 =

110,
POLA,
5;

CR CPT

CODE =
DEST =
ORIG1 =

110,
POLB,
10;

Fig. 9

. .
. .
. .
. .
. .
. .
. .
. .
. .
. .
. .
. .
. .
. .
. .

. . . . . .
. . . . . .
. . . . . .
. . . . . .
. . . . . .
. . . . . .
. . . . . .
. . . . . .
. . . . . .
. . . . . .
. . . . . .
. . . . . .
. . . . . .
. . . . . .
. . . . . .

SN2073EU01SN_0002
2002 Siemens AG

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

. . .
. . .
. . .
. . .
. . .
. . .
. . .
. . .
. . .
. . .
. . .
. . .
. . .
. . .
. . .

. . . . . . .
. . . . . . .
. . . . . . .
. . . . . . .
. . . . . . .
. . . . . . .
. . . . . . .
. . . . . . .
. . . . . . .
. . . . . . .
. . . . . . .
. . . . . . .
. . . . . . .
. . . . . . .
. . . . . . .

. . . .
. . . .
. . . .
. . . .
. . . .
. . . .
. . . .
. . . .
. . . .
. . . .
. . . .
. . . .
. . . .
. . . .
. . . .

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

. . . .
. . . .
. . . .
. . . .
. . . .
. . . .
. . . .
. . . .
. . . .
. . . .
. . . .
. . . .
. . . .
. . . .
. . . .

23

Siemens

Administration of the Inter-Exchange Circuit Network

ORIG1 = DEF
The introduction of a so-called default originating mark facilitates the management of
the digit translator in the case that:
for a code only one or a few originating mark(s) lead to specific destination (socalled exception destinations for this code) and
all other originating marks should, however, lead to the very same destination (so
called standard destination for this code).
This led to a lot of MML commands without using the solution with a default ORIG1.
Using the default ORIG1 :
the so-called exceptions must still be established with one command per
ORIG1/destination area combination.
the remaining originating marks, which all lead to the same destination area, are
however established with a single MML command with reference to the default
case.
Code points with a default originating mark are displayed with the corresponding
display commands DISP CPT/DIGITGP/DIGITCP.
The default originating Mark is realized in the digit translator in the following way:
The exception destination or exception destinations are created in the normal way.
Is a default ORIG1 used than the element "F" in the 1st ORIG1 block gets as the
result the destination, which was specified in the MML command with
ORIG1=DEF.
In case of the call processing comes to an ORIG1 element with the result "not
connected, it automatically takes the result of element "F" of the first ORIG1 block
for further processing.

24

SN2073EU01SN_0002
2002 Siemens AG

Siemens

Administration of the Inter-Exchange Circuit Network

Default ORIG1
Solution without default ORIG1
CR CPT:

CODE=08, ORIG1=0, DEST= dest1;

CR CPT:

CODE=08, ORIG1=1, DEST= dest1;

CR CPT:

CODE=08, ORIG1=2, DEST= dest1;

...........

........

CR CPT:

CODE=08, ORIG1=20, DEST= dest2; EXCEPTION

............

.......

CR CPT:

CODE=08, ORIG1=3839, DEST= dest1;

Solution with default ORIG1


CR CPT:

CODE=08, ORIG1=20, DEST= dest2; EXCEPTION

CR CPT:

CODE=08, ORIG1=DEF, DEST= dest1;

Fig. 10

Block for
first digit
(entry block 0)

Block for
ORIG1 first
part

Block for
second digit
(first digit 0)

Block for
ORIG1 third
part

Block for
ORIG1 second
part

CODE
0
1
2

come with digit


e.g. not connected
e.g. not connected

e.g. not connected

e.g. not connected

1
2
3

e.g. not connected

e.g. not connected

e.g. not connected

e.g. not connected

e.g. not connected

...

...

E
F

evaluate ORIG1
2 nd part

not connected

not connected

evaluate ORIG1
3 rd part

not connected

not connected

not connected

not connected

...

evaluate ORIG1
1st part

...
e.g. not connected

not connected

not connected

not connected

not connected

not connected

not connected

not connected

outgoing traffic

exception
destination

not connected
not connected

not connected

outgoing traffic
in case of not connected

not connected

not connected

not connected

standard
destination

Contents of the digit translator after:


CR CPT: CODE= 08, ORIG1= DEF, DEST= DEST1 (standard destination);
CR CPT: CODE= 08, ORIG1= 20, DEST= DEST2 (exception destination);
Fig. 11

SN2073EU01SN_0002
2002 Siemens AG

25

Siemens

2.1.3.2

Administration of the Inter-Exchange Circuit Network

Local Area Codes LAC in the Digit Translator

Creating local area codes


Local area codes are entered in the digit translator by ENTR AREACODE (if the
directory number volume of the exchange is ambiguous).
Ambiguity of directory number volume means that a calling party number can appear
several times within a single exchange but only once per installed local area network.
It is administered using the MML command ENTR DNATT:
1. The parameter DNVOL specifies whether the directory numbers within the entire
exchange are ambiguous.
2. The parameter EVLAC = YES has the result that the local area code is evaluated
in the digit translator.
Only the DLUs to which exactly one LAC is assigned (parameter DLU in ENTR
AREACODE) are able to work in the so called stand alone service SAS. If the
parameter DLUEM in the command MODCALLPOPT is set to true, the assignment
has to be done for all DLUs (i.e. to each DLU exactly one LAC). If DLUEM is set to
PARTLY, it is possibly to have DLUs to which no LAC is assigned. To these DLUs
subscribers of different local areas can be connected but SAS is not possible.

WARNING
A subsequent modification of the directory number attribute is possible only if
no directory numbers have been created yet. Therefore it is advisable to set up
the directory number volume ambiguously at the start, even if the directory
number volume is unique initially. This saves the effort required for
subsequent modification which involves first deleting the existing directory
numbers along with their subscribers in order to then reinstall them for
ambiguous (multiple) directory number volume.

26

SN2073EU01SN_0002
2002 Siemens AG

Siemens

Administration of the Inter-Exchange Circuit Network

SIEMENS

SIEMENS

LAC
08176

LAC
08178

DN=445566
LAC=08178

DN=445577
LAC=08178

DN=445566
LAC=08176

ENTR DNATT:

DNVOL = MULTIPLE,
EVLAC=YES;

ENTR AREACODE:

LAC = 08178, [DLU=];

ENTR AREACODE:

LAC = 08176, [DLU=];

DN=445577
LAC=08176

Fig. 12

SN2073EU01SN_0002
2002 Siemens AG

27

Siemens

Administration of the Inter-Exchange Circuit Network

Handling of the LAC in the digit translator


Ambiguity of directory numbers is solved in the digit translator by means of 3 special
blocks inserted into the digit chain.
The use of the LAC parameter for code points requires that the LAC has been
entered previously using the ENTR AREACODE command. With this command an
internal index is allocated to the created LAC. This LAC-index consists of a 3 half
byte hexadecimal number.
This LAC index is then used if a CPT is created with the parameter LAC. The index of
the specified LAC is chained into the code of this code point. As the index range can
lie between 1 and 3839, there 3 additional blocks chained-in.
In case of a call set up the LAC is determined in the following way:
1. If the CdPA includes a LAC, the first step of the digit translation determines the
LAC index of the dialed LAC. After the LAC index is found, the digit translation
starts again with the rest of the CdPA. If these digits lead to a CPT created with
LAC, the previously determined LAC index is evaluated.
2. If the CdPA does not include a LAC but leads to a CPT created with LAC, the
LAC index of the A-party is evaluated. This LAC index of the A-party is taken
from the LAC value assigned to the calling subscriber or incoming/bothway trunk
in the database of this exchange.
Example (see figure beside):
1. Creation of a local area code: ENTR AREACODE: LAC=02;
Result:
The LAC-index e.g.H'004 is assigned to the LAC 02, i.e. the code 02 leads in the
digit translator to the result NEW TRANSLATION with holding the LAC-INDEX
H'004 ready for the evaluation of the further digits of the CdPA
2. Creation of a CPT for terminating traffic to subscribers of the local area 02 with
DN starting with 123: CR CPT: CODE=123, TRATYP=CPTDN, LAC=02;
Result :
If no other code point without LAC and first digit 1 was created before, the digit
chain for this CPT is set up in the digit translator in the following way:

28

first step:

digit=1, result=evaluate LAC index first part

second step:

LAC-index first part=0, result=evaluate LAC index second part

third step:

LAC-index second part=0, result=evaluate LAC index third part

fourth step:

LAC-index third part=4, result=evaluate next digit of CdPA

fifth step:

digit=2, result=evaluate next digit of CdPA

sixth step:

digit=3, final result=go to directory number block 123 with LAC=02

SN2073EU01SN_0002
2002 Siemens AG

Siemens

Administration of the Inter-Exchange Circuit Network

dialed digits:
02 123xxx
0

dialed digits:
123xxx,
A-subscriber
has LAC 02

evaluate next
digit
evaluate
LACIndex

1
new translation,
LAC Index = 004

Block for
first digit=1 &
LAC Index=4 &
second digit=2

Block for
first digit=0

Block for
first digit

2
3

Result: DN-block123
with LAC 02

4
5

E
F
first digit=1 &
LAC Index=004

evaluate LAC index


second part

LAC INDEX
third part
evaluation for
first digit=1 &
LAC index first
part=0 &
second part=0

LAC INDEX
second part
evaluation for
first digit=1 &
LAC index first
part=0

LAC INDEX
first part
evaluation for
first digit=1

evaluate LAC index


0
third part

0
1
2

evaluate next
digit

E
evaluate next
digit

Fig. 13 Example for LAC evaluation

SN2073EU01SN_0002
2002 Siemens AG

29

Siemens

Administration of the Inter-Exchange Circuit Network

Distribution of one Local Area Code to different local exchanges


Examples beside:
SUB 1 (LAC=030, DN=27400) sets up calls:
called party address

terminating
subscriber

traffic type of the


call

23420

SUB2

local

03023420

SUB2

local

SUB4

national

Call is only through connected if


ENTRLOCDIAL:DIAL=LACDN was
entered in EX1
04023420

Because the DN volume of EX2 is ambiguous, the received CdPA 23420 can only be
translated successful if the A-LAC is known. This is important to know, because the
LAC of the calling party address transmitted in the ISUP-IAM cannot be evaluated in
the digit translator of the terminating exchange.
The following possibilities exist:
l

The LAC 030 is assigned in EX2 by MML command to the trunk group coming in
from exchange EX1. This LAC is then used for all incoming calls where the CdPA
does not include a LAC but the accessed CPT requires a LAC.

The so called "LAC insertion" is activated in the involved exchanges:


ENTR DNATT: LACINSOC=Y.
The insertion of the A-subscriber LAC in front of the called party address
(transmitted via the SS7 message IAM) will take place for each outgoing call (OC),
if
a) the A-subscriber has not dialed a LAC
b) and the B-directory number leads to a so called traffic type code point
TRATCPT (will be explained later), which was created with EXTTONSN=Y.

30

SN2073EU01SN_0002
2002 Siemens AG

Siemens

Administration of the Inter-Exchange Circuit Network

LAC=030

LAC=040

EX 2
LAC=030
LAC=040

27400

SUB 1

LAC=030

EX 1
LAC=030

LAC=030

long
distance
call

040/
23420

SUB 4

local call
030/
23420

SUB 2

DLU

030/
23421
SUB 3

MML example for distribution of a local area to multiple exchanges


EX 1

EX 2

CR CPT: CODE=23, DEST=EX 2,


LAC=030;

CR CPT: CODE=27, DEST=EX1,


LAC=030;

CR TGRP:TGNO=EX2, LAC=030,...;

CR TGRP: TGNO=EX1, LAC=030,...;

CR DN: DN=27000 && 27999,


LAC=030;

CR DN: DN=23000 && 239999,


LAC=030;

CR CPT: CODE=27, TRATYP=CPTDN, CRCPT: CPDE=23, TRATYP=CPTDN,


LAC=030
LAC=030
Fig. 14 Subscribes in a local area connected to various exchanges

local area 030

DN=27400
Dialed number:
23420
IAM with
CgPA= 030 27400
CdPA= 030 23420

SIEMENS

CRTRATCPT:
CODE=2,...,
EXTTONSN=Y;
and
ENTR DNATT:...,
LACINSOC=Y;

DN=23420

SIEMENS

trunk group

Dialed number:
23420

IAM with
CgPA= 040 88420
CdPA= 040 23420

DN=88420

DN= 23420

local area 040

Fig. 15 Application of the new feature LAC Insertion

SN2073EU01SN_0002
2002 Siemens AG

31

Siemens

Administration of the Inter-Exchange Circuit Network

2.1.4

Overview: MML Commands for the Administration of the


CdPA Digit Translation

Amongst other things the system provides the following commands for the creation,
cancellation and logging of the CP digit translation: CR CPT, CAN CPT, DISP CPT.
l

CR CPT:
The MML command CR CPT can be used to create a code point.

CAN CPT:
If a code point is canceled it must be defined via the parameter CODE and if
required via LAC, ORIG1 and MFCAT. You can enter an INCEPT value. Note that
if #an INCEPT value other than UNOBDE0 is used this will not really cancel the
code point. In this case the code point's structure is maintained and the end result
is merely replaced with a reference to the intercept table. In other words, the code
point cannot be overwritten.

There are two MML commands for logging the digit translator: DISP CPT and
DISP DIGITCP.
The command DISP CPT reproduces all the data that was entered with CR CPT
for one, several or all code points.
The command DISP DIGITCP reproduces data of all codes (CPT, LAC, TEPT,
SCFEA) of the digit translator (but not all data of the codes). It is very useful for
gaining an overview of all the used digit combinations or of all codes starting with
selected digits.

Creation of Codepoints
Codepoint for a destination (outgoing traffic)

CR CPT:

CODE= ,DEST= [,LAC=] [,ORIG1=] [,MFCAT=] ;

Codepoint for an intercept


CR CPT:

CODE= ,INCEPT= [,LAC=] [,ORIG1=] [,MFCAT=];

Codepoint for terminating traffic


CR CPT:

CODE= ,TRATYP= CPTDN [,LAC=] [,ORIG1=] [,MFCAT=];

Fig. 16 MML commands for creating code points

32

SN2073EU01SN_0002
2002 Siemens AG

Administration of the Inter-Exchange Circuit Network

Siemens

Cancelation of Codepoints
CAN CPT:

CODE= [,INCEPT=] [,LAC=] [,ORIG1=] [,MFCAT=];

Fig. 17 MML commands for canceling code points

Display of Codepoints
DISP CPT:

CODE= ;

DISP CPT:

{DEST= | INCEPT= | TRATYP= | ORIG1= | MFCAT= |


ROUTYP= | ZDIG= | PROVNAM=} [,CODE=] ;

DISP DIGITCP:

[CODE=] [,ORIG1=] ;

DISPDIGITCP;
DIGIT TRANSLATION DATA
CODE

LAC

ZDIG MFCAT
ORIG1 RESULT
ROUTYP
------------------------+---------+----+-----------+------+-------030
OUTGOING
089
OUTGOING
091
NEWTRANS
3011
091
- 1
TERMTRAF
8000
091
- 1
TERMTRAF
8001
091
- 1
TERMTRAF
8002
091
- 1
TERMTRAF
END JOB 7795 EXEC'D

Fig. 18 MML commands for creating code points

TIP
With MODCPT only specific data of a CPT can be modified (DEST, INCEPT or
TRATYP)

SN2073EU01SN_0002
2002 Siemens AG

33

Siemens

2.2
2.2.1

Administration of the Inter-Exchange Circuit Network

Intercept Handling
Functionality

The Intercept Handling usually serves to deal with those situations that differ from the
normal call setup. I.e. the so-called "Reason for Call Failure" or "Reason for Call
Termination" are allocated to a system reaction such as tone or announcement.
Examples of branching to the intercept handling:
1. ISUP Backward Release Cause such as: "no circuit / channel available", "No
route to destination", "unallocated number" etc. The respective causes are linked
to a symbolic intercept value (INCEPT) via a project specific mapping table.
2. Data base causes in the own exchange such as: digit translator delivers
UNOBDEn, because the code has not been set up or is blocked, call rejected
because A-subscriber has account suspension etc.
3. Accessing the intercept handling with individual announcement system functions
(INDAS). I.e. individual announcement functions are controlled by the call processing. Such a case always leads to the individual announcement system
OCANEQ (Operationally Controlled Announcement Equipment).
4. Accessing an announcement from the intelligent network. The SCP (Service
Control Point ) delivers an intercept number. This usually leads to an
announcement in the DAS or OCANEQ via the digit converter.
As a result the intercept handling usually delivers a tone that is indicated as symbolic
value, a new CODE for branching to the digit translator or a new DEST for directly
branching to the destination areas.

34

SN2073EU01SN_0002
2002 Siemens AG

Siemens

Administration of the Inter-Exchange Circuit Network

Backward
causes
e.g. "no circuit /
no channel
available"

Database
reasons
in the exchange
e.g.
Digit translator
UNOBDEn

INDAS
function

IN: SCP
PLAY
ANNOUNCEMENT

Intercept

Intercept Handling
Intercept Result

new digit translation


or
new destination

Digital announcement
system

OCANEQ
standard and individual
announcements

tone

General
destinations

Fig. 19 Intercept handling

SN2073EU01SN_0002
2002 Siemens AG

35

Siemens

2.2.2

Administration of the Inter-Exchange Circuit Network

MML Commands for the Administration of Intercepts

The intercept handling is set up with the MML command CR INC. You need to use
different parameters depending on whether a tone is to be activated or whether
branching to a destination area or to the digit translator is to be performed. In all
cases you will need the parameter INCEPT. It indicates the cause, i.e. the reason for
the withdrawal from the various data tables of the exchange. Intercepts can be
interlinked with the parameter SEQ (sequence number). I.e. the intercept is to be set
up several times with different results and ascending number in the SEQ parameter.
1. Accessing a tone:
The parameter TONE indicates the tone to be activated as symbolic value. The second parameter unit indicates the tone duration in seconds. The tone frequencies
and patterns are project specific.
2. Accessing the digit translator
The parameter CODE indicates a new code the digit translator is addressed with.
Additionally, set the parameter INRES to NEWCOD. You can also specify the
parameter TONE. The tone is then played in, if no announcement is possible.
3. Accessing a destination area
The DEST parameter is supplied with a destination area name to access the destination area and with that an announcement for example. Set the parameter INRES
to NEWDEST in this case.

36

SN2073EU01SN_0002
2002 Siemens AG

Siemens

Administration of the Inter-Exchange Circuit Network

Intercept Administration
Intercept with a tone
CR INC:

INCEPT=, TONE= a-b [,SEQ=];

Intercept with a new code


CR INC:

INCEPT=, INRES=NEWCOD,CODE= [,TONE= a-b]


[,SEQ=];

Intercept with a new destination area


CR INC:

INCEPT=, INRES=NEWDEST, DEST= [,SEQ=];

Display of intercepts
DISPINC:

<INCEPT=, INTYP= >;

Fig. 20 Intercept administration

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

SN2073EU01SN_0002
2002 Siemens AG

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

37

Siemens

2.3

Administration of the Inter-Exchange Circuit Network

Administration of the Traffic Type Digit


Translation

EWSD assigns to each call set up a so called traffic type TRAT. A TRAT is identified
by a symbolic name (TRAT=) and includes call processing characteristics. Except the
default TRAT=NOBLOCK all other up to 63 TRAT have to be created by CR TRAT.
The assignment of the TRAT to a call is done by the TRAT digit translator which is
applied for each call set up. This digit translator is filled with so called traffic code
points TRATCPT (CR TRATCPT). If for a dialed code no TRATCPT is created, the
default result TRAT=NOBLOCK is assigned automatically.
Beside the procedure of assigning a traffic type TRAT via the traffic type translator it
is also possible to determine the TRAT via the zoning of a call:
CR ZOPT:...,ZOTRAT=<trat>;
Function of traffic types TRAT for call set up:
l

Blocking of call set up for subscribers with traffic restriction


Example:
All calls with called party address starting with 0 are translated via TRATCPT 0 to
TRAT=NAT (CR TRATCPT:CODE=0,TRAT=NAT).
A-subscriber has activated the traffic restriction class TRACL1 which includes the
restriction for establishing calls with TRAT= NAT. Traffic classes are restricted for
traffic types by command ENTRTRABLOCK:TRAT=NAT,TRACL=TRACL1.
If this subscriber starts dialing 0..... the call set up is rejected and handled by the
intercept value, which is assigned to the TRAT (CR TRAT:
TRAT=NAT,INCEPT=...).

Restrictions for call diversion


It has to be defined for each traffic type TRAT whether call diversion is allowed to
destination codes with this TRAT.
Example: Diversion to destination codes starting with 00 (TRAT=INAT) should be
forbidden:
CRTRAT:TRAT=INAT,DIV=NO,INCEPT=......;
CR TRATCPT:CODE=00,TRAT=INAT;

Creation of TRATCPT in the traffic type translator:

38

A TRATCPT can depend not only on the dialed code but also on the LAC of the Aside: CR TRATCPT: TRAT=, CODE=, LACOR=;

It is possible to create a TRATCPT which code includes the code of an already


created TRATCPT (e.g. CR TRATCPT: TRAT=NAT,CODE=0; and
CRTRATCPT:TRAR=INAT,CODE=00;).

SN2073EU01SN_0002
2002 Siemens AG

Administration of the Inter-Exchange Circuit Network

Siemens

dialed digits

Traffic type translator: CR TRATCPT

CODE

TRAT

0
00
8 with

NAT
INAT
LOC1

8 with

LOC2

all other codes:

NOBLOCK

LACOR=023

all
allTRAT
TRAThave
haveto
tobe
be
created
by:
created by:
CR
CRTRAT
TRAT

LACOR=024

TRAT of the call

check whether
- A-side is blocked for this TRAT
- Diversion is allowed

Fig. 21

TIP
The MML command CR TRATCPT includes the optional parameter EXTTONSN=Y.
By this the LAC of the originating side is automatically added to a CdPA (if dialed
without LAC).

SN2073EU01SN_0002
2002 Siemens AG

39

Siemens

2.4
2.4.1

Administration of the Inter-Exchange Circuit Network

Administration of Code Block Points for Call


Gapping and Percentage Call Blocking
Functionality and MML Commands

With the feature call gapping the rate of outgoing call attempts to a specific digit
combination is controlled. This can be used to prevent the network and nodes from
overload.
A certain percentage of seizure attempts can be blocked or the code point can be
blocked during a fixed time interval (blocking interval). The destination (digit
combination) to be blocked is defined as code block point (CBPT).
Call gapping
The blocking interval indicates the period during which the code is blocked for the
seizure attempts following one permitted seizure attempt. On elapse of this blocking
interval the code can be reached again.
Percentage blocking
If a percentage is specified 8 calls are used as basis for 100%.

40

SN2073EU01SN_0002
2002 Siemens AG

Siemens

Administration of the Inter-Exchange Circuit Network

Offered calls

t
Successful call attempts with call Gapping blocking interval 30 s.

t
30 s

30 s

30 s

30 s

Successful call attempts with Blocking Percentage 25%:(2 calls blocked, next six
are through connected)

Fig. 22 Call gapping and percentage blocking example

Code blockpoint Administration


CR CBPT:

CODE=
(may be longer than codepoint CPT administered in same exchange)
[,LAC= ]
[,ORIGDC=]
[,CAT=]
[,ROUTYP=]
PERC=PERC0 or PERC12P5 or ... PERC100
or
CGAP=SEC0 or SEC0P25 or SEC0P5 or SEC1 or ... SEC600 or INF
INCEPT=

Fig. 23 MML commands for code block points

SN2073EU01SN_0002
2002 Siemens AG

41

Siemens

2.4.2

Administration of the Inter-Exchange Circuit Network

Example: Televoting during a TV Program

The problem of high traffic to only one destination is solved by reducing the traffic by
passing through only every n-th call. The blocking should take place in the network
as early as possible
In our example only 75% of the calls to the PBX (090722) with the televoting system
will be passed through.
MML commands:

42

CR
DEST:

DEST=DESTC; plus further inter exchange commands

CR CPT:

CODE=090,
DEST=DESTC;

CR
CBPT:

CODE=090722,
PERC=PERC25,
INCEPT=NETWOMA1;.

SN2073EU01SN_0002
2002 Siemens AG

Siemens

Administration of the Inter-Exchange Circuit Network

CODE=
090722

SIEMENS

SIEMENS

SIEMENS

CODE=
090722

SIEMENS

Call
Gapping

Call
Gapping

traffic to the televoting


system reduced to for
example 75% as early as
possible

SIEMENS

SIEMENS

C 090

PBX

televoting system
090722

Fig. 24 Traffic reduction with call gapping

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

SN2073EU01SN_0002
2002 Siemens AG

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

43

Siemens

2.5
2.5.1

Administration of the Inter-Exchange Circuit Network

Administration of Code Block Point Groups for


Call Rate Reduction (Leaky Bucket)
The Leaky Bucket Model

The feature "Call Rate Reduction" (Leaky Bucket) blocks the outgoing traffic for one
or more destinations. This is done by limiting with help of the leaky bucket call limit
rate, the maximum mean rate of calls. Codes that have to be blocked are combined
in code blocking point groups for this purpose. These groups represent the so-called
buckets.
One leaky bucket call limit rate is assigned to each bucket. Leaky bucket limit call
rate LBUCLCR can take on values between 0.05 and 30 call attempts per second.
Code blocking point groups and leaky bucket limit call rate can be administered by
MML command.
Call attempts rejected by Leaky Bucket go to an intercept.
The Leaky Bucket blockage method, which limits the outgoing traffic to a destination
or group of destinations to a defined number of call attempts per unit of time, is
suitable for overload protection tasks. Its mode of action can be illustrated with a
simple model:
A bucket is filled gradually by seizures for one code blocking point group (group of
codes). Once the bucket is full (depends on bucket depth LBTHR which can be
between 1 and 256 call attempts), it begins to overflow, i.e. additional calls go to an
intercept. As the bucket is leaky, however, its level drops constantly, meaning it can
be continuously re-filled with calls. The loss rate of the bucket can be adjusted by
MML command (adjustment via the nominal rate of calls offered, see example).
The bucket depth indicates the allowed number of call attempts to a bucket
acceptable if the bucket was previously empty. The default value of the bucket depth
is LBTHR=30, i.e. 30 call attempts.
The leaky bucket call limit rate, is the maximum mean rate of calls to certain
destinations. The ratio of leaky bucket limit call rate to the offered call rate
determines how rapidly the bucket will be filled (or how fast the threshold value will
be reached which results in rejection of the calls).

44

SN2073EU01SN_0002
2002 Siemens AG

Siemens

Administration of the Inter-Exchange Circuit Network

offered calls to one destination


or a group of destinations

Default: 30

Overflow
if already 10
calls accepted

INTERCEPT

contains
accepted calls

Controlled by
MML Command

number of calls
per second

Fig. 25 Leaky bucket model

SN2073EU01SN_0002
2002 Siemens AG

45

Siemens

2.5.2

Administration of the Inter-Exchange Circuit Network

Increment and Decrement of the Filling Level

The blocking mechanism determines the filling level of the bucket by upward and
downward counting and comparing the counted value with a predefined threshold
value. This value is set to 200.
l

The upward count - filling of the bucket - takes place by event control due to a call
attempt to the respective groups of destinations. The increment value of the
upward count, i.e. the evaluation of the accepted call, is calculated as:
"filling level" / "bucket depth"

Downward counting takes place according to the decrement value per completed
time interval (1sec). This value is calculated as:
"increment value" x "leaky bucket call limit rate

Example:
leaky bucket limit call rate

= 2 seizures / s (set by MML)

Bucket depth

= 10 seizures

Threshold value

= 200 (of filling level)

Increment value
threshold value / bucket depth

= 20 / seizure (of filling level)

Decrement value
("increment value" x "leaky bucket call rate:

= 40 / s

(set by MML)

20/seizure x 2 seizures/s=40/s)

46

SN2073EU01SN_0002
2002 Siemens AG

Siemens

Administration of the Inter-Exchange Circuit Network

Offered
calls

t [s]

filling
degree
[call attempts x 20]
200
180
160
140
120
100
80
60
40
20
1

t [s]

Fig. 26 Example of call rate reduction

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

SN2073EU01SN_0002
2002 Siemens AG

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

47

Siemens

2.5.3

Administration of the Inter-Exchange Circuit Network

MML Commands

Up to 16 selectable digit combinations can be combined to form one code blocking


point group (CR CBPGRP).
CBPGRPs can be created, modified and canceled by MML. A maximum of 31
CBPGRPs with respectively 16 code block points or, alternatively, 500 CBPGRPs
with respectively one code block point etc., can be created for Leaky Bucket.
Following the creation, the CBPGRP is initially deactivated.
The blockage can be activated/deactivated by MML for each CBPGRP (ACT
CBPGRP). One or more (up to 32) or all CBPGRPs can be activated or deactivated
by one single MML command at a time.
A CBPGRP can be modified both in the activated and deactivated condition.
One, several or all CBPGRPs can be canceled with a single MML command. The
CBPGRPs must be deactivated before they can be canceled, and no longer referred
to by a code block point. The cancellation of several or all CBPGRPs will not be
performed if one of the groups is still active.

48

SN2073EU01SN_0002
2002 Siemens AG

Siemens

Administration of the Inter-Exchange Circuit Network

Creation of a code blocking point group


CR CBPGRP:

CBPGRP= ,
LBUCLCR={LCPS0P05....LCPS30P0}
[,LBTHR=1,2,30];

Creation of a code blocking point


CR CBPT:

CODE= [,LAC=] [,ORIGDC=] [,CAT=] ,


CBPGRP= <predefined code blocking group>
INCEPT= ;

Activation of a code blocking group


ACT CBPGRP:

CBPGRP= {<predefined code blocking group>


[&<cbpgrp>[...&<cbpgrp>]] | X};

Fig. 27 MML commands for leaky bucket

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

SN2073EU01SN_0002
2002 Siemens AG

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

49

Siemens

2.5.4

Administration of the Inter-Exchange Circuit Network

Example for Leaky Bucket

The traffic mean rate to the frequently called destinations 08003 and 08006 and
01904 and 01905 should be limited.
1. Calls to these 0800 destinations should be limited to seize a maximum of 10
trunks. The mean holding time to these destinations is 30 s. The following
estimation shows the traffic mean rate for these numbers:
traffic mean rate [calls/s] = number of trunks / mean holding time [s]
traffic mean rate =10/30s=0.33calls/s
2. Calls to these 0190 destinations should be limited to seize a maximum of 20
trunks. The mean holding time to these destinations is 10 s. The following
estimation shows the traffic mean rate for these numbers:
traffic mean rate [calls/s] = number of trunks / mean holding time [s]
traffic mean rate =20/10s=2calls/s
With help of the MML commands on the opposite page the traffic mean rate to the
mentioned 0800 destinations should be limited to 0.3 calls/s and to the 0190
destinations to 2calls/s.

50

SN2073EU01SN_0002
2002 Siemens AG

Siemens

Administration of the Inter-Exchange Circuit Network

SIEMENS

CODE

SIEMENS

mean traffic rate


to 01904 and 01905
limited to 2 calls/sec
mean traffic rate
to 08003 and 08006
limited to 0.3 calls/sec
SIEMENS

other
traffic

SIEMENS

traffic
traffic
to 01904 to 08003
and 01905 and 08006

Fig. 28 Example of a leaky bucket application

CR CBPGRP :

CBPGRP=CFREE, LBUCLCR=LCPS0P3;

CR CBPT :

CODE = 08003, CBPGRP=CFREE, INCEPT=

CR CBPT :

CODE = 08006, CBPGRP=CFREE, INCEPT=

ACT CBPGRP :

CBPGRP=CFREE;

CR CBPGRP :

CBPGRP=PRC, LBUCLCR=LCPS2P0;

CR CBPT :

CODE = 01904, CBPGRP=PRC, INCEPT=

CR CBPT :

CODE = 01905, CBPGRP=PRC, INCEPT=

ACT CBPGRP :

CBPGRP=PRC;

Fig. 29 MML command example for leaky bucket

SN2073EU01SN_0002
2002 Siemens AG

51

Siemens

2.6

Administration of the Inter-Exchange Circuit Network

Administration of Traffic Discrimination Digits


and Country Code

Traffic Discrimination Digits


The so called traffic discrimination digits used as a prefix for national and
international calls are administered in the following way:
ENTR DNATT:

PFXNAT=

national prefix e.g.0

PFXINAT=

international prefix e.g.00

These prefixes are used to determine the so called "nature of address indicator"
which is used inside the CCS7 ISUP signaling messages to specify whether the
transmitted calling and called party addresses have to be evaluated as a subscriber
number in the national or international format. Inside the CCS7 ISUP messages
neither the national nor the international prefix is transmitted as part of the CdPA /
CgPA.
Own Country Code
Mainly in international gateway exchanges the own country code may be added to
the calling party address CgPA. By this it is guaranteed, that a B-subscriber with
CLIP always receives a A-DN which can be used for a recall.
The own country code is administered in the following way:
ENTR
CNTRYCOD:

52

CC= e.g. 49,

OWNCC=YES;

SN2073EU01SN_0002
2002 Siemens AG

Siemens

Administration of the Inter-Exchange Circuit Network

Exchange

LAC = 043
DN = 55555

Gateway
Country
Code: 33

IAM
dials
004989722...
PFXNAT=0
PFXINAT=00

called party
NA = international number
digits: 49...

PFXNAT=0
PFXINAT=00

calling party:
NA=national number
digits=4355555

IAM
called party
NA = international number
digits: 49...
calling party:
NA= international number
digits=334355555

Fig. 30

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

SN2073EU01SN_0002
2002 Siemens AG

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

53

Siemens

2.7

Administration of the Inter-Exchange Circuit Network

Administration of the Calling Party Address CgPA


Digit Translation (A-DN Screening)

Subscriber individual (also called A number dependent) digit translation (ORIG1),


zoning (ORIG2) or blocking can normally only be performed in the local exchange of
the A-subscriber.
In transit or gateway exchanges without direct subscriber access the ORIG1/2 can
only be assigned to incoming or bothway trunk groups, i.e. no subscriber individual
originating marks are available because ORIG1/2 cannot be signaled.
If A subscriber individual call handling should take place in higher ranking exchanges,
the A-DN received in the calling party address field CgPA of the ISUP IAM has to be
evaluated there.
Therefore the A-DN (CgPA) oriented digit translator ORIG-DAT is necessary in these
exchanges to offer following features:
1. A Number Screening (Blacklist / Whitelist Screening)
If the A-party number is entered in the blacklist (or not entered in a whitelist), the
call is not set up but leads to an intercept . In this case the ORIG-DAT translator
is used as an exchange related screening list for incoming calls.
2. A Number dependant Routing
Depending on the A-party number, the digit translation of the called party address
CdPA can be manipulated by setting a new ORIG1 value.
3. A Number dependant Zoning
Depending on the A-party number, the zoning translation of the called party
address CdPA can be manipulated by setting a new ORIG2 value.
Advantages:
1. Barring of the network usage at the gateway exchange for certain subscribers
(e.g. all subscribers who have no contract with this transit network operator).
2. Special routing for certain subscriber groups (subscriber related routing e.g. to
service numbers)
3. A-party number dependent charging (various tariffs)
Whether the A-DN is evaluated in the ORIG-DAT depends on the GCOS value of the
incoming / bothway trunk group:
GCOS=BLACKLST (or WHITELST) activates CgPA evaluation in the ORIG-DAT

54

SN2073EU01SN_0002
2002 Siemens AG

Siemens

Administration of the Inter-Exchange Circuit Network

SIEMENS

SIEMENS
ORIG-DAT evaluation
Zoning
004917288
NORIG 2 = 50
004917287
NORIG 2 = 51

Incoming
trunk group
GCOS=
BLACKLST

A-number

ORIG-DAT Y
required?

Routing
00491728645
NORIG 1 = 99
00491726132
NORIG 1 = 98

to zoning
translator

Blacklist
00491728943
00491729986

to digittranslator

to
Intercept
to digit and zoning
translator
Gateway or Transit Exchange
Fig. 31 CgPA evaluation

SN2073EU01SN_0002
2002 Siemens AG

55

Siemens

Administration of the Inter-Exchange Circuit Network

The A number (CgPA) digit translator is filled with codes and results by means of the
MML command CR ORIGDAT:
l

The parameter CODE may define a complete A-DN (in national format, i.e. with
LAC and DN) or a partial qualified CgPA, e.g. only the LAC or the LAC and the first
digits of a DN-volume. The ORIG-DAT translator can max. use 260000 Blocks
which means that depending on the length of the code up to about 100000 codes
can be entered.

The result of a code can be:


FEATURE = BLACKLST or WHITELST
If the incoming trunk group has GCOS=BLACKLST the BLACKLIST screening is
performed, i.e. only calls with A-DN not leading to the result BLACKLST are
through connected.
If the incoming trunk group has GCOS=WHITELST the WHITELIST screening is
performed, i.e. only calls with A-DN leading to the result WHITELST are through
connected.
All blocked calls lead to the INCEPT=BLOCKLST:
Additionally it is possible to exclude codes from the screening:
Example:
CODE=0897, FEATURE=BLACKLST
CODE=089722, FEATURE=NOBLACK
All incoming calls with CgPA starting with 0897 are rejected except the A-DN starts
with 089722.
FEATURE=ROUTING, NORIG1=...
A (new) ORIG1 is defined for the following digit translation of the CdPA of this call
FEATURE=CHARGING, NORIG2=...
A (new) ORIG2 is defined for the following zoning of this call

56

Furthermore it is possible to make the evaluation of the A-DN also dependant on


the ORIG1 of the incoming trunk group. Then the A-DN is translated into the given
result only if the incoming trunk group with GCOS=BLACKLST/WHITELST has the
according ORIG1 defined in CR ORIGDAT .

If a call is coming in on a TRGP with GCOS=BLACKLST/WHITELST but the CgPA


is not available the call is rejected and the INCEPT=ANIFLST is accessed. This
takes place if minimum to one code created with CR ORIGDAT the
FEATURE=BLACKLST/WHITELST was assigned.

SN2073EU01SN_0002
2002 Siemens AG

Siemens

Administration of the Inter-Exchange Circuit Network

Creation of ORIGDAT translator


CR ORIGDAT:

CODE=<A-party number or part of it>,


ORIG1=<requested ORIG1 of the incoming TGRP>
{FEATURE = BLACKLST or WHITELST or NOBLACK or
NOWHITE,
FEATURE = ROUTING,NORIG1= <new originating mark1>,
FEATURE = CHARGING,NORIG2= <new originating mark2>};

Fig. 32 Creation of ORIGDAT

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

SN2073EU01SN_0002
2002 Siemens AG

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

57

Siemens

Administration of the Inter-Exchange Circuit Network

Skip White/Black List Blocking for Certain Destinations


l

A destination that shall be reachable by any calling party is administrated as a


non-bearable code point.
When the GP call processing recognized such a code point, beside other
restrictions also a possibly set flag on black/white list evaluation
(GCOS=BLACKLST/WHITELST) is reset by the GP call processing. Due to this
reset value, the CP call processing skips the whole originating data evaluation, i.e.
any black/white list evaluation or any routing and charging information concerning
new ORIG1 / ORIG2.

It is also possible to create destinations, for which only the blocking because of
black/white list evaluation will be ignored.
Within command CR TRATCPT ( create traffic type code point ) the parameter
OVRBWLST is used to define whether a blockage due to black/white list
evaluation has to be overridden or not.
With the chosen solution the existing sequence of evaluation of the several digit
tables by the CP call processing has been kept:
A-Number Eval. Digit Transl. [...] Traffic Type Determ. [...]

58

SN2073EU01SN_0002
2002 Siemens AG

Administration of the Inter-Exchange Circuit Network

Siemens

CR / MOD / DISP TRATCPT: CODE=..., TRAT=...[, OVRBWLST = { NO / YES } ] [,...] ;


Explanation of the new parameter :
OVRBWLST
NO
YES

Override blockage due to black/white list evaluation result


No ( = default value )
Yes

Fig. 33

EXAMPLE FOR THE DESTINATION SPECIFIC SKIPPING OF BLOCKING BY


WHITELIST
Over trunk group number 17 only calls coming from area 089 are allowed.
Exception: The destination 0161 should be assessable by any A-subscriber.
CR TGRP: TGNO=17, OPMODE=BW, GCOS=WHITELST;
=>
For calls via trunk group 17 an additional check on the A-number will be
performed. If the A-number is not part of the white list, the connection will be
rejected and a defined intercept treatment will be executed.
CR ORIGDAT: CODE=089, FEATURE=WHITELST;
=>
Connection is allowed for calls coming from area 089. Any other connection has to
be blocked.
CR TRATCPT: CODE=0161, TRAT=INTRNET, OVRBWLST=YES;
=>
Any connection with destination 0161 will be set up, also those not coming from
area 089.
TIP
Remark: Creation of a non barrable code point with a stem of 0161 would abolish the
feature applied on this example, because a non barrable code point allows generally
the call set up to a given destination, skipping among others the black/white list
check.
Fig. 34

SN2073EU01SN_0002
2002 Siemens AG

59

Siemens

60

Administration of the Inter-Exchange Circuit Network

SN2073EU01SN_0002
2002 Siemens AG

Administration of the Inter-Exchange Circuit Network

Siemens

Destination Areas

SN2073EU01SN_0002
2002 Siemens AG

61

Siemens

Administration of the Inter-Exchange Circuit Network

A destination area is accessed by analyzing the dialing information via one or more
code points. There are several types of destination areas:
1. destination areas with fixed alternative routing
2. destination areas with repeated digit translation
3. destination areas with optimized dynamic routing
4. destination areas with routing dependent on the demanded transmission medium
quality
5. destination areas with conditional alternative routing (carrier quoting)

62

SN2073EU01SN_0002
2002 Siemens AG

Siemens

Administration of the Inter-Exchange Circuit Network

Digit
translation

Destination with
fixed alternative
routing (standard
routing)

Destination with
conditional
alternative routing
(carrier destination)

Destination with
repeat digit
translation

Destination with
routing dependent
on transmission
medium required

Destination with
optimized dynamic
routing

Fig. 35 Different types of destination areas

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

SN2073EU01SN_0002
2002 Siemens AG

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

63

Siemens

3.1
3.1.1

Administration of the Inter-Exchange Circuit Network

Destination Areas with Fixed Alternative Routing


(FAR)
Functionality

Standard destination areas serve to access up to 16 routes. These routes usually


lead to the selection of a trunk group for transferring outgoing calls to another
switching center.
Fixed alternative routing is initiated by trunk group selection. In other words, the
routes are checked in ascending hunting sequence to see whether there is at least
one idle trunk available in the trunk group. The pending seizure is allocated to the
first route in the hunting sequence which offers an idle trunk.
It is possible to create a final overflow code in the event that all lines of all possible
routes are seized. This new digit combination is then fed into the digit translator so
that a result can be found.

TIP
Fixed alternative routing can be deviated from by using the 'rerouting' service feature.
Rerouting means that if an unsuccessful call setup attempt (i.e. an outgoing trunk
group was successfully seized in the own exchange, but all accessed trunk groups
are seized in a transit exchange) is undertaken, the connection is set up via a route
which belongs to an alternative rerouting group from the previous route. This is
carried out in order that the same transit exchanges are not re-accessed.
Rerouting will be discussed in the Route-Chapter.

64

SN2073EU01SN_0002
2002 Siemens AG

Siemens

Administration of the Inter-Exchange Circuit Network

Digits

Digit
translation

Destination area with


fixed alternative routing
route hunting list
final overflow
code
Route
1

Route
16

Fig. 36 Standard destination

SN2073EU01SN_0002
2002 Siemens AG

65

Siemens

3.1.2

Administration of the Inter-Exchange Circuit Network

MML Command

The destination can be created, cancelled and displayed. Following parameters are
relevant:
l

The destination name DEST the destination area is identified with can contain 6 or
12 characters depending on the project. This max. length can be set using the
MML command MOD CALLPOPT: DESTMAXL= {SHORT|LONG}.

If all the trunk groups of the routes have been seized, a repeated translation of
digits can be carried out with the help of the code stored in the FOVCODE
parameter.

DEFEAT
The destination can be marked with some characteristics leading to special call
processing treatment.
AUTOINFO - Automatic information
When a switched through state is obtained, suffixes can be dialed. That is, B side
units, e.g. an automatic information service, require further MFC signals. Thus,
code receivers must not be deactivated.
RCALLBAC
With an A B connection via an operator, a hook flash can be used to bring the
operator back into the call.
FIRSTACT
If this value is set, the network traffic status "primary traffic" is set to the first active
route, which could be the last one.
Omitting this value assigns the network traffic status "primary traffic" to route
number 1 even if that route is deactivated.
FEATCHCK
This parameter value indicates, that the content of the SS7-ISUP IAM has to be
checked against a special "protocol table". This has normally the effect, that the
CgPA (A-DN) is not transmitted in the IAM generated for calls to this destination.

TLIM and MINMAX see following pages

TIP
With MODDEST it is possible to change or delete all the characteristics of a
destination area.

66

SN2073EU01SN_0002
2002 Siemens AG

Siemens

Administration of the Inter-Exchange Circuit Network

Destination Administration
CR DEST:

DEST= [,FOVCODE=] [,MINMAX=] [,TLIM=] [,DEFEAT=];

CAN DEST:

DEST= ;

DISP DEST:

DEST= [,FORMAT=];

Format=

ALL
STD
SORT
NOSORT

display of all types of DEST


display of standard DEST only
display in alphabetic order
display according to SW table entries

Fig. 37 Destination administration

DISPDEST:DEST=X,FORMAT=ALL;
DESTINATION NAMES AND STANDARD ROUTING PARAMETERS
TYP
DEST
: MINMAX DEFEAT
TLIM
--------------+-+------+---------+-----------------------------FKFT690TA
1-20
DIALTM1& RINGTM1& CLEATM1&
OFFCALL& RELTM3
HAMB410MN
1-20
DIALTM1& RINGTM1& CLEATM1&
OFFCALL& RELTM3
DSBG261MN
1-20
DIALTM1& RINGTM1& CLEATM1&
OFFCALL& RELTM3
END TEXT JOB 8084 EXEC'D
X722/CTYCPZ1V1150/P11/113
8084
OMT-00/MSC0

2882/06590

99-10-28

12:30:59

DISPDEST:DEST=X,FORMAT=ALL&SORT;
DESTINATIONS WITH CODE PROCESSING
DEST
TYP NEWCODE/FOVCODE
CONVCODE
------------+-+--------------------+-------------------------------+
IC.NC0049
0
END JOB 8084 EXEC'D

Fig. 38 Display of destinations

SN2073EU01SN_0002
2002 Siemens AG

67

Siemens

68

Administration of the Inter-Exchange Circuit Network

The parameter MINMAX is used to determine the total number of dialed digits to
be collected on the A-side. This is mainly important with inter exchange signaling
systems (e.g. MFCR1 or No5) which do not offer the possibility that the terminating
exchange can send back an "END OF SELECTION" or "ADDRESS COMPLETE"
message to inform the originating exchange that enough digits have been received
to determine the B-party.
With signaling systems using EOS/ACM (e.g.CCS7 ISUP) MINMAX may be used
to offer a stronger timer supervision of the intervals between the dialed digits in
order to avoid an unnecessary long call set up duration after the seizure of the
trunk (MIN is reached).
The parameter MINMAX contains two information units: The minimum number of
digits and the maximum number of digits. A special interdigit timer is set in the
outgoing LTG when the minimum number of digits has been dialed. If the time is
over the address is recognized as complete and transmitted as a block. If the
maximum number of digits has been reached the address is immediately
recognized as complete.
The minimum value of MINMAX must be equal or higher the DINO in the routes of
this DEST.
For DEST of CPT with LAC the LAC has not to be counted for defining the
MINMAX. If the CdPA the includes a LAC, the MINMAX is internally increased by
the number of the LAC digits.

The parameter TLIM enables you to manipulate timers with the help of symbolic
values. Every symbolic value is assigned to one of the GP timers which can be
modified via the command MOD TIOUT.

SN2073EU01SN_0002
2002 Siemens AG

Administration of the Inter-Exchange Circuit Network

Values of
destination specific
timers

GP Timer
DISP TIOUT

Meaning

DIALTM1..3
(default:1)

TIMER7, 8, 9

Dialtime or Address Complete


Supervision Timer on A-side

OFFDIA

No Dialtime supervision

RINGTM0

No Ringtime supervision

Siemens

RINGTM1..7
(default:1)

TIMER19...25

supervision on the A-side of the Bside ringing time

CLEATM1..6
(default:1)

TIMER34...39

A-side delay time between reception


of backward clearing message and
forwarding of RELEASE COMPLETE

RELCLEA

Release immediately after reception


of backward clearing message

OFFEND
RELTM0..3
(default:3)

backward clearing is not supervised


project specific solutions in the Aexchange concerning the handling
(delays) of the release of a call in
forward direction after the calling party
has gone on hook

CONVTM1..7
OFFCALL
(default)

TIMER27...33

A-side Call duration limitation


No A-sideCall duration limitation

Example: Monitoring of the dialing time on the A-party side


CPT: CODE=0893, DEST=ABC...
DEST ABC: MINMAX=8-15, TLIM=DIALTM1.....
A-party dials 08931234567:
>0>8>9>3 >:time supervision by general interdigit timer
>1>2>3>4 >:time supervision by DIALTM1
>5>6>7
>:time supervision by special MINMAX timer
Fig. 39 TLIM parameter values

SN2073EU01SN_0002
2002 Siemens AG

69

Siemens

3.2
3.2.1

Administration of the Inter-Exchange Circuit Network

Destination Areas with Repeated Digit Translation


Functionality

Instead of branching to a route via a destination area it is possible to jump back to the
digit translator with a new or modified code.

70

SN2073EU01SN_0002
2002 Siemens AG

Administration of the Inter-Exchange Circuit Network

Siemens

Digits

Digit translation

Destination area with


repeat digit translation
NEWCODE / CONVCODE

new or
modified code

Fig. 40 Principle of repeated digit translation

SN2073EU01SN_0002
2002 Siemens AG

71

Siemens

Administration of the Inter-Exchange Circuit Network

Example for the application of NEWCODE


The digits of the called party address which are already evaluated in the CP (CODE
of CPT) are replaced with the given NEWCODE. The remaining digits of the called
party address are unchanged.
Now a repeated digit translation is carried out with the NEWCODE plus the
unchanged digits.

72

SN2073EU01SN_0002
2002 Siemens AG

Administration of the Inter-Exchange Circuit Network

LAC=
089

dials 911

Siemens

Police station 1
DN=445566

ORIG1=5

dials 911

Police station 2
DN=556677

ORIG1=10
CR DEST: DEST =
NEWCODE =
CR DEST: DEST =
CR CPT:

CR CPT:

POL 1,
445566;
POL 2,

NEWCODE =

556677;

CODE =

911,

ORIG1 =

5-3,

DEST =

POL 1;

CODE=

911,

ORIG1 =

10-3,

DEST =

POL 2;

Fig. 41

SN2073EU01SN_0002
2002 Siemens AG

73

Siemens

Administration of the Inter-Exchange Circuit Network

Example for the application of CONVCODE


The digits already evaluated and also the non evaluated digits can be altered.
Exception: if a LAC of the exchange is part of the dialed called party address it
remains unchanged.
The following changes are possible:
1. Keep digits unchanged (X)
2. Delete digits (.)
3. Enter digits (+digit)
4. Replace digits (new digit)

74

SN2073EU01SN_0002
2002 Siemens AG

Administration of the Inter-Exchange Circuit Network

digits

Siemens

To DEST=POLN
with CPT=9900

110

digits

To DEST=FIREN
with CPT=9920

112

CR DEST: DEST =
CR CPT:

MODCOD,

CONVCODE =

9 9 X +0;

CODE =

11,

DEST =

MODCOD;

CR DEST: DEST =

POLN;

CR CPT:

CODE =

9900,

DEST =

POLN;

CR DEST: DEST =

FIREN;

CR CPT:

CODE =

9920,

DEST =

FIREN;

Fig. 42

SN2073EU01SN_0002
2002 Siemens AG

75

Siemens

3.2.2

Administration of the Inter-Exchange Circuit Network

Summary: MML Commands

Parameter NEWCODE: you can enter a new code with up to 20 digits here
Parameter CONVCODE: the parameter CONVCODE in the MML command CR
DEST serves to modify the digit combination for a repeat digit translation. The
parameter CONVCODE uses a special code to indicate how to modify the original
code digit by digit. There are special control characters in the CONVCODE that
specify whether to delete, replace or leave etc. the original digit at the respective digit
position or not.
CONVCODE control characters and their meaning

76

the original digit remains at the respective position

the original digit is deleted

+ <digits>

the digits after the + sign are inserted at the respective position

<digits>

the original digits are replaced at the respective position(s)

SN2073EU01SN_0002
2002 Siemens AG

Administration of the Inter-Exchange Circuit Network

Siemens

Destination Administration
CR DEST:

DEST= {[,NEWCODE=] | [CONVCODE=]};

CAN DEST:

DEST= ;

DISP DEST:

DEST= [,FORMAT=];

FORMAT=

ALL

All types of destinations are displayed

STD

Only standard destinations are displayed

SORT

Destinations are displayed in alphabetical


order

NOSORT

Destinations are displayed according to


their table entries

NEWCODE

Destinations with repeat digit translation are


displayed

Fig.43 Destination administration

CONVCODE control characters and their meaning


X

the original digit remains at the resp. position

the original digit is deleted

+ <digits>

the digits after the + sign are inserted at the


resp. position

<digits>

the original digits are replaced at the resp.


position(s)

Fig. 44 CONVCODE syntax

TIP
It is also possible to use the repeated digit translation for changing the ORIG1
(NEWORIG) or the carrier access code (NEWCAC).

SN2073EU01SN_0002
2002 Siemens AG

77

Siemens

3.3
3.3.1

Administration of the Inter-Exchange Circuit Network

Destination Areas with Optimized Dynamic


Routing (ODR)
Functionality

1. Fixed Alternative Routing


As already described in the chapter "destinations with fixed alternative routing"
the sequencing of the routes is only possible with a predetermined overflow
sequence. The position in the overflow sequence was specified by the parameter
ROUTE in the MML command CR ROUTE (further description in the chapter on
administration of routes). This method is known as "fixed alternative routing"
(FAR) and is preferably used in hierarchical networks, since their network
structure defines for the routes a different grade of directness.
2. Optimized Dynamic Routing (ODR)
ODR makes both a load-dependent dynamic route selection with the possibility of
rerouting and an avoidance of circular routing in intermeshed networks possible.
The application of this method requires that the different alternative routes to a
destination are not subject to any equipping priorities because they all have the
same grade of directness. Thus the application is located in intermeshed
networks also called "NON HIERARCHICAL NETWORK (NHN)".
3. Both methods: FAR and ODR can occur (mixed) upon the accessing of a
destination.
4. ODR should not be combined with a trunk group cluster, since the overflow within
the trunk group cluster is blocked by ODR.

78

SN2073EU01SN_0002
2002 Siemens AG

Siemens

Administration of the Inter-Exchange Circuit Network

SIEMENS

SIEMENS

SIEMENS

SIEMENS

SIEMENS

Route 3
SIEMENS

e
ut
o
R

SIEMENS

hierarchical network
with "fixed alternative
routing" (FAR)

SIEMENS

SIEMENS

SIEMENS

Route 1

Node B

Node A
Fig. 45 FAR routing

SIEMENS

d
SIEMENS

mi
a
yn

ou
cr

DR
O
e

SIEMENS

Node A

SIEMENS

Route 1(FAR)

dy
na
mi
c

rou

SIEMENS

SIEMENS

Node B

te
OD
R

SIEMENS

SIEMENS

Meshed network
NHN with "fixed
alternative routing"
(FAR) and
"optimized dynamic
routing" (ODR)

Fig. 46 ODR routing

SN2073EU01SN_0002
2002 Siemens AG

79

Siemens

Administration of the Inter-Exchange Circuit Network

Avoidance of circular routing


In hierarchical networks circular routing can be avoided as it has been up until now
by spotting traffic on the rise and decline in the network hierarchy with the help of the
ORIG1 parameter.
Until now this has presented some difficulties in intermeshed networks. In this case
the ODR procedure offers a new possibility but it also places certain demands on an
intermeshed network:
1. The intermeshing of all nodes:
All nodes of the network need to have a direct connection to all other nodes of the
network.
All nodes can be reached via n-2 (n= number of nodes in the network) equivalent
alternative routes.
2. Transit nodes
Every alternative route needs to run via exactly one transit node.
The selection of the direct route takes place via FAR. The selection of equivalent
alternative routes takes place via ODR. In order to avoid circular routing ODR may
only take place once during call set up in the intermeshed network level. ODR always
takes place in the originating nodes of the intermeshed or non-hierarchical network.
All incoming trunk groups from other nodes of the same network level will be marked
(CR TGRP:GCOS=NHNINC) to indicate that ODR has taken place already. Because
of this marking the system automatically prevents another ODR and accesses the
next node (end node within the non-hierarchical network) via the direct route (with
FAR) or leaves the non-hierarchical network (via FAR).

80

SN2073EU01SN_0002
2002 Siemens AG

Siemens

Administration of the Inter-Exchange Circuit Network

node B
SIEMENS

to

R
FA

node C
SIEMENS

node D

FA
R

to

not inter
meshed
lower or
higher
network
level
e.g. local
area
networks

SIEMENS

inter
meshed
network
level
(NHN)

SIEMENS

SIEMENS

SIEMENS

ODR to B

SIEMENS

TGRP from other ex.


of the NHN
CRTGRP:GCOS=NHNINC,...;

OD
R
to
OD
B
R
to
B

B
to
R
B
OD
to
R
OD

FAR to B

ODR to B

SIEMENS

node A

ODR forbidden

TGRP from local area network or other operator


CRTGRP:GCOS=NHNINC,...;

ODR allowed
Fig. 47 ODR with prevention of circular routing

SN2073EU01SN_0002
2002 Siemens AG

81

Siemens

3.3.2

Administration of the Inter-Exchange Circuit Network

Implementation

Accessing the FAR and ODR routes


Routes can be assigned to a destination area either according to the FAR or the
ODR method. The allocation of FAR routes takes place in the same manner as in
earlier versions.
In order to assign routes according to the ODR procedure, only one ODR list per
destination area may be created, which for its part contains up to 64 equivalent
routes (trunk groups to a destination area). These routes are now dynamically (loaddependent) active.
It must be ensured that no further route is selected in the FAR list after unsuccessful
routing in the ODR list. This does not apply when the ODR list is administratively
blocked and therefore skipped. As a rule, the FAR route(s) should be set up in the
overflow sequence as the first route(s) and the ODR list as an alternative route. As
already mentioned, further routes in the FAR list could follow on the ODR list, which
are then however only accessed, if the ODR list is administratively blocked.
The number of routes within the FAR list, for which call attempts are made before the
ODR list is accessed, is established while setting up the destination area.

82

SN2073EU01SN_0002
2002 Siemens AG

Siemens

Administration of the Inter-Exchange Circuit Network

node D
SIEMENS

S IEMENS

other
network

node A
S IEMENS

SI EME NS

ODR
forbidden
SIEMENS

node B
FAR route 1

S IEMENS

node
C

ODR
allowed

R
OD

meshed
network

te
rou

OD

SIEMENS

S IEMENS

ro
ut
e
SI EMENS

SIEMENS

node E

Fig. 48

FAR and ODR list in Node C


Dest
ODR allowed

Dest =

ODR forbidden NODE B

Routes

LINK= 1
FAR list
route 1

TGNO=CB

further routes
(not shown)

TGNO=CD
ODR List

Admin blocked

route 1
route 2

route n
n = max 16
m= max 64 overall
max 8 routing
attempts for one
call set up

TGNO=CE
further routes

further routes
(not shown)

route m
call release

Fig. 49 ODR principle

SN2073EU01SN_0002
2002 Siemens AG

83

Siemens

Administration of the Inter-Exchange Circuit Network

Route selection in the ODR list


Upon the first call setup the route selection begins ("first choice") in the ODR list with
the path set up as e.g. route 1. This action continues for a total of 6 (project specific
but changeable by means of a patch) attempted call setups; the next 6 new call
attempts begin with route 2, the next 6 with route 3, etc. After the last route in the
ODR list is used as "first choice" the process starts again with route 1.
If this first choice route has "all trunk busy" an attempt will be made to occupy the
next route (overflow) that is not blocked (administratively or dynamically) and that has
a higher route number (ROUTE=).
The number of routing attempts in the ODR list for one call can be restricted
administratively (CR/MOD ODR: MAXATT=1..8). If none of the attempts was
successful, a release follows.

84

SN2073EU01SN_0002
2002 Siemens AG

Administration of the Inter-Exchange Circuit Network

First choice
CR/MODODR:
MAXATT =
(max.seizure
attempts)

First choice

ODR list
route 1
route 2
route 3

Siemens

very first 6
call attempts

route n
ODR list
route 1
route 2
route 3

very second 6
call attempts

route n
ODR list
route 1
route 2
First choice

cyclic overflow

route n-1
route n

First choice
current 6 call attempts

route 1
route 2
route 3

First choice
last 6 call attempts

route n

cyclic first choice

Fig. 50 Route seizure attempts in the ODR list

SN2073EU01SN_0002
2002 Siemens AG

85

Siemens

Administration of the Inter-Exchange Circuit Network

Load-dependent transient blockage of the routes in the ODR list


1. The load-dependent distribution of traffic among the various routes of an ODR list
is achieved by temporary blockage of the routes. There are two different
blockage levels: A and B. These different levels are attained by means of
different events and are also cleared due to different events.
The first call attempt of a maximum of 6 on one ODR route is unsuccessful
because of "all trunk busy" in its own or the next node:
==> The route goes into blockage level A.
The first call attempt on one ODR route was successful, but another (2..6) is
unsuccessful because of "all trunk busy" in the own or the next node:
==> The route goes into blockage level B.
2. Blockage level B is cleared when all routes of the ODR list blocked.
3. Blockage level A is cleared after blockage level B is cleared, but fewer routes
than the maximum number of route seizure attempts per call setup are available
(CR/MOD ODR: MAXATT=)

86

SN2073EU01SN_0002
2002 Siemens AG

Siemens

Administration of the Inter-Exchange Circuit Network

ODR list
first call attempt
for this route
overflow

route n
blockage = A

ODR list
second to sixth
call attempt

route m
blockage = B

TGRP
all trunk busy in
own or next node

Blocking
TGRP
all trunk busy in
own or next node

overflow
all routes blocked
call attempt

route n
blockage = A or B

all routes blocked

Deblocking of all
routes with
blockage B and
continue overflow
for current call
attempt

TGRP
all trunk busy in
own or next node

Deblocking
route n
blockage = B

route n + 1
blockage A
route n + 2
blockage = B
route n +3
blockage = B

if number of
unblocked routes
maximum
route search
attempts
deblocking of routes
with blockage A

Fig. 51 Transient blocking and unblocking

SN2073EU01SN_0002
2002 Siemens AG

87

Siemens

3.3.3

Administration of the Inter-Exchange Circuit Network

MML Commands

1. The command CR ODR provides a new ODR list. It is identified with the help of
the ODR parameter. You can enter the parameter MAXATT to determine the
maximum attempts per call in this list when setting it up.
2. The command CAN ODR deletes an ODR list. The prerequisite for this is that the
list contains no routes anymore and is not linked to any destination area
anymore.
3. A newly set up ODR list has to be activated with ACT ODR.
This command can also be used for reactivating an ODR list deactivated with
DACT ODR or for a compulsory resetting of the temporary bars in the list.
4. The command DISP ODR is used to log the ODR list data.
5. MOD ODR modifies the maximum number of routing attempts per call.
6. CR DEST is used to assign an ODR list which has been allocated routes by
means of CR ROUTE (see Administration of routes) to a destination area. The
parameter LINK specifies the position in the hunting sequence of the FAR list
according to which branching into the ODR list is done.

TIP
1. The command ACT/DACT ODR without parameter ODR list is used as a general
activation / deactivation of the ODR feature.
2. With the command MOD ODR the rerouting function can be switched on and off
(explained in the ROUTE Chapter)

88

SN2073EU01SN_0002
2002 Siemens AG

Administration of the Inter-Exchange Circuit Network

Siemens

ODR List Administration


Creation of a new ODR list
CR ODR:

ODR= [,MAXATT=];

Cancelation of an ODR list


CAN ODR :

ODR= ;

Activation of a newly created or a deactivated ODR list


ACT ODR :

ODR= ;

Deactivation of ODR or an ODR list


DACT ODR :

ODR= ;

Display of the ODR data


DISP ODR:

ODR= ;

Modification of the maximum attempts


MOD ODR:

ODR= ,MAXATT=;

Fig. 52 MML commands for ODR administration

Destination Administration
CR DEST:

DEST= , ODR= , LINK= ;

CAN DEST:

DEST= ;

DISP DEST:

DEST= [,FORMAT=];

FORMAT=

ALL

All types of destinations are displayed

STD

Only standard destinations are displayed

SORT

Destinations are displayed in alphabetical


order

NOSORT

Destinations are displayed according to


their table entries

LINK

A linked ODR list and the link position is


displayed

Fig. 53 MML commands for DEST with ODR administration

SN2073EU01SN_0002
2002 Siemens AG

89

Siemens

Administration of the Inter-Exchange Circuit Network

Example
In the example shown an ODR list is set up with the name ODR9. If the parameter
MAXATT is not set, the default value 4 will be entered.
The ODR list is linked with the route: TGNO U089.
A destination area FKFT699TMM is set up and the ODR list ODR9 linked in after the
first FAR route.
The TGNO U039 is set up as ROUTE1 in the FAR list.

90

SN2073EU01SN_0002
2002 Siemens AG

Siemens

Administration of the Inter-Exchange Circuit Network

<CR ODR:ODR=ODR9;
MSC5/D2MMPK1V16180024/003
1365
OMT-00/SIEMENS0

2878/00007

98-02-20

CRODR:ODR=ODR9;

12:34:13
EXEC'D

END JOB 1365


1377
<DISP ODR:ODR=X;
MSC5/D2MMPK1V16180024/003
1377
OMT-00/SIEMENS0

2882/08885

98-02-20

12:34:21

98-02-20

12:36:11

DISPODR:ODR=X;
ODR GLOBAL : ACT

REROUTING : YES

ODR
MAXATT DACT
--------------+-------+---ODR9
4
*
END JOB 1377 EXEC'D
1411
<CR ROUTE:ODR=ODR9,TGNO=U089,ROUTE=1;
MSC5/D2MMPK1V16180024/003
1411
OMT-00/SIEMENS0

2878/00007

CRROUTE:ODR=ODR9,TGNO=U089,ROUTE=1;

EXEC'D

END JOB 1411


1611
<CR DEST:DEST=FKFT699TMM,ODR=ODR9,LINK=1;
MSC5/D2MMPK1V16180024/003
1611
OMT-00/SIEMENS0

2878/00007

98-02-20

CRDEST:DEST=FKFT699TMM,ODR=ODR9,LINK=1;

12:46:57
EXEC'D

END JOB 1611


1650
<CR ROUTE:DEST=FKFT699TMM,TGNO=U039,ROUTE=1;
MSC5/D2MMPK1V16180024/003
1650
OMT-00/SIEMENS0

2878/00007

CRROUTE:DEST=FKFT699TMM,TGNO=U039,ROUTE=1;

98-02-20

12:49:00
EXEC'D

END JOB 1650

Fig. 54 Example of ODR administration

SN2073EU01SN_0002
2002 Siemens AG

91

Siemens

Administration of the Inter-Exchange Circuit Network

Example cont.
The set up destination is logged without FORMAT parameter and amongst other
things the link to the ODR list is logged.
The ODR list ODR9 is activated.
Remark: Creating the corresponding code points and trunk groups was not
demonstrated in the example.

92

SN2073EU01SN_0002
2002 Siemens AG

Siemens

Administration of the Inter-Exchange Circuit Network

1662
<DISP DEST:DEST=FKFT699TMM;
MSC5/D2MMPK1V16180024/003
1662
OMT-00/SIEMENS0

2882/06379

98-02-20

12:49:32

DISPDEST:DEST=FKFT699TMM;
DESTINATION NAMES AND STANDARD ROUTING PARAMETERS
TYP
DEST
: MINMAX DEFEAT
TLIM
--------------+-+------+---------+-----------------------------FKFT699TMM
1-20
DIALTM1& RINGTM1& CLEATM1&
OFFCALL& RELTM3
END TEXT JOB 1662 EXEC'D
MSC5/D2MMPK1V16180024/003
1662
OMT-00/SIEMENS0

2882/08886

98-02-20

12:49:33

98-02-20

12:50:17

DISPDEST:DEST=FKFT699TMM;
DESTINATIONS WITH OPTIMIZED DYNAMIC ROUTING LINKAGE
DEST
ODR
LINK
--------------+--------------+---FKFT699TMM
ODR9
1
END JOB 1662 EXEC'D
1663
<ACT ODR:ODR=ODR9;
MSC5/D2MMPK1V16180024/003
1663
OMT-00/SIEMENS0
ACTODR:ODR=ODR9;

2878/00007

EXEC'D

END JOB 1663

Fig. 55 Example of ODR administration

SN2073EU01SN_0002
2002 Siemens AG

93

Siemens

94

Administration of the Inter-Exchange Circuit Network

SN2073EU01SN_0002
2002 Siemens AG

Administration of the Inter-Exchange Circuit Network

Siemens

Routes

SN2073EU01SN_0002
2002 Siemens AG

95

Siemens

4.1
4.1.1

Administration of the Inter-Exchange Circuit Network

Standard Routing
Functionality

A standard route links a destination area or an ODR list to a trunk group. In other
words, it is a trunk group leading to a particular destination area.
The hunting sequence is defined when allocating a route to a destination or an ODR
list. The hunting sequence is fixed for the destination area. The rules applying to the
ODR are described in the chapter 'Administration of destination areas'.

96

SN2073EU01SN_0002
2002 Siemens AG

Siemens

Administration of the Inter-Exchange Circuit Network

Destination area
Routes
1

16

ODR List

Route
Route

Routes
Route

64

TGRP
TGRP
TGRP

Route
Route
Route
TGRP
TGRP
TGRP

Fig. 56 Embedding routes into the routing database

SN2073EU01SN_0002
2002 Siemens AG

97

Siemens

4.1.2

Administration of the Inter-Exchange Circuit Network

MML Commands

A route is set up, deleted and logged with the commands CR ROUTE, CAN ROUTE
and DISP ROUTE. Setting up is always performed in ascending hunting sequence
and deleting in descending hunting sequence. Apart from this routes can be inserted
between existing routes or taken out of these by means of INS ROUTE and TAKO
ROUTE.

98

The parameters DEST and TGNO create a linkage between the destination area
and the trunk group. If a route is assigned to an ODR list instead of to a
destination, enter ODR instead of DEST.

The ROUTE parameter consists of 3 information units. The first unit indicates the
position in the sequence. The second unit {Y|N} indicates whether the last trunk of
the accessed trunk group can be seized for this route by normal subscribers. In
case of "N" the last trunk can only be seized by prioritized subscribers. The third
information unit indicates a rerouting group number. This is described separately in
the section 'Rerouting'.

The parameter DICON indicates how to modify the CdPA in forward direction
(explained later).

The parameter LNDES offers information on the application of the CLEARBACK


signal and the handling of meter pulses (METOTR) in case of zoning in higher
exchange. Furthermore all the first FAR route in a NHN is marked with
LNDES=PRIM to allow a more detailed traffic measurement on trunk groups.

The parameter TRACA offers information on the type of the call. This is where
among other things you specify whether it is an emergency call or not (explained
later).

With the help of the parameter ZDIG you can enter a language digit for the
operator-operator calls in order to ensure a connection with an operator of the
same language in the destination country.

The parameter DINO indicates at what point in time outward seizure is executed
and how many digits are to be sent in the CCS7 initial address message IAM. If
you want to send out the IAM as soon as possible (after the digit translation has
found the code point) you have to enter DINO=OVERLAP. The feature
DINO=ENBLOC (sending of the complete CdPA with one messages) can only be
used together with EOS=PROG. The DINO value must not exceed the minimum
value of MINMAX.

The parameter EOS (end of selection) determines whether the exchange will
receive an ADDRESS COMPLETE SIGNAL from the terminating exchange when
the B-party is there determined (EOS=SIGN) or has to determine the end of dialing
by the dial time supervision started in the MINMAX range (EOS=PROG). With
reaching EOS the originating EWSD will deactivate the code DTMF receiver on the
A-subscriber side, through-connect the speech path in the LTG group switch and
activated the ringing time supervision.

SN2073EU01SN_0002
2002 Siemens AG

Administration of the Inter-Exchange Circuit Network

Siemens

The parameter SSDI (start sending digits) is used to influence after which digit of
the processed CdPA the outpulsing of the digits should start. By this you can avoid
that e.g. the first three digits of the CdPA are signaled to the next exchange
because they are not needed anymore. In case of CCS7 ISUP signaling the
parameter SSDI has normally no function.

Route Administration
CR ROUTE:

{DEST= | ODR=}, ROUTE=, TGNO=


[,DINO=] [,TRACA=] [,LNDES=] [,DICON=]
[,SSDI=] [,EOS=] [,ZDIG=];

CAN ROUTE:

{DEST= | ODR=}, ROUTE=, TGNO= ;

DISP ROUTE:

{DEST= | ODR=}, ROUTE=, TGNO= [,FORMAT=];

INS ROUTE:

{DEST= | ODR=}, ROUTE=, TGNO= [,DINO=]


[,TRACA=] [,LNDES=] [,DICON=] [,SSDI=]
[,EOS=] [,ZDIG=];

TAKO ROUTE:

{DEST= | ODR=}, ROUTE=, TGNO= ;

Fig. 57 MML commands for routing administration

TIP
l The last route of a destination can only be cancelled if there is no more CPT
existing for this DEST.
l

The command MOD ROUTE may be used to change the characteristics (e.g.
DINO, DICON) of a ROUTE.

SN2073EU01SN_0002
2002 Siemens AG

99

Siemens

Administration of the Inter-Exchange Circuit Network

TIP
1. The parameter STAT (CR ROUTE) is only used if an exchange still works with
the old concept of inter-exchange revenue account IARA instead of the V11/V12
concept of IACHASTA.
2. Explanation of the parameter values for FORMAT (DISP ROUTE):
(NO)SOR (not)sorted alphabetically
T

100

ALL

active and blocked routes

ACT

active routes

DACT

blocked routes

COMB

FAR and ODR routes

M1ST

first part of the mask (TGNO, DEST, ROUTE, DINO,


SSDI,EOS,LNDES,TRACA,DACT)

M2ND

second part of the mask


(TGNO,DEST,ROUTE,STAT,ZDIG,DICON)

M3RD

third part of the mask (TGNO,DEST,ROUTE,DACT)

MALL

M1ST & M2ND & M3RD

SN2073EU01SN_0002
2002 Siemens AG

Siemens

Administration of the Inter-Exchange Circuit Network

DISPROUTE:DEST=X,FORMAT=ALL&SORT;
DACT
TGNO
DEST
ROUTE DINO
SSDI EOS LNDES
TRACA
:
----------+------------+------+----------+----+----+---------+-------+-O0INT
0INT
1-Y
D2
4
SIGN METOTR & NAT
PRIM
O1INT
1INT
1-Y
D2
4
SIGN METOTR & NAT
PRIM
O0INT
ODR
1-Y
OVERLAP
1
SIGN CLEARBA & NAT
PRIM
END TEXT JOB 5823 EXEC'D

DISPROUTE:DEST=X,FORMAT=ALL&SORT;
ZDIG
DACT
TGNO
DEST
ROUTE STAT : DICON
:
----------+------------+------+----+--+-------------------------------+O0INT
0INT
1-Y
0 0
O1INT
1INT
1-Y
0 0
O0INT
ODR
1-Y
0 0
END JOB 5823 EXEC'D
Fig. 58 Display of routing data

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

SN2073EU01SN_0002
2002 Siemens AG

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

101

Siemens

Administration of the Inter-Exchange Circuit Network

Parameter DICON
The DICON parameter in the MML command CR ROUTE serves to modify the called
party address CdPA for the digits to be transmitted in forward direction. With the help
of a special code the parameter DICON indicates how the original code is to be
modified digit for digit. The control characters indicate whether the original digits in
the respective positions are to be deleted, replaced or retained etc.
DICON control characters and their meaning
X

the original digit remains at the respective position

the original digit is deleted

+<digits>

the digits after the "+" sign are inserted at the respective position

<digits>

the original digits are replaced at the respective position(s)

TIP
l DICON is a route specific modification of the CdPA signaled to the next exchange
and has in opposite to NEWCODE and CONVCODE no influence to the digit
translation in the own exchange.
l

102

DICON has no effect to the dialed LAC of a CdPA, if the according CPT is created
with parameter CODE and LAC

SN2073EU01SN_0002
2002 Siemens AG

Siemens

Administration of the Inter-Exchange Circuit Network

DICON control characters and their meaning


X

the original digit remains at the resp. position

the original digit is deleted

+ <digits>

the digits after the "+" sign are inserted at the


resp. position

<digits>

the original digits are replaced at the resp.


position(s)

Fig. 59 DICON syntax

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

SN2073EU01SN_0002
2002 Siemens AG

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

103

Siemens

Administration of the Inter-Exchange Circuit Network

Parameter TRACA
The route specific traffic category serves to control call processing sequences in the
specific or neighboring exchange.
The procedure is carried out with the TRACA parameter (traffic category). The
various traffic categories used for routes with CCS7 trunk are described in brief as
follows:

104

EMCAL - Emergency call


States that the connection leads to an emergency call destination:
That is, the connection cannot be released from the A-side.
If no trunk of the route is free, a seizure attempt is repeated until a free trunk
becomes available ("pumping" for 30 sec with a connection attempt every 2 sec).
The second information unit of the parameter ROUTE (seizure of the last trunk) of
all other routes using this trunk group is to be set to NO.

RADCALO - Rate adapted calls only

REGICA - Regional call


Generates CAMA call charge data within a local network when there is traffic over
a regional exchange. The area code is set in front of the B-party number.

DIRECT - direct call


Outgoing international traffic from the IN only goes to the destination country via
the direct route, and not via transit countries. This request is signaled in a CCS7
ISUP national parameter (NP:SSP) and is therefore country specific.

OPCAL - Call to operator


Specifies that in the case of a public payphone operator call, an audible coin
validation tone is inserted after the off-hook signal. That is, the A-side is informed
that the operator knows that the calling party is using a public payphone.

NAT - National call


Represents a national call and is , in contrast to TERM, SUB and TRANS, the
default value.

SUB - Subscriber
Used for some CCS 7 user parts to transmit the CdPA without LAC since the next
exchange is the end exchange.

Term - Terminating call international


Specifies that the route leads to an international exchange of the destination
country.
In case of CCS7 ISUP only on routes with TRACA=TERM the parameter SSDI can
be used. In this way you can suppress the country code in the CdPA sent to the
terminating international exchange.

TRANS - Transit call international


Specifies that the route leads to an international exchange used as an international
transit exchange.

SN2073EU01SN_0002
2002 Siemens AG

Siemens

Administration of the Inter-Exchange Circuit Network

Parameter ZDIG (Language Digit)


The language digit (Z-digit) is used to access operator positions with specific
language characteristics. The language digit entered with the parameter is only
transmitted if a Z-digit has not already been received on the incoming side and if the
A-side category is an operator. A-side category means that the A-side operator is in
the exchange, the category has been signaled, or the category is assigned to the
incoming trunk (GCOS=OPOS).

national
network
CdPA=00498972241429

Country Code: 33
PFXINAT= 00
CR ROUTE:
DEST=GER,
ROUTE=1,
TRACA=TRANS,
TGNO=.....

originating
international
gateway

IAM
called party
NA = international number
digits: 498972241429

Country Code: 55
PFXINAT: 00

transit
international
gateway

CR ROUTE:
DEST=GER,
ROUTE=1,

TRACA=TERM,
SSDI=5
TGNO=.....

IAM

terminating
local
exchange

LAC = 089
DN = 722...

Local
area
code
089

IAM
called party
NA = national number
digits: 8972241429

called party
NA = national number
digits: 8972241429

Country Code: 49
Code Point 089
to
destnation MUNICH

terminating
international
gateway

Fig. 60 Parameter TRACA=TREM

SN2073EU01SN_0002
2002 Siemens AG

105

Siemens

4.2

Administration of the Inter-Exchange Circuit Network

Changing the Hunting Sequence

As already mentioned, routes can only be set up in ascending order and deleted in
descending order. Use the command INS ROUTE or TAKO ROUTE to insert or take
routes out of existing ones.
For relocations within the hunting sequence use the command
MOD ROUTE:DEST=.., TGNO=..., ROUTE=<new position>;

106

SN2073EU01SN_0002
2002 Siemens AG

Siemens

Administration of the Inter-Exchange Circuit Network

DEST

DEST
INS ROUTE:
DEST= ,
TGNO=XYZ,
ROUTE=3;

1 TGNO=ABC
2 TGNO=EFG

DEST
TAKO ROUTE:
1 TGNO=ABC
DEST= ,
TGNO=EFG,
2 TGNO=XYZ
ROUTE=2;

1 TGNO=ABC
2 TGNO=EFG

3 TGNO=IJK

3 TGNO=XYZ

3 TGNO=IJK

4 TGNO=LMN

4 TGNO=IJK

4 TGNO=LMN

5 TGNO=LMN

DEST

DEST
MOD ROUTE: 1 TGNO=EFG
DEST= ,
TGNO=ABC,
2 TGNO=IJK
ROUTE=3;

1 TGNO=ABC
2 TGNO=EFG
3 TGNO=IJK

3 TGNO=ABC

4 TGNO=LMN

4 TGNO=LMN

Fig. 61 Modification of route hunting

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

SN2073EU01SN_0002
2002 Siemens AG

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

107

Siemens

4.3
4.3.1

Administration of the Inter-Exchange Circuit Network

Rerouting
Rerouting for FAR Routing

If a desired connection is put through in the own switching system but not through
connected in another switching system e.g. because of "all trunk busy", this is
signaled backwards (e.g. RELEASE with CAUSE "No circuit/channel available"). If
rerouting is activated in the switching system the search for an available trunk group
is continued in the rerouting list.
Of course it does not make any sense to try again via the same transit switches as
there will probably be an "all trunk busy" case again. Therefore, routes that lead via
the same transit switching systems can be joined up to form a group. If the rerouting
case now occurs, the call is branched to a route that belongs to a different rerouting
group than the previous one.
Rerouting is executed only once per call attempt in a switching system.

108

SN2073EU01SN_0002
2002 Siemens AG

Administration of the Inter-Exchange Circuit Network

SIEMENS

DEST =
.............
Route Rer.group
1
1
2
1
3
2
......
.......

SIEMENS

Source

Route 3
Rerouting
Group 2
SIEMENS

SIEMENS

Transit

SIEMENS

Siemens

Route 2
Rerouting Group 1
SIEMENS

SIEMENS

SIEMENS

Transit

Route 1
Rerouting Group 1
SIEMENS

Transit

SIEMENS

Transit

SIEMENS

SIEMENS

all trunk
busy

Destination

R erouting G roup A dm inistration


C R R O U TE :

D E S T=.., TG N O =...,
R O U TE =< route no>-<seize last trunk>-<rerouting group>;

Fig. 62 Rerouting for FAR

SN2073EU01SN_0002
2002 Siemens AG

109

Siemens

4.3.2

Administration of the Inter-Exchange Circuit Network

Rerouting for ODR Routing

If no idle trunk is found within the next network node after a successful outgoing call
in the own node, it will be signaled back and an attempt will be made to seize the
next route (prerequisite: MOD ODR:REROUTE=YES;).
There are no rerouting groups for ODR rerouting as there are for FAR rerouting,
since an intermeshed network with only one transit node is required in this case.
Rerouting is carried out only once per through connection. This limitation is equally
valid for FAR and ODR.
Another limitation is that no rerouting is carried out for ODR if the maximum number
of call attempts has already been reached.

110

SN2073EU01SN_0002
2002 Siemens AG

Siemens

Administration of the Inter-Exchange Circuit Network

al

Ro
ut
e

SIEMENS

lt
ru
nk

bu
sy

DR

RE

IA
M

SIEMENS

SIEMENS

SIEMENS
SIEMENS

Node A

DR

FAR Route 1
w/o REROUTING
e.g. all trunk busy

SIEMENS

Node B

e
ut
Ro
+1

IA

SIEMENS

SIEMENS

MODODR:
REROUTE = YES,...;

Fig. 63 Rerouting for ODR

SN2073EU01SN_0002
2002 Siemens AG

111

Siemens

4.4
4.4.1

Administration of the Inter-Exchange Circuit Network

Routes Formed by Trunk Group Clusters


Functionality

General structure
It is possible to combine up to sixteen outgoing or bothway trunk groups in one trunk
group cluster in order to distribute the offered seizures under certain aspects.
Contrary to the feature "Destination areas with conditional alternative routing" the
distribution is not performed for the entire destination area but is route specific.
1. A trunk group cluster can be used to increase the number of trunk groups per
destination.
2. A trunk group cluster can be used to specify the seizure distribution among the
different trunk groups.

TIP
Trunk group clusters are normally only used in the FAR list.

112

SN2073EU01SN_0002
2002 Siemens AG

Siemens

Administration of the Inter-Exchange Circuit Network

Trunkgroup 1
Destination
Area

Cluster
Trunkgroup 16

Route 1
Route 2

Trunkgroup

Route 3

Trunkgroup 1
Cluster
Trunkgroup 16

Route 16

Trunkgroup

Fig. 64 Structure of trunk group cluster

SN2073EU01SN_0002
2002 Siemens AG

113

Siemens

Administration of the Inter-Exchange Circuit Network

First Choice specification


It is possible to specify the First Choice algorithm within a trunk group cluster. First
Choice is understood to be the trunk group that is checked first for an available trunk
for the respective seizure attempt. If the trunk group has no available trunk the overflow begins.
In contrast to the standard routing the First Choice is changeable for the trunk group
cluster, i.e. in a cluster a different trunk group can be First Choice for each call. For
standard routing the first choice is always route 1 unless it is barred.
The following procedures are available for the First Choice specification:
1. Fixed First Choice sequence (Fixed Sequence)
As with the standard routing the First Choice is always the first trunk group, but
within the cluster in this case. Advantage: Expansion of the trunk groups per
destination.
2. Circular First Choice (Equal Distribution)
For the first seizure attempt the First Choice begins with the first trunk group, for
the second seizure attempt with the second trunk group etc. After the last trunk
group the call is redirected to the first trunk group.
3. Individual First Choice (Variable Distribution)
The First Choice is distributed among trunk groups on the basis of administered
quotas.

114

SN2073EU01SN_0002
2002 Siemens AG

Siemens

Administration of the Inter-Exchange Circuit Network

100%

Trunk
Group
Cluster

Trunkgroup 1

just overflow

Trunkgroup 2
just overflow

Trunkgroup 3
just overflow

Trunkgroup n
Fixed Sequence
1. call

Trunk
Group
Cluster

Trunkgroup 1

2. call

Trunkgroup 2
3. call

Trunkgroup 3
n. call

Trunkgroup n
Equal Distribution
x%

Trunk
Group
Cluster

Trunkgroup 1

y%

Trunkgroup 2
z%

Trunkgroup 3
a%

Trunkgroup n
Variable Distribution
Fig. 65 First choice algorithm

SN2073EU01SN_0002
2002 Siemens AG

115

Siemens

Administration of the Inter-Exchange Circuit Network

Individual overflow specification


In the default case the overflow sequence is circular. This means that in the case of
"all trunk busy" the call flows over to the next trunk group. If you wish, you can obtain
an individual overflow sequence for each trunk group of a cluster, if it happens to be
the First Choice, within the cluster.

116

SN2073EU01SN_0002
2002 Siemens AG

Administration of the Inter-Exchange Circuit Network

1. Choice
Trunk
Group
Cluster

Siemens

Trunkgroup 1

2. overflow
Trunkgroup 2
1. overflow
Trunkgroup 3
3. overflow
Trunkgroup n

1. overflow
Trunk
Group
Cluster

Trunkgroup 1

1. Choice
Trunkgroup 2
3. overflow

Trunkgroup 3

2. overflow
Trunkgroup n

1. overflow
Trunk
Group
Cluster

Trunkgroup 1

3. overflow
Trunkgroup 2
2. overflow
Trunkgroup 3
1. Choice
Trunkgroup n

Fig. 66 Example of first choice individual overflow

SN2073EU01SN_0002
2002 Siemens AG

117

Siemens

4.4.2

Administration of the Inter-Exchange Circuit Network

MML Commands

A trunk group cluster and its name is created with the help of the MML command CR
TGCLU.
1. The FCQSAL parameter indicates which First Choice quota algorithm is to be
valid:
FISEQ fixed sequence
EQDI equal distribution
VARDI variable distribution
2. Under TGFCQ you have to enter the max. 16 TGNO belonging to this Cluster. In
case of FCQSAL=VARDI you have to define under TGFCQ for each TGRP also
the first choice quota in percent.
Example:TGFCQ=TGNOA-60&TGNOB-30&TGNOC-10
3. The parameter ROUSAL can have the values STD (standard) or PB (proportional
bidding). If PB is indicated the trunk groups used in the cluster must not be
assigned to any other cluster with PB anymore.
4. The overflow sequence can be modified trunk group specifically by means of the
MML command MOD TGCLU. The MML command needs to be entered for each
first choice trunk group.
5. A trunk group cluster is assigned to a destination area with CR ROUTE. To do so
set the second information unit in the parameter TGNO to "T" to distinguish the
cluster from simple trunk groups.

118

SN2073EU01SN_0002
2002 Siemens AG

Siemens

Administration of the Inter-Exchange Circuit Network

Trunk Group Cluster Administration


CR TGCLU:

TGCLU= [,ROUSAL=] [,FCQSAL=] ,TGFCQ=

MOD TGCLU:

TGCLU= , TGNO= ,
OVSEQ=<overflow tgno
overflow list postion> &...;

CR ROUTE:

DEST= ,ROUTE= ,TGNO=<tgclu name>-T,...;

Fig. 67 MML command

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

SN2073EU01SN_0002
2002 Siemens AG

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

119

Siemens

120

Administration of the Inter-Exchange Circuit Network

SN2073EU01SN_0002
2002 Siemens AG

Administration of the Inter-Exchange Circuit Network

Siemens

Trunk Groups

SN2073EU01SN_0002
2002 Siemens AG

121

Siemens

5.1

Administration of the Inter-Exchange Circuit Network

Functionality

A trunk group is an administrative collection of several PCM time slots that are
connected to an adjacent node. These are called trunks. The trunks can be used as
traffic or as CCS7 signaling channels.
This joint administration allows a simpler administration by allocating common
properties to all trunks belonging to this trunk group. This of course implies the
allocation of all trunks belonging to this group to a route (see CR ROUTE).
Direction of the call setup
When creating a trunk group, you can specify in which direction the call setup may be
carried out via this trunk group:
l

Call setup from the node in question in the direction of a neighboring node:
"outgoing trunk group"

Call setup from the adjacent node in the direction of the node in question:
"incoming trunk group"

Call setup to and from the neighboring nodes: "double or bothway trunk groups"

TIP
The usage of trunks as CCS7 signaling channels (signaling links) is not discussed in
this chapter.

122

SN2073EU01SN_0002
2002 Siemens AG

Siemens

Administration of the Inter-Exchange Circuit Network

Destination
or ODR list

Route

ROUTE

Trunk group
cluster
No routing

Trunk group
(outgoing or
bothway)
trunk list

Trunk 1

Trunk n

0 1 2 3 ... 31

PCM to adjacent switch

Trunk group
(incoming)
trunk list

Trunk 1

Trunk n

0 1 2 3 ... 31

PCM to adjacent switch

Fig. 68 Trunk group structure

SN2073EU01SN_0002
2002 Siemens AG

123

Siemens

5.2

Administration of the Inter-Exchange Circuit Network

MML Commands

A trunk group is set up, deleted, modified and displayed with the MML commands CR
TGRP, CAN TGRP, MOD TGRP and DISP TGRP.
l

A trunk group is identified with the parameter TGNO trunk group number.
In some countries additionally an up to 12 character long name TGNA and / or an
up to 4 digit long name TGN2 (may be written into the AMA record instead of
TGNO) is used.

The parameter OPMODE specifies whether the trunk group is operated in incoming direction, in outgoing direction or bothway.

The parameter GCOS offers important information on zoning, trunk seizure


mechanisms, signaling, line priority etc. A selection of parameter values is
discussed below.

The parameters ORIG1, ORIG2 and ORIDC imprint a trunk group with an origin
that can be evaluated in the digit translation, zone translation or in the so called
code block point translation.

The parameter PREFIX is used to define a digit string which has to be set in front
of the CdPA received for a call set up coming in on this incoming / bothway trunk
group.

The parameter BLK enables you to enter an administrative or maintenance


blocking.

The commands ENTR and CAN TGDAT serve to change the BLK (administrative
blockings only) and the GCOS parameter. The remaining parameters are modified
with MOD TGRP.

The MML command DISP TGRP displays the trunk group data. The parameter
SORT enables you to sort according to TGNO or OPMODE. The parameter
FORMAT specifies e.g. whether a full or brief information is to be displayed.

The command ENTR/CAN TMBLK is used to enter or remove maintenance


blockings.

TIP
As already discussed the GCOS=NHNINC is used for all incoming / bothway trunk
groups between exchanges of a non hierarchical network NHN with ODR.
Additionally the GCOS=NHNOUT is assigned to outgoing / bothway trunk groups in
this case. Together with the route parameter LNDES=PRIM it enables the traffic
measurement REC TGRP to distinguish for each call whether the TRGP is used as a
FAR or ODR route inside the NHN. In case of using the TRGP as an ODR route it is
further possible to distinguish between usage of the TGRP as first or second section
of a call set up inside the NHN.

124

SN2073EU01SN_0002
2002 Siemens AG

Administration of the Inter-Exchange Circuit Network

Siemens

Trunk Group Administration


Creation of a trunk group
CR TGRP :

TGNO= ,OPMODE= ,GCOS= [,PREFIX=]


[,ORIG1=] [,ORIG2=] [ORIGDC=,] [,BLK=] ....;

Cancelation of a trunk group


CAN TGRP :

TGNO= ;

Modification of a trunk group


MOD TGRP :

TGNO= <,NTGNO= ,
NPREFIX= ,PREFIX= ,NORIG1= ,ORIG1=
,NORIG2= ,ORIG2= ,.....>;

Modification of GCOS and blockings


ENTR TGDAT :

TGNO= <,GCOS= ,BLK=> :

CAN TGDAT :

TGNO= <,GCOS= ,BLK=> :

Display of a trunk group


DISP TGRP :

TGNO= [,OPMODE=] [,GCOS=] [,PREFIX=]


[,ORIG1=] [,ORIG2=] [,BLK=] [,SORT=]
[,FORMAT=] ;

Fig. 69 MML commands trunk group administration

TIP
Beside the parameter TGNO two further additional trunk group identifications can be
entered (country specific use):
l

TGNA
additional up to 12 characters long name

TGN2
additional four digit long identification, in some countries entered into AMA records
instead of the TGNO

SN2073EU01SN_0002
2002 Siemens AG

125

Siemens

Administration of the Inter-Exchange Circuit Network

In the command DISPTGRP you can influence the output by the parameters SORT
and FORMAT:
SORT=OPMODE (default)

sorted according to operating mode

SORT=TGNO

alphabetic sorting

FORMAT=ALL (default)

all data

FORMAT=SHORT

only TGNO and OPMODE

FORMAT=COUNT

only total number of TGRP and number of TGRP


fulfilling the entered criteria (e.g. GCOS=CCS7IUP)

FORMAT=BLOCKED

number of created trunks and number of blocked


trunks

XITE/AD366L8003E/NCGCBK1V1530/T46/000
8454 NetM
X25TH4N2
2871/06349

02-03-20

08:20:13

DISPTGRP:TGNO=X;
TGNO = S0CCS0 OPMODE = BW
MASKNO:06349
GCOS = JSUBORD &NOZON
&C7GLARE &CCS7IUP &PEVENGRP
MASKNO:06348
&USVERS0
SIGVAR
= VAR0
MASKNO:08467
TGNO = S1CCS0 OPMODE = BW
MASKNO:06349
GCOS = JSUBORD &NOZON
&C7GLARE &CCS7IUP &PODDGRP
MASKNO:06348
&USVERS0
SIGVAR
= VAR0
MASKNO:08467
TGNO = S0SPC0 OPMODE = BW
MASKNO:06349
GCOS = JSUBORD &NOZON
&C7GLARE &LPRIO1
&CCS7IUP
MASKNO:06348
&PEVENGRP &DARALLOW &USVERS1
SIGVAR
= VAR0
MASKNO:08467
TGNO = S1SPC0 OPMODE = BW
MASKNO:06349
GCOS = JSUBORD &NOZON
&C7GLARE &LPRIO1
&CCS7IUP
MASKNO:06348
&PODDGRP &DARALLOW &USVERS1
SIGVAR
= VAR0
MASKNO:08467
TGNO = V522
OPMODE = BW
MASKNO:06349
GCOS = JSUBORD &NOZON
&C7GLARE &CCS7IUP &PODD
MASKNO:06348
&USVERS0
SIGVAR
= VAR0
MASKNO:08467
..
..
..
TGNO = O1INT OPMODE = OG
MASKNO:06349
GCOS = PULSDIAL &NONSEQ
MASKNO:06348
SIGVAR
= VAR0
MASKNO:08467
TGNO = O0INT OPMODE = OG
MASKNO:06349
GCOS = PULSDIAL &NONSEQ
MASKNO:06348
SIGVAR
= VAR0
MASKNO:08467
END JOB 8454
Fig. 70

126

SN2073EU01SN_0002
2002 Siemens AG

Siemens

Administration of the Inter-Exchange Circuit Network

XITE/AD366L8003E/NCGCBK1V1530/T46/000
8455 NetM
X25TH4N2
2871/08468

02-03-20

08:21:44

02-03-20

08:22:04

DISPTGRP:TGNO=X,FORMAT=BLOCKED;
TGNO

OPMODE NO. OF
NO. OF
TRUNKS BLOCKED TRUNKS
------+------+-------+-------------S0CCS0
BW
1
0
S1CCS0
BW
1
0
S0SPC0
BW
1
0
S1SPC0
BW
1
0
V522
BW
30
0
VTC1
BW
60
0
RASTC3
BW
62
30
VTC3
BW
31
0
MLIO
BW
30
0
..
..
O1INT
OG
2
0
O0INT
OG
2
0
END JOB 8455
XITE/AD366L8003E/NCGCBK1V1530/T46/000
8463 NetM
X25TH4N2
2871/06349
DISPTGRP:TGNO=X,FORMAT=SHORT;
TGNO
TGNO
TGNO
TGNO
TGNO
TGNO
TGNO

=
=
=
=
=
=
=

S0CCS0
S1CCS0
S0SPC0
S1SPC0
V522
VTC1
RASTC3

OPMODE
OPMODE
OPMODE
OPMODE
OPMODE
OPMODE
OPMODE

=
=
=
=
=
=
=

BW
BW
BW
BW
BW
BW
BW

TGNO
TGNO
TGNO
TGNO

=
=
=
=

STC3
MLII
O1INT
O0INT

OPMODE
OPMODE
OPMODE
OPMODE

=
=
=
=

IC
IC
OG
OG

MASKNO:06349

......................
......................

END JOB 8463

Fig. 71

XITE/AD366L8003E/NCGCBK1V1530/T46/000
8474 NetM
X25TH4N2
2871/06349

02-03-20

08:22:38

DISPTGRP:TGNO=X,OPMODE=OG;
TGNO = O1INT OPMODE = OG
GCOS = PULSDIAL &NONSEQ
SIGVAR
= VAR0
TGNO = O0INT OPMODE = OG
GCOS = PULSDIAL &NONSEQ
SIGVAR
= VAR0

MASKNO:06349
MASKNO:06348
MASKNO:08467
MASKNO:06349
MASKNO:06348
MASKNO:08467

END JOB 8474


Fig. 72

SN2073EU01SN_0002
2002 Siemens AG

127

Siemens

5.3
5.3.1

Administration of the Inter-Exchange Circuit Network

Important GCOS Values


Trunk Seizure Mechanisms

Seizure mechanisms for non CCS7 trunk groups


l

Non Sequential Search (GCOS=NONSEQ):


Following the 'First in - First out' principle, it is always the trunk that has been in
idle state for the longest period of time that is seized in this case. This facilitates
the largest degree of even distribution on the trunks of one trunk group. This is
achieved by linking a trunk that changes from the "seized" state to the "idle" state
into the last position of the trunk list.

Rotating Search (GCOS=ROTARY)


Seizes the next idle trunk following the trunk that was seized for the previous call
setup attempt.

Sequential Search (GCOS=SEQSRCH)


The idle trunk with the smallest line number is seized first.

Sequential Search Backward (GCOS=SEQBKWD)


The idle trunk with the highest line number is seized first. In combination with
SEQSRCH in the neighboring switching center the highest possible level of glaring
protection (seizure of both sides quasi simultaneously with release on both sides)
is achieved for non CCS7 methods.

In case of bothway trunk groups it is possible to give in one of the two exchanges all
trunks the priority for glare situations: GCOS=GLARE.

128

SN2073EU01SN_0002
2002 Siemens AG

Siemens

Administration of the Inter-Exchange Circuit Network

Trunk List
Line No = 1

Line No = 1

Line No = 1

Line No = 1

Line No = 2

Line No = 2

Line No = 2

Line No = 3

Line No = 3

Line No = 3

Line No = 3

Line No = 4

Line No = 4

Line No = 4

Line No = 4

Line No = 5

Line No = 5

Line No = 5

Line No = 5

Line No = 2

initial situation

SIEMENS

SIEMENS

SIEMENS

SIEMENS

Line No 1 seized Line No 2 seized


by own switch
by own switch

First Choice 1. call attempt

Line No = 1

First Choice 2. call attempt

Line No = 2

First Choice 3. call attempt

Line No = 3

First Choice 4. call attempt

Line No = 4

First Choice 5. call attempt

Line No = 5

First Choice

Line No = 1

Line No 2 released

SIEMENS

SIEMENS

SIEMENS

SIEMENS

Line No = 2
Line No = 3
Overflow

Overflow

Line No = 4
Line No = 5

First Choice

Fig. 73 Non-sequential, rotary and sequential Search, sequential search backwards

TIP
The seizure mechanism can be changed for existing trunk groups using the
command ENTR TGDAT: GCOS=

SN2073EU01SN_0002
2002 Siemens AG

129

Siemens

Administration of the Inter-Exchange Circuit Network

Seizure mechanisms with implicit glare rules used for CCS7 trunk groups:
GCOS=PRIOPRE or PGRPPRE
These two seizure mechanisms can only be used on CCS7 trunk groups. In both
cases each switch has grouped the trunks of an outgoing / bothway trunk group in
two different lists:
l

one list contains the trunks for which this switch is prioritized in case of a glare
situation (both switches try to seize the same trunk), i.e. it continues the call set up
in case of glare.

the other list contains the trunks for which this switch is not prioritized in case of a
glare situation, i.e. it has to give up the call set up in case of glare.

Which trunks are belonging to the prioritized and which to the non prioritized list
depends on the SPC value of the adjacent switches and the CIC value of the trunks.
One of two different concepts described above can be used (both switches
connected by a trunk group have to use the same concept):
l

The decision is taken in both switches depending on the CIC and the SPC. The
switch with the higher SPC has priority on the even CICs and vice versa (GCOS
value PRIOPRE).

The decision is taken on the basis of so-called CIC groups and the SPC. The CICs
1...15 form the group 0, the CICs 16...31 form the group 1 and so on. The switch
with the higher SPC has priority on the even CIC groups and vice versa (GCOS
value PGRPPRE).

In other words, the uneven CICs or the CICs of the uneven group are in the priority
list in the switching center with lower SPC and the even CICs (or the CICs of the
even groups) are in the non priority list. In the partner switching center this is exactly
the other way around to avoid glaring as much as possible. This rule for the handling
of the glare situation is indicated with the GCOS value C7GLARE. It is automatically
set if either GCOS=PRIOPRE or PGRPPRE is entered.
The seizure methods applying in the priority list and in the non priority list differ:
l

Priority list: First in First out, i.e. the same procedure as with NONSEQ

Non priority list: Last in First Out, i.e. the trunk cleared last would be seized next

This is important as the non priority list corresponds to the priority list in the partner
switch, i.e. even with seizures from the non priority list glares are still avoided as
much as possible.

130

SN2073EU01SN_0002
2002 Siemens AG

Siemens

Administration of the Inter-Exchange Circuit Network

SIEMENS

SIEMENS

SIEMENS

SIEMENS

prioritized

CIC=<pcm>-1

non prioritized

CIC=<pcm>-2

prioritized

prioritized

CIC=<pcm>-3
CIC=<pcm>-4

non prioritized

non prioritized

non prioritized

prioritized

....
SPC=n-o-p-1

GCOS= PRIOPRE

CIC = <pcm>-1
CIC = <pcm>-3

SPC=n-o-p-7

CIC = <pcm>-2

First In First Out

CIC = <pcm>-4

CIC = <pcm>-5

CIC = <pcm>-6

CIC = <pcm>-7

CIC = <pcm>-8

Priority List

Priority List

CIC = <pcm>-2

CIC = <pcm>-1

CIC = <pcm>-4

Last In First Out

CIC = <pcm>-3

CIC = <pcm>-6

CIC = <pcm>-5

CIC = <pcm>-8

CIC = <pcm>-7

non Priority List

non Priority List

Fig. 74 Priority land non priority lists in case of GCOS=PRIOPRE

TIP
Seizure mechanisms SEQSRCH / SEQBKWD / NONSEQ / ROTARY can also be
used on CCS7 TGRP. In this case following glare rules can be selected:
l

When explicitly entering the GCOS=C7GLARE the following glare rule applies on
the CCS7 trunk group:
higher SPC: priority on even CICs / CIC groups with even number
lower SPC: priority on uneven CICs / CIC groups with uneven number.

When explicitly entering the GCOS=GLARE in one of the two exchanges, this
exchange has priority on all trunks of this trunk group.

SN2073EU01SN_0002
2002 Siemens AG

131

Siemens

132

Administration of the Inter-Exchange Circuit Network

SN2073EU01SN_0002
2002 Siemens AG

Siemens

Administration of the Inter-Exchange Circuit Network

SIEMENS

SIEMENS

non prioritized

CIC=<pcm>-1
CIC=<pcm>-2

SIEMENS

SIEMENS

prioritized

Group 0

....

prioritized

SPC=n-o-p-1

CIC=<pcm>-16
CIC=<pcm>-17

....
GCOS=PGRPPRE

CIC = <pcm>-16
CIC = <pcm>-17

Group 1

non prioritized

SPC=n-o-p-7

CIC = <pcm>-1

First In First Out

CIC = <pcm>-2

CIC = <pcm>-18

CIC = <pcm>-3

CIC = <pcm>-19

CIC = <pcm>-4

Priority List

Priority List

CIC = <pcm>-1

CIC = <pcm>-16

CIC = <pcm>-2

CIC = <pcm>-17

CIC = <pcm>-3
CIC = <pcm>-4
non Priority List

Last In First Out

CIC = <pcm>-18
CIC = <pcm>-19
non Priority List

Fig.75 Prioritized CIC groups

SN2073EU01SN_0002
2002 Siemens AG

133

Siemens

5.3.2

Administration of the Inter-Exchange Circuit Network

Zoning and Ticket Generation

It is possible to administer the billing procedure for incoming connection trunk group
specifically by means of the GCOS parameter.
l

GCOS=ZON
The zoning must be performed for this call. In other words, zone points for incoming
inter exchange calls need to be created in the digit zone translator.

GCOS=AMAREQD
General activation of the AMA ticket generation.

134

SN2073EU01SN_0002
2002 Siemens AG

Siemens

Administration of the Inter-Exchange Circuit Network

SIEMENS

GCOS=ZON

SIEMENS

Zone Translator

CODE ->
ZOPT

Fig. 76 Billing control by trunk group parameter GCOS = ZON

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

SN2073EU01SN_0002
2002 Siemens AG

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

135

Siemens

5.3.3

Administration of the Inter-Exchange Circuit Network

Signaling Specification

The signaling method used for the trunks of a trunk group is specified by means of
the parameter GCOS
ISUP - TGRP
l

GCOS = CCS7IUP
Signaling to other exchanges via CCS No 7 ISDN User Part (ISUP)

SIGVAR = VARx
The VARx is used to differentiate between ISUP variants in the LTG:
VAR0 defines that the CdPA in the IAM may contain maximally 16 digits (as
recommended by ITU/ETSI for ISUP92)
VAR1 defines that there is no restriction concerning the maximum number of digits
of the IAM parameter CdPA (as recommended by ITU/ETSI for ISUP97)
VAR15 defines that only signaling messages/parameters according to the ITU-T
recommended ISUP767 are used.

PROTTAB= (or GCOS=PROPn&PROPm&.....) :


For SS7-ISUP you can define the functional range of supplementary services
supported for this TGRP by the ISUP signaling (administration of the so called
ISUP protocol check).
Since V13 you may use for this purpose instead of the PROP values the
parameter PROTTAB (CRTGRP) or NPROTTAB (MODTGRP). By this you can
assign one out of 64 so called protocol tables. Which supplementary services are
supported by which protocol table can be administered by CR/MOD PROTTAB.
Whether the PROP values of the GCOS parameter or the parameter PROTTAB
have to be used, can be defined by an APS parameter (patch).

TIP
To differentiate between national and international ISUP you have to use the
parameter NETIND of the DPC a TGRP is leading to.

136

SN2073EU01SN_0002
2002 Siemens AG

Administration of the Inter-Exchange Circuit Network

Siemens

Non ISUP - TGRP


l

GCOS=MFCR2/MFCR1/MFNO5/PULSDIAL....
Other signaling methods that can be used apart from CCS No7, e.g. in direction to
analog exchanges:
MFCR2

Multifrequency R2

MFCR1

Multifrequency R1

MFNO5

Multifrequency No 5

MFV

DTMF for USA PBX with DID

PULSDIAL

Decadic signaling

NOTDIAL

Connection of PBX without DID

RINGDOWN

Connection of trunk for operator traffic (e.g. CCITT no. 1). No


register signaling is used. That is, the operator performs the
seizure on both sides or the prefix digits inserted in the incoming
trunk are used for seizure.

Example trunk group to/from a partner ISDN exchange


CR TGRP:
TGNO=U008F, OPMODE=BW, ORIG1=140,
GCOS=ZON&CCS7IUP&PROP1&PRIOPRE
SIGVAR=VAR1;
Fig. 77 Examples of CR TGRP

SN2073EU01SN_0002
2002 Siemens AG

137

Siemens

5.4

Administration of the Inter-Exchange Circuit Network

Overload Control

When an overload is recognized in the CP or in the LTGs, the GPs in the LTGs will
reject new call requests from certain priority classes.
In order to do so, the LTGs determine the so-called global overflow level from the
higher of the values of the (local) CP overload level and the LTG overload level.
Corresponding to the global overload levels, 0...6, the ports connected to the
subscriber lines and trunk groups are divided into a total of 7 priority levels.
The principle is that all seizures are rejected if their priority class is less than the
global overload level, all others are accepted and processed normally.
In the EWSD, subscriber lines and trunk groups are divided into cyclically varying and
fixed priority classes. This measure not only distributes the effects of overloads, but
also makes it possible to service particular types of connection preferentially in an
overloaded situation.
Priorities are issued as follows:
l

Overload priority handling for subscribers


Normal subscribers are divided into 4 equal groups:
Every group is given a "random" priority class of 0....
Every 30 seconds, the priority is automatically replaced, i.e. the assignment is
changed cyclically between groups 0 to 3. This means that they have an equal
chance of achieving a connection setup during an overload situation.
Priority subscribers are given priority class 5 by COS=SUBPRIO.

Overload priority handling for trunk groups


Priority trunk groups are given priority class 0 to 6 by GCOS=LPRIO0 to LPRIO6
Normal trunk groups are split into 5 equal groups (no LPRIOn entered):
Every group is given a "random" priority class of 1....
Every 30 seconds, the priority is automatically replaced, i.e. the assignment is
changed cyclically between groups 1 to 5. This means that they have an equal
chance of achieving a connection setup during an overload situation.

TIP
Each of the global overload level values, 0...6, generally corresponds to a particular
traffic rejection rate, determined by the allocation of subscribers and trunk groups to
the various priority classes. Overload level 7 is only used by the CP, in order to be
able to effect a total stoppage of call processing in special cases - e.g. a recovery.

138

SN2073EU01SN_0002
2002 Siemens AG

Siemens

Administration of the Inter-Exchange Circuit Network

DLU

Normal
subscriber:

LTG

Normal
trunk groups:
1

0
Priority
swapped
cyclically
every 30 s

1
2
3
Priority
subscribers:

Priority
swapped
cyclically
every 30 s

or:

Fixed
assignment
by MML
(GCOS=LPRIOn)

5
Assigned
by MML
command

Priority
trunk groups:

Assigned
by MML
command only
(GCOS=LPRIO6)

Fig. 78

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

SN2073EU01SN_0002
2002 Siemens AG

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

139

Siemens

5.5
5.5.1

140

Administration of the Inter-Exchange Circuit Network

Further Values of Trunk Groups


Further GCOS Values

MFC Categories
If the traffic in an exchange is to be routed depending on the MFC category, but
this cannot be signaled due to the signaling system, the category can be assigned
as trunk group data to incoming and bothway trunk groups.

INTLTRK - International trunk


Used in international gateway exchanges e.g. to add the originating country code
to the calling party address for outgoing calls on this trunk group.

Traffic Classes
It is possible to prevent access to certain destinations by allocating a traffic class
TRACLx to the incoming or bothway trunk groups. Traffic coming in on this trunk
group is then rejected if the CdPA leads to a traffic type code point TRATCPT with
a traffic type TRAT for which the TRACL of the TRGP is blocked (administered by
ENTR TRABLOCK).

LOCTRAFF - Local traffic


Used for traffic to and from other exchanges in the same local network. It is
required to obtain correct traffic assignment for traffic measurement parameter:
REC TRAFLOW.

SATLINK - Satellite link


Specifies, that the trunk group uses a satellite transmission system. Normally
maximum one satellite link from originating to terminating exchange is allowed in
order to avoid to high propagation delay.

DCMS - Digital circuit multiplex system


Specifies that the trunk group leads to a digital circuit multiplex system. Since
voice and non-voice traffic are handled differently by DCMS, it is important for the
system to know whether or not a DCMS is being assessed.

REDIREX - Redirecting exchange


Redirects an unsuccessful call (e.g. subscriber busy) back to an exchange which
has an REDIREX incoming trunk group. The call is then redirected to the operator.

OPERTRK - Operator trunk


Indicates that this trunk group leads to an exchange in which an operator can be
reached. Decides, e.g., in the case of descending international traffic with operator
request, whether an operator is inserted in the local exchange or the request is
forwarded to the next exchange.

SUPCBLK - Suppress code blocking


Indicates that code blocks (Code Block Points with 100% blocking) are ignored for
calls coming in via this TGRP.

SN2073EU01SN_0002
2002 Siemens AG

Siemens

Administration of the Inter-Exchange Circuit Network

GCOS values for Meaning


MFCCAT
JSUBORD
TESTEQ
OPOS
DATRANS
ISUBORD
IDATRANS
IOPOS
CAT11...15

Non-prioritized subscriber (national)


Test call (national)
Operator (national)
Data transmission (national)
Non-prioritized subscriber (international)
Data transmission (international)
Operator (international)
Reserve used country specifically (see
CML)

SUBMFC

Subscriber priority requested

Fig. 79

IGE

GCOS=TRACL10
Incoming call with 00 is rejected

00: TRATCPT with TRAT=INAT


TRACL10: blocked for TRAT INAT
TRACL20: not blocked for TRAT INAT

national
transit
exchange

Incoming call with 00 is throughconnected

GCOS=TRACL 20

Local exchange

Fig. 80

SN2073EU01SN_0002
2002 Siemens AG

141

Siemens

5.5.2

Administration of the Inter-Exchange Circuit Network

PREFIX, ORIG and LAC

Values which are required for the digit translation, but cannot be transmitted, can be
assigned to the incoming / bothway trunk group.
This concerns:
l

Prefix digits (PREFIX)


The digits defined here precede the received digits.

Originating mark 1 (ORIG1) evaluated for determination of the code point CPT

Originating mark 2 (ORIG2) evaluated for determination of the zone point ZOPT

Originating mark for destination control (ORIGDC) evaluated in case of Code


Block Points

Local area code (LAC)

TIP
l The ORIG1/2 of the TGRP can be overwritten by the A-DN digit translator
ORIGDAT
l

142

The LAC of the TGRP can be overwritten by the LAC of the CdPA

SN2073EU01SN_0002
2002 Siemens AG

Siemens

Administration of the Inter-Exchange Circuit Network

IAM with
CdPA=8972241429 &
NA=national number
EWSD
GCOS=CCS7IUP

CPT= 089
DEST=MUNICH

B-DN=8972241429
analog
switch

PREFIX=0
GCOS=PULSDIAL

Fig. 81

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

SN2073EU01SN_0002
2002 Siemens AG

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

143

Siemens

144

Administration of the Inter-Exchange Circuit Network

SN2073EU01SN_0002
2002 Siemens AG

Administration of the Inter-Exchange Circuit Network

Siemens

Trunks

SN2073EU01SN_0002
2002 Siemens AG

145

Siemens

6.1

Administration of the Inter-Exchange Circuit Network

Functionality and MML Commands

A trunk represents a time slot on a PCM carrier that is connected to an LTU in the
LTG and assigned to a trunk group administratively.

WARNING
Before the first trunk can be allocated to a trunk group with CCS No 7 signaling
(GCOS=CCS7IUP) the trunk group needs to be linked to a CCS No7 signaling
point to determine where the signaling message is to be sent to, or for which
trunk group the signaling message was received. This linkage is generated
with the MML command ENTR C7TGREL.
A trunk is defined by the following parameters:
l

TGNO: six character trunk group number. Provides the allocation to a trunk group.

CIC: Circuit Identification Code. Identification of the trunk for ISDN User Part
(ISUP). The CIC is sent together with the corresponding CCS No 7 message (e.g.
IAM Initial Address Message). The CIC consists of two information units: a-b.
a: is usually used for the PCM carrier number (values 0...511 for PCM30).
b: is usually used for the time slot. (values 0...31).
The CIC value must be identical in neighboring switching centers, otherwise
faults will occur in the circuit seizure.

LNO: Line Number: Continual identification of the trunk within a trunk group. If this
is not entered the LNO is issued by the system. Used for administratively addressing of the trunk.

Equipment Number: Consists of the following units:


LTG= <tsg>-<tsg highway number> , LC=<line trunk unit>-<timeslot>

LCOS: Line Class of Service. Contains values for controlling the signaling on the
trunk (project specific).

TRRANGE: Trunk range. With this parameter you can enter the number of trunks
on a PCM carrier that are to be created with one command. The CIC is automatically counted on in ascending order in this case.
The TRRANGE is applied in ascending order beginning with the indicated
equipment number or CIC. In this case the LNOs are used in ascending order
system internally. Canceling trunks may cause problems if they were not
created with TRRANGE and not in the sequence of the ascending equipment
number. E.g. 1. LTG=0-6, LC=3-3, 2. LTG=0-6, LC=3-2, 3. LTG=0-6, LC=3-1,
4.LTG=0-6, LC=3-4 and then ascending. If you were to cancel with TRANGE
now: LTG=0-6, LC=3-1, TRRANGE=31,... the command would be rejected as
there are only 29 trunks left from LC=3-1 on (because the trunks with LC=3-3
& 3-2 have lower LNO than the one with LC=3-1).

146

SN2073EU01SN_0002
2002 Siemens AG

Administration of the Inter-Exchange Circuit Network

Siemens

Trunk Group Relation


ENTR C7TGREL:

TGNO= , DPC= , NETIND= ;

Trunk Administration
CR TRUNK:

TGNO= , LTG= , LC= , CIC= , LCOS= [,TRRANGE= ]


[,LNO=] [,BLK=];

CAN TRUNK:

TGNO= ,{TRRANGE= | LNO= | CIC=};

DISP TRUNK:

TGNO= , {CIC= | LNO=} [,LCOS=][,BLK=][,SORT=]


[,FORMAT=];

FORMAT

SORT

ALL (all trunk data (default))


COUNT (total number of trunks & number of trunks matching selected
criteria
OPMODE sorted according to the OPMODE
TGNO sorted according to the TGNO

Example for LCOS: DIGSIG Values


Application

DIGSIG

No 7 Signalling Channel

DIGSIG ..

ISUP Trunk

DIGSIG ..

Remark:
The administrative blocking of trunks is administered by ENTR / CAN TRDAT
The maintenance blocking of trunks is administered by ENTR / CAN TMBLK
Fig. 82 Trunk administration

WARNING
With CCS7 a maximum of 4096 trunks can be created to one partner exchange
because only 4096 CIC values are available in the CCS7 ISUP messages
according to ITU recommendations.
Nevertheless it is possible to extend the CIC to 13 or 14 bits (only with SSNC).
In this case you may have up to 8191 or 16384 trunks between two nodes (if
you want, all belonging to one trunk group)!

SN2073EU01SN_0002
2002 Siemens AG

147

Siemens

Administration of the Inter-Exchange Circuit Network

XITE/AD366L8003E/NCGCBK1V1530/T46/000
8572

NetM

X25TH4N2

02-03-20

08:39:28

2871/09988

DISPTRUNK:TGNO=X;
TGNO = S0CCS0 OPMODE = BW LNO =
LTG =

1 CIC =

0- 1

0- 2 LC = 0- 1

MASKNO:09988
MASKNO:09989

LCOS

= DIGSIG8

&CCS7IUP

TSTTYP

= 0

MASKNO:09991

CONN

= NUC

MASKNO:40000

TGNO = S1CCS0 OPMODE = BW LNO =


LTG =

MASKNO:09998

1 CIC =

0- 1

0- 2 LC = 1- 1

MASKNO:09988
MASKNO:09989

LCOS

= DIGSIG8

&CCS7IUP

TSTTYP

= 0

MASKNO:09991

CONN

= NUC

MASKNO:40000

TGNO = S0SPC0 OPMODE = BW LNO =


LTG =

MASKNO:09998

1 CIC =

0- 2

0- 2 LC = 0- 2

MASKNO:09988
MASKNO:09989

LCOS

= DIGSIG12 &CCS7IUP

MASKNO:09998

TSTTYP

= 0

MASKNO:09991

TGNO = S1SPC0 OPMODE = BW LNO =


LTG =

1 CIC =

0- 2 LC = 1- 2

0- 2

MASKNO:09988
MASKNO:09989

LCOS

= DIGSIG12 &CCS7IUP

MASKNO:09998

TSTTYP

= 0

MASKNO:09991

........................................................................
........................................................................
TGNO = O0INT
LTG =

OPMODE = OG LNO =

0- 2 LC = 3- 3

LCOS

= DIGSIG4

TSTTYP

= 0

&PULSDIAL

MASKNO:09988
MASKNO:09989
MASKNO:09998
MASKNO:09991

END JOB 8572

Fig. 83

148

SN2073EU01SN_0002
2002 Siemens AG

Siemens

Administration of the Inter-Exchange Circuit Network

XITE/AD366L8003E/NCGCBK1V1530/T47/000
8656 NetM

X25TH4N2

02-03-20 08:46:33

2871/09988

DISPTRUNK:TGNO=X,BLK=ADMIN;
TGNO = RASTC3 OPMODE = BW LNO =
LTG = 0- 4 LC = 3- 1
LCOS
BLK

= DIGSIG12 &CCS7IUP
= ADMIN

TSTTYP = 0
TGNO = RASTC3 OPMODE = BW LNO =
LTG = 0- 4 LC = 3- 2
LCOS
BLK

= DIGSIG12 &CCS7IUP
= ADMIN

TSTTYP = 0
TGNO = RASTC3 OPMODE = BW LNO =
LTG = 0- 4 LC = 3- 3
LCOS
BLK

= DIGSIG12 &CCS7IUP
= ADMIN

TSTTYP = 0

32 CIC = 1- 1

MASKNO:09988

MASKNO:09989
MASKNO:09998
MASKNO:09999
MASKNO:09991
33 CIC = 1- 2

MASKNO:09988

MASKNO:09989
MASKNO:09998
MASKNO:09999
MASKNO:09991
34 CIC = 1- 3

MASKNO:09988

MASKNO:09989
MASKNO:09998
MASKNO:09999
MASKNO:09991

............................................................................................................................................
............................................................................................................................................
TGNO = RASTC3 OPMODE = BW LNO =
LTG = 0- 4 LC = 3-30
LCOS
BLK

= DIGSIG12 &CCS7IUP
= ADMIN

TSTTYP = 0

61 CIC = 1-30

MASKNO:09988

MASKNO:09989
MASKNO:09998
MASKNO:09999
MASKNO:09991

END JOB 8656

Fig. 84

SN2073EU01SN_0002
2002 Siemens AG

149

Siemens

6.2

Administration of the Inter-Exchange Circuit Network

Self-Supervision and Operational Status of Digital


Trunks

The self supervision is running permanently for all trunks:


l

If a fault is detected, the affected trunk is taken out of service automatically.

If preset thresholds for unavailable trunks are exceeded a TGRP-alarm will occur.

The self supervision functions can be divided into different groups:


l

Supervision of the status of the hardware used by the trunk:


a) status of the used LTG / DIU / PORT in the own exchange
(ACT/CBL/MBL/UNA)
b) status of the used PDC in the own exchange (ACT/MAL/SAL)

Supervision of manual blocking of trunks in the own exchange by MML command:


a) trunk is blocked for maintenance (ENTR TMBLK)
b) trunk is blocked for administration (ENTR TRDAT)

Supervision of blocking and unblocking/reset messages sent back by the partner


exchange because:
a) incoming / bothway trunk was blocked in the partner exchange
(trunk group blocking is not reported)
b) LTG / DIU was conditionally blocked in the partner exchange
c) LTG / DIU is unavailable in the partner exchange (UNA/MBL)

Supervision of the CCS7 signaling connection to the exchange the trunk is leading
to:
a) availability/unavailability of the destination point of the partner exchange
(ACT/UNA)
b) missing acknowledgement for blocking or unblocking/reset messages sent to
partner exchange

Optional supervisions activated trunk group individually (ENTR TMCNTL):


a) exceeding of call set up irregularity threshold (MDII)
b) exceeding of threshold for unusual short mean holding time (killer trunk status)
c) exceeding of threshold for extremely long call duration

Status change of trunks performed by the Self Supervision


The status change of the trunks performed by the self supervision is listed in the table
beside.

150

SN2073EU01SN_0002
2002 Siemens AG

Administration of the Inter-Exchange Circuit Network

Event

Siemens

New trunk status in own exchange

DIU/LTG hardware failure in own exchange (UNA) NDIU/NLTG/NPRT


Blocking in own exchange of:
TRUNK or TGRP (MAINT / ADMIN)
LTG / DIU (maintenance blocking)
LTG / DIU (conditional blocking)

BMNT/BADM or GBMN/GBAD
MLTG/MDIU/MPRT
CLTG/CDIU/CPRT

PDC Service Alarm in own exchange

NCAR & NMNI

PDC Maintenance Alarm in own exchange

NCAR & NMNT

threshold exceeded for MDII / KILLERTRUNK


supervision

AUTO

Unavailability of all CCS7 signaling routes to one


partner destination point

CCSF, after 1 min. NSYN

Blocking of trunks (not trunk groups) in partner


exchange
(status change is backward signaled by a CCS7
blocking message)

MOBB
(only used for trunks with CCS7ISUP signaling,
in case of CAS the status BBAC/BPERM is set)

Conditional blocking of LTG/DIU in partner


exchange
(status change is backward signaled by a CCS7
blocking message)

MOBB
(only used for trunks with CCS7ISUP signaling)

Unavailability (UNA/MBL) of LTG/DIU in partner


exchange
(status change is backward signaled by a CCS7
blocking message)

HOBB
(only used for trunks with CCS7ISUP signaling)

Backward signaled blocking/unblocking/reset


messages are not acknowledged by the partner
exchange in between 15 min. although a CCS7
signaling route is available

C7SF (&NSYNP for unacknowledged RESET


messages for releasing of before disturbed or
administartive blocked trunks)
(only used for trunks with CCS7ISUP signaling)

Fig. 85

SN2073EU01SN_0002
2002 Siemens AG

151

Siemens

Administration of the Inter-Exchange Circuit Network

Displaying the Trunk Status


STAT TRUNK: TGNO = ...;
l

search in a trunk group for active trunks (INC, OUT, INT) or trunks being ready for
use (IDLE)

information, if a trunk group contains signaling links (NUC)

check out the problem in case of disturbed trunks


(e.g. NCAR: Level 1 missing; C7SF/NSYN: no CCS7 signaling available;
BMNT/BADM/MPRT/MDIU/MLTG: unit blocked by operator; NPRT/NLTG/NDIU:
HW problem reported by EWSD; MOBB/HOBB: the problem is caused by the
other side of a CCS7 link)

output of the CIC (has to be identical in both exchanges)

STAT TRUNK: TGNO=, STATSUM=Y;


l

statistics concerning the current application of the trunks of a trunk group

STAT TRUNK: TGNO = X, CIC = ;


l

fetch information about a trunk, whose CIC is known

STAT TRUNK: TGNO = X, STATUS = TGIND;


l

output of all trunks which currently are affected by an indication

STAT TRUNK: TGNO = X, STATUS = TGALM;


l

output of all trunks which currently have an alarm

STAT TRUNK: TGNO = ..., STATUS = INC & OUT & IDLE;
l

output of all busy or idle trunks within a given trunk group

STAT PORT: LTG= <tsg> - <ltg>, LC= <diu>;


l

output of trunks related to given ports

ascertain, if a DIU contains active ports (INC, OUT, INT, BUSY) or ports ready for
use (IDLE)

check out the problem for disturbed ports


(e.g. NCAR: Level 1 missing; C7SF: no CCS7 signaling available;
BMNT/BADM/MPRT/MDIU/MLTG/MOBB: units blocked by operator;
NPRT/NLTG/NDIU/HOBB: HW problem detected by EWSD; MOBB/HOBB: the
problem is caused by the other side of a CCS7 link)

DISP CONN: LTG=<tsg> - <ltg>, LC=<diu>


l

152

e.g. for checking out, if there are still connections using the DIU or if the DIU may
be blocked for maintenance

SN2073EU01SN_0002
2002 Siemens AG

Siemens

Administration of the Inter-Exchange Circuit Network

STAT TRUNK: TGNO = ...;


STAT TRUNK: TGNO=..., STATSUM = Y;
STAT TRUNK: TGNO = X, CIC = ;
STAT TRUNK: TGNO = ..., STATUS = TGIND;
STAT TRUNK: TGNO = ..., STATUS = TGALM;
STAT TRUNK: TGNO = ..., STATUS = INC & OUT & IDLE;
STAT PORT: LTG= <ltgset> - <ltg>, LC= <diu> - [<timeslot>];
DISP CONN: LTG= <ltgset> - <ltg>, LC= <diu> [- <timeslot>];
Fig. 86

X722/AD399L8022/NCGCBK1V1530/P00/003
9463

NetM

X25TH4N2

STATTRUNK:TGNO=X,STATSUM=Y;

STATUS

SUM

S0CCS0

NUC

& RNUC

S1CCS0

NUC

& RNUC

S0SPC0

IDLE

S1SPC0

IDLE

I1INT

MDIU

O1INT

NCAR & NMNI

SSTAC2

RNUC & MDIU &

NMNI
RNUC & MDIU &
NMNI
END JOB 9463

X722/AD399L8022/NCGCBK1V1530/P00/003
9464

NetM

X25TH4N2

3069/00007

STATTRUNK:TGNO=X;
TRUNK STATUS LIST

-------+---------------+-------

SSX622

15:36:12
EXEC'D

TRUNK STATUS SUM OVERVIEW


TGNO

02-04-25
3069/00007

TGNO

LNO

CIC

EQTYP

OPMODE

LTG

LC

-------+------+-------+------+-------+------+------+
S0CCS0

0- 1

TRUNK

BW

0- 2 0- 1

S1CCS0

0- 1

TRUNK

BW

0- 2 1- 1

S0SPC0

0- 2

TRUNK

BW

0- 2 0- 2

S1SPC0

0- 2

TRUNK

BW

0- 2 1- 2

I1INT

TRUNK

IC

0- 2 2-17

I1INT

TRUNK

IC

0- 2 2-18

O1INT

TRUNK

OG

0- 2 3-17

O1INT

TRUNK

OG

0- 2 3-18

SSTAC2

TRUNK

IC

0- 4 1- 1

SSX622

TRUNK

IC

0- 4 0- 1

END JOB 9464

Fig. 87

SN2073EU01SN_0002
2002 Siemens AG

153

Siemens

6.3
6.3.1

Administration of the Inter-Exchange Circuit Network

Nailed-up Connection
Functionality

A nailed-up connection is a semi permanent connection between two ports which can
be administered and is switched through by the switching network. The throughconnection can be time-controlled or permanent. If trunk ports are switched in a
nailed-up connection, naturally the respective port in the partner switching center
needs to be switched too.
A typical application for a nailed-up connection is the through-connection of the
CCS7 signaling link from the PCM timeslot (port) to a SILTD module of the CCNC or
the LIC of the SSNC.

154

SN2073EU01SN_0002
2002 Siemens AG

Siemens

Administration of the Inter-Exchange Circuit Network

Nailed - up Connection

PCM

Signaling
Link

LTG

SDC:LTG

SN0&1

Trunks

LTG

SDC:LTG

PCM
Trunks

LTG
SDC:LTG

PCM
CCNC

SDC:CCNC

SILTD s

Nailed - up Connection

Fig. 88 Nailed-up connection

SN2073EU01SN_0002
2002 Siemens AG

155

Siemens

6.3.2

Administration of the Inter-Exchange Circuit Network

MML Commands

A nailed-up connection needs to be set up with the command CR NUC.


l

As already mentioned, a nailed-up connection can be set up for traffic channels as


well as for signaling links. Specify this in the parameter TYPE (PERM, MUX,
TEST).

Specify the ports to be linked with the parameters EQNIC and EQNOG (only for
non trunk ports).
In case of trunk ports you have to use LTGIC/LCIC and LTGOG/LCOG. In this
case it is important that for LTGIC/LCIC you only enter ports within a trunk group
that are incoming or bothway and for LTGOG/LCOG you only enter ports within a
trunk group that are outgoing or bothway.

In case of CCNC the ports of the SS7 signaling links on the PCM must always be
set up as LTGIC/LCIC and the corresponding SILTD port as LTGOG/LCOG.
The LTGOG value of the SILTD port is equal to the number of the highway the
CCNC is connected to the switching network. The LCOG value of the SILTD port
can be found in an allocation list (pseudo LTU/PORT and SILTD) in the TML (CR
NUC).

NOTE
Prerequisite: There must be trunk groups and trunks set up for the respective ports
on the PCM.
After setting up the nailed-up connection it must be activated with the command ACT
NUC. This activation can be performed as a permanent or time controlled activation.

156

SN2073EU01SN_0002
2002 Siemens AG

Administration of the Inter-Exchange Circuit Network

Siemens

Nailed - up Connection Administration (NUC)


Creation of a NUC
CR NUC:

NUC=, EQNIC=, EQNOG=, TYPE= ;


or
NUC=, LTGIC=, LCIC=, LTGOG=, LCOG=,
TYPE=

Cancelation of a NUC
CAN NUC:

NUC= ;

Activation of a NUC
ACT NUC:

NUC= [,UNCOND=] [<,BEG= ,TER= ,IV=


,PER= ,BEGTIME= ,TERTIME=>];

Deactivation of a NUC
DACT NUC:

NUC= [<,BEG= ,TER= ,IV= ,PER=


,BEGTIME= ,TERTIME=>];

Display of a NUC
DISP NUC:

{NUC=
[,EQN=] [,TYPE=] [,STATE=]} ;

Fig. 89 Administration of a nailed-up connection

SN2073EU01SN_0002
2002 Siemens AG

157

Siemens

6.4

Administration of the Inter-Exchange Circuit Network

CCS No 7 Trunk Testing

A trunk that is signaled with CCS No 7 should be created with the blocking ADMIN
and MAINT. Before the trunk is operated it must be tested. Prerequisite for this is the
module RM:CTC in the LTG. Before testing the ADMIN blocking is taken out with the
MML command CAN TRDAT. The test is carried out with the MML command TEST
C7TRUNK. If the test was successful the maintenance blocking is also removed
using the command CAN TMBLK.

158

SN2073EU01SN_0002
2002 Siemens AG

Siemens

Administration of the Inter-Exchange Circuit Network

CR TRUNK:TGNO,LTC,LC,CIC
LCOS=<digsigxx>,
BLK=ADMIN&MAINT

CAN TRDAT:TGNO,CIC
BLK=ADMIN

TEST C7TRUNK: TGNO,


CIC or LNO

N
Was the test successfull?

Fault Clearance
according to the
output mask

CAN TMBLK: TGNO,


CIC or LNO

Fig. 90 Trunk testing

SN2073EU01SN_0002
2002 Siemens AG

159

Siemens

160

Administration of the Inter-Exchange Circuit Network

SN2073EU01SN_0002
2002 Siemens AG

Administration of the Inter-Exchange Circuit Network

Siemens

Administration of Selective Trunk


Reservation

SN2073EU01SN_0002
2002 Siemens AG

161

Siemens

7.1

Administration of the Inter-Exchange Circuit Network

Functionality

The task of the feature trunk reservation consists in giving the operator the
opportunity to allocate one or two trunk reservation levels to trunk groups. Each
reservation level defines a series of free lines (max. all lines of the TGRP) within the
trunk group, the seizure of which is only permitted if certain preset traffic criteria are
fulfilled.
Thus, it is achieved that certain types of traffic are given preference or disadvantage
on specific trunk groups, if the number of free trunks has reached the corresponding
free trunk threshold value or fallen below it.
The calls rejected due to trunk reservation are given an INCEPT=TRSV. The
connection requests rejected to trunk reservation are carried to an additional counter
(i.e. per trunk group) of trunk group traffic measurement and of grade-of-service
measurement (per exchange).
The following traffic criteria are relevant for trunk reservation:
Traffic criteria which depend on either the origination or on the destination:
l

Traffic to preset destinations (i.e. code specific)


Depending on the digits designed for routing in the exchange the traffic to certain
destinations (e.g. 110 police or 112 fire brigade) shall be prioritized. Up to 16 code
specific traffic criteria are possible in this case.

Traffic to non hard to reach destinations


By traffic monitoring it is possible to detect destinations with unusual low answer
seizure rate, called hard to reach destinations. Traffic to non hard to reach
destinations shall be prioritized.

ISDN traffic
This criteria depends on whether the connections A-side is an ISDN subscriber or
a CCS7 ISUP trunk. Incoming ISDN traffic shall be prioritized on outgoing ISDN
trunks as compared to non ISDN traffic.

Priority traffic
Traffic from subscribers with priority shall be prioritized.

Traffic originated by preset incoming trunk groups


Traffic coming in on predefined trunk groups shall be prioritized.

Traffic criteria depending on the used operating mode of bothway trunks:


l

162

Incoming traffic
Incoming traffic is prioritized as compared to outgoing traffic in case of a two way
trunk.

SN2073EU01SN_0002
2002 Siemens AG

Siemens

Administration of the Inter-Exchange Circuit Network

Traffic criteria which depend on the routes used during call setup:
l

Primary traffic
The traffic using a trunk as primary route shall be prioritized as compared to the
traffic using the same trunk as overflow trunk.

Route-traffic
Traffic allocated to certain routes is prioritized

ISDN route traffic


Only ISDN traffic which is allocated to certain routes is prioritized, on the
precondition that the criteria ISDN traffic is fulfilled at the same time.

SIEMENS

SIEMENS

m in
inco
tr
rity
Prio

tru
nk

gr
ou

ic
traff

affic

N
ISD

oup
k gr
trun
ps
ting
grou
ana
runk
O r ig
ay t
othw
on b
ffic

g tra

re
ga
rd
e

Des
tina
tion
spe
Rou
cific
te s
traff
pec
ic
Rou
ific
traf
te s
fic
pec
ific
Prim
ISD
ary
N tr
traf
affic
fi c
Non
har
d to
rea
ch t
raff
ic

max. 4095

max. 4095

not reserved trunks


reserved trunks
for traffic which matches
first or second specified criterion
reserved trunks for traffic which
matches second specified criterion

Fig. 91 Trunk reservation

SN2073EU01SN_0002
2002 Siemens AG

163

Siemens

7.2

Administration of the Inter-Exchange Circuit Network

MML Commands for Trunk Reservation

Administration of Traffic Criteria for Trunk Reservation


l

Traffic criteria with global meaning not to be defined by MML command :


ISDNTRAF (ISDN traffic), PRIMTRAF(Primary traffic), PRIOTRAF (Prioritized
traffic), INCSZURE (Incoming traffic), NONHTR (Non Hard To Reach traffic)

Exchange specific traffic criteria which need to be predefined by MML command


ENTR TRSVCRIT (further commands: DISP TRSVCRIT / CAN TRSVCRIT):
ENTR TRSVCRIT: CRIT=DESTCD01...DESTCD16, CODE=...
Up to 16 code related traffic criteria can be created, i.e. to each of the 16 symbolic
values DESTCDxx one digit combination can be assigned.
ENTR TRSVCRIT: CRIT=ORIGTR01...ORIGTR08, TGNO=...
Up to 8 originating trunk group related traffic criteria can be created, i.e. to each of
the 8 symbolic values ORIGTR01...ORIGTR08 one or several incoming/bothway
TGNO (but only one per command) can be assigned.
ENTR TRSVCRIT: CRIT=ROUTTRAF or ISDNROUT, DEST=...,
ROUTE=<number of the route in the routing table of this destination>
One or several routes may be marked with the criteria ROUTTRAF or ISDNROUT
(can only be assigned to routes formed by trunk groups with CCS7ISUP).
Each definition of code or origin specific criteria is identified additionally by a
symbolic name (either entered with parameter NAME or assigned automatically,
only relevant for administration by Q3).

Administration of Trunk Reservation Traffic Elements (Traffic Criteria


Packages)
A traffic criteria package is created with the command ENTR TRSVTRAF. It defines
two lists of criteria (global or exchange specific created criteria) and is identified by a
symbolic name (either defined under the parameter NAME or assigned
automatically). Further commands: DISP / MOD / CAN TRSVTRAF
All criteria values entered under the parameter CRIT2 are internally automatically
added to the criteria list 1 and the criteria list 2, all criteria values entered under the
parameter CRIT1 are added to the criteria list 1 only. This can be displayed with
DISP TRSVTRAF (here the displayed lists are called CRIT1 and CRIT2). This means
that with the parameters CRIT1 and CRIT2 the two lists of traffic criteria are
predefined for further assignment to TGRPs. In the CML you find which of the criteria
are incompatible, i.e. cannot be combined in one list. Furthermore some
combinations of CRIT1 and CRIT2 are forbidden.

164

SN2073EU01SN_0002
2002 Siemens AG

Siemens

Administration of the Inter-Exchange Circuit Network

Predefinition of criteria
ENTR TRSVCRIT:

CRIT = DESTCD01...16, CODE = ....;

ENTR TRSVCRIT:

CRIT = {ISDNROUT|ROUTTRAF},
DEST = ...., ROUTE =....;

ENTR TRSVCRIT:

CRIT = ORIGTR01..08, TGNO=...;

Definition of trunk reservation traffic elements


ENTR TRSVTRAF:

NAME =
DESTCD01...16

CRIT1 =

PRIMTRAF
ROUTTRAF /
ISDNROUT
ISDNROUT
INCSZURE
PRIOTRAF
ORIGTR01...08
ORIG01PR...08PR
NONHTR

CRIT2=

The parameter values in CRIT1 and 2 can be linked by &

Fig. 92 MML commands for trunk reservation

.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.

SN2073EU01SN_0002
2002 Siemens AG

.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.

165

Siemens

Administration of the Inter-Exchange Circuit Network

Trunk Group specific Administration of the Trunk Reservation Control


(Allocation of a Criteria Package and Reservation Levels to a Trunk Group)
The predefined criteria packages have to be allocated to the reservation levels of a
trunk group. This allocation itself is performed by the command ENTR TRSVCNTL
and identified by a symbolic name (either entered with parameter NAME or assigned
automatically, only relevant for administration by Q3).
The parameter TRSVTRAF contains the symbolic name of the criteria package
assigned to this trunk group (parameter TGNO).
The parameter LEVEL1 defines the number of trunks as an absolute value,
PERCLEV1 as a percentage value reserved for the traffic which matches at least one
of the criteria defined under the parameter CRIT1 or CRIT2 of the assigned
TRSVTRAF (i.e. one of the criteria of the internal criteria list 1).
The parameter LEVEL2 defines the number of trunks as an absolute value,
PERCLEV2 as a percentage value reserved for the traffic which matches at least one
of the criteria defined under the parameter CRIT2 of the assigned TRSVTRAF (i.e.
one of the criteria of the internal criteria list 2).
Inside the lists the criteria are linked with an OR condition. Exception: In case of the
criterion non hard to reach, it is mandatory that the traffic matches at least the
condition non hard to reach.
With TRCNTRL=CANCEL all call set ups rejected on this trunk group because of
trunk reservation are forwarded to the intercept handling (INCEPT=TRSV). With
TRCNTRL=SKIP for all call set ups rejected on this trunk group because of trunk
reservation overflow to the next available route is performed.

166

SN2073EU01SN_0002
2002 Siemens AG

Siemens

Administration of the Inter-Exchange Circuit Network

Definition of the trunk reservation control


ENTR TRSVCNTL: TGNO =
TRSVTRAF =
{LEVEL1 =

1...4095

PERCLEV1=

1.. 100 }

[{LEVEL2 =

1...4095

PERCLEV2=

1...100 }]

TRCNTRL =

{CANCEL/SKIP}

Fig. 93

TIP
It is principally possible to have up to 16383 trunks in a TGRP. Therefore the ISUP
signaling has to be adapted (CIC with 14 instead of 12 bits). In this case the max.
value of the parameters LEVEL1/2 is 16383.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

SN2073EU01SN_0002
2002 Siemens AG

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

167

Siemens

7.3

Administration of the Inter-Exchange Circuit Network

Traffic-oriented Example

Task:
l

ISDN traffic has the highest priority on the trunk group STUTT (10 trunks are
reserved)

Primary traffic regardless if ISDN or not has priority over non ISDN alternative
traffic (5 trunks are reserved)

Solution:
Reservation of idle trunks for primary and ISDN traffic:
ENTR TRSVTRAF: NAME = RES1,
CRIT1 = PRIMTRAF,
CRIT2 = ISDNTRAF;
ENTR TRSVCNTL: TGNO = STUTT,
TRSVTRAF = RES1
LEVEL1 = 10,
LEVEL2 = 5,
TRCNTL
={SKIP|CANCEL};

168

If only 10 trunks of trunk group STUTT are idle, only primary traffic (CRIT1) or
ISDN traffic (CRIT2) is allowed. Calls originated by analog subscribers to for
example Augsburg (alternate traffic) go via the next overflow trunk group
(TRCNTRL=SKIP) available) or are rejected (TRCNTRL=CANCEL).

If only 5 trunks of trunk group STUTT are idle, only ISDN traffic is allowed. Any
calls originated by non ISDN subscribers go via the next overflow trunk group or
are rejected.

SN2073EU01SN_0002
2002 Siemens AG

Siemens

Administration of the Inter-Exchange Circuit Network

Trunk group STUTT


SIEMENS

SIEMENS

...

Munich

(Primary route to
Stuttgart and Karlsruhe,
Overflow route to Augsburg)

5 trunks reserved for


primary traffic or ISDN traffic
not reserved trunks

...
SIEMENS

SIEMENS

Stuttgart
ow
rfl
e
ov

Primary route
to Augsburg

5 trunks reserved for


ISDN traffic only
SIEMENS

SIEMENS

SIEMENS

Augsburg

SIEMENS

Karlsruhe

Fig. 94 Traffic oriented reservation

Example trunk reservation


ENTR TRSVTRAF: NAME = RES1,
CRIT1 = PRIMTRAF,
CRIT2 = ISDNTRAF;
ENTR TRSVCNTL: TGNO = STUTT,
TRSVTRAF = RES1,
LEVEL1= 10,
LEVEL2 = 5,
TRCNTL={SKIP|CANCEL};

Fig. 95 MML command for priority on primary and ISDN primary traffic

SN2073EU01SN_0002
2002 Siemens AG

169

Siemens

7.4

Administration of the Inter-Exchange Circuit Network

Code-oriented Example

Task:
The connection to a service number of the government (for example
CODE=07111122) has priority over all other connections on the trunk group STUTT
(10 trunks reserved).
Solution:
A number of idle lines (max. 15) is reserved for calls to the destination government.
ENTR TRSVCRIT: CRIT = DESTCD01,
CODE = 07111122;
ENTR TRSVTRAF: NAME = RES2,
CRIT1 = DESTCD01;
ENTR TRSVCNTL: TGNO = STUTT,
TRSVTRAF = RES2,
LEVEL1 = 10,
TRCNTL = {SKIP|CANCEL};
If only 10 lines in trunk group STUTT are idle, just calls to destination government
(code 07111122) are allowed. All other calls on trunk group STUTT are rejected or
go via an overflow trunk group until there are at least 11 idle lines.

170

SN2073EU01SN_0002
2002 Siemens AG

Siemens

Administration of the Inter-Exchange Circuit Network

CODE=
07111122

Trunk group STUTT


SIEMENS

(used for traffic to


Stuttgart and Karlsruhe)

SIEMENS

...

Munich

not reserved trunks

...
SIEMENS

SIEMENS

Stuttgart

10 trunks reserved for


traffic with CdPA starting
with CODE = 07111122
SIEMENS

SIEMENS

Karlsruhe

0711 1122

Fig. 96 Code oriented trunk reservation

Example trunk resrevation


ENTR TRSVCRIT: CRIT = DESTCD01,
CODE = 07111122;
ENTR TRSVTRAF: NAME = RES2,
CRIT1 = DESTCD01;
ENTR TRSVCNTL: TGNO = STUTT,
TRSVTRAF = RES2,
LEVEL1 = 10,
TRCNTL ={SKIP|CANCEL};
Fig. 97 MML command for priority for traffic to CODE=1122

SN2073EU01SN_0002
2002 Siemens AG

171

Siemens

172

Administration of the Inter-Exchange Circuit Network

SN2073EU01SN_0002
2002 Siemens AG

Administration of the Inter-Exchange Circuit Network

Siemens

Administration of the Carrier Access Code


CAC Dependent Routing in Deregulated
Networks

SN2073EU01SN_0002
2002 Siemens AG

173

Siemens

Administration of the Inter-Exchange Circuit Network

Due to deregulation, new competitors offering communication services are appearing


on the telecommunications market. Routing must therefore be expanded for the
handling of new operators (carriers). Carrier specific administrative functions are
being introduced to this, and standard routing is being expanded and adapted.
A carrier access code (CAC) has been introduced. This consists of the carrier code,
which is preceded by the carrier prefix (optional). Together, there can be no more
than 6 digits.
The carrier prefix is a string of digits shared by all carriers in the network, with which
all carrier access codes begin. It is meant to facilitate the administration of carriers
and can contain a maximum of 3 digits.
The carrier code is a string of digits which uniquely identifies the carrier in the
network. It is attached to the carrier prefix. Only one carrier prefix can be
administered for the entire network. The individual administration of several prefixes
is not possible.

174

SN2073EU01SN_0002
2002 Siemens AG

Siemens

Administration of the Inter-Exchange Circuit Network

Local network, Augsburg

Long Distance Network

CAR A

Local network, Munich

CAR A

CAR A

CAR B
B-side
CAR B

A-side
CAR B

CAR B

CAR A

Fig. 98

Carrier Access Code CAC

Carrier Prefix
(e.g. 010 in Germany)

Carrier Code
(xyz)

Fig. 99

SN2073EU01SN_0002
2002 Siemens AG

175

Siemens

8.1

Administration of the Inter-Exchange Circuit Network

Input Format for Dialing Information with CAC

From a purely mathematical point of view, the introduction of the CAC brings the
maximum total length of a national dialing sequence to 24 digits (6 CAC + 6 LAC +
12 DN), which means that the exchanges have to be able to evaluate codes with up
to 24 digits.
The CCS7ISUP parameter nature of address NADI for the Called Party Address is up
to now built up by the evaluation of the traffic discrimination code created with ENTR
DNATT: PFXNAT=, PFXINAT=. As long this procedure is not changed the subscriber
will always need to dial the traffic discrimination digit after the CAC.

TIP
At the moment the CAC is not signaled on international trunks.

176

SN2073EU01SN_0002
2002 Siemens AG

Siemens

Administration of the Inter-Exchange Circuit Network

Dialing Information for National Calls


Carrier Access Code

Local Area Code

DN

(CAC)
optional
Prefix

Carrier
Code

optional

traffic
discrimination
code

max. 6 digits

local network

max. 6 digits

max. 12 digits
(Worst Case)

Fig. 100

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

SN2073EU01SN_0002
2002 Siemens AG

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

177

Siemens

8.2
l

Administration of the Inter-Exchange Circuit Network

Possibilities for Carrier Selection

-call-specific carrier selection (CALL BY CALL method)


The A-subscriber can choose an existing carrier for each call individually
by entering a complete CAC digit combination before the actual directory number.

-priority carriers for subscribers (PRESELECT method)


A priority carrier can be defined for each subscriber in the subscriber data base. It
is used if no CAC is dialed.

-priority carrier for exchanges


A priority carrier can be specified for the whole exchange, which can be
understood as a default setting. If the Called Party Address does not start with a
CAC, then the system uses the exchange priority carrier, in the event that no
subscriber priority carrier is specified.

The following priorities are valid for carrier selection with normal subscribers
(listed in order of decreasing priority):
Carrier defined explicitly by the dialed Called Party highest priority
Address
Priority carrier registered in the subscriber/PBX
line data base
Priority carrier registered in the PBX data base
Priority carrier of the exchange

lowest priority

TIP
l If a carrier is specified, regardless of how, then overflow to another carrier will
normally not take place in case of all trunks busy.

178

If a CAC is not specified by the subscriber nor a priority carrier defined, then the
standard code point without CAC is selected.

If a CAC was used in the digit translation, this CAC will be signaled to the next
exchange. In the CCS7ISUP IAM the CAC is transmitted either as part of the
Called Party Address CdPA or in the field Transit Network Selection Control
TSNC.

In EWSD all CAC present in the country have to be created.

SN2073EU01SN_0002
2002 Siemens AG

Siemens

Administration of the Inter-Exchange Circuit Network

CAC is
included in
the ISUP
message
IAM

ALTG

A-subscriber
dials a CAC

A-subscriber
data:
Priority CAC

digit
translation
in CP

CAC is
included in
the ISUP
message
IAM

BLTG

Exchange
Priority CAC

Fig. 101

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

SN2073EU01SN_0002
2002 Siemens AG

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

179

Siemens

8.3

Administration of the Inter-Exchange Circuit Network

MML Commands for CAC Administration

Creating the carrier prefix


ENTR DNATT: PFXCAC=
The carrier prefix is a string of digits shared by all carriers in the entire national
network with which all carrier access codes begin. It comprises a maximum of
3 digits. The prefix can also be created if carrier access codes (CACs) have already
been created. All existing CACs are checked to be sure they begin with the same
digits, which are now defined as the prefix.
Creating a carrier:
CR CAC:

CARRIER= , CAC= ,
[, EXCCACn=] [, OWNCAC= , ROWNCAC=][, SCIALLOW=]
[, DEFNA=];

The parameter CARRIER defines the name of the carrier. It can be chosen freely
but must be unique to the exchange.

The Carrier Access Code is determined with the parameter CAC. This is a
maximum of 6 digits long, is unique to the national network and contains - if
available - the carrier prefix digits as well.

If a exchange priority carrier should be used, it is created with EXCCAC1 / 2=YES.


One or two carrier can be created as the exchange priority carrier. Which of the
two is used depends on the dialed CdPA.

The distinction between CAC of foreign carriers and the CAC of the own network is
made with the parameter OWNCAC.
Only one CAC can be created as the own network CAC (OWNCAC=YES).
Functionality of ROWNCAC=YES:
If the subscriber dials the OWNCAC in order e.g. to overwrite his priority CAC, the
digit translation is ignoring this part of the dialing information but also any priority
CAC of this subscriber.
Advantage: It is not necessary to create for all destinations which can be reached
via the own and foreign networks additionally to the CPT without CAC also a CPT
starting with the own CAC.

180

The ability to choose change the priority CAC via subscriber controlled input is
created with SCIALLOW=YES.

SN2073EU01SN_0002
2002 Siemens AG

Administration of the Inter-Exchange Circuit Network

Siemens

DEFNA describes the information supply of the NADI (nature of address indicator)
in the ISUP.
The default setting is DEFNA=NONAI. This means that the traffic discrimination
code (and not the CAC) defines the type of traffic (national or international traffic).
When a country decides that in case of CAC dialing the traffic discrimination code
is dropped, the CAC itself is used to determine whether a call is national or
international. In this case the DEFNA is set to NAT or INTNAT.

ENTR DNATT:

PFXCAC= ;

CR CAC:

CARRIER= ,
CAC=,
[, EXCCACn=YES]
[, OWNCAC=YES, ROWNCAC=YES/NO]
[, SCIALLOW=YES]
[, DEFNA=];

Fig. 102

SN2073EU01SN_0002
2002 Siemens AG

181

Siemens

8.4
8.4.1

Administration of the Inter-Exchange Circuit Network

CAC Administration on Subscriber Level


Allocation of One (or Two) Priority (Preselected) CAC to
Subscribers

CR/MOD SUB:

LAC=, DN= , ..,


COSDAT=

CAC1

<max. six digit cac>

[CAC2

<max. six digit cac>]

(&CACMOD)

(only if subscribers can change


the CAC per SCI)

A priority CAC can also be allocated to PBX, PBXLN and TGRP.


TIP
l In case of two preselected CAC it has to be administered in the exchange for
which called party addresses which of the two preselected CACs has to be taken
in consideration.
The default value for all call set ups is CAC1.
l

Example:
If a subscriber dials a national number (starting with 0) his CAC1 should be used, if
he dials an international number (starting with 00) his CAC2 should be used.

8.4.2

Blocking of CAC Dialing

It is also possible to define for all subscriber types (SUB, PBX, PBXLN) whether a
carrier access code (CAC) may be dialed or not. This provides a solution for cases
(e.g. calls from hotels) in which the dialing of a CAC by the subscriber is not
desirable. The rejected calls are routed to an intercept.
Block CAC dialing:
CR SUB/PBX/PBXLN :

LAC=
DN=
COS=INCACD

Create associated intercept:


CR INC:

INCEPT=CACNAUTH
DEST=

182

SN2073EU01SN_0002
2002 Siemens AG

Siemens

Administration of the Inter-Exchange Circuit Network

CAC1 / 2 application in the exchange


CR CACCPT:

CODE=0
DEFCAC=CAC1

CR CACCPT:

CODE=00
DEFCAC=CAC2

SIEMENS

Code 0->
Routing
with 01070..

Dials 08711.....
COSDAT=CAC1- 01070
COSDAT=CAC2- 01071
Dials 0033 ....

Code 00->
Routing
with 01071..

Fig. 103

SIEMENS

EWSD

Dials
010700711..

LAC=089

Call set up

PBX
Dials

COS=INHCACD

010700711..

Call is rejected ->


CACNAUTH

Fig. 104

SN2073EU01SN_0002
2002 Siemens AG

183

Siemens

Administration of the Inter-Exchange Circuit Network

8.5
8.5.1

Application of the CAC in the Digit Translation


Functionality of the Carrier Data Table CARDA

Following the deregulation of the market, it became clear that carrier-dependent


routing for specific code points had to be avoided. Prime examples of this are service
numbers (e.g. 0130), emergency calls (e.g. 110) or SCI (subscriber-controlled input)
services that are always routed to the service platform of the local service provider,
even if a carrier code point is dialed.
Destinations in the local area are also affected, since the dialed carrier digits had to
be truncated because a partially extremely awkward routing via one carrier makes
little sense in terms of the cost and the call processing expense.
To keep these problems under control, and to have more flexible handling of code
points with carrier routing in the future, these code points are administered in a
special translator database CARDA using the MML command CR CACCPT.
For each call set up the CARDA is always accessed prior to the digit translator. The
CARDA is entered with the called party address excluding any dialed or preselected
CAC.
Depending on the creation data in this table (different results are also possible for
dialed and preselected CACs) the CdPA of a call may be
l

forwarded to the digit translator with taking a dialed or preselected CAC (if
available) in consideration.
(CARDA result: ROUTE, i.e. use CAC, if available, for routing. This is the default
value, assigned to all called party addresses automatically if no CACCPT was
created for them.).

routed to an intercept code if a CAC was dialed or preselected.


(CARDA result: INCEPT)

forwarded to the digit translator without taking a dialed or preselected carrier


access code in consideration.
(CARDA result: IGNORE, i.e. don't use a dialed or preselected CAC for routing of
the call)

TIP
The evaluation result of the dialed digits can be valid on a global scale, i.e. the same
result for all CACs or different results depending on the CAC (selective).

184

SN2073EU01SN_0002
2002 Siemens AG

Administration of the Inter-Exchange Circuit Network

Siemens

Call set up
with CAC dialing
or
preselected CAC
or
without CAC

CdPA of the call set up excluding any CAC

CARDA
Possible CARDA results:

intercept handling
(INCEP=CACNEXEC)

INCEPT
ROUTE (default value)
IGNORE

CdPA
without dialed or
preselected CAC

Complete CdPA
including dialed or
preselected CAC
(if available)

Digit Translator DITDA


Normal digit translation
according to the created CPTs

Fig. 105

SN2073EU01SN_0002
2002 Siemens AG

185

Siemens

8.5.1.1

Administration of the Inter-Exchange Circuit Network

Creating CACCPT with Global Results

CACCPTs have only to be created for destinations, for which a dialed and / or
preselected CAC should not be used for the normal digit translation.
These destinations are defined in the context with the dialed called party number
(parameter code) and, if specified, information about the origin of the call (parameter
LACOR or ORIG1).
Explanation of the parameter values:
l

CODE
The parameter CODE used here is totally independent of the parameter CODE
used in the command CR CPT.
The chain of digits entered in the parameter code may not be a CAC.

LACOR
The LACOR designates the LAC of the calling party.

ORIG1
The identifier DEF may not be input.

If one of the actions IGNORE, INCEPT or ROUTE is valid for all CACs, all dialed
CACs or all preselected CACs , the following parameters must be used in the
command CR CACCPT:
l

CACGHUC (global handling for dialed and preselected carrier access codes),

CACGHDI (global handling of dialed carrier access codes) and

CACGHPS (global handling of preselected carrier access codes).

TIP
Ambiguous digit combinations can be created:
Example: dialed or preselected CACs should be ignored for calls with a called party
starting with 0130 except the called party has the value 01308888

186

CR CACCPT:

CODE=0130, CACGHUC=IGNORE;

CR CACCPT:

CODE=01308888, CACGHUC=ROUTE;

SN2073EU01SN_0002
2002 Siemens AG

Siemens

Administration of the Inter-Exchange Circuit Network

Administration of CAC handling for certain destinations (CARDA)


CR CACCPT:

CODE=
LACOR=
ORIG1=
CACGHUC=IGNORE/INCEPT/ROUTE
CACGHDI=IGNORE/INCEPT/ROUTE
CACGHPS=IGNORE/INCEPT/ROUTE

Create the intercept


CR INC:

INCEPT=CACNEXEC, ....;

Fig. 106

SIEMENS

EWSD

dials
CAC+110

dials
CAC+471122

LAC=089

Routing without
CAC

Police

Routing without
CAC
Subscriber with
DN 471122 in
same local area
Routing with CAC

dials
CAC+088...
CR CACCPT:

CODE
= 11
CACGHUC = IGNORE;

CR CACCPT:

CODE
= 4
CACGHUC = IGNORE;

National call to
destination area
088 via the
selected carrier

Fig. 107

SN2073EU01SN_0002
2002 Siemens AG

187

Siemens

8.5.1.2

Administration of the Inter-Exchange Circuit Network

Creating CACCPT with Special Results

In opposite to the CACCPT with global results, i.e. with a standard handling of all
dialed and / or preselected CAC it is also possible to define for a CACCPT a so
called CAC specific handling. This means, that for these CODEs the result of the
CARDA depends on the value of the dialed and / or preselected CAC.
Creating CAC lists
The command CR CACLST can be used to administer a list of 32 carrier access
codes and define the handling of these carrier access codes (IGNORE, ROUTE
(default) or INCEPT).
Note: The MOD CACLST command can be used to extend this list to up to 255
entries for each exchange. The CACs added to an existing CAC list may get
assigned a different type of handling than the one defined in the CR CACLST
command.
Assigning a CAC list to a CACCPT
A CAC list is assigned to a CODE of the CARDA by using following command:
CR CACCPT:

CODE=, LACOR=, ORIG1=,


{CACSHUC= | CACSHDI =| CACSHPS=},

The parameters
l

CACSHUC (special handling of dialed and preselected carrier access codes),

CACSHDI (special handling of dialed carrier access codes) and

CACSHPS (special handling of preselected carrier access codes)

are used to define the name of the CAC list assigned to this CODE.

188

SN2073EU01SN_0002
2002 Siemens AG

Administration of the Inter-Exchange Circuit Network

Siemens

SIEMENS

EWSD

LAC=089

Routing without
CAC

dials
cacx+0800

Routing with CAC


dials
cacy +0800
dials
cacz +0800

Routing without
CAC

CR CACLST:

NAME
CAC
ACTION

= name1
= cacx&cacz
= IGNORE;

CR CACCPT:

CODE
= 0800
CACSHDI = name1;

Fig. 108

Set the routing for certain destinations


CR CACCPT:

CODE=
LACOR=
ORIG1=
CACSHUC= <name of a list>
CACSHDI= <name of a list>
CACSHPS= <name of a list>

Create / modify a CAC list


CR CACLST:

NAME=<name>
CAC= 32 CACs can be linked in one command
ACTION=IGNORE/INCEPT/ROUTE

MOD CACLST

NAME=
CAC=
ACTION=

Fig. 109

SN2073EU01SN_0002
2002 Siemens AG

189

Siemens

Administration of the Inter-Exchange Circuit Network

Further examples:

CR CACCPT: CODE=0800,CACGHDI=INCEPT,
CACGHPS=IGNORE;

If a CAC and a no charge number (0800xxxx) are


dialed, this call is routed to the intercept
CACNEXEC and all preselected CACs are
ignored.

CR CACCPT: CODE=0800,CACGHPS=IGNORE; The preselected (default CAC) is ignored for


routing to the no charge number.
CR CACLST: NAME=<name1>,
CAC=01050&01090, ACTION=INCEPT; and
CR CACCPT: CODE=089,CACSHDI=<name1>,
CACGHPS=IGNORE;

When dialing the CACs 01050 or 01090 and a


number with 089xxxx, the call is routed to the
intercept CACNEXEC and all preselected CACs
are ignored.

CR CACCPT: CODE=1,CACGHUC=IGNORE;

All dialed and preselected CACs for numbers that


begin with '1 (e.g. 110, 112) are ignored.

CR CACCPT: CODE=2,CACGHPS=IGNORE;

Only the default CACs for routing to destinations


whose numbers begin with 2 are ignored.

Fig. 110

190

SN2073EU01SN_0002
2002 Siemens AG

Siemens

Administration of the Inter-Exchange Circuit Network

CR CACLST: NAME=<name2>,
CAC=01070,ACTION=IGNORE; and
CR CACCPT: CODE=0881,
LACOR=089,CACSHUC=<name2>;

CAC 01070 is ignored for routing to 0881xxx for


calls from 089xxx, regardless of whether it was
preselected or dialed.

CR CACCPT:
CODE=088122,CACGHUC=IGNORE;

All dialed or preselected CACs for routing to the


destination 088122 are ignored, regardless of the
origin of the call.

CR CACCPT: CODE=001,CACSHDI=<name2>;

Ignores CAC 01070 for routing to 001 only if the


CAC was dialed

CR CACCPT:
CODE=00122,CACGHUC=ROUTE;

All dialed and preselected CACs for routing to the


destination 00122 are used, even CAC 01070.

Fig. 111

. .
. .
. .
. .
. .
. .
. .
. .
. .
. .
. .
. .
. .
. .
. .
. .
. .
. .
. .
. .
. .
. .
. .
. .
. .
. .
. .
. .
. .
. .
. .
. .

. . . . . .
. . . . . .
. . . . . .
. . . . . .
. . . . . .
. . . . . .
. . . . . .
. . . . . .
. . . . . .
. . . . . .
. . . . . .
. . . . . .
. . . . . .
. . . . . .
. . . . . .
. . . . . .
. . . . . .
. . . . . .
. . . . . .
. . . . . .
. . . . . .
. . . . . .
. . . . . .
. . . . . .
. . . . . .
. . . . . .
. . . . . .
. . . . . .
. . . . . .
. . . . . .
. . . . . .
. . . . . .

SN2073EU01SN_0002
2002 Siemens AG

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

. . .
. . .
. . .
. . .
. . .
. . .
. . .
. . .
. . .
. . .
. . .
. . .
. . .
. . .
. . .
. . .
. . .
. . .
. . .
. . .
. . .
. . .
. . .
. . .
. . .
. . .
. . .
. . .
. . .
. . .
. . .
. . .

. . . . . . .
. . . . . . .
. . . . . . .
. . . . . . .
. . . . . . .
. . . . . . .
. . . . . . .
. . . . . . .
. . . . . . .
. . . . . . .
. . . . . . .
. . . . . . .
. . . . . . .
. . . . . . .
. . . . . . .
. . . . . . .
. . . . . . .
. . . . . . .
. . . . . . .
. . . . . . .
. . . . . . .
. . . . . . .
. . . . . . .
. . . . . . .
. . . . . . .
. . . . . . .
. . . . . . .
. . . . . . .
. . . . . . .
. . . . . . .
. . . . . . .
. . . . . . .

. . . .
. . . .
. . . .
. . . .
. . . .
. . . .
. . . .
. . . .
. . . .
. . . .
. . . .
. . . .
. . . .
. . . .
. . . .
. . . .
. . . .
. . . .
. . . .
. . . .
. . . .
. . . .
. . . .
. . . .
. . . .
. . . .
. . . .
. . . .
. . . .
. . . .
. . . .
. . . .

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

. . . .
. . . .
. . . .
. . . .
. . . .
. . . .
. . . .
. . . .
. . . .
. . . .
. . . .
. . . .
. . . .
. . . .
. . . .
. . . .
. . . .
. . . .
. . . .
. . . .
. . . .
. . . .
. . . .
. . . .
. . . .
. . . .
. . . .
. . . .
. . . .
. . . .
. . . .
. . . .

191

Siemens

8.5.2
l

Administration of the Inter-Exchange Circuit Network

Administration of Code Points in Deregulated Networks

Code points for destinations without CAC evaluation


These CPT are set up without using CAC digit chains in the CODE parameter:
CR CPT: CODE=<part of the called number>, DEST= ABC;

Code points for destinations with CAC evaluation


If a destination XYZ can be reached through CARRIER1 (own network) and
through CARRIER2 (foreign network) are set up as follows:
CR CPT: CODE=<CAC1 + part of the called number>, DEST=XYZ1;
CR CPT: CODE=<CAC2 + part of the called number>, DEST=XYZ2;
The routing table connected with the destination XYZ1 contains trunk groups that
lead to the network of CARRIER1, while the routing table connected with the
destination XYZ2 contains trunk groups that lead to the network of CARRIER2.

192

SN2073EU01SN_0002
2002 Siemens AG

Siemens

Administration of the Inter-Exchange Circuit Network

Code Points without CAC evaluation (CODE does not include a CAC)
These CPT can only be accessed if the
CRCPT: CODE= , TRATYP=CPTDN;
CRCPT: CODE= , DEST =<exchange in same local area>; digit translator is entered with a CdPA
not starting with a CAC
CRCPT: CODE=112, DEST = <emergency number>;

Code Points with CODE including a CAC


These CPT can only be accessed if the digit translator is entered
with a CdPA starting with a CAC:
the subscriber has dialed a CAC (call by call, CAC evaluation
in local exchange)
the ISUP-IAM includes a CAC in the TNSC or CdPA parameter
(CAC evaluation in higher ranking exchange)
the originator of the call (subscriber or inc. TGRP) a
preselected CAC is assigned to

CRCPT:
CODE= <CAC +....>,
DEST = <dest. with carrier
specific routing table>;

Fig. 112

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

SN2073EU01SN_0002
2002 Siemens AG

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

193

Siemens

8.6

Administration of the Inter-Exchange Circuit Network

Example

Database in the subscriber exchange Augsburg for calls to Munich and Stuttgart via the own network
and the transit network of carrier CARB
l

ENTR DNATT: PFXCAC=010;

CR CAC: CARRIER=CARA, CAC=01022, EXCCAC=NO, OWNCAC=YES, ROWNCAC=YES;


CR CAC: CARRIER=CARB, CAC=01033, EXCCAC=NO, OWNCAC=NO;

CR DEST: DEST=MNCH;
CR DEST: DEST=STUTT;
CR DEST: DEST=CARB;

CR CPT: DEST=MUNCH, CODE=089;

ROUTE1: TGNO=BWM
ROUTE1: TGNO=BWS
ROUTE1: TGNO=BWCARB

(CR CPT: DEST=MUNCH, CODE=01022089;


not necessary because own CAC 01022 is not used for digit translation)
l

CRCPT: DEST=STUTT, CODE=0711;


(CRCPT: DEST=STUTT, CODE=010220711;
not necessary because own CAC 01022 is not used for digit translation)

CRCPT: DEST=CARB, CODE=01033;

(CRCACCPT: CODE=0, CACGHUC=ROUTE;


not necessary because ROUTE is the default value)

Fig. 113

TIP
If a subscriber should be able to dial the OWNCAC (e.g. in order to overwrite his
preselected CAC), one CPT including the OWNCAC has to be created in the
exchange.
Reason: The LTG digit pre-translation accepts only dialing information, for which at
least one CPT is created.

194

SN2073EU01SN_0002
2002 Siemens AG

Siemens

Administration of the Inter-Exchange Circuit Network

Long distance network

TGNO=
BWM

Local network, Augsburg


CAR A

CAR A

CAR A

TGNO=
BWS

Local network, Munich 089

CAR B

CAR A

A-side
CAR B

CAR B

CAR A

TGNO=
BWCARB

Local network, Stutgart 0711


CAR x

CAR A

Exchange of
operator CAR x

CAR B

Fig. 114

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

SN2073EU01SN_0002
2002 Siemens AG

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

195

Siemens

Administration of the Inter-Exchange Circuit Network

TIP
Effects on various functions
l

individual subscriber screening (connection specific blockage of up to 50 directory


numbers) is possible regardless of the carrier, i.e. disabled subscriber directory
numbers can be entered with and without CAC .
Input without CAC: directory numbers disabled for all carriers in general
Input with CAC: directory numbers disabled only for the specified carrier

the CAC is not taken into account when determining the traffic type (TRAT) of a
connection

digit conversion of the routing paths does not affect the carrier codes

the originally selected CAC of new code destinations is replaced if the first
numbers of the new code correspond to an established CAC, otherwise the
original CAC remains valid and the new code replaces the B-directory number only

start sending digits (SSDI) affects only the destination directory number, the CAC
remains unaffected (not relevant for ISUP)

the handling of emergency calls or special services (information) for dialing with
and without carrier codes can be determined in the data base (CR CACCPT)

CR TGRP: ..., OPMODE=BW, GCOS=CACTNSC


GCOS=CACTNSC defines that the CAC is carried in the TNSC field (transit
network selection code) of the ISUP. If this GCOS value is missing, then the CAC
is transported as part of the CdPA.
CACTNSC can only be entered for ISUP trunk groups with OPMODE=BW.

CR TGRP: ..., GCOS=RCACINC or RCACOUT


The two identifiers suppress the further internal processing of a received own CAC
or the further signaling of the evaluated own CAC (entered with CR CAC: CAC=...,
OWNCAC=YES).
The type of signaling does not matter.
The following is valid:
GCOS=RCACINC (only for incoming and bothway TGRPs) suppresses the
incoming own network CAC
GCOS=RCACOUT (for outgoing and bothway TGRPs) suppresses the sending of
the own network carrier access code
This same trunk group data can be administered via ENTR TGDAT.

196

SN2073EU01SN_0002
2002 Siemens AG

Siemens

Administration of the Inter-Exchange Circuit Network

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

SN2073EU01SN_0002
2002 Siemens AG

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

197

Siemens

198

Administration of the Inter-Exchange Circuit Network

SN2073EU01SN_0002
2002 Siemens AG

Administration of the Inter-Exchange Circuit Network

Siemens

Flexible Routing via PA

SN2073EU01SN_0002
2002 Siemens AG

199

Siemens

Administration of the Inter-Exchange Circuit Network

It is possible to use a PA as a route to a destination at any position of the assigned


routing list. I.e. all above that
l

a routing list of a destination can contain different PA-routes (addressed by their


PDN)

PA-routes and trunk group-routes can be mixed inside one routing list

With this solution almost all existing routing features are available for calls to private
networks. Of course this is only useful if a private network is connected to the public
network via different PA interfaces (and additionally by trunk interfaces).
The figure shows an interconnection between the public network and a private PBX
network utilizing the concept of flexible routing. Here a call of the A - subscriber can
be routed in the public node A via different routes to the terminating private node
PBX B. The routes can be PA or TGNO routes.

200

SN2073EU01SN_0002
2002 Siemens AG

Siemens

Administration of the Inter-Exchange Circuit Network

Sub A

public
network

private
network

Trem.
PBX
Route: PA

node A
(EWSD)

Route:TGNO

Route: PA

transitnode C:
(EWSD)

Transit
PBX E

Trem.
PBX B

Transit
PBX D

Trem.
PBX

Routing list in node A for calls to PBX B:


1. Use the PA between the node A and the PBX B as the first choice route

(PA-route)
2. Use the PA between the node A and transit-PBX E as first overflow

route (PA-route). The transit-PBX E then routes the call inside the
private network to the terminating PBX B.
3. Use the trunk group TGNO between node A and node C as second

overflow route (TGNO-route). Node C routes the call to the transit-PBX


D which then routes the call inside the private network to the terminating
PBX B.

Fig. 115

TIP
The flexible routing, i.e., the utilization of routing lists which contain PAs and trunk
groups, is especially important for the interconnection of new network operators to
the incumbent telecom operators.

SN2073EU01SN_0002
2002 Siemens AG

201

Siemens

Administration of the Inter-Exchange Circuit Network

The Parameter CODE in the CR ROUTE Command


The new parameter CODE is added to the CR ROUTE command:
l

The syntax of the new parameter CODE is the same like the syntax of the already
existing parameters DICON or CONVCODE

The function of the new parameter CODE is similar to the function of the
destination parameter CONVCODE, i.e., both initiate a digit conversion and lead to
renewed digit translation.
But in opposite to CONVCODE the new CODE parameter is route and not
destination specific. Additionally also the LAC part of a received CdPA can be
changed with CODE (what is not possible with CONVCODE or DICON.

The code conversion because of the new parameter CODE may put digits before the
dialed number and/or replace digits of the translated part of the dialed number. The
user has to take care that not translated B-digits will not be changed. These new Bdigits will be translated at the Digit Translation Database (DITDA) once more into an
index, that should point at the PBX-Database.
After the second Digit Translation the Call Processing checks, if the result really
refers to a PBX-PDN (such a check is not performed when a ROUTE with CODE is
created). If the CODE doesnt belong to a PBX or if the PBX has no idle PBXLN, an
overflow to the next route is performed.
Charging is only possible for the dialed (original) number.
Seizing of a PBXLN via a CPT linked with a DEST (PA Route)
Each kind of Routing (classic for TGNOs or the new flexible one for PBXs too) starts
at the Digit Translation Table (DITDA), where the dialed or received number is
related to a destination of the destination database (DEADA) to classify the outgoing
traffic.
Besides the typical distribution to different trunk groups by the maximum of 16 routes,
the classic Routing already offered the possibility of a Final Overflow Code
(FOVCODE), which directs the call via a Codeprocessing Database (COPDA) and a
second digit translation at this same switch to another destination for outgoing traffic,
to an intercept handling or to all kinds of terminating traffic.
Now the flexible routing will offer approximately the same functionality like FOVCODE
to each route, i.e., a CODE can be assigned in the Route Database (ROSDA) to any
Route as an alternative to a TGNO. But in opposite to FOVCODE the result of the
second digit translation because of a CODE assigned to a Route must not be another
destination.

202

SN2073EU01SN_0002
2002 Siemens AG

Siemens

Administration of the Inter-Exchange Circuit Network

CR ROUTE : DEST= ,ROUTE= ,CODE= [,DINO=] [,LNDES=]


[,DICON=] [,NEWCAC=] [,STAT=] [,SSDI=] [,EOS=];
CODE FOR PBX
This parameter specifies a conversion mask to change the dialed digits into a code, which
addresses a PBX (CR PBX) for a more flexible routing.
Attention:
This parameter might also result in other objects than a PBX. In this case an overflow to the next
existing route is done.
Valid input characteres: 0-9, A-F, #, *, +, ., X
The modifications are specified in the form of a mask consisting of control characters and digits.
The control characters have the following significance:
X : The digit of the old code is left as it is.
. : The digit of the old code is deleted.
+ : The digits following this character, up to the next control character, are inserted.
0-9: Digits without a preceeding "+" replace the old code.
Example:
CODE = 123xx. specifies that the first 3 digits of the existing dial information are replaced by 1 2
3, the next 2 digits remain and the 6th digit is omitted.
The existing dial information 7944583 is changed to 123453.

Fig. 116

DITDA
CPT-1
Dest-Idx

outgoing
traffic

DEADA

ROSDA

ROJDA

StdDest-1

Route
Tgrp-Idx

Route
switch job

Route1
Route2
:
Route16

Route
Code-Idx

DBTGR
Trunk
group

Fovcode
COPDA

CPT-2
(CPTDN)

Code
processing

StdDest-2

second digit translation

continue with next route if no PBX line is idle


or if CODE does not result in a PDN
treminating
traffic

DBDNB/T
PBX

PBXLN

only possible with FOVCODE parameter


utilization of new route specific CODE parameter

Fig. 117

SN2073EU01SN_0002
2002 Siemens AG

203

Siemens

Administration of the Inter-Exchange Circuit Network

Example: Routing Database for Flexible Routing to a Private Network


In this example flexible routing to the private network XYZ is shown.
Database in EWSD (node A):
l

PBX E with PDN= 089 999 accessed via CPTDN with CODE=999 and LAC=089

DEST=XYZ (destination for the private network XYZ) accessed via CPT with
CODE=990 and LAC=089

Database in EWSD (node C):


l

PBX with PDN=089 998 accessed via CPTDN with CODE=998 and LAC=089

Routing to private network XYZ in EWSD (node A)


l

ROUTE 1: PA of PBX with PDN 089 999


The first ROUTE of DEST=XYZ is created in the following way:
CR ROUTE: DEST=XYZ, ROUTE=1, CODE=xxxxx9;
In case of a dialed CdPA 089 990 41429 the Digit Translation in node A results in
the DEST=XYZ.
When the routing process selects the first route, the original CdPA 089 990 41429
is converted into 089 999 41429 and the digit translation is started again.
The second digit translation results in the PDN 089 999. Now the call is forwarded
to the PBX E.
If no PBX line is idle, the CP continues with the routing (looking for next alternative
route (ROUTE=2).

ROUTE 2: Trunk group TGNO to node C


The second ROUTE of DEST=XYZ is created in the following way:
CR ROUTE: DEST=XYZ, ROUTE=2, TGNO=<trunk group to node C>;
When the routing process selects the second route, the original CdPA 089 990
41429 is forwarded unchanged to the public node C. It is than the task of the node
C to convert the received CdPA into the PDN of the PBX D (PDN= 089 998). I.e.,
in node C has to be created a CPT= 089 998 with a DEST containing a ROUTE
with CODE=xxxxx8 .

204

SN2073EU01SN_0002
2002 Siemens AG

Siemens

Administration of the Inter-Exchange Circuit Network

Sub A

089 990 41429

public
network
node A
(EWSD)

Route:TGNO

private
network
XYZ

Trem.
PBX

Route:
PAof PBX with
PDN= 089 999

transitnode C:
(EWSD)

Transit
PBX E

Transit
PBX D

Trem.
PBX B

41429

Trem.
PBX

PBX with
PDN=089 998

Public subscribers access the private network XYZ by access code 089 990
Routes to the private network XYZ created in node A:
- ROUTE1 with CODE=xxxxx9
- ROUTE2 with TGNO (trunk group to node C)
Fig. 118

TIP
l It is possible to enter route switches ROUTESW also for PA routes. Here PA
routes to be activated are identified by the new parameter CTACT, PA routes to be
blocked are identified by the new parameter CTBAR.
Example:
CR ROUTESW:DEST=XYZ,CTACT=xxxxx9,RTBAR=<tgno to node C>,TIME=0600;
CR ROUTESW:DEST=XYZ,CTBAR=xxxxx9,RTACT=<tgno to node C>,TIME=2200;
l

The parameter CODE is also available in following further routing commands:


CR/INS ROUTE, CAN/TAKO ROUTE, MOD ROUTE, ACT/BAR ROUTE,
DISP ROUTE

With DISP ROUTE an output mask appears which contains all routes with
parameter CODE.

SN2073EU01SN_0002
2002 Siemens AG

205

Siemens

Administration of the Inter-Exchange Circuit Network

Interworking of the new CODE Parameter with other Routing Features


For all functions that deal with trunk groups at routes and especially for all route
parameters it has to be made clear, if the routing to PA would mean identical,
comparable, different or wrong functionality. Some of the necessary rejections will be
made patchable to be able to meet updates in the future.
ROUTEPARAMETERS (in alphabetic order):

206

DEST
Different to trunk groups it is not checked, if a certain CODE exists only once
within a destination, because this is quite an old strategy, which could cause not
wanted limitations to the user. (The limitation for trunk groups can be avoided by
using different trunk group clusters, which are allowed to contain the same trunk
group.)

DICON
still needed for code processing at further nodes.

DINO, EOS
These parameters, which describe the number of needed digits and how the end
of the dialed digits has to be recognized, are still necessary. The CODE to a PA is
always totally existing, but the extension number might be received afterwards.
The according DINO parameter of the PBX is overruled.

LNDES
This parameter consists of a set of line descriptions, which are already restricted
for the different routing objects.
For PA routes following set values are rejected by an incompatibility mask
because all these are B-side orientated on trunk groups:
CLEARBA, METOTR, SUPMET, TRMET, TRMETSUB, CUS1DIG, CUS2DIG,
CUS3DIG, CUS4DIG, CREACUS, REACUS, OECNEXTE, SYNC1, SYNC2,
DIRECT

MINMAX
This destination parameter is evaluated for PA routes too and overrules the
according parameters of the PBX.

NEWCAC
eventually still needed at further nodes.

ODR
Not implemented at least in this version and explicitly rejected.

SSDI
This parameter of the route, which defines how many leading digits are not to be
sent, is to be used and overrules the one of the PBX.

SN2073EU01SN_0002
2002 Siemens AG

Administration of the Inter-Exchange Circuit Network

Siemens

TGNO
This parameter is not to be used together with the new parameter CODE (the
combination is explicitly rejected).

TLIM
This destination parameter activates or deactivates different timers and is
evaluated for PA routes too and overrules the time limits of the PBX.

TRACA
This parameter consists of a set of traffic categories and is explicitly rejected for
PA routes, because all of them are only relevant for outgoing traffic by trunk
groups.

ZDIG
not needed and explicitly rejected for PA routes, because this language
identification belongs to a trunk group, which should lead to an operator.

ROUTING FUNCTIONS (in alphabetic order) :


l

Carrier quotation
supported for PA routes within Carrier destinations. All three quotation procedures
are possible without additional adaptations.

Route threshold
This function is reserved for trunk groups. No rejection is necessary since the
Route threshold counter is only usable for TGNOs.

TMR IPI
According to the required transmission medium and the call history the TMR-IPI
destination (without any routes) leads to intercepts or the so called TIRDestination, which might consist of PA routes too; no additional adaptations
necessary.

Trunk group cluster


PA routes within a cluster to achieve e.g. proportional bidding are not to be
implemented at least in this version. No rejection necessary, because the cluster
already has only allowed trunk groups as elements so far.

Trunk reservation
only relevant for trunk groups.

SN2073EU01SN_0002
2002 Siemens AG

207

Siemens

208

Administration of the Inter-Exchange Circuit Network

SN2073EU01SN_0002
2002 Siemens AG

Administration of the Inter-Exchange Circuit Network

Siemens

10 Administration of Announcement Groups


and Lines

SN2073EU01SN_0002
2002 Siemens AG

209

Siemens

10.1

Administration of the Inter-Exchange Circuit Network

Function

Like for the standard routing, announcements are reached via the digit translator,
destination and route. The announcement is reached via an announcement group
instead of via a trunk group and via an announcement line instead of a trunk.
I.e. the announcement line represents the time slot on a PCM carrier to the DAS or
on a LTG internal highway to the OCANEQ. The announcement group is an administrative collection of the announcement lines.

210

SN2073EU01SN_0002
2002 Siemens AG

Administration of the Inter-Exchange Circuit Network

Siemens

Route
Route

Announcement
Announcement group
group

Announcement
Announcement line
line
Announcement
Announcement line
line
Announcement
Announcement line
line

Fig. 119 Announcement structure

SN2073EU01SN_0002
2002 Siemens AG

211

Siemens

10.2

Administration of the Inter-Exchange Circuit Network

Access to an Announcement Unit

Announcements can be accessed via integrated devices such as the OCANEQ


(operationally controlled announcement equipment) or via external equipment such
as the DAS ATIS.
Standard and individual announcements can be accessed via the OCANEQ, the DAS
can only be accessed for standard announcements. Standard announcements are
announcements with a fixed text. Individual announcements are announcements with
fixed and individual text. Individual text can for instance contain subscriber-specific
text such as account statements, telephone numbers, feature information etc.
Accessing the DAS and the OCANEQ differs for standard announcements and
individual announcement.

10.2.1

Accessing a DAS

The DAS is linked via a PCM link. Each time slot on the PCM represents a particular
text on the DAS. In other words, to obtain a certain text you need to select a certain
announcement line. As an announcement line cannot be accessed by several announcement groups the whole path through the routing database from the code point
to the time slot is individual for each text. In other words, a whole path through the
database needs to be set up for each text, i.e. announcement.

TIP
If a speech announcement is listened very frequently, you have to create several
announcement lines for one announcement group. All lines (PCM times slots) access
DAS modules where the same text is stored.

212

SN2073EU01SN_0002
2002 Siemens AG

Siemens

Administration of the Inter-Exchange Circuit Network

Codepoint
Codepoint
Destination
Destination
Route
Route

A001

A002

Codepoint
Codepoint
Destination
Destination
Route
Route

Announcement
Announcement
group
group

Announcement
Announcement
group
group

Announcement
Announcement
line
line

Announcement
Announcement
line
line

(announcement
(announcement
specific)
specific)

(announcement
(announcement
specific)
specific)

0 1 2 3

(announcement
(announcement
specific)
specific)

(announcement
(announcement
specific)
specific)

31

PCM

DAS

Fig. 120 Accessing a DAS

SN2073EU01SN_0002
2002 Siemens AG

213

Siemens

10.2.2

Administration of the Inter-Exchange Circuit Network

Accessing the OCANEQ for Standard Announcements

The OCANEQ is integrated in the LTG and is in the LTU position 1. Each time slot on
the LTG internal 2Mbit highway or LTU port can basically be used for any standard
announcement. Because the information on what announcement is played is
allocated to the announcement group and an announcement line cannot be accessed
by several announcement groups, in this case an LTU port is also allocated to one
standard announcement. Thus here the whole path through the routing database
from the code point to the LTU port is also individual for each text or standard
announcement. In other words a total path through the database needs to be set up
for each announcement.

214

SN2073EU01SN_0002
2002 Siemens AG

Siemens

Administration of the Inter-Exchange Circuit Network

Codepoint
Codepoint
Destination
Destination
Route
Route

A001

A002

Codepoint
Codepoint
Destination
Destination
Route
Route

Announcement
Announcement
group
group

Announcement
Announcement
group
group

Announcement
Announcement
line
line

Announcement
Announcement
line
line

STANNO=n
STANNO=n

(announcement
(announcement
specific)
specific)

0 1 2 3

STANNO=m
STANNO=m

(announcement
(announcement
specific)
specific)

31

LTG internal
highway

OCANEQ

Fig. 121 Accessing OCANEQ for standard announcements

SN2073EU01SN_0002
2002 Siemens AG

215

Siemens

10.2.3

Administration of the Inter-Exchange Circuit Network

Accessing the OCANEQ for Individual Announcements

The OCANEQ is integrated in the LTG and is in the LTU position 1. Each time slot on
the LTG internal 2 Mbit highway or LTU port can be used for any individual
announcement (so-called phrase). The information concerning which announcement
is played with which variable parts is controlled via the INDAS software (individual
announcement system) and passed on to the OCANEQ. Therefore the total path
through the routing database from the code point to the LTU port is not announcement-specific but can be used for all individual announcements equally.

216

SN2073EU01SN_0002
2002 Siemens AG

Siemens

Administration of the Inter-Exchange Circuit Network

DEF0

Codepoint
Codepoint
Destination
Destination
Route
Route

Announcement
Announcementgroup
group

(for
(forall
allindividual
individualannouncements)
announcements)

Announcement
Announcement
line
line

Announcement
Announcement
line
line

controlled by
INDAS SW
0 1 2 3

31

LTG internal
highway

OCANEQ

Fig. 122 Accessing OCANEQ for individual announcements

SN2073EU01SN_0002
2002 Siemens AG

217

Siemens

10.3
10.3.1

Administration of the Inter-Exchange Circuit Network

MML Commands
Announcement Group

An announcement group is administered via the command CR ANGRP. An announcement group is addressed via a trunk group number and can also be allocated to a destination area via CR ROUTE.
l

The parameter GCOS specifies general properties of the announcement group:


Enter OCANEQ if the announcement group leads to an OCANEQ.
Enter CHARGABL if the call to an announcement is zoned. In other words, if an
announcement is accessed directly billing is carried out in the zoning according to
the translated CODE and if it is accessed via INCEPT it is billed according to the
original dialed CODE.
For DAS call connections in which several subscribers can listen to an
announcement (broadcast) the values NONBARGE and STAGGER control the
beginning of the announcement for a second, third subscriber etc. NONBARGE
means that a further person hears the announcement from the beginning,
STAGGER means that the beginning of the announcements that come from several
announcement lines with the same text is evenly distributed over the entire
duration of the announcement. This reduces the waiting time when NONBARGE is
set.

218

The parameter STANNO specifies the number of the standard announcements that
is to be played from OCANEQ. Take the standard announcement number from the
respective project-specific INDAS catalogue.

The parameter NUMCYC specifies how often a subscriber may listen to the announcement. You cannot combine this specification with the broadcast mode.

The parameter SIT specifies that a project-specific information tone is to be


played before an OCANEQ announcement.

SN2073EU01SN_0002
2002 Siemens AG

Siemens

Administration of the Inter-Exchange Circuit Network

Announcement Group Administration


CR ANGRP:

TGNO= [,GCOS=] [,BLK=] [,STANNO=] [,NUMCYC=]


[,SIT=];

CAN ANGRP:

TGNO=;

DISP ANGRP:

TGNO=;

Fig. 123 Announcement group administration

1. line

announcement duration
10s

2. line

announcement duration
10s

3. line

announcement duration
10s

4. line

announcement
announcementduration
duration
10s
GCOS= NONBARGE

1. line
2. line

announcement duration
0s
2,5s
5,0s
7,5s

10s

announcement duration
0s
2,5s
5,0s
7,5s

3. line
4. line

10s

announcement duration
0s
2,5s
5,0s
7,5s

10s

announcement duration
0s
2,5s
5,0s
7,5s

10s

GCOS= NONBARGE&STAGGER
Fig. 124 GCOS = NONBARGE & STAGGER

SN2073EU01SN_0002
2002 Siemens AG

219

Siemens

10.3.2

Administration of the Inter-Exchange Circuit Network

Announcement Line

The announcement line assigns an LTU port to an announcement group, in order to


access a PCM time slot to a DAS or an OCANEQ port.

220

The parameter TGNO is used to perform the allocation to the ANGRP.

The optional parameter LNO (Line Number) specifies the position in the seizure
sequence. If this parameter is not set the number is issued by the system itself.

The EQN (Equipment Number) indicates the PCM port or OCANEQ port.

The optional parameter LCOS only needs to be set if a so-called user interaction
port (UI Port) is accessed or if neither the OCANEQ nor a DAS ATIS is accessed.
A UI port is needed for Intelligent Network for instance, when communicating with
the subscriber. In this case only as many OCANEQ ports can be seized as
pushbutton code receiver circuits (module CRP8) or voice recognition circuits
(module SCR) are available in the LTG.

The parameter SEIZMX (1...16) is only permitted for non-OCANEQ ports and
specifies how many subscribers may listen to an announcement simultaneously
(broadcast). The duplication takes place in the switching network. The limitation is
necessary to avoid a blocking of the time stage module.

SN2073EU01SN_0002
2002 Siemens AG

Siemens

Administration of the Inter-Exchange Circuit Network

Announcement Line Administration


CR ANLN:

TGNO= ,EQN= [,LNO=] [,LCOS=] [,BLK=]


[,SEIZMX=];

CAN ANLN:

TGNO= [,LNO=];

DISP ANLN:

TGNO= [,LNO=];

Fig. 125 MML commands for announcement lines

TSM

DAS
PDC

TSG

SN

SDC
LTG
LTG
LTG

TSM
Circuit 0

LTG
Circuit 1

30 Ports (TS) / PDC


SEIZMX = 16
16 X 30 = 480 TS
DANGER:
480 of the max. 512 timslots
throughconnected in a TSM
may be seized by the DAS

TSM

TSG

Fig. 126 SEIZMX parameter

SN2073EU01SN_0002
2002 Siemens AG

221

Siemens

222

Administration of the Inter-Exchange Circuit Network

SN2073EU01SN_0002
2002 Siemens AG

Administration of the Inter-Exchange Circuit Network

Siemens

11 Testing of the Basic Routing Function

SN2073EU01SN_0002
2002 Siemens AG

223

Siemens

Administration of the Inter-Exchange Circuit Network

It is difficult to localize database errors for routing administration. The database had
to be displayed separately with several commands. Operating personnel had to
establish the relation between the individual outputs on their own.
With the feature TEST ROUDB a much more comfortable method of database testing
is available. It is possible to specify via the command TEST ROUDB the call coming
into an exchange: the originator of the call (subscriber, trunk line or PABX) and the
called party number is entered together with additional call data such as language
digit, route type, TMR-IPI and catastrophe immunity.
The relevant zone number, destination, routes and trunk groups determined by the
exchange for this call set up are obtained as a result.
The database is tested mainly by means of those functions also employed by the
normal call processing programs. If the test is terminated (e.g. no CPT, ZOPT), then
the reason for the error is printed out.

TIP
l Incoming port blocking is not taken into consideration.

224

Traffic restrictions and toll catastrophe are incorporated in the routing test.

Time-dependent data such as route changeovers are not printed.

If a renewed call control (destination with NEWCODE / CONVCODE or intercept


with new code) takes place in the course of call processing, the new directory
number handling is also printed.

SN2073EU01SN_0002
2002 Siemens AG

Siemens

Administration of the Inter-Exchange Circuit Network

SIEMENS
NIXDORF

CODE
ZDIG
TMRIPI
........
SIEMENS

SIEMENS

subscriber
Trunk
group
SIEMENS

SIEMENS

Switching Center

PBX

Routing
Database
PBX
Other results
(e.g. CPTDN)
SIEMENS

SIEMENS

TGNO
ZONO
........

SIEMENS
NIXDORF

Switching Center

Fig. 127 Routing database functions test

SN2073EU01SN_0002
2002 Siemens AG

225

Siemens

Administration of the Inter-Exchange Circuit Network

MML Command
The TEST ROUDB command has 5 input variants, as well as the optional parameters
LACOR, CAT, ZDIG, ROUTYP, TMRIPI, CALLFEAT, ORIGCODE, TMQ, CAC,
CUSTID, FEATURE, CALLFEAT

Call coming in on TRGP with Called Party Number leading to a Subscriber of this Exchange
(Terminating Traffic)
9845
TESTROUDB:CODE=091800280,TGNO=I1INT;
X544/CTYCPZ1V1150/P50/110
9845 CA
EWSD0

99-05-18

2878/06891

11:21:48

TESTROUDB:CODE=091800280,TGNO=I1INT;
TEST ROUTING DB WITH ORIG1 :
CAC
TRANS RESULT
SDN
NEW CODE
RETRANS RESULT
OBJECT
-------CPT

:
: CPTDN
:
:
:

, ORIG2 :

, CAT : SUBORD

EVALDIGIT : 0918002
DESTDN
:
EVALDIGIT :

DEST
ROUTE TGNO
------------+-----+--------

STATUS
ZONO ZOCHA
---------+----+-------SIMEND

END JOB 9845

Call originated by a Subscriber a with Called Party Number leading to another Exchange
(Outgoing Traffic)
9851
TESTROUDB:CODE=089,DN=800240,LAC=091,SERV=CMSPEECH;
X544/CTYCPZ1V1150/P50/110
9851 CA
EWSD0

99-05-18

2878/06891

11:21:57

TESTROUDB:CODE=089,DN=800240,LAC=091,SERV=CMSPEECH;
TEST ROUTING DB WITH ORIG1 :
CAC
TRANS RESULT
SDN
NEW CODE
RETRANS RESULT
OBJECT
-------SDEST
ROUTE
TGRP

:
: OUTGTRAF
:
:
:

, ORIG2 :

, CAT : SUBORD

EVALDIGIT : 089
DESTDN
:
EVALDIGIT :

DEST
ROUTE TGNO
------------+-----+-------1INT
1INT
1
1INT
1 O1INT

STATUS
ZONO ZOCHA
---------+----+-------SUCCESS

127 ZONINHI

END JOB 9851

Fig. 128

226

SN2073EU01SN_0002
2002 Siemens AG

Siemens

Administration of the Inter-Exchange Circuit Network

Input possibilities for TEST ROUDB


Choice a A - side via
via TGNO
CODE =
, TGN0 =
[, LN0 =]
[, LACOR =]
...;

via LTG/LC
CODE =
, LTG=
, LC=
[, LACOR =]
...;

via EQN

via LSN

CODE =
, EQN =
[,SERV =]
[, LACOR =]
...;

via DN
CODE =
,DN =
[LAC =]
[,OPMODE =]
[,LN0 =]
[,SERV =]
...;

CODE =
, LSN =
[,LAC =]
[,SERV =]
...;

Fig. 129

. .
. .
. .
. .
. .
. .
. .
. .
. .
. .
. .
. .
. .
. .
. .
. .
. .
. .
. .
. .
. .
. .
. .
. .
. .
. .
. .
. .
. .
. .
. .

. . . . . .
. . . . . .
. . . . . .
. . . . . .
. . . . . .
. . . . . .
. . . . . .
. . . . . .
. . . . . .
. . . . . .
. . . . . .
. . . . . .
. . . . . .
. . . . . .
. . . . . .
. . . . . .
. . . . . .
. . . . . .
. . . . . .
. . . . . .
. . . . . .
. . . . . .
. . . . . .
. . . . . .
. . . . . .
. . . . . .
. . . . . .
. . . . . .
. . . . . .
. . . . . .
. . . . . .

SN2073EU01SN_0002
2002 Siemens AG

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

. . .
. . .
. . .
. . .
. . .
. . .
. . .
. . .
. . .
. . .
. . .
. . .
. . .
. . .
. . .
. . .
. . .
. . .
. . .
. . .
. . .
. . .
. . .
. . .
. . .
. . .
. . .
. . .
. . .
. . .
. . .

. . . . . . .
. . . . . . .
. . . . . . .
. . . . . . .
. . . . . . .
. . . . . . .
. . . . . . .
. . . . . . .
. . . . . . .
. . . . . . .
. . . . . . .
. . . . . . .
. . . . . . .
. . . . . . .
. . . . . . .
. . . . . . .
. . . . . . .
. . . . . . .
. . . . . . .
. . . . . . .
. . . . . . .
. . . . . . .
. . . . . . .
. . . . . . .
. . . . . . .
. . . . . . .
. . . . . . .
. . . . . . .
. . . . . . .
. . . . . . .
. . . . . . .

. . . .
. . . .
. . . .
. . . .
. . . .
. . . .
. . . .
. . . .
. . . .
. . . .
. . . .
. . . .
. . . .
. . . .
. . . .
. . . .
. . . .
. . . .
. . . .
. . . .
. . . .
. . . .
. . . .
. . . .
. . . .
. . . .
. . . .
. . . .
. . . .
. . . .
. . . .

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.

. . . . .
. . . . .
. . . . .
. . . . .
. . . . .
. . . . .
. . . . .
. . . . .
. . . . .
. . . . .
. . . . .
. . . . .
. . . . .
. . . . .
. . . . .
. . . . .
. . . . .
. . . . .
. . . . .
. . . . .
. . . . .
. . . . .
. . . . .
. . . . .
. . . . .
. . . . .
. . . . .
. . . . .
. . . . .
. . . . .
. . . . .

227

Siemens

228

Administration of the Inter-Exchange Circuit Network

SN2073EU01SN_0002
2002 Siemens AG

Administration of the Inter-Exchange Circuit Network

Siemens

12 Exercise

SN2073EU01SN_0002
2002 Siemens AG

229

Siemens

230

Administration of the Inter-Exchange Circuit Network

SN2073EU01SN_0002
2002 Siemens AG

Administration of the Inter-Exchange Circuit Network

Siemens

Exercise 1
Title:
Objectives:
Prerequisite:

Destination areas
The participant will be able to perform administration of
destination areas.
The destination area DEST has to be set up before

Task
Display the data for the destination area:...................................

Test
What is the ring time limit (in
seconds) of this destination
area?

SN2073EU01SN_0002
2002 Siemens AG

.........................................................................

231

Siemens

232

Administration of the Inter-Exchange Circuit Network

SN2073EU01SN_0002
2002 Siemens AG

Administration of the Inter-Exchange Circuit Network

Siemens

Exercise 2
Title:
Objectives:
Prerequisite:

Destination area with optimized dynamic routing


The participant will be able to perform administration for
destination areas with optimized dynamic routing.
n

ODR is generally active.

The TGRP were set up in the following way.


CRTGRP:TGNO=U019F,OPMODE=BW,GCOS=ZON
&CCS7IUP&PRIOPRE,ORIG1= 140,BLK=ADMIN;
CRTGRP:TGNO=U029F,OPMODE=BW,GCOS=ZON
&CCS7IUP&PRIOPRE,ORIG1= 140,BLK=ADMIN;
CRTGRP:TGNO=U039F,OPMODE=BW,GCOS=ZON
&CCS7IUP&PRIOPRE,ORIG1= 140,BLK=ADMIN;

Task
Set up the optimized dynamic routing as follows:
l

ODR list with the name ODR <ODR9> and max. 4 routing attempts per list access
(MAXATT).

ODR routes with the trunk groups U019F and U029F in the ODR list

Destination area with the name FKFT and ODR after 1. FAR route (trunk group
U039F)

Activate the ODR list ODR9


(The required trunk groups already exist )

Test
What MML
commands do you
need?

.........................................................................
.........................................................................
.........................................................................
.........................................................................
.........................................................................
.........................................................................

SN2073EU01SN_0002
2002 Siemens AG

233

Siemens

234

Administration of the Inter-Exchange Circuit Network

SN2073EU01SN_0002
2002 Siemens AG

Administration of the Inter-Exchange Circuit Network

Siemens

Exercise 3
Title:
Objectives:
Prerequisite:

Announcements and intercepts


The participant will be able to perform administration of
announcements and intercepts.
DAS with announcement on time slot 2 must be available

Task
n

The announcement of times slot 2 of the your DAS should be linked to the
intercept UNOBDE1:

The announcement listen in duration should be limited according to timer 27.

The information tone NUTONE should be inserted for 2 s after the listen in
duration to the announcement is exceeded.

The announcement can be listened simultaneously by two subscribers only, barge


in is not allowed.

Database parameter for the announcement connection:


n

The DAS is connected to the LTG...-.... LTU...

- Destination area for the announcement on time slot 2: A029

- Announcement group for the announcement on time slot 2: A029

- Code point for destination area A029: A029

Set up the corresponding intercept and the link to the DAS.

Test
What MML
commands do you
need?

.........................................................................
.........................................................................
.........................................................................
.........................................................................
.........................................................................
.........................................................................
.........................................................................

SN2073EU01SN_0002
2002 Siemens AG

235

Siemens

236

Administration of the Inter-Exchange Circuit Network

SN2073EU01SN_0002
2002 Siemens AG

Siemens

Administration of the Inter-Exchange Circuit Network

Exercise 4
Title:

Administration of a Speech Network with ISUP

Objectives:

The participant is able to create the database for a speech


network with ISUP

Pre-requisite:

The CCS7 signaling network is already created

Task
Create the shown speech network.
TAC4
TAC4

SPC=0-5-2
SPC=0-5-2
NETIND=INAT0
NETIND=INAT0

LX622
LX622

SPC=0-5-0
SPC=0-5-0
NETIND=INAT0
NETIND=INAT0

LX566
LX566

SPC=0-5-1
SPC=0-5-1
NETIND=INAT0
NETIND=INAT0

Fig. 130

Data of LX622

Data of LX566

Data of TAC4

Connection to LX566

Connection to LX622

Connection to LX622

CPT: Code=566

CPT: Code=622

CPT: Code=622

Dest=x566

Dest=x622

Dest=x622

TGNO=x566s

TGNO=x622s

TGNO=x622s

TRRANGE=3

TRRANGE=3

TRRANGE=3

LTG=0-3, LC=2-17

LTG=0-3, LC=2-17

LTG=0-4, LC=2-17

Connection to TAC4

Connection to TAC4

Connection to LX566

CPT: Code=444

CPT: Code=444

CPT: Code=566

Dest=TAC4

Dest=TAC4

Dest=x566

TGNO=TAC4s

TGNO=TAC4s

TGNO=x566s

TRRANGE=3

TRRANGE=3

TRRANGE=3

LTG=0-4, LC=2-17

LTG=0-4, LC=2-17

LTG=0-3, LC=2-17

SN2073EU01SN_0002
2002 Siemens AG

237

Siemens

238

Administration of the Inter-Exchange Circuit Network

SN2073EU01SN_0002
2002 Siemens AG

Administration of the Inter-Exchange Circuit Network

Siemens

13 Solutions

SN2073EU01SN_0002
2002 Siemens AG

239

Siemens

240

Administration of the Inter-Exchange Circuit Network

SN2073EU01SN_0002
2002 Siemens AG

Siemens

Administration of the Inter-Exchange Circuit Network

Solution 1
Title:
Objectives:
Prerequisite:

Destination areas
The participant will be able to perform administration of
destination areas.
The destination area DEST was set up before.

Task
Display the data for the destination area: KASSEL

Test
2036
<DISPDEST:DEST=KASSEL;
MSC5/D2MMPK1V16180025/213
2036
OMT-00/REMOTE#1

2882/06379

98-10-26

12:43:29

DISPDEST:DEST=KASSEL;
DESTINATION NAMES AND STANDARD ROUTING PARAMETERS
TYP
DEST
: MINMAX DEFEAT
TLIM
--------------+-+------+---------+-----------------------------KASSEL
1-20
DIALTM1& RINGTM1& CLEATM1&
OFFCALL& RELTM3
END TEXT JOB 2036 EXEC'D

MSC5/D2MMPK1V16180025/213
2036
OMT-00/REMOTE#1

2882/08886

98-10-26

12:43:30

DISPDEST:DEST=KASSEL;
DESTINATIONS WITH OPTIMIZED DYNAMIC ROUTING LINKAGE
DEST
ODR
LINK
--------------+--------------+---KASSEL
BERLIN1
2
END JOB 2036 EXEC'D

SN2073EU01SN_0002
2002 Siemens AG

241

Siemens

Administration of the Inter-Exchange Circuit Network

2062
<DISPTIOUT:TIMER=19;
MSC5/D2MMPK1V16180025/213
2062
OMT-00/REMOTE#1
DISPTIOUT:TIMER=19;

2882/04161

98-10-26

12:45:24
EXEC'D

LIST OF TIMEOUTS
TIMER

CURRENT VALUE
MINIMUM VALUE
MAXIMUM VALUE
STEP
HH:MM:SS,MSEC
HH:MM:SS,MSEC
HH:MM:SS,MSEC
HH:MM:SS,MSEC
------+---------------+---------------+---------------+---------------19
00:02:00,000
00:00:00,400
00:30:00,000
00:00:00,100
END JOB 206

What is the ring time limit (in


seconds) of this destination
area?

242

120 s

SN2073EU01SN_0002
2002 Siemens AG

Siemens

Administration of the Inter-Exchange Circuit Network

Solution 2
Title:
Objectives:
Prerequisite:

Destination area with optimized dynamic routing


The participant will be able to perform administration for
destination areas with optimized dynamic routing.
n

ODR is generally active.

The TGRP were set up in the following way.


CRTGRP:TGNO=U019F,OPMODE=BW,GCOS=ZON
&CCS7IUP&PRIOPRE,ORIG1= 140,BLK=ADMIN;
CRTGRP:TGNO=U029F,OPMODE=BW,GCOS=ZON
&CCS7IUP&PRIOPRE,ORIG1= 140,BLK=ADMIN;
CRTGRP:TGNO=U039F,OPMODE=BW,GCOS=ZON
&CCS7IUP&PRIOPRE,ORIG1= 140,BLK=ADMIN;

Task
Set up the optimized dynamic routing as follows:
l

ODR list with the name ODR <ODR9> and max. 4 routing attempts per list access
(MAXATT).

ODR routes with the trunk groups U019F and U029F in the ODR list

Destination area with the name FKFT and ODR after 1. FAR route (trunk group
U039F)

Activate the ODR list ODR9


(The required trunk groups already exist )

Test
1365
<CR ODR:ODR=ODR9;
MSC5/D2MMPK1V16180024/003
1365
OMT-00/SIEMENS0
CRODR:ODR=ODR9;

98-02-20

12:34:13

2878/00007
EXEC'D

END JOB 1365

SN2073EU01SN_0002
2002 Siemens AG

243

Siemens

Administration of the Inter-Exchange Circuit Network

1377
<DISP ODR:ODR=X;
MSC5/D2MMPK1V16180024/003
1377
OMT-00/SIEMENS0

98-02-20

12:34:21

98-02-20

12:36:11

2882/08885

DISPODR:ODR=X;
ODR GLOBAL : ACT

REROUTING : YES

ODR
MAXATT DACT
--------------+-------+---ODR9
4
*
END JOB 1377 EXEC'D
1411
<CR ROUTE:ODR=ODR9,TGNO=U019F,ROUTE=1;
MSC5/D2MMPK1V16180024/003
1411
OMT-00/SIEMENS0

2878/00007

CRROUTE:ODR=ODR9,TGNO=U019F,ROUTE=1;

EXEC'D

END JOB 1411


1415
<CR ROUTE:ODR=ODR9,TGNO=U029F,ROUTE=2;
MSC5/D2MMPK1V16180024/003
1415
OMT-00/SIEMENS0

98-02-20

12:38:11

2878/00007

CRROUTE:ODR=ODR9,TGNO=U029F,ROUTE=2;

EXEC'D

END JOB 1415


1611
<CR DEST:DEST=FKFT,ODR=ODR9,LINK=1;

MSC5/D2MMPK1V16180024/003
1611
OMT-00/SIEMENS0
CRDEST:DEST=FKFT,ODR=ODR9,LINK=1;

98-02-20

12:46:57

2878/00007
EXEC'D

END JOB 1611

244

SN2073EU01SN_0002
2002 Siemens AG

Siemens

Administration of the Inter-Exchange Circuit Network

1650
<CR ROUTE:DEST=FKFT,TGNO=U039F,ROUTE=1;
MSC5/D2MMPK1V16180024/003
1650
OMT-00/SIEMENS0

98-02-20

12:49:00

2878/00007

CRROUTE:DEST=FKFT,TGNO=U039F,ROUTE=1;

EXEC'D

END JOB 1650


1662
<DISP DEST:DEST=FKFT;

MSC5/D2MMPK1V16180024/003
1662
OMT-00/SIEMENS0

98-02-20

12:49:32

2882/06379

DISPDEST:DEST=FKFT;
DESTINATION NAMES AND STANDARD ROUTING PARAMETERS
TYP
DEST
: MINMAX DEFEAT
TLIM
--------------+-+------+---------+-----------------------------FKFT
1-20
DIALTM1& RINGTM1& CLEATM1&
OFFCALL& RELTM3
END TEXT JOB 1662 EXEC'D
MSC5/D2MMPK1V16180024/003
1662
OMT-00/SIEMENS0

98-02-20

12:49:33

2882/08886

DISPDEST:DEST=FKFT;
DESTINATIONS WITH OPTIMIZED DYNAMIC ROUTING LINKAGE
DEST
ODR
LINK
--------------+--------------+---FKFT
ODR9
1
END JOB 1662 EXEC'D
1663
<ACT ODR:ODR=ODR9;

SN2073EU01SN_0002
2002 Siemens AG

245

Siemens

246

Administration of the Inter-Exchange Circuit Network

SN2073EU01SN_0002
2002 Siemens AG

Administration of the Inter-Exchange Circuit Network

Siemens

Solution 3
Title:
Objectives:
Prerequisite:

Announcements and intercepts


The participant will be able to perform administration of
announcements and intercepts.
DAS with announcement on time slot 2 must be available

Task
n

The announcement of times slot 2 of the your DAS should be linked to the
intercept UNOBDE1:

The announcement listen in duration should be limited according to timer 27.

The information tone NUTONE should be inserted for 2 s after the listen in
duration to the announcement is exceeded.

The announcement can be listened simultaneously by two subscribers only, barge


in is not allowed.

Database parameter for the announcement connection:


n

The DAS is connected to the LTG 0- 2, LTU 3

- Destination area for the announcement on time slot 2: A029

- Announcement group for the announcement on time slot 2: A029

- Code point for destination area A029: A029

Set up the corresponding intercept and the link to the DAS.

SN2073EU01SN_0002
2002 Siemens AG

247

Siemens

Administration of the Inter-Exchange Circuit Network

2273
<CRINC:INCEPT=UNOBDE1,INRES=NEWCOD,CODE=A029,SEQ=1;
MSC5/D2MMPK1V16180025/213
2273
OMT-00/REMOTE#1

2878/00007

98-10-26

13:00:12

CRINC:INCEPT=UNOBDE1,INRES=NEWCOD,CODE=A029,SEQ=1;

EXEC'D

END JOB 2273


2274
<CRINC:INCEPT=UNOBDE1,TONE=NUTONE-2,SEQ=2;
MSC5/D2MMPK1V16180025/213
2274
OMT-00/REMOTE#1

2878/00007

98-10-26

CRINC:INCEPT=UNOBDE1,TONE=NUTONE-2,SEQ=2;

13:00:49
EXEC'D

END JOB 2274


2287
<DISPLTU:LTG=X-X;
MSC5/D2MMPK1V16180025/213
2287
OMT-00/REMOTE#1

3102/01017

98-10-26

13:01:09

DISPLTU:LTG=X-X;
LTG
LTU TYPE APPLIC MODVAR
-----+----+-----+-------+--------------------------------------0- 2
0
D30
CCSCCS 0-1 & 1-1 & 2-1 & 3-1 & 4-1 & 5-1 & 6-1
0- 2
2
D30
CCSCCS 0-1 & 1-1 & 2-1 & 3-1 & 4-1 & 5-1 & 6-1
0- 2
3
D30
CASRCA 0-1 & 1-1 & 2-1 & 3-1 & 4-1 & 5-1 & 6-1
0- 3
0
D30
CCSCCS 0-1 & 1-1 & 2-1 & 3-1 & 4-1 & 5-1 & 6-1
0- 3
1
D30
CCSCCS 0-1 & 1-1 & 2-1 & 3-1 & 4-1 & 5-1 & 6-1
........

2330
<CRANGRP:TGNO=A029,GCOS=NONBARGE;
MSC5/D2MMPK1V16180025/213
2330
OMT-00/REMOTE#1
CRANGRP:TGNO=A029,GCOS=NONBARGE;

2878/00007

98-10-26

13:02:52

EXEC'D

END JOB 2330

248

SN2073EU01SN_0002
2002 Siemens AG

Siemens

Administration of the Inter-Exchange Circuit Network

2388
<CRANLN:TGNO=A029,EQN=0-2-3-29,SEIZMX=2;
MSC5/D2MMPK1V16180025/213
2388
OMT-00/REMOTE#1

2878/00007

98-10-26

CRANLN:TGNO=A029,EQN=0-2-3-29,SEIZMX=2;

13:03:52
EXEC'D

END JOB 2388


2402
<DISPTIOUT:TIMER=27;
MSC5/D2MMPK1V16180025/213
2402
OMT-00/REMOTE#1

2882/04161

98-10-26

DISPTIOUT:TIMER=27;

13:04:24
EXEC'D

LIST OF TIMEOUTS
TIMER

CURRENT VALUE
MINIMUM VALUE
MAXIMUM VALUE
STEP
HH:MM:SS,MSEC
HH:MM:SS,MSEC
HH:MM:SS,MSEC
HH:MM:SS,MSEC
------+---------------+---------------+---------------+---------------27
00:00:10,000
00:00:00,400
00:30:00,000
00:00:00,100
END JOB 2402
2426
<CRDEST:DEST=A029,TLIM=CONVTM1;
MSC5/D2MMPK1V16180025/213
2426
OMT-00/REMOTE#1

2878/00007

98-10-26

CRDEST:DEST=A029,TLIM=CONVTM1;

13:06:07
EXEC'D

END JOB 2426


2433
<CRROUTE:DEST=A029,ROUTE=1,TGNO=A029;
MSC5/D2MMPK1V16180025/213
2433
OMT-00/REMOTE#1

2878/00007

CRROUTE:DEST=A029,TGNO=A029,ROUTE=1;

98-10-26

13:06:23
EXEC'D

END JOB 2433

SN2073EU01SN_0002
2002 Siemens AG

249

Siemens

Administration of the Inter-Exchange Circuit Network

2434
<CRCPT:CODE=A029,DEST=A029;
MSC5/D2MMPK1V16180025/213
2434
OMT-00/REMOTE#1
CRCPT:CODE=A029,DEST=A029;

2878/00007

98-10-26

13:06:56

EXEC'D

END JOB 2434

250

SN2073EU01SN_0002
2002 Siemens AG

Siemens

Administration of the Inter-Exchange Circuit Network

Solution 4
Title:

Administration of a Speech Network with ISUP

Objectives:

The participant is able to create the database for a speech


network with ISUP

Pre-requisite:

The CCS7 signaling network is already created

Task
Create the shown speech network.
TAC4
TAC4

SPC=0-5-2
SPC=0-5-2
NETIND=INAT0
NETIND=INAT0

LX622
LX622

SPC=0-5-0
SPC=0-5-0
NETIND=INAT0
NETIND=INAT0

LX566
LX566

SPC=0-5-1
SPC=0-5-1
NETIND=INAT0
NETIND=INAT0

Fig. 131

Data of LX622

Data of LX566

Data of TAC4

Connection to LX566

Connection to LX622

Connection to LX622

CPT: Code=566

CPT: Code=622

CPT: Code=622

Dest=x566

Dest=x622

Dest=x622

TGNO=x566s

TGNO=x622s

TGNO=x622s

TRRANGE=3

TRRANGE=3

TRRANGE=3

LTG=0-3, LC=2-17

LTG=0-3, LC=2-17

LTG=0-4, LC=2-17

Connection to TAC4

Connection to TAC4

Connection to LX566

CPT: Code=444

CPT: Code=444

CPT: Code=566

Dest=TAC4

Dest=TAC4

Dest=x566

TGNO=TAC4s

TGNO=TAC4s

TGNO=x566s

TRRANGE=3

TRRANGE=3

TRRANGE=3

LTG=0-4, LC=2-17

LTG=0-4, LC=2-17

LTG=0-3, LC=2-17

SN2073EU01SN_0002
2002 Siemens AG

251

Siemens

Administration of the Inter-Exchange Circuit Network

Data in LX622
<CMDFILE;
<SETCFOPT:ACKCFS=ALL,DANCMD=EXEC,ACKREQ=POS;
<CRDEST:DEST=x566,MINMAX=5-20;
<CRTGRP:TGNO=x566S,OPMODE=BW,GCOS=CCS7IUP&PRIOPRE,SIGVAR=VAR1;
<CRROUTE:DEST=x566,TGNO=x566S,ROUTE=1,DICON=...+091,DINO=D5;
<CRCPT:CODE=566,DEST=x566;
<CRZOPT:CODE=566,ZONO=1,BILLING=AMA&METERING,SUCHCNTR=CNTR1&CNTR2;
<ENTRC7TGREL:TGNO=x566S,DPC=0-5-1,NETIND=INAT0;
<CRTRUNK:TGNO=x566S,LTG=0-3 ,LC=2-17,LCOS=DIGSIG12,CIC=1-17,TRRANGE=3;
<CANTRDAT:TGNO=x566S,CIC=1-17,BLK=ADMIN,TRRANGE=3;
/
<CRDEST:DEST=TAC4,MINMAX=5-20;
<CRTGRP:TGNO=TAC4S,OPMODE=BW,GCOS=CCS7IUP&PRIOPRE,SIGVAR=VAR1;
<CRROUTE:DEST=TAC4,TGNO=TAC4S,ROUTE=1,DICON=...+091,DINO=D5;
<CRCPT:CODE=444,DEST=TAC4;
<CRZOPT:CODE=444,ZONO=1,BILLING=AMA&METERING,SUCHCNTR=CNTR1&CNTR2;
<ENTRC7TGREL:TGNO=TAC4S,DPC=0-5-2,NETIND=INAT0;
<CRTRUNK:TGNO=TAC4S,LTG=0-4,LC=2-17,LCOS=DIGSIG12,CIC=2-17,TRRANGE=3;
<CANTRDAT:TGNO=TAC4S,CIC=2-17,BLK=ADMIN,TRRANGE=3;
<RSETCFOPT;
<ENDFILE;

Data in LX566
<CMDFILE;
<SETCFOPT:ACKCFS=ALL,DANCMD=EXEC,ACKREQ=POS;
<CRDEST:DEST=x622,MINMAX=5-20;
<CRTGRP:TGNO=x622S,OPMODE=BW,GCOS=CCS7IUP&PRIOPRE,SIGVAR=VAR1;
<CRROUTE:DEST=x622,TGNO=x622S,ROUTE=1,DICON=...+091,DINO=D5;
<CRCPT:CODE=622,DEST=x622;
<CRZOPT:CODE=622,ZONO=1,BILLING=AMA&METERING,SUCHCNTR=CNTR1&CNTR2;
<ENTRC7TGREL:TGNO=x622S,DPC=0-5-0,NETIND=INAT0;
<CRTRUNK:TGNO=x566S,LTG=0-3,LC=2-17,LCOS=DIGSIG12,CIC=1-17,TRRANGE=3;
<CANTRDAT:TGNO=x566S,CIC=1-17,BLK=ADMIN,TRRANGE=3;
/
<CRDEST:DEST=TAC4,MINMAX=5-20;
<CRTGRP:TGNO=TAC4S,OPMODE=BW,GCOS=CCS7IUP&PRIOPRE,SIGVAR=VAR1;
<CRROUTE:DEST=TAC4,TGNO=TAC4S,ROUTE=1,DICON=...+091,DINO=D5;
<CRCPT:CODE=444,DEST=TAC4;
<CRZOPT:CODE=444,ZONO=1,BILLING=AMA&METERING,SUCHCNTR=CNTR1&CNTR2;
<ENTRC7TGREL:TGNO=TAC4S,DPC=0-5-2,NETIND=INAT0;
<CRTRUNK:TGNO=TAC4S,LTG=0-4,LC=2-17,LCOS=DIGSIG12,CIC=3-17,TRRANGE=3;
<CANTRDAT:TGNO=TAC4S,CIC=3-17,BLK=ADMIN,TRRANGE=3;
<RSETCFOPT;
<ENDFILE;

252

SN2073EU01SN_0002
2002 Siemens AG

Administration of the Inter-Exchange Circuit Network

Siemens

Data in TAC4
<CMDFILE;
<SETCFOPT:ACKCFS=ALL,DANCMD=EXEC,ACKREQ=POS;
<CRDEST:DEST=x622,MINMAX=5-20;
<CRTGRP:TGNO=x622S,OPMODE=BW,GCOS=CCS7IUP&PRIOPRE,SIGVAR=VAR1;
<CRROUTE:DEST=x622,TGNO=x622S,ROUTE=1,DICON=...+091,DINO=D5;
<CRCPT:CODE=622,DEST=x622;
<CRZOPT:CODE=622,ZONO=1,BILLING=AMA&METERING,SUCHCNTR=CNTR1&CNTR2;
<ENTRC7TGREL:TGNO=x622S,DPC=0-5-0,NETIND=INAT0;
<CRTRUNK:TGNO=x622S,LTG=0-4,LC=2-17,LCOS=DIGSIG12,CIC=1-17,TRRANGE=3;
<CANTRDAT:TGNO=x622S,CIC=1-17,BLK=ADMIN,TRRANGE=3;
/
<CRDEST:DEST=x566,MINMAX=5-20;
<CRTGRP:TGNO=x566S,OPMODE=BW,GCOS=CCS7IUP&PRIOPRE,SIGVAR=VAR1;
<CRROUTE:DEST=x566,TGNO=x566S,ROUTE=1,DICON=...+091,DINO=D5;
<CRCPT:CODE=566,DEST=x566;
<CRZOPT:CODE=566,ZONO=1,BILLING=AMA&METERING,SUCHCNTR=CNTR1&CNTR2;
<ENTRC7TGREL:TGNO=x566S,DPC=0-5-1,NETIND=INAT0;
<CRTRUNK:TGNO=TAC4S,LTG=0-3,LC=2-17,LCOS=DIGSIG12,CIC=3-17,TRRANGE=3;
<CANTRDAT:TGNO=TAC4S,CIC=3-17,BLK=ADMIN,TRRANGE=3;
<RSETCFOPT;
<ENDFILE;

SN2073EU01SN_0002
2002 Siemens AG

253

Siemens

254

Administration of the Inter-Exchange Circuit Network

SN2073EU01SN_0002
2002 Siemens AG

You might also like