Oracle Voicemail & Fax Administrator's Guide Release 9.0.3 Part Number B10034-01 |
|
| View PDF |
The Oracle Voicemail & Fax Administrator's Guide is intended for anyone planning, configuring, managing, or monitoring Oracle Voicemail & Fax. It provides an introduction to the components and concepts of Oracle Voicemail & Fax and describes the planning, configuring, and management tasks you will perform.
This preface contains these topics:
The Oracle Voicemail & Fax Administrator's Guide is intended for anyone planning, configuring, managing, or monitoring Oracle Voicemail & Fax. It provides an introduction to the components and concepts of Oracle Voicemail & Fax and describes the planning, configuring, and management tasks you will perform.
This book contains the following chapters:
This chapter contains an overview of the Oracle Voicemail & Fax system and describes its major features.
This chapter contains information on the administration tools and explains how to configure, start up, shut down, and refresh the Oracle Voicemail & Fax system .
This chapter contains information on administering Oracle Voicemail & Fax.
This chapter contains information on the different servers and processes of the Oracle Voicemail & Fax system.
This chapter contains information on Oracle Voicemail & Fax error messages.
This chapter contains information on the Oracle Voicemail & Fax access control lists.
Oracle Voicemail & Fax documentation is available in HTML and PDF.
The following documents are available on the Oracle Collaboration Suite documentation library:
For more information, see these Oracle resources:
In North America, printed documentation is available for sale in the Oracle Store at
http://oraclestore.oracle.com/
Customers in Europe, the Middle East, and Africa (EMEA) can purchase documentation from
http://www.oraclebookshop.com/
Other customers can contact their Oracle representative to purchase printed documentation.
To download free release notes, installation documentation, white papers, or other collateral, please visit the Oracle Technology Network (OTN). You must register online before using OTN; registration is free and can be done at
http://otn.oracle.com/admin/account/membership.html
If you already have a username and password for OTN, then you can go directly to the documentation section of the OTN Web site at
http://otn.oracle.com/docs/index.htm
To access the database documentation search engine directly, please visit
http://tahiti.oracle.com
For more information on Request for Comments (RFCs), please visit
http://www.ietf.org
This section describes the conventions used in the text and code examples of this documentation set. It describes:
We use various conventions in text to help you more quickly identify special terms. The following table describes those conventions and provides examples of their use.
Conventions in Text
Code examples illustrate SQL, PL/SQL, SQL*Plus, or other command-line statements. They are displayed in a monospace (fixed-width) font and separated from normal text as shown in this example:
SELECT username FROM dba_users WHERE username = 'MIGRATE';
The following table describes typographic conventions used in code examples and provides examples of their use.
Our goal is to make Oracle products, services, and supporting documentation accessible, with good usability, to the disabled community. To that end, our documentation includes features that make information available to users of assistive technology. This documentation is available in HTML format, and contains markup to facilitate access by the disabled community. Standards will continue to evolve over time, and Oracle Corporation is actively engaged with other market-leading technology vendors to address technical obstacles so that our documentation can be accessible to all of our customers. For additional information, visit the Oracle Accessibility Program Web site at
http://www.oracle.com/accessibility/
JAWS, a Windows screen reader, may not always correctly read the code examples in this document. The conventions for writing code require that closing braces should appear on an otherwise empty line; however, JAWS may not always read a line of text that consists solely of a bracket or brace.
This documentation may contain links to Web sites of other companies or organizations that Oracle Corporation does not own or control. Oracle Corporation neither evaluates nor makes any representations regarding the accessibility of these Web sites.