| Oracle Voicemail & Fax Administrator's Guide Release 2 (9.0.4) Part Number B10722_01 |
|
|
View PDF |
| Oracle Voicemail & Fax Administrator's Guide Release 2 (9.0.4) Part Number B10722_01 |
|
|
View PDF |
This chapter contains component-specific errors. This chapter contains the following topics:
Error messages can appear in any part of Oracle Voicemail & Fax. Users may see them in the end-user interface, and administrators may see them in the administrative tools and process logs.
Sometimes more than one error is displayed. A list of error messages is called an error stack. The bottommost error in the stack is typically the cause of the error.
|
Note: The error stack can contain error messages from other Oracle products that Oracle Voicemail & Fax uses. When these additional errors appear, refer to the documentation for the given product. |
Cause: The Oracle Internet Directory server is not accessible.
Action: Ensure the Oracle Internet Directory server is accessible.
Cause: The Oracle Internet Directory server is not accessible.
Action: Ensure the Oracle Internet Directory server is accessible.
Cause: The Oracle Internet Directory is down or inaccessible.
Action: None. The application automatically retries the connection.
Cause: Oracle Voicemail & Fax is answering calls for users who do not have Oracle Internet Directory entries or who have incorrect Oracle Internet Directory entries.
Action: If the user is a valid user, ensure that the user's VPIM user object has a correct VPIM mail address. If the user should not be on the system, then configure the PBX not to forward that user's calls to Oracle Voicemail & Fax.
Cause: The application is attempting to queue a message and the message queue location is undefined in Oracle Internet Directory.
Action: Set the message queue location in the appropriate process or instance objects in Oracle Internet Directory.
Cause: Error outputting a message to the recovery queue.
Action: Check disk space and permissions on the queue directory.
Cause: The mail store database is down or inaccessible or there is another problem with message sending.
Action: Ensure the recovery application is running. It sends the message when the database is accessible again. Check the database.
Cause: The coder type stored in a user or greeting Oracle Internet Directory object is incorrectly formatted. It may have been altered.
Action: Correct the formatting of the coder type, and ensure that the default coder types are valid ones.
Cause: The default installation localization message description string is poorly formed.
Action: Correct the message localization description string.
Cause: The default installation menu item bindings description string is poorly formed.
Action: Correct the menu item bindings description string.
Cause: The Oracle Internet Directory error occured while looking up the default installation message localization description string or the default installation menu item bindings description string.
Action: Ensure that a default menu object and a default prompts object exist in Oracle Internet Directory as immediate children of the installation container in Oracle Internet Directory. The default attributes of both objects should be set to true.
Cause: The CT server may be down.
Action: Ensure that the CT server is starting up. Once the server starts up, the application recovers.
Cause: The current configuration of the process instance being refreshed is invalid. A setting made since the process instance's last startup is wrong.
Action: Correct the process instances in the Oracle Internet Directory settings.
Cause: IT Media or CT Media API error.
Action: Check disk space, reboot the system, and report the problem if it persists.
Cause: A fax tone was detected for a call for which call details were unavailable.
Action: Ensure call details are available. Also ensure that fax tone settings in CT Media are correct.
Cause: The PBX connection type is missing or unrecognized, or, for SMDI connections, the SMDI monitor host, port, or timeout properties are missing.
Action: Correct all required PBX connection related properties in the appropriate Oracle Internet Directory process or instance object.
Cause: The CT server may be down.
Action: Ensure that the CT server is starting up. Once the server starts up, the application recovers.
Cause: A well-formed XML string has an integer parameter value that cannot be parsed as an integer.
Action: Examine the log files to determine which XML string is causing the problem and correct it.
Cause: A localized message description string is not correctly formed.
Action: Examine the log files to determine which string is not correctly formed and correct it.
Cause: Unexpected error.
Action: Examine the logs to determine which XML string is being parsed, and ensure the XML string is formed correctly.
Cause: Unknown error.
Action: If the problem persists, reboot the system and report the problem.
Cause: Attempting to reinitialize the application after an unknown error failed.
Action: Reboot the system and report the problem.
Cause: The application thread is shutting down due to failed reinitialization after an unknown error.
Action: Reboot the system and report the problem.
Cause: The application has attempted thread-specific cleanup and is shutting down due to failed initialization after an unknown error.
Action: Reboot the system and report the problem.
Cause: Application error condition occured.
Action: Restart the machine, check disk space, and report the problem if it persists.
Cause: The Oracle Internet Directory process or instance settings which are required for process startup are missing.
Action: Make sure that all Oracle Internet Directory properties required for the application are set in the appropriate process or instance objects.
Cause: An unexpected error condition occured with IT Media and CT Media.
Action: Make sure that IT Media is correctly installed.
Cause: Internal application coding error.
Action: Edit the menu item bindings configuration string to disable the menu item whose handler is missing.
Cause: There was a problem releasing the call to the attendant application. The attendant application is not running or not enough threads are running.
Action: Make sure the attendant application is running.
+ requestor.getAttendantAsi()Cause: There was a problem reconfiguring the group for forwarding to the attendant application. The UMMediaServicesProfile could be configured incorrectly.
Action: Check UMMediaServicesProfile.
Cause: There was an unexpected problem performing a resource operation such as playing a message or detecting signals.
Action: Consult CT Media documentation for the meaning of the error code, if one is logged. Make sure that all sound files are installed. Make sure that disk space is available. Restart machine if all else fails.
Cause: There was a problem releasing the call to the recording or retrieval application. The recording or retrieval application is not running or not enough threads are running.
Action: Make sure the recording or retrieval application is running.
Cause: There was a problem reconfiguring the group for forwarding to the recording or retrieval application. The UMMediaServicesProfile may be configured incorrectly.
Action: Check the UMMediaServicesProfile.
Cause: An unexpected error condition occured with IT Media and CT Media.
Action: Make sure that IT Media is correctly installed.
Cause: Message should never occur.
Action: Report the problem.
Cause: The Oracle Internet Directory server is inaccessible.
Action: Ensure the Oracle Internet Directory server is accessible.
Cause: The Oracle Internet Directory server is inaccessible.
Action: Ensure the Oracle Internet Directory server is accessible.
Cause: The Oracle Internet Directory is down or inaccessible.
Action: None. The application automatically retries the connection.
Cause: Oracle Voicemail & Fax is answering calls for users who do not have Oracle Internet Directory entries or who have incorrect Oracle Internet Directory entries.
Action: If the user should be on the system, ensure that the user's VPIM user object has a correct VPIM mail address. If the user should not be on the system, then configure the PBX not to forward that user's calls to Oracle Voicemail & Fax.
Cause: The application is attempting to queue a message and the message queue location is undefined in Oracle Internet Directory.
Action: Set the message queue location in the appropriate process or instance objects in Oracle Internet Directory.
Cause: Error outputting a message to the recovery queue.
Action: Check disk space and permissions on the queue directory.
Cause: The mail store database is down or inaccessible or there is another problem with message sending.
Action: Ensure the recovery application is running. It sends the message when the database is accessible again. Check database.
Cause: The coder type stored in a user or greeting object in Oracle Internet Directory is incorrectly formatted. It may have been altered.
Action: Correct the formatting of the coder type, and ensure that the default coder types are valid ones.
Cause: The default installation localization message description string is poorly formed.
Action: Correct the message localization description string.
Cause: The default installation menu item bindings description string is poorly formed.
Action: Correct the menu item bindings description string.
Cause: There was an Oracle Internet Directory error occured while looking up the default installation message localization description string or the default installation menu item bindings description string.
Action: Ensure that a default menu object and a default prompts object exist in Oracle Internet Directory. The default attributes of both objects should be set to True.
Cause: The CT server may be down.
Action: Ensure that the CT server is starting up. Once the server starts up, the application recovers.
Cause: The current configuration of the process instance being refreshed is invalid. A setting made since the process instance's last startup is wrong.
Action: Correct the Oracle Internet Directory process instance settings.
Cause: IT Media or CT Media API error.
Action: Check disk space, reboot the system, and report the problem if it persists.
Cause: The CT server may be down.
Action: Ensure that the CT server is starting up. Once the server starts up, the application recovers.
Cause: A well-formed XML string has an integer parameter value which cannot be parsed as an integer.
Action: Examine the logs to determine which XML string is causing the problem, and correct it.
Cause: A localized message description string is not formed correctly.
Action: Examine the logs to determine which string is not formed correctly, and correct it.
Cause: Unexpected error.
Action: Examine the logs to determine which XML string is being parsed, and ensure the XML string is well formed.
Cause: The Oracle Internet Directory is down and no default domain is set in the environment.
Action: If the installation encompasses multiple domains, do nothing. If it is a single domain installation, set the default domain parameter in Oracle Internet Directory to be the name of the single domain.
Cause: The user who called in does not have voice mail access.
Action: If the user should have voice mail access, enable the user's voice mail access in Oracle Internet Directory.
Cause: A fax call was received.
Action: None.
Cause: The message which is being replied to or forwarded has a sender whose text name is numeric, but not a phone number of a user in the system. The sender could have been removed from the system or could have an entirely numeric text name defined in Oracle Internet Directory.
Action: None
Cause: The ASI is not set in the fax process instance's Oracle Internet Directory object referenced in this process instance's object.
Action: Ensure the ASI is set in the appropriate fax process or instance object.
Cause: CT Media or IT Media API error.
Action: Check disk space and report the problem if it persists.
Cause: CT Media or IT Media API error.
Action: Check disk space and report the problem if it persists.
Cause: CT Media or IT Media API error, or an additional RTC has been defined in the CT Media application profile.
Action: Check disk space, correct the application if necessary, and report the problem if it persists.
Cause: The user's transfer extension cannot be found in Oracle Internet Directory.
Action: Ensure that the transfer extension is set in Oracle Internet Directory under one of the user's parent group profiles.
Cause: The telephone number field for a VPIM user is not set.
Action: Set the telephone number to the local telephone number of the VPIM user.
Cause: The user's telephone number is too long to be played.
Action: Shorten the user's telephone number. The length should be large enough to accommodate any phone number.
Cause: Unknown error.
Action: If the problem persists, reboot the system and report the problem.
Cause: Attempting to reinitialize the application after an unknown error failed.
Action: Reboot the system and report the problem.
Cause: The application thread is shutting down due to failed reinitialization after an unknown error.
Action: Reboot the system and report the problem.
Cause: The application has attempted thread-specific cleanup and is shutting down due to failed initialization after an unknown error.
Action: Reboot the system and report the problem.
Cause: Application error condition occured.
Action: Restart the machine, check disk space, and report the problem if it persists.
Cause: The Oracle Internet Directory process or instance settings which are required for process startup are missing.
Action: Make sure that all Oracle Internet Directory properties required for the application are set in the appropriate process or instance objects.
Cause: An unexpected error condition occured with IT Media and CT Media.
Action: Make sure that IT Media is correctly installed.
Cause: Internal application coding error.
Action: Edit the menu item bindings configuration string to disable the menu item whose handler is missing.
Cause: There was a problem releasing the call to the attendant application. The attendant application is not running or not enough threads are running.
Action: Make sure the attendant application is running.
Cause: There was a problem reconfiguring the group for hand off to the attendant application. The UMMediaServicesProfile profile is not configured correctly.
Action: Check UMMediaServicesProfile.
Cause: An unexpected error condition occured with IT Media and CT Media.
Action: Make sure that IT Media is correctly installed.
Cause: Message should never occur.
Action: Report the problem.
Cause: There was a problem delegating the call to the fax application. The fax application is not running or not enough threads are running.
Action: Make sure the fax application is running.
Cause: An unknown error condition occured.
Action: Report the problem if it persists.
Cause: CT server corruption.
Action: Check disk space and reboot the CT server.
Cause: The user did not specify any message recipients.
Action: None.
Cause: Unexpected error condition occured or CT server corruption.
Action: Check disk space and reboot the CT server.
Cause: An error communicating with the database, or simultaneous deletion of the message being forwarded or replied to.
Action: Check database connection.
Cause: Unknown error.
Action: If the problem persists, reboot the system and report the problem.
Cause: Attempting to reinitialize the application after an unknown error failed.
Action: Reboot the system and report the problem.
Cause: The application thread is shutting down due to failed reinitialization after an unknown error.
Action: Reboot the system and report the problem.
Cause: The application has attempted thread-specific cleanup and is shutting down due to failed initialization after an unknown error.
Action: Reboot the system and report the problem.
Cause: Application error condition occured.
Action: Restart the machine, check disk space, and report the problem if it persists.
Cause: The Oracle Internet Directory process or instance settings which are required for process startup are missing.
Action: Make sure that all Oracle Internet Directory properties required for the application are set in the appropriate process or instance objects.
Cause: An unexpected error condition occured with IT Media and CT Media.
Action: Make sure that IT Media is correctly installed.
Cause: Internal application coding error.
Action: Edit the menu item bindings configuration string to disable the menu item whose handler is missing.
Cause: There was a problem releasing the call to the attendant application. The attendant application is not running or not enough threads are running.
Action: Make sure the attendant application is running.
Cause: There was a problem reconfiguring the group for hand off to the attendant application. The UMMediaServicesProfile profile could be configured incorrectly.
Action: Check the UMMediaServicesProfile.
Cause: An unexpected error condition occured with IT Media and CT Media.
Action: Make sure that IT Media is correctly installed.
Cause: Message should never occur.
Action: Report the problem.
Cause: An unexpected application condition.
Action: Check disk space, network connectivity, and access privileges.
Cause: Database down, disk space, or other error after a call has disconnected.
Action: Check disk space and see if database is reachable.
Cause: Database down or other error.
Action: Check if database is reachable.
Cause: An error delegating to recording for a reply, forward, or new message composed within retrieval.
Action: Make sure that the recording application is running.
Cause: Database communication problem or disk space problem while setting the unread flag on a message.
Action: Make sure that the database is accessible and that there is sufficient disk space.
Cause: Database communication problem or disk space problem while deleting a message.
Action: Make sure that the database is accessible and that there is sufficient disk space.
Cause: Database communication problem or disk space problem while obtaining message header information.
Action: Make sure that the database is accessible and that there is sufficient disk space.
Cause: A data object in CT Media's container subsystem was externally deleted or there is an internal CT Media error.
Action: Check disk space. Reinstall CT Media if the problem persists.
Cause: Disk space or internal CT Media error.
Action: Check disk space. Reinstall CT Media if the problem persists.
Cause: There was a database communication problem or disk space problem while obtaining message header information.
Action: Make sure that the database is accessible and that there is sufficient disk space.
Cause: There was an error accessing a just-recorded greeting or name. The greeting or name was removed, there is a disk space problem, or there was another CT Media error.
Action: Check disk space. Reboot the server if the problem persists.
Cause: There was an error storing a just recorded greeting or name in Oracle Internet Directory.
Action: Make sure that the Oracle Internet Directory server is accessible.
Cause: The Oracle Internet Directory server is inaccessible.
Action: Ensure the Oracle Internet Directory server is accessible.
Cause: The Oracle Internet Directory server is inaccessible.
Action: Ensure the Oracle Internet Directory server is accessible.
Cause: The Oracle Internet Directory is down or inaccessible.
Action: None. The application automatically retries the connection.
Cause: Oracle Voicemail & Fax is answering calls for users who do not have Oracle Internet Directory entries or who have incorrect Oracle Internet Directory entries.
Action: If the user should be on the system, ensure that the user's VPIM user object has a correct VPIM mail address. If the user should not be on the system, then configure the PBX not to forward that user's calls to Oracle Voicemail & Fax.
Cause: The application is attempting to queue a message and the message queue location is undefined in Oracle Internet Directory.
Action: Set the message queue location in the appropriate process or instance objects in Oracle Internet Directory.
Cause: Error outputting a message to the recovery queue.
Action: Check disk space and permissions on the queue directory.
Cause: The mail store database is down or inaccessible or there is another problem with message sending.
Action: Ensure the recovery application is running. It sends the message when the database is accessible again. Check database.
Cause: The coder type stored in a Oracle Internet Directory user or greeting object is incorrectly formatted. It may have been altered.
Action: Correct the formatting of the coder type, and ensure that the default coder types are valid ones.
Cause: The default installation localization message description string is poorly formed.
Action: Correct the message localization description string.
Cause: The default installation menu item bindings description string is poorly formed.
Action: Correct the menu item bindings description string.
Cause: The Oracle Internet Directory error occured while looking up the default installation message localization description string or the default installation menu item bindings description string exist in Oracle Internet Directory as immediate children of the installation container in Oracle Internet Directory. The default attributes of both objects should be set to true.
Cause: The CT server may be down.
Action: Ensure that the CT server is starting up. Once the server starts up, the application recover.
Cause: The current configuration of the process instance being refreshed is invalid. A setting made since the process instance's last startup is wrong.
Action: Correct the process instance's Oracle Internet Directory settings.
Cause: IT Media or CT Media API error.
Action: Check disk space, reboot the system, and report the problem if it persists.
Cause: The ASI for the transfer application is not defined in the Oracle Internet Directory transfer object to which this process instance's Oracle Internet Directory configuration points.
Action: Define the transfer ASI in the appropriate Oracle Internet Directory object.
Cause: The CT server may be down.
Action: Ensure that the CT server is starting up. Once the server starts up, the application recovers.
Cause: A well-formed XML string has an integer parameter value which cannot be parsed as an integer.
Action: Examine the logs to determine which XML string is causing the problem, and correct it.
Cause: A localized message description string is not formed correctly.
Action: Examine the logs to determine which string is not formed correctly, and correct it.
Cause: Unexpected error.
Action: Examine the logs to determine which XML string is being parsed, and ensure the XML string is well formed.
Cause: An error communicating with Oracle Internet Directory. This error is non-fatal, but may reveal more serious Oracle Internet Directory communication problems.
Action: Try the operation again and see whether the condition recurs. Check if the Oracle Internet Directory server is down.
Cause: An error communicating with Oracle Internet Directory. This error is non-fatal, but may reveal more serious Oracle Internet Directory communication problems.
Action: Try the operation again and see whether the condition recurs. Check if the Oracle Internet Directory server is down.
Cause: Connection lost with Oracle Internet Directory.
Action: None. The application automatically retries the connection at the beginning of every call.
Cause: The user pressed only the pound key when asked to enter a mailbox number.
Action: None.
Cause: Third party bug was triggered and workaround is being attempted.
Action: None
Cause: Third party bug was triggered and workaround is being attempted.
Action: None
Cause: Loss of Oracle Internet Directory connection.
Action: None. The application automatically retries the connection at the beginning of every call.
Cause: Loss of Oracle Internet Directory connection.
Action: None. The application automatically retries the connection at the beginning of every call.
Cause: The user pressed only the pound key when prompted for a password.
Action: None.
Cause: The Oracle Internet Directory error occurred while looking up a user.
Action: Check the user's Oracle Internet Directory settings.
Cause: The owner field of the Oracle Voicemail & Fax user object is not set.
Action: Set the owner field of the Oracle Voicemail & Fax user object to point to a mail user.
Cause: The owner field of the Oracle Voicemail & Fax user object is a DN which does not exist in the Oracle Internet Directory server.
Action: Correct the owner field of the Oracle Voicemail & Fax user object.
Cause: The mail user's orclMailStore attribute is not set.
Action: Set the mail user's orclMailStore attribute.
Cause: The mail user's targetdn attribute is not set or set incorrectly.
Action: Correct the targetdn to point to the mail user's corresponding public user.
Cause: The mail user's orclMailStore attribute is a DN which does not exist on the Oracle Internet Directory server.
Action: Correct the mail user's orclMailStore attribute.
Cause: The mail store orcldbdistinguishedname attribute is not set.
Action: Set the mail store orcldbdistinguishedname attribute.
Cause: The mail store orcldbdistinguishedname attribute is set to a DN which does not exist in the Oracle Internet Directory server.
Action: Correct the mail store object's orcldbdistinguishedname attribute.
Cause: The DBService orcldbglobalname attribute is not set in Oracle Internet Directory.
Action: Set the DBService orcldbglobalname attribute.
Cause: Loss of Oracle Internet Directory connection.
Action: None. The application automatically retries the connection at the beginning of every call.
Cause: Loss of Oracle Internet Directory connection.
Action: None. The application automatically retries the connection at the beginning of every call.
Cause: The VPIM mail user's object does not have the vpimmail ID set. As this attribute is required by the schema, a severe Oracle Internet Directory corruption has occurred.
Action: Contact Oracle Internet Directory server support.
Cause: The VPIM mail user's vpimmail ID was altered during the course of the telephone call. Most likely an Oracle Internet Directory corruption.
Action: Contact Oracle Internet Directory server support.
Cause: Unknown error authenticating user. Database could be down.
Action: Check database status.
Cause: E-mail server is missing the user's account.
Action: Ensure that user's account is properly set up in the e-mail server and Oracle Internet Directory.
Cause: The message for which a reply or forward is being composed has no message ID.
Action: None.
Cause: A failure to find items in the message header of a message to be forwarded or replied.
Action: None.
Cause: Unknown error while changing password.
Action: None.
Cause: The user's transfer extension cannot be found in Oracle Internet Directory.
Action: Ensure that the transfer extension is set in Oracle Internet Directory under one of the Oracle Voicemail & Fax user's parent Group Profiles.
Cause: The user's VPIM user object could not be found. There may have been an Oracle Internet Directory communication error or the owner attribute of the user object may have been incorrectly set.
Action: Ensure that the user's owner object is set to the dn of the mail user / VPIM user. Check that Oracle Internet Directory is available.
Cause: The user's VPIM user object could not be found. There may have been an Oracle Internet Directory communication error or the owner attribute of the user object may have been incorrectly set.
Action: Ensure that the user's owner object is set to the dn of the mail user or VPIM user. Check that Oracle Internet Directory is available.
Cause: Unknown error.
Action: If the problem persists, reboot the system and report the problem.
Cause: Attempting to reinitialize the application after an unknown error failed.
Action: Reboot the system and report the problem.
Cause: The application thread is shutting down due to failed reinitialization after an unknown error.
Action: Reboot the system and report the problem.
Cause: The application has attempted thread-specific cleanup and is shutting down due to failed initialization after an unknown error.
Action: Reboot the system and report the problem.
Cause: Application error condition occured.
Action: Restart the machine, check disk space, and report the problem if it persists.
Cause: The Oracle Internet Directory process or instance settings which are required for process startup are missing.
Action: Make sure that all Oracle Internet Directory properties required for the application are set in the appropriate process or instance objects.
Cause: An unexpected error condition occured with IT Media and CT Media.
Action: Make sure that IT Media is correctly installed.
Cause: Internal application coding error.
Action: Edit the menu item bindings configuration string to disable the menu item whose handler is missing.
Cause: There was a problem releasing the call to the attendant application. The attendant application is not running or not enough threads are running.
Action: Make sure the attendant application is running.
Cause: There was a problem reconfiguring the group for hand off to the attendant application. The UMMediaServicesProfile profile could be configured incorrectly.
Action: Check the UMMediaServicesProfile.
Cause: An unexpected error condition occured with IT Media and CT Media.
Action: Make sure that IT Media is correctly installed.
Cause: An unexpected application condition.
Action: Check disk space, network connectivity, and access privileges.
Cause: Database down, disk space, or other error after a call has disconnected.
Action: Check disk space and see if database is reachable.
Cause: Database down or other error.
Action: Check if database is reachable.
Cause: An error delegating to recording for a reply, forward, or new message composed within retrieval.
Action: Make sure that the recording application is running.
Cause: Database communication problem or disk space problem while deleting a message.
Action: Make sure that the database is accessible and that there is sufficient disk space.
Cause: Database communication problem or disk space problem while obtaining message header information.
Action: Make sure that the database is accessible and that there is sufficient disk space.
Cause: A data object in CT Media's container subsystem was externally deleted or there is an internal CT Media error.
Action: Check disk space. Reinstall CT Media if the problem persists.
Cause: Disk space or internal CT Media error.
Action: Check disk space. Reinstall CT Media if the problem persists.
Cause: There was a database communication problem or disk space problem while obtaining message header information.
Action: Make sure that the database is accessible and that there is sufficient disk space.
Cause: There was an error accessing a just-recorded greeting or name. The greeting or name was removed, there is a disk space problem, or there was another CT Media error.
Action: Check disk space. Reboot the server if the problem persists.
Cause: There was an error storing a just recorded greeting or name in Oracle Internet Directory.
Action: Make sure that the Oracle Internet Directory server is accessible.
Cause: The Oracle Internet Directory server is inaccessible.
Action: Ensure the Oracle Internet Directory server is accessible.
Cause: The Oracle Internet Directory server is inaccessible.
Action: Ensure the Oracle Internet Directory server is accessible.
Cause: Oracle Internet Directory is down or inaccessible.
Action: None. The application automatically retries the connection.
Cause: Oracle Voicemail & Fax is answering calls for users who do not have Oracle Internet Directory entries or who have incorrect Oracle Internet Directory entries.
Action: If the user should be on the system, ensure that the user's VPIM user object has a correct VPIM mail address. If the user should not be on the system, then configure the PBX not to forward that user's calls to Oracle Voicemail & Fax.
Cause: The application is attempting to queue a message and the message queue location is undefined in Oracle Internet Directory.
Action: Set the message queue location in the appropriate process or instance objects in Oracle Internet Directory.
Cause: Error outputting a message to the recovery queue.
Action: Check disk space and permissions on the queue directory.
Cause: The mail store database is down or inaccessible or there is another problem with message sending.
Action: Ensure the recovery application is running. It sends the message when the database is accessible again. Check the database.
Cause: The coder type stored in a user or greeting Oracle Internet Directory object is incorrectly formatted. It may have been altered.
Action: Correct the formatting of the coder type, and ensure that the default coder types are valid ones.
Cause: The default installation localization message description string is poorly formed.
Action: Correct the message localization description string.
Cause: The default installation menu item bindings description string is poorly formed.
Action: Correct the menu item bindings description string
Cause: Oracle Internet Directory error while looking up the default installation message localization description string or the default installation menu item bindings description string.
Action: Ensure that a default menu object and a default prompts object exist in Oracle Internet Directory. The immediate children of the installation container in Oracle Internet Directory. The default attributes of both objects should be set to true.
Cause: The CT server may be down.
Action: Ensure that the CT server is starting up. Once the server starts up, the application recovers.
Cause: The current configuration of the process instance being refreshed is invalid. A setting made since the process instance's last startup is wrong.
Action: Correct the process instance's Oracle Internet Directory settings.
Cause: The CT server may be down.
Action: Ensure that the CT server is starting up. Once the server starts up, the application recovers.
Cause: A well-formed XML string has an integer parameter value which cannot be parsed as an integer.
Action: Examine the logs to determine which XML string is causing the problem, and correct it.
Cause: A localized message description string is not formed correctly.
Action: Examine the logs to determine which string is not formed correctly, and correct it.
Cause: Unexpected error.
Action: Examine the logs to determine which XML string is being parsed, and ensure the XML string is well formed.
Cause: Unknown error.
Action: If the problem persists, reboot the system and report the problem.
Cause: Attempting to reinitialize the application after an unknown error failed.
Action: Reboot the system and report the problem.
Cause: The application thread is shutting down due to failed reinitialization after an unknown error.
Action: Reboot the system and report the problem.
Cause: The application has attempted thread-specific cleanup and is shutting down due to failed initialization after an unknown error.
Action: Reboot the system and report the problem.
Cause: Application error condition occured.
Action: Restart the machine, check disk space, and report the problem if it persists.
Cause: Oracle Internet Directory process or instance settings which are required for process startup are missing.
Action: Make sure that all Oracle Internet Directory properties required for the application are set in the appropriate process or instance objects.
Cause: An unexpected error condition occured with IT Media and CT Media.
Action: Make sure that IT Media is correctly installed.
Cause: An unexpected error condition occured with IT Media and CT Media.
Action: Make sure that IT Media is correctly installed.
Cause: Message should never occur.
Action: Report the problem.
Cause: The Oracle Internet Directory server is inaccessible.
Action: Ensure the Oracle Internet Directory server is accessible.
Cause: The Oracle Internet Directory server is inaccessible.
Action: Ensure the Oracle Internet Directory server is accessible.
Cause: Oracle Internet Directory is down or inaccessible.
Action: None. The application automatically retries the connection.
Cause: Unified Messaging is answering calls for users who do not have Oracle Internet Directory entries or who have incorrect Oracle Internet Directory entries.
Action: If the user should be on the system, ensure that the user's VPIM user object has a correct VPIM mail address. If the user should not be on the system, then configure the PBX not to forward that user calls to Oracle Voicemail & Fax.
Cause: The application is attempting to queue a message and the message queue location is undefined in Oracle Internet Directory.
Action: Set the message queue location in the appropriate process.
Cause: Error outputting a message to the recovery queue.
Action: Check disk space and permissions on the queue directory.
Cause: The mail store database is down or inaccessible or there is another problem with message sending.
Action: Ensure the recovery application is running. It sends the message when the database is accessible again. Check the database.
Cause: The coder type stored in a user or greeting Oracle Internet Directory. The object is incorrectly formatted. It may have been altered.
Action: Correct the formatting of the coder type, and ensure that the default coder types are valid ones.
Cause: The default installation localization message description string is poorly formed.
Action: Correct the message localization description string.
Cause: The default installation menu item bindings description string is not formed correctly.
Action: Correct the menu item bindings description string.
Cause: Oracle Internet Directory error while looking up the default installation message localization description string or the default installation menu item bindings description string.
Action: Ensure that a default menu object and a default prompts object exist in Oracle Internet Directory as immediate children of the installation container in Oracle Internet Directory. The default attributes of both objects should be set to true.
Cause: The CT server may be down.
Action: Ensure that the CT server is starting up. Once the server starts up, the application recovers.
Cause: The current configuration of the process instance being refreshed is invalid. A setting made since the process instance's last startup is wrong.
Action: Correct the Oracle Internet Directory process instance settings.
Cause: IT Media or CT Media API error.
Action: Check disk space, reboot the system, and report the problem if it persists.
Cause: The ASI for the transfer application is not defined in the transfer Oracle Internet Directory objects.
Action: Define the transfer ASI in the appropriate Oracle Internet Directory object.
Cause: The CT server may be down.
Action: Ensure that the CT server is starting up. Once the server starts up, the application recovers.
Cause: A well-formed XML string has an integer parameter value which cannot be parsed as an integer.
Action: Examine the logs to determine which XML string is causing the problem, and correct it.
Cause: A localized message description string is formed incorrectly.
Action: Examine the logs to determine which string is formed incorrectly, and correct it.
Cause: Unexpected error.
Action: Examine the logs to determine which XML string is being parsed, and ensure the XML string is well formed.
Cause: Call detail information is unavailable.
Action: Ensure that the SMDI Monitor, if one exists, is running, and that the PBX integration settings in Oracle Internet Directory are correct.
Cause: Oracle Internet Directory is down and no default domain is set in the environment.
Action: If the installation encompasses multiple domains, do nothing. If it is a single domain installation, set the default domain parameter in Oracle Internet Directory to be the name of the single domain.
Cause: The user to whom a fax is being sent has fax-in access disabled.
Action: If the user should have fax-in access enabled, then enable it.
Cause: CT Media or IT Media API error.
Action: Check disk space and report the problem if it persists.
Cause: Unknown error.
Action: If the problem persists, reboot the system and report the problem.
Cause: Attempting to reinitialize the application after an unknown error failed.
Action: Reboot the system and report the problem.
Cause: The application thread is shutting down due to failed reinitialization after an unknown error.
Action: Reboot the system and report the problem.
Cause: The application has attempted thread-specific cleanup and is shutting down due to failed initialization after an unknown error.
Action: Reboot the system and report the problem.
Cause: Application error condition occured.
Action: Restart the machine, check disk space, and report the problem if it persists.
Cause: Oracle Internet Directory process or instance settings which are required for process startup are missing.
Action: Make sure that all Oracle Internet Directory properties required for the application are set in the appropriate process or instance objects.
Cause: An unexpected error condition occured with IT Media and CT Media.
Action: Make sure that IT Media is correctly installed.
Cause: Internal application coding error.
Action: Edit the menu item bindings configuration string to disable the menu item whose handler is missing.
Cause: There was a problem releasing the call to the attendant application. The attendant application is not running or not enough threads are running.
Action: Make sure the attendant application is running.
Cause: There was a problem reconfiguring the group for hand off to the attendant application. The UMMediaServicesProfile could be configured incorrectly.
Action: Check UMMediaServicesProfile.
Cause: An unexpected error condition occured with IT Media and CT Media.
Action: Make sure that IT Media is correctly installed.
Cause: Message should never occur.
Action: Report the problem.
Cause: An error during fax reception.
Action: Check disk space, and reinstall CT Media if problems persist.
Cause: The user did not specify any message recipients.
Action: None.
Cause: The CT server may be down.
Action: Ensure that the CT server is starting up. Once the server starts up, the application recovers.
Cause: The class location URL is not set in Oracle Internet Directory.
Action: Set the class location in Oracle Internet Directory.
Cause: Insufficient disk space or file system privileges.
Action: Check disk space and privileges.
Cause: The SMDI Monitor or CT Media MWI session service is unavailable.
Action: Verify that Oracle Internet Directory settings of PBX properties are correct. Verify that the SMDI Monitor, if any, is running. The MWIService automatically reestablishes the connection.
Cause: The PBX connection type is missing or unrecognized, or the SMDI Monitor host, port, or timeout properties are missing.
Action: Correct all required PBX connection-related properties in the appropriate process or instance Oracle Internet Directory object.
Cause: The Oracle JDBC classes are not correctly installed.
Action: Reinstall the Oracle JDBC classes.
Cause: The advanced queue for MWI does not exist, or is unavailable.
Action: Ensure the queue is installed and available.
Cause: The database is unavailable or inaccessible.
Action: Ensure the database is running and is accessible.
Cause: An Oracle Internet Directory server connection or authentication error occurred
Action: Ensure that the Oracle Internet Directory server is running. Reset authentication credentials if necessary.
Cause: An unknown error.
Action: None. It automatically reestablishes a connection.
Cause: An error establishing a connection after an unknown error.
Action: None. A reconnection is attempted every 60 seconds.
Cause: The class oracle.AQ.AQOracleDriver cannot be found.
Action: Ensure that Oracle AQ classes are installed.
Cause: A RMI registry could not be located at the host and port number of the RMI URL set in Oracle Internet Directory.
Action: Ensure that an rmiregistry is running at the host and port number of the RMI URL set in Oracle Internet Directory.
Cause: The URL of the MWIService set in Oracle Internet Directory under the MWI service process or instance object is not formed correctly.
Action: Correct the MWIService URL.
Cause: The MWIService is not registered at the expected URL.
Action: Ensure that an MWIService is running at the location set in Oracle Internet Directory under the MWIService process or instance object.
