Routing To An Announcement

ROUTING TO AN ANNOUNCEMENT
INSTALLATION METHODS AND PROCEDURES
3BL 41392 AAAA MSAGA Ed. 04

Status RELEASED 2005/01/10
Short title
All rights reserved. Passing on and copying of this document, use

and communication of its contents not permitted without written
authorization from Alcatel.
3BL 41392 AAAA MSAGA Ed. 04 RELEASED

CONTENTS
1. PREFACE.................................................................................................................. 4
1.1. REFERENCED DOCUMENTS .............................................................................. 4
1.2. Applicability............................................................................................................ 4
1.3. General.................................................................................................................. 4
1.4. General problem .................................................................................................... 4
1.5. General operating requirements............................................................................. 5
1.6. Services to be performed by the customer ............................................................. 5
1.7. Services to be performed by the manufacturer....................................................... 5
1.8. GENERAL INTERVENTION CONSTRAINTS ........................................................ 5
1.9. TECHNICAL AND OPERATIONAL SEQUENCING CONSTRAINTS ..................... 6
1.9.1. PREREQUISITES .............................................................................................. 6
1.9.2. PROCEDURE .................................................................................................... 6
1.10. OPERATIONS TO BE CARRIED OUT BY THE CUSTOMER............................ 7
2. UNLOCKING AT SSP LEVEL.................................................................................... 8
2.1. GENERAL.............................................................................................................. 8
2.2. PRELIMINARY CHECKS....................................................................................... 8
2.3. OUTPUTTING THE ANNOUNCEMENT CHARACTERISTICS .............................. 8
2.4. CREATING DATA LINKS....................................................................................... 9
2.5. MODIFYING THE FIDIF FILE ("BROADCASTS FILE").......................................... 9
2.6. INCLUSION OF MODIFICATIONS .......................................................................10
2.7. FUNCTIONALITY TEST .......................................................................................10
2.8. RETURN TO OPERATION ...................................................................................10
3. UNLOCKING AT RCP LEVEL ..................................................................................11
3.1. RCP BACKUP ......................................................................................................11
3.2. SETTING THE RYR_MCCI RELATION ................................................................11
3.3. SETTING THE RYR_FILM RELATION .................................................................11
3.3.1. UPDATING THE RYR_FILM RELATION. .........................................................13
3.4. FOR "CALL HOLD" ANNOUNCEMENTS .............................................................15
3.5. SETTING THE RYR_OBFM RELATION...............................................................15
3.6. INCLUSION OF MODIFICATIONS .......................................................................16
3.7. RCP BACKUP ......................................................................................................16
3.8. RETURN TO OPERATION ...................................................................................16
3.9. TESTING THE FUNCTIONALITY. ........................................................................16
4. APPENDIX A = LIST OF ANNOUNCEMENTS .........................................................17
5. APPENDIX B = ERROR KEY AND TEXT .................................................................22
6. APPENDIX C = DIAGNOSTIC REPORTS (D_DIAGN) .............................................28
7. APPENDIX D = LINKS BETWEEN ANNOUNCEMENT NUMBERS, TIME SLOTS,
DATA LINKS AND ROUTING...............................................................................................29
8. APPENDIX E = RETRIEVING ROUTINGS AND DATA LINK NUMBERS.................30
8.1. REPLACING THE LD............................................................................................30
8.1.1. FOR A TYPE 3 LD ............................................................................................30
8.1.2. FOR A TYPE 1 LD ............................................................................................30
8.1.3. FOR A FSM WITH ONLY ONE SLC .................................................................31
8.2. REPLACING THE ROUTING................................................................................32

1. PREFACE
The service can be unlocked and locked only by the manufacturer or one of its
representatives.
1.1. REFERENCED DOCUMENTS
- RXTACH Routing to an announcement 3BL33336AAAAREAGA

- FEX: PCFS Save-Restore Function 3BL40611BAAXREAGA
1.2. Applicability
R6, R7, R8
1.3. General
This procedure describes how unlocked/locked the function:
This function is for broadcasting an announcement to a mobile or the fixed network

(depending on the case) when the type of call allows ("speech" call or "mixed
speech/data" call beginning with a "speech" phase).
There are three types of announcement:

- Call failure announcement telling the caller the reason for the call not being set up
- Greeting announcement
- Information announcement.
Call failure announcements must be defined in the SSP before the RCP is placed in
service. The greeting and information announcements can be entered at any time to suit
the operator.
The recorded announcements are handled by routings from the SSP and do not
require construction in the RCP.
NOTE (S):
For this function to operate correctly, the SSP MUST BE IN RELEASE R24
minimum.
1.4. General problem
The function is unlocked or locked using manufacturer or operator commands from a

customer terminal.
The operation takes a few minutes (excluding backups).
4

1.5. General operating requirements

The stations must be in perfect working order.
1.6. Services to be performed by the customer

The customer:
- Takes a backup of the station or stations before the operation.
- The customer must specify:

1) which announcement broadcasts are required
2) the associated system (SSP) numbers.
However, if the operator does not himself wish to supply the announcement
numbers, it is always possible to set the numbers arbitrarily for new
announcement, particularly from number 52 where the INAP and SSP system
numbers are the same (see table in section 3.3).
- Supplies and executes a test plan after the operation.
- Takes a backup of the station or stations after operation.
1.7. Services to be performed by the manufacturer

The manufacturer:
- Applies the procedure described in the following sections.
- Checks that the services to be performed by the customer are complete.
- In addition:
. Before modifying a station:
- Creates a conformity reference using the WINCONF tool.
. After modifying a station:
- On the first site (trial site), establishes a new conformity reference
and sends it to the Alcatel customer interface.
- On the other sites, checks data conformity using the first site as a
reference.
1.8. GENERAL INTERVENTION CONSTRAINTS
Implementation of the functionalities linked to recorded announcements carries the

following requirements:
1 The MPNA PCM time slots must correspond to the announcement numbers.
2) The data link (LD) numbers for the announcements are FIXED AND MANDATORY.
5

3) The routing to announcement numbers (type 4 routing) must not mention the
circuit group name.
4) The announcement broadcast LD number must be entered in the FIDIF file in the
record for that announcement.
A table in Appendix D gives the cross-references between the numbers:

1-routing, 2-announcement, 3-time slot, 4-data link.
THE VALUES IN THIS TABLE MUST BE FOLLOWED TO OBTAIN CORRECT

ANNOUNCEMENT OPERATION (SYNCHRONIZATION / ANNOUNCEMENT).
1.9. TECHNICAL AND OPERATIONAL SEQUENCING CONSTRAINTS
1.9.1. PREREQUISITES
The announcements must first be recorded in the recorded announcement
machine(s) linked to the SSP. Then the corresponding time slot on the MPNA
PCM link is assigned to each announcement (see Appendix D).
Before creating or modifying any data relating to the broadcast of an announcement,

the following points must be checked:
1) Routings with numbers between 17 and 46 must not be used for functions other
than broadcasting announcements.
- If a routing numbered between 17 and 46 is used for other functions (routing to a

circuit group or server), it must be replaced. See Appendix E.
2) Data links with numbers between 256 and 285 must not be used for functions
other than broadcasting announcements.
- If an LD between 256 and 285 is used for another function (type 1 LD/type 3 LD),
it must be replaced. See Appendix E.
3) Make sure that the SSP stations are at release R24 minimum.
1.9.2. PROCEDURE
AT THE SSP
First, the call failure announcements must be defined in the SSP that means that an
INAP announcement number (transmitted by the RCP) must reflect a system number
that in turn is linked to an announcement or a tone in the SSP.

Call failure announcements can be in five different languages. The language used is
chosen on a per-case basis according to the Mobile Country Code (MCC). If this is
not known, the fifth language is automatically selected.
AT THE RCP
This involves updating the RYR_MCCI, RYR_FILM and RYR_OBFM relations at the
RCP.
1.10. OPERATIONS TO BE CARRIED OUT BY THE CUSTOMER
- Back up the stations before the operation.
- The customer must specify:

1) Which announcement broadcasts are required,
2) The associated system (SSP) numbers.
However, if the operator does not himself wish to supply the announcement
numbers, it is always possible to set the numbers arbitrarily for new announcements,
particularly from number 52 where the INAP and SSP system numbers are the same
(see the mapping table).
- Provide and run a test plan after the operation.
- Back up the stations after the operation.

2. UNLOCKING AT SSP LEVEL
2.1. GENERAL
Depending on the number of recorded announcement machines (MP) and the
number of PCM links they have, and depending on whether the SSP is connected to
an IP, the number of announcements will be:
- 1 MP with 1 PCM link: up to 30 announcements

- 1 MP with 2 PCM links: up to 60 announcements
- 2 MP with 2 PCM links: up to 120 announcements
- 2 MP with 2 PCM links and connection to an IP: up to 127 recorded announcements
2.2. PRELIMINARY CHECKS

In principle, a recorded announcement circuit group (NFSC = MPNC1) consists
of circuits 223-00-01 < 223-00-31 that are ENG.
Check that all the time slots of the MPNA PCM link are in fact assigned to the circuit
group and are ENG.
- @FSCIN:
NFSC=MPNC1;
EXAMPLE
@FSCIN,CEN=1:
CEN=1/97-07-04/15 H 33 MN 03/INTERROGATE A CIRCUIT GROUP
NFSC=MPNC1:
PROCESS TGCIN ACC
NFSC=MPNC1 GENR=TD SG=L01E20
AFCT =223-00-01
ETAT=ENG
AFCT =223-00-02
ETAT=ENG
AFCT =223-00-31
ETAT=ENG
If necessary, add the missing time slots.
- @FSCAD:
NFSC=MPNC1,AFCT=223-0-xx<yy;
2.3. OUTPUTTING THE ANNOUNCEMENT CHARACTERISTICS

Use the following command:
@ARCIN
ARCH = XATR
FICH = FIDIF
NUM = 1 TO N
Where n is the number of announcements that have been declared.
Depending on the characteristics read and the ones that are required, make the
necessary changes (duration, etc.) to the announcements according to the
customer's requirements.
2.4. CREATING DATA LINKS

Create one data link for each announcement.
2.5. MODIFYING THE FIDIF FILE ("BROADCASTS FILE")

The announcement or broadcast file is called FIDIF. It must be modified using the
"ARCMO" command when any new announcements are added.
@ARCMO:
ARCH=XATR,FICH=FIDIF,AF=ALL,NUM=XX,CHSI=IN1-A+CL-B+CE-C+NTONA-
D+TRA-E+TONI-F+ANL-G+TEMPO-H+LST-I;
Where:
- xx: Announcement number
- IN1: Signaling code inside the exchange (a=1)
- CL: Line code, if b=1 the announcement is synchronized whereas if b=2 the
announcement is not synchronized
- CE: Recorder code (c varies from 2 to 13, c=4)
- NTONA: Announcement number (d varies from 1 to 127)
- TRA: Transcom category (e=0)
- TONI: Number of the tone to be sent while awaiting connection of the

announcement. Announcement with starting point - (f varies from 1 to 15)

- ANL: Announcement length. g=announcement duration. If g=0, the announcement

duration is supplied by h ("TEMPO" parameter). If g and h are not zero, the
announcement duration will be g with ANL taking priority.
- TEMPO: h=announcement duration. This parameter is effective if g=0 ("ANL"

parameter).
- LST: Charge-free line (i is 0 or 1)
EXAMPLE FOR ANNOUNCEMENTS 1 AND 2:
@ARCMO:
arch=xatr,fich=fidif,af=all,num=01,chsi=in1-1,+cl-1+ce-4+NTONA-1+TRA-0
+TONI-5+ANL-0+TEMPO-20+LST-1;
@ARCMO:
arch=xatr,fich=fidif,af=all,num=02,chsi=in1-1,+cl-1+ce-4+NTONA-2+TRA-0
+TONI-5+ANL-0+TEMPO-20+LST-1;
2.6. INCLUSION OF MODIFICATIONS

The changes take effect when the SMCs supporting the ML CC are rebooted.
2.7. FUNCTIONALITY TEST

The customer only runs the test plan once the modifications have been taken into
account on the different machines in the network.
2.8. RETURN TO OPERATION

None.
10

3. UNLOCKING AT RCP LEVEL
3.1. RCP BACKUP

Before unlocking, a complete system backup must be carried out using the FEX
"PCFS" (see the "Referenced documents" section).
3.2. SETTING THE RYR_MCCI RELATION

This relation has at the maximum 4 tuples of 3 octets each that can be modified
using operator command. The first two octets constitute an MCC (D-MCC), and the
value of the third (MCC identifier = D_MCC_ID) is 01, 02, 03, 04.
The RYR_MCCI relation is delivered empty for the D_MCC_ID values.
MCC <-> language key is:

01 -> announcement in language no. 1
The command to be used is therefore:
*** in ATHOSCO/ATHOSCO/CSMMI ***
INSTUP:PYRC,RYR_MCCI,,,H'XXXFID;
WHERE:
XXXF = MCC
ID = MCC identifier - must be from 1 to 4 inclusive.
The MCC identifier (D_MCC_ID) can be found in the RYR_FILM relation

because it is its first attribute.
3.3. SETTING THE RYR_FILM RELATION

This relation describes the characteristics of each announcement:
the MCC identifier in which it applies,
the protocol (INAP/DTAP),
the error,
the diagnostic report,
the announcement number (D_TFILM). Only this last parameter needs to be completed.
The first four attributes are supplied completed in this relation.
11

NOTE(S): It has one tuple for each message and for each language. On delivery, all
the announcement numbers are zero. When the announcement number is
zero, the tuple has no effect. This is why enabling a particular
announcement requires a no null value in the fifth attribute.
So the operator must specify the announcement to which he linked a particular

system (SSP) number when it was declared in the SSP. For this the proposed
announcements are listed in the following table.
The following mapping table is for working out the announcement number to be
inserted in the RYR_FILM relation.
Number in RCP Number in E10B Number in RCP Number in E10B

1 7 22 27
2 8 23 28
3 16 24 29
4 19 25 30
5 17 26 9
6 6 27 36
7 1 28 18
8 20 29 31
9 21 From 30 to 33 From 32 to 35
num num+2
10 10 34 14
11 11 35 37
12 12 From 36 to 49 From 38 to 51
num num+2
13 5 50 2
14 13 51 3
15 4 52 52
16 15 From 53 to 127 From 53 to 127
num num
17 22
18 23
19 24
20 25
21 26
12

3.3.1. UPDATING THE RYR_FILM RELATION.
The RYR_FILM tuple is :
D_MCC_ID + D_PRTCOL + D_ERROR + D_DIAG + D_TFILM
The tuples of this relation are accessed by key and not directly. The key name is
ERRDIAG; it is a primary key and consists of four of the five attributes in the relation.
These attributes are:
- attribute no. 1: 1 octet, "Mobile Country Code" (it is in the RYR_MCCI relation and
is the 2nd attribute). It varies from 0 to 5, but for an identifier number 5, nothing
must be set. Name of this attribute: D_MCC_ID.
- attribute no. 2: 1 octet, specifies the protocol used. The values are: 06 for DTAP
and 09 for MAP and INAP. Name of this attribute: D_PRTCOL.
- attribute no. 3: 7 octets, error code. Name of this attribute: D_ERROR.
- attribute no. 4: 2 octets, diagnostic. Name of this attribute: D_DIAG .
- attribute no. 5: 5 octets, announcement number. Name of this attribute: D_TFILM.
DESCRIPTION OF D_TFILM
D_TFILM is completed as follows:
With valkey= value of the key (11 bytes which are:

D_MCC_ID+D_PRTCOL+D_ERROR+D_DIAG)
1) For an announcement by tone (current):
UPDTUP:PYRC,RYR_FILM,KEY,ERRDIAG,H'VALKEY,,,5:H'01000000NT;
Where: NT = Number of announcement by tone
13

2) For an announcement by film (current):
UPDTUP:PYRC,RYR_FILM,KEY,ERRDIAG,H'VALKEY,,,5:H'0200NF0000;
Where: NF = Number of the announcement by film
3) For an announcement by tone (with sending of CON or ACM+ANM):
4) For an announcement by film (with sending of CON or ACM+ANM):
5) When an announcement by tone must lead to an efficient call:
*** In ATHOSCO/ATHOSCO/CSMMI ***
6) When an announcement by film must lead to an efficient call:
*** In ATHOSCO/ATHOSCO/CSMMI ***
14

7) For no announcement:
UPDTUP:PYRC,RYR_FILM,KEY,ERRDIAG,H'VALKEY,,,5:H'00XXXXXXXX;
Where: XXXXXX = Any value because it will not be read.

Consequently, the function is disabled for a particular announcement
when the first octet of the associated tuple in RYR_FILM is set to H'00.
NOTE (S): In addition, here is an example of a modification to be made in the

RYR_MCCI and RYR_FILM relations to declare an announcement:

INSTUP:PYRC,RYR_MCCI,,,H'208F01;
Therefore, for the 208F MCC (language 1), D_MCC_ID is 01. In this
language, we will set the announcement number 03 for the "mobile black
list (security failure)" error message:
UPDTUP:PYRC,RYR_FILM,KEY,ERRDIAG,H'0106620115000000000A19,,,5:H'0200030000;
3.4. FOR "CALL HOLD" ANNOUNCEMENTS
For the "Call Hold" announcement, do not use its number in the RYR_FILM relation.
For the procedure, apply the MPI "Processing SS notifications"

(Ref. 3BL 41417AAAA MSAGA).
3.5. SETTING THE RYR_OBFM RELATION
This relation indicates the announcement numbers with one tuple for each
announcement, knowing that the RCP can record up to 127 announcements. It is
used for observations on announcements. It comprises a single attribute,
D_FM_NBR, which is the announcement number in the RCP and is 2 octets long.
INSTUP:PYRC,RYR_OBFM,,,H'NNNN;
Where NNNN = Announcement number
15

NOTE (S):
It is important to perform a switchover (running the "SWOCTL" command) so that any
modifications to this relation take effect.
3.6. INCLUSION OF MODIFICATIONS

Inclusion of the modification is not immediate and a switchover is necessary when
you take into consideration the announcement counters.
The modification of RYR_FILM is immediate.
3.7. RCP BACKUP

After unlocking, a complete system backup must be carried out using the FEX
"PCFS" (see the "Reference documents" section).
3.8. RETURN TO OPERATION

None.
3.9. TESTING THE FUNCTIONALITY.

The customer executes his test plan, only when the station has been modified.
16

4. APPENDIX A = LIST OF ANNOUNCEMENTS
The DTAP/INAP errors with the associated diagnostic reports are shown in the tables
below for terminating and originating calls.
DTAP cause value for Mobility Management Diagnostic Comments

IMSI unknown in HLR
Illegal MS No announct
IMSI unknown in VLR No announct
IMEI not accepted
Illegal ME
PLMN not allowed
Location Area not allowed
National Roaming not allowed in this LA
Network failure
Congestion
Service option not supported
Requested service option not subscribed
Service option temporarily out of order
Call cannot be identified
Invalid messages
Figure 1. DTAP (Mobility Management) errors
DTAP cause value for Call Control Diagnostic Comments
Unassigned (unallocated) number

No route to destination Absent subscriber
detected at HLR
No route to destination
Channel unacceptable
Operator determined barring
Normal call clearing No announct
User busy
User busy CCBS possible
No user responding
User alerting, no answer
Call rejected Security failure
Call rejected SCP Call barred
Call rejected Operator barring
Call rejected Translation failure
17

Call rejected SCP server absent

Call rejected SCP call release
Call rejected CF blocked
Number changed
Destination out of order
Invalid number format
Facility rejected Unknown CUG id
Facility rejected No CUG selected
Facility rejected CUG id incompatible with
requested BS
Facility rejected OC barred within CUG
Facility rejected
Response to STATUS ENQUIRY
Normal, unspecified Call barred due to BAOC
(SS)
Normal, unspecified Call barred due to BOIC or
BOIC-exHC
Normal, unspecified Absent subscriber
Normal, unspecified Operator barring no announct
Normal, unspecified Special Information Tone
Normal, unspecified CF blocked
Normal, unspecified CAMEL modified number CCBS
Normal, unspecified SCP Server Absent
Normal, unspecified SCP Call Release
No circuit channel available
No circuit channel available CCBS possible
Network out of order
Temporary failure no accounct
Switching equipment congestion
Switching equipment congestion Call gaping
Access information discarded
Requested circuit/channel not available
Resource unavailable, unspecified
Quality of service unavailable
Requested facility not subscribed CLIR not subscribed
Requested facility not subscribed
Incoming call barred in the CUG
Bearer capability not authorized
Bearer capability not presently available
Service or option not available,unspec
Bearer service not implemented
ACM equal to or greater than ACM max
Requested facility not implemented
Only restricted digital information
Service or opt. not implemented,unspec
Invalid Transaction Identifier value
User not member of CUG
Incompatible destination
Invalid transit network selection
18

Semantically incorrect message

Protocol errors
Recovery On Timer Expiry
Interworking, unspecified
Figure 2. DTAP (Call Control) errors
INAP error Diagnostic Comments

Unallocated number
No route to specified transit network
No route to destination
Send special information tone
Misdialed number
Channel unacceptable
Call awarded and being delivered in an
establishment channel
Preemption
Preemption - circuit reserved
Normal clearing No announct
User busy User Determined User
Busy UDUB
User busy NDUB
User busy CF Blocked
User busy CCBS possible
User busy
No user responding
No user responding No paging response
No user responding Paging Congestion
No answer from user (user alerted)
No answer from user CF Blocked
Subscriber absent No paging response
Subscriber absent Paging congestion
Subscriber absent Detected by HLR
Subscriber absent Other Radio Problem
Subscriber absent CF Blocked
Subscriber absent
Call rejected
Call rejected
Call rejected Call barred
Call rejected Call operator barring
Number changed CF Blocked
Intercepted subscriber
Non selected user cleaning
Destination out of order
Destination out of order SCP Call Barred
Destination out of order Operator barring
Invalid number format (incomplete
addr.)
19

Facility rejected
Facility rejected UDUB
Facility rejected NDUB
Response to STATUS ENQUIRY
Normal, unspecified SCP server absent
Normal, unspecified SCP call release
Normal, unspecified Security failure
Normal, unspecified Radio Interface Failure
Normal, unspecified
No circuit/channel available
No circuit/channel available CCBS possible
No circuit/channel available Paging Congestion
Network out of order
Permanent frame mode connection out
of service
Permanent frame mode connection
operational
Temporary failure Radio interface failure
Temporary failure Radio congestion
Temporary failure No paging response
Temporary failure Paging congestion
Temporary failure
Switching equipment congestion
Switching equipment congestion Call gaping
Access information discarded
Requested circuit/channel not available
Precedence call blocked
Resource unavailable, unspecified
Quality of service not available
Requested facility not subscribed
Outgoing call barred within CUG
Incoming call barred within CUG
Bearer capability not authorized
Bearer capability not presently available
Inconsistency in designated outgoing
access info. and subscriber class
Service or option not available,unspec.
Bearer capability not implemented
Channel type not implemented
Requested facility not implemented
Only restricted digital information,
Service or option not implemented,
unspecified
Invalid call reference value
Identified channel does not exist
A suspended call exists
Call identity in use
No call suspended
Call having the requested call identity
20

User not member of CUG Call barred SS

User not member of CUG Operator barred
User not member of CUG
Incompatible destination
Incompatible destination Call Barred
Incompatible destination Operator Barred
Non existent CUG
Invalid transit network selection
Invalid message, unspecified
Protocol errors, unspecified
Interworking, unspecified
Figure 3. INAP errors
21

5. APPENDIX B = ERROR KEY AND TEXT
NOTE (S):
The key is not duplicated; its name is ERRDIAG and it comprises the
following attributes: (1) D_MCC_ID, (2) D_PRTCOL, (3) D_ERROR, (4)
D_DIAGN.
The letters between brackets, I or G, following the above attribute names

mean:
-I: ALCATEL error
-G: GSM specific error
DTAP MOBILITY MANAGEMENT (LOCATION ATTEMPT FAILURE)
attributes 2 + 3 + 4 = texts
06000000020000000000 = IMSI unknown in HLR

06000000030000000000 = Illegal MS
06000000040000000000 = IMSI unknown in VLR
06000000050000000000 = IMEI not accepted
06000000060000000000 = Illegal ME
060000000B0000000000 = PLMN not allowed
060000000C0000000000 = Location area not allowed
060000000D0000000000 = National roaming not allowed
06000000110000000000 = Network failure
06000000160000000000 = Congestion
06000000200000000000 = Service option not supported
06000000210000000000 = Requested service option not subscribed
06000000220000000000 = Service option temporarily out of order
06000000260000000000 = Call cannot be identified
060000005F0000000000 = Invalid messages
06000000650000000000 = Invalid messages
060000006F0000000000 = Invalid messages
DTAP CALL CONTROL (OC SET UP FAILURE)
06620101000000000000 = Unassigned (unallocated) number

06640101000000000000 = Unassigned (unallocated) number (SWitch)
06620103000000000A18 = No route to destination - Absent subscriber HLR (I)
06620103000000000000 = No route to destination
06620106000000000000 = Channel unacceptable
06620108000000000000 = Operator determined barring
06620110000000000000 = Normal call clearing
! 066A0110000000000000 = Normal call clearing
06620111000000000000 = User busy
06640111870000000607 = User busy CCBS possible (GSM)
06640111000000000607 = User busy CCBS possible (GSM)
22

06620112000000000000 = No user responding

06620113000000000000 = User alerting no answer
06620115000000000000 = Call Rejected
06620115000000000A19 = Call Rejected Security failure (I)
06620115000000000A1B = Call Rejected Translation failure (I)
06620115000000000A15 = Call Rejected (OC) SCP Server Absent (I)
06620115000000000A16 = Call Rejected (OC) SCP Call Release (I)
06640115000000000A14 = Call Rejected (SW) SCP Call Barred (I)
06640115000000000A21 = Call Rejected (SW) Operator Barring (I)
06620115000000000A25 = Call Rejected (SW) CF Blocked
06620116000000000000 = Number changed
0662011B000000000000 = Destination out of order
! 0664011B000000000A14 = Destination out of order - SCP Call Barred (I)
! 0664011B000000000A21 = Destination out of order - Operator barring(I)
0662011C000000000000 = Invalid number format
0662011D000000000603 = Facility rejected Unknown CUG index (G)
0662011D000000000602 = Facility rejected No CUG selected (G)
0662011D000000000604 = Facility rejected CUG index Incompatible (G)
0662011D000000000601 = Facility rejected CUG index Incompatible (G)
0662011D000000000000 = Facility rejected
0664011D000000000000 = Facility rejected (SW)
0664011D850000000605 = Facility rejected CUG Call Failure Unspe (G)(SW)
0662011E000000000000 = Response to STATUS ENQUIRY
0662011F000000000A14 = Normal Unspecified Call barred (I)
0662011F000000000A15 = Normal Unspecified SCP Server Absent(I)
0662011F000000000A16 = Normal Unspecified SCP Call Release (I)
0662011F000000000A18 = Normal Unspecified Absent Subscriber at HLR (I)
0662011F000000000A21 = Normal Unspecified Operator Barring (I)
0662011F000000000A23 = Normal Unspecified Special Information Tone(I)
0662011F000000000000 = Normal Unspecified
0664011F000000000A18 = Normal Unspecified (SW) Absent Subscriber (I)
0662011F000000000A24 = Normal Unspecified Call barred BOIC or BOICexHC
0662011F000000000A25 = Normal Unspecified CF Blocked
0662011F000000000A26 = Normal Unspecified CAMEL modified number CCBS
06620122000000000000 = No circuit channel available
06640122870000000607 = No circuit channel available CCBS possible (GSM)
06640122000000000607 = No circuit channel available CCBS possible (GSM)
06620126000000000000 = Network out of order
06620129000000000000 = Temporary failure
06640129000000000000 = Temporary failure (SW)
0662012A000000000000 = Switching equipment congestion
0662012A000000000A28 = Switching equipment congestion - Call Gapping
0662012B000000000000 = Access info discarded
0662012C000000000000 = Requested circuit channel not available
0662012F000000000000 = Resource unavailable unspecified
06620131000000000000 = Quality of service unavailable
06620132000000000606 = Requested facility not subscribed CLIR not subscribed (G)
06620132000000000000 = Requested facility not subscribed
06620137000000000000 = Incoming calls barred in the CUG
23

06640137000000000000 = Incoming calls barred in the CUG (SW)

06620139000000000000 = Bearer capability not authorized
06640139000000000000 = Bearer capability not authorized (SW)
0662013A000000000000 = Bearer capability not presently
0662013F000000000000 = Service or option not available
0664013F000000000000 = Service or option not available (SW)
06620141000000000000 = Bearer service not implemented
06620144000000000000 = ACM equal to or greater than ACM mx
06620145000000000000 = Requested facility not implemented
06620146000000000000 = only restricted digital info
0662014F000000000000 = Service or option not implemented
0664014F000000000000 = Service or option not implemented (SW)
06620151000000000000 = Invalid transaction Identifier value
06620157000000000000 = User not member of CUG
06640157000000000000 = User not member of CUG (SW)
06620158000000000000 = Incompatible destination
0662015B000000000000 = Invalid transit network selection
0662015F000000000000 = Semantically incorrect message
06620160000000000000 = Protocol errors
06620161000000000000 = Protocol errors
06620162000000000000 = Protocol errors
06620163000000000000 = Protocol errors
06620164000000000000 = Protocol errors
06620165000000000000 = Protocol errors
! 06620166000000000000 = Recovery On Timer Expiry
06620167000000000000 = Protocol errors
06620168000000000000 = Protocol errors
06620169000000000000 = Protocol errors
0662016A000000000000 = Protocol errors
0662016B000000000000 = Protocol errors
0662016C000000000000 = Protocol errors
0662016D000000000000 = Protocol errors
0662016E000000000000 = Protocol errors
0662016F000000000000 = Protocol errors
0662017F000000000000 = Interworking unspecified
INAP (TC SET UP FAILURE)

09028081000000000000 = Unallocated number
09028082000000000000 = No route to specified transit network
09028083000000000000 = No route to destination
09028084000000000000 = Send special information tone
09028085000000000000 = Misdialed number
09028086000000000000 = Channel unacceptable
09028087000000000000 = Call awarded and being delivered
09028088000000000000 = Preemption
09028089000000000000 = Preemption circuit reserved
09028090000000000000 = Normal clearing
09028091000000000A1C = User busy NDUB (I)
09028091000000000A17 = User busy UDUB (I)
24

09028091000000000A25 = User busy CF Blocked

09038091010000000607 = User busy CCCBS possible (GSM)
09028091000000000000 = User busy (I)
09028092000000000000 = No user responding
! 09028092000000000A1D = No user responding - No paging response
! 09028092000000000A22 = No user responding - Paging Congestion
09028093000000000000 = No answer from user
09028093000000000A25 = No answer from user - CF Blocked
09028094000000000A1D = Subscriber absent - No paging response (I)
D_TFILM=0200220000
09028094000000000A1E = Subscriber absent Detected by the HLR (I)
09028094000000000A22 = Subscriber absent Paging Congestion (I)
09028094000000000A25 = Subscriber absent CF Blocked
09028094000000000A27 = Subscriber absent Other radio problem
09028094000000000000 = Subscriber absent
09028095000000000000 = Call Rejected
09028095000000000A14 = Call Rejected Call Barred (I)
09028095000000000A21 = Call Rejected Operator Barring (I)
09028095000000000A25 = Call Rejected CF Blocked
! 09028095000000000A29 = Call Rejected Call Collect (I)
09028096000000000000 = Number changed
09028099000000000000 = Intercepted subscriber
0902809A000000000000 = Non selected user clearing
0902809B000000000000 = Destination out of order
! 0902809B000000000A14 = Destination out of order SCP Call Barred (I)
! 0902809B000000000A21 = Destination out of order Operator barring (I)
0902809C000000000000 = Invalid number format
0902809D000000000000 = Facility rejected
0902809D000000000A17 = Facility rejected UDUB
0902809D000000000A1C = Facility rejected NDUB
0902809E000000000000 = Response to status enquiry
0902809F000000000A15 = Normal unspecified SCP Server Absent (I)
0902809F000000000A16 = Normal unspecified SCP Call Release (I)
0902809F000000000A19 = Normal unspecified Security Failure (I)
! 0902809F000000000A20 = Normal unspecified Radio Interface Failure (I)
! 0902809F000000000A29 = Normal unspecified Call Collect (I)
0902809F000000000000 = Normal unspecified
090280A2000000000000 = No circuit channel available
090380A2010000000607 = No circuit channel available CCBS possible (GSM)
! 090280A2000000000A22 = No circuit channel available Paging Congestion (I)
090280A6000000000000 = Network out of order
090280A7000000000000 = Permanent frame mode connection out
090280A8000000000000 = Permanent frame mode connection operator
090280A9000000000A20 = Temporary failure Radio interface failure (I)
090280A9000000000A1F = Temporary failure Radio Congestion (I)
090280A9000000000000 = Temporary failure
! 090280A9000000000A1D = Temporary failure No paging response (I)
! 090280A9000000000A22 = Temporary failure Paging Congestion (I)
090280AA000000000000 = Switching Equipment congestion
25

090280AA000000000A28 = Switching Equipment congestion - Call Gapping (I)

090280AB000000000000 = Access information discarded
090280AC000000000000 = Requested circuit channel not available
090280AE000000000000 = Precedence call blocked
090280AF000000000000 = Resource unavailable unspecified
090280B1000000000000 = Quality of service not available
090280B2000000000000 = Requested facility not subscribed
090280B5000000000000 = Outgoing calls barred within CUG
090280B7000000000000 = Incoming calls barred within CUG
090280B9000000000000 = Bearer capability not authorized
090280BA000000000000 = Bearer capability not presently available
090280BE000000000000 = Inconsistency in designated
090280BF000000000000 = Service or option not available
090280C1000000000000 = Bearer capability not implemented
090280C2000000000000 = Channel type not implemented
090280C5000000000000 = Requested facility not implemented
090280C6000000000000 = Only restricted digital info
090280CF000000000000 = Service or option not implemented
090280D1000000000000 = Invalid call reference value
090280D2000000000000 = Identified channel does not exist
090280D3000000000000 = A suspended call exist
090280D4000000000000 = Call identity in use
090280D5000000000000 = No call suspended
090280D6000000000000 = Call having the requested call identity
090280D7000000000A14 = User not member of CUG Call barred
090280D7000000000A21 = User not member of CUG Operator barred
090280D7000000000000 = User not member of CUG
090280D8000000000000 = Incompatible destination
090280D8000000000A14 = Incompatible destination Call barred
090280D8000000000A21 = Incompatible destination Operator barring
090280DA000000000000 = Non existent CUG
090280DB000000000000 = Invalid transit network selection
090280DF000000000000 = Invalid message unspecified
! 090280E4000000000000 = Invalid IE contents
090280EA000000000000 = Protocol errors
090280EB000000000000 = Protocol errors
090280EC000000000000 = Protocol errors
090280ED000000000000 = Protocol errors
090280EE000000000000 = Protocol errors
090280EF000000000000 = Protocol errors
26

090280FF000000000000 = Interworking unspecified
27

6. APPENDIX C = DIAGNOSTIC REPORTS (D_DIAGN)
C.1 GSM DIAGNOSTICS
* 01 : Outgoing calls barred within CUG

* 02 : No CUG selected
* 03 : Unknown CUG index
* 04 : CUG index incompatible with requested basic service
* 05 : CUG call failure unspecified
* 06 : CLIR not subscribed
* 07 : CCBS possible
C.2 NO-GSM DIAGNOSTICS
* 14 : Call Barred (Supplementary Service)

* 15 : SCP server absent
* 16 : SCP Call Release
* 17 : User Determine User Busy
* 18 : Absent subscriber detected at HLR (MS_MS call)
* 19 : Security failure
* 1A : Call rejected
* 1B : Translation Failure
* 1C : Network Determined User Busy
* 1D : No paging response
* 1E : Detected by the HLR (MS detach, VLR address UnK, Roaming not allowed)
* 1F : Radio congestion
* 20 : Radio interface failure
* 21 : Operator Barring
* 22 : Paging Congestion
* 23 : Special Information Tone
* 24 : Call barred BOIC or BOICexHC
* 25 : Blocking of CF according to calling party category
* 26 : CAMEL modified number at CCBS recall
* 27 : Other radio problem
* 28 : Call Gapping
* 29 : Call collect
28

7. APPENDIX D = LINKS BETWEEN ANNOUNCEMENT
NUMBERS, TIME SLOTS, DATA LINKS AND ROUTING
ANN TS LD ROUT FIDIF ANN TS LD ROUT FIDIF

no. no. no. no. Record no. no. no. no. Record
01 01 256 017 01 16 17 271 032 17

02 02 257 018 02 17 18 272 033 18
03 03 258 019 03 18 19 273 034 19
04 04 259 020 04 19 20 274 035 20
05 05 260 021 05 20 21 275 036 21
06 06 261 022 06 21 22 276 037 22
07 07 262 023 07 22 23 277 038 23
08 08 263 024 08 23 24 278 039 24
09 09 264 025 09 24 25 279 040 25
10 10 265 026 10 25 26 280 041 26
11 11 266 027 11 26 27 281 042 27
12 12 267 028 12 27 28 282 043 28
13 13 268 029 13 28 29 283 044 29
14 14 269 030 14 29 30 284 045 30
15 15 270 031 15 30 31 285 046 31
29

8. APPENDIX E = RETRIEVING ROUTINGS AND DATA LINK
NUMBERS
If a routing between 17 and 46 or a data link between 256 and 285 is used for
functions other than broadcasting announcements, it must be replaced.
8.1. REPLACING THE LD

LIST THE CHARACTERISTICS OF THE LD TO BE REPLACED
@LDIL:
SRV='srv-name',ILS='ils-name';
8.1.1. FOR A TYPE 3 LD

1) On the adjacent machines, RCP, HLR, STp, MV etc, find the signaling link that
uses this LD.
2) If possible, block the signaling link.
3) Delete the LD:
@LDSU:
4) Rebuild the LD with the parameters previously noted using LDIL:
@LDCR:
AFCTE=ur-pcm-ts,AFCTS=ur-pcm-ts,TYLD=3,SRV=srv-name,ILS=ils-name,
DISLD=survx;
6) If necessary unblock the signaling link.
8.1.2. FOR A TYPE 1 LD

1) Find the SLC using that LD:
@CSMIN:
LSD=nnn;
nnn = NLD value read using LDIL
2) Display the signaling link set to which the SLC belongs:
@FSMIN:
NFSM=='fsm-name';
fsm-name = NFSM value read using CSMIN
30

3) Block the signaling link:
@CSMMO:
NFSM='fsm-name',SLC=nn,ETCS=INAC+BLOM;
4) Remove the link from the signaling link set:
@FSMRE:
NFSM='fsm-name',SLC=nn;
5) Delete the LD:
@LDSU:
@LDCR:
AFCTE=ur-pcm-ts,TYLD=1,SRV='srv-name',ILS='ils-name';
7) Add the link to the signaling link set:
@FSMAD:
NFSM='fsm-name',SLC=nn,SRV='srv-name',ILS='ils-name',RANC=rank,TSV=tsv;
8) Unblock the signaling link:
@CSMMO:
NFSM='fsm-name',SLC=nn,ETCS=ACTI+NBLO;
8.1.3. FOR A FSM WITH ONLY ONE SLC
If the signaling link set consists of only one SLC, the traffic between the SSP and the
remote unit using the SLC will be completely disconnected during the operation.
1) Create a working LD with an AFCTE, an SRV and any ILS:
@LDCR:
AFCTE=ur-pcm-ts,TYLD=1,SRV='srv-name',ILS='ils-name'...;
2) Add a working link to the signaling link set:
@FSMAD:
SRV and ILS of the working LD
3) Block the signaling link that is using the LD to be retrieved:

31

@CSMMO:
NFSM='fsm-name',SLC=nn,ETCS=INAC+BLOM;
4) Remove the link from the signaling link set:
@FSMRE:
5) Delete the LD:
@LDSU:
@LDCR:
AFCTE=ur-pcm-ts,TYLD=1,SRV='srv-name',ILS='ils-name';
7) Add the link to the signaling link set:
@FSMAD:
8) Unblock the signaling link:
@CSMMO:
NFSM='fsm-name',SLC=nn,ETCS=ACTI+NBLO;
9) Remove the working link created in 2) from the signaling link set:
@FSMRE:
10) Delete the working LD created in 1):
@LDSU:
8.2. REPLACING THE ROUTING
1) Interrogate the routing to be replaced:
@ACHIN:
ACH='routing-no.';
routing-no. = routing to be replaced = 17 < routing no. > 46
32

2) Create a new routing with the same characteristics as the routing to be

replaced:
@ACHCR:
ACH='routing-no.',TYPE=type,NFSC=nfsc,AC=x-y,DIS=dis,....:
3) Find out whether the routing belongs to a type12 or type07 MULTIPLE routing:
@ACHIL:
TYPE = 12,ACM = 'routing-no.':
TYPE = 7,ACM = 'routing-no.';
If the routing belongs to a multiple routing:
4) Modify the multiple routing so as to replace the routing number to be retrieved

with the routing number that has just been created:
@ACHMO:
ACH = 'routing-type-7/12',ACM=x-'routing-no.';
5) Find the area codes pointing to the routing number to be replaced:
@RANIN:
ACH=ROUTING NO;
6) Modify these area codes to send them to the new routing that has just been
created:
@INDMO:
IND=AREACODE NO.,ACHN=ROUTING NO.-1<64;
7) Delete the routing for which the number has just been retrieved:
@ACHSU:
ACH='routing-no.';
33

Routing To An Announcement

Hochgeladen von

Dokumentinformationen

Originaltitel

Copyright

Verfügbare Formate

Dieses Dokument teilen

Dokument teilen oder einbetten

Freigabeoptionen

Stufen Sie dieses Dokument als nützlich ein?

Sind diese Inhalte unangemessen?

Copyright:

Verfügbare Formate

Routing To An Announcement

Hochgeladen von

Copyright:

Verfügbare Formate

ROUTING TO AN ANNOUNCEMENT

INSTALLATION METHODS AND PROCEDURES

3BL 41392 AAAA MSAGA Ed. 04

Status RELEASED 2005/01/10

All rights reserved. Passing on and copying of this document, use

3BL 41392 AAAA MSAGA Ed. 04 RELEASED

3BL 41392 AAAA MSAGA Ed. 04 RELEASED

1.1. REFERENCED DOCUMENTS

- RXTACH Routing to an announcement 3BL33336AAAAREAGA

This procedure describes how unlocked/locked the function:

This function is for broadcasting an announcement to a mobile or the fixed network

There are three types of announcement:

1.4. General problem

The function is unlocked or locked using manufacturer or operator commands from a

3BL 41392 AAAA MSAGA Ed. 04 RELEASED

1.5. General operating requirements

1.6. Services to be performed by the customer

- Takes a backup of the station or stations before the operation.

- The customer must specify:

- Supplies and executes a test plan after the operation.

- Takes a backup of the station or stations after operation.

1.7. Services to be performed by the manufacturer

1.8. GENERAL INTERVENTION CONSTRAINTS

Implementation of the functionalities linked to recorded announcements carries the

3BL 41392 AAAA MSAGA Ed. 04 RELEASED

A table in Appendix D gives the cross-references between the numbers:

THE VALUES IN THIS TABLE MUST BE FOLLOWED TO OBTAIN CORRECT

1.9. TECHNICAL AND OPERATIONAL SEQUENCING CONSTRAINTS

Before creating or modifying any data relating to the broadcast of an announcement,

- If a routing numbered between 17 and 46 is used for other functions (routing to a

3BL 41392 AAAA MSAGA Ed. 04 RELEASED

1.10. OPERATIONS TO BE CARRIED OUT BY THE CUSTOMER

- Back up the stations before the operation.

- The customer must specify:

- Provide and run a test plan after the operation.

- Back up the stations after the operation.

3BL 41392 AAAA MSAGA Ed. 04 RELEASED

2. UNLOCKING AT SSP LEVEL

- 1 MP with 1 PCM link: up to 30 announcements

2.2. PRELIMINARY CHECKS

If necessary, add the missing time slots.

2.3. OUTPUTTING THE ANNOUNCEMENT CHARACTERISTICS

3BL 41392 AAAA MSAGA Ed. 04 RELEASED

Use the following command:

Where n is the number of announcements that have been declared.

2.4. CREATING DATA LINKS

2.5. MODIFYING THE FIDIF FILE ("BROADCASTS FILE")

- xx: Announcement number

- IN1: Signaling code inside the exchange (a=1)

- CE: Recorder code (c varies from 2 to 13, c=4)

- NTONA: Announcement number (d varies from 1 to 127)

- TRA: Transcom category (e=0)

- TONI: Number of the tone to be sent while awaiting connection of the

3BL 41392 AAAA MSAGA Ed. 04 RELEASED

- ANL: Announcement length. g=announcement duration. If g=0, the announcement

- TEMPO: h=announcement duration. This parameter is effective if g=0 ("ANL"

- LST: Charge-free line (i is 0 or 1)

EXAMPLE FOR ANNOUNCEMENTS 1 AND 2:

2.6. INCLUSION OF MODIFICATIONS

2.7. FUNCTIONALITY TEST

2.8. RETURN TO OPERATION

3BL 41392 AAAA MSAGA Ed. 04 RELEASED

3. UNLOCKING AT RCP LEVEL

* in ATHOSCO/ATHOSCO/CSMMI *

* in ATHOSCO/ATHOSCO/CSMMI *

* in ATHOSCO/ATHOSCO/CSMMI *

* in ATHOSCO/ATHOSCO/CSMMI *

* in ATHOSCO/ATHOSCO/CSMMI *

* In ATHOSCO/ATHOSCO/CSMMI *

* In ATHOSCO/ATHOSCO/CSMMI *

* in ATHOSCO/ATHOSCO/CSMMI *

* in ATHOSCO/ATHOSCO/CSMMI *

* in ATHOSCO/ATHOSCO/CSMMI *

* in ATHOSCO/ATHOSCO/CSMMI *