VoiceMail Alcatel

Alcatel-Lucent OmniPCX Enterprise
Communication Server
Voice Mail
Legal notice:
Alcatel, Lucent, Alcatel-Lucent and the Alcatel-Lucent logo are trademarks of

Alcatel-Lucent. All other trademarks are the property of their respective
owners.
The information presented is subject to change without notice.
Alcatel-Lucent assumes no responsibility for inaccuracies contained herein.
Copyright © 2014 Alcatel-Lucent. All rights reserved.
The CE mark indicates that this product conforms to the following Council
Directives:
- 2004/108/EC (concerning electro-magnetic compatibility)
- 2006/95/EC (concerning electrical safety)
- 1999/5/EC (R&TTE)

Chapter 1
Alcatel-Lucent 4645 VMS
Overview .................................................................................................... 1.1

Overview ........................................................................................................ 1.1
Architecture .............................................................................................. 1.2
Architecture ................................................................................................... 1.2
Alcatel 4645 voice mail characteristics .......................................................... 1.3
Capacities and limits ...................................................................................... 1.4
Voice Mail .................................................................................................. 1.4
Main voice mail services ................................................................................ 1.4
Voice mailbox characteristics ........................................................................ 1.5
Personal options (Administration and voice mailbox owner rights) ............... 1.7
Caller and answering machine mode ............................................................ 1.8
Other features ................................................................................................ 1.8

Notifying the user of messages ....................................................................1.10
Customizing 4645 voice guides ....................................................................1.10
Use of ports ..................................................................................................1.10
Voice mail system and PCX network ............................................................1.11
Hotel voice mailboxes ...................................................................................1.11
Automated Attendant ........................................................................... 1.11
General information ......................................................................................1.11
Automated Attendant Entry (AA Entry) .........................................................1.12
Automated Attendant Menu (AA Menu) ........................................................1.12
Ubiquity ..................................................................................................... 1.13

0-1

General information ......................................................................................1.13

Choices offered to the caller by the Ubiquity assistant .................................1.14
Ubiquity template design ..............................................................................1.14
Installation procedure ......................................................................... 1.15

Foreword ......................................................................................................1.15

ACTIS Locks .................................................................................................1.17

Setting up the Voice Mail Service (non-Duplicated System) ........................1.18

Setting up the Voice Mail Service (Duplicated System) ...............................1.22

Loading Voice Mail Voice Guides .................................................................1.23
Configuration procedure .................................................................... 1.24
Configuration ................................................................................................1.24
Configuring with the PCX Management Tool ...............................................1.25
Configuring by Telephone Set ......................................................................1.31
Ubiquity Detailed Management ....................................................................1.31
Maintenance ............................................................................................ 1.31
General .........................................................................................................1.31
vmail .............................................................................................................1.32
The Eva-tool command ................................................................................1.32
Incidents .......................................................................................................1.40
Chapter 2
IMAP Service
Overview .................................................................................................... 2.1

Overview ........................................................................................................ 2.1
Architecture .............................................................................................. 2.2
Configurations with a 4645 Voice Mail .......................................................... 2.2
Configurations with a 4635 Voice Mail .......................................................... 2.3
Detailed description .............................................................................. 2.4
Operating Principle ........................................................................................ 2.4
Licenses ........................................................................................................ 2.5
Limits ............................................................................................................. 2.5
Configuration procedure ..................................................................... 2.6
0-2

Overview ........................................................................................................ 2.6

Prerequisites .................................................................................................. 2.6
Basic Principles ............................................................................................. 2.6
Checking ACTIS Lock ................................................................................... 2.6
Putting Imapd Server into Service ................................................................. 2.7

Assigning IMAP Service Rights to the Users ................................................2.10
Configuring an IMAP account for a PC .........................................................2.11
Updating External Imapd Server ..................................................................2.11
Operation .................................................................................................. 2.12
Overview .......................................................................................................2.12
Procedure .....................................................................................................2.12
Chapter 3
VPIM Service
Overview .................................................................................................... 3.1

Glossary ........................................................................................................ 3.1
Overview ........................................................................................................ 3.1
Architecture of the VPIM service ................................................................... 3.2
Network Transparency of Voice Mail Features .............................................. 3.4
Limits of the VPIM service ............................................................................. 3.5

Related modules ............................................................................................ 3.5
Operating principle ........................................................................................ 3.5
Control of the VPIM service ........................................................................... 3.8
Overview ........................................................................................................ 3.8
Configuration for 4645 ................................................................................... 3.8
Configuration for 4635 ..................................................................................3.13
Configuration examples ...................................................................... 3.15
On the 4635 Voice Mail ................................................................................3.15
Operation .................................................................................................. 3.17
Overview .......................................................................................................3.17

0-3

Procedure .....................................................................................................3.17
Chapter 4
Centralized Voice Messaging
Overview .................................................................................................... 4.1

Introduction .................................................................................................... 4.1
Use ................................................................................................................ 4.1
Reference to the other modules .................................................................... 4.1
Stand-alone voice messaging system ........................................................... 4.2
Networked voice messaging systems ........................................................... 4.3
Centralised voice messaging system with integrated management .............. 4.4
Installing the voice messaging system .......................................................... 4.6
Installing ABC logical links ............................................................................. 4.7
Configuring the centralised messaging system ............................................. 4.7
Distribution to the entire network ..................................................................4.11
Maintenance ............................................................................................ 4.11
Vmail .............................................................................................................4.11
InitMevo ........................................................................................................4.11
Chapter 5
External Voice Mail (VPS protocol)
Overview .................................................................................................... 5.1

Overview ........................................................................................................ 5.1
Basic description ................................................................................... 5.1
Basic description ........................................................................................... 5.1
0-4

RSVP protocol ............................................................................................... 5.3

Message LED ................................................................................................ 5.4
Hunt groups ................................................................................................... 5.4
Voice mail on an ABC network ...................................................................... 5.5
Implementation procedure ............................................................................. 5.5
Checking licenses .......................................................................................... 5.5
Declaring signaling modes ............................................................................ 5.6
Declaring analog lines to the voice mail service ............................................ 5.6
Declaring set hunt groups .............................................................................. 5.7

Voice mail directory number .......................................................................... 5.7
Configuring the message LED ....................................................................... 5.8
Managing users with voice mail rights ........................................................... 5.8
Use on an ABC network ................................................................................ 5.9

0-5

0-6

1.1 Overview
1.1.1 Overview
The Alcatel 4645 voice mail system (or e-VA for e-Business Voice Application) has been
developed for integration in telephone systems running in an IP environment.
The Alcatel 4645 voice mail system is a multi-service voice application that primarily offers a
voice mail service. This voice mail service offers the following features:
- Voice mail features allowing:
• Callers to leave a message in a user's voice mail box when the user is busy or absent.
Users miss no calls, and their mailboxes can store up to 50 messages (depending on
configuration).
• The owner of a mailbox to send messages to other users
- Automated Attendant (automatic switchboard), providing all features allowing the voice
mail system to act like an attendant: answer incoming calls, transfer them to the requested
number and present general company information.
- Information messages, that enable a series of messages giving company information
(opening times, description of departments [marketing], etc.) to be played to callers.
Implementing this type of service involves configuring specific Automated Attendant
parameter settings.
- Ubiquity, enabling a caller to select various options (offered by an Ubiquity assistant)
when they cannot reach the requested user. The Ubiquity assistant is created by
configuring specific Automated Attendant parameter settings.
From R5.1, the following additional services are included in the voice mail service:
- The IMAP service, that allows a mailbox owner to consult voice mail from a remote PC
(e-mail client) connected via the IP network.
- The VPIM service, allowing several voice mail systems to be networked over the IP
network.
From R6.0, the Alcatel 4645 Starter Pack is available. Designed for stand-alone mid-market
sites, the 4645 Starter Pack is a reduced 4645 with the following characteristics:
- The 4645 is not on a separate CPU
- Applicable to 80, 150, and 250 Alcatel-Lucent OmniPCX Enterprise Communication Server
engines only
- No Alcatel-Lucent OmniPCX Enterprise CS redundancy
- No Networking
- Limited to 30 users
- Limited to two hours storage
The 4645 Starter Pack does not permit the following upgrades:
- Capacity

1-1
Chapter 1
!
- Number of languages
- To the Networking Value Pack
- To My Messaging
1.2 Architecture
1.2.1 Architecture
The 4645 voice mail system can operate on either:
- The same physical support as the Call Server: CS board or Appliance Server
- A dedicated server: CS board or Appliance Server
Note 1:
The CS board is inserted into an OmniPCX Enterprise and is composed of an XMEM daughter-board and
a hard disk.
In duplicated configurations and if it is located on the same physical support as one of the two
Call Servers, the 4645 voice mail service continues to run, whether the Call Server is in main
or backup mode.
Important:
The voice mail service cannot be duplicated (one voice mail service per system only). However,
voice mail data can be backed up (with or without mailbox messages) in a specific directory using
the swinst tool.
A single 4645 voice mail system can handle all the sets of an Alcatel-Lucent OmniPCX
Enterprise CS. These sets can be connected behind an OmniPCX Media Gateway or an ACT
Media Gateway.
The 4645 voice mail system can provide a centralized voice mail service on a private network
and be part of a distributed voice mail system.
The 4645 voice mail uses the IP network for transfer of voice flows. It only processes
G711-coded voice flows. If the other end of the voice flow cannot use this coding, compression
resources (INT-IP or GD MCV) are used to convert flows.
If the 4645 voice mail system is embedded on:
- The same physical support as the Call Server (main or backup), it has the IP address of
the support Call Server.
- A dedicated server, it has its own IP address.
Note 2:
This IP address is required by system management when the voice mail service is created. It is
mandatory whatever the system configuration used. In a duplicated configuration, it is used to designate
on which CPU (local or twin) the voice mail service is to run.
1-2

!
Figure 1.1: 4645 voice mail system on a dedicated CS board
1.2.2 Alcatel 4645 voice mail characteristics

The 4645 voice mail system differs from previous voice mail systems in that:
- The PC-MMC previously used for configuration has been suppressed and replaced by
management fully integrated with PCX management.

1-3
Chapter 1
!
- Messages and voice guides are stored on the hard drive.

For further information on specific 4645 voice mail system features, refer to the modules listed
below.
- For voice mail services, refer to the Alcatel-Lucent 4645 VMS - Voice Mail .
- For information on the automated attendant, refer to the Alcatel-Lucent 4645 VMS -
Automated Attendant .
- For information on Ubiquity, refer to the module Alcatel-Lucent 4645 VMS - Ubiquity .
1.2.3 Capacities and limits

The number of ports and hard drive capacity are not subject to a lock, and the number of
mailboxes is configured by each Call Server.
To allow supplementary services that require several mailboxes for each subscriber, such as
Ubiquity or Automated Attendant (AA), up to one thousand mailboxes can be created.
These mailboxes can be of the following types:
- Standard voice mailbox
- Guest voice mailbox
- Automated Attendant entry (AA entry)
- Automated Attendant menu (AA menu), that specifies actions corresponding to menu
options that the caller selects by pressing a key on the set keypad.
- System distribution List (SDL), that can contain up to fifty members (standard or guest
mailboxes).
Note:
There is no personal distribution list.
For each mailbox, the following parameters can be configured:
- The maximum duration of message recording
- The maximum number of messages allowed in the mailbox
- The maximum duration of the greeting message
Eight languages are offered for a system, but only one is offered free with the standard
version. The seven other languages are dependent on an ACTIS lock.
The numbering plan can comprise three to eight digits.
An audiomaster feature enables the various greeting messages to be customized (for
example, the company greeting message, the automated attendant menu).
The Ubiquity feature is controlled by an ACTIS lock. The number of Ubiquity users can be
increased using ACTIS locks.
The VPIM and IMAP services are loaded and controlled by an ACTIS lock.
1.3 Voice Mail
1.3.1 Main voice mail services
1-4

!
Voice mail services are used:

- To create standard or guest type voice mailboxes.
- To enable a voice mailbox to be accessed without a secret code via the Skip secret code
feature (this is the default programming for access to a hotel type mailbox).
To enable a variable length secret code of 3 to 8 digits.
- To transfer the caller to the Automated Attendant if there is no mailbox.
- For messages: to hear all, hear date and time, listen again (repeat), move back, move
forward, identify start and end, save, skip, forward a copy with an introduction, call sender,
answer (reply), pause, continue, cancel
- To record, pause, and continue to record a message.
- To enable Classes of Services to be customized for standard and hotel voice mailboxes.
- To send a message and acknowledge receipt.
- To provide user help, by configuring the dynamic function keys displayed on a UA set.
- To customize voice mailboxes with the following choices: three greeting messages,
notification, extension to absence mode, System Distribution Lists, the Ubiquity feature,
outgoing call notification.
- For two types of notification time management: one for standard messages and the other
for urgent messages.
- For automatic implementation of direct calls to the voice mailbox.
- For the hotel service : check-in, check-out, and wake-up.
- For multi-language guidance.
- For access to the Automated Attendant from the main menu.
- For on-line call recording.
1.3.2 Voice mailbox characteristics

A user who owns a standard voice mailbox can use the voice mail system to send messages
to other users without calling them directly. When a message has been created, a wide range
of processing capabilities are offered, both in voice mail and "answering machine" modes. By
calling a voice mailbox, the user can:
- Send messages
- Listen to messages
- Save messages
- Answer messages
- Call the sender of the message
- Send a copy of a message to other users
- Delete messages
Visual guidance, in addition to guidance by voice guides, is provided on sets equipped with
dynamic keys and a display.
Messages that reach the expiration date are automatically deleted without the user being
notified.

1-5
Chapter 1
!
1.3.2.1 Calling the voice mailbox

Calls are made:
- By dialing the prefix and/or directory number of the voice mail service (internal or external)
or by using the message key.
- Automatically at offhook (after a set time), when a new message has arrived.
1.3.2.2 Accessing a standard voice mailbox for the first time
At first access, users must change the original secret code and register their name.
1.3.2.3 Visual guidance
Visual guidance is available on sets equipped with a display, whether or not there are dynamic
keys. Sets with a display only (without dynamic keys) show message envelope data.
1.3.2.4 Notification
Users are notified of new messages in one of two ways:
- On the user set by either a flashing LED, an icon display, or a voice guide announcement.
- If notification forwarding is enabled, users can either call a forwarding number (internal or
external) and a voice message is played which informs them of new messages, or they
can call a pager service, followed by their pager number.
1.3.2.5 Consulting voice mail
This paragraph describes the features available to users when consulting their messages. For
specific information on implementation, refer to theAlcatel-Lucent 4645 VMS - Personal notes
(reminder) - Operating diagram.
The 4645 voice mail-specific Skip password feature allows users to access their voice mail by
direct call without having to enter a secret code. This function is enabled by default for hotel
mailboxes.
The Auto-play feature, configured in the user's COS (Class Of Services) profile, allows (while
accessing the mailbox) messages to be listened to automatically without using the main menu
voice guide. The user hears new messages first, then saved messages.
Messages can also be consulted in the main menu of the owner mailbox. Depending on the
user's choice, unread and saved messages or only unread messages are played.
While listening to a message, the user can:
- Return to the start of the message
- Move ten seconds back
- Pause and then continue to listen
- Move ten seconds forward
- Go to the end of the message
- Stop listening and return to the main menu
- Skip a message and go to the next one.
At the end of a message, the user can:
1-6

!
- Hear the entire message again

- Delete or save the message
- Send a copy of the message with an introduction
- Reply to the sender
- Users also hear the date and time at which messages were sent.
The 4645 voice mail also allows immediate call back to the sender via the main menu. This is
followed by the Options while listening feature. This feature, which is a supervised transfer,
informs users of transfer status and allows them to return to the menu if the set called is busy
or there is no answer.
1.3.2.6 Sending messages
Message processing comprises recording followed by addressing. Silences at the start and
end of the message are automatically deleted. While recording a message, the user can use
the pause, continue recording, delete, re-record, and end commands. With 4645 voice mail it
is not necessary to confirm recording and, during recording, the user can exit the session to
return to the main menu.
The message is sent by dialing the destination number or by spelling the recipient's name. For
a call made using "Call by name", the user is guided by voice guides.
4645 voice mail allows access to System Distribution Lists, if the corresponding right has been
granted by the administrator in the user's COS profile.
Before sending the message the user must confirm or modify the destination or delete it and
enter a new one.
4645 voice mail allows messages marked Urgent to be sent. This allows the recipient to
consult them before consulting regular messages. In addition, the notification cycle is shorter.
1.3.2.7 Acknowledgement and location of messages sent
Some time after a message has been sent, the sender can ensure the recipient has received
the message. The voice mailbox plays messages that have not been consulted. Messages can
be checked one by one.
1.3.2.8 Recording during a call
If the administrator has granted this right to the user in the phone features categories, a
specific dynamic key is displayed during calls on UA sets. Pressing this key starts recording;
pressing the Stop recording key stops recording (recording will also stop when the time allotted
for recording on-line messages runs out).
During recording, the appropriate dedicated dynamic keys can be used to reset, stop, or
resume recording.
1.3.3 Personal options (Administration and voice mailbox owner rights)

Voice mailbox owners can:
- Record or modify their name
- Record and modify all personal greeting messages (from one to three). Maximum duration
for each greeting message is from ten seconds to five minutes (30 seconds by default).*
- Select and activate one of the greeting messages

1-7
Chapter 1
!
- Change their secret code *

- Select the type of signal for new messages (none, notification only, or full access) *
- Record or modify the Extended absence message
Note:
If Extended absence is enabled, the caller hears the greeting message but cannot leave a recorded
message. The call may be transferred to the attendant.There is no key to toggle this mode on/off.
- Record or modify their greeting on busy message, as well as the Ubiquity greeting
message.
*: These options are configured by the administrator in the COS associated to the user voice
mail.
The administrator also configures call notification, which includes determination of time cycle,
phone number, and the user pager number for pager services 1 and 2.
1.3.4 Caller and answering machine mode

If a user cannot answer a call and has enabled forwarding to their voice mailbox, the call is
transferred to the mailbox. The caller is guided in different ways, depending on whether or not
Ubiquity is enabled.
If Ubiquity is not enabled, the voice mailbox operates as follows:
- If forwarding on no answer or immediate forwarding is programmed, callers hear the
personal greeting message and are requested to leave a message. At the end of the
message, answering machine mode options are available: callers can listen to the
message again (repeat), confirm recording, hang up, or delete and re-record the message.
4645 voice mail also allows callers to mark their messages as Urgent.
- If forwarding on busy is programmed, callers hears a busy greeting message (default or
customized), and are requested to leave a message. At the end of the message,
answering machine mode options are available.
Note:
If the forwarding set is a multi-line set, the caller will hear the busy greeting message only if all set
lines are busy.
- Answering machine mode recording and end of message options are available while
callers are recording their messages. By using either the 0 or 9 keys, callers can reach the
attendant and request help with saving the message.
If the caller hangs up, either during or after recording, the message is saved.
For information on Ubiquity, refer to the Alcatel-Lucent 4645 VMS - Ubiquity .
1.3.5 Other features

1.3.5.1 Dial (call) by name
An internal mailbox can be reached by pressing the # key and entering the corresponding
name (standard mailbox name, AA Entry name, etc.), by using the keys on the set keypad (for
example, key 5 corresponds to the letters JKL). After the name has been entered, the mailbox
announces available names and the user selects the recipient.
This type of call can be used:
1-8

!
- For sending a voice message to a voice mailbox (by the owner of a voice mailbox or an
attendant).
- With the Automated Attendant, to reach a user who owns a corresponding voice mailbox or
an AA menu.
- To leave a message in a mailbox
1.3.5.2 Wake-Up
All wake-up operations are performed by the PCX. The voice mailbox only plays the wake-up
voice guide.
1.3.5.2.1 Programming wake-up calls
The user enters the wake-up prefix. The user is guided to enter the desired wake-up time and
(optionally) the call number of the set concerned. The user is then connected to a voice
mailbox that confirms wake-up time and that the wake-up call has been recorded. This
announcement is repeated three times (if the user does not hang up).
Wake-up time is stored in the PCX.
1.3.5.2.2 Making wake-up calls
The PCX connects to the voice mailbox. All wake-up calls programmed for the same time and
to be made in the same language are transmitted on the same port of the voice mailbox. When
the user off hooks, the voice mailbox plays a voice guide with a reminder that a wake-up call
has been programmed and gives the programmed time.
Note:
The 4645 voice mail provides a voice guide to confirm wake-up time.
1.3.5.3 System Distribution Lists (SDLs)

If System Distribution Lists rights have been granted, mailbox owners can send voice mail to
lists of people, either by entering the list number or spelling its name. User rights to SDLs are
granted by the administrator.
SDLs are addressed in the same way as voice mailboxes, because they have a phone number
and a name. With a secret code, these lists are created or deleted by the administrator in the
same way as voice mailboxes. The administrator manages list content. Each list can include
up to fifty recipients.
Note:
There is no personal distribution list.
1.3.5.4 Distribution service

The administrator can record a general distribution message from a system set, using a
specific mailbox. This message will be played to all users owning a voice mailbox (whether
administrator configured or customized).
When the message has been sent, the set LED flashes to notify mailbox owners of its arrival
(the set does not ring). Users can only listen to the message when connected to their voice
mailbox.
1.3.5.5 External information and audiotex service
Info-Boxes are created using an AA menu type mailbox. Info-Boxes cannot be concatenated.

1-9
Chapter 1
!
These boxes allow a series of company information messages to be distributed to the caller
(sectors of activity, opening times, etc.).
1.3.5.6 Managing a voice mailbox secret code
When the voice mailbox is created, its secret code is the same as for the set. This provisional
secret code can be changed by the administrator and is then sent to the mailbox as the initial
mailbox secret code.
For a standard voice mailbox, the secret code must be modified the first time the mailbox is
accessed. The secret code for the set and the new mailbox secret code are subsequently
handled separately, and the subscriber can change either independently.
In the event of a forgotten his secret code, the administrator can assign a new provisional
secret code using Eva-tool.
For a hotel guest mailbox, the secret code is activated when the guest checks in. This secret
code is always identical to the password for the set and cannot be modified by the guest.
1.3.6 Notifying the user of messages

The owner of a mailbox is informed of a new message by a LED flashing on the set.
- For 4004 and 4010 sets: the flashing red LED indicates unconsulted messages in the
mailbox. A steady red LED indicates that there are only saved messages in the mailbox.
- For 4020, 4035, 4038, and 4068 sets: the flashing green LED and message icon indicate
unconsulted messages in the mailbox. LED OFF and message icon ON indicate that there
are only saved messages in the mailbox.
Note:
On UA sets with a display, when there are new (unconsulted) messages, pressing the Message key will
display the number of messages.
1.3.7 Customizing 4645 voice guides

Customized voice guides (company greeting, Automated Attendant main menu, etc.) can be
either recorded in a studio or, for better quality, with the Alcatel Audio Station.
Each recording generates a new G.711 sampling file. The administrator must then import this
file from the hard drive using the Eva_tool command.
During the import, the customized message is added to the voice message file and replaces
the previous message, which can be the default message or a message recorded from a set.
Deleting the customized message results in the default message being restored.
1.3.8 Use of ports

All declared ports that are free can be used for incoming calls. If there are outgoing calls, a
minimum number of ports must be available for incoming calls.
The following rule applies:
1-10

!
The maximum number of ports used simultaneously for outgoing calls must be less than or
equal to the number of declared ports divided by two.
Example:
For a voice mail system with eight ports declared, 4 can be simultaneously used for outgoing calls.
1.3.9 Voice mail system and PCX network

The 4645 voice mail system is designed to be installed in a PCX network (ABC network) as a
centralized or distributed voice mail server.
The 4645 voice mail system can co-exist with a 4635 voice mail system, provided there is not
more than one voice mail system per network node.
1.3.10 Hotel voice mailboxes

This type of mailbox is easy to use. The secret code is not required when it is called from the
assigned room set, but is required when it is accessed from any other set.
Messages are played automatically and only a limited number of options are available: skip
message, hear again (repeat), delete, and date and time of reception.
Note:
As an option, guests can record their name.
Check-in: when a new guest checks in, the mailbox is automatically created with the same
secret code, same number and same language as the room set assigned.
Check-out: when the guest leaves, the mailbox is closed (messages can no longer be left) and
unconsulted messages are deleted.
1.4 Automated Attendant
1.4.1 General information

The 4645 voice mail system has an Automated Attendant feature that can be used to
- Answer calls
- Execute transfer to requested number
- Broadcast information messages concerning the company
To do this, the Automated Attendant uses two specific voice mailboxes:
- The Automated Attendant Entry or AA Entry mailbox
- The Automated Attendant Menu or AA Menu mailbox
The following features are available:
- Language selection
- Automated Attendant menu direct call from its call number
- Supervised or blind transfer
- Call pre-routing: company greeting or good bye message

1-11
Chapter 1
!
- Configuration of a powerful Automatic Attendant by using two basic building blocks (AA
Entry and AA Menu) to create multiple entry points.
The 4645 voice mail system enables the administrator to configure a multiple entry, multiple
level Automated Attendant tree structure.
The basic building blocks for an Automated Attendant are AA Entry and AA Menu.
1.4.2 Automated Attendant Entry (AA Entry)

This is the Automated Attendant entry point. This entry has a company greeting message,
language selection (optional), and usually a reference to an AA Menu or to a voice mailbox.
A caller usually reaches the Automated Attendant from a virtual set with immediate forwarding
to AA Entry. When the call arrives, the company greeting message is played and an (optional)
voice guide helps the caller to select a language before transferring the call to AA Entry.
The administrator can customize the AA Entry greeting by consulting it, as for a regular voice
mailbox, with a secret code. The administrator records the company greeting message to be
played when a call is received. To simplify identification, the AA Entry can have a recorded
name. If no customized company greeting message has been recorded, the default greeting
message is played.
While the company greeting message is played, callers can press the # key to consult their
mailbox. They must then enter the mailbox number and secret code. This feature (voice
mailbox access using the # key) can be disabled by the administrator. In this case, the function
of the # key is to skip the company greeting message.
1.4.3 Automated Attendant Menu (AA Menu)

The AA menu allows a caller to be connected to different destinations according to the
configuration determined by the administrator. A connection destination can be configured for
each key (keys 0 to 9). A final connection destination (the attendant) can also be configured,
for when the caller does not respond to the menu prompt (after the options have been
repeated a second time).
Connection destinations are:
- Not used: the key used has no function
- Transfer by entering the number: the caller can enter the number or select the key
corresponding to this type of connection. This activates a voice guide requesting the caller
to enter the number
- Transfer by entering the name: the caller enters the name of the called party using the
keys on their set keypad. Only destinations for which the name is recognized can be
selected: for example, a voice mailbox, AA Entry, or the AA menu. Transfer destinations
with no associated voice mailbox are not included in the Call by name tree structure.
- Transfer to a pre-selected number: number preconfigured by the administrator
- Transfer to attendant: by using a key (0 to 9)
- Leave a message in a voice mailbox (or change AA menu) by entering number: the caller
enters the number and is connected to the voice mailbox (or AA menu) specified
- Leave a message in a voice mailbox (or change AA menu) by entering name: using the
DTMF keys, the caller enters the number and is connected to the voice mailbox (or AA
menu) specified
1-12

!
- Leave a message in a voice mailbox (or change AA menu) by entering a preset number:
number preconfigured by the administrator
- Hangs up,
- Back: the call is redirected to its previous destination (for example, the last AA menu) or
exits the voice mailbox.
A transfer can be performed in two modes:
- blind transfer: transfer is performed without control on the status of the called party. The
benefit is to release the voicemail resources as soon as the transfer is initiated. In case of
failure (for example because the called party is busy):
• if the calling party is external, the call is routed according to the entity table of the
called party
• if the calling party is internal, the call is released
- supervised transfer: in case the transfer can not be carried out, the voice mail system
informs the user about the status of the destination. Cause of failure may be:
• the called party is free but does not answer before supervised transfer timeout has
occured
• the called party is busy
• the called extension does not exist
• you are not allowed to call this number
The transfer mode is a configuration parameter of the voice mail box.
The function of the * key is predetermined to redirect the call to the last menu (planned AA
menu, exit the voice mailbox). The function of the # key, if not disabled by the administrator, is
preconfigured for mailbox consultation.
If keys 0 and 9 are not configured or there is an AA menu operation error (no caller response
to the menu prompt), the caller is transferred to the attendant.
The administrator can customize AA menu announcements by consulting the AA menu with a
secret code (in the same way as for a standard voice mailbox).
For each language installed, the AA menu has an announcement that requests the caller to
select an entry key.
Recording the customized greeting messages used by the AA menu is the administrator's
responsibility. If messages are not customized, the default messages will be used.
1.5 Ubiquity
1.5.1 General information

Ubiquity is used to offer callers choices when they cannot reach the person called. These
choices are offered by the Ubiquity Assistant, an AA Menu type voice mailbox.
The Ubiquity feature is configured from the 4645 voice mail system. It only applies to standard
mailboxes, and is used to:
- Provide a default greeting message if no customized greeting message has been recorded
- Create an Ubiquity Assistant profile with a combination of soft keys
- Create nine transfer destinations, configured by the administrator

1-13
Chapter 1
!
- To program a mobile number (by the administrator)

- To program a mobile phone using a dedicated prefix (by the user)
The Ubiquity feature allows a voice mailbox owner to customize the mailbox help menu (usin
the AA menu). The help menu is used to guide a caller by offering a choice of different
forwarding destinations. The Ubiquity feature is enabled by using one of the forwarding
prefixes (immediate, on busy, etc.), followed by the Ubiquity assistant prefix number, or by
pressing the corresponding dynamic key on the UA set. If Ubiquity forwarding is not enabled,
regular voice mailbox operation is used. The user cannot enable the Ubiquity forwarding
feature unless rights to this feature have been granted by the administrator.
Using the Ubiquity assistant prefix, the user can (for direct calls) reach the Ubiquity assistant
for their mailbox to record a personal Ubiquity greeting message instead of using the default
(existing) message.
When there is an incoming call, the customized Ubiquity greeting message (if there is one) is
played, otherwise the default message is played. The caller selects one of the options offered
and (after a timeout has elapsed) can leave a message.
1.5.2 Choices offered to the caller by the Ubiquity assistant

The following choices can be offered to a caller by the Ubiquity assistant:
- Up to nine transfer destinations (if they have been configured by the administrator), using
keys 1 to 9. A transfer destination is configured in three steps:
• In the Ubiquity Assistant template object, fill in Transfer type with the Local number
type for an internal or external number, and Voice mailbox number type if the transfer
destination is the owner of the mailbox. By default, keys 1 to 3 are configured as the
local number, and keys 4 to 9 as Option not used.
• If the transfer destination is a local number, the administrator must have specified it in
the Ubiquity assistant template object. This number may be a phone number or an
Ubiquity service prefix.
• If the transfer destination is an Ubiquity prefix number, the administrator must complete
the Mobile number field or Contact number field (or both) for each Ubiquity subscriber.
- By entering the Ubiquity mobile programming prefix, the owner of the mailbox, after
entering their secret code, can customize the greeting message played to callers when
they are connected to the mailbox Ubiquity assistant.
- By entering the "Ubiquity Assistant" prefix, the owner of the mailbox can listen to the
greeting message recorded (this is an AA menu). To customize this menu, mailbox owners
must call their mailbox and enter the number of the AA menu that activates the Ubiquity
assistant. They can then, after entering their secret code, follow the voice guide to
customize the AA menu greeting.
1.5.3 Ubiquity template design

The Ubiquity template is designed to allow the Ubiquity template prefix to be created in the
numbering plan:
- This prefix number is dialed by the user as a forward destination number on Ubiquity
(which is an AA menu). In the Ubiquity Assistant, the function associated with each digit
can be specified; for example, a mobile phone, contact, voice mailbox, etc.).
- The Ubiquity template is internally linked with an AA menu which allows the administrator
to record a Ubiquity greeting message in the Ubiquity template AA menu. This is done by
1-14

!
calling the voice mailbox and consulting the AA menu linked with Ubiquity template.
- The Ubiquity template can be used as a template for each Ubiquity subscriber with the
same combination of digits (mobile phone, contact, voice mailbox, etc.) and the same
Ubiquity greeting message. Each Ubiquity subscriber can customize this greeting
message. The Ubiquity subscriber and Ubiquity templatet are linked in the Ubiquity
subscription object.
A caller who reaches the Ubiquity assistant can select to leave a message or wait for an
Ubiquity automatic transfer to the subscriber's voice mailbox. On the subscriber's voice
mailbox, a voice guide requests the caller to leave a message after the audio signal (beep).
When the Ubiquity greeting message has not been customized by the owner of the mailbox,
the default greeting message (“To leave a message for [mailbox owner name], press one.“) is
played. This message is not played if the mailbox is configured in extended absence greeting
message mode.
A transfer destination can be configured by the administrator, as Not used. In this case, the
associated key (from 1 to 9) has no function.
When the Ubiquity greeting message has not been customized, content of the default greeting
message depends on transfer destination type:
- When the name has been recorded and the transfer number is an internal number
associated with a mailbox, the message played is: ”To transfer to [mailbox owner name],
press two.”.
- When the name has been recorded and the transfer number is an internal or external
number, but the transfer destination is not available, the message played is: “To transfer to
extension <1234>, press two.”.
Note:
The caller can reach the attendant at any time by entering 0 or 9, but this option is not announced by
the voice guide.
The number of Ubiquity subscribers is controlled by an ACTIS lock.
1.6 Installation procedure
1.6.1 Foreword
This module describes the 4645 voice mail installation procedure, that may be broken down
into two steps:
1. Setup of the voice mail service, whether on a duplicated system or not.
2. Loading voice mail voice guides to the system.
This first step may vary somewhat according to site hardware configuration, namely, whether
the 4645 voice mail service and the Call Server are located on the same CPU or not.
1. The 4645 voice mail service and Call Server are located on the same CPU. The hardware
configuration will therefore be:

1-15
Chapter 1
!
Note 1:
The Call Server and 4645 voice mail service can also be located on an Appliance Server. The
installation procedure remains identical.
2. The 4645 voice mail service and Call Server are located on two different CPUs. The
hardware configuration will therefore be:
1-16

!
Note 2:
The Call Server or 4645 voice mail service can also be located on an Appliance Server. The
installation procedure remains identical.
In both cases, the installer must have the following to configure 4645 voice mail:
- either a VT100 console (Hyperterminal) locally connected to the CPU(s),
- or a PC with an Ethernet link to the company LAN (Telnet).
Whatever the hardware configuration used, make sure the CPU(s) concerned by installation of
4645 voice mail are already correctly loaded with the software required for installation. If this
operation has not been performed, refer to the CD-ROM containing the required software
version, the installation tool, and documentation covering software loading.
For 4645 voice mail limits and operating status, see the ACTIS locks configured for the system
in the following section.
1.6.2 ACTIS Locks

There are five Actis locks for the 4645 voice mail service. These are:
1. lock 178-EVA_engine, which indicates whether the system has a voice mail service or
not. There are two possible states: 0: no voice mail installed / 1: voice mail installed (2 for
the 4645 Starter Pack).
2. lock 179-EVA_vm_box, which indicates the number of mailboxes available on the system.
This number of mailboxes varies according to size of the system. Possible values are 30
(for the 4645 Starter Pack) 80, 150, 250, 500 and Open given that, for the latter, the
maximum value is 1000.

1-17
Chapter 1
!
3. lock182-EVA_network, which indicates whether the system has a networked 4645 voice
mail service or not. There are two possible states: 0: internal voice mail / 1: networked
voice mail (0 only for the 4645 Starter Pack).
Note 1:
This lock concerns the VPIM service.
4. lock 183-EVA_add_lang, which indicates the number of languages available for 4645
voice mail (the first language is provided free). The maximum number is 8 (0: one
language). For the 4645 Starter Pack, only 0 is permitted.
5. lock 194-EVA_PORTAL_VALUE, which indicates the number of 4645 mailboxes with portal
access. This number is incremented in steps of ten (nb x10). This lock number must be
more or equal to that of lock 179-EVA_vm_box. For the 4645 Starter Pack, the lock
number cannot exceed 30.
Note 2:
This lock concerns the IMAP service.
To display lock state, proceed as follows:

From the CS CPU prompt, enter the command spadmin -m.
(1)xa000000> spadmin -m
Display current counters ........................... 1
Display active file ................................ 2
Check active file coherency..........................3
Install a new file ................................. 4
Read the system CPUID .............................. 5
Add a CPUID .........................................6
Remove a CPUID ......................................7
Display active and new file ........................ 8
Display OPS limits ................................. 9
Exit ............................................... 0
choice: 2
Select menu 2, then press the Enter key on the keyboard to go to the next screen:
Example:
Hit to continue !
163-NiceCentralRecNode : p1: 9999
164-NiceRemoteBChanRec : p1: 9999
165-Release4400 : p1: 30
........
176-IPUser : p1: 9999
177-SIPUser : p1: 9999
178-EVA_engine : p1: 1
179-EVA_vm_box : p1: 500
181-OmniPcxEnterprise : p1: 1
182-EVA_network : p1: 1
183-EVA_add_lang : p1: 5
184-IntegGateKeep : p1: 9999
185-SIPGateway : p1: 9999
Hit to continue !
All 4645 voice mail locks and their respective values can be displayed from this screen.
In the example, the system has a networked voice mail system. It can provide 500 mailboxes
and play voice guides and announcements in 5 languages (once configured).
1.6.3 Setting up the Voice Mail Service (non-Duplicated System)

1.6.3.1 Configuration with the Call Server and 4645 Voice Mail on the Same CPU
1-18

!
Note 1:
To simplify, the CPU on which the Call Server and 4645 voice mail service are located is referred to as
the "Enterprise CPU". This CPU can also be an Appliance Server.
Caution:
take into account the fact that the Call Server is already operating on the CPU involved (phone
started).
From the ">" prompt by the Enterprise CPU, initiate the 4645 voice mail procedure as follows:
- Step 1: declare the 4645 voice mail in management system (this step is described in
Alcatel-Lucent 4645 VMS - Configuration procedure - Preliminary Remarks). Then validate
to ensure that the system will take into account the modifications. This action triggers the
voice mail commissioning.
Remarks:
Two of the parameters impact voice mail installation. They are:
• the voice mail directory number: once a number is given to the voice mail system, it
is automatically created as aAlcatel-Lucent OmniPCX Enterprise CS virtual "EVA
board". This allows to check its operating status.
Note 2:
This "EVA board" is seen in shelf 18 in the same way as the GD board.
• The name of the CPU on which the voice mail will operate.: In this configuration,
the name must define the Enterprise CPU (for example: cpu_ent).
Note 3:
This parameter can also be completed with CPU IP address (for example, 192.168.4.52).
- Step 2: checking voicemail commissioning.
From the Enterprise CPU prompt, enter the command Config 18, as shown below:
(E)cpu_ent> config 18
+-------------------------------------------------------------------------+
| Cr | cpl | cpl type | coupler state | coupler ID |
|----|-----|--------------|--------------------------|--------------------|
| 18 | 0 | GD | IN SERVICE| NO SHELF on CR |
| 18 | 1 | EVA | INITIALIZATION 2 RUNNING| NO SHELF on CR |
+-------------------------------------------------------------------------+
.........
(E)cpu_ent>
From the Enterprise CPU prompt, enter the command Config18, to check that 4645 voice
mail is becoming operational.
(1)cpu_ent> config 18
+-------------------------------------------------------------------------+
|----|-----|--------------|--------------------------|--------------------|
| 18 | 1 | EVA | IN SERVICE| NO SHELF on CR |
+-------------------------------------------------------------------------+
.........
(1)cpu_ent>
- Step 3: Once this is completed, also check that the eva.cfg file is present under /usr3/mao.
This file gives the IP addresses of the Call Server and 4645 (eva) voice mail. These
addresses must always be specified as the Call Server and 4645 voice mail system are
located on the same CPU.

1-19
Chapter 1
!
Example:
(E)cpu_ent> cd /usr3/mao
(E)cpu_ent> more eva.cfg
callserver1 = 192.168.4.52
eva = 192.168.4.52
1.6.3.2 Configuration with the Call Server and 4645 Voice Mail on two Different CPUs
Note 1:
To simplify, the CPU where the voice mail service is located is called CPU 4645. Likewise, the CPU
where the Call Server is located is called CPU CS. Either of these CPUs may be an Appliance Server.
The procedure remains identical.
Caution 1:
- For the CPU 4645: Check CPU board micro-switch settings before starting up. Remove the
board and check the micro-switches are set as shown: (ON/OFF/OFF/OFF), then re-
install the board. Micro-switch configuration will determine type (CS or GD) of CPU board
(CS in this example).
- For the CPU CS: take into account the fact that the Call Server is already operating on the
CPU CS (phone started).
Once the CPU 4645 has been started and the installer logged on, the voice mail
commissioning procedure can be started from the ">" prompt. To do this, follow the steps
described below:
- Step 1: since the Alcatel-Lucent OmniPCX Enterprise CS is installed in the IP environment
of a client, it is necessary to execute the following operations under Netadmin:
a. declare the name and IP address of the CPU 4645, as well as the subnetwork mask
value:
From the 4645 CPU prompt, enter the command netadmin -m, as shown below:
(E)xa000010> netadmin -m
Alcatel e-Mediate IP Network Administration
===========================================
1. 'Installation'
2. 'Show current configuration'
3. 'Local Ethernet interface'
4. 'CPU redundancy'
5. 'Role addressing'
6. 'Serial links (SLIP/PPP)'
7. 'Tunnel'
8. 'Routing'
9. 'Host names and addresses'
10. 'Copy setup'
11. 'Security'
12. 'DHCP configuration'
13. 'SNMP configuration'
14. 'VLan configuration'
15. 'History of last actions'
16. 'Apply modifications'
0. 'Quit'
What is your choice ?
1-20

!
Then select menu 1. 'Installation' and follow the instructions displayed on screen to
successively enter:
• 4645 CPU name (e.g.: cpu_4645),
• CPU 4645 IP address (e.g.: 192.168.4.53),
• subnetwork mask (e.g.: 255.255.255.0).
Once this step is completed, return to main menu.
b. declare the physical IP address and name of the CPU CS in the CPU 4645 Host file:
Remaining under Netadmin, successively select menu9. 'Host names and
addresses', then menu 2. 'Add/Update'. Then follow the instructions displayed on
screen to enter CPU CS IP address and name.
Once this step is completed, return to main menu.
Caution 2:
This operation must be repeated for the CPU CS. The IP address and name of the CPU
4645 must be specified in the CPU CS host.
c. Declare the main IP address if it has been previously managed at CPU CS level. This
step is documented in the netadmin - Operation - Role Addressing.
- Step 2: enable telephone automatic start on CPU 4645.
From the CPU 4645 prompt, enter the command exit. Under the connection login, enter
swinst, then the password.
From swinst, select in turn menu 2 Expert menu, 6 system management and 2
Autostart management. Follow the instructions on the screen.
- Step 3: declaring the 4645 voice mail in the CPU CS system management parameters.
This step is documented in Alcatel-Lucent 4645 VMS - Configuration procedure -
Preliminary Remarks.
Remark:
Two of the parameters impact voice mail installation. They are:
• the voice mail directory number: once a number is given to the voice mail system, it is
automatically created in the Alcatel-Lucent OmniPCX Enterprise CS as a virtual "EVA board".
This allows to check its operating status.
Note 2:
This "EVA board" is seen in shelf 18 in the same way as the GD board.
• the name of the CPU on which the voice mail will operate: In this configuration, the name
must represent the 4645 CPU (for example: cpu_4645). The voice mail service will operate after
the CPU 4645 has been re-initialized (see step 5).
Note 3:
This parameter can also be completed with CPU IP address (e.g. 192.168.4.53).
From the CPU CS prompt, enter the command Config 18, to check the presence of 4645
voice mail.

1-21
Chapter 1
!
(E)cpu_cs> config 18
+-------------------------------------------------------------------------+
|----|-----|--------------|--------------------------|--------------------|
| 18 | 0 | GD |REGISTERED NOT INITIALIZED| NO SHELF on CR |
| 18 | 1 | EVA |REGISTERED NOT INITIALIZED| NO SHELF on CR |
+-------------------------------------------------------------------------+
.........
(E)cpu_cs>
- Step 4: Check that the EVA_ONLY (on 4645 CPU only) and eva.cfg files in /usr3/mao are
present. The latter file gives the Call Server and 4645 voice mail IP addresses configured
previously (see step 1). This check must be performed on both CPUs.
Example:
(E)cpu_cs> cd /usr3/mao
(E)cpu_cs> more eva.cfg
callserver1 = 192.168.4.52
eva = 192.168.4.53
- Step 5: starting the CPU 4645.
From the CPU 4645 prompt, run the command shutdown -r now, as shown below:
(E)cpu_4645> shutdown —r now
......
- Step 6: After starting CPU 4645, check that 4645 voice mail is enabled.
From the CPU CS prompt, run the command Config 18 as shown below:
(1)cpu_cs> config 18
+-------------------------------------------------------------------------+
|----|-----|--------------|--------------------------|--------------------|
| 18 | 1 | EVA | IN SERVICE| NO SHELF on CR |
+-------------------------------------------------------------------------+
.........
(1)cpu_cs>
1.6.4 Setting up the Voice Mail Service (Duplicated System)

The actions described above are identical for a system with a duplicated Call Server.
However, during step 1, the physical IP address of the twin CS CPU must be declared (see the
Call Server duplication - Configuration procedure - Configuring the Twin Com Server).
Consequently, when checking that the eva.cfg file is present, the twin CPU CS IP address will
also be displayed. Main IP addresses for these two CS CPUs (local and twin) must also be
taken into consideration (see the Call Server duplication - Configuration procedure -
Configuring Role IP Addresses).
Example:
(E)cpu_cs> cd /usr3/mao
(E)cpu_cs> more eva.cfg
callserver1 = 192.168.4.52
callserver2 = 192.168.3.51
callservermain1 = 192.168.4.50
callservermain2 = 192.168.3.50
eva = 192.168.4.53
Caution:
when switching Call Servers, the 4645 voice mail automatically resets to confirm its operation
with the new Main Call Server.
1-22

!
1.6.5 Loading Voice Mail Voice Guides

1.6.5.1 Overview
When setup is complete, only one voice guide language file is installed by default on the
system for the voice mail service. This file is the GEA (Generic English Alcatel) language file.
To make voice guides in another language available, they must be loaded to the hard drive of
the voice mail CPU.
To do this, you need the CD-ROM. This contains:
- Voice guides in 40 languages (A law) and 20 languages (µ law). See: List of Available
Languages for Voice Guides
- The voice guide transfer tool (utility).
- The documentation explaining transfer tool installation and detailing the contents of the
CD-ROM (list of available voice guide languages, etc).
The transfer tool allows voice guide language files to be transferred from the CD-ROM to the
hard drive of the voice mail CPU (to the directory “/DHS3ext/vgeva”).
1.6.5.2 List of Available Languages for Voice Guides
Notes:
- Lc stands for the language code: extension of the voice guide language file
- Nb stands for the number of voice guides per language
table 1.16: List of Available Languages for Voice Guides
Language Lc Nb A Law µ Law
Arabic (Feminine voice) AR1 577 x
Arabic (Male voice) AR0 579 x
Cantonese CA0 574 x x
Catalan ES1 577 x
Croatian HR0 630 x
Czech CS0 628 x
Danish DA0 576 x
Dutch NL0 581 x x
English EN0 575 x x
English (Australia) AS0 579 x
English (United States) US0 579 x x
Finnish FI0 565 x x
Flemish NL1 578 x
French FR0 587 x
French (Canada) FR2 587 x x
German DE0 586 x x

1-23
Chapter 1
!
Language Lc Nb A Law µ Law

Greek GR0 590 x
Hungarian HU0 575 x
Icelander IS0 575 x
Italian IT0 583 x x
Japanese JP0 578 x x
Korean KR0 653 x x
Latvian LV0 622 x
Lithuanian LT0 607 x
Mandarin (China) CN0 578 x x
Mandarin (Taiwan) CN1 579 x x
Norwegian NO0 579 x x
Polish PL0 604 x x
Portuguese PT0 592 x x
Portuguese (Brazil) PT1 591 x x
Romanian RO0 576 x
Russian RU0 583 x x
Slovak SK0 588 x
Slovene SI0 583 x
Spanish ES0 584 x
Spanish (Latin America) ES2 598 x x
Spanish (United States) ES2 590 x x
Swedish SV0 577 x x
Turkish TR0 574 x
Valenciano ES3 581 x
1.6.5.3 Transfer Procedure

The procedure consists of two steps:
1. Transfer tool installation and use (opening a session).
2. Transferring voice guide files from the CD-ROM to the system.
These two steps are described in the Voice guides and music-on-hold - Voice guide transfer
software.
Caution:
When transfer is complete, remember to reset a virtual voice mail board using the rstcpl 18 1
command.
1.7 Configuration procedure
1.7.1 Configuration
1-24

!
The 4645 voice mail system is configured using the PCX management tool (extensive
configuration) or a telephone set (limited configuration).
There is no interaction between these two modes of configuration as the fields that can be
configured by one means cannot be configured using the other means.
1.7.2 Configuring with the PCX Management Tool

1.7.2.1 Preliminary Remarks
This section describes the standard configuration operations the installer must perform to
create the 4645 voice mail service only.
For detailed management of the 4645 voice mail system, refer to the Administrator Manual,
Alcatel-Lucent 4645 VMS - Overview.
1.7.2.2 Creating the 4645 Voice Mail Service
Caution:
- At creation, you assign a directory number to the 4645 voice mail service in the same way as
for system users. It is therefore necessary to take the system numbering plan into account so
as to avoid any conflict between voice mail service directory number and system user
directory numbers.
Procedure:
1. Select the object: Applications > Voice mail.
2. Select "Review/Modify" mode.
Attributes:
Voice Mail Dir. No. : Enter the 4645 voice mail directory number. 3 to 8 di-
gits.
Connection COS ID : Enter a connection category number. From 0 to 31.
This selection determines whether sets are author-
ized or forbidden to call the 4645 voice mail service.
Note:
A connection category compatible with those of voice mail
service subscribers must therefore be selected.
% of Authorized Camp-on : Enter the camp on percentage allowed. From 0 to
200.
This choice determines the number of camping calls
authorized on the voice mail service.
Example:
200% camp on calls on an 4645 voice mail service
equipped with 8 ports allows 16 simultaneous camping
calls.

1-25
Chapter 1
!
Directory Name : Enter the name identifying the 4645 voice mail ser-
vice. 1 to 16 digits and/or characters.
This name is shown on sets when they are:
- forwarding to their mailbox,
- connected to their mailbox.
Number Of Accesses : Leave the default value. Not significant in a 4645
voice mail context.
Voice Mail Type : Select: 4645.
Voice Mail Server No. : Assigning a unique identifier allows this voice mail
service to be identified on the VPIM network. Enter
this value even if the VPIM service is not used.
Justified : Select:
- Yes: all outgoing calls from the 4645 voice mail
service are taken into account by accounting.
- No: no outgoing calls from the 4645 voice mail
service are taken into account by accounting.
Voice Mail CPU Name : Enter the name of the CPU that supports the 4645
voice mail service.
This field must be completed whatever the system
configuration adopted. For a duplicated system, it will
specify on which CPU (main or backup) the voice mail
service is to run.
Other actions that can be performed on the 4645 voice mail service:
- Delete the voice mail service:
Procedure:
a. First make sure there are no mailbox owners, distribution lists and no Automated Attend-
ant for the voice mail service.
b. Select the object: Applications > Voice mail.
c. Select "Review/Modify" mode and enter the number of the voice mail service.
d. When voice mail service parameters are displayed, replace its directory number with the
string, "".
- Modifying the voice mail service:

Procedure:
a. First make sure there are no mailbox owners, distribution lists and no Automated Attend-
ant for the voice mail service.
b. Select the object: Applications > Voice mail.
c. Select "Review/Modify" mode and enter the number of the voice mail service.
d. When voice mail service parameters are displayed, make any modifications concerning:
• voice mail service directory number,
• type of voice mail service,
• voice mail CPU name.
Then confirm changes for them be applied by the system.
1.7.2.3 4645 Voice Mail Service Global Parameters

1.7.2.3.1 General
1-26

!
To complete declaration of the 4645 voice mail service, a series of global parameters must be
configured.
The operating mode of some of these parameters requires some explanation. This concerns:
- the languages used by the voice mail service,
- message notification by paging.
1.7.2.3.2 Languages Used
When a user connects to a voice mailbox, the language requested for playback of voice guides
and set display is sent to the voice mail system (in in the following diagram).
Remark:
The language assigned to the voice mailbox is one of the nationalities configured for the system. It is
formed by the combination of a display language and a voice guide language.
The voice mail system checks whether the language requested for the user's voice mailbox is
available in the list of languages that it offers (in ). There are two possible cases:
- the requested language is available. In this case, the voice mail service authorizes use of
this language when the mailbox is called (in in the following diagram),
- the requested language is not available. In this case, the voice mail service will designate
the language configured as default language as the language to be used when the mailbox
is called (in in the following diagram).
The organization of objects used to manage 4645 voice mail languages can be broken down
as follows:

1-27
Chapter 1
!
1.7.2.3.3 Notification by Pager

The 4645 voice mail system allows subscribers to be informed of the arrival of new messages
in their mailbox via a pager.
Two pager services (1 and 2) are offered to the subscriber when he programs notification type
on his set. After accessing his mailbox, the user puts one of the two numbers (#1 or #2)
identifying the pager service in front of his pager number.
Each message specifying pager service can be configured by the installer.
1.7.2.3.4 Configuring Global Parameters
1-28

!
Procedure:
1. Select the object: Applications > Voice Mail > Descend hierarchy > 4645 VM Global
Parameters.
2. Select "Review/Modify" mode.
Attributes:
Attendant key : Displays attendant key number, 0 or 9. This number
depends on country of installation.
This enables the caller to get help from an attendant
by pressing this key when the called party cannot be
reached or to request information.
Attendant Destination : Enter the number of an individual attendant group of
attendants or entity prefix.
This will be the destination when the caller presses
the attendant key described above.
Pager Script 1.1 : Enter the message that will be displayed on the sub-
Pager Script 1.2 scriber's pager when he is informed of new messages
Pager Script 1.3 in his mailbox. This represents pager service 1.
The message can comprise 60 characters maximum
on 3 parameter lines: Pager Script 1.1, 1.2 and 1.3,
each specified by 20 characters. The characters al-
lowed are 0 to 9, *, #, M, N and [ ] with:
- M : the user's mailbox number,
- N: the call number notification. This number cor-
responds to the number of the set from which the
user will be informed that new messages have ar-
rived in his mailbox.
Note 1:
this call number notification is managed from the per-
sonal options of the user's mailbox (see Alcatel-Lucent
4645 VMS - Personal options - Notification service).
- [ ] : pause that can be used when composing a
script (in tenths of a second).

1-29
Chapter 1
!
Pager Script 2.1 : Enter the message that will be displayed on the sub-
Pager Script 2.2 scriber's pager when he is informed of new messages
Pager Script 2.3 in his mailbox. This represents pager service 2.
The message can comprise 60 characters maximum
on 3 parameter lines: Pager Script 2.1, 2.2 and 2.3,
each specified by 20 characters. The characters al-
lowed are 0 to 9, *, #, M, N and [ ] with:
- M : the user's mailbox number,
- N: the call number notification. This number cor-
responds to the number of the set from which the
user will be informed that new messages have ar-
rived in his mailbox.
Note 2:
this call number notification is managed from the per-
sonal options of the user's mailbox (see Alcatel-Lucent
4645 VMS - Personal options - Notification service).
- [ ] : pause that can be used when composing a
script (in tenths of a second).
Administrator Password : Enter the password to access the system administra-
tion mailbox.
The password must contain at least 1 digit and a
maximum of 8 digits.
Note 3:
The actions offered by the system administration mailbox
are given in the Alcatel-Lucent 4645 VMS - Additional man-
agement.
Confirm : Enter the password again.
Timeout Supervised Transfer : Enter maximum wait time before the transferred call is
(sec) considered as failed if the called party does not off-
hook. From 10 to 120 seconds (default value 40).
Second Attempt Of Notif. : Enter wait time before which a second attempt at new
after(mn) message notification is made on the subscriber's set.
This follows a first attempt which the subscriber has
not taken account of. From 3 to 60 minutes (default
value 10).
Other Attempt Of Notif. : Enter wait time before a final attempt for new mes-
after(mn) sage notification is made on the subscriber's set.
From 3 to 60 minutes (default value 10).
Voice Mail Language 1 : Select one of the languages available for the voice
mail service. This first language will be used as de-
fault language for the voice mail service.
Voice Mail Language 2 : Same as above
.......... :
1-30

!
Trivial Password Allowed : False: obvious passwords (easily guessed) are re-
fused:
- Passwords that are the same as the mailbox
number
- Passwords that are the same as the mailbox
number in reverse order
- Passwords composed of a logical series of figures
(ex: 12345, 6543 or 13579)
- Passwords based on repetition of the same figure
- New password identical to the old password
True: obvious passwords (easily guessed) are autor-
ised.
1.7.3 Configuring by Telephone Set

The interface between the administrator and the embedded 4645 voice mail service is based
on sending DTMF digits from an analog set or messages generated on a UA set keypad. The
administrator is guided via menus and voice guides that confirm data, notify him of errors or
prompt him to enter data.
Note:
The administrator can "anticipate" voice guidance by entering configuration data before being prompted
to do so.
To get the voice mail administration menu, the administrator enters a mailbox number #
followed by *, # , or 00 and enters his administrator secret code.
"Configuration from a set" mode only allows limited configuration that allows:
- a message to be sent to all voice mailboxes in the voice mail system.
- to record (after selecting the number of the language to be used) "goodbye"
announcements and notification following message deposit announcements.
1.7.4 Ubiquity Detailed Management

For a detailed description of the Ubiquity feature, refer to the Ubiquity - Overview.
1.8 Maintenance
1.8.1 General
To handle 4645 voice mail service, the following commands (to launch on the system terminal)
have been developed or adapted.
- vmail: controls accesses (or ports) to voice mail and hence ensures it is operating
correctly. Note that vmail gives port status on the Call Server (and not 4645 side),
- Eva_tool: seen as a menu, it allows the manager to perform specific operations on voice
mail, such as deleting messages or mailboxes, changing the secret code for a mailbox,
resetting accesses to voice mail, etc.).
To back up 4645 voice mail data (with or without mailbox messages) in a specific directory, the
manager uses the swinst tool. The backup procedure is described in the Swinst - Operation -

1-31
Chapter 1
!
Backup and Restore.
1.8.2 vmail
Caution:
The vmail command must only be run after the PCX telephone application has fully started
(RUNTEL finished).
When prompted by the Call Server CPU, enter vmail as shown below:
Example:
(1)CPUA> vmail
Number of EVA access: 16
Voice mail number: 3333
Voice mail type: 6
Voice mail name: messagerie 4645
Equipment init: 1159 led: 1160
Link status OK
mr1 mr2 q23 0
neqt Free/B stat outserv nulog cristal cpl term incom outgo
1227 F OK 0 0 18 1 0 Y Y
1228 F OK 0 1 18 1 1 Y Y
1229 F OK 0 2 18 1 2 Y Y
1230 F OK 0 3 18 1 3 Y Y
1231 F OK 0 4 18 1 4 Y Y
1232 F OK 0 5 18 1 5 Y Y
1233 F OK 0 6 18 1 6 Y Y
1234 F OK 0 7 18 1 7 Y Y
1235 - KO 0 8 18 1 8 Y Y
1236 - KO 0 9 18 1 9 Y Y
1237 - KO 0 10 18 1 10 Y Y
1238 - KO 0 11 18 1 11 Y Y
1239 - KO 0 12 18 1 12 Y Y
1240 - KO 0 13 18 1 13 Y Y
1241 - KO 0 14 18 1 14 Y Y
1242 - KO 0 15 18 1 15 Y Y
Three parameters are used to indicated status of accesses (or ports) to voice mail. They are:
- the line Link status, which indicates whether the connection is established or not (see
example above: OK).
- the column Free/B set to:
• B: indicates that the port is busy,
• F: indicates that the port is free (see the example above),
- the column state set to:
• KO: indicates that the port is not in operation,
• OK: indicates that the port is in operation and available to receive incoming calls (see
the example above for the 8 voice mail accesses).
1.8.3 The Eva-tool command

1.8.3.1 Activation
Caution:
The Eva_tool command must only be run after the PCX telephone application has fully started
(RUNTEL finished). If the Eva_tool command is run when the telephone application is stopped,
the management menu displayed does not offer the manager the same options. The options
1-32

!
offered are exclusively reserved for Alcatel-Lucent support.

When prompted by the 4645 CPU, enter Eva_tool as shown below:
Note:
a language option allows to get the following menu in a number of different languages. Syntax is as
follows:
Eva_tool followed by country code (eg: FR0 for France, US0 for United States, etc.).
(E)eva> Eva_tool —l US0

MANAGEMENT TOOL
0 : Exit
1 : Delete a mailbox
2 : Modify a password
3 : Delete messages from mailbox
4 : Delete messages
5 : Dump nodes and mailboxes
6 : Reset a port
7 : Update led
8 : Status of line
9 : Disable lines after hanging up
10 : Force disable all line
11 : Enable all lines
12 : Interactif import of greeting
13 : Automatic import of greetings
14 : Mov_debug
Your choice :
Several options are offered:
- option 0 : End which is used to exit the management menu,
- options 1 to 13 are described below.
1.8.3.2 Option 1: Delete a mailbox
Option 1: Delete a mailbox allows the mailbox of a system user to be deleted. This
deletion is executed whatever the state of the mailbox when it is deleted, whether it contains or
not archived or unread messages. The mailbox "owner" set can also be on forwarding to the
voice mail service.
Example:
Your choice: 1
Enter mailbox's number
3000
The mailbox is deleted
1.8.3.3 Option 2: Modify a password

Option 2: Modify a password allows the secret code to the mailbox of a system user to
be changed. When this is done, the mailbox owner must first enter this modified secret code
before being allowed to use a new secret code.
Example:

1-33
Chapter 1
!
Your choice: 2
3001
Enter a new password (3 to 8 characters)
1234
The password of mailbox 3000 has been modified
1.8.3.4 Option 3: Delete all messages from mailbox

A first deletion level is suggested by option 3: Delete all messages from mailbox.
When launched, this option results in the total deletion of all messages unread or archived in
the mailbox.
Example:
Your choice: 3
3000
1.8.3.5 Option 4: Delete messages

A second deletion level is suggested by option 4: Delete messages. When launched, this
option suggests a series of sub-menus which allow you to target the messages to be deleted.
They are shown below:
1. sub menu 1 is used to select messages according to date and time of deposit.
2. sub menu 2 is used to select all messages or stored (archived) messages only.
3. sub menu 3 is used to select mailboxes from which to delete messages.
Example:
delete all archived messages left in mailbox 3000 after June 16, 2002
1-34

!
Your choice: 4
0 : Return
1 : Selection by time
2 : Selection by date of creation
3 : Selection by date and time
Your choice: 2
Enter limit date
All messages stored before this date will deleted
Enter the day (1-31)
16
Enter the month (1-12)
06
Enter the year (format yyyy)
2002
Among this messages, do you want to delete :
0 : Return
1 : Delete all messages
2 : Only stored messages
Your choice: 2
0 : Return
1 : All mailboxes
2 : By type of mailbox
3 : Only one mailbox
4 : An interval of mailboxes
Your choice: 3
3000
Treatment in the process
Treatment is finished
1.8.3.6 Option 5: Dump nodes and mailboxes

Option 5: Dump nodes and mailboxes allows access to all voice mail information,
whether part of an ABC network or not. This option offers a sub menu allowing you to select
the kind of information to access.
Your choice: 5
0 : End
1 : Dump nodes and mailboxes
2 : Dump local mailbox
3 : Dump local node
4 : Dump network mailbox
5 : Dump all
6 : Dump messages
Options are as follows:
- 1: Dump nodes and mailboxes: is used to list all declared voice mailbox on the node
(or nodes) using voice mail. Each mailbox will be listed with its name, number and mailbox
type.
- 2: Dump local mailbox: is used to access information on one mailbox and, in
particular:
• its name and directory number,
• its type (e.g. standard),
• data concerning its secret code,
• its class of services,
• which personal greeting, busy or absence message is currently in use for incoming

1-35
Chapter 1
!
calls,
• etc.
- 3: Dump local node: is used to access local node configuration, including:
• prefix number,
• voice mail access number,
• voice mail server name,
• voice mail domain name,
• network type: eVA network , eVA domain, non-eVA,
• minimum and maximum allowed numbers,
• network message encoding type,
• other information on secret code, IMAP, etc.
- 4: Dump network mailbox: this option is similar to option 2 with the difference that it
allows access to a mailbox belonging to a node different from local in the network.
- 5: Dump all: lists all information available from previous options.
- 6: Dump messages: lists all messages processed by voice mail with their arrival time
and duration.
1.8.3.7 Option 6: Reset a port
Option 6: Reset a port, is used to reset a port accessed via the vmail command (see
vmail ). With this option, all calls on arrival on the selected port are released.
Example:
Your choice: 6
Enter port's number
1
1.8.3.8 Option 7: Update led

Option 7: Update led, allows information (LED, voice mail dedicated function key, etc.) on
a set with a mailbox to be updated on the system side.
Example:
Your choice :7
3000
Treatment in progress
1.8.3.9 Option 8: Status of line

Option 8: Line status, allows all access paths to the voice mail service to be viewed by
specifying, for each path, its busy state (F: Free/B: Busy) and its operating state (OK: in
service (enabled)/NOK: out of service (disabled)).
Example:
1-36

!
Your choice: 8
nulog Free/Busy stat
0 F OK
1 B OK
2 F OK
3 F OK
4 F OK
5 F OK
6 F OK
7 F OK
1.8.3.10 Option 9: Disable lines after hanging up

Option 9: Disable lines after hanging up, allows all access paths to voice mail to
be put out of service when the last call in progress (connected to the voice mail service) is
released.
Example 1:
Your choice: 9
(*)
Treatment is finished:
All lines are disable
(*) : If one or more lines are busy (calls in progress), the following message is displayed:
Example 2:
6 7 busy
Where 6 and 7 are the access paths used by calls. The message only disappears when the
last call is released.
Once finished, you can check that access paths are out of service (disabled) with option 8:
Status of line This displays:
0 - NOK
1 - NOK
2 - NOK
3 - NOK
4 - NOK
5 - NOK
6 - NOK
7 - NOK
1.8.3.11 Option 10: Force disable all line

Option 10: Force disable all line, allows all access paths to voice mail to be put out
of service whatever the status of calls connected to the voice mail service (in progress or not).
Example:
Your choice: 10
All lines are disable
Note:
If there are calls in progress, they are cut off immediately. The users making these calls are requested to
hang up. If users subsequently attempt to make another call, they ring the called set with no overflow to
the voice mail system if this is programed (forwarding is not operational).
Once finished, you can check that access paths are out of service (disabled) with option 8:
Status of line This displays:

1-37
Chapter 1
!

0 - NOK
1 - NOK
2 - NOK
3 - NOK
4 - NOK
5 - NOK
6 - NOK
7 - NOK
1.8.3.12 Option 11: Enable all lines

Option 11: Enable all lines, is used to put all access paths to the voice mail system
back into service.
Example:
Your choice: 11
All lines are enable
You can check that access paths are in service with option 8: Status of line
1.8.3.13 Option 12: Interactif import of greeting
Option 12: Interactif import of greeting, allows the installer to replace one of the
messages available in a standard mailbox (greeting messages (1 to 3), etc.) with a new
message. The new message must have been previously recorded and transferred to the
system hard drive (via AAS or FTP) in *.wav file (G711 format (A or µ law) or 16 bits PCM
format).
The installer must then:
1. Select the standard mailbox.
2. Select the type of message to be replaced (greeting message (1 to 3), busy, extended
absence or the recorded name).
3. Specify the complete path for new message (*.wav file) address.
Note:
Before the complete path is entered, the format that the new message must be in is specified (see
the example below).
Example:
Your choice: 12
Enter number of the mailbox: 3000
0 : Return
1 : Personal_1 announcement
4 : Busy announcement
5 : Absence greeting
6 : Recorded name
1
Be careful, the format of file should be:
a G711 format, law A or Mu
or a linear format type PCM with 16 bits per sample
8000 samples per second for all files
Please name of file to up load (total path):
/tmp/annoncperso1.wav
1.8.3.14 Option 13: Automatic import of greetings
1-38

!
Option 13: Automatic import of greetings, allows the installer to automatically

replace the messages or announcements available in system mailboxes (AA Entry or AA
Menu type, etc.) by new messages in *.wav format (G711 (A or µ law) or 16 bits PCM). These
messages must have been previously recorded and transferred to the system hard drive via
AAS or FTP with the file listing them (*.csv file).
*.csv file structure:
Each line must successively contain: MCDU,GREETING,LANGUAGE,PATH, where:
- MCDU is the number of the mailbox concerned by the change of message or
announcement.
- GREETING is the number of the message or announcement (*) to be updated.
- LANGUAGE is the language of the message or announcement. In some cases, a
language number is required for the message as it may be available is several languages.
- PATH is the access path to the *.wav file.
Example 1:
*.csv file content
MCDU;GREETING,LANGUAGE,PATH
3060;9;;/tmp/nom3060.wav
3061;5;1;/tmp/accueil3061.wav
3062;8;2;/tmp/nom3062.wav
......
Caution:
When the message or announcement has no language number, do not complete the LANGUAGE
field. Note that language number is voice mail language index.
The installer must only give the complete path for the *.csv file to be imported.
Example 2:
Your choice: 13
Please name of file to up load (total path):
/tmp/auto.csv
(*): Summary of message numbers and correspondences.
Message No. Message type Corresponding mailbox Language
0 Greeting 1 Standard Not required
3 Busy Standard Not required
4 Extended absence Standard Not required
5 Greeting AA Entry Not required
6 Exit Administrator Mandatory
7 Notification Administrator Mandatory
8 Name AA Menu/Ubiquity Mandatory

1-39
Chapter 1
!
9 Name Any type of mailbox Not required
1.8.4 Incidents
The following incident is related to the 4645 voice mail:
- Incident 904: a wrong password has been dialed
1-40

2.1 Overview
2.1.1 Overview
In the context of Alcatel 4645 or 4635 voice mail service use, the IMAP (Internet Message
Access Protocol) service allows users to consult their voice mail from any PC with an Internet
connection. The IMAP service is available from R5.1.
The IMAP service is based on the use of an Alcatel-Lucent OmniPCX Enterprise CS integrated
messaging server named Imapd. The Imapd server supports the IMAP protocol and operates
in client-server mode. The Imapd server:
1. Sets up the connection between the user's PC and his voice mail service (authentication)
2. Provides access to voice messages from a messaging program on the PC:
• Outlook Express®
• Netscape Messenger®
• From R6.0, OmniTouch Unified Communication
3. Ensures synchronization between the voice mail service and the messaging program on
the PC. Thus, when a message is deleted on the PC, this is automatically reflected by
deletion of the message in the voice mailbox (and vice-versa).
___change-begin___
___change-end___

2-1
Chapter 2 " # $
2.2 Architecture
2.2.1 Configurations with a 4645 Voice Mail

Two types of configuration are available with a 4645 voice mail system:
- An internal IMAP service where the Imapd server can run on the same CPU board (CS
board) as:
• The Call Server and the 4645 voice mail
• The 4645 voice mail only
At CPU initialization, running the 4645 voice mail automatically starts the Imapd server.
Imapd server start up is transparent for the system administrator and no action is required.
- An external IMAP service where the Imapd server can run on a dedicated CPU board (CS
board).
• Recognition of the voice mail by the Imapd server is ensured by a vimap process.
Vimap is installed on the CPU board of the voice mail and starts up after the voice mail
has started.
• At CPU initialization, the start of the Imapd server in stand alone is not automatic.
Before starting, the system administrator must define the role of the CPU board as
Imapd server. This action is made from the Imapd server setup tool on the dedicated
CPU.
Note:
In all cases:
- The software package loaded on the CPU board includes the Call Server, 4645 voice mail, and the
Imapd server.
- The CPU board used can be also an Appliance Server.
2-2

" # $
___change-begin___
___change-end___
Figure 2.2: Configurations with a 4645 Voice Mail
2.2.2 Configurations with a 4635 Voice Mail

Two types of configuration are available with a 4635 voice mail system:
- An internal IMAP service where the Imapd server can run on the same CPU board
(VPM35 or VPS35 board) as the Alcatel 4635 voice mail.
• The software package loaded on the CPU board includes the 4635 voice mail and the
Imapd server.
• At CPU initialization, running the 4635 voice mail does not automatically start the
Imapd server. Before starting, the system administrator must validate the Imapd server
start from the 4635 configuration tool accessible by SMT console.
- An external IMAP service where the Imapd server can run on a dedicated CPU board (CS
board or Appliance Server).
• The software package loaded on the CPU board includes the Imapd server.
• Recognition of the voice mail by the Imapd server is ensured by the vimap process.
Vimap is installed on the CPU board of the voice mail and starts up after the voice mail
has started.
• At CPU initialization, the start of the Imapd server in stand alone is not automatic.
Before starting, the system administrator must define the role of the CPU board as
Imapd server. This action is made from the Imapd server setup tool on the dedicated
CPU.
___change-begin___

2-3
Chapter 2 " # $
___change-end___
Figure 2.3: Configurations with a 4635 Voice Mail
2.3 Detailed description
2.3.1 Operating Principle

The basic operating principle of the IMAP service is as follows:
___change-begin___
___change-end___
: User B calls user A whose set is forwarded to the voice mail service. User B decides to
2-4

" # $
leave a message in user A's voice mailbox.

: User A, who is out of office, wants to consult his mailbox from a PC with Internet access.
From the PC's messaging program, user A connects to the Imapd server using the password
for his mailbox.
: After user A has been identified (authentication), the Imapd server transfers voice
messages in user A's mailbox to the in-box of the PC's messaging program.
: User A receives the voice message in the form as an e-mail with a *.wav attachment.
User A can:
- Click on the relative attached file to hear the message
- Delete the message
- Order the messages by, date, sender, etc. (if there are several messages)
Note:
- When the user is connected to the Imapd server, any new message is transferred to the PC
program's in-box. The user is informed immediately of the current mailbox status (number of
messages, new messages).
- If the user performs no operation during a period of 30 minutes, the connection with the Imapd server
is automatically cut off.
- Deleting a message in the messaging program also deletes the message in the voice mailbox (and
vice versa).
- Messages marked as "Read", "Unread", or "Saved" in the mailbox are unmarked in the messaging
program. All messages are displayed as new messages.
- A new message read from the messaging program is registered as "partially read" in the voice mail
program. This message is still displayed as new message in the voice mailbox. When all new
messages are read from the messaging program, the LED notifying new messages stops flashing (is
unlit) on the set.
2.3.2 Licenses
The IMAP service is subject to ACTIS control via the lock:
- 194-4645 My Messaging for the 4645 IMAP service
- 314-4635 My messaging use for the 4635 IMAP service
This lock gives the number of mailboxes authorized for the IMAP service on the Alcatel-Lucent
OmniPCX Enterprise CS.
Each voice mailbox is assigned a Class of Service when it is created by system management.
The Class of Service has a corresponding parameter to grant users IMAP service rights. The
number of voice mailboxes that can be created/modified with IMAP service rights is limited to
the number specified in the lock.
Similarly, if a Class of Service is modified to be granted IMAP service rights and the number of
voice mailboxes with this Class of Service exceeds the number specified by the lock, all such
mailboxes will be refused IMAP service rights.
2.3.3 Limits

2-5
Chapter 2 " # $
The maximum number of connections to the Imapd server depends on the configuration used:
CPU Call Server CPU 4645 voice CPU 4635 voice CPU Imapd serv-
Configuration + 4645 voice mail mail mail er
+ Imapd server + Imapd server + Imapd server
Maximum num- 100 1000 75 1000
ber of connec-
tions
Downloading a message from the voice mail to the PC can take as long as the length of the
message itself.
2.4.1 Overview
This chapter describes the settings used to implement the IMAP service on the Alcatel-Lucent
2.4.2 Prerequisites
The Call Server and voice mail (4635 or 4645) are understood to already be in service on the
Alcatel-Lucent OmniPCX Enterprise CS.
2.4.3 Basic Principles

IMAP service administration is performed as follows:
1. Check the Actis lock for IMAP service use
2. Put the Imapd server into service
3. Grant IMAP service rights to the users
4. Add a voice mail (messaging) account for access to the IMAP service in the messaging
program of a PC
2.4.4 Checking ACTIS Lock

1. From the Call Server CPU prompt, enter the spadmin -m command
2. Select menu 2, then press Enter key on the keyboard
The next screen displays all locks and their respective value
3. Check that the lock authorizes IMAP service use. The lock is:
• 194-4645 My Messaging for 4645 IMAP service
• 314-4635 My messaging use for 4635 IMAP service
Note:
This lock determines the number of mailboxes authorized for the IMAP service on the Alcatel-Lucent
2-6

" # $
2.4.5 Putting Imapd Server into Service

Put Imapd Server into service requires to check the type of voice mail used (4645 or 4635
voice mail) and the CPU board configuration on which the Imapd server is to operate (with or
without voice mail).
Depending on checks done before, do one of the following to put Imapd server into service:
Voice mail used CPU board configur- IMAP service corres- Action
ation pondence
4645 Call Server + 4645 Internal IMAP service No action to be per-
voice mail + Imapd formed
server
or
4645 voice mail +
Imapd server
4645 Imapd server External IMAP service See External Imapd
Server
4635 4635 voice mail + Internal IMAP service See Internal Imapd
Imapd server Server
4635 Imapd server External IMAP service See External Imapd
Server
2.4.5.1 External Imapd Server

On the CPU board dedicated to the Imapd server use, proceed in the order listed below to put
Imapd server into service:
1. Deactivate the service automatic start
2. Declare the CPU supporting voice mail. This operation allows to validate the next start of
the dedicated CPU in Imapd server
3. Only in case of 4635 voice mail use, configure the IVR LAN (Id 240), ASA LAN (Id 241)
and IMS (Id 253) applications passwords. These applications ensures the dialog between
the 4635 voice mail and the Imapd server
4. Start the dedicated CPU in the Imapd server
On the voice mail CPU and only in case of 4635 voice mail use, add the IVR LAN (Id 240),
ASA LAN (Id 241) and IMS (Id 253) applications from the 4635 configuration tool accessible
via SMT console. The declaration of these applications is mandatory to allow dialog between
the 4635 voice mail and the Imapd server
2.4.5.1.1 Deactivating Service Automatic Start
On the Alcatel-Lucent OmniPCX Enterprise CS, the CPU board dedicated to the Imapd server
use must be installed and initialization launched. Once the initialization is over, the service
(Call Handling or other) started must be stopped. If it is not the case, proceed in the order
listed below to deactivate the service automatic start:
- From the dedicated CPU prompt, open a session (log on) using swinst
- Select 2 Expert menu

2-7
Chapter 2 " # $
- Select 6 System management

- Select 2 Autostart management
- Select 2 Unset autostart
- Press return
- Exit swinst
- Reboot the CPU with shutdown command
2.4.5.1.2 Declaring the CPU Supporting Voice Mail
1. From the dedicated CPU prompt, open a session (log on) using swinst
2. Select 2 Expert menu
3. Select 6 System management
4. Select 6 IMAP server management
This menu of swinst opens the Imapd server setup tool
5. Select 2 + Setup
6. Select 2 . CPU Add
7. Enter the name of the CPU supporting voice mail and select voice mail type as shown
below:
CPU Add
VIMAP CPU List
4645 : <no cpu>
4635 : <no cpu>
New CPU ? 4635_CPU (for example)
Voice mail type (0=4645, 1=4635) ? 1 (for example)
CPU Added
2.4.5.1.3 Checking Imapd Server Configuration

1. From Imapd server setup tool, select 2 + Setup
2. Select 1 . Actual Configuration
3. Check that the voice mail CPU declaration is done as shown below:
Actual Configuration
Actual Configuration
Imapd package is installed
4635 package is installed
VIMAP CPU List
4645 : <no cpu>
4635 : 4635_CPU (for example)
2.4.5.1.4 Configuring 4635 Applications Passwords

1. From Imapd server setup tool, select 2 + Setup
2. Select 5 . Configuration of 4635 application passwords
3. Enter the password of each application asked for 4635 voice mail system:
Configuration of 4635 application
passwords
Password IMS (253) : 2222 (for example)
Password ASA (241) : 2222 (for example)
Password IVR (240) : 2222 (for example)
2.4.5.1.5 Starting the Dedicated CPU in the Imapd Server

From the dedicated CPU prompt, use the shutdown command to start the dedicated CPU in
2-8

" # $
the Imapd server.

2.4.5.1.6 Adding Applications in 4635 Voice Mail System
You must declare applications in the 4635 configuration tool. It concerns the following
applications: IVR LAN (Id: 240), ASA LAN (Id: 241) and IMS (Id: 253).
1. Connect to the 4635 SMT console
2. Select 17 - External Application Management
3. Select 2 - Application Administration
4. Select 1 - Add Application
5. Enter valid information for the first application (Id, name, maximum sessions allowed and
password) as shown below:
Menu 17 - External Application Management
- Add
Application -
Application ID : 240
Application Name : IVR LAN
Maximum Sessions allowed : 64 (for example)
Application Password : 2222 (for example)
Caution:
The application password must be identical to the one entered at Configuring 4635
Applications Passwords .
6. Validate and repeat operations for the other applications
2.4.5.2 Internal Imapd Server
On the 4635 voice mail CPU, proceed in the order listed below to put Imapd server into
service:
1. Add the IVR LAN (Id 240) and ASA LAN (Id 241) applications from the 4635 configuration
tool accessible via SMT console. The declaration of these applications is mandatory to
allow dialog between the 4635 voice mail and the Imapd server
2. Validate the start of the Imapd server
2.4.5.2.1 Adding Applications in 4635 Voice Mail System
Two applications must be declared in the 4635 configuration tool. It concerns: IVR LAN (Id:
240) and ASA LAN (Id: 241).
3. Select 2 - Application Administration
4. Select 1 - Add Application
5. Enter valid information for the first application (Id, name, maximum sessions allowed and
password), for example:
- Add
Application -
Application ID : 240
Application Name : IVR LAN
Maximum Sessions allowed : 64 (for example)
Application Password : 2222 (for example)
6. Validate and repeat operation for the other application

2-9
Chapter 2 " # $
2.4.5.2.2 Validating the Imapd Start

3. Select 5 - Internal IMAP Server administration
4. Validate the Imapd server start as shown below:
Internal IMAP Server
Configuration
Start Internal Imap Server : Y
2.4.6 Assigning IMAP Service Rights to the Users

Perform the following operations for each IMAP service user:
1. Assign a Class of Service to each user's mailbox
2. Configure the Class of Service to authorize IMAP service use
2.4.6.1 Assigning a Class of Service to the User's Mailbox
1. Connect to the mgr or the 4760 configuration tool
2. Select Users
3. Review/modify the following attribute:
Example:
4645 Voice Mail Box

4645 Voice Mail Type Displays the type of mailbox
4645 Class of Service Enter the number of the Class of Service for
this mailbox
Note:
Only the attributes relevant to this step are described.
4. Confirm your entry
2.4.6.2 Configuring the Class of Service to Authorize IMAP Service Use
This operation differs following voice mail system used:
- For 4645 voice mail, proceed in the order listed below to configure the Class of Service to
authorize IMAP service use:
a. Connect to the mgr or the 4760 configuration tool
b. Select Applications > Voice Mail > 4645 VM Classes of Services
c. Review/modify the following attribute:
IMAP access Enter Yes to authorize IMAP service use
Only the attribute relevant to this step is described. For more information, see the
Alcatel-Lucent 4645 VMS - Basic management - Reviewing or modifying a Class of
Service
d. Confirm your entry
2-10

" # $
- For 4635 voice mail, proceed in the order listed below to configure the Class of Service to
authorize IMAP service use:
a. Connect to the 4635 SMT console
b. Select 7 - Change Class of Service Profile
c. Enter the number of the Class Of Service, then press Enter key on the keyboard
d. In the field My messaging, select Y
e. Validate and repeat operation for the next Class Of Service used
2.4.7 Configuring an IMAP account for a PC
Note:
Each PC must be equipped with:
- A messaging program such as Outlook Express®, Netscape Messenger®, eCC, etc.
- A program that can read *.wav audio files
- Sound card
- Loudspeakers
- An Internet connection
For each PC, perform the following procedure to allow IMAP service use:
1. Ensure you have the following information:
• The type of server used (IMAP)
• Account name and password (user's voice mailbox number and password)
• Incoming voice mail/messaging server name (voice mail IP address)
• Outgoing voice mail/messaging server name (the user's default messaging server
name)
2. Create the IMAP account with the previously provided information. Depending on the
messaging program used, operation can differ. For information, refer to the on-line help for
your messaging program.
Important:
If the user is to create the account, they must obtain the information required to open the account
and on how to perform the procedure from the network administrator.
2.4.8 Updating External Imapd Server

When a new software (change of version) is installed on a CPU dedicated to the Imapd server,
update is not automatic and requires an action as shown below:
1. From the prompt of the dedicated CPU, open a session (log on) using swinst
2. Select 2 Expert menu
3. Select 6 System management
4. Select 6 IMAP server management
This menu of swinst opens the Imapd server setup tool
5. Select 3 . Update
For example:

2-11
Chapter 2 " # $
Update
Uninstalling imapd
Installing imap-2.0-1oxe.i386.rpm ...
Uninstalling vimap-4635 ...
Cannot remove /var/a4635/cache/vimap - directory no empty
Cannot remove /etc/a4635 _ directory no empty
Installing vimap-4635-2.0-1oxe.i386.rpm ...
2.5 Operation
2.5.1 Overview
This chapter is intended for IMAP service users and describes the procedure used to consult
voice mail from a messaging program on a PC.
2.5.2 Procedure
1. Open the messaging program in-box.
2. Download voice messages in the message reception window.
• If connecting for the first time, click the “In-box” folder of the IMAP service account.
• Otherwise, click the "Refresh" button in the reception window.
3. Double-click a message to display the attached *.wav file.
4. Double-click the *.wav file to play it.
5. When you have listened to the message, you can delete it in the reception window.
In the toolbar, click the Delete button. The message is displayed struck out but is not
deleted.
To delete the message completely, click Remove deleted messages in the Edit menu.
Important:
Depending on the messaging program used, operations may differ from those described above. If
this is the case, refer to the on-line help for your messaging program.
2-12

3.1 Overview
3.1.1 Glossary
- VPIM network: a network of VPIM compliant voice mails that exchange messages using
the VPIM protocol
- Call server sub-network: a network of call server linked by ABC-F type private links that
share an homogeneous numbering plan
- IP network: a group of call server and voice mail systems linked using the IP protocol
3.1.2 Overview
The VPIM service (Voice Processing Internet Messaging) is available from R5.1 and allows
(via the IP network) an Alcatel 4645 or 4635 voice mail system node to be connected with
several other voice mail system nodes (Alcatel 4645 or 4635 systems, or systems from
another manufacturer). The VPIM service thus allows voice messages to be exchanged
between users with a mailbox on one of these voice mail nodes.
Note 1:
As of R8.0, there is voice mail service limitation specific to Alcatel 4635 voice mail system.
In a VPIM or OctelNet network, it is not possible to send a reply message from remote voice mail
system nodes (Alcatel 4645 or 4635 or voice mail systems from non-Alcatel manufacturers) to a
distribution list of Alcatel 4635 voice mail system node.
Once the voice message has been recorded, the VPIM service encodes it, translates it into an
e-mail format message, and routes it to the mailbox on the remote node via the IP network.
Example:

3-1
Chapter 3 #" $
In the context of VPIM service use, "voice mail system node" refers to a PCX or PBX with a
voice mail service and a connection to the IP network. Voice mail nodes interconnected by the
VPIM service form a VPIM network.
Note 2:
In the rest of this document, for reasons of clarity:
- "Local node" is used to refer to the Alcatel 4645 Voice Mail node sending the message.
- "Remote node" is used to refer to the voice mail node to which this message is sent.
- "VPIM message" is used to refer to a voice message sent to a recipient via the VPIM service.
3.1.3 Architecture of the VPIM service

There are several VPIM network configurations, based on the hardware configuration of the
remote node. These are:
3-2

#" $
Where:
: 4645 Domain
- The 4645 domain is formed of nodes connected both by ABC-F type private links and the
IP network. The remote nodes are composed of Alcatel-Lucent OmniPCX Enterprise CS
type PCXs with 4645 Voice Mail.
- The dialing plan is homogeneous within a 4645 domain, this means that each voice
mailbox has a directory number that is recognized by all domain nodes.
- Service level:
• Send VPIM messages to one or more users.
• Reply to VPIM messages.
• Call the sender of a VPIM message.
• Use the “Dial by name” feature to call the recipient of a VPIM message.
• Confirm the name of the recipient before sending the VPIM message.
: 4645 Network
- The 4645 network is composed of nodes connected by the IP network only. The remote
nodes are Alcatel-Lucent OmniPCX Enterprise CS type PCXs with 4645 Voice Mail.
- The dialing plan is not homogeneous on a 4645 network. An access prefix for the remote
node must be configured in the local node's dialing plan.
- Service level:
• Send VPIM messages.
• Use the “Dial by name” feature to call the recipient of a VPIM message.

3-3
Chapter 3 #" $
• Confirm the name of the recipient before sending the VPIM message.
: Non 4645 Network
- A non 4645 network is composed of nodes connected by the IP network only. The remote
nodes are:
• Alcatel-Lucent OmniPCX Enterprise CS type PCXs with 4635 Voice Mail.
• And/or non Alcatel PBXs with a voice mail system supporting VPIM from a
manufacturer other than Alcatel-Lucent.
- The dialing plan is not homogeneous on a non 4645 network. An access prefix for the
remote node must be configured in the local node's dialing plan.
- Service level:
• Send VPIM messages.
3.1.4 Network Transparency of Voice Mail Features

The following table illustrates the availabilty of voice mail features when used in different 4645
network topologies.
Feature 4645 Domain 4645 Network non 4645 Network
Send message Y N N
without prefix address-
ing
Send message with Y1 Y Y
prefix addressing
Spoken name confirm- Y2 N N
ation
Personal Greetings N N N
Extended absence N N N
greeting
Send VPIM message N N N
in telephone answer.3
Reply to a VPIM voice Y Y Y
message4
Call sender5 Y N N
6
Check receipt N N N
AA consult mailbox7 N N N
AA reach mailbox by N N N
dialing the number 7
AA reach mailbox by N N N
dialling the name 7
AA go back N N N
1
Only necessary for nodes outside the domain
3-4

#" $
3.1.5 Limits of the VPIM service

VPIM service limitations are:
Maximum number of nodes in a VPIM network 500
Maximum number of voice mailboxes in a VPIM 48000
network
Maximun length of a VPIM message 5 hours
3.1.6 Related modules

The VPIM service is described in the following modules:
- Functional description, see the VPIM service - Detailed description
- Configuration, see the VPIM service - Configuration procedure
- Configuration example, see the VPIM service - Configuration examples
- Use (operation), see the VPIM service - Operation
3.2.1 Operating principle

3.2.1.1 The 4645 domain
2
Available after the first message has been received, stored in a local cache
3
A caller might enter a system via telephone answering and then leave messages in several
different mail boxes
4
If reply address is available (not set to "From: non-mail-user@domain")
5
Depends on CLI availability
6
Implementation restriction: a remote query for ststus of messages is not available
7
Would require to transfer the call to a different voice messaging node and hand-over call
context information

3-5
Chapter 3 #" $
User A decides to send a VPIM message to user B.

1. From his set, user A connects to his voice mailbox.
2. From the main mailbox menu, user A selects the send menu, then records the VPIM
message.
3. When recording is complete and when requested by the voice mail service, user A
dials/enters either:
• User B's voice mailbox number
• User B's name
Note 1:
The number dialed must be that of a Standard, Guest voice mailbox or a distribution list.
When entry is complete, the system checks the requested number.
4. Once the number has been checked by the system, user A hears (as confirmation) either:
• Voice mailbox number (if connecting for the first time)
• The name 8 recorded by user B for his voice mailbox (if this is a new connection).
5. When the confirmation message has been played, user A confirms whether or not the
VPIM message is to sent.
Note 2:
- User A can also simultaneously send a VPIM message to several users. In this case, the number
dialed/entered in step 3 is for a Distribution list type mailbox or he can repeat the steps 3 to 4 with
other numbers.
- After user B has listened to the VPIM message, he can either:
• Reply by sending a VPIM message
• Call user A
- When the VPIM message does not reach User B due to a conversion, transfer, or other type of
8
This data is managed/configured by the site installer.
3-6

#" $
problem, User A is informed of this by a voice message.

Example:
A VPIM message cannot be sent to User B if his voice mailbox is in extended absence mode or is
full.
3.2.1.2 The 4645 and non 4645 networks
The operating principle of the VPIM service is similar for these two network configurations.
However, as of R8.0 there is voice mail service limitation specific to Alcatel 4635 voice mail
system. In a VPIM or OctelNet network, it is not possible to send a reply message from
remote voice mail system nodes (Alcatel 4645 or 4635 or voice mail systems from non-Alcatel
manufacturers) to a distribution list of Alcatel 4635 voice mail system node.
Example 1:
Remote node consisting of a Alcatel-Lucent OmniPCX Enterprise CS with 4635 Voice Mail.
User A decides to send a VPIM message to User B.

1. From his set, user A connects to his voice mailbox.
2. From the main mailbox menu, User A selects the send menu, and then records the VPIM
message.
3. When recording is complete and when requested by the voice mail service, User A
dials/enters the remote node prefix 9 followed by User B's voice mailbox number . The
system considers entry to be complete when any of the following occur:
• The maximum number of digits 9 to be dialed is reached and the inter-digit timer
elapses.
• The maximum number of digits to be dialed is reached and User A presses the # key
on the set.
• The maximum number of digits 9 to be dialed is reached.
When entry is complete, the system checks the requested number.

3-7
Chapter 3 #" $
4. Once the number has been checked by the system, User A hears (as confirmation) either:
• The name recorded 9 for the remote node (if any) followed by the voice mailbox
number
• The remote node's access prefix followed by the voice mailbox number.
5. When the confirmation message has been played, User A confirms whether or not the
VPIM message is to be sent.
Note:
- When User B has listened to the VPIM message, he can reply by sending a VPIM message.
- (Only on a 4645 network): If User B replies by sending a VPIM message, User A can, if he wants to
send another VPIM message to User B, use the following features:
• In step 3, the Dial by name feature.
• In step 4, the name recorded by User B for his mailbox.
- When the message does not reach User B due to a conversion, transfer, or other type of problem,
User A is informed of this by a voice message.
Example 2:
A VPIM message cannot be sent to User B if his voice mailbox is in extended absence mode.
3.2.2 Control of the VPIM service

The VPIM service is subject to ACTIS control via the lock 182-EVA_network. This lock
allows or prohibits VPIM service from the local node.
When the VPIM service is active on the local node, all users with a voice mailbox on the node
can use the VPIM service. For information on how to consult lock status, refer to the
Alcatel-Lucent 4645 VMS - Installation procedure - ACTIS Locks.
3.3.1 Overview
This chapter describes the different settings to configure on an Alcatel-Lucent OmniPCX
Enterprise CS to include 4645 or 4635 voice mails in a VPIM network.
Important:
The Call Server, 4645 and 4635 voice mail must already be in service on the Alcatel-Lucent
3.3.2 Configuration for 4645

3.3.2.1 Basics
VPIM service administration is performed as follows:
1. Voice mail number check: check that each voice mail is declared with a voice mail
9
This data is managed/configured by the site installer.
3-8

#" $
number that is unique whithin the VPIM network.

2. VPIM nodes declaration: each node must know the other nodes of the VPIM network. A
VPIM node is identified by its voice mail number and a FQDN (Fully Qualified Domain
Name).
3. IP configuration: on each node, proceed to IP configuration so that FQDN of VPIM nodes
can be translated into IP addresses.
3.3.2.2 Checking Voice Mail Numbers
Each time a voice mail is declared, it must be assigned a UNIQUE voice mail number. For
each 4645 and 4635 voice mail systems of the VPIM network, this number can be reviewed
via mgr or the 4760 configuration tool:
1. Select Applications > Voice Mail
2. Enter the Voice Mail Dir.No.
3. Check the value of the following attribute:
Voice Mail Server No. This number must be unique in the entire VPIM net-
work.
3.3.2.3 Declaring VPIM Nodes

3.3.2.3.1 Principle
Each node of the VPIM network must acknowledge all the other nodes of the network.
Declaration of VPIM nodes must be performed on one node only, on each call server
subnetwork containing 4645 voice mails. Once these declarations have been performed, they
are broadcast to the other nodes of the subnetwork by the audit/broadcast mechanism.
1. On each call server subnetwork containing 4645 voice mails, select one node.
2. On this node, declare all the VPIM nodes of the VPIM network. This includes:
• The node itself
• The other VPIM nodes of the subnetwork
• VPIM Nodes outside the subnetwork
To declare VPIM nodes, see Declaring VPIM nodes .
3. Ensure that these declarations are broadcast to the other nodes of the network: see VPIM
Nodes Broadcast and Audit
3.3.2.3.2 Declaring VPIM nodes
VPIM nodes are declared via mgr or the 4760 configuration tool:
1. Select Applications > Voice Mail > 4645 VM VPIM
2. Review/modify the following attributes:

3-9
Chapter 3 #" $
VM Node Num- Enter the ID number of the remote node on the VPIM network.
ber
Caution:
The VM Node Number must be the unique identifier of this voice mail in the
VPIM network. For an Alcatel 4645 or 4635 voice mail, it must match its Voice
Mail Server No. attribute (see Checking Voice Mail Numbers ).
Prefix Number Enter the remote node access prefix (2 to 8 digits).
Note 1:
Do not enter anything when the remote voice mail belongs to the same subnetwork.
VM Phone Num- Enter the directory number of the remote node voice mail system. Either:
ber • The voice mail is in the same call server subnetwork. Enter the local
number of the voice mail in the homogeneous numbering plan
• The voice mail is not in the same call server subnetwork. The number
to be entered consists of the prefix number followed by the voice mail
number.
Directory Name Enter a name for the remote node voice mail service (optional). This name
will be displayed on the set when a name is recorded for the node.
Domain name Enter the name of the IP domain to which the remote node belongs. This
name is used to compose the message recipient IP address when the mes-
sage is sent over the IP network.
Reminder:
The VPIM service uses standard Internet addressing format: User name@Domain
name, where the local part is the recipient's directory number and the domain part is
a Fully Qualified Domain Name (FQDN), in other words, a domain name.
Destination Enter the type of network configuration to which the remote node belongs:
type • 4645 Network: the remote voice mail is a 4645 in a different call server
subnetwork
• 4645 Domain: the remote voice mail is a 4645 in the same call server
subnetwork
• NO 4645: the remote voice mail is not a 4645
Min No. digits Enter the minimum number of digits to dial before the system recognizes
these digits as a voice mailbox number (between 3 and 8).
Note 2:
This number must be less than the Max No. digits attribute.
Max No. digits Enter the maximum number of digits to dial for remote node voice mail
boxes (between 3 and 8).
Audio encoding Select the type of audio encoding to be used for VPIM messages:
• G.711 between two 4645 voice mails
• G.726 for all other cases
Email encoding Base64
3. Confirm your entries

4. Repeat operations for the other VPIM nodes of the VPIM network
3.3.2.3.3 VPIM Nodes Broadcast and Audit
The VPIM node declarations must be broadcast to all nodes (and their 4645 voice mails) of the
subnetwork.
3-10

#" $
If this is not the case, the audit feature must be used. To launch the audit of VPIM voice mails
in this Call Server subnetwork, use the audit menu:
58 * 4645 VM VPIM
3.3.2.4 IP Configuration
3.3.2.4.1 Basics
IP configuration is necessary to allow name resolution, i.e. the translation of the FQDN (filled in
the Domain Name attribute of 4645 VM VPIM objects) into IP addresses.
Name resolution can be achieved in any of the following ways:
- With a domain name server (DNS). The advantage of using a DNS is to avoid having to
declare all FQDNs on VPIM nodes. Name resolution is insured by DNS.
- With aliases declared on the PCX. This method is the most strenuous of all, because
FQDNs of all VPIM nodes must be declared on the Alcatel-Lucent OmniPCX Enterprise
CS via the netadmin command.
- With a mail router. The advantage of a mail router is to avoid having to declare all FQDNs
on VPIM nodes. Name resolution is insured by the mail router. But the mail router itself
must be configured using alias unless the system used a DNS hostname resolution.
Note:
These three methods are not exclusive. It is possible, for instance, to use a mail router for nodes outside
the local IP domain, DNS or aliases inside the IP domain.
3.3.2.4.2 Local Node IP Configuration

The local node must have a FQDN address for sendmail to work correctly. This FQDN must be
declared with the netadmin command.
1. Log on the Call Server under the mtcl account
2. Run the command netadmin -m.
3. Select 9. 'Host names and addresses'
4. Select 2. 'Aliases'
5. Select 2. 'Add/Update'
6. Enter the FQDN of the local node, its host name and IP address, e.g.:
Aliases update
==============
Alias name ? local_vmail.col.bsf.alcatel.fr
Host's IP name ? local_vmail
Host's IP address (default is 192.40.55.54) ?
7. Enter 0 to return to the main menu, then select 16. 'Apply modifications'
8. Enter 0 to exit netadmin.
3.3.2.4.3 Using a Domain Name Server
1. Log on the Call Server under the root account
2. Add in the /etc/resolv.conf file:
• The domain name of the local host
• One, or possibly several, domain name servers

3-11
Chapter 3 #" $
Example:
domain col.bsf.alcatel.fr
nameserver 192.40.55.10
where domain is followed by the name of the local host and nameserver is followed by
IP address of one DNS.
3.3.2.4.4 Using Aliases
If no DNS or mail router is used, the FQDN of all distant nodes must be declared via a
netadmin command.
1. Run the command netadmin -m.
2. Select 9. 'Host names and addresses'
3. Select 1. 'Host database update'
4. Select 2. 'Add/Update'
5. Enter the FQDN host name and IP address of a VPIM node, for example:
Host database update
====================
Host name ? evacs7.col.bsf.alcatel.fr
Host address ? 192.40.55.56
6. Repeat this operation for all the nodes (4645 VM VPIM objects) declared on the local
node.
3.3.2.4.5 Using a Mail Router
To use a mail router, configure the router address and request that sendmail uses it.
1. Log on the Call Server under the root account
2. If there is no activated DNS, add the router FQDN to the hosts:
a. Run the command netadmin -m.
b. Select 9. 'Host names and addresses'
c. Select 1. 'Host database update'
d. Select 2. 'Add/Update'
e. Enter the host name and IP address of the mail router, for example:
Host database update
====================
Host name ? mail_router.col.bsf.alcatel.fr
Host address ? 192.40.55.1
f. Enter 0 to return to the main menu, then select 16. 'Apply modifications'
g. Enter 0 to exit netadmin.
3. Update the /etc/mail/mailertable file as follows:
. smtp:mail_router.col.bsf.alcatel.fr
Caution 1:
Note the period at the beginning of the line.
Note:
It is possible to route network nodes from the local IP domain directly, without using the router:
1. Add the following line at the beginning of /etc/mail/mailertable file:
.col.bsf.alcatel.fr smtp:%1.col.bsf.alcatel.fr
3-12

#" $
Caution 2:
2. Run the command rstcpl 18 1 or rstcpl 18 0 on the Call Server to restart sendmail.
3.3.3 Configuration for 4635

3.3.3.1 Basics
This section describes IP configuration necessary to allow name resolution, i.e. the translation
of the FQDN (filled in the Domain Name attribute of 4645 VM VPIM objects) into IP
addresses.
Name resolution can be achieved in any of the following ways:
- With a domain name server (DNS). The advantage of using a DNS is to avoid having to
declare all FQDNs on VPIM nodes. Name resolution is insured by DNS.
- With aliases declared on the PCX. This method is the most strenuous of all, because
FQDNs of all VPIM nodes must be declared on the 4635.
- With a mail router. The advantage of a mail router is to avoid having to declare all FQDNs
on VPIM nodes. Name resolution is insured by the mail router. But the mail router itself
must be configured using alias unless the system used a DNS hostname resolution.
Note:
These three methods are not exclusive. It is possible, for instance, to use a mail router for nodes outside
the local IP domain, DNS or aliases inside the IP domain.
Caution:
VPIM configuration on the SMT console is not described in this document.
3.3.3.2 Using Domain Name Server

To use a domain name server, you must declare:
- The IP domain of the local host
- One, or possibly two, domain name servers
2. Select 22 - LAN Interface Management
3. Select 2 - TCP/IP Parameter Configuration
4. Enter valid information for DNS and domain fields, for example:
Menu 22 - LAN Interface Management N1_R2
- TCP/IP Parameter Configuration -
This Server's Ethernet Address: ......... 00:80:9F:04:2E:0D

This Server's IP Address: ............... 192.168.48.29
IP Net Mask: ............................ 255.255.255.0
Broadcast Address: ...................... 192.168.48.255
Gateway IP Address: ..................... 192.168.48.254
Backup Server IP Address: ............... 192.168.48.44
Primary DNS.............................. 192.168.48.190
Secondary DNS............................ 0.0.0.0
Domain Name: ............................
---> ecccol.dhs3abca.com col.bsf.alcatel.fr
5. Check the /etc/resolv.conf file to see that your configuration is correct

3-13
Chapter 3 #" $
search ecccol.dhs3abca.com col.bsf.alcatel.fr

3.3.3.3 Using Aliases

This configuration is not recommended for 4635 voice mail because many actions must be
configured manually and no backup/restore mechanism is available for all the operations
involved. This is why DNS configuration should be used whenever possible.
FQDN of the local node and of all VPIM nodes of the network must be declared in the
/etc/hosts file.
1. Log on to the 4635 linux as root user
2. Edit the /etc/hosts file
3. Declare a FQDN for the local host and each network hosts:
#
# 4635 hosts file
#
127.0.0.1 localhost
192.168.48.29 4635_cmdev54.col.bsf.alcatel.fr 4635_cmdev54
192.168.48.28 4635_cinfra.col.bsf.alcatel.fr 4635_cinfra
192.168.48.61 eva_cs9 eva_cs9.col.bsf.alcatel.fr
4. Create a file /etc/mail/service.switch
5. Add the following lines:
hosts files
aliases files
6. Edit the /etc/sendmail.cf file
7. Replace the line
#0 ServiceSwitchFile=/etc/service.switch
with
0 ServiceSwitchFile=/etc/mail/service.switch
8. Run the /etc/rc.d/sendmail restart command to restart sendmail

Note:
FQDN declared in the /etc/hosts file must match those registered on 4634 SMT console in the menu:
- 15 - Network Management
- 1 - OctelNet/VPIM Administration
- 3 - Define/Change Node Profile
3.3.3.4 Using a Mail Router
To use a mail router, configure the router address and request that sendmail uses it.
1. Log on to the 4635 linux as root user
2. If there is no activated DNS, edit the /etc/hosts file and add the FQDN of the mail
router:
#
# 4635 hosts file
# 127.0.0.1 localhost
192.40.55.1 mail_router.col.bsf.alcatel.fr
3. Update the /etc/mail/mailertable file as follows:
. smtp:mail_router.col.bsf.alcatel.fr
3-14

#" $
Caution 1:
Note:
It is possible to route network nodes from the local IP domain directly, without using the router:
1. Add the following line at the beginning of /etc/mail/mailertable file:
.col.bsf.alcatel.fr smtp:%1.col.bsf.alcatel.fr
Caution 2:
2. Run the /etc/rc.d/sendmail restart command to restart sendmail
3.4 Configuration examples
3.4.1 On the 4635 Voice Mail

1. Create the applications 240, 241 and 253 from the Menu 17 External application
Management
• Application 240
- Add Application -
Application ID: 240
Application Name: IVR LAN
Maximum Sessions Allowed: 24
Application Password: 2222
• Application 241
- Add Application -
Application ID: 241
Application Name: ASA LAN
• Application 253
- Add Application -
Application ID: 253
Application Name: InterMail VPMOD TO HOST
2. Create a Mailbox of type 40 associated to the application 240
Menu 8 - Add Mailbox
Number: 1999 Mailbox Type; 40 - Info Proc. Mailbox
Mailbox Number: 1999
Mailbox Name: type40 Community N°.:
Department: Express Address:
Mailbox Mgr. Extention: 1999 Alias Address:
Operator Destination: Group ID:
Busy Mailbox: Operator Schedule:
Down Mailbox: After Hours Mailbox
Interrup Mailbox: Int. Link Number: 1
Type of Access: 0 - Mailbox VPMOD ID: PSO
Application ID: 240
Mailbox Lang.: 1 - European French

3-15
Chapter 3 #" $
3. Create the VPIM node for the distant voice mail from the Menu 15 - Network Management
- OctelNet Administration -
- Node Profile -
Node Number: 2 Node Name: xa000010
Transmission Type: 0 - Normal Node Type: 3 - VPIM 32KADPCM
Number of Digits in a Mailbox: 5 Serial Number:
NameNet Type: 0 - COS-based Site ID:
NameSend: 3 - Send And Receive
Phone Number: 0155631050 Ext:
Dialing Sequence: Authorization Code:
Access Type: 0 - Direct Dial Country: 5 - France
Max Simultaneous Analog Transmissions: 1 Threshold: 0 msgs, 0 mins
FQ Mailhost: xa000010.alcatel.fr
IP Address: 0.0.0.0 Fallback: 0 - None
Name Transmission Allowed: Y Play Node Name: Y
ASCII Name Check: 1 - Check All Msgs Node Response Allowed: N
System Manager Name: Mailbox Number:
System Manager Phone Number: Ext:
4. Create the access prefix for the distant voice mail from the Menu 15 Network Management
- OctelNet Administration -
- Node Profile -
Node Number: 2 Node Name: xa000010
Prefix D Prefix D Prefix D Prefix D Prefix D
------ -- ------ -- ------ -- ------ -- ------ --
2 5
5. Verify the lock "connectivity" on 4635 in the Menu 13 System Maintenance
25 NOV 04 16:17:56 pso pso
VPMOD Serial #------------4444 Sotware Release--------5.2.2
Network Serial #----------4444 System Type-----A4635J / VPU5 Rev. 0
Y 68 - Extension Mailbox 71 - No Beep for Record on-line
Y 73 - Connectivity Y 74 - Digital Networking
75 - Octel Admin Y 77 - System Backup & Restore
6. Validate the VPIM in the Class of Service
Menu 7 - Class of Service Profile pso
Classe of service: 10
Name: COS10 Number of Mailboxes: 10
Personal greeting: 2 - Mult. Greetings Octenet Priority Level: 2 - Priority
Extended Absence Greeting Allowed: Y NameNet Entry Type: 0 - Usage-based
Max Greeting Lenght (min:sec): 0:00:30 Type of Amis Networking: 0 - none
7. Validate this COS for the users having rights for VPIM
Validate this Class of Service for the users having the right to send the messages by
VPIM. The parameters of the Class of Service are in the voice mail box of the user.
8. Get information about the different IP addresses necessary
Menu 22 - LAN Interface Management pso
- TCP/IP Parameters Configuration -
This Server's Ethernet Address: 00:80:9F:04:AF094
This Server's IP Address: 10.9.1.20
IP Net Mask 255.255.0.0
Broadcast Address 10.9.255.255
Gateway Server IP Address 10.9.1.10
Primary DNS 0.0.0.0
Secondary DNS 0.0.0.0
Domain Name alcatel.fr
9. The server number must be unique in the VPIM network. During the configuration of the
voice mail service, a server number is requested. This server number must be unique in
the VPIM network, and each voice mail must have a different server number.
• 4400
Verify the lock ACTIS 151 - A4635 VPIM = <indicate the number of ports>
3-16

#" $
• 4645
In the 4645 voice mail service, the VPIM network is configured from the mgr. Go to
application Menu / Voice Mail / Descend hierarchy / 4645 VM VPIM
Creation: 4645 VM VPIM
Node Number(reserved) : 10
Instance (reserved) : 1
Instance (reserved) : 1
VM Node Number : 1
Prefix Number : 21
VM Phone Number : 1500
Directory Name : VoiceMail
Domain Name : Pso.alcatel.fr
Destination Type + Non 4645
Min No.digits : 4
Max No.digits : 5
Audio Encoding + G726
Email Encoding + Base64
3.5 Operation
3.5.1 Overview
This chapter is intended for VPIM service users. It describes the procedure used to send a
VPIM message from the voice mail service.
3.5.2 Procedure
To send a VPIM message from the voice mail service:
1. Obtain the remote node access prefix from the system administrator.
Reminder:
This prefix is required if the recipient of the message is located on the remote node of a 4635 or non
4645 network.
2. Connect to the voice mail service.
3. From the main menu, select Send.
4. Record the VPIM message.
5. When you have finished recording, enter the recipient's address with:
• The recipient's voice mailbox number, if the remote node belongs to a 4645 domain.
• Prefix number + voice mailbox number, if the remote node is part of a 4635 or non
4645 network.
6. When you have entered the address, confirm that the VPIM message is to be sent.
Note:
- These steps are described (except step 5.) in the Alcatel 4645 Voice Mail User Guide. Refer to the
Alcatel-Lucent 4645 VMS - Sending messages - Sending a message by dialing a directory number.
- For more information on sending VPIM messages, refer to the VPIM service - Detailed description -
Operating principle.
- Part 5 can be repeated several times to address the message to several recipients that can be local
to the voicemail itself or part of 4645 domain, 4645 network and non 4645 network.

3-17
Chapter 3 #" $
3-18

4.1 Overview
Caution:
This topic has not been updated for OmniPCX Enterprise as neither the operating principle or
implementation has been significantly modified.
4.1.1 Introduction
This document presents two features integrated to voice mail :
- messaging system centralisation : a messaging system installed on one node can have
users installed on other nodes.
- messaging system integrated management : during the declaration of a user set on the
PABX, the set can be assigned, directly in the management menu, a voice mailbox in a
previously installed messaging system.
4.1.2 Use
From the point of view of a user located on a remote node, a centralised voice messaging
system is seen as a stand-alone messaging system that is located on the same node as the
user's set. This means that the functionality and use are exactly the same in both cases and
depend on the messaging system installed. Therefore, refer to the documentation
corresponding to the messaging system installed.
The additional functions, specific to the network configuration (of the messaging systems)
depends on the inter voice messaging systems communication protocol used. This protocol
can be :
- AMIS Analog (for 4635H).
- Octelnet (for 4635H only).
4.1.3 Reference to the other modules

- Functionnal Description (see Centralised voice messaging - Detailed description ),
- Management (see Centralised voice messaging - Configuration procedure ),
- Maintenance (see Centralised voice messaging - Maintenance ).

Voice mail can be used according to three topologies :
- voice messaging system in stand-alone mode,
- voice messaging systems in network mode (in the AMIS or OctelNet meaning of the word),
- centralised voice mail with integrated management.
This module gives a reminder of the first two topologies and presents the centralised voice
mail with integrated management.

4-1
Chapter 4
% &&
''
4.2.1 Stand-alone voice messaging system

On any stand-alone PABX or a PABX belonging to any type of network (with any types of
links), a single voice messaging system is installed on one of the nodes. Each user of this
node can possess (within the limit of the available resources) a voice mail box in this
messaging system. The messaging system can be type 4635. It is also possible to have
several messaging systems installed on the network (maximum one per node) but only the
users of a node where a messaging system is installed can assess a mailbox : therefore, there
are several stand-alone systems.
Example:
Figure 4.1: "stand-alone" voice messaging system

Characteristics:
In this example, the four PABXs are of any type. The inter-PABX links are of any type (ABC,
BCA, ISDN, etc.). Voice messaging system VM1 is type 4635. Each user of node 1 can have a
voice mailbox (within the limits of the available resources) on voice messaging system VM1.
The users of the other nodes cannot possess a voice mailbox on voice messaging system
VM1. The sets which have a voice mailbox are at least analog type with message signalling
LED and DTMF signalling (in order to be able to select the different menus).
Comments:
This voice messaging system organisation is as simple as possible. It requires one voice
messaging system per node in the case where each network user must have a voice mailbox
(multi stand-alone case).
4-2

% &&
''
4.2.2 Networked voice messaging systems

On any PABX network, with any types of links, several voice messaging systems are installed
(maximum one per node) on different modes. Only the sets installed on the nodes possessing
a messaging system may have a voice mailbox for this messaging system. The messaging
systems can be type 4635. A messaging system network is superimposed on the different
PABXs (private network or connected over the public network) offering additional functionality.
The messaging systems can inter-communicate (send messages, acknowledgement,
message read indicator, etc.), over an ordinary voice link using the AMIS Analog and Octelnet
protocols (based on DTMF code exchanges).
Figure 4.2: Networked voice messaging systems

Characteristics:
In this example, the four PABXs are of any type and make. The inter-PABX links are of any
type (ABC, BCA, ISDN, etc.). Voice messaging systems VM1, VM2, and VM3 are type 4635.
There can only be one messaging system (maximum) per node. Each user of node 1 can have
a voice mailbox (within the limits of the available resources) on voice messaging system VM1.
The same applies for the users on the other nodes on their respective voice messaging
systems. The users of the node 4 cannot possess a voice mailbox. The sets which have a
voice mailbox are at least analog type with message signalling LED and DTMF type
numbering (for the inter-node exchanges).
Comments:
Each voice messaging system is created and managed locally, on its installation node and can
only have users who are on the same node. This configuration corresponds to a set of

4-3
Chapter 4
% &&
''
stand-alone messaging systems, equipped with certain additional services. The latter (send
messages to a list of users, acknowledgement, message read indicator) are handled by the
AMIS Analog and Octelnet protocols (for 4635 only). Based on DTMF code exchanges, they
only require an ordinary voice link in order to provide these various functions.
4.2.3 Centralised voice messaging system with integrated management

On an Alcatel-Lucent OmniPCX Enterprise CS homogeneous sub-network (with ABC-F2 type
links),the users can be installed on a different node than that of the messaging system in
which they possess a voice mailbox. In addition, the system administrator can, from the PABX
management system, allocate a voice mailbox to one of the node users without using the
specific management of the messaging system.
A voice messaging system (4635) is installed (maximum one per node) on the different notes.
Each network user can have one voice mailbox on his node or on a remote node if he does not
have one on his own node. From the user point of view, the use is totally transparent. The user
does not need to know on which node his mailbox is installed when he wants to use it (or the
mailbox of one of his correspondents for whom he wants to leave a message). The different
network messaging systems are seen as a single messaging system by the user.
Example 1:
Figure 4.3: Characteristic for the four PABX

Characteristics:
In this example, the four PABXs are Alcatel-Lucent OmniPCX Enterprise CS type. The
inter-PABX links are ABC—F2 type. Voice messaging system VM2 is type 4635. Each user of
each node can have a voice mailbox (within the limits of the available resources) on one of the
voice messaging systems. The sets of node 4 can have a mailbox in one of the different
4-4

% &&
''
voicemail system. The sets which have a voice mailbox are at least analog type with message
signalling LED.
Comments:
The messaging systems are created on their source node and the information is then supplied
to each node in the network via the distribution mechanism.
The notion of a voice messaging system network can be superimposed on this notion of
centralised voice messaging system (in the AMIS or OctelNet meaning of the word).
Example 2:
Characteristics:
The characteristics are the same for a case without AMIS (or OctelNet) network.
Comments:
This organisation combines the functionality of the centralised messaging system and the
network messaging system.
Reminder concerning the links used:

4-5
Chapter 4
% &&
''
- Allocating a voice mailbox in VM1 to set A located on node 1 is carried out from the PABX
1 (NMC 1) management system. Then PABX 1 sends the information to the messaging
system node (PABX 3) via the LOG.Nd.Seq files in the IP/X25 tunnel during the distribution
process.
- The information is exchanged between the messaging system and the node on which the
messaging system is installed by the ABCA protocol on a C1 (for the 4635).
- Message notification from the messaging system to a set (D, for example) is carried out via
the logical link using the ABC-F protocol.

To implement a centralised voice messaging system, you must proceed as follows,:
- install the voice messaging system(s) (type 4630 or 4635) on the different nodes
- install or check correct operation of the ABC type logical links between the different nodes
in the network on which the sets with voice mailboxes are to be installed
- on each node, configure the users
- using the distribution mechanism, the system provides the new information to the other
nodes in the network. However, if you do not want to use the distribution mechanism, you
can inform each node manually. In this case, certain restrictions (mentioned below) need
to be considered.
4.3.1 Installing the voice messaging system

Refer to the documentation corresponding to the voice messaging system chosen.
4-6

% &&
''
4.3.2 Installing ABC logical links

For the installation and configuration of the ABC logical links, refer to the ABC-F homogeneous
private network - Overview .
4.3.3 Configuring the centralised messaging system

The management parameters concerning the centralised voice messaging system are as
follows (some of these parameters are also valid for messaging systems in stand-alone and
ordinary network modes) :
Object name: Applications > Voice Mail
Attributes:
Voice Mail Dir. No. : corresponds to the repertory number of the voice mes-
saging system.
Directory Name : corresponds to the name given to the voice messaging
system
Voice Mail Server No. : corresponds to the number of the node in the voice
messaging system network (this notion differs from that
of the PABX node). In the case of a simple centralised
messaging system, this number is not important since
the voice messaging system is unique. In the case of a
centralised network, this number can be the same as
the PABX node one (this is not mandatory, but is re-
commended in order to simplify manage ment).
Once these parameters have been completed, the values are automatically duplicated in the
following parameters. Therefore, you need to check :
Object name: Applications > Voice Mail Dir. No.
Attributes:
Directory Number : the value must be the same as the one indicated previ-
ously
Directory Name : the value must be the same as the one indicated previ-
ously
Voice Mail Server No. : the value must be the same as the one indicated previ-
ously.
You now need to declare the voice mailbox of each user requiring a voice mailbox.
Object name: Users
Attributes:

4-7
Chapter 4
% &&
''
Voice Mail Dir No. : corresponds to the repertory number of the messaging
system in which the user possesses his voice mailbox.
Note: if you want to delete the voice mailbox of a user,
just replace the repertory number of the voice mes-
saging system by the "" string. You cannot delete a
voice mailbox that contains one or more messages that
have not been consulted.
After validating the repertory number allocated to this
parameter, a dialogue between the management sys-
tem and the voice messaging system is established to
allow the recording of new users.
If the voice mailbox cannot be created in the server, an
incident is sent.
Voice Mail Type : No Voice Mail, 4630 or 4635. This item is automatically
uupdated after validation of the previous item.
In the remainder of the menu, a new series of parameters can be configured for each user
(example for 4630 voice messaging system):
Network Prefixes authorized : This parameter authorises either an ordinary answer-
phone or a recorder answer-phone.
Personal lists authorized : This parameter authorises message drop to personal
lists.
General Lists authorized : This parameter authorises message drop to general
lists.
Voice Mail Manager : This parameter authorises the user as administrator or
else holder.
Announcement messages : This parameter is used to configure the maximum num-
length ber of blocks per message.
Conversation authorized : This parameter allows the holder to record conversa-
tions in his mailbox.
Category of Greeting : This parameter allows the holder to select whether to
play a standard announcement or a personal an-
nouncement.
In the case of the 4635H messaging system, the specific parameters are partially different:
- Voice Mail : 0.
From this box, the user can send or receive mes-
sages locally or across the network. This box has
the most possibilities.
- Listen only info.center: 1.
This box allows the caller to listen to an information
message (for example: opening times) without an-
swering. The information can be a voice message
or a fax.
- Listening/Reply info.center: 2.
This box allows the caller to listen to an announce-
ment and to reply afterwards.
4-8

% &&
''
- Rotating greetings info center: 3.

Same as type 1 box, this box can contain up to six
different messages which will be played in turn with
each call.
- Bulletin: 4.
This box is used for information distribution to a
group or set of local users.
- Announcement: 5.
This box is used for distributing information over ex-
ternal loudspeakers.
- System Distri.list: 6.
This box corresponds to a "system" distribution list,
generated by the system administrator and which
allows each user to send an identical message to
several correspondents.
- Fax deliverey: 7.
This box allows the user to send fax messages. It
receives from the caller the destination indications.
- Question, Response: 10.
This box allows a user to create a database in
which he can store information by replying to pre-
recorded questions. A series of answers constitutes
a single message.
- Transcriber: 11.
This box, which complements the previous one, is
used to listen to the answers collected, without
listening to the questions.
- Question DTMF response: 12.
This box is the same as number 10, except that the
input is not by voice but by DTMF codes
- Hotel guest (DTMF): 20.
This box is destined for hotel guests (equipped with
a DTMF numbering set) and can be interrogated
directly from the room or via a code from the out-
side.
- Hotel Guest (Rotary): 21.
Same as the previous box but with decimal num-
bering sets.
- Hotel Front Desk: 22.
This box is that of the hotel receptionist, who can
access all guest boxes.
- Extension: 28.
This box is dedicated to users sharing a same set
(up to 9 users). Each user has an individual box
that can be selected in a menu prior to use.

4-9
Chapter 4
% &&
''
- Address By Name: 29.

With this box, the user can send a message by en-
tering the recipient name using the DTMF keys
(2=ABC, 3=DEF).
- Automated Attendant: 30.
This box is used to collect incoming calls in a com-
pany. It prompts the correspondent to select a cor-
respondent (or service) by dialling or by spelling.
- Caller's menu: 31.
This box is used to route the incoming calls to the
person or service to be reached within the com-
pany. This routing is obtained by proposing menus
through which the caller navigates by answering
with DTMF codes.
- Caller'menu + Dial ext.: 32.
Same as the previous box, this box also offers the
possibility of dialling the set number of the called
party and hence to be routed more quickly
- Caller'menu + Dial Mailbox: 33.
Same as the previous box, but here the caller is
routed to the correspondent's mailbox rather than
the set.
- Transfert: 34.
This box is used to forward a call immediately to a
pre-determined set.
- Conditional Transfert: 35.
This box is used to forward a call according to the
time of day to another voice mailbox.
- Information processing
- InfoTex: 41.
This box is used as distribution point for a user
equipped with a pager.
- general fax message: 45.
This collective box is used to redirect a fax received
so that it can be printed. It is also used to store fax
messages if the printer is temporarily not available.
- voice messaging - A: 51.
sages either locally or across the network.
- Simplified tel.answering: 53.
sages either locally all across the network. Simpli-
fied use.
- Simplified voice mess.: 54.
sages either locally or across the network.
4-10

% &&
''
- conference: 58.
This box is used to record conferences or meetings
for a global duration of three hours.
- monitored: 60.
This box is destined for certain services in the com-
pany, where all members need to monitor the same
information source.
- loop back test: 61.
This box allows the system administrator to test
correct operation of the installation.
- Not Valide
4635 COS : This parameter is used to select a service class defined
in the messaging system management.
4.3.4 Distribution to the entire network

For distribution of information to the entire network, see Audit and broadcast - Overview .
4.4 Maintenance
The following maintenance commands that can be executed on the PABX (under mtcl) are
available for the technician:
4.4.1 Vmail
This command, which is common to messaging system 4635, can be used - amongst other
things - to test the link between the PABX and the messaging system. The link is correctly
established when the "link state" parameter is 3.
- 0 = V24 link not established OK,
- 1 = V24 link OK. Voice mail disabled,
- 2 = V24 link OK. Voice mail in restricted access,
- 3 = V24 link OK. Voice mail enalbled.
Managament from the PABX is possible if the status is other than 0. The audit will disable the
messaging system. Therefore, during the operation the status changes to 1 and the returns to
3 when the audit was terminated.
4.4.2 InitMevo
in the case where the technician installs a release 1.5.3 on a node which already has voice
messaging system 4635H with an earlier release. Running this command will inform the PABX
database of those users with a voice mailbox.

4-11
Chapter 4
% &&
''
4-12

! "#
5.1 Overview
5.1.1 Overview
The “Voice mail using VPS protocol” service (also called RSVP protocol) allows an external
voice mail service to connect to the Alcatel-Lucent OmniPCX Enterprise CS. The external
voice mail service connects to the Alcatel-Lucent OmniPCX Enterprise CS via analog lines.
Figure 5.1: Example showing voice mail service connection with VPS protocol
Dialog between the two machines is via DTMF Q23 signal exchange in compliance with VPS
protocol.
This service is available on the Alcatel-Lucent OmniPCX Enterprise CS with an ACT Media
Gateway or OmniPCX Media Gateway.
Note:
The old 4620 voice mail service operates with VPS protocol.
5.2 Basic description
5.2.1 Basic description

5.2.1.1 Mailboxes

5-1
Chapter 5 (

)# *
A voice mail system includes mailboxes. Some users (subscribers) have a mailbox on the
Alcatel-Lucent OmniPCX Enterprise CS, these users are called mailbox "owners". For correct
system operation, owner user number and mailbox number must be identical.
5.2.1.2 Connecting to the voice mail service
Each analog line to the voice mail service is declared as a specific type of analog user
(subscriber). Such users are referred to as "pseudo subscribers".
Figure 5.2: Voice mail pseudo subscriber

The pseudo subscribers are grouped in a hunt group and can be reached via a single number.
This number is the voice mail call number.
5.2.1.3 Calling the voice mail service
The following procedure is used to call the voice mail service:
- The user/subscriber (internal or external) dials the voice mail call number.
- The Alcatel-Lucent OmniPCX Enterprise CS dialogs with the voice mail service using VPS
protocol. It sends the number of the mailbox owner and, possibly, calling number.
- The Alcatel-Lucent OmniPCX Enterprise CS connects the caller to the voice mail service.
- The caller and voice mail service communicate using DTMF frequencies and voice guides.
A message may be deposited, the mailbox accessed or any other operation performed.
5-2

(

)# *
5.3.1 RSVP protocol

5.3.1.1 Overview
RSVP protocol governs exchanges between the Alcatel-Lucent OmniPCX Enterprise CS and
the external voice mail service. There are two version of VPS protocol:
- The old version called “Standard VPS”, that does not handle calling number.
- “Expanded VPS” (or VPS2), that handles calling number.
The Alcatel-Lucent OmniPCX Enterprise CS can work with either version depending on a
configuration option. The version selected must match external voice mail service operating
mode.
5.3.1.2 Enabling the voice mail service
When a forwarded or direct call is received by the voice mail service, the Alcatel-Lucent
OmniPCX Enterprise CS returns the following codes to the external voice mail service:
- A0:
Access to the main menu of the automatic switchboard (some voice mail systems also
have automatic switchboard capability)
- A1+ Directory number + Calling number:
Call to the voice mail service following unconditional forwarding (see note, below).
- A2+ Directory number:
Consultation call to the voice mail service.
- A3 + Directory number + calling number:
Call to the voice mail service for direct deposit in the user's mailbox (see note, below).
- A4:
Callback to the automatic switchboard following transfer failure or no answer.
- A5 + Directory number + Calling number:
Call to the voice mail service following forwarding on busy (see note, below).
- A6 + Directory number + Calling number:
Call to the voice mail service following forwarding on no answer (see note, below).
- A7:
Call to the voice mail service. Access to a mailbox once the owner has provided ID
(directory number + personal code/password).
Note:
Calling number is only presented if expanded RSVP protocol (VPS2) is used and if the number was sent.
The calling number used is the number processed by the external callback translator. It is usually
preceded by the trunk seize prefix.
5.3.1.3 Call control

In some cases, the external voice mail service may request call setup. Two signaling modes
are used to transmit call status to the external voice mail service.

5-3
Chapter 5 (

)# *
5.3.1.3.1 DTMF Q23 signaling
Send prompt code “B5”

Called party free code “B6”
Called party busy code “B7”
Called party unavailable code “B8”
Called party hung up code “B9”
Example:
The Alcatel-Lucent OmniPCX Enterprise CS sends code “B9” to inform the voice mail service that the
called party has hung up.
5.3.1.3.2 Signaling tone
Send prompt Dial tone

Called party free Ring tone
Called party busy Busy tone
Called party unavailable Congestion tone
Called party hung up Busy tone
Both signaling modes can be simultaneously enabled. In this case, the DTMF frequencies are
followed by the corresponding tones.
5.3.2 Message LED

Some sets have a message LED. The LED is:
- On when one or more messages are waiting to be consulted.
- Off when there is no message waiting to be consulted.
Change of LED status is controlled by the voice mail service. The voice mail service sends a
prefix (configured in management) followed by set call number to turn the message LED on or
off.
5.3.3 Hunt groups

The external voice mail service has one analog line per access. The lines are grouped in a
hunt group and can be accessed using a single number.
On the Alcatel-Lucent OmniPCX Enterprise CS, hunt groups are composed of 40 sets
maximum. If a voice mail service with more than 40 simultaneous accesses is required,
overflow must be declared as shown in the following figure.
5-4

(

)# *
Figure 5.3: Example of a voice mail service with 90 accesses

For the first groups, overflow is immediate (0% wait). For the final group, waiting is authorized.
5.3.4 Voice mail on an ABC network

The voice mail service may be called by a user on another PCX in the same ABC network.
All analog lines must be connected to the same PCX.
5.4.1 Implementation procedure

To put a voice mail system using VPS protocol into service, the administrator must perform the
following steps:
- Check that the site has VPS service rights (check the licenses).
- Declare the signaling mode used by the voice mail service.
- Declare the "pseudo subscriber(s)” supporting the analog lines to the voice mail service.
- If multiple accesses are to be used, declare the “pseudo subscriber” hunt group(s).
- Check that the “Voice mail directory number” object is automatically created.
- Create the message LED management prefixes and grant user rights to the pseudo
subscribers.
- Specify which users have voice mail rights.
- In the event of networked use, check voice mail service number is broadcast.
5.4.2 Checking licenses

Using the “spadmin” tool, check that the licenses allow VPS service operation:
- Lock 21, Nb of VPS ports: determines the number of VPS analog accesses allowed.
- Lock 121, CLIP on VPS : determines the number of VPS analog accesses allowed to use
the "CLIP on VPS "feature. If you want to use expanded VPS (VPS2), lock 121 must be
equal to lock 21. If you are working with standard VPS, lock 121 is not used.

5-5
Chapter 5 (

)# *
5.4.3 Declaring signaling modes

Signaling mode must be configured to match the type of voice mail service used.
Object name: System > Other System Parameters > Voice Mail Parameters
Attributes:
System Option : Select: DTMF For VPS Protocol
DTMF For VPS Protocol : Yes: the Alcatel-Lucent OmniPCX Enterprise CS generates
call control messages. These messages use DTMF protocol
(B7, B8...).
No: No DTMF call control messages.
Object name: System > Other System Parameters > Voice Mail Parameters
Attributes:
System Option : Select: Tone For VPS Protocol
Tone For VPS Protocol : Yes: the Alcatel-Lucent OmniPCX Enterprise CS generates
call control tones.
No: No call control tones.
Both modes can be simultaneously enabled. In this case, the DTMF frequencies are
immediately followed by the tones.
5.4.4 Declaring analog lines to the voice mail service

A pseudo subscriber must be declared for each line to the voice mail service.
Object name: Users
Attributes:
Directory Number : Enter the directory number of the analog line to the voice mail
service.
Directory Name : Enter the name of the voice mail service.
Shelf Address : Enter the address of the shelf to which the analog line is con-
nected.
Board Address : Enter the address of the board to which the analog line is
connected.
Equipment Address : Enter the address of the device to which the analog line is
connected.
Set Type : Select:
- 4620 (VPS + CLIP): for voice mail systems using expan-
ded VPS protocol (with calling number).
- 4610 (VPS No CLIP): for voice mail systems using stand-
ard VPS protocol (no calling number).
Entity ID : Enter the entity number of the voice mail service.
Tel. Features COS ID : Assign the appropriate COS to the set (see Phone Features
Classes of Service ).
5-6

(

)# *
Connection COS ID : Enter the connection COS of the voice mail service. Sets that
connect to the voice mail service to deposit or consult mes-
sages must be compatible.
5.4.5 Declaring set hunt groups

If there are several accesses to the voice mail system, these accesses must be grouped as
one or more hunt groups.
Object name: Groups > Hunt Group
Attributes:
Directory Number : Enter the number of the group.
Directory Name : Enter the name of the group.
Type of Hunt Group : Select:
RSVP Hunt Group.
Assigning VPS devices to a hunt group changes the group to
an RSVP hunt group.
Circular Search Type : Select:
Circular: Recommended value for groups of lines to a voice
mail service.
Overflow Directory Number : Enter the number of the overflow Group. If there are more
than 40 accesses to the voice mail service, one or more over-
flow groups must be used.
Authorized Camp on Calls % : Enter the percentage of camp on (waiting) calls allowed (0%
to 1000%). For a voice mail service, only the last group can
have a value other than 0.
Connection COS ID : Enter the connection COS of the voice mail service. Sets that
connect to the voice mail service to deposit or consult mes-
sages must be compatible as regards COS.
Dir.No Assigned to the group : Enter the call numbers of the pseudo subscribers one by one.
The maximum number of items allowed in this type of group
is 40.
Entity ID : Enter the entity number of the voice mail service.
The number of the first hunt group can be a DID number to allow consultation from an external
set.
For more information on groups, see Hunt groups - Overview.
5.4.6 Voice mail directory number

Once pseudo subscribers have been created, the system automatically creates the “Voice mail
directory number” object, that can be consulted by the administrator.
Object name: Applications > Voice Mail Dir. No.
Attributes:

5-7
Chapter 5 (

)# *
Directory Number : Check voice mail directory number.

In this case, voice mail number must be the number of
the first group.
Voice Mail Type : Check voice mail type.
5.4.7 Configuring the message LED

5.4.7.1 Declaring prefixes
The following prefixes are required to switch the message LED on and off. The same prefixes
must also be declared in the voice mail service.
Object name: Translator > Prefix Plan
Attributes:
Number : Enter prefix number. It must be compatible with the dialing
plan.
Prefix Meaning : Select "Local Features".
Local Features : Select:
- “Message deposit” to configure the prefix used to switch
on the message LED.
- “Switch off Message LED” to configure the prefix that
switches off the message LED.
The two prefixes must be communicated to the external voice mail service administrator.
5.4.7.2 Phone Features Classes of Service
To use the above prefixes, analog pseudo subscribers must have the corresponding rights.
Object name: Classes of Service > Phone Features Classes of Service
Attributes:
COS ID : Enter phone feature COS number.
Local Features (PCX Services) :
Message deposit : Enter 1 to authorize message LED switch-on.
Enter 0 to forbid it.
Switch off Message LED : Enter 1 to authorize message LED switch-off.
Voice Mail Access : Enter 1 to authorize mailbox access (message consultation).
5.4.8 Managing users with voice mail rights

To grant voice mail rights to a user, configure user voice mail number.
Object name: Users
Attributes:
5-8

(

)# *
Directory Number : Enter the user's number.

Voice Mail Dir. No. : Enter the number of the voice mail service.
5.4.9 Use on an ABC network

The system automatically broadcasts voice mail service number in the form of a network
prefix.
It is advisable to check that this prefix is present on the different nodes. If it is not present, it
may be necessary to create it manually.
Object name: Translator > Prefix Plan
Attributes:
Prefix Number : Check or enter the number of the voice mail service.
Prefix Meaning : Check or select “Network No.”.
Network No. : Check or enter network number.
Node Number/ABC-F Trunk Group : Check or enter the number of the node supporting the voice
mail service.
Number With Subaddress (ISDN) : No, subaddress is never used.
Type : Check or select “Voice mail”.
Identifier : Not used (leave the default value, 0).

5-9
Chapter 5 (

)# *
5-10

VoiceMail Alcatel

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

VoiceMail Alcatel

Uploaded by

Copyright:

Available Formats

Alcatel-Lucent OmniPCX Enterprise

Alcatel, Lucent, Alcatel-Lucent and the Alcatel-Lucent logo are trademarks of

The information presented is subject to change without notice.

Alcatel-Lucent assumes no responsibility for inaccuracies contained herein.

Copyright © 2014 Alcatel-Lucent. All rights reserved.

 Overview .................................................................................................... 1.1

         

  General information ......................................................................................1.13

 Overview .................................................................................................... 2.1

0-2          

 Overview ........................................................................................................ 2.6

 Overview .................................................................................................... 3.1

         

 Overview .................................................................................................... 4.1

 Overview .................................................................................................... 5.1

0-4          

 RSVP protocol ............................................................................................... 5.3

         

0-6          

         

1-2          

Figure 1.1: 4645 voice mail system on a dedicated CS board

1.2.2 Alcatel 4645 voice mail characteristics

         

- Messages and voice guides are stored on the hard drive.

1.2.3 Capacities and limits

1.3 Voice Mail

1.3.1 Main voice mail services

1-4          

Voice mail services are used:

1.3.2 Voice mailbox characteristics

         

1.3.2.1 Calling the voice mailbox

1-6          

- Hear the entire message again

1.3.3 Personal options (Administration and voice mailbox owner rights)

         

- Change their secret code *

1.3.4 Caller and answering machine mode

1.3.5 Other features

1-8          

1.3.5.3 System Distribution Lists (SDLs)

1.3.5.4 Distribution service

         

1.3.6 Notifying the user of messages

1.3.7 Customizing 4645 voice guides

1.3.8 Use of ports

1-10          

1.3.9 Voice mail system and PCX network

1.3.10 Hotel voice mailboxes

1.4 Automated Attendant

1.4.1 General information

         

1.4.2 Automated Attendant Entry (AA Entry)

1.4.3 Automated Attendant Menu (AA Menu)

1-12          

1.5.1 General information

         

- To program a mobile number (by the administrator)

1.5.2 Choices offered to the caller by the Ubiquity assistant

1.5.3 Ubiquity template design

1-14          

1.6 Installation procedure

Overview .................................................................................................... 1.1

General information ......................................................................................1.13

Overview .................................................................................................... 2.1

0-2

Overview ........................................................................................................ 2.6

Overview .................................................................................................... 3.1

Overview .................................................................................................... 4.1

Overview .................................................................................................... 5.1

0-4

RSVP protocol ............................................................................................... 5.3

0-6

1-2

1-4

1-6

1-8

1-10

1-12

1-14

1-16

1-18

1-20

1-22

1-24

1-26

1-28

1-30

1-32

1-34

1-36

1-38

1-40

2-2

2-4

2-6