Skip Headers
Oracle® Voicemail & Fax Administrator's Guide
10g Release 1 (10.1.2.4.1)

Part Number B25458-03
Go to Documentation Home
Home
Go to Book List
Book List
Go to Table of Contents
Contents
Go to Index
Index
Go to Master Index
Master Index
Go to Feedback page
Contact Us

Go to previous page
Previous
Go to next page
Next
View PDF

1 Overview of Oracle Voicemail & Fax

This chapter discusses the following topics:


See Also:

Note 416319.1 on http://www.metalink.com for information discovered after this document was published.

Oracle Voicemail & Fax Features

This section describes the major features of Oracle Voicemail & Fax.

Voice

Oracle Voicemail & Fax is a voicemail system that answers phone calls and saves voice messages in users' Inboxes. It provides greater flexibility than other phone answering systems and increased productivity by allowing users to access their voicemail messages through the interface of their choice: telephone, e-mail client, or Web browser. Voicemail messages can be accessed through e-mail clients as a WAVE file attachment. Oracle Voicemail & Fax provides a basic Dual-Tone Multifrequency (DTMF) interface, providing the capability to change users' preferences using the telephone interface. Because Oracle Voicemail & Fax is a single-repository solution, actions taken on a voicemail message or on a users' account preferences through the telephone interface are visible through other channels.

Fax

Oracle Voicemail & Fax provides inbound facsimile capabilities. Faxes sent to a user's phone number are delivered to the user's Inbox as a message attachment. Faxes are stored as TIFF attachments in MIME-compliant messages that can be printed or forwarded to any e-mail address using standards-based clients or Web clients.

Access to Voicemail and Fax Through GUI Clients

Oracle Voicemail & Fax provides access to voicemail messages through multiple channels, including the telephone, standards-based clients (IMAP4 or POP3), and through the Web. Because messages are stored in the industry-standard WAVE and TIFF formats, many readily available media players and graphics readers can be used. This allows great flexibility in accessing messages from the computer and for forwarding the messages. Because the user's e-mail, voicemail, and fax messages are in a single Inbox, this increases users' productivity and provides great ease in using the product.

Notification Through Wireless Devices

Oracle Voicemail & Fax, along with other Oracle Collaboration Suite components, provides a comprehensive set of notification features. Making use of the server-side rules in the Oracle Collaboration Suite Database, users can define their own rules for when and how they are notified. Oracle Voicemail & Fax supports e-mail notification through SMTP-enabled pagers and cell phones. Oracle Voicemail & Fax enhances the Oracle Collaboration Suite 10g Mobile Collaboration component of Oracle Collaboration Suite. This component provides gateways for direct one-way and two-way communication with a number of devices, including many popular Systems Management Server (SMS) systems and pager networks.

Centralized System Administration

Oracle Voicemail & Fax administration is integrated into Oracle Enterprise Manager, allowing for centralized management and systemwide monitoring of the Oracle environment. Oracle Voicemail & Fax supports multiple domains within the same system and allows for central or distributed system administration in a hosted environment.

Self-Service User Preferences Management

Oracle Voicemail & Fax provides Web-based preferences management through the Oracle Collaboration Suite 10g WebMail client, Oracle Collaboration Suite 10g Web Access Client, and Oracle Connector for Outlook. Users can make distribution lists accessible to the telephone user interface (TUI) menu, set their voicemail password, set the language in which they hear their voicemail prompts, select the active greeting, and select the dial-out extension. Users also have the option of setting their preferences through the TUI.

Oracle Voicemail & Fax Architecture

The following topics are covered in the subsequent sections:

Application Flow in an Oracle Voicemail & Fax System

A call comes in to the PBX (private branch exchange). If the call is not answered, the PBX transfers the call to the Voicemail & Fax Server. The Voicemail & Fax Application retrieves information about the user and the user's preferences and system information from Oracle directory server, for example, the language in which to play the voicemail prompts, and the voicemail user's recorded greetings. Voicemail messages are stored and retrieved from the Oracle Collaboration Suite Database. The Oracle Collaboration Suite 10g Mail IMAP server retrieves voicemail messages from the database and displays these messages in the user's Inbox. When the voicemail user calls in to the voicemail system for her messages, PL/SQL APIs are used to retrieve the voicemail messages from Oracle Collaboration Suite Database (Figure 1-1).

Figure 1-1 Oracle Voicemail & Fax Application Flow

Oracle Voicemail Fax call flow

Oracle Collaboration Suite Database

Oracle Voicemail & Fax uses the Oracle Collaboration Suite Database as the repository for all voicemail and fax messages, the same message repository used by Oracle Mail. The database provides common access methods for e-mail, voicemail, and fax messages in the format that is appropriate. For example, voicemail and fax messages are stored in VPiM format. All messages are available through standard IMAP4 or POP3 e-mail clients. A single repository makes the voicemail messages simultaneously accessible through e-mail or through the telephone interface.

Oracle Voicemail & Fax uses the Oracle Mail PL/SQL application programming interface (API) to access the database to store and retrieve voicemail messages in the user's Inbox.The database is accessed whenever a message is left for a voicemail user or if a voicemail user accesses the voicemail system to listen to his or her messages.

Although the Oracle Collaboration Suite Databases may be on the same physical server as the Voicemail & Fax Applications, in most situations, the databases are installed on a different server. A minimum of one Oracle Collaboration Suite Database is required for a Voicemail & Fax system.

Oracle Directory Server

Information about the user and the user's preferences, and system information is stored in the Oracle directory server. Oracle Voicemail & Fax enhances the user information and preferences of Oracle Mail and extends this to include attributes specific to voicemail. The voicemail attributes include site information, the user's recorded greetings, access to the voicemail and fax features, and the user's phone number. System configuration information stored in Oracle directory server include attributes such as system parameters, menus, and prompts.

Voicemail & Fax Server

The Voicemail & Fax Application is installed on top of the Telephony Server. Along with Oracle Container, they comprise the Voicemail & Fax Server. These components are described in more detail later in this chapter.

Oracle Mail IMAP Server

IMAP services are part of the Oracle Mail component of the Oracle Collaboration Suite. These services provide access to voicemail messages and faxes to a user using a standard IMAP client. The voicemail messages can be played using any media player that supports WAVE files. The fax messages can be viewed using a graphics viewer that supports TIFF format.

Voicemail & Fax Server Architecture

The components of the Voicemail & Fax Server (Figure 1-2) are the Voicemail & Fax Application, the Telephony Server, and the Oracle Container Subsystem. These components are described in the following sections.

Figure 1-2 Voicemail & Fax Server Architecture

Description of Figure 1-2 follows
Description of "Figure 1-2 Voicemail & Fax Server Architecture"

Telephony Server

The Oracle Telephony Server (OCS) is an Oracle implementation of the CT Server standard proposed by Enterprise Computer Telephony Forum (ECTF). This standard defines the infrastructure required to build platform-independent computer telephony applications. The Oracle Telephony Server manages the telephone calls and the resources. The Oracle Telephony Server runs on an Intel-based server (with the Windows 2000 or 2003 operating system) and consists of the Telephony Monitor Service and Intel NetStructure® Host Media Processing (HMP) Software. Host Media Processing (HMP) Software provides a Voice over Internet Protocol (VoIP) interface based on the Session Initiation Protocol (SIP) using the server's existing Ethernet NIC (Network Interface Card).

The Oracle Telephony Server uses the s.410 (also known as JTAPI Media) specification, which defines the application-level programming interface, and the s.300 specification. The Oracle Telephony Server uses the Generic JTAPI (GJTAPI) implementation of the JTAPI standard.

Oracle Container Subsystem

The Oracle Telephony Server provides encapsulated APIs to all processes. One of these encapsulations is the ECTF Container System standard. The Container System allows processes to retrieve and store recordings and to manipulate files. The Container System uses the Oracle framework to store and retrieve data in the Oracle Collaboration Suite Database.

The Container System provides direct access to the Oracle Collaboration Suite Database through Oracle Call Interface (OCI) and PL/SQL. The Container System allows two types of data storage manipulation: file system & database. These two types of operations are separated into the File System Container and the Oracle Container respectively.

Oracle Voicemail & Fax Application

Oracle Voicemail & Fax consists of the following services:

  • Routing Service receives and passes calls to other services.

  • Retrieval Service authenticates callers and allows voicemail users to retrieve and respond to voicemail messages and manage their voicemail accounts.

  • Recording Service plays the greeting, records messages, and delivers messages.

  • Interactive Voice Response (IVR) Service runs simple call answering programs that system administrators can define and customize.

  • Call Transfer Service transfers calls to the phone number configured as the operator or attendant number.

  • Message Delivery Monitor Service tracks and reports the time it takes to deliver messages.

  • Message Recovery Service recovers and redelivers messages that are not successfully delivered the first time.

  • Telephony Monitor Service runs, tracks and reports on the status of the Telephony Server.

  • Fax Receiving Service receives and delivers fax messages.

  • MWI (Message Waiting Indicator) Service activates and deactivates users' message waiting indicators.

Some services are optional such as the IVR Service, Fax Receiving Service and Message Delivery Monitor Service. The services, collectively, are referred to as the Voicemail & Fax Application. There is one Voicemail & Fax Application for each Telephony Server, and multiple Telephony Servers can be included in a single Oracle Voicemail & Fax system.

The PBX routes calls to the Oracle Telephony Server. Calls are received by the Oracle Telephony Server and are routed to Oracle Voicemail & Fax.

Oracle Voicemail & Fax Architecture Stack

The Oracle Telephony Server encapsulates access to Host Media Processing (HMP) Software through Intel Global Call APIs. The Oracle Telephony Server abstracts out access to file systems including reading, writing, and deleting files on local file systems.

Figure 1-3 Oracle Voicemail & Fax Architecture Stack

Description of Figure 1-3 follows
Description of "Figure 1-3 Oracle Voicemail & Fax Architecture Stack"

Oracle Voicemail & Fax Deployments

There are two basic types of VoIP Voicemail & Fax deployments: single-site and multisite deployments. In a single-site VoIP deployment (Figure 1-4), there is a direct connection between the PBX and the Voicemail & Fax Server. One or more Voicemail & Fax Servers at one site connect to an Oracle Collaboration Suite Database and to Oracle Internet Directory. The Infrastructure Tier may be in the same location as the PBX and server or, as in this example, may be in a different location.

Figure 1-4 Single-site, VoIP Gateway Deployment

Description of Figure 1-4 follows
Description of "Figure 1-4 Single-site, VoIP Gateway Deployment"

In a multisite VoIP deployment, there are one or more Voicemail & Fax Servers for each PBX, each serving a different location (Figure 1-5). For example, there may be one Voicemail & Fax Server for each of the following cities: San Francisco, New York, and London. All Voicemail & Fax Servers connect to a single, centralized Infrastructure Tier located in Denver.

Figure 1-5 Multisite VoIP Deployment

Description of Figure 1-5 follows
Description of "Figure 1-5 Multisite VoIP Deployment"


Note:

See Chapter 12, "Deploying Oracle Voicemail & Fax," in Oracle Collaboration Suite Deployment Guide for more information about deployment options. See Chapter 14, "VoIP Gateway Deployments" for more information about Voice over IP deployments.

How the Oracle Voicemail & Fax Services Work

There are two basic types of calls received by a voicemail system: forwarded calls and direct calls. A forwarded call is a phone call that is not answered by the intended recipient (also known as the called party), and therefore, the call is transferred to the voicemail system. A direct call is a call made by a voicemail user to the voicemail system, typically to retrieve messages or to manage his or her voicemail preferences.

The sections that follow describe how calls are handled by the Voicemail & Fax Application. The Oracle Telephony Server performs as a resource manager and interacts with each of the application's services to route calls between the services. The Telephony Monitor Service also acts as the Oracle Telephony Server. It manages incoming calls, call resources, and passes calls between Oracle Voicemail & Fax services.

Routing a Forwarded Call

A call comes in and the called party does not pick up the call. The PBX passes the call to the Telephony Server, and the call is picked up by the Routing Service. The Routing Service retrieves call-detail information from the PBX, including the caller's phone number, the destination phone number, and how the call arrived at the voicemail system (direct or forwarded). For a forwarded call, the Routing Service queries the PBX-Application Cluster which handles the phone number and checks the PBX-Application Cluster's call routing map. If the call's destination number is listed in the call routing map, the call is passed to the IVR (Interactive Voice Response) Service. All other forwarded calls are passed to the Recording Service, which retrieves the called party's information from the Oracle directory server and verifies that the called party is enabled for voicemail. Then, the Recording Service looks for a greeting, in the following order, until it finds one and it plays the greeting:

  1. Called party's recorded greeting

  2. Generic greeting with the called party's recorded name

  3. Generic greeting with the called party's phone number

After the message is recorded, the Recording Service delivers the message to the voicemail user's Inbox on the Oracle Collaboration Suite Database.

If a fax tone is detected at any time during the interaction, the call is passed to the Fax Receiving Service, which receives the fax message and delivers the message to the voicemail user's Inbox. If the user chooses to transfer the call to an attendant, the call is passed to the Call Transfer Service, which performs this task.

Routing a Direct Call

A voicemail user calls into the voicemail system and the PBX passes the call to the Telephony Server where the Routing Service picks up the call. The Routing Service retrieves call-detail information from the PBX, including the caller's phone number, the destination phone number, and how the call arrived at the voicemail system (direct or forwarded). If it is a direct call, the Routing Service passes the call to the Retrieval Service, which formulates the mailbox number by using the caller ID or by prompting the voicemail user to enter a mailbox number. The Retrieval Service verifies that the user is a valid voicemail user against the data stored in Oracle directory server. Once the user has been verified, the user is prompted for a password, and the voicemail system authenticates the password against Oracle directory server. After the user has been successfully authenticated, the Retrieval Service interacts with the Oracle Collaboration Suite Database to retrieve voicemail messages and other account information.

After being authenticated by the voicemail system, the voicemail user is given the following options:

  • Listen to new or saved messages

  • Send a message to another voicemail user

  • Reply to the sender of a voicemail message

  • Forward the voicemail message to one or more recipients, with the option of including a message

  • Perform administrative tasks such as changing passwords and recording or changing greetings

When the voicemail user listens to a message, the Retrieval Service plays the message. If the user chooses an option that involves creating a message, the Retrieval Service passes the call to the Recording Service. After the message is recorded and delivered to the user's Inbox by the Recording Service, the call is returned back to the Retrieval Service, and the user is given the choice to select another menu option.

Transferring Calls to an Attendant

During a call, if the caller chooses the menu option to transfer the call to an attendant, the call is passed to the Call Transfer Service, which looks up the attendant's number in Oracle directory server. It starts with the user profile, and if none is configured at the user level, it searches through the user's parent hierarchy. The call is transferred to the attendant through the PBX. (The Call Transfer Service returns the call to the PBX, which dials the attendant's phone number.)

Who the user is varies depending on which service passes the call to the Call Transfer Service. If the Retrieval Service passes the call, (that is, for a direct call), then the user is the authenticated voicemail user who is logged in to his mailbox. If the Recording Service hands off the call, (that is, for a forwarded call), then the user is the voicemail user for whom the caller recorded a message or for whom the caller intended to record a message.

Backup Message Delivery

There are times when the Recording Service and Fax Receiving Service attempt to deliver a recorded message to the Oracle Collaboration Suite Database and encounter errors. These messages end up in the file system queue of the Message Recovery Service, which makes periodic attempts to redeliver the message. Once the Message Recovery Service successfully delivers a message to the database, the message is deleted from its queue.

The Message Recovery Service maintains connections to all Oracle Collaboration Suite Databases configured for the host on which the Voicemail & Fax Application is installed. Each time the service picks up a message from the file system queue, it attempts to send the message in its queue through its connections to each Oracle Collaboration Suite Database until it is successful. If it encounters an error sending the message through every Oracle Collaboration Suite Database, it requeues the message on the file system and picks it up the next time it tries to deliver queued messages.

Delivering Fax Messages

When a forwarded call is passed to the Recording Service and the service detects a fax tone, it passes the call to the Fax Receiving Service, which looks up the called party's information in the Oracle Internet Directory. If the Fax Receiving Service determines that the called party is a valid user with the fax access feature enabled, it receives the fax and sends it to the called party's Inbox in the Oracle Collaboration Suite Database.

Forwarding Calls to an Interactive Voice Response System

Oracle Voicemail & Fax provides administrators with the ability to create and customize simple call answering programs. These call answering programs are sometimes referred to as auto attendants or Interactive Voice Response (IVR) systems. Oracle Voicemail & Fax IVR systems play messages, transfer calls, search the user directory, offer simple DTMF (Dual-Tone Multifrequency) menus, and integrate with the Recording Service and Retrieval Service. The IVR Service supports multiple administrator-defined IVR deployments, each of which may specify an action for business hours, nonbusiness hours, holidays, and special times that fit none of these categories. When a forwarded call is passed to the Routing Service, it consults the PBX-Application Cluster's call routing map, which contains a mapping of telephone numbers to IVR deployments. If the call routing map contains a mapping for the originally dialed telephone number, the Routing Service sends the call to the IVR Service. The IVR Service then executes the applicable action for the appropriate IVR deployment.

Oracle Voicemail & Fax Monitoring Services

There are two monitoring services, the Telephony Monitor Service and the Message Delivery Monitor Service. The Telephony Monitor Service monitors the Telephony Server and reports the status and some key metrics of the Telephony Server to Oracle Enterprise Manager. It periodically checks the status of the server and the number of active calls being handled by the server.

The Message Delivery Monitor Service measures the time it takes for a message to be delivered to the Oracle Collaboration Suite Database. The service sends test messages to a test account on each Oracle Collaboration Suite Database, and reports the time it takes for the test message to arrive in the Inbox of the target Oracle Collaboration Suite Database.

PBX-Application Clusters

A PBX-Application Cluster defines the relationship between a Voicemail & Fax Application and a PBX. The Voicemail & Fax Application needs to have certain information about the PBX in order to work with the PBX. For example, Oracle Voicemail & Fax converts all phone numbers into international format. So it needs to know in what form the PBX passes phone numbers to the application, so it can convert the phone numbers to international format. When the application sends a phone number to the PBX, it needs to convert this number from international format into a form that the PBX can dial, so it needs to know how to do this conversion. The way the PBX dials an internal phone number differs from dialing an external number, and the application needs to know which phone numbers belong to the PBX and which are external phone numbers, and what rules to apply. These and other specifications that are required for a PBX and Voicemail & Fax Application to work together are contained in the concept of a PBX-Application Cluster (Figure 1-6).

Figure 1-6 PBX-Application Cluster

Description of Figure 1-6 follows
Description of "Figure 1-6 PBX-Application Cluster"

This configuration applies to any Voicemail & Fax Application that is associated with the PBX-Application Cluster. By creating this definition for a PBX, you can associate it with any Voicemail & Fax Application. System administrators can add another Voicemail & Fax Application without having to configure the PBX to work with it by using the existing PBX-Application Cluster configuration (Figure 1-7).

Figure 1-7 Adding Another Voicemail & Fax Application to a PBX-Application Cluster

Description of Figure 1-7 follows
Description of "Figure 1-7 Adding Another Voicemail & Fax Application to a PBX-Application Cluster"

System administrators can exchange one Voicemail & Fax Application for another, again, without any additional configuration (Figure 1-8).

Figure 1-8 Exchanging One Voicemail & Fax Application for Another

Description of Figure 1-8 follows
Description of "Figure 1-8 Exchanging One Voicemail & Fax Application for Another"