2
Oracle Voicemail & Fax Processes

This chapter discusses the telephony processes of the Oracle Voicemail & Fax system.

This chapter contains the following topics:

• Overview
• Managing Oracle Voicemail & Fax Processes Through Oracle Enterpise Manager
• Oracle Voicemail & Fax Process Parameters
• Oracle Voicemail & Fax Log Files

Overview

The Oracle Voicemail & Fax telephony component consists of several processes based on the computer telephony server (CT server) architecture from the enterprise computer telephony forum (ECTF). Each process interacts with a call, performs the task(s) at hand and transfers the call to different processes.

These are the telephony processes:

• Routing Process: Answers inbound calls to the Oracle Voicemail system and directs them to the recording or retreival process
• Voice Mail Recording Process: Records voice messages and stores them in the mail store
• Voice Mail Retreival Process: Interacts with the user and retrieves and renders messages from the mail store
• Fax Receiving Process: Receives and stores fax messages in the mail store
• Transfer Process: Manages and transfers calls when a user wishes to speak with an operator
• Recovery Process: Manages queued voice mail and fax messages if the mail store is unavailable
• AQMWI Process: Manages the message waiting indicator (MWI) requests from the mail server
• MWI Service Process: Manages the message waiting indicator (MWI) for individual switch implementations

The following are examples of how a call goes through the various processes:

• Recording: The routing process picks up the call from the PBX and parses call detail information. Once the routing process determines that it is a recording call type, the call is handed off to the recording process. If a fax tone is detected, then the call is routed to the fax receiving process. Recording and fax receiving processes interact with Oracle Internet Directory and the mail store to store the recorded message. Calls to be transfered to an operator are handed off to the transfer process.
• Retreival: The routing process picks up the call from the PBX and parses call detail information. Once the routing process determines that it's a retreival call type, the call is handed off to the retreival process. The retreival process interacts with Oracle Internet Directory and the mail store. For reply and forward, the call is handed off to the recording process and for transfers, the call is handed off to the transfer process.
• MWI: The MWI service process activates and deactivates of MWI for a specific PBX. When a new voice mail message arrives into an Oracle Voicemail & Fax subscriber's inbox, a message waiting indicator (MWI) activation request is generated for the advanced queueing message waiting indicator (AQMWI) process. The AQMWI process interacts with Oracle Internet Directory, looks up the corresponding MWI service process and relays the request to that MWI service process. Conversely, when there are no more unread voice mail messages in the subscriber's inbox, an MWI deactivation request is generated to the AQMWI process and the same procedure is followed.

Routing Process

When the CT server receives a call from the PBX, the routing process answers the call. This process retrieves call detail information from the PBX, which indicates whether the call is a direct call to the voice mail system or a forwarded call from an unanswered or busy extension. The routing process sends forwarded calls to the voice mail recording process and direct calls to the voice mail retreival process. If no call detail information is available, the routing process allows the caller to between voice mail recording or voice mail retreival.

The routing process maintains a pool of worker threads. Each thread can handle one call at any time. The routing process retrieves call details through a simplified message desk interface (SMDI) or the Intel CT Media, based on the PBX type and Oracle Voicemail & Fax configuration.

Voice Mail Recording Process

The Oracle Voicemail & Fax voice mail recording process records and sends voice mail messages. Messages can be marked with normal or urgent priority before they are sent. To assist in addressing messages, the recording process provides access to a user directory that callers can search by dialing users' names on a telephone keypad. The voice mail recording process maintains a pool of worker threads. Each thread can handle one call at any time. There are six scenarios in which the caller interacts with the recording process.

• Normal Recording: When the routing process receives a forwarded call, the process routes the call to voice mail recording and provides the extension number of the call's intended recipient. Voice mail recording acquires the recipient's information from Oracle Internet Directory. The process verifies that the recipient has telephone access enabled and plays the recipient's greeting message: a personal greeting, a vacation greeting, a default greeting with a recorded name, or a default greeting with a telephone number. If a fax calling tone is detected while the greeting is played, the call is routed to the fax receiving process. The caller records a message, and can choose to edit it. Finally, the voice mail recording process interacts with the CT server to store the voice mail in the mail store.
• Unknown Origin Recording: When the routing process receives a call without call detail information and the caller chooses to record a message, the routing process sends the call to the voice mail recording process, prompting the caller to specify a recipient.
• The caller may either enter the user's telephone number, or he may search a directory of users at the site that he called. After obtaining the recipient from Oracle Internet Directory, the system plays the user's greeting.
• Reply to a Message: When users choose to reply through the telephone user interface to a voice mail from another Oracle Voicemail & Fax user, the voice mail retreival process routes the call to voice mail recording. This process plays a generic system greeting, the user records a message, and can choose to edit it. The message's recipient is the sender of the original message. Finally, voice mail recording interacts with the CT server to store the voice mail in the mail store.
• Forward a Message: When users choose to forward a message through the telephone user interface, the voice mail retreival process routes the call to voice mail recording. This process plays a generic system greeting, the user records and addresses a message, and can choose to edit it. Finally, voice mail recording interacts with the CT server to store the voice mail in the mail store.
• Authenticated User Recording: When users choose to compose a message while they are logged in through the telephone user interface, the retreival process transfers them to recording. This process plays a generic system greeting, the user records and addresses a message, and can choose to edit it. Finally, voice mail recording interacts with the CT server to store the voice mail in the mail store.
• Transfer from Retreival: When users in the retreival process press the star key before logging in, they are routed to the recording process and the call is handled as an Unknown Origin Recording call.

The Voicemail recording process provides a searchable user directory to assist in addressing messages. For unknown origin recording and tansfer from retrieval cases, the caller may search a directory of all users at the site that he called. For all cases except Normal Recording, the caller can choose whether to search a directory of all users at the site he called or to search a global directory of all users in the system. In all cases, a caller can bypass the directory by entering a recipient's telephone number.

If there are any delivery problems while sending a message, the recording process places the message in a file system queue. The recovery process attempts to redeliver the message. This can occur due to network failure or if the mail store database is unavailable.

Voice Mail Retreival Process

The voice mail retreival process enables users to log in, retrieve messages, administer their accounts, reply to and forward messages, and record new messages. This process maintains a pool of worker threads that can each process one call at any time. All calls to this process arrive through the routing process.

The retreival process prompts the caller to enter an extension number and password, and authenticates the caller against a user object in the Oracle Internet Directory server. Upon a successful authentication, this process interacts with the CT server to retrieve voicemail messages and other account information. The voice mail retreival process enables the user to listen to, save, and delete voice mail messages. Users can also set a PIN, and record or administer greetings. Account information for the user is stored in Oracle Internet Directory.

See Also: Using Voicemail & Fax for more information

Transfer Process

The transfer process receives a call when the caller chooses to transfer to an operator during an interaction with the voice mail recording or retreival processes. The transfer process looks up the operator extension in the user's group profile, and if none exists, it looks up the default extension defined in the process properties. The caller is then transferred out of the voice mail system to the extension. If this call is not answered, it will be redirected to the voice mail system.

Fax Receiving Process

The fax receiving process receives fax messages. This process maintains a pool of worker threads can each process one call at any time. All calls arrive through the voice mail recording process when a fax calling tone is detected. This process receives a fax message and then delivers it to the e-mail server mail store by communicating with the CT server. This occurs after the call has been routed to the voice mail system. Users answering a fax call on the extension will hear a fax tone.

Recovery Process

The recovery process attempts to redeliver messages if the voice mail recording or fax receiving process experiences errors communicating with the mail store. This process wakes periodically and attempts to send any messages found in the file system queue. Once the recovery process successfully sends a message, the message is removed from the queue.

Process Manager Process

Note: The process manager process is not managed by the Oracle Voicemail & Fax administration tool.

The process manager process enables remote process startup for all Oracle Voicemail & Fax Windows-based processes. The process manager process registers itself with the Java Remote Method Invocation (RMI) registry and Java RMI activation daemon.

Client programs, such as the Oracle Enterprise Manager JSP pages, invoke a remote method in the process manager process to start up a specific process instance. When this service receives the request, it creates and starts a service in the Windows Registry for the specified process instance. If the service is already installed, it restarts the existing service.

Processes managed by the process manager process are:

• Routing Process
• Voice Mail Recording Process
• Voice Mail Retreival Process
• Transfer Process
• Recovery Process
• Fax Receiving Process
• MWI Service Process

  Note: rmiregistry and the rmid must be running before the process manager process can be started.

AQMWI Process

The AQMWI process retrieves message waiting indicator (MWI) activation or deactivation requests from an advanced queue (AQ), and routes them to an MWI service process through Java Remote Method Invocation (RMI). When a user receives a new voice mail, the mail store inserts a request to activate that user's MWI into an advanced queue. When a user reads his or her last unread voice mail, the mail store inserts a request to deactivate that user's MWI into an advanced queue. The AQMWI process retrieves the request from the advanced queue, looks up the user's telephone number and finds an MWI service process responsible for handling MWI for that telephone number. Finally, the AQMWI Process sends the MWI request to the appropriate MWI service process through Java RMI.

MWI Service Process

The MWI service process activates and deactivates the message waiting indicators for a specific PBX in response to requests received through Java RMI. This process maintains either an SMDI or a CT Media connection with the PBX. Exactly one MWI service process should be running for each PBX with voice mail users. The AQMWI process initiates RMI requests for this process.

Managing Oracle Voicemail & Fax Processes Through Windows Services

The Oracle Voicemail & Fax processes can be managed through Windows services or Oracle Enterprise Manager.

Oracle Voicemail & Fax process instances are registered as Windows services. You can start and stop Oracle Voicemail & Fax process instances using Windows services.

Process instances that have been started through Oracle Enterprise Manager or oesctl have a corresponding service name. The service names are in the following format:

• UMProcessMgrService: Process manager service
• UMFaxRecv_instance number: Fax Receiving Application
• UMMWI_instance number: MWI Service
• UMRecording_instance number: Voicemail Recording Application
• UMRecovery_instance number: Voicemail Recovery Application
• UMRetrieval_instance number: Voicemail Retrieval Application
• UMRouting_instance number: Voicemail Routing Application
• UMTransfer_instance number: Voicemail Transfer Application

Automatic services occur when services start when the machine is started. The Oracle Voicemail & Fax applications answer calls automatically within several minutes of startup time, unless the default settings have been changed. Occasionally, it may be necessary to manually start and stop Oracle Voicemail & Fax processes.

Manually Starting or Stopping an Oracle Voicemail & Fax Process Instance

Perform the following steps to start or stop an Oracle Voicemail & Fax process instance using Windows services:

1. Select Start > Settings > Contol Panel > Services.
2. Scroll down to the services with names that begin with UM.
3. Right click on the service name that you want to start or stop.
4. Select Start or Stop.

Occasionally, a process instance may seem to not be running, even if Windows services indicates that the process instance has been started. If this occurs, it can be due to one of the following reasons:

• The process instance was running, but stopped due to an unexpected error.
• The process instance is running, but is waiting to contact the Oracle Internet Directory server for configuration information. In this case, no log file will be written. The process instance may wait up to a minute after the Oracle Internet Directory server is accessible before it attempts to contact it.
• The process instance is running, but is waiting for the CT server to come to level 5. In this case, a log file will be written under %ORACLE_HOME%\um\log. The process instance may wait up to a minute after the CT server reaches level 5 before it attempts a connection.
• The process instance is initializing and can take several minutes.

  See Also: Chapter 4, "Error Messages" for more information

Managing Oracle Voicemail & Fax Processes Through Oracle Enterpise Manager

This section describes how to create, delete, modify, start, stop, and reinitialize Oracle Voicemail & Fax processes through Oracle Enterprise Manager.

Note: The process manager process is not managed by the Oracle Voicemail & Fax administration tool. The process manager process starts up when automatically when Windows starts up.

Creating an Oracle Voicemail & Fax Process Instance

Using Oracle Enterprise Manager, perform the following steps to create an Oracle Voicemail & Fax process instance:

To create a new Oracle Voicemail & Fax process instance with default parameters:

1. Navigate to the Oracle Voicemail & Fax Service Targets page.
2. Select an Oracle Voicemail & Fax process.
3. Click Create. This creates a new Oracle Voicemail & Fax process instance with default parameters.

To create a new Oracle Voicemail & Fax process instance with the same parameter values as an existing Oracle Voicemail & Fax process instance:

1. Select the instance with the parameters you want to replicate.
2. Click Create Like. This creates a new Oracle Voicemail & Fax process instance with the same parameters as the selected Oracle Voicemail & Fax process instance.

Deleting an Oracle Voicemail & Fax Process Instance

Warning: Deleting an Oracle Voicemail & Fax process may disable some or all telephony processes.

Note: A process must be shut down before it can be deleted.

Using Oracle Enterprise Manager, perform the following steps to delete an Oracle Voicemail & Fax process instance:

1. Navigate to the Oracle Voicemail & Fax Service Targets page.
2. Select an Oracle Voicemail & Fax process.
3. Select the Oracle Voicemail & Fax process instance you want to delete.
4. Click Delete.

Modifying Parameters for a Specific Oracle Voicemail & Fax Instance

Note: Processes must be reinitialized whenever parameters are modified.

Using Oracle Enterprise Manager, perform the following steps to modify parameters for a specific Oracle Voicemail & Fax process instance:

1. Navigate to the Oracle Voicemail & Fax Service Targets page.
2. Select an Oracle Voicemail & Fax process.
3. Select the Oracle Voicemail & Fax instance you want to modify.
4. Modify the parameters you want to change.
5. Click Apply.

Modifying Oracle Voicemail & Fax Process Parameters

Note: Processes must be reinitialized whenever parameters are modified.

Using Oracle Enterprise Manager, perform the following steps to modify Oracle Voicemail & Fax process default parameters:

1. Navigate to the Oracle Voicemail & Fax Service Targets page.
2. Select an Oracle Voicemail & Fax process.
3. Select Change Settings.
4. Modify the parameters you want to change.
5. Click Apply.

Starting, Stopping, or Reinitializing All Oracle Voicemail & Fax Processes

Starting an Oracle Voicemail & Fax process starts all the processes comprising that service type. When an Oracle Voicemail & Fax process is started for the first time, a file is created in the log file directory.

Stopping an Oracle Voicemail & Fax system sends a request to the operating system to shut down all of the Oracle Voicemail & Fax processes.

Note: Administrators may need to stop the Oracle Voicemail & Fax system to perform maintenance, such as upgrading the server hardware or software. It is not possible for the processes to be running these types of upgrades are performed.

Reinitializing an Oracle Voicemail & Fax process informs the operating system to reload its operational settings from the Oracle Internet Directory server. The process does not stop running, which means that users continue to receive uninterrupted service. Whenever na Oracle Voicemail & Fax process parameter is modified, it must be reinitialized to make the changes take effect.

Note: The following functions can only be executed if at least one Oracle Voicemail & Fax instance has been created.

Using Oracle Enterprise Manager, perform the following steps to start, stop, or reinitialize all Oracle Voicemail & Fax processes:

1. Navigate to the Oracle Voicemail & Fax Service Targets page.
2. Select an Oracle Voicemail & Fax process.
3. Click Start, Stop, or Reinitialize.

Starting an Oracle Voicemail & Fax Process Instance

Using Oracle Enterprise Manager, perform the following steps to start an Oracle Voicemail & Fax process instance:

1. Navigate to the Oracle Voicemail & Fax Service Targets page.
2. Select an Oracle Voicemail & Fax process.
3. Select the Oracle Voicemail & Fax process instance you want to start.
4. Click Start.

Stopping an Oracle Voicemail & Fax Process Instance

Using Oracle Enterprise Manager, perform the following steps to stop an Oracle Voicemail & Fax process instance:

1. Navigate to the Oracle Voicemail & Fax Service Targets page.
2. Select an Oracle Voicemail & Fax process.
3. Select the Oracle Voicemail & Fax process instance you want to stop.
4. Click Stop.

Reinitializing a Oracle Voicemail & Fax Process Instance

Note: Processes must be reinitialized whenever parameters are modified.

Using Oracle Enterprise Manager, perform the following steps to reinitialize an Oracle Voicemail & Fax process instance:

1. Navigate to the Oracle Voicemail & Fax Service Targets page.
2. Select an Oracle Voicemail & Fax process.
3. Select the Oracle Voicemail & Fax process instance you want to reinitialize.
4. Click Reinitialize.

Oracle Voicemail & Fax Process Parameters

This section describes the Oracle Voicemail & Fax process parameters.

See Also: Intel CT Media 2.1 Administrator's Guide for Windows 2000 for more information on CT Media and CT server

Routing Process

Log Level

This parameter controls the type of logging performed by the UM process.

Table 2-1 Log Level Acceptable Values

Acceptable Values	Description
INTERNALERROR	Reports only the critical errors
ERROR	Reports all errors
WARNING	Reports all errors and warnings
NOTIFICATION	Reports high level flow of operations within the process
TRACE	Reports all debugging information

Default Value: WARNING

Active Flag

This parameter specifies whether the instance is running.

Acceptable Values: True or False

Default Value: Value is not set until the process is started

Number of Threads per Process

This parameter specifies the number of threads for this routing process within one JVM.

Acceptable Value: A positive integer

Default Value: 4

Root Context for UM

This parameter specifies the distinguished name of the Oracle Voicemail & Fax container in Oracle Internet Directory. This domain name's subtree contains Oracle Voicemail & Fax information.

Acceptable Value: A valid Oracle Internet Directory distinguished name

Default Value: None

Root Context for ES

This parameter specifies the distinguished name of the e-mail server container in Oracle Internet Directory. This domain name's subtree contains e-mail server - specific information.

Acceptable Value: A valid Oracle Internet Directory distinguished name

Default Value: None

Install Context for UM

This parameter specifies UM Install Context, such as, um_system.

Acceptable Value: A valid Oracle Internet Directory distinguished name

Default Value: None

Voice Retrieval Application DN

This parameter specifies the distinguished name for the voice mail retrieval application instance where calls are routed.

Acceptable Value: A valid Oracle Internet Directory Distinguished Name

Default Value: None

Voice Recording Application DN

This parameter specifies the distinguished name entry for the recording application instance to which recording calls are routed.

Acceptable Value: A valid Oracle Internet Directory distinguished name.

Default Value: None

Transfer Application DN

This parameter specifies the distinguished name entry for the transfer application instance the the calls are routed to when transferred to the operator function.

Acceptable Value: A valid Oracle Internet Directory distinguished name.

Default Value: None

Mail Store

The distinguished name in Oracle Internet Directory of the mail store that delivers administrative messages for this process.

Acceptable Value: The distinguished name of a mail store in Oracle Internet Directory

Default Value: Chosen during the voice mail telephony middle tier installation

Maximum Number of Log Files

The maximum number of log files to write for a process. Once the maximum number of log files has been written and all log files are full, the oldest log file is overwritten.

Acceptable Values: Positive integers

Default Value: 10

Maximum Log File Size (Bytes)

The maximum size of each log file, in bytes. Once this size is exceeded, another log file is written.

Acceptable values: Positive integers

Default value: 500000

Telephony Port Map

This parameter is for routing processes that use SMDI connections, the port map specifies, for each telephony port on the system, the telephone extension number of that port. For routing processes that use CT Media connections, the port map is ignored.

Acceptable Values: A semicolon delimited string with elements of the form truncated_device_ID extension. A truncated device ID is the part of a CT Media Line Device name after the last underscore. For example, suppose that a machine has four line devices.

Line device VMSERVER2_D240PCI_T1_pci0_13Trunk1GC1 is connected to extension 44001.

Line device VMSERVER2_D240PCI_T1_pci0_13Trunk1GC2 is connected to extension 44002.

Line device VMSERVER2_D240PCI_T1_pci0_13Trunk1GC3 is connected to extension 44003.

Line device VMSERVER2_D240PCI_T1_pci0_13Trunk1GC4 is connected to extension 44004.

The port map should read: 13Trunk1GC1 44001;13Trunk1GC2 44002;13Trunk1GC3 44003;13Trunk1GC4 44004.

Default Value: None

PBX integration type

This parameter specifies the PBX connection type. If the connection type is CT Media, then this process attempts to set or unset the MWI through CT Media. If the connection type is SMDI, then this process attempts to set or unset the MWI through an SMDI monitor process.

Acceptable Values: SMDI or CT Media

Default Value: None

SMDI Monitor Host Name

This parameter specifies the host name of a machine running the SMDI monitor.

Acceptable Value: A valid host name, such as smdimon.acme.com

Default Value: None

SMDI Monitor Port

This parameter specifies the port number on which the SMDI monitor accepts connections.

Acceptable Value: A valid TCP port number

Default Value: None

SMDI Monitor Timeout Value

This parameter specifies the timeout (in milliseconds) for socket communication with the SMDI monitor.

Acceptable Value: A positive integer

Default Value: None

CT Server Name

This parameter specifies the host name of the machine where the CT server is installed. The name should be in the following format:

hostname:port_number

The port number is 2019.

Acceptable Value: A valid host name

Default Value: None

CT Server Application Profile Name

This parameter specifies the name of the CT server profile that contains application configuration information.

The application profile contains information on the signal processing resources the application requires, declares the application service identifiers (ASIs) the application uses to identify itself to the CT server, and documents the ASIs that the application uses to identify other applications to hand-off calls to.

Acceptable Value: A valid CT server profile name

Default Value: UMMediaServicesProfile

CT Server Group Configuration

This parameter specifies the name of the CT server group configuration that represents a collection of resources.

Acceptable Value: A valid CT server group configuration

Default Value: UMMediaServicesProfile

CT Application Service Name

This parameter specifies the CT server application service identifier (ASI), and is the name the application uses to register itself with the CT server. For call routing purposes, each application is identified by its ASIs, which are defined in the application's associated application profile.

If the newly installed application expects to receive incoming calls from the system call router (SCR) or from other applications, or hand-off calls to other applications, the new application's ASI(s) must be added to the ASI map profile and, optionally, the routing rules profile.

Acceptable Value: A valid CT server application service name

Default Value: UMMediaServicesProfile

CT Media Call Timeout Value

This parameter specifies the time (in seconds) that CT Media waits to configure resources for this application.

Acceptable Value: A string of digits

Default Value: 5000

Voice Mail Recording Process

Maximum Message Recording Duration

This parameter specifies the maximum length of a recorded message in milliseconds.

Acceptable Value: A string of digits

Default Value: 120000

Maximum Silence Duration

This parameter specifies the length of continuous silence in miliseconds which causes message recording to stop.

Acceptable Value: A string of digits

Default Value: 10000

Log Level

This parameter controls the type of logging performed by the UM process.

Table 2-2 Log Level Acceptable Values

Acceptable Values	Description
INTERNALERROR	Reports only the critical errors
ERROR	Reports all errors
WARNING	Reports all errors and warnings
NOTIFICATION	Reports high level flow of operations within the process
TRACE	Reports all debugging information

Default Value: WARNING

Active Flag

This parameter specifies whether the instance is running.

Acceptable Values: True or False

Default Value: None

Number of Threads per Process

This parameter specifies number of threads for this Oracle Voicemail & Fax process within one JVM, such as 4.

Acceptable Value: A positive integer

Default Value: None

Root Context for UM

This parameter specifies the distinguished name of the Oracle Voicemail & Fax container in Oracle Internet Directory. This domain name's subtree contains Oracle Voicemail & Fax specific information.

Acceptable Value: A valid Oracle Internet Directory distinguished name

Default Value: None

Root Context for ES

This parameter specifies the distinguished name of the e-mail server container in Oracle Internet Directory. This domain name's subtree contains e-mail server specific information.

Acceptable Value: A valid Oracle Internet Directory distinguished name

Default Value: None

Install Context for UM

This parameter specifies UM Install Context

Acceptable Value: A valid UM Install Context

Default Value: None

CT Server Name

This parameter specifies the host name of the machine where the CT server is installed. The name should be in the following format:

hostname:port_number

The port number is 2019.

Acceptable Value: A valid host name

Default Value: None

CT Server Application Profile Name

This parameter specifies the name of the CT server profile that contains application configuration information.

The application profile contains information on the signal processing resources the application requires, declares the application service identifiers (ASIs) the application uses to identify itself to the CT server, and documents the ASIs that the application uses to identify other applications to hand-off calls to.

Acceptable Value: A valid CT server profile name

Default Value: UMMediaServicesProfile

CT Server Group Configuration

This parameter specifies the name of the CT server group configuration that represents a collection of resources.

Acceptable Value: A valid CT server group configuration

Default Value: UMMediaServicesProfile

CT Application Service Name

This parameter specifies the CT server application service identifier (ASI), and is the name the application uses to register itself with the CT server. For call routing purposes, each application is identified by its ASIs, which are defined in the application's associated application profile.

If the newly installed application expects to receive incoming calls from the system call router (SCR) or from other applications, or hand-off calls to other applications, the new application's ASI(s) must be added to the ASI map profile and, optionally, the routing rules profile.

Acceptable Value: A valid CT server application service name

Default Value: UMMediaServicesProfile

CT Media Call Timeout Value

This parameter specifies the time (in seconds) that CT Media waits to configure resources for this application.

Acceptable Value: A string of digits

Default Value: 5000

Message Coder Type

This parameter specifies audio coder type for voice mail messages.

Acceptable Value: A valid audio coder type

Default Value: v_Linear8Bit_64k

Greeting Coder Type

This parameter specifies the audio coder type for greetings and recorded names. Valdi audio coder types are defined by the Intel card used.

Acceptable Value: A valid audio coder type

Default Value: v_Linear8Bit_64k

Mail Box Minimum Length

This parameter is used to implement short extensions at a single site. This number specifies the minimum number of digits the user can enter for the application to be able to resolve the user's mailbox number.

Acceptable Value: A positive integer

Default Value: None

Mail Box Maximum Length

This parameter specifies the maximum number of digits permitted for the mailbox number.

Acceptable Value: A positive integer

Default Value: None

International Number Prefix List

This parameter defines a mapping between PBX extension numbers and international telephone numbers. The mapping is a list of submappings separated by semicolons. Each submapping follows the form:

international_prefix PBX_prefix
 

where international_prefix is the sequence of digits that should be appended to a PBX extension number beginning with PBX_prefix. If the prefix list is 1650506;1650607, the extension 60000 is mapped to 16505060000, and 70000 is mapped to 16506070000.

Acceptable Value: A string of digits delimited by a semicolon

Default Value: None

Prefix to be Added to the PBX Number

This parameter specifies the prefix to be added to the phone numbers that are sent to the application through the PBX in order to formulate a phone number in the international format.

Acceptable Value: A string of digits

Default Value: 1

Length of the Number Sent by the PBX

This parameter specifies the number of digits that the PBX sends to the Oracle Voicemail & Fax application.

Acceptable Value: A positive integer

Default Value: 10

Directory Name for Stored Queued Messages

This parameter specifies the directory on the CT server where the undelivered messages are stored for future delivery.

Acceptable Value: A file system directory path, such as ORACLE_HOME\vm1_queue

Default Value: None

Fax Receiving Application DN

This parameter specifies the distinguished name entry for the fax receiving application instance where fax calls are routed.

Acceptable Value: A valid Oracle Internet Directory distinguished name

Default Value: None

Transfer Application DN

This parameter specifies the distinguished name entry for the transfer application instance where calls are routed to when transferring to an operator.

Acceptable Value: A valid Oracle Internet Directory distinguished name

Default Value: None

Full Path Name of UM Log Directory

This parameter specifies the directory under which log files are written.

Acceptable Value: A path name of a file system directory

Default Values:

On UNIX: $ORACLE_HOME/um/log

On Windows: %ORACLE_HOME%\um\log

Site DN To Be Used For Directory Searches

This parameter specifies the DN containing all users within the site that this process serves. When a caller chooses to do a site-specific directory search, the system searches only for users under this DN. If this parameter is unset, all searches are global searches.

Acceptable Value: A valid Oracle Internet Directory distinguished name in the subtree cn=UMContainer,cn=Products,cn=oraclecontext

Default Value: None

Maximum Size of Result Set For Directory Searches

This parameter specifies the maximum number of directory search results with which to present a caller. If a caller performs a directory search with more results, the system prompts him to refine the search criteria.

Acceptable Value: A positive integer

Default Value: 10

Default Domain Name

This optional parameter specifies the e-mail domain name for all of the users on the system. When the LDAP server is down and this parameter is set, the system sends messages to the address international_phone_number@default_domain_name. To enable delivery of messages while LDAP is down, this property must be set, and it can only be set if all users on the system are on the same e-mail domain.

Acceptable Value: A valid e-mail domain

Default Value: None

Mail Store

The distinguished name in Oracle Internet Directory of the mail store that delivers administrative messages for this process.

Acceptable Value: The distinguished name of a mail store in Oracle Internet Directory

Default Value: Chosen during the voice mail telephony middle tier installation

Maximum Number of Log Files

The maximum number of log files to write for a process. Once the maximum number of log files has been written and all log files are full, the oldest log file is overwritten.

Acceptable Values: Positive integers

Default Value: 10

Maximum Log File Size (Bytes)

The maximum size of each log file, in bytes. Once this size is exceeded, another log file is written.

Acceptable values: Positive integers

Default value: 500000

Voice Mail Retreival Process

Maximum Greeting Recording Duration

This parameter specifies the maximum length of a recorded greeting in milliseconds.

Acceptable Value: A string of digits

Default Value: 30000

Maximum Silence Duration

This parameter specifies the length of continuous silence that causes the greeting recording to stop in milliseconds.

Acceptable Value: A string of digits

Default Value: 10000

Log Level

This parameter controls the type of logging performed by the UM process.

Table 2-3 Log Level Acceptable Values

Acceptable Values	Description
INTERNALERROR	Reports only the critical errors
ERROR	Reports all errors
WARNING	Reports all errors and warnings
NOTIFICATION	Reports high level flow of operations within the process
TRACE	Reports all debugging information

Default Value: WARNING

Active Flag

This parameter specifies whether the instance is running.

Acceptable Values: True or False

Default Value: None

Number of Threads per Process

This parameter specifies the number of threads for this Oracle Voicemail & Fax process within one JVM.

Acceptable Value: A positive integer

Default Value: 4

Root Context for UM

This parameter specifies the distinguished name of the Oracle Voicemail & Fax container in Oracle Internet Directory. This domain name's subtree contains Oracle Voicemail & Fax information.

Acceptable Value: A valid Oracle Internet Directory distinguished name

Default Value: None

Root Context for ES

This parameter specifies the distinguished name of the e-mail server container in Oracle Internet Directory. This domain name's subtree contains e-mail server specific information.

Acceptable Value: A valid Oracle Internet Directory distinguished name

Default Value: None

Install Context for UM

This parameter specifies the UM Install Context

Acceptable Value: A valid UM Install Context

Default Value: None

CT Server Name

This parameter specifies the host name of the machine where the CT server is installed. The name should be in the following format:

hostname:port_number

The port number is 2019.

Acceptable Value: A valid host name

Default Value: None

CT Server Application Profile Name

This parameter specifies the name of the CT server profile that contains application configuration information.

The application profile contains information on the signal processing resources the application requires, declares the application service identifiers (ASIs) the application uses to identify itself to the CT server, and documents the ASIs that the application uses to identify other applications to hand-off calls to.

Acceptable Value: A valid CT server profile name

Default Value: UMMediaServicesProfile

CT Server Group Configuration

This parameter specifies the name of the CT server group configuration that represents a collection of resources.

Acceptable Value: A valid CT server group configuration

Default Value: UMMediaServicesProfile

CT Application Service Name

This parameter specifies the CT server application service identifier (ASI), and is the name the application uses to register itself with the CT server. For call routing purposes, each application is identified by its ASIs, which are defined in the application's associated application profile.

If the newly installed application expects to receive incoming calls from the system call router (SCR) or from other applications, or hand-off calls to other applications, the new application's ASI(s) must be added to the ASI map profile and, optionally, the routing rules profile.

Acceptable Value: A valid CT server application service name

Default Value: UMMediaServicesProfile

CT Media Call Timeout Value

This parameter specifies the time (in seconds) CT Media waits to configure resources for this application.

Acceptable Value: A string of digits

Default Value: 5000

Message Coder Type

This parameter specifies audio coder type for voice mail messages.

Acceptable Value: A valid audio coder type

Default Value: v_Linear8Bit_64k

Greeting Coder Type

This parameter specifies the audio coder type for greetings and recorded names.

Acceptable Value: A valid audio coder type

Default Value: v_Linear8Bit_64k

Mail Box Minimum Length

This parameter is used to implement short extensions at a single site. This number specifies the minimum number of digits the user can enter for the application to be able to resolve the user's mailbox number.

Acceptable Value: A positive integer

Default Value: None

Mail Box Maximum Length

This parameter specifies the maximum number of digits permitted for the mailbox number.

Acceptable Value: A positive integer

Default Value: None

International Number Prefix List

This parameter defines a mapping between PBX extension numbers and international telephone numbers. The mapping is a list of submappings separated by semicolons. Each submapping follows the form:

international_prefix PBX_prefix
 

where international_prefix is the sequence of digits that should be appended to a PBX extension number beginning with PBX_prefix. If the prefix list is 1650506;1650607, the extension 60000 is mapped to 16505060000, and 70000 is mapped to 16506070000.

Acceptable Value: A positive integer

Default Value: None

Prefix to Be Added to the PBX Number

This parameter specifies the prefix to be added to the phone numbers that are sent to the application through the PBX in order to formulate a phone number in the international format.

Acceptable Value: A positive integer

Default Value: 1

Length of the Number Sent by the PBX

This parameter specifies the number of digits that the PBX sends.

Acceptable Value: A positive integer

Default Value: 10

Voice Recording Application DN

This parameter specifies the distinguished name entry for the recording application instance to which recording calls are routed.

Acceptable Value: A valid Oracle Internet Directory distinguished name.

Default Value: None

Transfer Application DN

This parameter specifies the distinguished name entry for the transfer application instance the the calls are routed to when transferred to the operator function.

Acceptable Value: A valid Oracle Internet Directory distinguished name.

Default Value: None

Full Path Name of UM Log Directory

This parameter specifies the directory under which log files are written.

Acceptable Value: A pathname of a file system directory.

Default Values:

On UNIX: $ORACLE_HOME/um/log

On Windows: %ORACLE_HOME%\um\log

Mail Store

The distinguished name in Oracle Internet Directory of the mail store that delivers administrative messages for this process.

Acceptable Value: The distinguished name of a mail store in Oracle Internet Directory

Default Value: Chosen during the voice mail telephony middle tier installation

Maximum Number of Log Files

The maximum number of log files to write for a process. Once the maximum number of log files has been written and all log files are full, the oldest log file is overwritten.

Acceptable Values: Positive integers

Default Value: 10

Maximum Log File Size (Bytes)

The maximum size of each log file, in bytes. Once this size is exceeded, another log file is written.

Acceptable values: Positive integers

Default value: 500000

Transfer Process

Log Level

This parameter controls the type of logging performed by the UM process.

Table 2-4 Log Level Acceptable Values

Acceptable Values	Description
INTERNALERROR	Reports only the critical errors
ERROR	Reports all errors
WARNING	Reports all errors and warnings
NOTIFICATION	Reports high level flow of operations within the process
TRACE	Reports all debugging information

Default Value: WARNING

Active Flag

This parameter specifies whether the instance is running.

Acceptable Values: True or False

Default Value: None

Number of Threads per Process

This parameter specifies the number of threads for this Oracle Voicemail & Fax process within one JVM.

Acceptable Value: A positive integer

Default Value: 4

Root Context for UM

This parameter specifies the distinguished name of the Oracle Voicemail & Fax container in Oracle Internet Directory. This domain name's subtree contains Oracle Voicemail & Fax specific information.

Acceptable Value: A valid Oracle Internet Directory distinguished name

Default Value: None

Root Context for ES

This parameter specifies the distinguished name of the e-mail server container in Oracle Internet Directory. This domain name's subtree contains e-mail server specific information.

Acceptable Value: A valid Oracle Internet Directory distinguished name

Default Value: None

Install Context for UM

This parameter specifies UM Install Context

Acceptable Value: A valid UM Install Context

Default Value: None

CT Server Name

This parameter specifies the host name of the machine where the CT server is installed. The name should be in the following format:

hostname:port_number

The port number is 2019.

Acceptable Value: A valid host name

Default Value: None

CT Server Application Profile Name

This parameter specifies the name of the CT server profile that contains application configuration information.

The application profile contains information on the signal processing resources the application requires, declares the application service identifiers (ASIs) the application uses to identify itself to the CT server, and documents the ASIs that the application uses to identify other applications to hand-off calls to.

Acceptable Value: A valid CT server profile name

Default Value: UMMediaServicesProfile

CT Server Group Configuration

This parameter specifies the name of the CT server group configuration that represents a collection of resources.

Acceptable Value: A valid CT server group configuration

Default Value: UMMediaServicesProfile

CT Application Service Name

This parameter specifies the CT server application service identifier (ASI), and is the name the application uses to register itself with the CT server. For call routing purposes, each application is identified by its ASIs, which are defined in the application's associated application profile.

If the newly installed application expects to receive incoming calls from the system call router (SCR) or from other applications, or hand-off calls to other applications, the new application's ASI(s) must be added to the ASI map profile and, optionally, the routing rules profile.

Acceptable Value: A valid CT server application service name

Default Value: UMMediaServicesProfile

CT Media Call Timeout Value

This parameter specifies the time (in seconds) CT Media waits to configure resources for this application.

Acceptable Value: A string of digits

Default Value: 5000

Dialing Number For Transfer

A PBX-dialable working telephone number where calls are routed when a user chooses to be transferred out of voice mail and to an operator. Users can have individual numbers set in their preferences.

Acceptable Value: A string of digits

Default Value: None

Full Path Name of UM Log Directory

This parameter specifies the directory under which log files are written.

Acceptable Value: A pathname of a file system directory.

Default Values:

On UNIX: $ORACLE_HOME/um/log

On Windows: %ORACLE_HOME%\um\log

Mail Store

The distinguished name in Oracle Internet Directory of the mail store that delivers administrative messages for this process.

Acceptable Value: The distinguished name of a mail store in Oracle Internet Directory

Default Value: Chosen during the voice mail telephony middle tier installation

Maximum Number of Log Files

The maximum number of log files to write for a process. Once the maximum number of log files has been written and all log files are full, the oldest log file is overwritten.

Acceptable Values: Positive integers

Default Value: 10

Maximum Log File Size (Bytes)

The maximum size of each log file, in bytes. Once this size is exceeded, another log file is written.

Acceptable values: Positive integers

Default value: 500000

Fax Receiving Process

Log Level

This parameter controls the type of logging performed by the UM process.

Table 2-5 Log Level Acceptable Values

Acceptable Values	Description
INTERNALERROR	Reports only the critical errors
ERROR	Reports all errors
WARNING	Reports all errors and warnings
NOTIFICATION	Reports high level flow of operations within the process
TRACE	Reports all debugging information

Default Value: WARNING

Active Flag

This parameter specifies whether the instance is running.

Acceptable Values: True or False

Default Value: None

Number of Threads per Process

This parameter specifies the number of threads for this Oracle Voicemail & Fax process within one JVM.

Acceptable Value: A positive integer

Default Value: 4

Root Context for UM

This parameter specifies the distinguished name of the Oracle Voicemail & Fax container in Oracle Internet Directory. This domain name's subtree contains Oracle Voicemail & Fax specific information.

Acceptable Value: A valid Oracle Internet Directory distinguished name

Default Value: None

Root Context for ES

This parameter specifies the distinguished name of the e-mail server container in Oracle Internet Directory. This domain name's subtree contains e-mail server specific information.

Acceptable Value: A valid Oracle Internet Directory distinguished name

Default Value: None

Install Context for UM

This parameter specifies UM Install Context

Acceptable Value: A valid UM Install Context

Default Value: None

CT Server Name

This parameter specifies the host name of the machine where the CT server is installed. The name should be in the following format:

hostname:port_number

The port number is 2019.

Acceptable Value: A valid host name

Default Value: None

CT Server Application Profile Name

This parameter specifies the name of the CT server profile that contains application configuration information.

The application profile contains information on the signal processing resources the application requires, declares the application service identifiers (ASIs) the application uses to identify itself to the CT server, and documents the ASIs that the application uses to identify other applications to hand-off calls to.

Acceptable Value: A valid CT server profile name

Default Value: UMMediaServicesProfile

CT Server Group Configuration

This parameter specifies the name of the CT server group configuration that represents a collection of resources.

Acceptable Value: A valid CT server group configuration

Default Value: UMMediaServicesProfile

CT Application Service Name

This parameter specifies the CT server application service identifier (ASI), and is the name the application uses to register itself with the CT server. For call routing purposes, each application is identified by its ASIs, which are defined in the application's associated application profile.

If the newly installed application expects to receive incoming calls from the system call router (SCR) or from other applications, or hand-off calls to other applications, the new application's ASI(s) must be added to the ASI map profile and, optionally, the routing rules profile.

Acceptable Value: A valid CT server application service name

Default Value: UMMediaServicesProfile

CT Media Call Timeout Value

This parameter specifies the time (in seconds) CT Media waits to configure resources for this application.

Acceptable Value: A string of digits

Default Value: 5000

Mail Box Minimum Length

This parameter is used to implement short extensions at a single site. This number specifies the minimum number of digits the user can enter for the application to be able to resolve the user's mailbox number.

Acceptable Value: A positive integer

Default Value: None

Mail Box Maximum Length

This parameter specifies the maximum number of digits permitted for the mailbox number.

Acceptable Value: A positive integer

Default Value: None

International Number Prefix List

This parameter defines a mapping between PBX extension numbers and international telephone numbers. The mapping is a list of submappings separated by semicolons. Each submapping follows the form:

international_prefix PBX_prefix
 

where international_prefix is the sequence of digits that should be appended to a PBX extension number beginning with PBX_prefix. If the prefix list is 1650506;1650607, the extension 60000 is mapped to 16505060000, and 70000 is mapped to 16506070000.

Acceptable Value: A positive integer

Default Value: None

Prefix to Be Added to the PBX Number

This parameter specifies the prefix to be added to the phone numbers that are sent to the application through the PBX in order to formulate a phone number in the international format.

Acceptable Value: A positive integer

Default Value: 1

Length of the Number Sent by the PBX

This parameter specifies the number of digits that the PBX sends.

Acceptable Value: A positive integer

Default Value: 10

Directory Name for Stored Queued Messages

This parameter specifies the directory in which undelivered messages are stored for future delivery.

Acceptable Value: A file system directory path, such as ORACLE_HOME\vm1_queue

Default Value: None

Full Path Name of UM Log Directory

This parameter specifies the directory under which log files are written.

Acceptable Value: A pathname of a file system directory

Default Values:

On UNIX: $ORACLE_HOME/um/log

On Windows: %ORACLE_HOME%\um\log

Default Domain Name

This optional parameter specifies the e-mail domain name for all of the users on the system. When the LDAP server is down and this parameter is set, the system sends messages to the address international_phone_number@default_domain_name. To enable delivery of messages while LDAP is down, this property must be set, and it can only be set if all users on the system are on the same e-mail domain.

Acceptable Value: A valid e-mail domain

Default Value: None

Mail Store

The distinguished name in Oracle Internet Directory of the mail store that delivers administrative messages for this process.

Acceptable Value: The distinguished name of a mail store in Oracle Internet Directory

Default Value: Chosen during the voice mail telephony middle tier installation

Maximum Number of Log Files

The maximum number of log files to write for a process. Once the maximum number of log files has been written and all log files are full, the oldest log file is overwritten.

Acceptable Values: Positive integers

Default Value: 10

Maximum Log File Size (Bytes)

The maximum size of each log file, in bytes. Once this size is exceeded, another log file is written.

Acceptable values: Positive integers

Default value: 500000

Recovery Process

Log Level

This parameter controls the type of logging performed by the UM process.

Table 2-6 Log Level Acceptable Values

Acceptable Values	Description
INTERNALERROR	Reports only the critical errors
ERROR	Reports all errors
WARNING	Reports all errors and warnings
NOTIFICATION	Reports high level flow of operations within the process
TRACE	Reports all debugging information

Default Value: WARNING

Active Flag

This parameter specifies whether the instance is running.

Acceptable Values: True or False

Default Value: None

Number of Threads per Process

This parameter specifies the number of threads for this Oracle Voicemail & Fax process within one JVM.

Acceptable Value: A positive integer

Default Value: 4

Root Context for UM

This parameter specifies the distinguished name of the Oracle Voicemail & Fax container in Oracle Internet Directory. This domain name's subtree contains Oracle Voicemail & Fax specific information.

Acceptable Value: A valid Oracle Internet Directory distinguished name

Default Value: None

Root Context for ES

This parameter specifies the distinguished name of the e-mail server container in Oracle Internet Directory. This domain name's subtree contains e-mail server specific information.

Acceptable Value: A valid Oracle Internet Directory distinguished name

Default Value: None

Install Context for UM

This parameter specifies UM Install Context

Acceptable Value: A valid UM Install Context

Default Value: None

CT Server Name

This parameter specifies the host name of the machine where the CT server is installed. The name should be in the following format:

hostname:port_number

The port number is 2019.

Acceptable Value: A valid host name

Default Value: None

CT Server Application Profile Name

This parameter specifies the name of the CT server profile that contains application configuration information.

The application profile contains information on the signal processing resources the application requires, declares the application service identifiers (ASIs) the application uses to identify itself to the CT server, and documents the ASIs that the application uses to identify other applications to hand-off calls to.

Acceptable Value: A valid CT server profile name

Default Value: UMMediaServicesProfile

CT Server Group Configuration

This parameter specifies the name of the CT server group configuration that represents a collection of resources.

Acceptable Value: A valid CT server group configuration

Default Value: UMMediaServicesProfile

CT Application Service Name

This parameter specifies the CT server application service identifier (ASI), and is the name the application uses to register itself with the CT server. For call routing purposes, each application is identified by its ASIs, which are defined in the application's associated application profile.

If the newly installed application expects to receive incoming calls from the system call router (SCR) or from other applications, or hand-off calls to other applications, the new application's ASI(s) must be added to the ASI map profile and, optionally, the routing rules profile.

Acceptable Value: A valid CT server application service name

Default Value: UMMediaServicesProfile

CT Media Call Timeout Value

This parameter specifies the time (in seconds) CT Media waits to configure resources for this application.

Acceptable Value: A string of digits

Default Value: 5000

Full Path Name of UM Log Directory

This parameter specifies the directory under which log files are written.

Acceptable Value: A path name of a file system directory

Default Values:

On UNIX: $ORACLE_HOME/um/log

On Windows: %ORACLE_HOME%\um\log

List of MailStore DB Service Names

This parameter specifies the list of service names of mail stores to which messages in the recovery queue are sent. Any message in the recovery queue are sent to any mail store in this list. If one mail store is unavailable, messages are recovered through another mail store.

Acceptable Value: A semicolon-delimited list of service names.

Default Value: None.

Queue Monitoring Interval in Seconds

This parameter specifies the amount of time, in seconds, that the recovery process waits between polling the recovery queue.

Acceptable Value: A positive integer.

Default Value: 900

Maximum Number of Log Files

The maximum number of log files to write for a process. Once the maximum number of log files has been written and all log files are full, the oldest log file is overwritten.

Acceptable Values: Positive integers

Default Value: 10

Maximum Log File Size (Bytes)

The maximum size of each log file, in bytes. Once this size is exceeded, another log file is written.

Acceptable values: Positive integers

Default value: 500000

MWI Service Process

Log Level

This parameter controls the type of logging performed by the UM process.

Table 2-7 Log Level Acceptable Values

Acceptable Values	Description
INTERNALERROR	Reports only the critical errors
ERROR	Reports all errors
WARNING	Reports all errors and warnings
NOTIFICATION	Reports high level flow of operations within the process
TRACE	Reports all debugging information

Default Value: WARNING

Set of International Phone Numbers

This parameter specifies the set of phone numbers for which this process controls MWI activation or deactivation.

Acceptable Value: A semicolon-delimited list of international phone number subsets. A phone number subset is a string of digits and asterisk characters which are wildcards. For example, 1650506****; 1650507****.

Default Value: None

RMI URL

This parameter specifies the RMI URL of the MWI service. The MWI service registers as an RMI service with the name service_name. If a port number is specified, the MWI service registers with the RMI registry on that port. Otherwise, it uses the default port. Other processes use the entire RMI URL to connect to this MWI service through RMI.

Acceptable Value: A well-formed URL for RMI.

Default Value: None

PBX integration type

This parameter specifies the PBX connection type. If the connection type is CT Media, then this process attempts to set or unset the MWI through CT Media. If the connection type is SMDI, then this process attempts to set or unset the MWI through an SMDI monitor process.

Acceptable Values: SMDI or CT Media

Default Value: None

SMDI Monitor Host Name

This parameter specifies the host name of a machine running the SMDI monitor.

Acceptable Value: A valid host name, such as smdimon.acme.com

Default Value: None

SMDI Monitor Port

This parameter specifies the port number on which the SMDI monitor accepts connections.

Acceptable Value: A valid TCP port number

Default Value: None

SMDI Monitor Timeout Value

This parameter specifies the timeout (in milliseconds) for socket communication with the SMDI monitor.

Acceptable Value: A positive integer

Default Value: None

MWI Phone Number Suffix Size for SMDI

This parameter indicates the number of digits from the phone number to pass to the SMDI monitor. If the suffix size is five, then the rightmost five digits of phone number are used, and the rest are discarded. If the SMDI MWI prefix is defined, it is prepended to those five digits.

Acceptable Value: A positive integer

Default Value: None

MWI Phone Number Prefix for CT Media

This parameter specifies the string of digits to be prepended to a phone number before it is passed to the CT Media service.

Acceptable Value: A string of digits

Default Value: None

CT Media MWI Provider Name

This parameter specifies the provider string for the CT server that hosts the MWI session service.

Acceptable Value: An IT Media provider string of the following form:

profilename@server:port

Default Value: None

CT Media MWI Service Name

This parameter specifies the name of the MWI session service.

Acceptable Value: A valid name of a CT Media session service

Default Value: MWI service

MWI Phone Number Suffix Size for CT Media

Indicates the number of digits from the phone number to pass to the CT Media service. If the suffix size is 5, the rightmost five digits of the phone number are used, and the rest are discarded. The CT Media MWI prefix, if one is defined, is then prepended to those 5 digits.

Acceptable Value: A positive integer

Default Value: None

MWI Phone Number Prefix for CT Media

A string of digits to be prepended to a phone number before it is passed to the CT Media service.

Acceptable Value: A string of digits

Default Value: None

Full Path Name of UM Log Directory

This parameter specifies the directory under which log files are written.

Acceptable Value: A path name of a file system directory

Default Values:

On UNIX: $ORACLE_HOME/um/log

On Windows: %ORACLE_HOME%\um\log

Mail Store

The distinguished name in Oracle Internet Directory of the mail store that delivers administrative messages for this process.

Acceptable Value: The distinguished name of a mail store in Oracle Internet Directory

Default Value: Chosen during the voice mail telephony middle tier installation

Maximum Number of Log Files

The maximum number of log files to write for a process. Once the maximum number of log files has been written and all log files are full, the oldest log file is overwritten.

Acceptable Values: Positive integers

Default Value: 10

Maximum Log File Size (Bytes)

The maximum size of each log file, in bytes. Once this size is exceeded, another log file is written.

Acceptable values: Positive integers

Default value: 500000

AQMWI Process

Log Level

This parameter controls the type of logging performed by the UM process.

Table 2-8 Log Level Acceptable Values

Acceptable Values	Description
INTERNALERROR	Reports only the critical errors
ERROR	Reports all errors
WARNING	Reports all errors and warnings
NOTIFICATION	Reports high level flow of operations within the process
TRACE	Reports all debugging information

Default Value: WARNING

Number of Threads

This parameter specifies the number of threads that should be listening to the AQ and processing MWI requests.

Acceptable Value: A positive integer

Default Value: 1

AQ name

This parameter specifies the name of the AQ on which MWI requests are made.

Acceptable Value: A valid name for an Oracle Advanced Queue, such as MWI_Q

Default Value: None

User ID for connecting to the database

This parameter specifies the user ID for connecting to the database.

Acceptable Value: A valid Oracle user ID

Default Value: None

Password for connecting to the database

This parameter specifies the password for connecting to the database.

Acceptable Value: A valid Oracle user password

Default Value: None

Install Root Context

This parameter specifies the distinguished name of the container for this installation in Oracle Internet Directory. This domain name's subtree contains information specific to a Oracle Voicemail & Fax installation.

Acceptable Value: A valid Oracle Internet Directory distinguished name

Default Value: None

Root Context for UM

This parameter specifies the distinguished name of the Oracle Voicemail & Fax container in Oracle Internet Directory. This domain name's subtree contains Oracle Voicemail & Fax specific information.

Acceptable Value: A valid Oracle Internet Directory distinguished name

Default Value: None

Root Context for ES

This parameter specifies the distinguished name of the e-mail server container in Oracle Internet Directory. This domain name's subtree contains e-mail server specific information.

Acceptable Value: A valid Oracle Internet Directory distinguished name

Default Value: None

Process Root Context

This parameter specifies the domain name of the e-mail server container in Oracle Internet Directory. The subtree of this domain name contains configuration information for all processes.

Acceptable Value: A valid Oracle Internet Directory distinguished name

Default Value: None

Full Path Name of UM Log Directory

This parameter specifies the directory under which log files are written.

Acceptable Value: A path name of a file system directory

Default Values:

On UNIX: $ORACLE_HOME/um/log

On Windows: %ORACLE_HOME%\um\log

Mail Store

This parameter specifies the distinguished name in Oracle Internet Directory of the mail store for whose users this process handles MWI service. The mail store also delivers administrative messages for this process.

Acceptable Value: The distinguished name of a mail store in Oracle Internet Directory

Default Value: None

Maximum Number of Log Files

The maximum number of log files to write for a process. Once the maximum number of log files has been written and all log files are full, the oldest log file is overwritten.

Acceptable Values: Positive integers

Default Value: 10

Maximum Log File Size (Bytes)

The maximum size of each log file, in bytes. Once this size is exceeded, another log file is written.

Acceptable values: Positive integers

Default value: 500000

Oracle Voicemail & Fax Log Files

The following table specifies the Oracle Voicemail & Fax log file locations:

Table 2-9 Log File Location

Process Name	Windows	Unix
Routing Process	%ORACLE_ HOME%\um\log\RoutingProcess	N/A
Voice Mail Recording Process	%ORACLE_ HOME%\um\log\RecordingProcess	N/A
Voice Mail Retreival Process	%ORACLE_ HOME%\um\log\RetreivalProcess	N/A
Transfer Process	%ORACLE_ HOME%\um\log\TransferProcess	N/A
Fax Receiving Process	%ORACLE_ HOME%\um\log\FaxInProcess	N/A
Recovery Process	%ORACLE_ HOME%\um\log\MsgRecoveryProcess	N/A
MWI Service Process	%ORACLE_ HOME%\um\log\MWIServiceProcess	N/A
AQMWI Process	%ORACLE_ HOME%\um\log\AQMWIProcess	$ORACLE_HOME/um/log/AQMWIProcess