Authorised AVAYA - NEC - Infoblox - ShoreTel - Telstra  Dealers - AUSTRALIA WIDE
30 Years - Phone Systems
Sales - Support  - Knowledge
Freecall - 1800 800 170

Contact Us

AVAYA VoiceMail - Other Features   

Using Text To Speech (TTS) Facilities within a Call Flow

A Text To Speech (TTS) engine can be added to further enhance IP Office IVR capabilities; TTS facilities can enhance the callers experience by allowing the system to read back to them any information that has been extracted from a database. For example, in a Book Shop, the caller dials into the system and is asked for an ISBN number of the book they require. The caller enters the ISBN through the telephone keypad and the system locates the title of the book from the database. As well as finding the title, the system could also look up the author of the book and whether there were any books in stock. By using TTS, the system could now respond to the call:

"The book, Lord Of The Rings, costing $6.99, written by J R R Tolkien is in stock".

 

The languages currently supported by the Avaya TTS engine are:

Chinese (Mandarin)
Dutch
English (UK)
English (US)
French (Standard)
German
Japanese
Italian
Korean
Norwegian
Portuguese (Brazilian)
Russian
Spanish
Spanish (Latin)

 

TTS Licensing

TTS is an optional licensed component of VoiceMail Pro, and adds a TTS resource pool for VoiceMail Pro to use and release as required. TTS licenses are independent of VoiceMail Pro licenses. If a system integrator wants to use a different TTS language set from those supplied by Avaya this can be done by using the 3rd party TTS license instead of the Avaya language TTS. Both license types are based on a concurrent usage model.
 

Visual Basic (VB) Scripting

The VoiceMail Pro call flow programming interface has been extended to allow an administrator to provide Visual Basic (VB) scripted logic that can be interpreted by the VoiceMail Pro server. This ability allows system administrators to program the voice system via VB Scripts thus providing additional choice and flexibility in providing IVR applications. The VB script action contains a VB-Scripting parser (Syntax checker) to ensure the legitimacy of the administrator derived VB Script before it's incorporation. Each VB script action used within a call flow can contain a maximum of 10,000 characters; however a call flow may contain multiple VB script actions within it.

VB Scripting on IP Office VoiceMail Pro is an optional licensed component.
 

Extended Personal Greetings

In INTUITY emulation mode, the VoiceMail Pro system has the ability to hold a number of greetings within each user’s mailbox that can be played to a caller. In addition to the standard mailbox greetings, the extended personal greetings provide the ability to present the caller with a greeting that reflects where the call has come from (internal or external) or why the called party is unable to take the call. A mailbox user can configure the responses played back to the caller, based upon the reason the caller was routed to the voicemail. The supported call states are:

Busy/Engaged
The user is currently on a call and unable to accept a second call.
No Reply
The user is away from the desk and unable to take a call.
Internal
A greeting to be played to internal calls
External
The greeting to be played to external callers
Out Of Hours
The greeting played when a hunt group is operating 'out of hours'. Out of hours is defined with IP Office Manager and is only applicable to Hunt Group mailboxes.

 

A greeting can be recorded for each of the above conditions through the Telephone User Interface (TUI). If a recording is made for each condition, the order of play back to a caller will be:

1. Out of hours (Hunt group mailboxes only).
2. Internal/External greeting.
3. Busy/Engaged.
4. No reply.

 

A mailbox owner will need to record greetings against these conditions to deliver the greeting that they wish to present to a caller. Phone Manager Pro users can record and manage their voicemail greetings through the Phone Manager GUI.
 

Hunt Group Broadcast Messages

With VoiceMail Pro, two modes of operation exist for the handling of hunt group messages.  The method used is configured for the group through the IP Office Manager.

Hunt group mode
Messages are stored in the Hunt Group mailbox and Message Waiting only informs those individuals configured for message waiting indication from that group. This is ideal for scenarios where only a few people such as a call center supervisor need to be initially aware of group messages. Any message waiting light lit by this is extinguished when the new hunt group message is accessed by a user. This is the default mode of operation.
Broadcast mode
Messages are not stored in the hunt group mailbox. Instead they are broadcast (copied and forwarded) to the individual mailboxes of the entire hunt group membership. This lights the individual messages waiting light of each user of the Hunt Group until they access their mailbox.

Cascaded Out-Calling

VoiceMail Pro can send a notification, with an escalation capability, that a new voice message has been received in a user's mailbox to specified phone number(s). This is particularly useful in environments such as healthcare and support where important voice messages are left and need to be answered promptly - even outside of office hours.

For example should a patient leave an important message to the main number of the doctor’s office, the voicemail system can ring the doctor at the office then on no response escalates to the doctor’s mobile/cell phone, his/her home phone or the doctor on duty after a programmable timeout. This avoids having to rely on an external answering service and allows mobile/cell and home phone numbers to remain private.

The voicemail notification can be sent for:

Any new voice messages
Any new priority voice messages

 

Mailbox owners can configure their own options from their handset (Telephone User Interface or TUI) and through their IP Office Phone Manager.

Create own Time Profile – defining when notification should take place (e.g. office hours only)
Out-calling destinations – defining where notification should take place and in which priority order

 

Five destinations can be defined by the mailbox owner through the TUI (Telephone User Interface). The destinations selected in the escalation list are called in sequence. The possible destinations are:

Desk
Mobile/Cell
Home
Delegate
Other

 

Each time an outcall event occurs, each number in the escalation list will be called until either the call is answered, or the end of the list is reached. This process will be repeated on each retry attempt, for the number of retries set.

Out-calling preferences are set for global operation via the VoiceMail Pro Client. Out-calling is only available in INTUITY Mode. The administrator sets the number of retries and time interval between retries on a system-wide level.
 
 
Personal Distribution Lists

Personal Distribution Lists are only available with VoiceMail Pro when operating in INTUITY emulation mode.  The feature provides the ability for a user to distribute a voicemail message to a list of recipients simultaneously.  Lists can be configured by a voicemail box subscriber either through their voicemail box telephone user interface (TUI) or through the desktop PC application Phone Manager Pro.

The features available to a voicemail box subscriber include:

Create up to 20 lists with 360 members per list
Mark a list as Private or Public, Private lists can not be accessed by any other voicemail subscriber.  Public lists can be used by other subscribers but can not be edited.
Public lists can be copied from one subscriber to another by adding the contents into a new list.
Subscribers can ‘Create’ new lists, ‘Scan’ contents of an existing list or ‘Modify’ existing lists.
List members can be added by using the station number or mailbox name (names are not supported for VoiceMail Pro Networked Messaging mailboxes).
Lists can include voicemail boxes that exist on other Avaya voicemail systems that are available through VoiceMail Pro Networked Messaging.
Lists can be added together, duplicate members are automatically removed.  This includes public lists owned by other voicemail subscribers.
Mailing lists are accessible to the user at any ‘send message’ and ‘forward message’ option within the user's voicemail box.
When displayed within Phone Manager Pro, distribution lists can have a list description added to it, this is only visible within Phone Manager Pro.
Call Recording

VoiceMail Pro also offers call recording services that allow the automatic/manual recording of calls for a variety of applications, such as for training purposes or to monitor abusive callers.  As standard, recordings can be directed to the called extension’s voicemail box or to any other mailbox for later retrieval.  Alternatively, recordings can be stored in a central database for retrieval through a Web based browser by using ContactStore for IP Office.

The system administrator can select whether all calls are required to be automatically recorded or just a selection of calls. Alternatively, calls can be manually selected for recording.  If for any reasons resources are not available then a recording may not be taken (for example all voicemail ports are busy).

VoiceMail Pro provides a number of methods for triggering the recording of a call.

Most of the settings and controls for automatic voice recording are accessed through the IP Office Manager application. The proportion of incoming and/or outgoing calls that should be recorded and the time-period during which Voice Recording should operate can be selected.

User Recording
The calls to and/or from a particular user can be automatically recorded. By default the recordings are placed in the user's mailbox
Hunt Group Recording
The calls to a particular hunt group can be automatically recorded. By default the recordings are placed in the hunt group's mailbox, but there is the ability to select a target mailbox made for or on behalf of a subscriber.
Account Code Recording
An account code can be applied to a call by the user before it is made. This can be used to trigger recording of outgoing calls.
Caller ID Recording
Account codes can be assigned to a call by Caller ID matching. This allows recording to be based on a Caller ID match.
Time Profiles
For each user, hunt group and/or account code, an IP Office time profile can be used to determine when auto-recording is used.
Incoming Call Routes
Incoming Call Routes can trigger automatic call recording.

 

Note: It is possible for several recordings to be made of the same call.  For example, if both automatic hunt group recording and automatic user recording are applicable to the same call, separate recordings are produced for both the hunt group and the user.  Recording only continues while the party triggering the recording is part of the call, for example:

Recording triggered by a user stops when that call is transferred to another user.
Recording triggered by a hunt group continues if the call is transferred to another member of the same group.
Recordings triggered by an incoming call route last until the call is cleared from the system.

 

Call recording uses the conference facility and so is subject to the conference restrictions of the IP Office system. For some situations, it may be a requirement that call parties are advised that their call is about to be recorded. This is done by switching on the Play Advice on Call Recording option via the VoiceMail Pro client. The maximum length of any call recording is 60 minutes

Centralized Messaging with Avaya Communication Manager

Where IP Office is deployed in an Avaya Communication Manager (ACM) Environment, it may be desirable to use one centrally managed voicemail system (INTUITY or Modular Messaging) to provide voicemail services to IP Office users. IP Office can be configured to use an INTUITY or Modular Messaging system over a remote connection such that all messaging calls divert to this location and message waiting indications are provided from the remote location and are displayed correctly on IP Office extensions. Connectivity must be either an E1 or T1 circuit or an IP trunk running QSIG services. In addition to the IP Office license Key (Centralized VM with ACM RFA) that enables this service, further license keys may be required on the ACM system.

PC Requirements

General Requirements

An IP Office Feature Key is required for VoiceMail Pro.
License for VoiceMail Pro and any additional ports required. If VoiceMail Pro server is installed without a license it will run for 2 hours and then shutdown.
License for all options of VoiceMail Pro being installed.
IP Office VoiceMail Pro CD.
Installation on the same PC as being used for IP Office Manager is recommended.
Switch off any PC and hard disk sleep, power down, suspend, hibernation modes.

 

PC Specification

Always refer to the latest Avaya IP Office Technical Tip or Technical Bulletin for any updated information with regard to Operating Systems, Service Packs or PC hardware
Refer to Technical Specifications section of the Product Description for Operating System and Hardware requirements

 

Network

The Voicemail PC must be configured and tested for TCP/IP networking.
The Voicemail PC must have a fixed IP address.

 

Disk Space

A compact or typical installation requires 500MB for the VoiceMail Pro software. A full installation requires up to 2GB of disk space. However prompts and recorded messages consume an additional 1MB of disk space per minute.

For Avaya IP Office - Small Office Edition, you can expect to require at least 200 minutes of message recording space, that is 200MB.
For a busy environment you can expect to require at least 1,000 minutes of message recording space, that is 1GB.

 

Web Server Operation

If web browser access to Unified Messaging Services (UMS) web service and or campaigns is required, Microsoft IIS Web Server must be installed on the Voicemail PC before VoiceMail Pro. Both applications must run as a service. A server operating system is required for IIS.

 

UMS Client Requirement

UMS IMAP access requires IMAP4 capable email clients such as Outlook. For voicemail web access see Web Server Operation above

 

Voicemail Email Connection

Voicemail Email operation is supported using either MAPI or SMTP. MAPI requires the VoiceMail Pro server PC to have a MAPI compliant email client install. See Voicemail Email Integration.

If Text to Speech is installed, email text to speech is supported using MAPI.

In both cases above, full email sending from the server PC to users PC should be configured and tested before VoiceMail Pro installation using the same PC user account under VoiceMail Pro will be installed.

 

IMS Pro Connection

IMS requires the Voicemail server to use MAPI.

Integrated Messaging Pro (IMS) is supported on Microsoft Exchange 5.5, 2000 and 2003.
An Exchange User account for user 'IMSAdmin' will be needed to as part of IMS installation.
Must be a member of the same Domain as VoiceMail Pro Server.
A list equating Exchange User account names with voicemail box users.

 

Voice Recording Library Management

IP Office Voice Recording Library (VRL) application is IP Office ContactStore. This application and its installation are documented separately. However:

Avaya ContactStore for IP Office should be installed after VoiceMail Pro has been installed and its operation verified.
Avaya ContactStore for IP Office must use a separate hard disk partition for its message archiving from that used by VoiceMail Pro for current mailbox messages. Use of a separate hard disk or installation onto a separate server PC are alternatives.
The use of RAID 1 or RAID 5 are recommended.
The use of a DVD recorder for long-term archiving is recommended.
A figure of 7.2MB per hour of archived recordings is given.
The archived messages held by IP Office ContactStore are accessed via web browser using the port address 8888. This port address is not configurable and so it is necessary to ensure that it does not conflict with any other web server service running on the same server PC.

 

 

 

 

Powered by OnlyBusiness.com Copyright ©  2009-2012  • Planet Telecommunications (NSW)  1800 800 170
                                    • Sydney, Melbourne, Brisbane, Perth