7/17/2019 F100

http://slidepdf.com/reader/full/f100 1/6

BugFix

  1

EWSD

Individual Digital Announcement System (INDAS)

General

There is an enormous variety of uses for announce-

ments in everyday telephone communications. For in-

stance:

 – informing callers that the number they have dialed

has changed

 – informing callers that the person they are trying to

reach is unavailable

 – providing assistance with procedures related to a

variety of special services

With the Individual Digital Announcement System (IN-

DAS), EWSD provides a modern announcement sys-

tem which is universal, versatile and quick to apply.

Announcements types

Announcements created with INDAS are classified in

announcement types. This allows announcements to

be tailored to a range of different situations.

INDAS provides the following announcements types:

• Standard announcements

•

Individual announcementsStandard and individual announcements can be con-

nected at the same time to different points. Several an-

nouncements may be connected one after the other to

the same subscriber without releasing and reestablish-

ing the speech connection to INDAS.

Announcements can be played in a network node in up

to four different languages. The languages can be com-

bined in any order so that the announcement can be

output in different languages. On reaching the stipulat-

ed number of announcement cycles the announcement

connection is immediately cleared on the calling partyside.

Announcements types

Structure and elements of announcements

System components

Call charge registration

Administration

Technical data

EWSD

network node

INDAS

OCANEQ

Softwarecallingsubscriber announcement

Benefits

... for the operator

 – Easy generation and administration

of announcements

 – improved call processing service

... for the subscriber

 – Prompt and precise information at

any time

7/17/2019 F100

http://slidepdf.com/reader/full/f100 2/6

2

Standard announcements

INDAS standard announcements are permanently de-

fined recorded announcements comprising one or

more parts (fragments). Uniquely defined announce-

ment numbers are assigned to each standard an-

nouncement.

Examples of INDAS standard announcements:

 – “This call is toll free.” – “This number is not connected."

A standard announcement is permanently assigned to

an announcement port, i.e. for each standard an-

nouncement at least one announcement port has to be

used. Standard announcement ports are able to handle

broadcast function, that means one of these ports is

able to handle up to 16 calling parties. By administra-

tion it is possible to secure that each party hears the an-

nouncement from the beginning (i.e. None Barge In,

NBI).

Individual announcements

Individual announcements comprise one or more IN-

DAS phrases. An INDAS phrase corresponds to at

least one fully spoken sentence. It generally consists of

permanent and variable parts. Uniquely defined INDAS

phrase numbers are assigned to each INDAS function.

The variable parts in the example below are enclosed

in pointed brackets and are not assigned to the relevant

values until the announcement is created.

Individual announcements are addressed by means of

intercept codes. Using the INDAS function, whichuniquely identifies the logical meaning and structure of

a specified individual announcement, the correct se-

quence of text fragments is read out of the operationally

controlled equipment for announcements, OCANEQ

(see System components). The subscriber is connect-

ed with the trunk of an announcement trunk group of

the type" individual announcement" and hears the an-

nouncement. Individual announcements ports are not

able to handle the broadcast function.

Examples of individual announcements are:

•

Announcement for a changed directory numberThe INDAS function “announcement for a changed

directory number” has the effect that after a sub-

scriber, PBX or extension number has been

changed the new number is announced to callers

who call theold number. An announcement with the

changed directory number is addressed using the

dialed number.

The INDAS phrase number 901 is permanently as-

signed to this INDAS function.

 – Permanent part

"The number you have dialed is invalid. The newnumber is as follows:"

 – Variable part

"<directory number>"

The permanent part of an INDAS phrase consists

of one or more text fragments. The text fragments

corresponding to the variable part are determined

on the basis of INDAS parameter values. Each IN-

DAS parameter has a group of INDAS words as its

range of values.

INDAS parameter values are automatically deter-mined from the database by the system e.g., read-

ing out the changed directory number. The digits 0

to 9 are output internally as the INDAS word num-

bers 1 to 10 (permanently coded). These INDAS

word numbers have to be assigned by MML com-

mand to the appropriate text fragments in order for

the calling party to hear the correct announcement.

Different announcements can be played at a port

for individual announcements (e.g., announce-

ments for alarm calls and for changed directory

numbers).

• Time announcement

With the INDAS function "time announcement", a

time announcement can be assembled to suit indi-

vidual requirements.A time announcement comprises:

<introductory text> (<date>) <time> <gong tone>

The <date> part is optional.

The contents of the <introductory text> are identical

for all time announcements implemented with the

same OCANEQ variant.

The layouts of <date> and <time> are identical for

all time announcements implemented with the

same OCANEQ variant.

Example: “At the next tone it will be ten o’clock and

thirty seconds” <gong tone>

The order of languages can be specific to the net-

work or separate for each time announcement

group.

Structure and elements of

announcements

Announcements consist of a sequence of elements

(speech fragments) and can be digitized and pro-

grammed with the aid of software tools.Announcement

elements are administrable and logically addressable

announcement contents.

Spoken text fragment: INDAS word number:

“Zero” 1

“One” 2

... ...

“Nine” 10

7/17/2019 F100

http://slidepdf.com/reader/full/f100 3/6

  3

The following elements are defined:

 – INDAS standard announcement

is made of one or more (max. 1024) text fragments

in every language and contains no INDAS parame-

ters.

 – Individual announcement (INDAS phrase)

is a series of fixed or variable components. A fixed

component consists of one or more text fragments.

The variable component consists of text fragmentswhich may be defined during runtime using the IN-

DAS parameters.

 – INDAS pause

consists of a pause fragment and is inserted to sep-

arate INDAS phrases and to separate different lan-

guage outputs within a multi-lingual

announcement.

 – INDAS parameter

defines a variable part of an INDASphrase. It points

to a group of INDAS words.

 – INDAS wordconsists of a text fragment. One or two INDAS

words are assigned to every possible value of an

INDAS parameter; an INDAS word for normal

speech melody and, if necessary, an INDAS word

for lower tone variants.

 – Text fragment

is the smallest language unit addressable by

means of its text fragment number. It consists of a

string of text words (pauses and tones are included

in thedefinition of the text word). Thetext fragments

are generated from recordings and are stored in a

speech memory of the OCANEQ module

 – Text word

is a spoken word, a pause or a tone.

System components

INDAS consists of several software programs and one

hardware component. The software programs are:

• ALINA

• PC-CAPE

• OCANEQ service PC with OCANEQ service soft-

ware

The hardware component is:

• OCANEQ module

A normal PC is used to design and control the an-

nouncements using the software programs PC-CAPE,

ALINA and the OCANEQ service software. The three

software programs can also run separately on different

PCs.

OCANEQ

module

Operator PC

Tone studio

MML files with

announcement

definitionsALINAALINA

WAV-

audio files

PC-CAPE service PC

Digitizing announcements

Cutting announcements into

text fragments

Assigning fragment numbers to

relevant speech fragment files

Creating a load table

Operator PC

PC-CAPE

Transfer of text

fragments

CAP files

OCANEQ

service

software

List of text

fragments

PC-CAPE

7/17/2019 F100

http://slidepdf.com/reader/full/f100 4/6

4

The procedure for generating and administrating new

announcements is as follows:

 – The announcements and the announcement cata-

log are created with ALINA.

 – All of the texts required for the announcement are

spoken, for example, onto tape in a sound studio

and read into PC-CAPE.

 – Using PC-CAPE, the announcements are record-

ed, digitized and cut into text fragments. The frag-ment number required as per announcement

catalog is also assigned to the relevant speech

fragment file (creation of a load table).

 – The OCANEQ service software is used for the

transfer of firmware and fragments to the OCANEQ

module on the basis of the load table supplied by

the PC-CAPE. In addition to local transfer, external

service PCs can be connected with the OCANEQ

module by means of an ISDN dialed connection.

For checking the announcements stored in the

OCANEQ module operators can start an audible checkvia specific MML commands.

ALINA

ALINA (Administration of Language data for Individual

Announcements) is the central component of INDAS.

ALINA is used for the administration of announce-

ments. At the graphical user interface (GUI), operators

can define how text fragments are combined. ALINA

also provides access to existing data and to extensive

documentation on the current status of the database.

Via a comfortable graphical user interface, ALINA pro-vides possibilities for:

• Administering system and customer announce-

ments

ALINA classifies announcements as either system

announcements or customer announcements. For

system announcements, text information and an-

nouncement layout are administered in addition to

the announcements themselves. For customer an-

nouncements, no text information is stored. In-

stead, numbers are assigned to the fragments.

• Creating a fragment inventory

Operators can create an advance inventory of text

fragments that are not yet used in any of the current

announcements. It is suggested that operators

have the professional speaker record as many dif-

ferent sentences as possible. Using the fragment

number, operators can access these text fragments

at any time.

• Verifying recorded data

To administer the announcements, operators have

to import the files generated by PC-CAPE to ALI-

NA. These files contain information on the edited

voice fragments (required memory capacity, speak-

er ID). This enables operators to see how much

memory is still available on the OCANEQ module.

ALINA also issues a warning if operators attempt to

combine fragments spoken by different speakers inthe same announcement.

• Administering distribution data

If several OCANEQ modules are installed, opera-

tors can use ALINA to administer the total or avail-

able memory capacity.

• Creating output files

ALINA can generate various types of output file,

simplifying announcement administration tasks:

 – MML command files

ALINA creates the necessary MML commands

to create or modify the announcement relatedparts of the EWSD database (OCANEQ- and UI-

database), so that announcements can be acti-

vated or deactivated.

 – Fragment lists

Fragment numbers are assigned automatically,

providing a link between text fragments and their

logical addresses. The information in the frag-

ment list can be processed with PC-CAPE.

 – Sample lists

A sample list contains complete announcement

texts in the form of the sequence of fragment

numbers required to compose each announce-

ment.

 – Distribution lists

The distribution list produced by ALINA shows

which speech version must be loaded to which

OCANEQ modules.

7/17/2019 F100

http://slidepdf.com/reader/full/f100 5/6

  5

PC-CAPE

The PC-CAPE software enables operators to create

and modify their own announcements flexibly and effi-

ciently. The main function of PC-CAPE is to record

voice data, edit the data and convert it into a format

suitable for the OCANEQ service PC. The PC on which

it runs must be equipped with a microphone, a sound

card and headphones or active loudspeakers.

A user-friendly interface supports the creation and edit-

ing of announcement speech fragments. Written as a

Windows application, PC-CAPE produces a graphical

representation of the voice file as an "envelope curve".

Texts can then be cut and excerpted as required.

The PC-CAPE window is divided into two areas. The

top area shows the entire envelope curve, as an over-

view of the text currently being processed. In the bot-

tom area the envelope curve can be cut. In this way,

announcements to meet operators’ needscan easily be

designed.

To create an individual announcement using PC-

CAPE, the following steps must be performed:

• Recording voice data

Using a microphone announcement texts can easi-

ly be recorded directly in PC-CAPE. For phonetic

reasons, the required phrases must be spoken in

complete sentences. To obtain good quality an-

nouncements, it is often advisable to have the an-

nouncement texts recorded on tape by aprofessional speaker at a recording studio. The re-

sult should be WAV-files, which can be used by PC-

Cape. The recorded data can be stored either in

WAV audio format or in PC-CAPE's own CAP for-

mat.

• Processing voice files

A typical voice file contains several minutes of spo-

ken text. Using PC-CAPE, parts out of this large

quantity of voice data can then be cut and the se-

lected text sections can be stored, with a suitable

pause before and after, under a new file name.• Adjusting the volume

PC-CAPE allows operators to measure the level of

their text fragments in decibels. If any of the voice

fragments deviates too far from the defined level

plan, digital level adjustment can be applied.

• Producing multilingual versions

Once all of the text fragments have been produced,

a speech version is generated. This includes the

level-adapted, companded voice files and a list of

files to be loaded (load table). A consistency check

determines whether the corresponding voice file

exists for each specified fragment number.

7/17/2019 F100

http://slidepdf.com/reader/full/f100 6/6

6

OCANEQ service PC with OCANEQ service soft-

ware

A PC or notebook with Windows NT 4.0 becomes an

OCANEQ service PC by adding the OCANEQ service

software.

The OCANEQ service software contains a program

which rapidly loads text fragments and control firmware

to the OCANEQ module. Connected locally, theOCANEQ service PC uses the Ethernet interface on

the OCANEQ module. Alternatively, the OCANEQ

module can be loaded remotely via a dial-up ISDN con-

nection. In this case, the OCANEQ service PC must be

equipped with an ISDN card.

PC-CAPE transfers a load table (list of files to be load-

ed), the level-adapted and companded voice files and

an OCANEQ header file to the OCANEQ service PC.

The OCANEQ header is the module's "visiting card",

providing information on the language version loaded in

the OCANEQ.

OCANEQ module

The OCANEQ (Operationally Controlled Equipment for

Announcement) comprises one module equipped with

control logic and voice memory.

The OCANEQ module is installed in a user interaction

line/trunk group (UI-LTG) in place of a digital interface

unit (DIU). Only one OCANEQ is permitted per LTG. It

has 63 announcement ports and is capable of storing

65535 addressable text fragments. For details on the

hardware please refer to the description User interac-

tion LTG (UI-LTG)

OCANEQ builds announcements out of the text frag-

ments stored in its voice memory using the text frag-

ment numbers. The logical sequence of text fragments

in an announcement is defined in a fragment list.

Call charge registration

The network operator uses an MML command to define

the charge data for announcements to be recorded

(see Operation Manual OMN:EXCH–TA).

The connection to INDAS can be recorded with auto-

matic message accounting (AMA) or pulse metering.

Administration

System administration

The following feature data can be administrated in

EWSD network nodes:

 – creation of announcements

 – recording by means of traffic measurement

For information on system administration please referto OMN:EXCH-SY.

Routing administration

For information on routing administration please refer

to OMN:EXCH-RO.

Technical data

PC-CAPE, ALINA, OCANEQ Service Software

Pentium PC (133 MHz or faster) with 32 Mbyte RAM

(recommended configuration) and 2 Gbyte hard disk

Operating system Windows NT 4.0

PC-CAPE also requires:

Sound card, Microphone, headphones or active loudspeakers

OQANEC Service Software also requires: ISDN card (for remote

update) or ethernet card for local update

OCANEQ

Mounting location: 1 LTU slot per LTG

Memory: 32/96/288 Mbyte = 70/210/630 minutes storage capacity

for announcements

65535 fragments (max. 1024 per announcement)

Local interface: Ethernet connector

EWSD

Maximum 1 OCANEQ per LTG

Up to 10 OCANEQ variants per network node(i.e. OCANEQs with

different voice contents)

Up to 4 languages per network node

Any number of OCANEQs can be assigned to each OCANEQ

variant

Per OCANEQ variant up to:a total of 2500 standard announcements for all languages

including

UI announcements without variable parts and broadcast-capable

customer announcements

900 UI announcements with variable parts in any language

199 text elements for non-broadcast-capable customer

announcements

approx. 16 intercept announcements with variable parts

Copyright (C) Siemens AG 2002

Issued by Information and Communications Group • Hofmannstraße 51 • D-81359 München

Technical modifications possible. Technical specifications and features are binding only insofar as they are specifically and expressly agreed upon in a written contract.

Order Number: A30828-X1160-F100-1-7629 Visit our Website at: http://www.siemens.com