|
|
The following pages describe 3.0 and higher style alarms that are processed by the current alarm-handling mechanisms and what can be done to respond to them. Unlike the 2.2 style alarms, these alarms have only a single ID. These alarms occur in relation to standard communication and container services, and contain slightly different information than 2.2 style alarms.
There is a site configuration mismatch between sites, sites are present in site-local configuration but not on remote site
Create the sites on the remote site.
There is a site configuration mismatch between sites, sites are present in remote site configuration but not on local site.
Create the remote sites on the local site.
The application does not exist, or is in state inactive.
Create to application instance if it does not exist. Active the application in it is in state inactive.
The service provider or application could not be resolved.
Make sure that the service provider and application account exists.
The request rate is higher than the rate stated in the Service Level Agreement for the service type.
Notify the service provider or update the SLA.
The quota for the service type stated in the Service Level Agreement is exceeded.
Notify the service provider or update the SLA.
Properties passed in by an application are not allowed.
Notify the service provider of the application behavior.
The value of a parameter passed in by an application is not allowed.
Notify the service provider of the application behavior or update the SLA to allow the parameter value.
The RequestInfo object is empty. Cannot proceed with the request.
An application tried to use a method that is not allowed according to the SLA.
Notify the service provider or update the SLA.
An application tried to use a method that is not allowed according to the SLA.
Notify the service provider or update the SLA.
A service correlator threw an exception when it was invoked.
The RequestFactory threw an exception when it was invoked.
Could not find a global node or service provider node SLA.
The service contract in the SLA for the service provider group or application group has expired.
The service contract for the service type in the SLA for the service provider group or application group has expired.
The service contract for the service type in the SLA for the service provider group or application group could not be found.
A message has been rejected as a result of a subscriber SLA setting of restrict all.
Check to make sure that the SLA setting is correct.
A message has been rejected as a result of reaching a quota or rate limit set in a subscriber SLA.
Check to make sure that the SLA setting is correct.
A network-triggered SMS message has arrived at an NT server that does not have an active bind to the target application. If the OfflineMO attibute has been set to true, the message was placed in a JMS queue to be fetched by an application that does have an active bind. If no server fetches it within the configured time, the message is deleted and this alarm sounds..
There is configuration mismatch between local and remote sites.
Compare the accounts and SLAs for the different sites and synchronize them.
Could not replicate a a configuration update from the master site to a slave site.
Check the connection between the sites.
Internal exception thrown when performing a Corba operation.
Send any log with stack trace to Oracle
Internal exception thrown when performing a Corba operation.
Send any log with stack trace to Oracle
Internal exception thrown when performing a Corba operation.
Send any log with stack trace to Oracle
Internal exception thrown when performing a Corba operation.
Send any log with stack trace to Oracle
Internal exception thrown when performing a Corba operation.
Send any log with stack trace to Oracle
Internal exception thrown when performing a Corba operation.
Send any log with stack trace to Oracle
Internal exception thrown when performing a Corba operation.
Send any log with stack trace to Oracle
Internal exception thrown when performing a Corba operation.
Send any log with stack trace to Oracle
Internal exception thrown when performing a Corba operation.
Send any log with stack trace to Oracle
Internal exception thrown when an MBean does not comply to the MBean specification
Send any log with stack trace to Oracle.
Internal exception thrown when an MBean Object Name is malformed.
Send any log with stack trace to Oracle.
Internal exception thrown when an MBean fails to register.
Send any log with stack trace to Oracle.
Internal exception thrown when an instance of an MBean already exists.
Send any log with stack trace to Oracle.
Internal exception thrown when a requested instance of an MBean does not exist.
Send any log with stack trace to Oracle.
Internal exception thrown when a management error severity fault happens.
Send any log with stack trace to Oracle.
Either the Plug-in Manager rejected an application initiated request towards a plug-in because a policy rule rejected that request. or the Plug-in Manager rejected the registration of the plug-in if the plug-in is not supported.
If the exception says that the plug-in is not supported, make sure that the plug-in JAR has been woven by aspects. Otherwise, check the SLA to make sure it allows the request.
A plugin-in tries to register itself in the plugin-in manager but one with that ID has already been registered.
Contact Oracle with the appropriate log file.
No plugin-in appropriate for this request can be found.
Check that the plugin-in is correctly deployed and running. Also make sure that a route exists to this plugin-in.
The Plugin-in Manager is asked to return a plugin-in corresponding to this ID but none can be found.
Contact Oracle with the appropriate log file.
An internal error occurred in the Plugin-in Manager causing a generic exception thrown from the Plugin-in Manager. The exception message explains the error.
Send any log with stack trace to Oracle
The number of destination addresses for the message exceeded the SMPP maximum (254)
Have the service provider send multi-destination messages in 254 unit groups.
| Note: | This alarm may be triggered by either the SMS communication service or the binary SMS communication service. |
An error occurred when a short message was sent to the SMSC.
Made sure there is no problem with the connectivity between the Oracle Communications Services Gatekeeper and the SMPP SMSC. Check the configuration of the SMSC and the configuration of the SMS SMPP Plug-in. If the problem persists, contact Oracle Support.
| Note: | This alarm may be triggered by either the SMS communication service or the binary SMS communication service. |
The Oracle Communications Services Gatekeeper was unable to notify the application of a network initiated message
Make sure that the network connectivity between the Access Tier of the Oracle Communications Services Gatekeeper and the application is working properly. Make sure that the endpoint URL of the notification is correct.
| Note: | This alarm may be triggered by either the SMS communication service or the binary SMS communication service. |
The Oracle Communications Services Gatekeeper received a network initiated message for which there was no registered notification.
| Note: | This alarm may be triggered by either the SMS communication service or the binary SMS communication service. |
The Oracle Communications Services Gatekeeper was unable to notify the application of a network message delivery status.
Make sure that the network connectivity between the Access Tier of the Oracle Communications Services Gatekeeper and the application is working properly. Make sure that the endpoint URL of the notification is correct.
| Note: | This alarm may be triggered by either the SMS communication service or the binary SMS communication service. |
Unable to create the needed service for calls from the Oracle Communications Services Gatekeeper to the application
Provide logs with exception stack trace to Oracle.
| Note: | This alarm may be triggered by either the SMS communication service or the binary SMS communication service. |
The Oracle Communications Services Gatekeeper SMPP plug-in failed with a heartbeat attempt to the SMSC and will therefore attempt to reestablish the connection between the Oracle Communications Services Gatekeeper SMPP Plug-in and the SMSC
This could indicate a network issue. Check the connectivity between the SMSC and the Oracle Communications Services Gatekeeper SMPP Plug-in.
| Note: | This alarm may be triggered by either the SMS communication service or the binary SMS communication service. |
Some of the multiple destinations to which the message was sent have failed to be delivered. This alarm is sent for each message failure.
Look in the SMSC logs to find why the messages failed.
| Note: | This alarm may be triggered by either the SMS communication service or the binary SMS communication service. |
The Oracle Communications Services Gatekeeper SMS SMPP Plug-in failed to start the transmitter or receiver connection procedure.
Verify that the configuration on the Oracle Communications Services Gatekeeper SMPP Plug-in is correct. Make sure the network layer on the Oracle Communications Services Gatekeeper can access the SMSC. Make sure the SMSC is running properly.
| Note: | This alarm may be triggered by either the SMS communication service or the binary SMS communication service. |
Oracle Communications Services Gatekeeper has detected that segments from this message are missing.
| Note: | This alarm may be triggered by either the SMS communication service or the binary SMS communication service. |
Oracle Communications Services Gatekeeper is unable to bind to the SMSC.
This alarm is triggered periodically until the connection is restored.
The alarm information contains SMSC IP, SMSC port, server name, and module ID.
| Note: | This alarm may be triggered by either the Parlay X 2.1 Short Messaging SMS/SMPP communication service or the Binary SMS/SMPP communication service. |
Check the logs. Make sure the SMSC is online and reachable.
Oracle Communications Services Gatekeeper is able to bind to the SMSC. The alarm information contains the SMSC IP, port, server name, and module ID.
This alarm clears alarm 110616.
| Note: | This alarm may be triggered by either the SMS communication service or the binary SMS communication service. |
Oracle Communications Services Gatekeeper is able to connect to the SMSC.
Check the logs. Make sure the SMSC is online and reachable.
| Note: | This alarm may be triggered by either the SMS communication service or the binary SMS communication service. |
Either there is a client error or the binary content is too large for Oracle Communications Services Gatekeeper to handle.
Verify that the client is working correctly. Check the size of the binary content.
An internal error has occurred while the Presence SIP plug-in was trying to send a notification to the client about the decision on a pending subscription or the status change of the presentity
Provide logs with exception stack trace to Oracle
The Presence SIP plug-in was not able to notify the client about the decision on a pending subscription. No further notification will be attempted.
The client may try to get presentity information by invoking getUserPresence() and startPresenceNotification(): either operation will fail if the subscription was not authorized. Verify the client is running at the endpoint specified in the subscription to receive future notifications for new subscriptions.
An error occurred when the Presence SIP plug-in was trying to notify the client about the status change of the presentity. No further notification will be sent on the current status change.
Verify the client is running at the endpoint specified to receive future notifications.
An error occurred while the Presence SIP plug-in was processing a subscribePresence request.
Verify the following Presence SIP plug-in configurations in the Management Console:
Make sure OCCAS is running and in good condition
An error occurred while the Presence SIP plug-in was processing a getUserPresence request. Possible causes are:
Verify the client is running at the endpoint specified in the subscription; resubmit the current request after the authorization notification has been received
An error occurred while the Presence SIP plug-in was processing a startPresenceNotification request. Possible causes are:
Verify the client is running at the endpoint specified in the subscription; resubmit the current request after the authorization notification has been received.
An error occurred while the Presence SIP plug-in was processing a startPresenceNotification() request. Possible causes are:
Verify the database is running. Try to restart Oracle Communications Services Gatekeeper. Provide logs with exception stack trace to Oracle.
An internal error occurred when the Presence SIP plug-in was started. It will not function properly unless the underlying problems are corrected
Try to restart the Oracle Communications Services Gatekeeper. Provide logs with exception stack trace to Oracle
An OAM operation error has occurred. This is most likely due to storage service errors
Verify the database is running. Try to restart Oracle Communications Services Gatekeeper. Provide logs with exception stack trace to Oracle
The budget service discovered a site configuration mismatch between geo-redundant sites.
Verify that the list of geo-redundant sites in GeoRedundantService and GeoMasterSiteId settings in GeoStorageService is identical on all geo-redundant sites of the Oracle Communications Services Gatekeeper
Duplicate geo-redundancy masters were detected. The situation has been corrected.
Verify network connectivity between geo-redundant sites. This alarm is likely an indication of a previous network split between sites.
Communication with a remote site has failed a configured number of times. The number of failures before this alarm is raised is determined by the remote site reachability alarm threshold setting.
Verify that network connectivity between geo redundant sites is operational and that the remote site is functioning.
A new geo-redundancy master has been elected and activated
Verify that there is network connectivity between geo-redundant sites and that the remote site is operational. This alarm could be an indication of a network split or a crash at the remote site.
The Oracle Communications Services Gatekeeper was unable to reach one of the remote geo-redundant sites.
Verify that there is network connectivity between geo-redundant sites and that the remote site is operational. This alarm could be an indication of a network split or a crash at the remote site.
A mismatch in budget configuration between geo-redundant sites has been detected.
Re-sync the slave site manually using the syncFromGeoMaster operation
The value of the budget is below 20% of the maximum value.
Inform the service provider that the request limit is closing or update the SLA.
An error occurred while the storage service was removing expired entries from the store database table.
Verify that the database is running and provide logs with exception stack trace to Oracle.
An error occurred when the Storage Service was being activated
Verify that the database is running and provide logs with exception stack traces to Oracle.
An error occurred when the Storage Service was being activated.
Verify that the database is running and that there is network connectivity within the cluster. Provide logs with exception stack traces to Oracle.
An error occurred while performing asynchronous writes to the persistent storage. The requested changes may have been lost without the communication service being aware of it.
Verify that the database is running and provide logs with exception stack traces to Oracle.
A generic storage exception was thrown in a communication service
Provide logs with exception stack traces to Oracle.
The result of a query result was possibly truncated due to maximum query result size limit.
Provide logs with exception stack traces to Oracle.
Succeeded in sending a heartbeat to the MLP Server. Plugin-in status has been set to active.
Failed to send a heartbeat to the MLP Server. Plugin-in status has been deactivated.
Check the MLP server to make sure it is available.
The Terminal Location MLP plugin-in failed to start.
Check the log for more information.
The Terminal Location MLP plugin-in failed to stop.
Check the log for more information.
The Terminal Location MLP plugin-in was not activated.
Check the log for more information.
The Terminal Location MLP plugin-in was not deactivated.
Check the log for more information.
The attempt to send a location request failed.
Make sure the MLP server is available. Check the log for more information.
Oracle Communications Services Gatekeeper was unable to notify the application that location notification has ceased.
Make sure the AT layer and the notification URL are available. Check the log for more information.
Oracle Communications Services Gatekeeper was unable to notify the application that a location error has occurred.
Make sure the AT layer and the notification URL are available. Check the log for more information.
Oracle Communications Services Gatekeeper was unable to notify the application that a location notification has been received.
Make sure the AT layer and the notification URL are available. Check the log for more information.
Oracle Communications Services Gatekeeper was unable to send a multimedia message to the network.
Check the log for more information. Common problems: missing/invalid required parameters; configuration problems; storage errors.
Oracle Communications Services Gatekeeper was unable to get delivery status on a multimedia message from the network.
Check the log for more information. Common problems: invalid request identifier; storage errors.
Oracle Communications Services Gatekeeper was unable to send the list of received messages to the application.
Check the log for more information. Common problems: invalid MM7 configuration; storage errors.
Oracle Communications Services Gatekeeper was unable to send a requested received multimedia message - including attachment - to the application.
Check the log for more information. Common problems: no attachment found; storage errors.
Oracle Communications Services Gatekeeper was unable to send an MM7 message to the network.
Check the log for more information. Common problems: MM7 Relay Server not ready or misconfigured.
Oracle Communications Services Gatekeeper was unable to activate the MM7 plug-in.
Check the log for more information. Common problems: Plugin-in not ready; plugin-in ID duplicated.
Oracle Communications Services Gatekeeper was unable to deactivate the MM7 plug-in.
Check the log for more information. Common problems: can’t find the plugin-in with the ID provided.
Oracle Communications Services Gatekeeper was unable to start the MM7 plug-in.
Check the log for more information. Common problems: failed to located WorkContextMap; MBean-related exceptions.
Oracle Communications Services Gatekeeper was unable to stop the MM7 plug-in.
Check the log for more information. Common problem: MBean-related exceptions.
Oracle Communications Services Gatekeeper was unable to notify the application that a message has been received from the network.
Check the log for more information. Common problems: no matching NotificationInfo; storage errors; unsupported address type; application not available.
Oracle Communications Services Gatekeeper was unable to notify the application that a message delivery receipt has been received from the network.
Check the log for more information. Common problems: no matching messageinfo, recipient number not found; application unavailable.
Oracle Communications Services Gatekeeper was unable to contact the application.
Check the availability of the application.
The delivery acknowledgement does not have a recipient number that matches any of the destination addresses of the sent message. Uncommon.
Check the log for more information. Common problem: issue between Oracle Communications Services Gatekeeper and MMSC.
The incoming delivery report did not correlate to a message info. For example: the MMSC sent up a delivery report which Oracle Communications Services Gatekeeper has no record of sending.
Check the log for more information. Common problem: Oracle Communications Services Gatekeeper is not configured to request delivery reports but the MMSC is sending them anyway.
Oracle Communications Services Gatekeeper does not support the address type attached to the multimedia message.
Check the log for more information and check the address type.
Oracle Communications Services Gatekeeper is unable to start message notification.
Check the log for more information. Common problems: duplicated correlator IDs; storage errors.
Oracle Communications Services Gatekeeper is unable to stop message notification.
Check the log for more information. Common problems: Correlator ID doesn’t exist; storage errors.
The MMSC and Oracle Communications Services Gatekeeper are out of sync with respect to notifications. A mobile-originated message has been sent from the network no application has set up a notification to receive it.
Check the log for more information.
The SubmitResponse returned an error-code.
Look at the logs to see the specific status code and status text.
The budget quota for a subscriber with limitExceedOK set to true has been exceeded.
Oracle Communications Services Gatekeeper was unable to start the CDR to Diameter module
Check the logs for more information.
Oracle Communications Services Gatekeeper was unable to start the CDRDiameter node
Check the logs for more information.Check the configuration of the CDR to Diameter module.
Oracle Communications Services Gatekeeper failed to shutdown the CDRDiameter node
Check the logs for more information.
A general exception occurred when sending Diameter ACR
Check the logs for more information.
An input/output exception occurred when sending Diameter ACR.
Check the logs for more information.
The Diameter response contained an error.
Check logs for more information. The Diameter server might have denied request
No connection to the Diameter server is available, even though CDR to Diameter module is set to enable
Check logs for more information. The Diameter server might be down
An I/O error occurred during the sending of the INITIAL Diameter CCR.
Check the logs for more information.
An I/O error occurred during the sending of the TERMINATE Diameter CCR.
Check the logs for more information.
Oracle Communications Services Gatekeeper failed to start the credit control interceptor.
Check the logs for more information.
The Diameter node failed to start.
Check the logs for more information. Check the credit control interceptor module’s configuration.
The Diameter node failed to shutdown.
Check the logs for more information.
A site configuration mismatch has been detected. Sites present in the site-local configuration are not in the remote site configuration.
Verify that the list of geo-redundant site is identical on all geo-redundant sites of Oracle Communications Services Gatekeeper.
A site configuration mismatch has been detected. Sites present in the remote site configuration are not in the site-local configuration.
Verify that the list of geo-redundant sites is identical on all geo-redundant sites of the Oracle Communications Services Gatekeeper.
An account configuration mismatch has been detected. Checksums for one or more stores are different.
Re-sync the slave site manually using the syncFromGeoMaster operation.
The service failed to replicate a configuration update, either master to slave or slave to master.
Check the logs for more information.
Failed to connect to Diameter server.
Check configuration of Parlay X 3.0 Payment/Diameter plug-in.
Check the logs for more information.
Failed to disconnect from Diameter server.
Check configuration of Parlay X 3.0 Payment/Diameter plug-in.
Check the logs for more information.
Because the heartbeat service is sending pings, the expiration of the timer is ignored.
The heatbeat service was able to contact the plugin-in
The heatbeat service was unable to contact the plugin-in
Oracle Communications Services Gatekeeper was unable to start the plug-in.
Check logs for more information. Possible issues: Oracle Communications Services Gatekeeper was unable to locate the WorkContextMap; MBean-related exceptions.
Oracle Communications Services Gatekeeper was unable to stop the plug-in.
Check logs. Possible issues: MBean-related exceptions.
Oracle Communications Services Gatekeeper was unable to activate the plug-in.
Check the log for more information. Possible issues: The plugin-in is not ready or there is a duplicated Plugin-in ID.
Oracle Communications Services Gatekeeper was unable to deactivate the plug-in.
Check the log for more information. Possible issues: Oracle Communications Services Gatekeeper is unable to find a plug-in with the given ID.
Oracle Communications Services Gatekeeper was unable to update call status.
Check the log for more information. Make sure the storage service is available.Verify the database is running. Try to restart Oracle Communications Services Gatekeeper.
Oracle Communications Services Gatekeeper was unable to update call status.
Check the log for more information. Make sure the storage service is available.Verify the database is running. Try to restart Oracle Communications Services Gatekeeper.
Oracle Communications Services Gatekeeper was unable update call status.
Check the log for more information. Make sure the storage service is available.Verify the database is running. Try to restart Oracle Communications Services Gatekeeper.
Oracle Communications Services Gatekeeper was unable to update call status.
Check the log for more information. Make sure the storage service is available.Verify the database is running. Try to restart Oracle Communications Services Gatekeeper.
Oracle Communications Services Gatekeeper was unable to update call status
Check the log for more information. Possible issues: the Parlay gateway is unavailable or in an abnormal state; the call control manager is not in active state; or the call control call is not in idle or active state.
Oracle Communications Services Gatekeeper was unable to invoke IpMultiPartyCall.getInfoReq on the Parlay gateway
Check the log for more information. Possible issues: the Parlay gateway is unavailable or in an abnormal state; the call control manager is not in active state.
Oracle Communications Services Gatekeeper was unable to invoke to invoke IpCallLeg.continueProcessing on Parlay gateway.
Check the log for more information. Possible issues: the Parlay gateway is unavailable or in an abnormal state; the call leg doesn't exist in the network; or the call leg is in releasing state.
Oracle Communications Services Gatekeeper was unable to invoke IpMultiPartyCall.createAndRouteCallLegReq on Parlay gateway.
Check logs for more information. Possible issues: the Parlay gw is in an abnormal status or unavailable; the call is not in idle or active state; the call control manager is not in active state.
Oracle Communications Services Gatekeeper was unable to invoke IpMultiPartyCallControlManager.createCall on Parlay gateway.
Check the log for more information. Possible issues: the Parlay gateway is unavailable or in an abnormal state; the call control manager is not in active state.
Oracle Communications Services Gatekeeper was unable to invoke IpCallLeg.eventReportReq() on the Parlay gateway.
Check the log for more information. Possible issues: the Parlay gateway is unavailable or in an abnormal state; the call leg does not exist in the network or is in releasing state.
Oracle Communications Services Gatekeeper was unable to invoke IpCallLeg.getInfoReq() on Parlay gateway.
Check the log for more information. Possible issues: the Parlay gateway is unavailable or in an abnormal state; the call leg does not exist in the network or is in releasing state.
Oracle Communications Services Gatekeeper was unable to invoke IpMultiPartyCall.release on the Parlay gateway.
Check the log for more information. Possible issues: the Parlay gateway is unavailable or in an abnormal state; the call leg does not exist in the network or is in releasing state.
Oracle Communications Services Gatekeeper was unable to invoke IpCallLeg.routeReq on the Parlay gateway.
Check the log for more information. Possible issues: the Parlay gateway is unavailable or in an abnormal state; the call leg does not exist in the network or is in releasing state.
Oracle Communications Services Gatekeeper was unable to invoke IpMultiPartyCall.createCallLeg on the Parlay gateway.
Check the log for more information. Possible issues: the Parlay gateway is unavailable or in an abnormal state; the call does not exist in the network or is in releasing state.
The Parlay MPCC plugin-in for the Parlay X 3.0 Call Notification communication service failed to start.
Check the log for more information.
The Parlay MPCC plugin-in for the Parlay X 3.0 Call Notification communication service failed to activate.
Check the log for more information.
The Parlay MPCC plugin-in for the Parlay X 3.0 Call Notification communication service failed to stop.
Check the log for more information.
The Parlay MPCC plugin-in for the Parlay X 3.0 Call Notification communication service failed to deactivate.
Check the log for more information.
Oracle Communications Services Gatekeeper was unable to deliver a notification to the application.
Check the log for more information. Make sure the AT layer is available and that the notification URL is correct and available.
Oracle Communications Services Gatekeeper was unable to deliver the location of a recorded message to the application.
| Note: | The Audio Call communication service does not support Play and Record Interaction for 4.0. |
Oracle Communications Services Gatekeeper was unable to deliver the digits collected from the end user to the application.
Check the log for more information. Make sure the AT layer is available and that the notification URL is correct and available.
Oracle Communications Services Gatekeeper was unable to delete a notification registration in the Parlay gateway.
Check the log for more information. Make sure the gateway is available. Use OAM methods to make sure the connection is alive.
Oracle Communications Services Gatekeeper was unable to create a notification registration in the Parlay gateway.
Check the log for more information. Make sure the gateway is available. Use OAM methods to make sure the connection is alive.
Oracle Communications Services Gatekeeper was unable to set a callback for a call leg in the Parlay Gateway.
Check the log for more information. Make sure the gateway is available. Use OAM methods to make sure the connection is alive.
Oracle Communications Services Gatekeeper was unable to invoke continueProcessing on the Parlay Gateway.
Check the log for more information. Make sure the gateway is available. Use OAM methods to make sure the connection is alive.
Oracle Communications Services Gatekeeper was unable to create a call leg for the call session in the Parlay gateway.
Check the log for more information. Make sure the gateway is available. Use OAM methods to make sure the connection is alive.
Oracle Communications Services Gatekeeper was unable to start the plug-in.
Check the log for more information. Possible issues: unable to location WorkContextMap, MBean related exceptions.
Oracle Communications Services Gatekeeper was unable to activate the plug-in.
Check the log for more information. Possible issues: MBean related exceptions.
Oracle Communications Services Gatekeeper was unable to change the state of the plug-in to active.
Check the log for more information. Possible issues: the plugin-in is not ready; there are duplicate plugin-in IDs.
Oracle Communications Services Gatekeeper was unable to change the state of the plug-in to inactive.
Check the log for more information. Possible issues: the plugin-in with the ID specified cannot be found.
Oracle Communications Services Gatekeeper was unable to update the status of the call.
Check the log for more information. Make sure that the database and the database connection are active.
Oracle Communications Services Gatekeeper was unable to update the status of the call.
Check the log for more information. Make sure that the database and the database connection are active.
Oracle Communications Services Gatekeeper was unable to update the status of the call.
Check the log for more information. Make sure that the database and the database connection are active.
Oracle Communications Services Gatekeeper was unable to update the status of the call.
Check the log for more information. Make sure that the database and the database connection are active.
Oracle Communications Services Gatekeeper was unable to update the status of the call.
Check the log for more information. Make sure that the database and the database connection are active.
Oracle Communications Services Gatekeeper was unable to update the status of the call.
Check the log for more information. Make sure that the database and the database connection are active.
Oracle Communications Services Gatekeeper was unable to update the status of the call.
Check the log for more information. Make sure that the database and the database connection are active.
Oracle Communications Services Gatekeeper was unable to update the status of the call.
Check the log for more information. Make sure that the database and the database connection are active.
Oracle Communications Services Gatekeeper was unable to invoke a method on the Parlay gateway.
Check the log for more information. Make sure the gateway is available. Use OAM methods to make sure the connection is alive. Make sure IpAppUICallRef is not null.
Oracle Communications Services Gatekeeper was unable to invoke a method on the Parlay gateway.
Check the log for more information. Make sure the gateway is available. Use OAM methods to make sure the connection is alive. Make sure the UI session is valid.
Oracle Communications Services Gatekeeper was unable to invoke a method on the Parlay gateway.
Check the log for more information. Make sure the gateway is available. Use OAM methods to make sure the connection is alive. Make sure the UI session is valid. Make sure the criteria are valid.
Oracle Communications Services Gatekeeper was unable to invoke a method on the Parlay Gateway.
Check the log for more information. Make sure the gateway is available. Use OAM methods to make sure the connection is alive. Make sure the UI session is valid.
Oracle Communications Services Gatekeeper was received an error message back from the Parlay Gateway.
Check the log for more information. Possible issues: the provided information (InfoId, InfoData, or InfoAddress) is invalid; improper response by call participant.
Oracle Communications Services Gatekeeper was received an error message back from the Parlay gateway.
Check the log for more information. Possible issues: the provided information (InfoId, InfoData, or InfoAddress) is invalid; improper response by call participant.
Oracle Communications Services Gatekeeper was received an error message back from the Parlay gateway.
Check the log for more information. Possible issues: invalid address or the call was not in a valid state for the requested operation.
Oracle Communications Services Gatekeeper was received an error message back from the Parlay Gateway.
Check the log for more information. Possible issues: invalid address or the call was not in a valid state for the requested operation.
Reactivation timer fired. Setting plug-in status to active.
Reactivation timer breached. Setting plug-in status to inactive.
Check the connection to the network element.
Oracle Communications Services Gatekeeper was unable to start the plug-in.
Check the log for more information.
Oracle Communications Services Gatekeeper was unable to activate the plug-in.
Check the log for more information.
Oracle Communications Services Gatekeeper was unable to stop the plug-in.
Check the log for more information.
Oracle Communications Services Gatekeeper was unable to deactivate the plug-in.
Check the log for more information.
Oracle Communications Services Gatekeeper was unable to perform the “get” method call.
Check the log for more information.
Oracle Communications Services Gatekeeper was unable to perform the “getProfile” method call.
Check the log for more information.
Oracle Communications Services Gatekeeper was unable to establish a call session
Check the log for more information.
Oracle Communications Services Gatekeeper was unable to retrieve information on a call
Check the log for more information.
Oracle Communications Services Gatekeeper was unable to end a call
Check the log for more information.
Oracle Communications Services Gatekeeper was unable to cancel a call request
Check the log for more information.
Oracle Communications Services Gatekeeper was unable to initiate a call attempt for the first participant
Check the log for more information. Check the plug-in connection to the SS7 stack.
Oracle Communications Services Gatekeeper was unable to initiate a call attempt for the second participant
Check the log for more information. Check the plug-in connection to the SS7 stack.
Oracle Communications Services Gatekeeper was unable to continue call processing
Check the log for more information. Check the plug-in connection to the SS7 stack.
Oracle Communications Services Gatekeeper was unable to terminate an INAP dialog
Check the log for more information. Check the plug-in connection to the SS7 stack.
Oracle Communications Services Gatekeeper was unable to release a call session
Check the log for more information. Check the plug-in connection to the SS7 stack.
Oracle Communications Services Gatekeeper was unable to activate the plug-in instance
Check the log for more information.
Oracle Communications Services Gatekeeper was unable to deactivate the plug-in instance
Check the log for more information.
Oracle Communications Services Gatekeeper was unable to send a push message
Check the log for more information.
Oracle Communications Services Gatekeeper was unable to send a result notification message
Check the log for more information.
Oracle Communications Services Gatekeeper did a successful bind to the SMSC.
Oracle Communications Services Gatekeeper lost the connection with the SMSC.
Reset the SMPP connection using the Administration console.
The SMPP connection were activated.
All SMPP connections are inactive.
Reset the SMPP connection using the Administration console
Failed to send a network-triggered message to an application.
Application failed to bind to the Native SMPP Service Facade.
The plug-in failed to send the first part of a short message to the SMSC.
Verify that the SMPP connection is up.
The plug-in failed to send the first part of a short message to the SMSC.
Verify that the SMPP connection is up.
The plug-in failed to correlate a network-triggered message with an application.
An exception was thrown when the application attempted to submit a message to the network.
Check the log for more information.
An exception was thrown when the MMSC attempted to deliver a message using the incorrect .xsd.
Check the log for more information.
An exception was thrown when the MMSC attempted to deliver a delivery report using the incorrect .xsd.
Check the log for more information.
An exception was thrown when the MMSC attempted to deliver a read reply report using the incorrect .xsd.
Check the log for more information.
A generic exception was thrown in a communication service.
Provide logs with exception stack traces to Oracle.
|