5
Telephony Processes

This chapter discusses the different telephony processes of the Oracle9iAS Unified Messaging system.

This chapter contains the following topics:

• Overview

• Routing Process

• Voice Mail Recording Process

• Voice Mail Retrieval Process

• Attendant Process

• Fax Receiving Process

• Recovery Process

• Process Manager Process

• MWI Service Process

• AQMWI Process

• Wireless Process

• SMS Gateway Process

• WCTP Gateway Process

• Managing Telephony Processes

Overview

The Oracle9iAS Unified Messaging telephony component consists of several processes. Based on the computer telephony server (CT server) architecture from enterprise computer telephony forum (ECTF). Each process interacts with a call, performs the task(s) at hand and transfers the call to different processes. Its object oriented architecture provides the flexibility for scalability and performance.

These are the telephony processes:

• Routing Process: Acts as the routing agent when calls are first recieved by the Oracle9iAS Unified Messaging system.

• Recording Process: Records voice messages and stores them in the Oracle9iAS Unified Messaging mail store

• Fax Receiving Process: Records and stores fax messages in the Oracle9iAS Unified Messaging mail store

• Attendent Process: Manages and transfers calls when a user wishes to speak with an operator.

• Retrieval Process: Interacts with the user and retrieves/renders messages from the Oracle9iAS Unified Messaging mail store.

• Recovery Process: Manages queued voice mail / fax messages if the Oracle9iAS Unified Messaging mail store is unavailable.

• MWI Service Process: Manages the message waiting indicator (MWI) for individual switch implementations.

• AQMWI Process: Manages the message waiting indicator (MWI) requests from the Oracle9iAS Unified Messaging mail server.

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

• Recording: The routing process will pick up the call from the PBX and parses call detail information. Once the Routing process determines that it's a recording call type, the call will be handed off to the Recording process or, if fax tone is detected, the call will be routed to the Fax Receiving process. Recording and Fax Receiving processes will interact with OID and the Oracle9iAS Unified Messaging mail store to store the recorded message. Calls to be transfered to an operator will be handed off to Attendant process.

• Retrieval: The routing process will pick up the call from the PBX and parses call detail information. Once the Routing process determines that it's a retrieval call type, the call will be handed off to the retrieval process. The retreival process interacts with OID and the Oracle9iAS Unified Messaging mail store. For reply/forward, the call will be handed off to the recording process and for transfers, the call will be handed off to the attendant process.

• MWI: When a new voice mail message arrives into a Oracle9iAS Unified Messaging telephony subscriber's inbox, a message waiting indicator (MWI) activation request is generated for the AQMWI process. The AQMWI process interacts with OID, 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 Oracle9iAS Unified Messaging telephony subscriber's inbox, an MWI deactivation request is generated to the AQMWI process and the same procedure is followed. MWI Service process performs activates and deactivates MWI for a specific PBX location.

Routing Process

The Oracle9iAS Unified Messaging routing process is implemented based on CT server (Computer Telephony Server) architecture from ECTF (Enterprise Computer Telephony Forum) organization.

When the voice mail server receives a call from the PBX, the routing process answers the call. This process retrieves call detail information from the PBX. This information indicates whether the current call was a direct call to the voice mail system or a forwarded call from a busy or unanswered extension. The routing process routes forwarded calls to the voice mail recording process and direct calls to voice mail retrieval process. If no call detail information is available, the routing process enables the caller to choose whether to access voice mail recording or voice mail retrieval.

The routing process maintains a pool of worker threads. Each thread can handle one call at any time.

The routing process can retrieve call details through SMDI or CTMEDIA.

Voice Mail Recording Process

Oracle9iAS Unified Messaging voice mail recording process is implemented based on CT server architecture from ECTF organization. Process Architecture

The Oracle9iAS Unified Messaging voice mail recording process records and sends voice mail messages. The voice mail recording process maintains a pool of worker threads. Each thread can handle one call at any time. There are four 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 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 routes the call to the voice mail recording process, which prompts the caller for the recipient's telephone number. The latter process plays a generic system greeting. Next, the caller records 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.

• Reply to a Message: When a user chooses to reply through the telephone user interface to a voice mail from another Oracle9iAS Unified Messaging user, the voice mail retrieval process routes the call to voice mail recording. This process plays a generic system greeting, and then 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 a user chooses to forward a message through the telephone user interface, the voice mail retrieval process routes the call to voice mail recording. This process plays a generic system greeting, and then the user records a message, addresses it, and can choose to edit it. Finally, voice mail recording interacts with the CT server to store the voice mail in the mail store.

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 may occur if the mail store database is unavailable.

Voice Mail Retrieval Process

The Oracle9iAS Unified Messaging voice mail retrieval process is implemented based on computer telephony server (CT server) architecture from the Enterprise Computer Telephony Forum (ECTF) organization.

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

The retrieval process prompts the caller to enter an extension number and password, and authenticates him or her 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 retrieval 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: Oracle9iAS Unified Messaging User's Guide for more information

Attendant Process

The Oracle9iAS Unified Messaging attendant process is implemented based on CT server architecture from ECTF organization.

The attendant process receives a call when the caller chooses to transfer to an operator during an interaction with the voice mail recording process or the retrieval process. The attendant process looks in the Oracle Internet Directory server for a system defined operator telephone extension and transfers the call to that extension.

Fax Receiving Process

The Oracle9iAS Unified Messaging fax receiving process is implemented based on the computer telephony server (CT server) architecture from the Enterprise Computer Telephony Forum (ECTF) organization.

The fax receiving process receives fax messages. This process maintains a pool of worker threads each of which can 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.

Recovery Process

The Oracle9iAS Unified Messaging recovery process is implemented based on the computer telephony server (CT server) architecture from the Enterprise Computer Telephony Forum (ECTF) organization.

The recovery process attempts to redeliver messages if the voice mail recording or fax receiving process experience errors when 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 can successfully send a message, the process deliquesce any messages.

Process Manager Process

The Oracle9iAS Unified Messaging process manager process is implemented based on the Java RMI architecture.

The RMI service enables remote process startup for all Windows based processes for Oracle9iAS Unified Messaging. The RMI service registers itself with the RMI registry and RMID activation daemon. Client programs, like the Oracle Enterprise Manager JSP pages invoke a remote method in this RMI service to start up a specific process instance. When this service receives the request, it creates a service in the Windows Registry for the specified process instance and starts it up. If the service is already installed, it restarts the existing service.

Processes managed by this RMI service are:

• Routing Process

• Voice Mail Recording Process

• Voice Mail Retrieval Process

• Attendant Process

• Recovery Process

• Fax Receiving Process

• MWI Service Process

rmiregistry and the rmid must be running before the RMI service can be started.

MWI Service Process

The Oracle9iAS Unified Messaging message waiting indicator (MWI) service process is implemented based on the Java Remote Method Invocation (RMI) architecture.

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

AQMWI Process

The Oracle9iAS Unified Messaging AQMWI process is implemented based on the Java RMI architecture.

The AQ MWI 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 into an AQ a request to activate that user's MWI. When a user reads his or her last unread voice mail, the mail store inserts into an AQ a request to deactivate that user's MWI. The AQMWI Process retrieves the request from the AQ, looks up the user's telephone number and finds an MWI service process responsible for handling MWI for that telephone number. Finally, the AQ MWI Process sends the MWI request to that MWI service process through Java RMI.

Wireless Process

The Oracle9iAS Unified Messaging wireless process is implemented using the Oracle AQ architecture.

The wireless process is responsible for delivering wireless messages originating from a web client or a notification server, and sending a wireless notification to a given device address. The components insert messages into the wireless in-queue to be processed by the wireless server.

The wireless messages originating from notification servers and Web clients are processed differently from messages originating from a device directed to another device. Messages originating from notification server and Web clients contain the the following parameters:

• From address

• To address

• Text of the message

• Device name

With these parameters, the wireless process dequeues and prepares the message according to the device protocol specifications.

Messages originating from a device directed to another device contain the following parameters:

• From address: device number from which this message originated.

• To address: gateway address defined for each device type, using which, this message can be received by the gateway process listening on a given port.

• Text of the message: contains the actual address that this message be delivered to along with the message body to be sent and the device type to be used.

• Device name: gateway to indicate that this message originated from a device.

Using these parameters, the wireless process parses the message text to find out the destination and device type according to the device protocol specifications. The wireless process dequeues each message from the in-queue, resolves the destination address, and prepares it according to the device chosen. Depending upon the device protocol specifications, this process may send multiple messages for a single message body.

Once processed, the wireless process inserts this message into the out-queue, where the gateway processes dequeue the message. Depending on the type of device, messages are sent to the destination by connecting to the gateway servers.

SMS Gateway Process

The Oracle9iAS Unified Messaging SMS gateway process is implemented using the Oracle AQ architecture.

The SMS gateway process sends and receives wireless messages connecting to the gateway server. The process dequeues the prepared messages from the wireless server out-queue and routes them to the SMS - Center (SMSC) gateway servers. Once a message is received by the gateway server, a response is sent to the gateway process. The delivery of messages between server and the device is outside the scope of the Oracle9iAS Unified Messaging wireless system.

The SMS gateway process listens on the wireless server out-queue. This process dequeues wireless messages whose gateway type matches with its own gateway type and delivers them to the SMSC. The following SMS gateway processes are implemented in this release:

• SMSNokia

• SMSCMG

• SMSUnisys

These gateway processes are capable of two-way messaging and can receive wireless messages originating from a device into the Oracle9iAS Unified Messaging system, that are routed to another wireless address or an e-mail address.

WCTP Gateway Process

The wireless communication transfer protocol (WCTP) transfers information content between the wireline and wireless devices. The information is transferred in blocks using an XML format. Any protocol which is capable of transferring the data in blocks can be used to send the message. Over the internet, HTTP protocol is used to send these messages. The 1.1 version of this protocol supports one-way communication to the device.

Oracle9iAS Unified Messaging WCTP gateway process dequeues wireless messages with the gateway type orclmailwctp, prepares a XML document with the from, to, message text, and the time stamp of the message. Once the XML document is prepared, the process connects to the gateway server through HTTP on a given URL connection, to send the message. As a result, this gateway process receives a response from the server. Status 200 from the server indicates that the message has been received successfully by the HTTP server. Any other status code indicates an error. A proxy server host and port are defined in this process when implemented behind a firewall.

Managing Telephony Processes

This section describes how to start, stop, reinitialize, and modify telephony processes.

Note: The process manager process is not managed by the Oracle9iAS Unified Messaging administration tool

Starting, Stopping, or Reinitializing All Telephony Processes

Note: The following functions can only be executed if there is at least one instance has been created.

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

1. Navigate to the Oracle9iAS Unified Messaging Service Targets page.

2. Select a telephony process.

3. Click Start, Stop, or Reinitialize.

Creating a Telephony Process Instance

Using Oracle Enterprise Manager, perform the following steps to create a telephony process instance:

To create a new telephony process instance with default parameters:

1. Navigate to the Oracle9iAS Unified Messaging Service Targets page.

2. Select a telephony process.

3. Click Create. This creates a new telephony process instance with default parameters.

To create a new telephony process instance with the same parameter values as an existing telephony process instance:

1. Select the instance with the parameters you want to replicate.

2. Click Create Like. This creates a new telephony process instance with the same parameters as the selected telephony process instance.

Deleting a Telephony Process Instance

Warning: Deleting a telephony 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 a telephony process instance:

1. Navigate to the Oracle9iAS Unified Messaging Service Targets page.

2. Select a telephony process.

3. Select the telephony process instance you want to delete.

4. Click Delete.

Starting a Telephony Process Instance

Using Oracle Enterprise Manager, perform the following steps to start a telephony process instance:

1. Navigate to the Oracle9iAS Unified Messaging Service Targets page.

2. Select a telephony process.

3. Select the telephony process instance you want to start.

4. Click Start.

Stopping a Telephony Process Instance

Using Oracle Enterprise Manager, perform the following steps to stop a telephony process instance:

1. Navigate to the Oracle9iAS Unified Messaging Service Targets page.

2. Select a telephony process.

3. Select the telephony process instance you want to stop.

4. Click Stop.

Reinitializing a Telephony Process Instance

Note: Processes must be reinitialized whenever parameters are modified.

Using Oracle Enterprise Manager, perform the following steps to reinitialize a telephony process instance:

1. Navigate to the Oracle9iAS Unified Messaging Service Targets page.

2. Select a telephony process.

3. Select the telephony process instance you want to reinitialize.

4. Click Reinitialize.

Modifying Parameters for a Specific Telephony Instance

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

1. Navigate to the Oracle9iAS Unified Messaging Service Targets page.

2. Select a telephony process.

3. Select the telephony instance you want to modify.

4. Modify the parameters you want to change.

5. Click Apply.

Modifying Telephony Process Parameters

Using Oracle Enterprise Manager, perform the following steps to modify telephony process default parameters:

1. Navigate to the Oracle9iAS Unified Messaging Service Targets page.

2. Select a telephony process.

3. Select Change Settings.

4. Modify the parameters you want to change.

5. Click Apply.

Telephony Process Parameters

The following is a list of telephony process parameters and definitions:

Routing Process

Log Level

This parameter specifies the log level parameter that controls amount of logging performed by the UM process.

Acceptable Values:

• INTERNALERROR

• ERROR

• WARNING

• NOTIFICATION

• TRACE

Default Value: WARNING

Process ID

This parameter specifies the process identification.

Acceptable Values: None

Default Value: None

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 routing process within one JVM.

Acceptable Values: None

Default Value: None

Root Context for UM

This parameter specifies the distinguished name of the Oracle9iAS Unified Messaging container in Oracle Internet Directory. This domain name's subtree contains Oracle9iAS Unified Messaging - specific information.

Acceptable Values: 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 Values: A valid Oracle Internet Directory distinguished name

Default Value: None

Install Context for UM

This parameter specifies UM Install Context. For example, um_system.

Acceptable Values: The name of a UM Install Context

Default Value: None

Voice Mail Recording Process

Maximum Message Recording Duration

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

Acceptable Values: A string of digits

Default Value: 120000

Maximum Silence Duration

This parameter specifies the amount of continuous silence which causes message recording to stop.

Acceptable Values: A string of digits

Default Value: 10000

Log Level

This parameter specifies the log level parameter that controls amount of logging performed by the Oracle9iAS Unified Messaging process.

Acceptable Values:

• INTERNALERROR

• ERROR

• WARNING

• NOTIFICATION

• TRACE

Default Value: WARNING

Process ID

This parameter specifies the process identification.

Acceptable Values: None

Default Value: None

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 Oracle9iAS Unified Messaging process within one JVM.

Acceptable Values: A positive integer

Default Value: None

Root Context for UM

This parameter specifies the distinguished name of the Oracle9iAS Unified Messaging container in Oracle Internet Directory. This domain name's subtree contains Oracle9iAS Unified Messaging specific information.

Acceptable Values: 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 Values: A valid Oracle Internet Directory distinguished name

Default Value: None

Install Context for UM

This parameter specifies UM Install Context

Acceptable Values: 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.

Acceptable Values: 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.

Acceptable Values: A valid CT server profile name

Default Value: None

CT Server Group Configuration

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

Acceptable Values: A valid CT server group configuration

Default Value: None

CT Application Service Name

This parameter specifies the name of CT application service name which is a unit of CTMEDIA functionality that corresponds to a Windows NT service offering OS functionality.

Acceptable Values: A valid CT server application service name

Default Value: None

CTMEDIA Call Timeout Value

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

Acceptable Values: A string of digits

Default Value: None

Message Coder Type

This parameter specifies audio coder type for voice mail messages.

Acceptable Values: 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 Values: A valid audio coder type

Default Value: v_Linear8Bit_64k

Mail Box Minimum Length

This number specifies the minimum number of digits that can be entered by the user for the application to be able to resolve the user's mailbox number.

Acceptable Values: A positive integer

Default Value: None

Mail Box Maximum Length

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

Acceptable Values: 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 list of submappings separated by semicolons. Each submapping follows the form <international prefix>; <PBX prefix>.

Where <international prefix> is a sequence of digits and <PBX prefix> is the digit sequence to prepend to a PBX extension number beginning with <PBX prefix>. For example, if the prefix list is 1650506 and 1650607, the extension 60000 is mapped to the international number 16505060000, and 70000 is mapped to the international number 165050670000.

Acceptable Values: A string of digits delimited by a semicolon

Default Value: None

Prefix to be Added to the PBX Number

This parameter specifies the prefix that needs 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 Values: A string of digits

Default Value: None

Length of the Number Sent by the PBX

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

Acceptable Values: A positive integer

Default Value: None

Directory Name for Stored Queued Messages

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

Acceptable Values: A full file system directory path

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 Values: A valid Oracle Internet Directory distinguished name

Default Value: None

Attendant Application DN

This parameter specifies the distinguished nameentry for the attendant application instance where the calls are routed to when transferred to operator function.

Acceptable Values: A valid Oracle Internet Directory distinguished name

Default Value: None

Voice Mail Retrieval Process

Maximum Greeting Recording Duration

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

Acceptable Values: A string of digits

Default Value: 30000

Maximum Silence Duration

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

Acceptable Values: A string of digits

Default Value: 10000

Log Level

This parameter specifies the log level parameter that controls amount of logging performed by the Oracle9iAS Unified Messaging process.

Acceptable Values:

• INTERNALERROR

• ERROR

• WARNING

• NOTIFICATION

• TRACE

Default Value: WARNING

Process ID

This parameter specifies the process identification.

Acceptable Values: None

Default Value: None

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 Oracle9iAS Unified Messaging process within one JVM.

Acceptable Values: A positive integer

Default Value: None

Root Context for UM

This parameter specifies the distinguished name of the Oracle9iAS Unified Messaging container in Oracle Internet Directory. This domain name's subtree contains Oracle9iAS Unified Messaging specific information.

Acceptable Values: 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 Values: A valid Oracle Internet Directory distinguished name

Default Value: None

Install Context for UM

This parameter specifies UM Install Context

Acceptable Values: 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.

Acceptable Values: 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.

Acceptable Values: A valid CT server profile name

Default Value: None

CT Server Group Configuration

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

Acceptable Values: A valid CT server group configuration

Default Value: None

CT Application Service Name

This parameter specifies the name of CT application service name which is a unit of CTMEDIA functionality that corresponds to a Windows NT service offering OS functionality.

Acceptable Values: A valid CT server application service name

Default Value: None

CTMEDIA Call Timeout Value

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

Acceptable Values: A string of digits

Default Value: None

Message Coder Type

This parameter specifies audio coder type for voice mail messages.

Acceptable Values: 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 Values: A valid audio coder type

Default Value: v_Linear8Bit_64k

Mail Box Minimum Length

This number specifies the minimum number of digits that can be entered by the user for the application to be able to resolve the user's mailbox number.

Acceptable Values: A positive integer

Default Value: None

Mail Box Maximum Length

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

Acceptable Values: A positive integer

Default Value: None

Maximum Allowed Digits in Pin Number

This parameter specifies the maximum number of digits allowed for the PIN.

Acceptable Values: A positive integer

Default Value: None

Minimum Allowed Digits in Pin Number

This parameter specifies the minimum number of digits allowed for the PIN. If the PIN entered by the user does not fall within the minimum and maximum range, it is rejected.

Acceptable Values: 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 list of submappings separated by semicolons. Each submapping follows the form <international prefix>; <PBX prefix>.

Where <international prefix> is a sequence of digits and <PBX prefix> is the digit sequence to prepend to a PBX extension number beginning with <PBX prefix>. For example, if the prefix list is 1650506 and 1650607, the extension 60000 is mapped to the international number 16505060000, and 70000 is mapped to the international number 165050670000.

Acceptable Values: A positive integer

Default Value: None

Prefix to Be Added to the PBX Number

This parameter specifies the prefix that needs 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 Values: A positive integer

Default Value: None

Length of the Number Sent by the PBX

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

Acceptable Values: A positive integer

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 Values: A valid Oracle Internet Directory distinguished name.

Default Value: None

Attendant Application DN

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

Acceptable Values: A valid Oracle Internet Directory distinguished name.

Default Value: None

Attendant Process

Log Level

This parameter specifies the log level parameter that controls amount of logging performed by the Oracle9iAS Unified Messaging process.

Acceptable Values:

• INTERNALERROR

• ERROR

• WARNING

• NOTIFICATION

• TRACE

Default Value: WARNING

Process ID

This parameter specifies the process identification.

Acceptable Values: None

Default Value: None

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 Oracle9iAS Unified Messaging process within one JVM.

Acceptable Values: A positive integer

Default Value: None

Root Context for UM

This parameter specifies the distinguished name of the Oracle9iAS Unified Messaging container in Oracle Internet Directory. This domain name's subtree contains Oracle9iAS Unified Messaging specific information.

Acceptable Values: 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 Values: A valid Oracle Internet Directory distinguished name

Default Value: None

Install Context for UM

This parameter specifies UM Install Context

Acceptable Values: 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.

Acceptable Values: 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.

Acceptable Values: A valid CT server profile name

Default Value: None

CT Server Group Configuration

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

Acceptable Values: A valid CT server group configuration

Default Value: None

CT Application Service Name

This parameter specifies the name of CT application service name which is a unit of CTMEDIA functionality that corresponds to a Windows NT service offering OS functionality.

Acceptable Values: A valid CT server application service name

Default Value: None

CTMEDIA Call Timeout Value

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

Acceptable Values: A string of digits

Default Value: None

Dialing Number For Attendant

A working telephone number where the calls are routed to when they are transferred to the operator function.

Acceptable Values: A string of digits

Default Value: None

Fax Receiving Process

Log Level

This parameter specifies the log level parameter that controls amount of logging performed by the Oracle9iAS Unified Messaging process.

Acceptable Values:

• INTERNALERROR

• ERROR

• WARNING

• NOTIFICATION

• TRACE

Default Value: WARNING

Process ID

This parameter specifies the process identification.

Acceptable Values: None

Default Value: None

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 Oracle9iAS Unified Messaging process within one JVM.

Acceptable Values: A positive integer

Default Value: None

Root Context for UM

This parameter specifies the distinguished name of the Oracle9iAS Unified Messaging container in Oracle Internet Directory. This domain name's subtree contains Oracle9iAS Unified Messaging specific information.

Acceptable Values: 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 Values: A valid Oracle Internet Directory distinguished name

Default Value: None

Install Context for UM

This parameter specifies UM Install Context

Acceptable Values: 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.

Acceptable Values: 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.

Acceptable Values: A valid CT server profile name

Default Value: None

CT Server Group Configuration

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

Acceptable Values: A valid CT server group configuration

Default Value: None

CT Application Service Name

This parameter specifies the name of CT application service name which is a unit of CTMEDIA functionality that corresponds to a Windows NT service offering OS functionality.

Acceptable Values: A valid CT server application service name

Default Value: None

CTMEDIA Call Timeout Value

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

Acceptable Values: A string of digits

Default Value: None

Mail Box Minimum Length

This number specifies the minimum number of digits that can be entered by the user for the application to be able to resolve the user's mailbox number.

Acceptable Values: A positive integer

Default Value: None

Mail Box Maximum Length

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

Acceptable Values: 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 list of submappings separated by semicolons. Each submapping follows the form <international prefix>; <PBX prefix>.

Where <international prefix> is a sequence of digits and <PBX prefix> is the digit sequence to prepend to a PBX extension number beginning with <PBX prefix>. For example, if the prefix list is 1650506 and 1650607, the extension 60000 is mapped to the international number 16505060000, and 70000 is mapped to the international number 165050670000.

Acceptable Values: A positive integer

Default Value: None

Prefix to Be Added to the PBX Number

This parameter specifies the prefix that needs 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 Values: A positive integer

Default Value: None

Length of the Number Sent by the PBX

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

Acceptable Values: A positive integer

Default Value: None

Directory Name for Stored Queued Messages

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

Acceptable Values: A file system directory path

Default Value: None

Recovery Process

Log Level

This parameter specifies the log level parameter that controls amount of logging performed by the Oracle9iAS Unified Messaging process.

Acceptable Values:

• INTERNALERROR

• ERROR

• WARNING

• NOTIFICATION

• TRACE

Default Value: WARNING

Process ID

This parameter specifies the process identification.

Acceptable Values: None

Default Value: None

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 Oracle9iAS Unified Messaging process within one JVM.

Acceptable Values: A positive integer

Default Value: None

Root Context for UM

This parameter specifies the distinguished name of the Oracle9iAS Unified Messaging container in Oracle Internet Directory. This domain name's subtree contains Oracle9iAS Unified Messaging specific information.

Acceptable Values: 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 Values: A valid Oracle Internet Directory distinguished name

Default Value: None

Install Context for UM

This parameter specifies UM Install Context

Acceptable Values: 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.

Acceptable Values: 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.

Acceptable Values: A valid CT server profile name

Default Value: None

CT Server Group Configuration

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

Acceptable Values: A valid CT server group configuration

Default Value: None

CT Application Service Name

This parameter specifies the name of CT application service name which is a unit of CTMEDIA functionality that corresponds to a Windows NT service offering OS functionality.

Acceptable Values: A valid CT server application service name

Default Value: None

CTMEDIA Call Timeout Value

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

Acceptable Values: A string of digits

Default Value: None

Process Manager Process

Log Level

This parameter specifies the log level parameter that controls amount of logging performed by the Oracle9iAS Unified Messaging process.

Acceptable Values:

• INTERNALERROR

• ERROR

• WARNING

• NOTIFICATION

• TRACE

Default Value: WARNING

Process ID

This parameter specifies the process identification.

Acceptable Values: None

Default Value: None

Active Flag

This parameter specifies whether the instance is running.

Acceptable Values: True or False

Default Value: None

Root Context for UM

This parameter specifies the distinguished name of the Oracle9iAS Unified Messaging container in Oracle Internet Directory. This domain name's subtree contains Oracle9iAS Unified Messaging specific information.

Acceptable Values: 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 Values: A valid Oracle Internet Directory distinguished name

Default Value: None

JavaHome

Full path name of the Java home directory that is used to locate the java.exe executable.

Acceptable Values: A file system directory path

Default Value: None

System Root

Full path name of the Windows system root directory that is used to located cmd.exe and any other windows system executables.

Acceptable Values: A file system directory path

Default Value: None

ResourceKit Home

This parameter specifies the full path name of the Windows resource kit directory. Is used to locate the srvany.exe, instsrv.exe, sc.exe, and other resource kit executables.

Acceptable Values: A file system directory path

Default Value: None

CTMEDIA Home

Full path name of the CTMEDIA directory that issued to locate the libraries and dlls under CTMEDIA\Shared Files folder.

Acceptable Values: A file system directory path

Default Value: None

MWI Service Process

Log Level

This parameter specifies the log level parameter that controls amount of logging performed by the Oracle9iAS Unified Messaging process.

Acceptable Values:

• INTERNALERROR

• ERROR

• WARNING

• NOTIFICATION

• TRACE

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. The set is the union of all phone number subsets listed under this attribute.

Acceptable Values: 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, 1650506xxxx; 1650507xxxx.

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 Values: A well-formed URL for RMI.

Default Value: None

PBX integration type

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

Acceptable Values: SMDI or CTMEDIA

Default Value: None

SMDI Monitor Host Name

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

Acceptable Values: A valid host name

Default Value: None

SMDI Monitor Port

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

Acceptable Values: 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 Values: A positive integer

Default Value: None

MWI Phone Number Suffix Size for SMDI

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 Values: A positive integer

Default Value: None

MWI Phone Number Prefix for SMDI

A string of digits to be prepended to a phone number (after suffix truncation) before it is passed to the SMDI monitor.

Acceptable Values: A string of digits

Default Value: None

CTMEDIA MWI Provider Name

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

Acceptable Values: An IT Media provider string of the following form <profilename>@<server>:<port>

Default Value: None

CTMEDIA MWI Service Name

This parameter specifies the name of the MWI session service.

Acceptable Values: A valid name of a CTMEDIA session service.

Default Value: MWI service

MWI Phone Number Suffix Size for CTMEDIA

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

Acceptable Values: A positive integer

Default Value: None

MWI Phone Number Prefix for SMDI

A string of digits to be prepended to a phone number (after suffix truncation) before it is passed to the CTMEDIA service.

Acceptable Values: a string of digits

Default Value: None

AQMWI Process

Log Level

This parameter specifies the log level parameter that controls amount of logging performed by the Oracle9iAS Unified Messaging process.

Acceptable Values:

• INTERNALERROR

• ERROR

• WARNING

• NOTIFICATION

• TRACE

Default Value: WARNING

Number of Threads

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

Acceptable Values: a positive integer

Default Value: 1

Port number of AQ DB Listener

This parameter specifies the port number on which the database listens for connections.

Acceptable Values: A valid TCP port number

Default Value: 1521

Connect string for AQ DB

This parameter specifies the connect string for the database which holds the AQ.

Acceptable Values: A valid Oracle connect string

Default Value: None

AQ name

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

Acceptable Values: A valid name for an Oracle Advanced Queue

Default Value: None

User ID for connecting to the database

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

Acceptable Values: 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 Values: A valid oracle user password

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 Oracle9iAS Unified Messaging installation.

Acceptable Values: A valid Oracle Internet Directory distinguished name

Default Value: None

Root Context for UM

This parameter specifies the distinguished name of the Oracle9iAS Unified Messaging container in Oracle Internet Directory. This domain name's subtree contains Oracle9iAS Unified Messaging specific information.

Acceptable Values: 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 Values: 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 Values: A valid Oracle Internet Directory distinguished name

Default Value: None

Wireless Process

Log Level

This parameter specifies the log level parameter that controls amount of logging performed by the Oracle9iAS Unified Messaging process.

Acceptable Values:

• INTERNALERROR

• ERROR

• WARNING

• NOTIFICATION

• TRACE

Default Value: WARNING

Process ID

This parameter specifies the process identification.

Acceptable Values: None

Default Value: None

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 Oracle9iAS Unified Messaging process within one JVM.

Acceptable Values: A positive integer

Default Value: None

Root Context for UM

This parameter specifies the distinguished name of the Oracle9iAS Unified Messaging container in Oracle Internet Directory. This domain name's subtree contains Oracle9iAS Unified Messaging specific information.

Acceptable Values: 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 Values: A valid Oracle Internet Directory distinguished name

Default Value: None

Install Context for UM

This parameter specifies UM Install Context

Acceptable Values: A valid UM Install Context

Default Value: None

Exception Queue

This parameter specifies the name of the exception queue which stores the exception messages.

Acceptable Values: A valid AQ name

Default Value: exqueue

In-Queue Table

This parameter specifies the name of the queue table in which the wireless process inqueue is created.

Acceptable Values: A valid queue table name

Default Value: exqueue

Out-Queue Table

This parameter specifies the name of the queue table in which the wireless process outqueue is created. In case of the same machine hosting both queues, the queuetable is same.

Acceptable Values: A valid queue table name

Default Value: Queue Table

In-Queue Driver

Type of the driver used to connect to the AQ.

Acceptable Values: A valid JDBC driver type

Default Value: thin

Mail Transport Protocol

This parameter specifies the name of the protocol used to send e-mail notifications.

Acceptable Values: A valid protocol name

Default Value: SMTP

SMTP Port

Port number used for the SMTP protocol.

Acceptable Values: A valid SMTP port number

Default Value: None

In-Queue Connect String

This parameter specifies the connect string used for the database hosting the inqueue for wireless process.

Acceptable Values: A valid connect string

Default Value: None

In-Queue Host

Host machine which contains the wireless inqueue.

Acceptable Values: A valid host name

Default Value: None

In-Queue Port

Port to connect to database.

Acceptable Values: A valid port number

Default Value: 1521

In-Queue ID

This parameter specifies the name of the user id used to connect to the queues.

Acceptable Values: A valid database user ID

Default Value: None

Out-Queue Connect String

connect string used to connect to the database hosting the out queue. This is same in case of a machine hosting both in and out queues.

Acceptable Values: A valid connect string

Default Value: None

Out-Queue Host

Host machine which contains the wireless outqueue.

Acceptable Values: A valid host name

Default Value: None

Out-Queue Port

Port to connect to the database. In case of the one machine hosting both queues, (which is quite often), the last 3 parameters above are same as the one for the in queue parameters.

Acceptable Values: None

Default Value: 1521

Process Sleep Duration

Sleep duration for the process.

Acceptable Values: A positive integer

Default Value: 30 seconds

SMTP Host

This parameter specifies the host name on which the SMTP process is running.

Acceptable Values: A valid host name

Default Value: None

Wireless Gateway Type

This is the parameter which defines the type of the gateway/wireless process to choose to send a wireless message. For all the messages which is inserted by other components, the type is "WS," which denotes wireless server, to be processed by wireless server process.

Acceptable Values: A valid wireless gateway type

Default Value: None

Wireless In-Queue

This parameter specifies the name of the queue created to be inqueue for wireless process.

Acceptable Values: A valid queue name

Default Value: None

Wireless Out-Queue

This parameter specifies the name of the queue created to be the outqueue for the wireless process.

Acceptable Values: A valid AQ name

Default Value: None

Password Attribute

Password used to connect to the database.

Acceptable Values: A valid database user password

Default Value: None

Wireless Process DN

This parameter specifies the distinguished name for the wireless process instance.

Acceptable Values: A valid Oracle Internet Directory DN

Default Value: None

Mail Store DN

This parameter specifies the mail store distinguished name for AQ messages.

Acceptable Values: A valid Oracle Internet Directory DN

Default Value: None

SMS Gateway Process

Log Level

This parameter specifies the log level parameter that controls amount of logging performed by the Oracle9iAS Unified Messaging process.

Acceptable Values:

• INTERNALERROR

• ERROR

• WARNING

• NOTIFICATION

• TRACE

Default Value: WARNING

Process ID

This parameter specifies the process identification.

Acceptable Values: None

Default Value: None

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 Oracle9iAS Unified Messaging process within one JVM.

Acceptable Values: A positive integer

Default Value: None

Root Context for UM

This parameter specifies the distinguished name of the Oracle9iAS Unified Messaging container in Oracle Internet Directory. This domain name's subtree contains Oracle9iAS Unified Messaging specific information.

Acceptable Values: 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 Values: A valid Oracle Internet Directory distinguished name

Default Value: None

Install Context for UM

This parameter specifies UM Install Context

Acceptable Values: A valid UM Install Context

Default Value: None

Wireless Gateway Host

Host name to access the gateway.

Acceptable Values: A valid host name

Default Value: None

Wireless Gateway Type

This parameter identifies each gateway process. For example: For SMSNokia, this parameter is defined as orclmailsmsnokia.

Acceptable Values: A valid wireless gateway type

Default Value: None

Wireless In-Queue Value

This parameter defines the in queue from which the gateway process dequeues its wireless messages to be sent out. The out-queue parameter for the wireless server is same as the in-queue parameter for the gateway process.

Acceptable Values: A valid AQ name

Default Value: out-queue

UM In-Queue Host Name

This parameter specifies the name of the machine hosting the gateway process's in queue. In case of a machine hosting both in and out queues, the host name is the same for the In-Queue Host Name and Out-Queue hostname parameter.

Acceptable Values: A valid AQ name

Default Value: None

UM In-Queue Port

This parameter specifies the port to connect to the in queue.

Acceptable Values: A valid port number

Default Value: None

UM In-Queue ID

This parameter specifies the user ID used to connect to the queue.

Acceptable Values: A valid database user name

Default Value: None

Password Attribute

This parameter is used to store the password to connect to the queues.

Acceptable Values: A valid database user password

Default Value: None

UM In-Queue Connect String

This parameter specifies the connect string used to connect to the queues. For this release, both queues are created on the same machine, thus, making many of the connection attributes common for both in and out queues.

Acceptable Values: A valid connect string

Default Value: None

Process Sleep Duration

This parameter specifies the time a process is allowed to sleep between requests in seconds.

Acceptable Values: A positive integer

Default Value: None

Gateway Host

This parameter specifies the name of the machine to which gateway process connects to in order to send out the wireless message machine name.

Acceptable Values: A positive integer

Default Value: None

Gateway Port

This parameter specifies the port through which the gateway process connect to the gateway server to both send and receive wireless messages post to connect to.

Acceptable Values: A valid host name

Default Value: None

Gateway ID

This parameter specifies the user ID to connect to the gateway server.

Acceptable Values: A valid database user ID

Default Value: None

Gateway Password

This parameter specifies the password used to connect to the gateway server.

Acceptable Values: A valid user password

Default Value: None

SMS Gateway Receive Process

This parameter listens on a port to receive wireless messages from SMS gateway server. The following parameters are required for a SMS gateway receive process. Example: SMSNokiaReceiveProcess

Acceptable Values: A valid port number

Default Value: None

Wireless Out-Queue Name

This parameter specifies the queue name to insert the messages into, after receiving from gateway server.

Acceptable Values: A valid AQ name

Default Value: None

UM Out-Queue Host

This parameter specifies the machine name hosting the queues.

Acceptable Values: A valid host name

Default Value: None

UM Out-Queue Port

This parameter specifies the port to connect to the queues in database.

Acceptable Values: A valid port number

Default Value: 1521

UM Out-Queue ID

This parameter specifies the user ID used to connect to the queues.

Acceptable Values: A valid user ID

Default Value: None

UM Out-Queue Connect String

This parameter specifies the connect string used to connect to the queues.

Acceptable Values: A valid connect string

Default Value: None

Password Attribute

This parameter is used to store the password to connect to the queues.

Acceptable Values: A valid database password

Default Value: None

Wireless Gateway Type

This parameter specifies the string which determines the gateway process. Example: orclmailsmsnokia

Acceptable Values: A valid gateway type

Default Value: None

Process Sleep Duration

This parameter specifies the time a process is allowed to sleep between requests.

Acceptable Values: A positive integer

Default Value: None

Gateway Host

This parameter specifies the name of the machine to which gateway process connects to in order to receive messages from the gateway server.

Acceptable Values: A valid host name

Default Value: None

Gateway Port

This parameter specifies the port through which the gateway process connect from the gateway server to receive wireless messages.

Acceptable Values: A valid port number

Default Value: None

Gateway ID

This parameter specifies the user ID to connect to the gateway server.

Acceptable Values: A valid database user ID

Default Value: None

Gateway Password

This parameter specifies the password to connect to the gateway server.

Acceptable Values: A valid user password

Default Value: None

Mail Store DN

This parameter specifies the mail store distinguished name for AQ messages.

Acceptable Values: A valid Oracle Internet Directory DN

Default Value: None

WCTP Gateway Process

Log Level

This parameter specifies the log level parameter that controls amount of logging performed by the Oracle9iAS Unified Messaging process.

Acceptable Values:

• INTERNALERROR

• ERROR

• WARNING

• NOTIFICATION

• TRACE

Default Value: WARNING

Process ID

This parameter specifies the process identification.

Acceptable Values: None

Default Value: None

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 Oracle9iAS Unified Messaging process within one JVM.

Acceptable Values: A positive integer

Default Value: None

Root Context for UM

This parameter specifies the distinguished name of the Oracle9iAS Unified Messaging container in Oracle Internet Directory. This domain name's subtree contains Oracle9iAS Unified Messaging specific information.

Acceptable Values: 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 Values: A valid Oracle Internet Directory distinguished name

Default Value: None

Install Context for UM

This parameter specifies UM Install Context

Acceptable Values: A valid UM Install Context

Default Value: None

Wireless Gateway Type

This parameter identifies each gateway process. For example: For WCTP, this parameter is defined as orclmailwctp.

Acceptable Values: A valid wireless gateway type

Default Value: None

Wireless In-Queue Value

This parameter defines the in queue from which the gateway process dequeues its wireless messages to be sent out. Note that the outqueue parameter for the wireless server is same as the inqueue parameter for the gateway process.

Acceptable Values: A valide queue name

Default Value: outqueue

UM Out-Queue Host

This parameter specifies the machine name hosting the queues.

Acceptable Values: A valid host name

Default Value: None

UM Out-Queue Port

This parameter specifies the port to connect to the queues in database.

Acceptable Values: A valid port number

Default Value: 1521

UM Out-Queue ID

This parameter specifies the user ID used to connect to the queues.

Acceptable Values: A valid user ID

Default Value: None

UM Out-Queue Connect String

This parameter specifies the connect string used to connect to the queues.

Acceptable Values: A valid connect string

Default Value: None

Password Attribute

This parameter is used to store the password to connect to the queues.

Acceptable Values:

Default Value:

UM In-Queue Connect String

This parameter specifies the connect string used to connect to the queues. For this release, both queues are created on the same machine, making many of the connection attributes common for both in and out queues.

Acceptable Values:

Default Value:

Process Sleep Duration

This parameter specifies the time a process is allowed to sleep between requests.

Acceptable Values:

Default Value: 30 seconds

Proxy Host

This parameter specifies the machine name hosting the proxy server.

Acceptable Values:

Default Value:

Proxy Port

Port to connect to the proxy server.

Acceptable Values:

Default Value: 80

Telephony Log Files

The following is a list of telephony log file locations:

Routing Process

On UNIX:

$ORACLE_HOME/um/log/UMMediaApp

On Windows:

%ORACLE_HOME\um\log\UMMediaApp

Voice Mail Recording Process:

On UNIX:

$ORACLE_HOME/um/log/VMrecordingMediaApp

On Windows:

%ORACLE_HOME\um\log\VMrecordingMediaApp

Voice Mail Retrieval Process

On UNIX:

$ORACLE_HOME/um/log/VMretrievalMediaApp

On UNIX:

%ORACLE_HOME\um\log\VMretrievalMediaApp

Attendant Process

On UNIX:

$ORACLE_HOME/um/log/AttendantMediaAPP

On Windows:

%ORACLE_HOME\um\log\AttendantMediaAPP

Fax Receiving Process

On UNIX:

$ORACLE_HOME/um/log/FaxReceivingMediaApp

On Windows:

%ORACLE_HOME\um\log\FaxReceivingMediaApp

Recovery Process

On UNIX:

$ORACLE_HOME/um/log/DBRecovery

On Windows:

%ORACLE_HOME\um\log\DBRecovery

Process Manager Process

On UNIX:

$ORACLE_HOME/um/log/ProcessMgrService

On Windows:

%ORACLE_HOME\um\log\ProcessMgrService

MWI Service Process

On UNIX:

$ORACLE_HOME/um/log/MWIService

On Windows:

%ORACLE_HOME\um\log\MWIService

AQMWI Process

On UNIX:

$ORACLE_HOME/um/log/AQMWIStarter

On Windows:

%ORACLE_HOME\um\log\AQMWIStarter

Wireless Process

On UNIX:

$ORACLE_HOME/um/log/WirelessAppInstance

On Windows:

%ORACLE_HOME\um\log\WirelessAppInstance 

SMS Gateway Process

On UNIX:

$ORACLE_HOME/um/log/SMSNokiaSendProcess
$ORACLE_HOME/um/log/SMSNokiaReceiveProcess

On Windows:

%ORACLE_HOME\um\log\SMSNokiaSendProcess
%ORACLE_HOME\um/log\SMSNokiaReceiveProcess

WCTP Gateway Process

On UNIX:

$ORACLE_HOME/um/log/WCTPSendProcess

On UNIX:

%ORACLE_HOME\um\log\WCTPSendProcess