Announcement handling

1 Routing definitions

1.1 Displaying routing information

Output the routes in the MSC.
Command(s): <RRI:GSW:;

Output one of the routes in the previous exercise.

Command(s): <RRI:GSW:ROU=A00;
What kind of information is found here?
ROU=400, TYPE=EXT, OUTR=OMCGD, STP=1, TON=UNK
NCCP=BSSAP, STATE=WO-EX, NCGR=BSC01

Output the Circuit Groups (CGRs) in the MSC.

Command(s): <RCI:;
Give two names of internal circuit groups and external circuit groups.

Internal circuit groups External circuit groups

AFS BSC01
OSIAS7 BSC02

Output the CGR towards the BSC(s).

Command(s): <RCI:SEA=3:NCGR=BSC02:;

Output the CGR towards the PSTN(s).

Command(s): <RCI:SEA=3:NCGR=BJ:;

Output the CGR towards the other MSC(s).

Command(s): <RCI:SEA=3:NCGR=MSC02;

Draw the Training Centre Network based on the information you have
discovered so far.
 D O C U M EN TTYPE
Announcement handling
T y p e U n it O r D e p a r tm e n t H e r e
T y p e Y o u rN a m e H e re T y p e D a te H e re

1.2 Creating routing definitions towards a new MSC

These exercises assume that you have already created the signalling network
definitions required to incorporate the new MSC into the existing network.
Use the signalling definitions for the new exchanges that you created from the
signalling chapter to continue these exercises.

O W N M SC
R O U T E :_ _ _ _ R O U T E :_ _ _ _
N C G R :_ _ _ _ _ S P C :_ _ _ N C G R :_ _ _ _ _
C R C T :_ _ _ _ _ C R C T :_ _ _ _ _
M SC 3 M SC 1
E T :_ _ E T :_ _
S P C :_ _ _ S P C :_ _ _

M SC 4 M SC 2
E T :_ _ E T :_ _
R O U T E :_ _ _ _ R O U T E :_ _ _ _
S P C :_ _ _ N C G R :_ _ _ _ _ N C G R :_ _ _ _ _ S P C :_ _ _
C R C T :_ _ _ _ _ C R C T :_ _ _ _ _
 Announcement handling

1.2.1 Creating circuits and circ uit groups

Create a circuit group towards the new MSC.

Command: <RCC:TYPE=CCS,NCGR= ,CGR= :DIR= BI,
NET=NA0, SPC= , LSI= : METHOD= , TREE= , INR= ,
NCCP= :;

<RCA: NCGR= : CRCT= ,: CCSPCM= :;

Note
While creating the circuit group, pay special attention to the following
items:

a) Circuits are not defined using the command RCC, add circuits, using
the command RCA.
b) Direction: This parameter defines the direction of the circuit group.
The direction is set as:
DIR=BI: bi-directional, if the circuit group is used for both incoming
and outgoing traffic.
DIR=OUT: outgoing, if the circuit group is used for outgoing traffic
only. No analysis tree (TREE) or register signalling (INR) needs to
be defined.
DIR=IN: incoming, if the circuit group is intended for incoming
traffic only.
c) The possible values for Line Signalling Indicator (LSI). Although this
is a network which uses common channel signalling, the use of a line
signalling indicator is necessary for control actions on the circuit,
such as, the use of the Service Information Octet while C7 messages
are being sent. This parameter has an operator/country specific value.
One of the possible values could be TUP01. Ask your instructor for
the correct value for the exercise.
d) The possible incoming register signalling (INR). This is a parameter
similar to the LSI, but this one is required for call processing. The
INR has an operator/country specific value. Check with the trainer
for possible values at the training centre. This parameter is needed
only if the circuit group is Incoming or Bi-directional.
e) CIC (CCSPCM number + TS number). This is a parameter that
uniquely identifies a PCM line between two adjacent elements. It is
required, because the actual PCM number for the same physical line
could be different at both ends. Thus, this parameter has to be defined
with the same number for the same PCM line at both ends.
 Announcement handling

What value did you give for the parameter TREE? What does it mean? Can you
give a value for it?
TREE=70
This tree is used for Digit Analysis for TOC (Trunk Originated Call).

What kind of circuit group definitions would be needed, if the NE were a BSC?
Command: <RCC: TYPE= CCS, NCGR= , CGR= : DIR=
OUT, NET=NA1, SPC= ,LSI= ,;
RCA: NCGR= : CRCT= ,: CCSPCM= :;

What kind of circuit group definitions would be needed, if the NE were a HLR?
No circuit group definitions are needed.

What kind of circuit group definitions would be needed, if the NE were a PSTN
node?
Same as if the NE were an MSC.

1.2.2 Creating routes

Create the route leading to the new MSC and use the circuit group that you have
already created.
Command: <RRC:EXT:ROU= , OUTR= , NCCP ,
STP= , TON= , NCGR= ;

Note
Check with the instructor the possible values of Outgoing Register
Signalling (OUTR) . Check also from the already created circuit groups,
which one you have to use. In practice this depends on the INR of the
other node (in this case the MSC).

What does the parameter STP mean? What kind of values can you give?
STP = Starting Transfer Point. This parameter is used to define which
digit will be sent first to the route.
 Announcement handling

1.2.3 Changing state of circuit, CGR and route

Output the state of new circuits in your circuit group.

Command: <CEL:NCGR= ;

Change the state of circuits to WO-EX.

Command: <CEC:CRCT=:;

Output the state of your circuits group.

Command: <CRI:NCGR=;

Change the states of the circuit groups to WO-EX.

Command: <CRM:NCGR=:;

5. Output the state of your route.

Command: <CRL:ROU=;

Change the state of your route to WO-EX.

Command: <CRC:ROU=:;
 Announcement handling

1.3 Creating digit analysis

1.3.1 Digit analysis definition exercises

At the moment, the new MSC is a part of the network. Assuming that the new
MSC is a GMSC through which all international calls are routed, and assuming
that the PSTN is accessible via this GMSC, which definitions are required for
the following situations?

MS to MS call
a. subscriber A in our MSC, subscriber B in new MSC
b. subscriber A in new MSC, subscriber B in our MSC
c. subscriber A and B are both under our MSC.

MS - PSTN call
a. subscriber A in our MSC, subscriber B in the PSTN
b. subscriber A in the PSTN, subscriber B in our MSC

International calls from a subscriber in our MSC

Call Forwarding Unconditional to a PSTN

Call Forwarding Unconditional to a mobile subscriber located in

a. our MSC
b. new MSC.
c.
Fill in the following tables for each of the above cases.
One entry in the table can be used for more than one case.
 Announcement handling

1.3.1.1 Subscriber A in our MSC calls subscriber B in the new MSC

Definition in our MSC Definition in the new MSC

TREE 2, DIG=B-number, TON=NAT TREE 70, DIC= MSRN, TON=NAT
 
DEST=HLRENQ DEST=GSMEND
 
SDEST=HLRENQ SDEST=GSMEND
 
SPR=2 SPR=1
TREE 50, DIG=MSRN of new MSC,
TON=INT

DEST=NEW MSC

SDEST=NEW MSC

ROU=1000
 Announcement handling

1.3.1.2 Subscriber A in new MSC calls subscriber B in our MSC

Definition in our MSC Definition in the new MSC

TREE=70, DIG=MSRN , TON=NAT TREE=2, DIG=B-number,
TON=NAT

DEST=GSMEND 
DEST=HLRENQ

SDEST=GSMEND 
SDEST=HLRENQ

SPR=1 
SPR=2
TREE=50, DIG=MSRN of MSC,
TON=INT

DEST= MSC

SDEST=MSC

ROU=2000
 Announcement handling

1.3.1.3 Subscriber A and B are both under our MSC

Definition in our MSC Definition in the new MSC

TREE=2, DIGIT=B-SUB, TON=NAT

DEST=HLRENQ

SDEST=HLRENQ

SPR=2

TREE=50, DIGIT=MSRN of MSC,

TON=NAT

DEST=GSMEND

SDEST=GSMEND

SPR=1
 Announcement handling

1.3.1.4 Subscriber A in our MSC calls subscriber B in the PSTN

Definition in our MSC Definition in the new MSC

TREE=2, DIGIT=B-NUMBER, TREE=70, DIGIT=B-NUMBER,
TON=NAT TON=NAT
 
DEST=PSTN DEST=PSTN
 
SDEST=NEW MSC SDEST=PSTN
 
ROU=1000 ROU=3000
 Announcement handling

1.3.1.5 Subscriber A in the PSTN calls subscriber B in our MSC

Definition in our MSC Definition in the new MSC

TREE=70, DIGIT=MSRN of MSC, TREE=70, DIGIT=B-NUMBER,
TON=NAT TON=NAT
 
DEST=GSMEND DEST=HLRENQ
 
SDEST=GSMEND SDEST=HLRENQ
 
SPR=1 SPR=2

TREE=50, DIGIT=MSRN of
MSC, TON=INT

DEST=MSC

SDEST=MSC

ROU=2000
 Announcement handling

1.3.1.6 Subscriber A in our MSC makes international calls to subscriber B in other country

Definition in our MSC Definition in new MSC

TREE=2, DIGIT=B-NUMBER, TREE=70, DIGIT=B-NUMBER,
TON=INT TON=INT
 
DEST=INTPSTN DEST=INTPSTN
 
SDEST=NEW MSC SDEST=INTPSTN
 
ROU=1000 ROU=3000

1.3.1.7 Subscriber A calls B who has Call Forwarding Unconditional to subscriber C in the
PSTN
 Announcement handling

Definition in our MSC Definition in new MSC

TREE=2, DIGIT=B-NUMBER, TREE=70, DIGIT=C-NUMBER,
TON=NAT TON=NAT
 
DEST=HLRENQ DEST=PSTN
 
SDEST=HLRENQ SDEST=PSTN
 
SPR=2 ROU=3000

TREE=20, DIGIT=C-NUMBER,
TON=INT

DEST=PSTN

SDEST=NEW MSC

ROU=1000

1.3.1.8 Subscriber A calls B who has Call Forwarding Unconditional to subscriber C in the
new MSC
 Announcement handling

Definition in our MSC Definition in new MSC

TREE=2, DIGIT=B-NUMBER, TREE=70, DIGIT=MSRN of new
TON=NAT MSC, TON=NAT
 
DEST=HLRENQ (for B-NUMBER) DEST=GSMEND
 
SDEST=HLRENQ SDEST=GSMEND
 
SPR=2 SPR=1

TREE=20, DIGIT=C-NUMBER,
TON=INT

DEST=HLRENQ (for C-NUMBER)

SDEST=HLRENQ

SPR=2
 Announcement handling

TREE=50, DIGIT=MSRN of NEW

MSC, TON=INT

DEST=NEW MSC

SDEST=NEW MSC

ROU=1000

1.3.1.9 Subscriber A calls B who has Call Forwarding Unconditional to subscriber C in our
MSC

Definition in our MSC Definition in new MSC

TREE=2. DIGIT=B-NUMBER,
TON=NAT

DEST=HLRENQ (for B-NUMBER)

SDEST=HLRENQ

SPR=2
 Announcement handling

TREE=20, DIGIT=C-NUMBER,
TON=INT

DEST=HLRENQ (for C-NUMBER)

SDEST=HLRENQ

SPR=2

TREE=50, DIGIT=MSRN (MSC),

TON=INT

DEST=GSMEND

SDEST=GSMEND

SPR=1

1.3.2 Creating digit analysis components and digit analysis

Summarise all definitions that you had to create in your MSC in your previous
cases.

Tree number: TON: Digits: Destination Subdestination Route number

or SPR number
 Announcement handling

How many charging cases do you have to define?

Depends on the operator.

Create the charging cases.

Command: <RDE:NCHA= :CP=OE;

Create the subdestination.

Command: <RDE:NSDEST= :ROU= , CT= , SP= ;

Define the destinations.

Commands: <RDE:NDEST= :NSDEST= :NCHA= ;

Create digit analysis according to your table for tree 2, tree 20, tree 50 and the
used tree for TOC.
Commands: <RDC:DIG= , TREE= , TON= :NDEST= ;
 Announcement handling

2 Local calls

What are the definitions needed in the preanalysis?

Type of preanalysis: Default preanalysis
Type of number: UNK
Numbering plan: ISDN / Telephony
Digits: -

What are the required outputs?

Digit TON NPI Result Call Service NBR CON Other

Identifiers characteristic Number necessary
parameter
- UNK EILA CONT Normal call - - Local -

Check the preanalysis and create the missing entry if necessary.

Commands: <RWR:MOC,2,:3,LOC,0,;

Which is the tree for local calls?

Tree number: 2

Create a number modification special route to modify the local number.

Command: <RNC:SPR= :SRD=1,SAD=1,NRD=0,DIG= ,
TON=NAT:TREE=2;

Create digit analysis for the respective tree (how many methods are there for
creating digit analysis for local calls?)
Create new charging case or use the existing one.
 Announcement handling

Commands: <RDE:NCHA= :CP=OE;

Create subdestination.
Commands: <RDE:NSDEST= :ROU= , CT= , CP= ;
Create destination.
Commands: <RDE:NDEST= :NSDEST=: NCHA= ;
Create digit analysis for a local number.
Commands: <RDC:DIG= , TREE= , TON= :NDEST= ;

Make a call with a local number.

 Announcement handling

3 Area service numbers

What are the definitions needed in preanalysis?

Type of preanalysis: Normal preanalysis
Type of number: UNK
Numbering Plan: E16A
Digits: service number

What are the required outputs?

Digit TON NPI Result Call Service NBR CON Other

Identifiers characteristic Number necessary
parameter
Service number UNK E16A Continue Service call Number - Local -
1-23

Check the preanalysis and create the missing entries if necessary.

Commands: <RWI:ORIG=MOC;

3. Output the area service numbers already defined in the system (if any).
Command: <RUI;

4. What are the definitions needed in the area service number handling for
your number?
E.g. Routing zone Service type Area Service Number
5 5 5643278
 Announcement handling

5. Create the area service numbers for your service.

Command: <RUA: SN= ,ST=1,RZ= ,TREE=30,TON=INT;

6. Create the digit analysis for your service in the respective tree.
Create new charging case or use the existing one.
Commands: <RDE:NCHA=:CP=OE;

Create subdestination.
Commands: <RDE:NSDEST= : ROU= , CT= , CP= ;

Create destination.
Commands: <RDE:NDEST= :NSDEST= ;

Create digit analysis for your service number.

Commands: <RDC:DIG= ,TON= , TREE=30 :NDEST= ;

7. Make a call with your service number.

 Announcement handling

4 Announcement handling

4.1 Direct call to announcement

Interrogate the current announcement parameters.

Command: RAL;
Are they suitable?

2. Create a special route for the announcement.

Command:
<RAC:SPR= ,DEV=INT::TXIND= ,ALLO=OND,A
NAM= ,
AFIL=7;

3. Change the state of the announcement special route to ‘ON’.

Command: <RAM:SPR= :STATE=ON;

Create digit analysis for your analysis in the tree for MOC to hear the
announcement.
Create a new charging case or use the existing one.
Commands: <RDE:NCHA= :CP=OE;

Create subdestination.
Commands: <RDE:NSDEST= :ANN= , CT= , CP= ;

Create destination.
 Announcement handling

Commands: <RDE:NDEST= :NSDEST= :NCHAR= ;

Create digit analysis for the direct number in order to hear the
announcement.
Commands: <RDC:TREE=2,DIG= ,TON= :NDEST= ;

Create digit analysis for your analysis in the announcement tree.

Create new charging case or use the existing one.
Commands: <RDE: NCHAR= :CP=OE;

Create subdestination.
Commands: <RDE:NSDEST= :SPR= ,CT= ,CP= ;

Create destination.
Commands: <RDE:NDEST= :NSDEST= ;
Create digit analysis for your announcement number.
Commands: <RDC:TREE=48, DIG= ,TON=UNK:NDEST= ;

Verify your definitions by dialling the related number.

4.2 Intermediate announcement

Set up the related digit analysis in the correct tree.

Create new charging case or use the existing one.
Commands: <RDE: NCHA= :CP=OE;
 Announcement handling

Create subdestination.
Commands: <RDE:NSDEST= :SPR= ,CT= ,CP= ;

Create destination.
Commands: <RDE:NDEST= :NSDEST= ;
Create digit analysis for your announcement number.
Commands: <RDC:TREE=48, DIG= ,TON=UNK:NDEST= ;

2. Modify the EOS-analysis for a specific clear code so that it points to the
created announcement.
Command: <RXM:1:0005:STOP,,,,,100,,,:;

Test your announcement. (You must think of a case where the modified clear
code will be generated.)