Annoucement Play

Open USER GUIDE 1 (12) Prepared (also subject responsible if other) No.

EED/P/TG M.Geisen 1/1553-C/APT 210 26/3 Uen Approved Checked

Date Rev Reference EED/P/TC (N. Floeren) - 2004-01-11 A

Announcement at Call Set-up, User Guide

Copyright

© Ericsson AB 2004, all rights reserved. No part of this document may be reproduced in any form without the written permission of the copyright holder.

Disclaimer

The contents of this document are subject to revision without notice due to continued progress in methodology, design, and manufacturing.

Ericsson shall have no liability for any errors or damages of any kind resulting from the use of this document.

Abstract

The .Announcement At Call Set-up. function provides the operator an option to play an announcement to the calling subscriber before the call setup procedure is continued to the final destination.

Contents

1 General................................................................................................2

1.1 Revision History..................................................................................2

1.2 Glossary..............................................................................................2

1.3 Scope..................................................................................................2

1.4 Introduction..........................................................................................2

2 How to Use..........................................................................................3

2.1 Routing the call to announcement.......................................................3

2.2 Generation of early ACM as first backward messages........................5

2.3 Generation of release after the announcement is finished..................5

2.4 Continuation of call setup to final destination......................................6

2.5 Examples.............................................................................................8

3 Configuration.....................................................................................11

4 References........................................................................................11




1 General

1.1 Revision History

This is a new document.

1.2 Glossary

1.2.1 Concepts

Announcement An announcement (in the sense of this document) is an already defined and recorded message. The announcement can be identified by an announcement code (either included in the B-number or defined on the route to the announcement system). The announcement code definition in the MGW (if used) and the AXE has to be kept consistent.

EOS code An AXE internal End-of-selection code used when the call set-up is regarded as unsuccessful. It contains the reason for failure. It can be received and used for analysis purpose until an answer is received.

Early Address Complete Message An early address complete message is an address complete message with no information concerning the called subscriber.

1.2.2 Abbreviations

ANNC - Announcement Code RSV - Register Signaling Diagram Variant FNC - Function Code EOS - End of Selection Code BO - B-Number Origin RC - Routing Case

1.3 Scope

This document describes the configuration of the .Announcement At Call Set-up. functionality, which applies to MSC/VLR and GMSC nodes. Only relevant announcement data for this function are explained in this document. For detailed announcement data specification see Chapter References.

1.4 Introduction

The .Announcement At Call Set-up. function provides the operator an option to play an announcement to the calling subscriber before the call set-up procedure is continued to the final destination. With this function the operator is able to provide the subscriber information during the call set-up procedure, for example about a re-routing or tariff per minute and the subscriber can decide to continue the call or not.




The announcement is triggered within the traffic control analysis functions.

1.4.1 Background

The message at call set-up function plays an announcement to the calling subscriber before the call is routed to the final destination.

When the first forward set-up message is received in the analysis of the destination is pointing at a route towards announcement. To select the announcement,

an announcement code (ANNC) is either specified in the B-number (first five digits that are added to the B-Number) or the announcement code is specified in route data.

A first backward set-up message is sent indicating in-band information available and no indication for called party status in order to through connect for the subscriber to hear the announcement. The backward message also causes the time supervision to be stopped.

The announcement is played.

At the end of the announcement an EOS-code is generated.

The analysis of this EOS-code leads to route the call towards the final destination.

2 How to Use

2.1 Routing the Call to Announcement

2.1.1 Defining the Announcement Code in B-number

To access an announcement from different traffic analysis functions, for example Carrier Analysis, Charging Analysis, A-number analysis and so on the modification of the B-number should be done by the means of EOS analysis. Therefore, it is recommended to use one of the reserved EOS codes (500-599) from the traffic analysis functions to add the announcement code to controlling B-number. The announcement code is fixed to a length of five digits.

If the announcement shall be only accessed from the B-number analysis the B-number analysis can add the announcement code directly to the called party number. After the B-number modification the B-number analysis shall be started/restarted from the first digit on in a separate origin, specified in the F parameter. The restarted B-number analysis shall lead to an RC towards a route of device type TCIA.




Figure 1: Analysis function involved in a call to announcement. The announcement code is added to the B-number.

2.1.2 Defining the Announcement Code in Route Data

The announcement code can be defined without called party number modification as well. Therefore, the parameter MB (modification of B-number) has to be defined in route data that represents the announcement code (See Application Information of block TCIA for further information).

Note, that the defined announcement code in route data has priority over the included announcement code in the B-number if an announcement code is defined in both.

Figure 2: Analysis function involved in a call to announcement using the announcement code specified in route data.

Route Analysis

RC

B-num

ber Analysis

B-number, BO

R= TCIAxx MB=ANNC

RC

B-number

Analysis

Route Analysis

ANNC +B-number, New BO

B-number

, BO

EOS Analysis

R= TCIAxx DETY=TCIA

EOS code Open USER

GUIDE 5 (12) Prepared (also subject responsible if other) No.

EED/P/TG M.G

eisen 1/1553-C/APT 210 26/3 Uen Approved Checked Date Rev Reference

E

ED/P/TC (N. Floeren) - 2004-01-11 A

2.2 Generation of Early ACM as First Backward Messages

To play an announcement a route with device type TCIA has to be set up. The TCIA route has to be configured that an early ACM is sent and a speech path is established. Therefore, the Register Signaling Variant (RSV) in route data of the TCIA route has to be set to the following value (for further information see Application Information of block TCIA):

• The B-answer indicator (RSV.Y) has to be set to .no B-answer. so no .alerting. indication is set

and it is possible to reroute the call to the final destination.

• The end of selection indicator has to be set up to .speech position. when the announcement is played (RSV.Z).

• An early ACM shall be sent which has to be indicated in the RSV.W before the announcement is played to prevent a timer expiry during the announcement.

2.3 Generation of Release after the Announcement is Finished

2.3.1 TCIA Route Configuration

The TCIA route has to be configured that after the announcement is played an immediate release is sent. Therefore, the Register Signaling Variant (RSV) in route data of the TCIA route has to be set to the following value (ffor further information see Application Information of block TCIA):

• The immediate release (RSV.X) is mandatory for this function because otherwise it is not possible to establish the call leg to the final destination. Therefore, the RSV.X has to be set to .Yes..

Open USER GUIDE 6 (12) Prepared (also subject responsible if other) No. EED/P/TG M.Geisen 1/1553-C/APT 210 26/3 Uen Approved Checked Date Rev Reference EED/P/TC (N. Floeren) - 2004-01-11 A

2.3.2 SI Parameter Configuration in Route Analysis

Before the call is routed to announcement the SI value has to be defined in route analysis. The SI value determines the EOS code that is analyzed after the call leg to the announcement is released. The result of this EOS analysis determines how to proceed with the call set-up.

Figure 3: Route analysis data configuration to determine the EOS code to continue the call

It is recommended to use also only the reserved EOS codes from the traffic analysis functions (500-599).

Note, that the SI parameter is a generic parameter used to trigger actions in the specified device type (DETY in EXROI) in route data. If the device type is TCIA the SI value is interpreted as EOS code. For other device types the SI parameter might trigger other actions (see Application Information of the route owning blocks of type OT or BT).

2.4 Continuation of Call Set-up to Final Destination

2.4.1 Deleting of Announcement Code in B-Number

To delete the possibly inserted announcement code digits in the B-number the SI . EOS code, returned when the announcement call leg is released, can be used. The EOS analysis should also define the BO where the B-number analysis is continued from the first digit on.

It is important that a different origin from the first B-number analysis, leading to the announcement is used to analyze the number because otherwise the call might end up in a loop.

As a second alternative a possibly included announcement code in the B-number can be also deleted by adapting the sending program in route analysis in the RC to the final destination (for example, if five digits to specify the announcement code are inserted in the B-number the sending program shall be adapted that the number is sent from the sixth digit on).

2.4.2 Continuation of Call Set-up with Next Route Alternative

When a routing program to the announcement is set up the SI-EOS is configured to .select next route alternative. (NXR result).

EOS Analy

sis

TCIA Route, SI

Route Analysis

RC

EOS= SI

Announce

ment Open USER GUIDE 7 (12) Prepared (also subject responsible if other)

No.

EED/P/TG M.Geisen 1/1553-C/APT 210 26/3 Uen Approved Checke

d Date Rev Reference

EED/P/TC (N. Floeren) - 2004-01-11 A

2.4.3 B-Number Analysis Configuration

If the announcement code is specified in the called party number the B-number analysis can be the central control point of the function. The analysis has to be set up in such a way that a B-number which includes the announcement code leads to an RC which lead to a route of device type TCIA (for the announcement). If the B-number does not include an announcement code the RC should lead to the final destination of the call. It is proposed to keep both kinds of B-number separately in the analysis table in different BOs.

Figure 4: RC configuration in B-number analysis and Route analysis.

2.4.4 Route Analysis Configuration

If the announcement code is defined in route data of device type TCIA the route analysis can be set up as the central control point of the function. Therefore, a routing program has to be set up that the route of device type TCIA is always selected before the route to final destination.

When the .select next route alternative result (NXR). is received from EOS analysis within routing program a reference to a new RC is found. In the referenced RC the route or another routing program with different alternatives are defined to the final destination of the call.

Figure 5: Routing Program configuration in Route analysis

Final destinati

on

ANNC+B-number, BO= .x.

B-number, BO= .y.

RC

Route to final de

stination

B-number Analysis

RC (TCIA)

TCIA-Route

Route

Analysis

Announcement

2. Route to final destination

1. TCIA

Route

RC

B-number, BO

B-number Analysis

Announcement

Final destination

Route Analysis (NXR) Open USER GUIDE

8 (12) Prepared (also subject responsible if other) No.

EED/P/TG M.Geisen

1/1553-C/APT 210 26/3 Uen Approved Checked Date Rev Reference

EED/P/T

C (N. Floeren) - 2004-01-11 A

2.5 Examples

2.5.1 Example 1: Immediate Announcement For Changed Service Hotline

The operator offers to all its subscribers a service hotline that can be reached with the B-number 1234 for free. This behavior shall be changed. The service hotline shall cost 50 cent per minute for pre - subscribers and for subscribers with a contract (post-paid) the current behavior is kept. All pre . subscribers shall be informed about this change in the network, therefore, an immediate announcement shall be played.

The B-number analysis for pre-paid subscribers and post-paid is kept separately (different BOs are used, the BO 5 is used for pre-paid).

The figure below shows the involved traffic analysis functions.

Figure 9: Overview example1 immediate announcement for changed

service hotline

Step 1: Definition of EOS codes

The EOS analysis is configured in such a way that the announcement code (00002) is added to the B-number when the EOS code 502 is received (2.). In this EOS case the B-Number analysis after the modification is continued in BO 6 from the first digit on (3.). ANESI:ES=502, M=0-00002, F=6; To delete the announcement code from the B-number after the announcement is finished the EOS code 501 is used. After the announcement code is deleted and the B-number analysis is continued in the BO 7 from the first digit on (7.).

ANESI:ES=501, M=5, F=7;

Final destination Service hotline

1.

1234, BO=5

8. RC = 11

9. R=HOTLINE

2.

B-number Analysis

Route Analysis

4. RC = 10

5. R=ANNC02, DETY=TCIA

EOS=502

7.

1234, BO=7

3. 000021234, BO=6

EOS Analysis

Announcement

6.EOS= 501Open USER GUIDE 9 (12) Prepared (also subject responsible if o

ther) No.

EED/P/TG M.Geisen 1/1553-C/APT 210 26/3 Uen Approved

Checked Date Rev Reference

EED/P/TC (N. Floeren) - 2004-01-11 A

Step 2: Definition of TCIA-Route (5.) First a route with device type (DETY) TCIA has to be defined.

EXROI:R= ANNC02, DETY=TCIA;

In the route data the Register Signaling Variant (RSV) has to be changed. The RSV.X is set to .0. (immediate release is sent), the RSV.Y set to .1. (no B-answer), the RSV.Z is set to 16 (set-up speech condition) and the RSV.W is set to.1. (early ACM).

EXRBC: R= ANNC02, RSV=12292; Finally, after the route data is set up the ANNC02 route has to be de-blocked.

BLORE: R= ANNC02;

Note, the announcement code has to be connected to the announcement route, see Operational Instruction .Traffic Control, Announcement Interface Route, Define. for further information.

Step 3: Definition of Route Analysis For the service hotline the operator has already defined the RC 11 leading to the route .HOTLINE. in route analysis (9.). To play the intermediate announcement the new RC 10 is specified (5.). As route analysis data the SI value 501 is specified (returned as EOS code at release after the announcement is finished). ANRSI: RC=10, R=ANNC02, SI=501, SP=MM1; Step 4: Definition of B-Number Analysis

The B-number analysis in BO 5 on the B-number series 1234 results in EOS code 502 (1.).

ANBSI:B=5-1234, ES=502;

The EOS analysis adds the announcement code and orders to continue a B-Number analysis in BO 6 from the first digit on (2. and 3.). In BO 6 the added announcement code (00002) is analyzed and RC 10 is found leading to announcement 00002 (4.). ANBSI:B=6-00002, RC= 10;

After the announcement is finished the EOS code 501 is analyzed (6.) and the B-number analysis is continued in BO7 (7.). There the original dialed number (1234) is analyzed leading to RC 11 to the final destination (8.). ANBSI:B=7-1234, RC=11;




2.5.2 Example 2: Immediate Announcement When Carrier Is Dialed

The operator offers to its subscribers different carriers for calls to the PSTN network. The subscriber can select the preferred carrier by dialing a prefix before the B-number. Before the call is routed to the carrier the subscriber hears a spoken message that informs the subscriber about the tariff. The figure below shows the involved traffic analysis functions.

Figure 8: Overview example 2 immediate announcement when carrier is dialed

Step 1: Definition of TCIA-Route (2.)

First a route with device type (DETY) TCIA has to be defined.

EXROI: R= ANNC05, DETY=TCIA;

In the route data the Register Signaling Variant (RSV) has to be changed. The RSV.X is set to .0. (immediate release is sent), the RSV.Y set to .1. (no B-answer), the RSV.Z is set to 16 (set-up speech condition) and the RSV.W is set to.1. (early ACM).

EXRBC: R= ANNC05, RSV=12292; Finally, after the route data is set up the ANNC05 route has to be de-blocked.

BLORE: R= ANNC05;

Note, the announcement code has to be connected to the announcement route see Operational Instruction .Traffic Control, Announcement Interface Route, Define. for further information.

Step 2: Definition of Route Analysis

For the calls to carrier .XYZ. with immediate announcement the RC 5 is received from the carrier analysis. A routing program is set up as follows for this RC (1.):

An

nouncement

Final destination to carrier

Carrier Analysi

s

Route Analysis

5. R=XYZ

1. RC=5

2. R=ANNC05, DETY=TCIA

4. NXR

3. EOS= 500

EOS Analysis Open USER GUIDE 11 (12)

Prepared (also subject responsible if other) No.

EED/P/TG M.Geisen 1/1553-C

/APT 210 26/3 Uen Approved Checked Date Rev Reference

EED/P/TC (N. Fl

oeren) - 2004-01-11 A

ANRPI: RC=5; ANRSI: P01=1, R=ANNC1, SP=MM1, SI=500; ANRSI: P01=2, NRC=6; ANRPE;

To the carrier .XYZ. the operator has already defined the route .XYZ. (5.). The RC 6 is already leading to the route .XYZ.. Therefore, a reference routing case is given in the routing program to the RC 6 when the next route alternative result is received from EOS analysis (4.).

Step 3: Definition of EOS codes (4.) The EOS analysis is configured that the .next route alternative. is selected when the EOS code 500 is received. In this case the routing program will find the reference RC 6. In RC 6 the route to the final destination will be selected and the call routed to the carrier .XYZ..

ANESI:ES=500, NXR;

3 Configuration

-

4 References

Application Information: Traffic Control Interface towards ANS and IM Changeable Exchange Adaptation

Adaptation Directions: Traffic Data: Traffic Control, Announcement Interface Routes Traffic Data: Route Characteristics Traffic Data: End of Selection Analysis Traffic Data: Route Analysis Traffic Data: B-number Analysis

Operational Instructions: Traffic Control, Announcement Interface Route, Define Traffic Control, Announcement Interface Route, Change Traffic Control, Announcement Interface Route, Delete Traffic Control, Announcement Interface Route, Test Route Analysis Data, Change B-Number Analysis Data, Change End of Selection Analysis Data, Change




Command Descriptions: Analysis Of B-Number Specification, Initiate (ANBSI) Analysis Of End-of-Selection Case, Specification, Initiate (ANESI) Analysis Of Route Case, Specification, Initiate (ANRSI) Exchange Data, Specification of Route Data, Initiate (EXROI) Exchange Data, Specification of Route Data, Change (EXRBC) Blocking of Route, End (BLORE)

Annoucement Play

Documents

Transcript of Annoucement Play