Announcement

Announcements

DN985153Issue 9-0 en

# Nokia Siemens Networks 1 (59)

MSCDOCM14PDFCDMSC/HLR, Rel. M14.0, Product Documentation,v.3

The information in this document is subject to change without notice and describes only theproduct defined in the introduction of this documentation. This documentation is intended for theuse of Nokia Siemens Networks customers only for the purposes of the agreement under whichthe document is submitted, and no part of it may be used, reproduced, modified or transmitted inany form or means without the prior written permission of Nokia Siemens Networks. Thedocumentation has been prepared to be used by professional and properly trained personnel,and the customer assumes full responsibility when using it. Nokia Siemens Networks welcomescustomer comments as part of the process of continuous development and improvement of thedocumentation.

The information or statements given in this documentation concerning the suitability, capacity, orperformance of the mentioned hardware or software products are given “as is” and all liabilityarising in connection with such hardware or software products shall be defined conclusively andfinally in a separate agreement between Nokia Siemens Networks and the customer. However,Nokia Siemens Networks has made all reasonable efforts to ensure that the instructionscontained in the document are adequate and free of material errors and omissions. NokiaSiemens Networks will, if deemed necessary by Nokia Siemens Networks, explain issues whichmay not be covered by the document.

Nokia Siemens Networks will correct errors in this documentation as soon as possible. IN NOEVENT WILL NOKIA SIEMENS NETWORKS BE LIABLE FOR ERRORS IN THISDOCUMENTATION OR FOR ANY DAMAGES, INCLUDING BUT NOT LIMITED TO SPECIAL,DIRECT, INDIRECT, INCIDENTAL OR CONSEQUENTIAL OR ANY LOSSES, SUCH AS BUTNOT LIMITED TO LOSS OF PROFIT, REVENUE, BUSINESS INTERRUPTION, BUSINESSOPPORTUNITY OR DATA, THAT MAYARISE FROM THE USE OF THIS DOCUMENT OR THEINFORMATION IN IT.

This documentation and the product it describes are considered protected by copyrights andother intellectual property rights according to the applicable laws.

The wave logo is a trademark of Nokia Siemens Networks Oy. Nokia is a registered trademark ofNokia Corporation. Siemens is a registered trademark of Siemens AG.

Other product names mentioned in this document may be trademarks of their respective owners,and they are mentioned for identification purposes only.

Copyright © Nokia Siemens Networks 2008. All rights reserved.

2 (59) # Nokia Siemens Networks DN985153Issue 9-0 en

Announcements

Contents

Contents 3

List of tables 5

List of figures 6

Summary of changes 7

1 Introduction to announcements 91.1 Types of announcements 91.1.1 Voice announcements 101.1.2 Text announcements 101.1.3 Fixed and variable-content announcements 111.1.4 Synchronised and non-synchronised announcements 111.1.5 Intelligent network announcements 111.1.6 Phased announcements 121.1.7 Multilingual announcements 131.1.8 Test announcements 131.1.9 Facility control announcements 131.1.10 Announcement backups 141.2 Announcements analyses 141.2.1 Announcement identifier 151.2.2 Announcement analysis tree 171.3 Announcement devices 181.4 Speech sample and language structure files 191.5 IN Announcements 231.5.1 Chargeable and free announcements 231.5.2 Announcements from External Specialised Resource Point (External

SRP) 241.5.3 Interaction with MSC announcements 251.5.4 Additional information on IN announcements 25

2 Creating announcement devices 272.1 Creating internal announcement device 272.2 Installing VANG, VANG-S, VANG-U or VANG-A/B in active network

element 30

3 Creating announcements 35

4 Modifying announcements 494.1 Loading modified speech sample files 494.2 Updating language structure files 504.3 Restoring old speech sample files 504.4 Modifying general announcement parameters 504.5 Modifying announcements 514.6 Modifying an announcement analysis 52

5 Deleting announcements 53



Contents

6 Announcements troubleshooting 55

7 Additional information on VANG plug-in units 59


Announcements

List of tables

Table 1. Announcement identifier 16

Table 2. Announcement cases 16

Table 3. Numbering and contents of VAD files 19

Table 4. Identifiers of VAD element groups 21

Table 5. Language identifiers of VAD files per plug-in unit 22

Table 6. VANG and VANG-S PCM connectors 28

Table 7. VANG-A/VANG-B equipping 59



List of tables

List of figures

Figure 1. Direct call to announcement service 15

Figure 2. Structure of announcement analysis tree 17

Figure 3. Internal announcement device 18


Announcements

Summary of changes

Changes between document issues are cumulative. Therefore, the latestdocument issue contains all changes made to previous issues.

Changes made between 9-0 and 8-0

Section Introduction to announcements

. Facility control announcement has been added.

Section Additional information on VANG plug-in units

. Information on subrack network elements has been removed as theyare no longer supported.

Changes made between issues 8-0 and 7-0

Throughout the document: 'external IP has been replaced with 'SRP'

Section Introduction to announcements

. Subsection IN Announcements has been added.

. Announcement case 'intelligent network announcement when thetone is played by SCP with PA or PC' has been added.

Section Creating announcements

. The command syntax has been changed for Step Activate theannouncement (RAM).

. The command syntax has been changed for Example Movingannouncement from a spare channel to another SPR.

. The information relevant for the called number and its analysis hasbeen removed from Example Creating intelligent networkannouncement in three languages.



Summary of changes

Section Announcements troubleshooting

. Clear code 0B2D INTELLIGENT NETWORK APPLICATIONRESPONSE has been corrected to 0B2D INTELLIGENTNETWORK APPLICATION RESPONSE TIME-OUT.

. Corrective action for the occurence of Alarm 2194 has been added.

. The section has been updated with Core INAP and CAMELinformation.

Changes made between issues 7-0 and 6-1

Section Creating external announcement device has been removed.

All references to external devices have been removed throughout thedocument.


Announcements

1 Introduction to announcements

In the following section, you can find the description of the different typesof announcements and announcement devices.

Note

. All announcement features (for example, the use of textannouncements) are customer-specific.

. Only partial syntax descriptions of the relevant MML commands aregiven here. Since the same commands are not used in all networkelements, the commands presented here are merely examples.More detailed information about the individual commands can befound in the MML-specific command descriptions, which containcomplete MML-specific syntax descriptions and parameterexplanations.

For information on the announcements functionalities, announcementstypes, speech sample and language structure files of Multimedia Gateway,and for the procedures for announcement file handling in MultimediaGateway, see Tones and Announcements in Multimedia Gateway,Functional Description, and Multimedia Gateway for MSC Server,Functional Description in Nokia Multimedia Gateway documentation.

1.1 Types of announcements

The two main types of announcements are the following:

. direct (or 'diallable') announcement

. intermediate announcement



Introduction to announcements

A direct announcement is given when the subscriber calls a specificannouncement service number, for example, time service. Intermediateannouncements, however, are given in special cases of call control, forexample, when the call set-up is interrupted because the called subscriberdoes not answer, and the calling subscriber must be informed that the callcannot be connected.

Announcements can be given in the form of written or spoken text, in oneor more languages. Depending on what announcement device is used,voice announcements can also be phased or synchronised.

1.1.1 Voice announcements

A voice announcement can consist of a maximum of three phases: pre-announcement, main announcement, and post-announcement.

All the phases can be given from the internal announcement device, but aphase can also be in the form of a tone from the tone generator. Only themain announcement is obligatory. The length of the announcementphases is defined in the general announcement parameters. Each phaseconsists of a maximum of 62 speech sample files.

1.1.2 Text announcements

Text announcements (also called 'notifications') are fixed-contentannouncements that can be shown in the display of an ISDN terminal (forexample, a PBX terminal). A text announcement can be used as anindependent announcement, or it can be added to a voice announcement.An independent text announcement requires its own special route andannouncement analysis, meanwhile, the additional text announcementsare created to the same special route as the voice announcement to whichthey are connected, and the analyses are created for the voiceannouncement only.

The text announcement cannot be a direct announcement, only anotification.


Announcements

1.1.3 Fixed and variable-content announcements

The content of an announcement given from the internal announcementdevice can be either fixed or variable. Fixed-content announcements arestandard announcements given to all subscribers (for example, 'Thank youfor your call'), whereas variable-content announcements include customer-specific information, which varies according to the given situation. Variableparts can be used in Intelligent Network (IN) announcements and in facilitycontrol announcements.

1.1.4 Synchronised and non-synchronised announcements

If an announcement is synchronised with the beginning, it always startsfrom the beginning when it is connected to a new call. An announcementcan be synchronised with the beginning if it is given from the internalannouncement device and allocated on demand.

In non-synchronised announcements, the subscriber can be connected tothe middle of an announcement. An announcement cannot besynchronised with the beginning in the following cases:

. it is given from the internal announcement device and its allocationmode is 'fixed'

. it is the pre- or post-announcement of an announcement

. it is given from the tone generator

1.1.5 Intelligent network announcements

Intelligent network announcements can be played from both internalannouncement device: Verbal Announcement Generator (VANG) andexternal announcement device: Specialised Resource Point (SRP). Theinternal device announcements are created, modified, and deleted asspecified in the Integrated Announcing Equipment feature. Theannouncement identifier, brought to the announcement analysis, consistsof a language code, the announcement case number, and anannouncement specifier provided by the Service Control Point (SCP). Theannouncement index obtained from the analyses is sent to the ServiceSwitching Point (SSP) by the SCP, and the SSP starts the announcement.

Intelligent network announcements allow the use of variable-content parts.

For the detailed description, see Section 1.5 IN announcements.




The external device announcements are handled according to theinterface specifications for MSC/SSP-SCP Camel Application Part (CAP)and for MSC/SSP/IP - SCP.

1.1.6 Phased announcements

Phasing announcements means that the same announcement is givenfrom several channels, starting at different times. It reduces the time thesubscriber has to wait before the announcement starts.

Internal announcement device

An announcement given from the internal announcement device can bephased, in the following cases:

. the number of announcement listening times is limited. The numberof listening times is defined in the LCL general announcementparameter, when creating the announcement.

. the number of channels in use exceeds the value defined in theANN_PHASE_PERCENTAGE (000:0012) PRFILE parameter. Thedefault value is 50, which means that phasing is started when 50%of the announcement channels have been reserved.

Note

For the optimisation of channel capacity, the recommended value of theANN_PHASE_PERCENTAGE (000:0012) PRFILE parameter is 25%.

. the length of any of the announcement listening times exceeds thelimit defined in the ANN_PHASE_TIME (000:0011) PRFILEparameter. The parameter indicates the time after which theannouncement starts from the beginning on another channel, that is,it tells how long the subscriber has to wait to hear theannouncement. If the announcement is shorter than the definedvalue in the ANN_PHASE_TIME (000:0011) PRFILE parameter,the announcement is not phased. In this case, the call is onlyconnected to the announcement when the announcement startsfrom the beginning again. The default value is 5 seconds.

For example, if an announcement lasts for 11-15 seconds, and thevalue of the ANN_PHASE_TIME (000:0011) PRFILE parameter is5 seconds, the announcement must be given from three differentchannels in three phases so that the waiting time is not exceeded.


Announcements

1.1.7 Multilingual announcements

Multilingual announcements are used when the same announcement mustbe repeated in several languages. The announcement is created byrecording the same text in different languages (every language variant isrecorded in its own speech sample file), and by listing the speech samplefiles in the command, which is used to create the announcement.

In intelligent network announcements, a non-default announcementlanguage can be defined in the language identifier. Every language variantrequires its own special route.

For more information on setting the language of the announcement, seeExample Creating intelligent network announcement in three languages.

1.1.8 Test announcements

By using test announcements, the VANG supervision program tests thecircuits connected to the VANG plug-in unit. Test announcement is createdin the same way as an ordinary voice announcement, except that while theannouncement identifier of an ordinary announcement consists of 5 digitswhich can vary from one announcement case to another, the identifier of atest announcement is always 012.

1.1.9 Facility control announcements

The operator can configure announcements in the Nokia Voice over IP(VoIP) Server for supplementary services. For example, an announcementcan be made for call hold activation status or for forwarded-to number incase of call forwarding.

Facility control announcements allow the use of variable-content parts.

For more information, see Feature 1741: Control of SupplementaryServices in NVS, Feature Description.




1.1.10 Announcement backups

If an announcement is created with two announcement channels, channel1 automatically functions as the primary announcement channel, whilechannel 2 remains a spare channel, which is used when the primarychannel fails. The system recognises channel 2 as a spare channel whenthe two announcement channels are on different PCM circuits. If thechannels are on the same Pulse Code Modulation PCM circuit, theannouncement is phased.

A more efficient way of backing up announcements is to create analternative routing for the announcement service. Alternative routingenables the distribution of traffic load between two or more routingalternatives, which helps to ensure uninterrupted operation also underheavy traffic.

For more information on creating alternative routing, see ExampleCreating alternative routing for the announcement service in SectionCreating announcements.

1.2 Announcements analyses

Announcements can be given as a result of several call control analyses:charging and routing analysis, End Of Selection analyses (EOS analyses),EOS attribute analyses, routing attribute analysis, call barring analysis,and function analysis. If the result of a call control analysis indicates thatan announcement must be given, the call control software forms anannouncement identifier that is analysed in the announcement analysis.On the basis of the data obtained from the announcement analysis, theannouncement service starts the announcement.

The following figure shows how a direct call to announcements isanalysed.


Announcements

Figure 1. Direct call to announcement service

1. Call control makes an analysis of the received digits in an analysistree defined for the incoming call. If the result of the analysis isannouncement specifier, call control knows that the call must beconnected to an announcement.

2. To the announcement specifier, the call control adds a languageidentifier and an announcement case number. The result is anannouncement identifier.

3. Call control sends the announcement identifier to the announcementserver, and asks it to make an announcement analysis.

4. The announcement server brings the announcement identifier to anannouncement analysis tree in the Central Memory (CM).

5. The announcement analysis produces the data on the basis of whichthe announcement is started. If the announcement device used is aninternal announcement device, the result of the announcementanalysis is an announcement index.

1.2.1 Announcement identifier

Call control requests the announcements from the announcement serveron the basis of the announcement identifiers. An announcement identifierconsists of a language identifier, an announcement case, and anannouncement specifier. See the following example:

1. NUMBER TOBE ANALYSED

ANNOUNCEMENTSERVER

5. ANNOUNCEMENT DATA

CENTRALMEMORY

4. ANNOUNCEMENTIDENTIFIER

3. ANNOUNCEMENT IDENTIFIER

2. ANNOUNCEMENTSPECIFIER

ANNOUNCEMENTDEVICE

CALLCONTROL




Table 1. Announcement identifier

0 3 507

language announcement announcement

identifier case specifier

Language identifier

The language identifier specifies the language in which the announcementis given. The number of supported languages depends on what kind ofVerbal Announcement Generator (VANG) Plug-in Unit (PIU) the networkelement has:

. If the PIU is VANG or VANG-S, the language identifier can bebetween 0 and 4.

. if the PIU is VANG-A, VANG-B or VANG-U, the language identifiercan be between 0 and F. (For more information, see Section Speechsample and language structure files.)

Language identifier 0 denotes the default language of the country inwhich the network element is located.

In IN announcements, the language identifier is provided by the SignalControl Point (SCP).

Announcement case

The announcement case describes the call phase or the situation in whichthe announcement is given. The announcement case can be:

Table 2. Announcement cases

Ann. case number Announcement case

0 direct call to announcement

3 intermediate announcement

6 facility control

9 intelligent network announcement (normalvoice announcement)

C intelligent network announcement (toneannouncement)

E text announcement


Announcements

Announcement specifier

Announcement specifier is used to distinguish announcements of thesame announcement case from each other. Call control obtains theannouncement specifier as a result of the call control analysis. Inannouncements created by the operator, the specifier is a three-digitnumber between 100 and 799. The specifiers can be selected freely, but itis advisable to use systematic numbering. Call control has fixedannouncement specifiers for certain features; use them to ensure that thefeatures function properly. Fixed announcements are marked withspecifiers 001 - 099 and 800 - 999. You can freely define the content of theannouncement itself.

In IN announcements, the announcement specifier is provided by the SCP.

1.2.2 Announcement analysis tree

The announcement analysis is created to an announcement analysis tree,which is hierarchically divided into three logical levels according tolanguage, announcement case, and announcement specifier, aspresented in the following figure.

Figure 2. Structure of announcement analysis tree

The value of the analysis tree is defined in the ANN_ANAL_TREE(000:0009) PRFILE parameter. The default value is 48.

48

0

1 ... n LANGUAGE0

3 9 E

001... ... 999 ANNOUNCEMENT SPECIFIER

ANNOUNCEMENTCASE

C




1.3 Announcement devices

Announcements can be given from an internal announcement device(VANG), or a tone generator.

A tone generator is a standard part of the DX 200 network element,meaning that it does not need to be brought into use separately. Thequality of the tones can be defined according to the customer'srequirements: some of the tone generators are programmable, others areusually provided with Programmable Read-only Memories (PROMs)specially programmed for the customer. Information on tone definition of apre-programmed PROM is delivered to the customer with the PROM.

The software for an internal announcement device consists of a specialroute file (located in the CM), an announcement parameter file (in the CM,signalling unit and Marker Unit (M)), an announcement file (in the CM andM), an announcement text file (in the CM and on the OMU disk), anannouncement speech sample file with a control file for dynamic elements(on the OMU disk), and a control file of speech sample files (in the CM andM).

The actual announcement device incorporates a VANG plug-in unit, whichcan be located either in the Marker, the Common Channel SignallingManagement Unit (CCMU), the Central Memory, or (in Compact MSCi) inthe Central Memory and Marker (CMM). A cartridge-construction MSCican be equipped with 1-3 VANGs of the VANG-A/B type.

Figure 3. Internal announcement device

The Voice Announcement Recording System (VARS) equipment, by whichthe announcements of an internal announcement device are recorded,consists of a standard microcomputer, a voice-handling software and aplug-in unit with an analogue and digital connection.

OMU = Operation &Maintenance Unit

M/CM/CMM/CCM VANG

VARS

2 X MB


Announcements

The texts used in text announcements are located in their own file in theCM.

1.4 Speech sample and language structure files

Voice announcements given from the internal announcement device arerecorded by the VARS equipment. Every speech sample and languagestructure is recorded in its own file. The recorded files are transferred tothe network element, and loaded to the sample memory of the VANG plug-in unit, from which the Voice Announcement Service Program Block(VANSER) selects the required files when an announcement is requested.

You need to record the variable-content speech sample files beforebuilding the language structure files.

VAT files

The VAT files ('fixed-content speech sample files') consist of data that canbe used as a common part in several announcements. The files are storedto the network element as VAT0nnnn.IMG files, the 'nnnn' denoting a freelyselectable integer in the range of 0001 - 3999.

VAD files

The VAD files ('variable-content speech sample files') consist of data thatvaries according to the customer or the situation. They can be used only inintelligent-network announcements. One announcement can contain amaximum of 5 variable parts. The files are stored to the network elementas VAD0nnnn.IMG files. The following table shows the numbering andcontents of the files.

Table 3. Numbering and contents of VAD files

Number of VAD file Identifier of

element group

Contents of sample file

VAD00001/

VAD01001

V1, V2, V3,

V4, V5, V6

silence

VAD00002/

VAD01002

V0 test announcement

VAD00003-

VAD00005

Vx special words such as 'and','year', 'day' and so on




Table 3. Numbering and contents of VAD files (cont.)

Number of VAD file Identifier of

element group

Contents of sample file

VAD00006-

VAD00015

V1, V2, V3,

V4, V5, V6

numbers 0-9

VAD00016-

VADxxxxx

V2, V3, V4,

V5, V6

numbers 10-59

VADxxxxx-

VADxxxxx

V2, V3,

V5, V6

numbers 60-99

VADxxxxx-

VADxxxxx

V2, V3,

V5, V6

'hundred', 'hundred', 'thousand','thousand', 'million', 'million','billion', 'billion'

Please, see the note below forthe singular and plural samplesof these numbers.

VADxxxxx-

VADxxxxx

V3, V4 'second', seconds', 'minute','minutes', 'hour', 'hours'

VADxxxxx-

VADxxxxx

V2 'pound', 'pounds', 'penny', 'pence'(local currency)

VADxxxxx-

VADxxxxx

Vx ordinal numbers for date and/orfor some other use

VADxxxxx-

VADxxxxx

V5 months

VADxxxxx-

VAD00199

Vx masculine and feminine forms ofsome numbers or words forsome other special use

Note

This file contains the speech samples for the singular and plural formsof 'hundred', 'thousand', 'million', and 'billion'. Since these numbers donot have plural forms in English, the singular forms are given both forthe singular and the plural speech samples.


Announcements

The first two sets of files listed in the table (VAD00001/VAD01001 andVAD00002/VAD01002) are obligatory speech sample files, of whichVAD00001.IMG and VAD00002.IMG are used with VANG and VANG-S,VAD01001.IMG and VAD01002.IMG with VANG-A, VANG-B and VANG-U.The files have predefined contents that are configured separately for everynew software build, and they cannot be modified.

If VAD files are needed in an announcement, the VANSER program blockloads all the speech sample files of one sample group ('element group')into the memory of the VANG plug-in unit when the unit is started or whenthe announcement is created. All the speech sample files of the elementgroup must be available so that the announcement can be given. Thefollowing table shows the identifiers of the element groups.

Table 4. Identifiers of VAD element groups

Identifier Meaning

V0 test announcement

V1 subscriber number announcement

V2 charge announcement

V3 call duration announcement

V4 time announcement

V5 date announcement

V6 number announcement

. Subscriber number announcement (V1)

A subscriber number announcement provides information on thesubscriber phone numbers. The phone numbers are enumerateddigit by digit, in groups of two or three digits, each group followed bya 500 millisecond pause (in VANG and VANG-S), or a 125millisecond pause (in VANG-U, VANG-A and VANG-B). Each partcontains a maximum of 24 phone numbers.

. Charge announcement (V2)

A charge announcement is given in the following form: <fixedbeginning> + 'two thousand three hundred and fifty-two pounds andforty-two pence' + <fixed end>. Each word in the quotation markscorresponds to one speech sample file. The biggest number that canbe announced is over 4 billion.

. Call duration announcement (V3)




A call duration announcement is given in the following form: <fixedbeginning, for example 'Your call lasted for'> + 'five hours threeminutes and fifty-two seconds'. Hours, minutes and seconds, can allbe given.

. Time announcement (V4)

A time announcement is given in the following form: <fixedbeginning, for example 'The time is'> + 'nine forty-five'. Seconds canalso be given, if necessary.

. Date announcement (V5)

A date announcement is given in the following form: <fixedbeginning, for example 'Today is'> + 'January the 1st, nineteenninety-seven'.

. Number announcement (V6)

A number announcement is given as integers, for example 'Twenty-three'. The biggest number that can be announced is over 4 billion.

VAD files also have fixed, plug-in unit dependent language identifiers,which are listed in the following table.

Table 5. Language identifiers of VAD files per plug-in unit

VANG plug-in unit Language

identifier

Number of VAD file

VANG, VANG-S: 0 VAD00003-VAD00199

1 VAD00203-VAD00399

2 VAD00403-VAD00599

3 VAD00603-VAD00799

4 VAD00803-VAD00999

VANG-A, VANG-B,VANG-U:

5 VAD01003-VAD01199

... ...

F VAD03003-VAD03199


Announcements

VAL files

The VAL files ('language structure files') are built by the operator or byNokia by using the VARS equipment. VAL files are used by the VANSER toconstruct the variable parts of the announcements. The files contain thelanguage-specific structure for each language identifier used in thenetwork element. The language structures are made by filling thelanguage structure files for each language individually. The files are storedto the network element as VAXLnnGX.IMG files, the 'nn' denoting aninteger between 00 and 15, which is the language identifier. For example,the default language is 0, and the file is stored as VAXL00GX.IMG to thenetwork element. Different plug-in units use different VAL files: the filenumbers from VAXL00 to VAXL04 are used in the VANG and VANG-Splug-in units, and the file numbers from VAXL00 to VAXL15 are used in theVANG-A/B and VANG-U plug-in units. The file numbers always remain thesame.

By default, the language structure files are initialised to support theexisting variable-content announcement structure. If the announcementsalready function correctly in some language, there is no need to changethe speech sample or language structure files. While the VANSER loadsthe speech sample files for the variable-content announcements, it checkswhich languages (0-F) are defined in the network element and whichspeech sample files are included in particular element groups.

When generating the variable-content announcements, the VANSERselects the correct language structure file by using the language identifierdefined in the announcement request.

1.5 IN Announcements

The SCP is able to control the use of the internal or externalannouncement device. The same announcement device is used both incall-gapping and in normal MSC announcements.

1.5.1 Chargeable and free announcements

In GSM networks, the MSC generates charging records which contain thenecessary billing information. These charging records are transmitted tothe billing centre for post-processing. Core Intelligent Network ApplicationProtocol (CoreINAP) does not change these charging principles.




In the MSC/SSP, CoreINAP announcements are charged by default, butthey can also be configured to be free. The SCP is able to set a specialcharge rate for CoreINAP announcements, and can also set these to befree.

From the MSC/SSP point of view, Customised Applications for MobileNetwork Enhanced Logic (CAMEL) announcements are always free. Inthis case, charging is handled by the SCP on the basis of, for example, thecall periods that are consumed inside the MSC/SSP.

For more information on the generation and the content of CDRs indifferent call cases, see MSC/SSP-SCP Camel Application Part (CAP),Interface Specification and Generation and Contents of CDRs in DifferentCall Cases, Interface Specification.

PRFILE for free announcement calls

You can use the ANSWER_FROM_FREE_ANN (002:0732) PRFILEparameter to determine whether the answer message is sent in the freeannouncement calls. It can have the following values:

. 0D: Answer message is sent in the free announcement call, but thecall is compiled to statistics as unsuccessful.

. 1D: Answer message is not sent in the free announcement calls.

. 2D: Answer message is sent in the free announcement calls.

1.5.2 Announcements from External Specialised Resource Point (ExternalSRP)

The SRP assists the SSP in end-user interaction. The SRP functionalityincludes, for example, giving announcements (in different languages) andcollecting Dual-tone Multifrequency (DTMF) dialling. It is possible toconnect an external SRP to the basic MSC/SSP platform, and thusconcentrate the SRP functions to a single point. The external SRPcomplements the integrated internal announcement device (VANG) in theMSC/SSP.

IN announcements, given from the internal announcement device, consistof fixed-content parts and variable-content parts. These announcementsare called variable-content announcements. Other announcements can begiven with other announcement devices supported by the MSC. The SCPis able to control the use of the internal or external announcement device.The same announcement device is used both in call gapping and normalMSC announcements.


Announcements

The external SRP is connected to the SSP directly or through the network.The Core INAP protocol is used between the SCP and the external SRP.The ISDN User Part (ISUP) protocol is used between the SSP and theSRP. For the MSC/SSP-IP communication, feature ISUP Interface toExternal IP is needed in the MSC/SSP. For more information, see Feature743: ISUP Interface to External IP, Feature Description.

The Core INAP or CAMEL protocol is used between the SCP and theexternal SRP.

1.5.3 Interaction with MSC announcements

It is possible to configure meeting a Basic Call State Model (BCSM)Detection Point (DP) and playing a tone or an announcement to the EOSanalysis. If the EOS analysis result is both IN DP and announcement, thefunctionality in Originating BCSM is that DP is met and reported to theSCP, and the response is expected before the tone or the announcementis started.

1.5.4 Additional information on IN announcements

SuppressOfAnnouncement from Connect

It is possible to suppress announcement at the terminating MSC byreceiving Connect operation from SCP with suppressOfAnnouncementindicator. For more information, see MSC/SSP-SCP Camel ApplicationPart (CAP), Interface Specification.

Gapping announcements

When SCP overload control is active, the gapping announcements can beused. For more information, see Feature 739: Core INAP CS-1 v.3,Feature Activation Manual, Feature 1148 and 1159: CAMEL Phase 3,Feature Activation Manual, and for Features 1196 and 1197: CAMELPhase 4, Feature Activation Manual.





Announcements

2 Creating announcement devices

The instructions of creating announcement devices describe how to createan internal announcement device, how to install verbal AnnouncementGenerators (VANG), VANG-A/B in an active network element.

2.1 Creating internal announcement device

Before you start

Before creating an internal announcement device, consider the followingpoints:

. what type of plug-in unit is needed (VANG-A/B)

. how many plug-in units are needed

. how many free tracks and PCMs are available

. in what unit the plug-in units are installed (CM, M or CMM)

The type of the VANG plug-in unit and the unit to which VANG is createdmust be chosen according to the requirements of the network element.

. VANG-A/B

VANG-A/B uses dynamic addressing and it requires cabinet-cartridge hardware with PCI bus in the network element. VANG-B isa ROHS compliant plug-in unit, but otherwise, it is not different fromVANG-A.

The dynamic VANG-A/B base addressing is executed by the PCIbus interface. The memory base address and I/O base address aredefined when the PCI interface is configured. The plug-in unit data isstored to the DEVICE register in the PCI interface.



Creating announcement devices

The Central Memory and Marker (CMM) can house 1 VANG-A/Bplug-in unit, the Common Channel Signalling Management Unit(CCMU), and maximum 3 VANG-A/B plug-in units. In the CMM, thesame PCM circuits can be used both on the active and on the spareside. In the CCMU, different PCM circuits have to be used on bothsides.

The equipping of the plug-in units in the DX 200 network elements isdescribed in Section Additional information on VANG plug-in units. Formore detailed information, see the Equipment Lists delivered in the SiteDocuments binder.

Steps

1. Create an internal announcement device (WTP)

ZWTP:<unit type>,<unit index>:<plug—in unit type>,<plug-in unit index>,<track>::<function>,<PCMtype>,<PCM>,<timeslot type>,<TSLs>;

List in the command all the circuits through which the plug-in unit isconnected to the switching network.

2. Connect the VANG to the switching network (WUC)

ZWUC:<unit type>,<unit index>:<plug-in unit type>,<plug-in unit index>;

You can connect the plug-in unit to the switching network either at afront or a rear connector. The operating mode of the plug-in unit'sPCM connector is determined on the basis of the number of PCMcircuits reserved for the unit, as indicated in the following table.

Table 6. VANG and VANG-S PCM connectors

PCM mode Number of PCM circuits connected to plug-in unit

1 2 4

2 M rear connector front connector front connector

4 M rear connector rear connector front connector

Further information


Announcements

Example

Create a VANG plug-in unit to Marker 1 (M,1), track 9, and connect theannouncement device to the network element's switching network. ThePCM mode of the plug-in unit's is 4 M, and all the timeslots (TSL,0&&31)on PCM circuits 120 - 123 (4) are connected to the VANG.

1. ZWTP:M,1:VANG,1,9::GENERAL,4,120&&123,TSL,0&&31;

2. ZWUC:M,1:VANG,1;

Example

1. Create one VANG-A plug-in unit on track 3 with all the timeslots(TSL,0&&31) of the 16 PCM circuits (90&&105) in 4 M mode in theCMM

ZWTP:CMM,0:VANG_A,0,3::GENERAL,4,90&&105,TSL,0&&31;

2. Connect the VANG-A to the network element's switching network

ZWUC:CMM,0:VANG_A,0;

Example

1. Create one VANG-A on track 3 with all the timeslots (TSL,0&&31) ofthe 16 PCM circuits (70&&85) in 4 M mode in the CCM

ZWTP:CCM,0:VANG_A,0,3::GENERAL,4,70&&85,TSL,0&&31;

2. Connect the VANG-A to the network element's switching network

ZWUC:CCM,0:VANG_A,0;

For detailed syntax and parameter descriptions of these commands, seeEquipment Management, WT Command Group and Unit ConnectionsHandling, WU Command Group.

For more information, see Section Announcement devices.




2.2 Installing VANG, VANG-S, VANG-U or VANG-A/B inactive network element

Before you start

Before the plug-in unit is installed in the network element, consider thefollowing points:

. how many plug-in units are needed

. how many free tracks and PCMs are needed for the particular type ofthe plug-in unit

. check the cabling

For instructions on cabling and strappings, see Cabling Lists delivered inthe Site Documents binder, and Jumper Settings of the Plug-in Units.

Take the plug-in unit into use as instructed below; then restart the VoiceAnnouncement Service Program Block (VANSER).

Steps

1. Block the alarms (ABB)

Block the alarms 2055 VANG FAILURE, 2056 CHECKSUM ERRORIN VANG SAMPLE and 2626 VANG PCM-INTERFACE FAULTY:

ZABB:2055;

ZABB:2056;

ZABB:2626;

2. Force-activate WO-EX Marker

Force-activate WO-EX Marker by flicking the lowest MCU switch inboth OMUs.. Left: M0 active. Right: M1 active

3. Change the state of the spare side unit from SP-EX to SE-NH(USC)


Announcements

Change the state of the spare side unit (M,1) to which the VANG isconnected from SP-EX to SE-NH. In the following example, theVANG is connected to the Marker (M).

ZUSC:M,1:TE; (from SP-EX into TE-EX)

ZUSC:M,1:SE; (from TE-EX into SE-OU)

ZUSC:M,1:SE; (from SE-OU into SE-NH)

4. Check PCM activity in GSW1

If the PCMs have not been activated, activate them as instructed inthe following steps.

a. Switch the power off in PSC1 PIU of GSW1

b. Make the PCM activation wiring

5. Connect the PCM cables to GSW1

Connect the PCM cables to GSW1 and switch the power on inGSW1. For more information, see Site Documents.

6. Change the state of the marker M1 into TE-EX (USC)

Change the state of the marker M1 into TE-EX, and run GSWdiagnostics.

ZUSC:M,1:SE; (from SE-NH into SE-OU)

ZUSC:M,1:TE; (from SE-OU into TE-EX)

ZUDU:M,1;

7. Change the state of the M1 into SE-NH (USC)

ZUSC:M,1:SE; (from TE-EX into SE-OU)

ZUSC:M,1:SE; (from SE-OU into SE-NH)

8. Check the strappings of the VANG plug-in unit

For more information, see Site Documents.

9. Connect the VANG




10. Connect the PCM cable

Connect the PCM cable from the GSW to the VANG plug-in unit. Formore information, see Site Documents.

11. Add the VANG to the HW configuration of the M (WTP)

See the PCM numbers in Site Documents and the parameter valuesin Section Additional information on VANG plug-in units.

VANG, VANG-S: ZWTP:M,1:<VANG,VANG_S>,0,<track>:MS=________, ME=________,IS=____,IE=____,: GENERAL,4,<PCM1&&PCM4>,TSL,0&&31;

VANG-U: ZWTP:M,1:<VANG_U>,0,<track>:MS=________, ME=________,IS=____,IE=____,: GENERAL,4,<PCM1&&PCM16>,TSL,0&&31;

VANG-A, VANG-B:ZWTP:M,1:<VANG_A>,0,<track>::GENERAL,4,<PCM1&&PCM16>,TSL,0&&31;

12. Connect the VANG to the Functional Unit (M) (WUC)

ZWUC:M,1:<VANG,VANG_S,VANG_U,VANG_A>,0;

13. Change the spare side unit into the side transmitting traffic(USC, UDU)

Change the spare side unit into the side transmitting traffic, so thatthe traffic transmitting side becomes the spare side unit. Change thespare side unit's state first from SE-NH into TE-EX, and rundiagnostics for the VANG plug-in unit.

ZUSC:M,1:SE; (from SE-NH into SE-OU)

ZUSC:M,1:TE; (from SE-OU into TE-EX)

ZUDU:M,1:VANG::;

Note

If the PCMs have not been activated in the GSW0, the partialdiagnostics of VANG fails.


Announcements

14. Start VANSER on the active side (DDS, ODR)

Start VANSER on the active side (the side in the WO-EX state). TheODR starting command is given on the service terminal from thegiven unit.

a. Start a remote debugger session (DDS)

If you cannot make a direct service terminal connection, start aremote debugger session.

ZDDS:M,0;

b. Start VANSER with a service terminal command (ODR)

The family identifier of VANSER is 192.

ZODR:192;

c. Close the remote debugger session by command E.

15. Change the state of the M1 into SP-EX (USC)

ZUSC:M,1:SP; (from TE-EX into SP-EX)

If this was the first unit, continue from the Step Change the lowestMCU switch back into the middle position. If not, continue from theStep Change the state of the M0 into WO-EX (USC).

16. Change the lowest MCU switch back into the middle position

17. Change the state of the M1 into WO-EX (USC)

ZUSC:M,1:WO; (from SP-EX into WO-EX)

18. Repeat steps from Change the state of the spare side unit fromSP-EX to SE-NH (USC) to Change the state of the M1 into SP-EX(USC) for M0 and GSW0

19. Change the state of the M0 into WO-EX (USC)

ZUSC:M,0:WO; (from SP-EX into WO-EX)

20. Run diagnostics and update the equipment information if thepartial diagnostics of VANG has failed (UDU)

a. Change M1 into TE-EX and run diagnostics (UDU)

b. Change M1 into SP-EX

The equipment information is updated correctly.

21. Remove the blocking from the alarms (ABU)




Remove the blocking from the alarms 2055 VANG FAILURE, 2056CHECKSUM ERROR IN VANG SAMPLE, and 2626 VANG PCM-INTERFACE FAULTY.

ZABU:2055;

ZABU:2056;

ZABU:2626;

22. Create the announcements and analyses

Create the necessary announcements and analyses as instructed inSection Creating announcements.


Announcements

3 Creating announcements

Before creating announcements, plan all the following details carefully:

. the contents of the announcements

. speech sample files

. announcement indexes

. to which special routes announcements are created

. in what languages announcements are given

. language identifiers

Steps

1. Check free and reserved memory of the VANG plug-in unit (RAI)

Before you start

Before you start creating announcements which contain new speechsample files, always check if there is enough free memory in theVANG plug-in unit. VANG can have several free areas in thememory. The command output shows the starting block and the sizeof every free area.

a. Check the memory capacity of VANG-S (RAI)

Check the amount of free and reserved VANG memory in anetwork element which has 2 VANG-S plug-in units.

ZRAI:DEV=VAN:VANG;

Expected outcome:

VANG MEMORY CHECKING:

VANG 0

RESERVED MEMORY FREE MEMORY

34 BLOCKS 4046 BLOCKS

0 MIN 17 SEC 33 MIN 43 SEC

FREE AREAS IN VANG 0



Creating announcements

AREA START BLOCK LENGTH OF AREA

0 24 4046

ONE BLOCK IS 4096 BYTES


VANG 1






0 24 3288


COMMAND EXECUTED

The free memory capacity of the first VANG-S is 33 minutesand 43 seconds, that of the second VANG-S is 27 minutes and24 seconds.

b. Check the memory capacity of VANG-U (RAI)

Check the amount of free and reserved VANG memory in anexchange which has 1 VANG-U.

ZRAI:DEV=VAN:VANG;

Expected outcome:


VANG 0






0 4 4012

1 4031 6


COMMAND EXECUTED

The free memory capacity of the plug-in unit is 238 minutesand 28 seconds.

2. Record and store speech sample files

Announcements given from the internal announcement device arerecorded with the VARS equipment. Every speech sample isrecorded in its own file. The announcement can be recorded eitheras a whole, so that the entire announcement consists of one singlespeech sample file, or in parts which can be used in severalannouncements.


Announcements

Announcements that are recorded as a whole sound more naturalthan those recorded in parts, but they also require considerablymore memory in the announcement device. Always check inadvance that the total duration of the announcements do not exceedthe capacity of the announcement device.

Store the recorded VAD and VAT files to diskettes or to the systemdisk of the network element (follow the operating instructions of therecording equipment). The identifier of a file stored to a diskette mustconsist of the file number and of an extension part, which can be t ord, depending on the file type. For example, 10.t for VAT file 10, and11.d for VAD file 11.

3. Construct and store language structure files

Form the language structure files with VAPRGEN by following theoperating instructions of the VARS equipment. After that, store thefiles to diskettes. The identifier of the file stored to a diskette mustconsist of the file number and of the extension part which is l, forexample 12.l.

4. Transfer and load new speech sample and language structurefiles to the network element (RAT)

a. Transfer VAD and VAT files (RAT). Transfer VAD and VAT files from the diskette or from the

system disk to the network element's mass memory.When transferring files from the system disk, give alsothe name of the source subdirectory in the command.The target directory does not need to be defined,because the program automatically stores the files to theLFILES directory.

. Transfer the fixed-content speech sample files 5.t, 10.t,11.t, and 12.t from the VATFILES directory to the LFILESdirectory.

ZRAT:FTYP=VAT,FNUM=5&10&&12:WS,VATFILES;. You can define the numbering of VAT files in the FCD

parameter. If older files of the same numbers alreadyexist in the mass memory, they are replaced by the newones. This is why the program asks you to confirm thecommand before it is executed.

. If the parameter is not given, the system numbers thefiles in the transfer consecutively, starting from the nextavailable file number. For example, if you copy VAT files1.t, 2.t, and 10.t to a directory where there are noprevious VAT0xxxx.IMG files, the new files arenumbered VAT00001.IMG, VAT00002.IMG and




VAT00003.IMG. If the directory already contains, forexample, a VAT00001.IMG file, the new files arenumbered VAT00002.IMG, VAT00003.IMG, andVAT00004.IMG.

. VAD files have no default numbering. They are alwaysnumbered by the system, and the numbering cannot bechanged.

. The program stores the transferred files to the LFILESdirectory as VAD0nnnn.IMG and VAT0nnnn.IMG files.

b. Transfer VAL files (RAT). Transfer the language structure files (VAL files) from the

diskette or from the system disk to the network element'smass memory. When transferring files from the systemdisk, give also the name of the source subdirectory in thecommand. The target directory does not need to bedefined, because the program automatically stores thefiles to the LFILES directory.

. Before transferring the VAL files, the language-specificvariable-content speech sample files (VAD files) shouldbe updated first.

. Transfer the VAL files 9.l, 10.l, 11.l, and 15.l from theVALFILES directory to the LFILES directory.

ZRAT:FTYP=VAL,FNUM=9&&11&15:WS,VALFILES;. When the updated language structure files are stored to

the system disk, the ANEHAN MML requests theVANSER to update the language structure files ofcertain languages.

c. Load new speech sample files. The RAT command does not load the speech sample

files into the VANG sample memory, it only moves themto the system disk.

. New speech sample files does not need to be loadedseparately; the Voice Announcement Service ProgramBlock (VANSER) loads the files automatically when theVANG plug-in unit is started or when the announcementis created.

Note

The modified speech sample files need to be loaded separately to theVANG plug-in unit. For more information, see Section Loading modifiedspeech sample files.


Announcements

5. Create general announcement parameters (RAA)

General announcement parameters are needed when creatingannouncements for the internal announcement device. The purposeof these parameters is to define certain basic conditions for theannouncement service. They determine, for example, whatannouncement device is used, how many times (or for how long) theannouncement can be played to the same caller, and how manysimultaneous listeners are allowed for the announcement.

Note

The length of the pre-announcement phase should not be more thanten seconds.

a. Create a general announcement parameter for the internalannouncement device (RAA)

Create a general announcement parameter APAR1 for anannouncement given from the internal announcement device.The parameter limits the number of listening times to 2.

ZRAA:ANAM=APAR1,DEV=VAN,LCL=2;

6. Create an announcement (RAC)

The announcement is created by creating a special route whichincludes the specified announcement parameters.

When creating announcements for the internal announcementdevice, in the command, define the speech sample files that is usedin the announcement. VAT files are identified by the number of thecorresponding .IMG file. For example, the numbers 13 and 127 referto VAT00013.IMG and VAT00127.IMG, respectively. VAD files areidentified by the identifiers of their corresponding element groups.For example, the variable part '13 minutes' is referred to by theidentifier V3, and the variable part '2 pounds' by the identifier V2.

If you are creating a voice announcement which consists of morethan one announcement phase, the announcement devices fromwhich additional announcement phases (pre- and post-announcements) are given must also be given in the command.




Note

A beginning tone is given before the actual announcement and italways lasts for one second, whereas the length of a tone given in oneof the three announcement phases must be defined when creating theannouncement.

A text announcement can be created to a free special route or to onewhich contains a voice announcement.

a. Create an announcement for the internal announcementdevice (RAC)

Create an announcement for the internal announcementdevice to special route 102. The announcement is identified bythe general announcement parameter APAR1. The mainannouncement consists of speech sample files 45 and 31. It ispreceded by a beginning tone, given in timeslot 4, andfollowed by a tone, given in timeslot 3. The tone lasts for 2seconds. The announcement index is 9. Announcementchannel is allocated on demand.

ZRAC:SPR=102,DEV=VAN,ADEV=TG::AIND=9,ALLO=OND,ANAM=APAR1,AFIL=45&31:TONE=3,LTIM=2:BTO=4;

b. Add a text announcement to the announcement (RAC)

Add a text announcement 'TEST TEXT' to the announcementon special route 109. The text announcement index is 5.

ZRAC:SPR=109,TXIND=5,TXTEXT="TEST TEXT";

7. Activate the announcement (RAM)

Before a new announcement can be used, it has to be activated bychanging the state of the announcement special route into ON.

Activate the announcement created to special route 105.

ZRAM:SPR=102:STATE=ON;

8. Create an announcement analysis (RDC)

Announcement analyses are created to an analysis tree whosevalue is determined in the ANN_ANAL_TREE (000:0009) PRFILEparameter . The default value is 48. The analysis is usually definedfor the call type 'special call', and the type of number is 'unknown'.The analysis leads to the special route where the announcementparameters are.


Announcements

Create an announcement analysis for an intermediateannouncement given in the default language. The announcementspecifier obtained from the call control is 161. The analysis leads tospecial route 103, and the call is charged at your own exchange.

ZRDC:DIG=03161,TREE=48,TON=UNK:SPR=103,CT=SC,SP=5:CP=OE;

Further information

When creating an announcement analysis, use the SC (special call)value for the CT (call type) parameter. The value for the SP (seizurepoint) parameter must be the same as the number of digits broughtto the analysis.

More information about how analysis trees are created and modifiedcan be found in Digit Analysis Handling, RD Command Group andRouting and Analyses, Operating Instructions. For instructions onhow the values of the PRFILE parameters are interrogated andmodified, refer to Parameter Handling, WO Command Group.

9. Create a call control analysis (RDC)

The call control analysis in which the called number is analysed, iscreated to an analysis tree of an incoming call. The standardanalysis trees and their default values have been listed in Routingand Analyses, Operating Instructions.

If the announcement case is a direct call to announcement, theanalysis is created for the number that is the call number of theannouncement service. The analysis must lead to an announcementspecifier, on the basis of which the call control software forms theannouncement identifier to be taken to the announcement analysis.

When creating intermediate announcements, the announcementspecifier is defined in the result of an EOS analysis, EOS attributeanalysis, routing attribute analysis, call barring analysis, or functionanalysis. The analyses are managed by Attribute Analysis Handling,RQ Command Group, End-of-Selection and Function AnalysisHandling, RX Command Group, and Outgoing Call Barring AnalysisHandling, RK Command Group. A detailed description of theanalyses can be found also in Basic Routing Functions, FunctionalDescription.




Create a call control analysis for number 5116320 to the defaultanalysis tree of mobile-originating calls. The analysis results in anannouncement specifier 145. The call is charged at your ownexchange, and the seizure point of an outgoing circuit is 7.

ZRDC:DIG=5116320,TREE=2:ANN=145,CT=SC,SP=7:CP=OE;

Further information

When creating a call control analysis leading to announcementanalysis, use the SC (special call) value for the CT (call type)parameter. The value for the SP (seizure point) parameter must bethe same as the number of digits brought to the analysis.

Further information

In the following, you can find examples for how different types ofannouncements can be created.

Example Creating test announcement

Create a test announcement for the internal announcement device tospecial route 100. The maximum number of announcement listeningtimes, defined in the general announcement parameter TEST0, is 3. Thecall is charged at your own exchange, the announcement index is 200, andthe announcement channel is allocated on demand.

1. Create the general announcement parameter

ZRAA:ANAM=TEST0,DEV=VAN,LCL=3;

2. Create the announcement

ZRAC:SPR=100,DEV=VAN::ALLO=OND,ANAM=TEST0,AIND=200,AFIL=V0;

3. Activate the announcement


4. Create the announcement analysis

ZRDC:DIG=012,TREE=48:SPR=100,CT=NGC,SP=3:CP=OE;


Announcements

Example Creating direct announcement of internal announcementdevice

Create a direct announcement to special route 120. The call number of theannouncement service is 5116320; it is analysed in the default analysistree of mobile-originating calls. The announcement is given from theinternal announcement device and identified by a general announcementparameter VANG1, which limits the maximum number of announcementlistening times to 2. The announcement itself consists of two fixed-contentspeech sample files, VAT00045.IMG and VAT00123.IMG. Theannouncement analysis is made in tree 48, the announcement specifier is145, and the announcement channel is allocated on demand. Theannouncement index is 12. The call is charged at your own exchange.


ZRAA:ANAM=VANG1,DEV=VAN,LCL=2;


ZRAC:SPR=120,DEV=VAN::ALLO=OND,ANAM=VANG1,AIND=12,AFIL=45&123;




ZRDC:DIG=00145,TREE=48,TON=UNK:SPR=120,CT=SC,SP=5:CP=OE;

5. Create the call control analysis


Example Creating alternative routing for the announcement service

An alternative routing for the announcement service is defined by creatinga new special route for the announcement and by adding it to the routingalternatives of the destination. In the following, an alternative routing isdefined for the announcement created in Example Creating directannouncement of internal announcement device. The new subdestination,SUBDEST2, consists of special route 9, and it is added as routingalternative 1 to the DEST1 destination. The announcement index is 9.

1. Create a new special route for the announcement

ZRAC:SPR=9,DEV=VAN::ALLO=OND,ANAM=VANG1,AIND=9,AFIL=45&123;




2. Activate the announcement on the new special route


3. Create a subdestination which leads to the new special route

ZRDE:NSDEST=SUBDEST2:SPR=9,CT=SC,SP=7;

4. Add the subdestination alternative to the destination

ZRDE:NDEST=DEST1,ALT=1:NSDEST=SUBDEST2:CP=OE;

5. Create an announcement analysis that leads to the destination

ZRDC:DIG=00145,TREE=48,TON=UNK:NDEST=DEST1;

Example Creating announcement with spare channel

Create a direct announcement with spare channel to special route 115.The announcement is identified by the general announcement parameterAPAR1, which limits the number of announcement listening times to 2. Theprimary announcement channel consists of timeslot 4 on PCM line 41, thespare channel of timeslot 5 on PCM line 42. The call number of theannouncement service, 5116320, is analysed in tree 2. Theannouncement analysis is made in the default tree and it leads to adestination called DEST1 through the primary subdestination SUBDEST1.The announcement specifier is 125. The call is charged at your ownexchange.


ZRAA:ANAM=APAR1,DEV=VAN,LCL=2;


ZRAC:SPR=5,DEV=VAN::ANAM=APAR1,ANCH1=41-4::ANCH2=42-5;



4. Create a subdestination connected to the announcement specialroute


5. Create the destination

ZRDE:NDEST=DEST1:NSDEST=SUBDEST1:CP=OE;


Announcements



7. Create a call control analysis that leads to the announcement


Example Moving announcement from spare channel to another SPR

In the following example, the announcement channel used as a sparechannel is removed, and alternative routing is defined for theannouncement. The new subdestination, SUBDEST2, consists of specialroute 7, and it is added as routing alternative 1 to the destination DEST1.

1. Deactivate the announcement

ZRAM:SPR=5:STATE=OFF;

2. Turn the announcement circuits into the barred state

ZCEC:CRCT=41-4:BA;

ZCEC:CRCT=42-5:BA;

3. Remove the spare channel

ZRAM:SPR=5,DEV=VAN:ANCH2=0&&0;

4. Create a new special route for the spare announcement

ZRAC:SPR=7,DEV=VAN::ANAM=APAR1,ANCH1=42-5;

5. Bring the announcement circuits into a working state

ZCEC:CRCT=41-4:WO;

ZCEC:CRCT=42-5:WO;

6. Activate the announcement on both special routes



7. Create a subdestination connected to the new special route


8. Add the subdestination alternative 1 to the destination

ZRDE:NDEST=DEST1,ALT=1:NSDEST=SUBDEST2:CP=OE;






Example Creating multilingual announcement

Create an intermediate announcement to special route 100. Theannouncement is identified by a general announcement parameter MULTI,which limits the number of announcement listening times to 3. Theannouncement is given in Finnish, Swedish, and English, theannouncement index is 100, and the announcement channel is allocatedon demand. The call is charged at your own exchange.


ZRAA:ANAM=MULTI,DEV=VAN,LCL=3;


ZRAC:SPR=100,DEV=VAN::AIND=100,ALLO=OND,ANAM=MULTI,AFIL=101&201&301;




ZRDC:DIG=03100,TREE=48:SPR=100,CT=NGC,SP=5:CP=OE;

Example Creating intelligent network announcement in three languages

Create an intelligent network announcement, which is given in Finnish,Swedish and English.

The announcement consists of two fixed-content speech sample fileswhose numbers are 100 and 101 (Finnish), 200 and 201 (Swedish), and300 and 301 (English), and of two variable parts whose identifiers are V2and V3. The Finnish announcement is given from special route 100, theSwedish announcement from special route 200, and the Englishannouncement from special route 300. The announcement indexes are100, 200 and 300, respectively.

The maximum number of listening times, defined in the generalannouncement parameters FINN1, SWED1 and ENGL1, is 3. Theannouncement analysis is made in the default analysis tree, theannouncement specifier obtained from the SCP is 123, and theannouncement channel is allocated on demand. The call is charged atyour own exchange.


Announcements

1. Create the announcement in Finnish

a. ZRAA:ANAM=FINN1,DEV=VAN,LCL=3;

b. ZRAC:SPR=100,DEV=VAN::AIND=100,ALLO=OND,ANAM=FINNI,AFIL=100&V3&101&V2;

c. ZRAM:SPR=100:STATE=ON;

d. ZRDC:DIG=09123,TREE=48,TON=UNK:SPR=100,CT=SC,SP=5:CP=OE;

2. Create the announcement in Swedish

a. ZRAA:ANAM=SWED1,DEV=VAN,LCL=3;

b. ZRAC:SPR=200,DEV=VAN::AIND=200,ALLO=OND,ANAM=SWEDI,AFIL=200&V3&201&V2;



3. Create the announcement in English

a. ZRAA:ANAM=ENGL1,DEV=VAN,LCL=3;

b. ZRAC:SPR=300,DEV=VAN::AIND=300,ALLO=OND,ANAM=ENGLI,AFIL=300&V3&301&V2;



For instructions about how Integrated Announcing Equipment is activated,see Feature 236: Integrated Announcing Equipment, Feature ActivationManual.





Announcements

4 Modifying announcements

The instructions of modifying announcements describe how to loadmodified speech sample files, how to update language structure files, howto restore old speech sample files, and how to modify announcements,general announcement parameters, and an announcement analysis.

4.1 Loading modified speech sample files

If the speech sample files of an internal announcement device have beenmodified, they have to be loaded from the system disk into the VANGspeech sample memory. The loading of VAD files can take severalminutes, because the files of one element group are all loaded at one time.The command loads the files in groups of 18 files, into the active andpassive units alternately.

If you are modifying announcements, you do not need to load the speechsample files used in them separately. The program loads the files into theVANG sample memory when the modification command is given.

Files that have listeners cannot be loaded. The program tries a few timesto load the files before it informs the user that there are files which cannotbe loaded.

Steps

1. Load VAT files (RAY)

Load VAT files 50...99 from the LFILES directory to the VANGsample memory.

ZRAY:AFIL=50&&99;



Modifying announcements

4.2 Updating language structure files

Modify the old files, or construct new language structure files (VAL files)and store them to a diskette or to the system disk. Update the languagestructure files by transferring the modified files from the diskette or thesystem disk to the network element's mass memory by using the RATcommand. Before transferring the VAL files, update the language-specificvariable-content speech sample files (VAD files) first.

For more information, see Section Creating announcements.

Steps

1. Update VAL files (RAT)

Transfer all the VAL files from the diskette to the LFILES directory onthe system disk.

ZRAT:FTYP=VAL;

4.3 Restoring old speech sample files

If the file transfer has failed, or if you are not satisfied with the contents ofthe new speech sample files, you can restore the old versions of the filesfrom the mass memory.

Steps

1. Restore old versions of VAT files (RAT)

Restore the old versions of VAT files 3 and 22.

ZRAT:FTYP=VAT,FRES=3&22;

4.4 Modifying general announcement parameters

The modification of a general announcement parameter affects all theannouncements in which the same parameter has been used. This is whythe program checks whether the parameter has been defined for morethan one announcement (special route). If it has, the program puts out alist of all the special routes on which the parameter is used, and asks youto confirm the command before it is executed.


Announcements

Steps

1. Modify the general announcement parameter (RAN)

The general announcement parameter ANNP1 determines that theannouncement has a phase time of 10 seconds, and a maximumlistening time of 20 seconds. Modify the announcement so that thenew listening time limit is 30 seconds, but do not change the phasetime.

ZRAN:ANAM=ANNP1,LTL=3;

4.5 Modifying announcements

Before you start modifying an announcement, deactivate it by changingthe state of the special route into OFF.

In the PHA parameter you can define which announcement phase ismodified. If the parameter is not given, the modification affects the mainannouncement phase. By the modification command, you can also deletetext announcements, and add or delete pre- and post-announcements.

After the modification, the announcement has to be activated again.

Steps

1. Modify the announcement (RAM)

Change the announcement on special route 109 so that the listeningtime of the tone given in the post-announcement phase becomes 4seconds.

ZRAM:SPR=109,PHA=POS:LTIM=4;

2. Delete the text announcement (RAM)

Delete a text announcement from special route 109, which alsocontains a voice announcement.

ZRAM:SPR=109,DEL=TXANN;



Modifying announcements

4.6 Modifying an announcement analysis

Announcement analyses can be modified with the RMR command of DigitAnalysis Modification, RM Command Group.

Steps

1. Move the announcement (RMR)

Move the announcement on special route 112 to special route 102.The announcement identifier is 00145.

ZRMR:DIG=00145,TREE=48:SPR=102;


Announcements

5 Deleting announcements

Announcements are deleted in the opposite order to the one in which theyhave been created.

Steps

1. Delete the call control analysis (RDD)

Delete the call control analysis connected to the announcement.Remove the announcement analysis if such an analysis exists.

ZRDD:DIG=<digits>,TREE=<analysis tree>;

2. Deactivate the announcement (RAM)

ZRAM:SPR=<special route number>:STATE=OFF;

3. Delete the announcement (RAD)

ZRAD:SPR=<special route number>;

4. Delete the general announcement parameters (RAR)

You can delete the general announcement parameters only if theparameters are not used in other announcements.

ZRAR:ANAM=<name of announcement parameter>;

Further information

Speech sample files cannot be deleted, they can only be removed from anannouncement by modifying the announcement. If the announcementincludes speech sample files which are not needed in otherannouncements, the files are automatically deleted from the VANG samplememory.



Deleting announcements

Note

Text announcements can be removed without deleting the entirespecial route. For more information, see Section Modifyingannouncements.


Announcements

6 Announcements troubleshooting

If the announcement does not function properly, that is, no announcementcan be heard, the fault is most likely in one of the following:

. call control (for example, a fault in service request)

. announcement server (ASEPRB) and Outgoing Call Control forAnnouncements in CCIF Interface (OCZPRB)

. VAN control (VANSER)

. Verbal Announcement Generator (VANG) plug-in unit

. announcement parameters

See Sections PRFILE for free announcement calls and Phasedannouncements.

. the announcement has been created incorrectly

. call control analysis

. PRFILE parameters which concern announcements (parameterclasses 000 and 002)

See Sections PRFILE for free announcement calls and Phasedannouncements.

. cabling or strapping

. MSS is in CMN mode

Steps

1. Check that the announcement has been created correctly (RAI)

ZRAI:<special route number>;. If it has been created correctly, go to Step Change the state to

ON (RAM).. If it has not been created correctly, correct it, and then go to

Step Check the alarms and the clear codes (AHP).



Announcements troubleshooting

. If the state is OFF, go to Step Change the state to ON (RAM).

. If the state is ON, go to Step Check the analyses (RII).

2. Change the state to ON (RAM)

ZRAM:<special route number>:STATE=ON;. If you succeed, go to Step Collect the logs and messages

(WTI).. If you do not succeed, go to Step Check the analyses (RII).

3. Check the analyses (RII)

ZRII:TREE=48;. If the analyses are correct, go to Step Listen to the

announcements again.. If the analyses are not correct, correct them and then go to

Step Check the alarms and the clear codes (AHP).

4. Check the announcement devices (WTI)

Check the announcement devices (for example, strappings andcabling). Compare the information to the ones in the configurationdatabase.

ZWTI:P:<computer_unit>,<unit_ind>:<VANG_name>,<VANG_ind>;. If there is no problem, go to Step Collect the logs and

messages (WTI).. If you find any problem, correct it, and then go to Step Collect

the logs and messages (WTI).

5. Listen to the announcements again. If you still can find any problem, go to Step Check the alarms

and the clear codes (AHP).

6. Check the alarms and the clear codes (AHP)

Check if all the alarms related to announcements are set. For moreinformation, see the instructions on error messages.

ZAHP;

The following alarms are associated to announcements:


Announcements

. 1000 SPEECH SAMPLE FILE LOADING FAILED

. 1153 ERROR IN DIAL ANALYSIS DATA

. 2055 VANG FAILURE

. 2056 CHECKSUM ERROR IN VANG SAMPLE

. 2194 ANNOUNCEMENT ID ANALYSIS ERROR

. 2626 VANG PCM-INTERFACE FAULTY

The following clear codes are related to announcements:. 0000 NORMAL END OF THE CALL. 0406 CONNECTION FAILED IN GSW/SWI. 0509 FILE ERROR. 0608 SETTING OF CHARGING FAILED. 070D ANNOUNCEMENT SERVICE FAILURE. 0B2C IN APPLICATION PROTOCOL ERROR. 0B2D INTELLIGENT NETWORK APPLICATION RESPONSE

TIME-OUT. 0C0E SUBSCRIBER, INTERACTION ERROR

For more information, see the Clear Code List.

7. Collect the logs and messages (WTI)

If you still do not hear the announcement, do the following beforecontacting Nokia Customer Services Centre for help:

a. Collect the messages from VANSER, ASEPRB, OCZPRB andRMAPRB signalling units, and also from CM, CMM and M byusing the commands of the GD and OQ service terminalcommand groups

Note

In case of IN announcements, collect messages also from CZGPRB,SREPRB, and CAMPRB from the signalling units.

Note

Extended message monitoring (OE) is preferred to message monitoring(OQ), and the most preferred one is SOLMON.



Announcements troubleshooting

b. Collect the logs from the computer unit in which the VANGplug-in units have been installed. Check the unit (M or CM)with the WTI command:

ZWTI:P;

Collect error logs from all signalling units, CM, CMM and fromM.

The logs appear on the service terminal.

Note

The OCZPRB can only fail in case of a direct announcement, so thereis no need to collect logs from other types of announcements.

c. Print version information from the above mentioned programblocks (WQV)

d. List announcement analyses (RII)

e. Interrogate announcements definitions (RAI)

Troubleshooting for Alarm 2194

If 2194 ANNOUNCEMENT ID ANALYSIS ERROR alarm occurs, take thefollowing steps:

1. Check that the analysis, which is informed by the alarm, exists in theanalysis tree 48.

2. If it is missing, and the alarmed analysis is reasonable, create theanalysis in the analysis tree 48.

Use the RDC command.


Announcements

7 Additional information on VANG plug-inunits

VANG plug-in units equipped in the network elements are shown in thefollowing table:

VANG-A/VANG-B equipping

The equipping of VANG-A/VANG-B plug-in unit differs from the above inthat it requires PCI hardware. The addressing is dynamic, and thereforedependent on the overall plug-in unit equipping, and on the availableaddresses.

Table 7. VANG-A/VANG-B equipping

NE Cartridge, unit PIU Track

DX 200 MSCi, DX 200 TransitMSCi

CC3C-A cartridge

CCMU VANG-A/B 0 3

VANG-A/B 1 4

VANG-A/B 2 5

DX 200 Compact MSCi CC3C-A cartridge

CMM VANG-A/B 0 4



Additional information on VANG plug-in units

Announcement

Documents

nokiasiemens networks

announcements analyses

multilingual announcements

phased announcements

test announcements

voice announcements

text announcements

types of announcements