Sie sind auf Seite 1von 6

BugFix

EWSD
Individual Digital Announcement System (INDAS)

General Benefits

Announcements types ... for the operator


Structure and elements of announcements Easy generation and administration
System components of announcements
Call charge registration improved call processing service
Administration ... for the subscriber
Technical data Prompt and precise information at
any time

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 Announcements types
has changed Announcements created with INDAS are classified in
informing callers that the person they are trying to announcement types. This allows announcements to
reach is unavailable be tailored to a range of different situations.
providing assistance with procedures related to a
INDAS provides the following announcements types:
variety of special services
Standard announcements
With the Individual Digital Announcement System (IN- Individual announcements
DAS), EWSD provides a modern announcement sys-
Standard and individual announcements can be con-
tem which is universal, versatile and quick to apply.
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.
EWSD
network node Announcements can be played in a network node in up
to four different languages. The languages can be com-
INDAS bined in any order so that the announcement can be
output in different languages. On reaching the stipulat-
OCANEQ ed number of announcement cycles the announcement
calling Software connection is immediately cleared on the calling party
subscriber announcement
side.

1
Standard announcements Variable part
INDAS standard announcements are permanently de- "<directory number>"
fined recorded announcements comprising one or The permanent part of an INDAS phrase consists
more parts (fragments). Uniquely defined announce- of one or more text fragments. The text fragments
ment numbers are assigned to each standard an- corresponding to the variable part are determined
nouncement. on the basis of INDAS parameter values. Each IN-
DAS parameter has a group of INDAS words as its
Examples of INDAS standard announcements: range of values.
This call is toll free. INDAS parameter values are automatically deter-
This number is not connected." mined from the database by the system e.g., read-
A standard announcement is permanently assigned to ing out the changed directory number. The digits 0
an announcement port, i.e. for each standard an- to 9 are output internally as the INDAS word num-
nouncement at least one announcement port has to be bers 1 to 10 (permanently coded). These INDAS
used. Standard announcement ports are able to handle word numbers have to be assigned by MML com-
broadcast function, that means one of these ports is mand to the appropriate text fragments in order for
able to handle up to 16 calling parties. By administra- the calling party to hear the correct announcement.
tion it is possible to secure that each party hears the an-
Spoken text fragment: INDAS word number:
nouncement from the beginning (i.e. None Barge In,
NBI). Zero 1
One 2
Individual announcements ... ...
Individual announcements comprise one or more IN- Nine 10
DAS phrases. An INDAS phrase corresponds to at
least one fully spoken sentence. It generally consists of
permanent and variable parts. Uniquely defined INDAS Different announcements can be played at a port
phrase numbers are assigned to each INDAS function. for individual announcements (e.g., announce-
ments for alarm calls and for changed directory
The variable parts in the example below are enclosed numbers).
in pointed brackets and are not assigned to the relevant Time announcement
values until the announcement is created. With the INDAS function "time announcement", a
Individual announcements are addressed by means of time announcement can be assembled to suit indi-
intercept codes. Using the INDAS function, which vidual requirements.
uniquely identifies the logical meaning and structure of A time announcement comprises:
a specified individual announcement, the correct se- <introductory text> (<date>) <time> <gong tone>
quence of text fragments is read out of the operationally The <date> part is optional.
controlled equipment for announcements, OCANEQ The contents of the <introductory text> are identical
(see System components). The subscriber is connect- for all time announcements implemented with the
ed with the trunk of an announcement trunk group of same OCANEQ variant.
the type" individual announcement" and hears the an- The layouts of <date> and <time> are identical for
nouncement. Individual announcements ports are not all time announcements implemented with the
able to handle the broadcast function. same OCANEQ variant.
Examples of individual announcements are: Example: At the next tone it will be ten oclock and
Announcement for a changed directory number thirty seconds <gong tone>
The INDAS function announcement for a changed The order of languages can be specific to the net-
directory number has the effect that after a sub- work or separate for each time announcement
scriber, PBX or extension number has been group.
changed the new number is announced to callers
who call the old number. An announcement with the
Structure and elements of
changed directory number is addressed using the
dialed number. announcements
The INDAS phrase number 901 is permanently as- Announcements consist of a sequence of elements
signed to this INDAS function. (speech fragments) and can be digitized and pro-
Permanent part grammed with the aid of software tools.Announcement
"The number you have dialed is invalid. The new elements are administrable and logically addressable
number is as follows:" announcement contents.

2
The following elements are defined: Text fragment
INDAS standard announcement is the smallest language unit addressable by
is made of one or more (max. 1024) text fragments means of its text fragment number. It consists of a
in every language and contains no INDAS parame- string of text words (pauses and tones are included
ters. in the definition of the text word). The text fragments
Individual announcement (INDAS phrase) are generated from recordings and are stored in a
is a series of fixed or variable components. A fixed speech memory of the OCANEQ module
component consists of one or more text fragments. Text word
The variable component consists of text fragments is a spoken word, a pause or a tone.
which may be defined during runtime using the IN-
DAS parameters.
INDAS pause System components
consists of a pause fragment and is inserted to sep- INDAS consists of several software programs and one
arate INDAS phrases and to separate different lan- hardware component. The software programs are:
guage outputs within a multi-lingual ALINA
announcement. PC-CAPE
INDAS parameter OCANEQ service PC with OCANEQ service soft-
defines a variable part of an INDAS phrase. It points ware
to a group of INDAS words. The hardware component is:
INDAS word OCANEQ module
consists of a text fragment. One or two INDAS
words are assigned to every possible value of an A normal PC is used to design and control the an-
INDAS parameter; an INDAS word for normal nouncements using the software programs PC-CAPE,
speech melody and, if necessary, an INDAS word ALINA and the OCANEQ service software. The three
for lower tone variants. software programs can also run separately on different
PCs.

MML files with


announcement
ALINA
ALINA definitions

List of text
fragments

Operator PC

OCANEQ Transfer of text


PC-CAPE
Digitizing announcements service fragments
OCANEQ
software module
Cutting announcements into
text fragments

Assigning fragment numbers to


relevant speech fragment files
PC-CAPE service PC
Creating a load table

WAV-
audio files

Tone studio

PC- CAP files


CAPE

Operator PC

3
The procedure for generating and administrating new Verifying recorded data
announcements is as follows: To administer the announcements, operators have
The announcements and the announcement cata- to import the files generated by PC-CAPE to ALI-
log are created with ALINA. NA. These files contain information on the edited
All of the texts required for the announcement are voice fragments (required memory capacity, speak-
spoken, for example, onto tape in a sound studio er ID). This enables operators to see how much
and read into PC-CAPE. memory is still available on the OCANEQ module.
Using PC-CAPE, the announcements are record- ALINA also issues a warning if operators attempt to
ed, digitized and cut into text fragments. The frag- combine fragments spoken by different speakers in
ment number required as per announcement the same announcement.
catalog is also assigned to the relevant speech Administering distribution data
fragment file (creation of a load table). If several OCANEQ modules are installed, opera-
The OCANEQ service software is used for the tors can use ALINA to administer the total or avail-
transfer of firmware and fragments to the OCANEQ able memory capacity.
module on the basis of the load table supplied by Creating output files
the PC-CAPE. In addition to local transfer, external ALINA can generate various types of output file,
service PCs can be connected with the OCANEQ simplifying announcement administration tasks:
module by means of an ISDN dialed connection. MML command files
For checking the announcements stored in the ALINA creates the necessary MML commands
OCANEQ module operators can start an audible check to create or modify the announcement related
via specific MML commands. parts of the EWSD database (OCANEQ- and UI-
database), so that announcements can be acti-
ALINA vated or deactivated.
ALINA (Administration of Language data for Individual Fragment lists
Announcements) is the central component of INDAS. Fragment numbers are assigned automatically,
ALINA is used for the administration of announce- providing a link between text fragments and their
ments. At the graphical user interface (GUI), operators logical addresses. The information in the frag-
can define how text fragments are combined. ALINA ment list can be processed with PC-CAPE.
also provides access to existing data and to extensive Sample lists
documentation on the current status of the database. A sample list contains complete announcement
texts in the form of the sequence of fragment
Via a comfortable graphical user interface, ALINA pro-
numbers required to compose each announce-
vides possibilities for:
ment.
Administering system and customer announce-
Distribution lists
ments
The distribution list produced by ALINA shows
ALINA classifies announcements as either system
which speech version must be loaded to which
announcements or customer announcements. For
OCANEQ modules.
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.

4
PC-CAPE To create an individual announcement using PC-
The PC-CAPE software enables operators to create CAPE, the following steps must be performed:
and modify their own announcements flexibly and effi- Recording voice data
ciently. The main function of PC-CAPE is to record Using a microphone announcement texts can easi-
voice data, edit the data and convert it into a format ly be recorded directly in PC-CAPE. For phonetic
suitable for the OCANEQ service PC. The PC on which reasons, the required phrases must be spoken in
it runs must be equipped with a microphone, a sound complete sentences. To obtain good quality an-
card and headphones or active loudspeakers. nouncements, it is often advisable to have the an-
nouncement texts recorded on tape by a
A user-friendly interface supports the creation and edit- professional speaker at a recording studio. The re-
ing of announcement speech fragments. Written as a sult should be WAV-files, which can be used by PC-
Windows application, PC-CAPE produces a graphical Cape. The recorded data can be stored either in
representation of the voice file as an "envelope curve". WAV audio format or in PC-CAPE's own CAP for-
Texts can then be cut and excerpted as required. mat.
The PC-CAPE window is divided into two areas. The Processing voice files
top area shows the entire envelope curve, as an over- A typical voice file contains several minutes of spo-
view of the text currently being processed. In the bot- ken text. Using PC-CAPE, parts out of this large
tom area the envelope curve can be cut. In this way, quantity of voice data can then be cut and the se-
announcements to meet operators needs can easily be lected text sections can be stored, with a suitable
designed. 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.

5
OCANEQ service PC with OCANEQ service soft- Administration
ware
A PC or notebook with Windows NT 4.0 becomes an System administration
OCANEQ service PC by adding the OCANEQ service The following feature data can be administrated in
software. EWSD network nodes:
The OCANEQ service software contains a program creation of announcements
which rapidly loads text fragments and control firmware recording by means of traffic measurement
to the OCANEQ module. Connected locally, the For information on system administration please refer
OCANEQ service PC uses the Ethernet interface on to OMN:EXCH-SY.
the OCANEQ module. Alternatively, the OCANEQ
module can be loaded remotely via a dial-up ISDN con- Routing administration
nection. In this case, the OCANEQ service PC must be For information on routing administration please refer
equipped with an ISDN card. to OMN:EXCH-RO.
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.
Technical data
The OCANEQ header is the module's "visiting card",
PC-CAPE, ALINA, OCANEQ Service Software
providing information on the language version loaded in
the OCANEQ. Pentium PC (133 MHz or faster) with 32 Mbyte RAM
(recommended configuration) and 2 Gbyte hard disk

OCANEQ module Operating system Windows NT 4.0

The OCANEQ (Operationally Controlled Equipment for PC-CAPE also requires:


Sound card, Microphone, headphones or active loudspeakers
Announcement) comprises one module equipped with
OQANEC Service Software also requires: ISDN card (for remote
control logic and voice memory.
update) or ethernet card for local update
The OCANEQ module is installed in a user interaction
line/trunk group (UI-LTG) in place of a digital interface
OCANEQ
unit (DIU). Only one OCANEQ is permitted per LTG. It
has 63 announcement ports and is capable of storing Mounting location: 1 LTU slot per LTG

65535 addressable text fragments. For details on the Memory: 32/96/288 Mbyte = 70/210/630 minutes storage capacity
for announcements
hardware please refer to the description User interac-
tion LTG (UI-LTG) 65535 fragments (max. 1024 per announcement)
Local interface: Ethernet connector
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 EWSD
in an announcement is defined in a fragment list. Maximum 1 OCANEQ per LTG
Up to 10 OCANEQ variants per network node(i.e. OCANEQs with
different voice contents)
Call charge registration
Up to 4 languages per network node
The network operator uses an MML command to define
Any number of OCANEQs can be assigned to each OCANEQ
the charge data for announcements to be recorded variant
(see Operation Manual OMN:EXCHTA). Per OCANEQ variant up to:
The connection to INDAS can be recorded with auto- a total of 2500 standard announcements for all languages
including
matic message accounting (AMA) or pulse metering. 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 Hofmannstrae 51 D-81359 Mnchen
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