Oracle® Communications Services Gatekeeper Alarm Handling Guide Release 5.0 Part Number E16614-02 |
|
|
View PDF |
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.
Major
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.
Major
Create the remote sites on the local site.
The application does not exist, or is in state inactive.
Major
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.
Major
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.
Major
Notify the service provider or update the SLA.
The quota for the service type stated in the Service Level Agreement is exceeded.
Major
Notify the service provider or update the SLA.
Properties passed in by an application are not allowed.
Major
Notify the service provider of the application behavior.
The value of a parameter passed in by an application is not allowed.
Minor
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.
Minor
Check the logs.
An application tried to use a method that is not allowed according to the SLA.
Major
Notify the service provider or update the SLA.
An application tried to use a method that is not allowed according to the SLA.
Minor
Notify the service provider or update the SLA.
A service correlator threw an exception when it was invoked.
Critical
Examine the log files.
The RequestFactory threw an exception when it was invoked.
Critical
Examine the log files.
Could not find a global node or service provider node SLA.
Major
Update the node SLA.
The service contract in the SLA for the service provider group or application group has expired.
Major
Update the SLA.
The service contract for the service type in the SLA for the service provider group or application group has expired.
Major
Update the SLA.
The service contract for the service type in the SLA for the service provider group or application group could not be found
Major
Update the SLA.
The composed service contract has expired.
Major
Update the SLA.
The request rate is higher than the rate specified in the composed service contract.
Major
Notify the service provider or update the SLA.
The quota for the composed service contract has been exceeded.
Major
Notify the service provider or update the SLA.
There is configuration mismatch between local and remote sites.
Major
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.
Major
Check the connection between the sites.
Internal exception thrown when performing a Corba operation
Minor
Send any log with stack trace to Oracle
Internal exception thrown when performing a Corba operation
Minor
Send any log with stack trace to Oracle
Internal exception thrown when performing a Corba operation
Minor
Send any log with stack trace to Oracle
Internal exception thrown when performing a Corba operation
Minor
Send any log with stack trace to Oracle
Internal exception thrown when performing a Corba operation
Minor
Send any log with stack trace to Oracle
Internal exception thrown when performing a Corba operation
Minor
Send any log with stack trace to Oracle
Internal exception thrown when performing a Corba operation
Minor
Send any log with stack trace to Oracle.
Internal exception thrown when performing a Corba operation.
Minor
Send any log with stack trace to Oracle.
Internal exception thrown when performing a Corba operation.
Minor
Send any log with stack trace to Oracle.
Internal exception thrown when an MBean does not comply to the MBean specification.
Minor
Send any log with stack trace to Oracle.
Internal exception thrown when an MBean Object Name is malformed.
Minor
Send any log with stack trace to Oracle.
Internal exception thrown when an MBean fails to register.
Minor
Send any log with stack trace to Oracle.
Internal exception thrown when an instance of an MBean already exists.
Minor
Send any log with stack trace to Oracle.
Internal exception thrown when a requested instance of an MBean does not exist.
Minor
Send any log with stack trace to Oracle.
Internal exception thrown when a management error severity fault happens.
Minor
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.
Minor
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.
Minor
Contact Oracle with the appropriate log file.
No plugin-in appropriate for this request can be found.
Minor
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.
Minor
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.
Minor
Send any log with stack trace to Oracle
The number of destination addresses for the message exceeded the SMPP maximum (254).
Minor
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.
Minor
Check the connection between Services Gatekeeper and the SMSC in the SMPP Server Service.
Note:
This alarm may be triggered by either the SMS communication service or the binary SMS communication service.Services Gatekeeper was unable to notify the application of a network-initiated message.
Minor
Check the connection between Services Gatekeeper and the application in the SMPP Server Service. 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.Services Gatekeeper received a network-initiated message for which there was no registered notification.
Minor
Informational only.
Note:
This alarm may be triggered by either the SMS communication service or the binary SMS communication service.Services Gatekeeper was unable to notify the application of a network message delivery status.
Minor
Check the connection between Services Gatekeeper and the application in the SMPP Server Service. 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 Services Gatekeeper to the application.
Major
Check the exception stack trace in the log.
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.
Minor
Check the SMSC logs.
Note:
This alarm may be triggered by either the SMS communication service or the binary SMS communication service.Services Gatekeeper has detected that segments from this message are missing.
Warning
Check the logs.
Note:
This alarm may be triggered by either the SMS communication service or the binary SMS communication service.An illegal XParameter was passed.
Minor
Check the SOAP headers.
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 Services Gatekeeper to handle.
Major
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.
Warning
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.
Warning
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.
Warning
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.
Possible causes are:
the subscription already exists
no SIP-URI mapping has been configured for the application instance group
internal errors such as storage service errors or connectivity issues with OCCAS
Warning
Verify the following Presence SIP plug-in configurations in the Administration Console:
SIPNodeUrl, SipNodeUsername and SIPNodePassword
SIP URL mapping
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:
a subscription has not been submitted or approved
a policy violation occurred when trying to retrieve unauthorized presence attributes
an internal error such as a storage service error occurred
Warning
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:
a presence subscription has not been submitted or approved
a start notification request with the same correlator already exists
a start notification request for the specified presentity has already been submitted by the same application instance group
an internal error such as a storage service error has occurred
Warning
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:
a startPresenceNotification has not been submitted by the client
internal errors such as storage service errors
Warning
Verify the database is running. Try to restart 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.
Warning
Try to restart Services Gatekeeper. Provide logs with exception stack trace to Oracle
An Oracle Access Manager operation error has occurred. This is most likely due to storage service errors.
Warning
Verify the database is running. Try to restart Services Gatekeeper. Provide logs with exception stack trace to Oracle
The budget service discovered a site configuration mismatch between geo-redundant sites.
Major
Verify that the list of geo-redundant sites in GeoRedundantService and GeoMasterSiteId settings in GeoStorageService is identical on all geo-redundant sites of Services Gatekeeper
Duplicate geo-redundancy masters were detected. The situation has been corrected.
Minor
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.
Major
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.
Minor
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.
Services Gatekeeper was unable to reach one of the remote geo-redundant sites.
Major
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.
Major
Re-sync the slave site manually using the syncFromGeoMaster
operation
The value of the budget is below 20% of the maximum value.
Major
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.
Warning
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.
Major
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.
Major
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.
Warning
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.
Minor
Provide logs with exception stack traces to Oracle.
The result of a query result was possibly truncated due to maximum query result size limit.
Warning
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.
Major
Informational only.
Failed to send a heartbeat to the MLP Server. Plugin-in status has been deactivated.
Major
Check the MLP server to make sure it is available.
The Terminal Location MLP plugin-in failed to start.
Major
Check the log for more information.
The Terminal Location MLP plugin-in failed to stop.
Major
Check the log for more information.
The Terminal Location MLP plugin-in was not activated.
Major
Check the log for more information.
The Terminal Location MLP plugin-in was not deactivated.
Major
Check the log for more information.
The attempt to send a location request failed
Major
Make sure the MLP server is available. Check the log for more information.
Services Gatekeeper was unable to notify the application that location notification has ceased.
Major
Make sure the AT layer and the notification URL are available. Check the log for more information.
Services Gatekeeper was unable to notify the application that a location error has occurred.
Major
Make sure the AT layer and the notification URL are available. Check the log for more information.
Services Gatekeeper was unable to notify the application that a location notification has been received.
Major
Make sure the AT layer and the notification URL are available. Check the log for more information.
Services Gatekeeper was unable to send a multimedia message to the network.
Major
Check the log for more information. Common problems: missing/invalid required parameters; configuration problems; storage errors.
Services Gatekeeper was unable to get delivery status on a multimedia message from the network.
Major
Check the log for more information. Common problems: invalid request identifier; storage errors.
Services Gatekeeper was unable to send the list of received messages to the application
Major
Check the log for more information. Common problems: invalid MM7 configuration; storage errors.
Services Gatekeeper was unable to send a requested received multimedia message - including attachment - to the application.
Major
Check the log for more information. Common problems: no attachment found; storage errors.
Services Gatekeeper was unable to send an MM7 message to the network.
Major
Check the log for more information. Common problems: MM7 Relay Server not ready or misconfigured.
Services Gatekeeper was unable to activate the MM7 plug-in.
Warning
Check the log for more information. Common problems: Plugin-in not ready; plugin-in ID duplicated.
Services Gatekeeper was unable to deactivate the MM7 plug-in.
Warning
Check the log for more information. Common problems: can't find the plugin-in with the ID provided.
Services Gatekeeper was unable to start the MM7 plug-in.
Warning
Check the log for more information. Common problems: failed to located WorkContextMap; MBean-related exceptions.
Services Gatekeeper was unable to stop the MM7 plug-in.
Warning
Check the log for more information. Common problem: MBean-related exceptions.
Services Gatekeeper was unable to notify the application that a message has been received from the network.
Warning
Check the log for more information. Common problems: no matching NotificationInfo; storage errors; unsupported address type; application not available.
Services Gatekeeper was unable to notify the application that a message delivery receipt has been received from the network.
Warning
Check the log for more information. Common problems: no matching messageinfo, recipient number not found; application unavailable.
Services Gatekeeper was unable to contact the application.
Warning
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.
Warning
Check the log for more information. Common problem: issue between Services Gatekeeper and the MMSC.
The incoming delivery report did not correlate to a message info. For example: the MMSC sent up a delivery report which Services Gatekeeper has no record of sending.
Warning
Check the log for more information. Common problem: Services Gatekeeper is not configured to request delivery reports but the MMSC is sending them anyway.
Services Gatekeeper does not support the address type attached to the multimedia message.
Warning
Check the log for more information and check the address type.
Services Gatekeeper is unable to start message notification
Major
Check the log for more information. Common problems: duplicated correlator IDs; storage errors.
Services Gatekeeper is unable to stop message notification.
Major
Check the log for more information. Common problems: Correlator ID doesn't exist; storage errors.
The MMSC and 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.
Major
Check the log for more information.
The SubmitResponse returned an error-code.
Major
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.
Minor
Informational only.
Services Gatekeeper was unable to start the CDR to Diameter module.
Major
Check the logs for more information.
Services Gatekeeper was unable to start the CDRDiameter node.
Minor
Check the logs for more information.Check the configuration of the CDR to Diameter module.
Services Gatekeeper failed to shut down the CDRDiameter node.
Minor
Check the logs for more information.
A general exception occurred when sending Diameter ACR.
Minor
Check the logs for more information.
An input/output exception occurred when sending Diameter ACR.
Minor
Check the logs for more information.
The Diameter response contained an error.
Minor
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
.
Minor
Check logs for more information. The Diameter server might be down
An I/O error occurred during the sending of the INITIAL Diameter CCR.
Minor
Check the logs for more information.
An I/O error occurred during the sending of the TERMINATE Diameter CCR.
Minor
Check the logs for more information.
Services Gatekeeper failed to start the credit control interceptor.
Major
Check the logs for more information.
The Diameter node failed to start.
Minor
Check the logs for more information. Check the credit control interceptor module's configuration.
The Diameter node failed to shut down.
Minor
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.
Major
Verify that the list of geo-redundant site is identical on all geo-redundant sites of Services Gatekeeper.
A site configuration mismatch has been detected. Sites present in the remote site configuration are not in the site-local configuration.
Major
Verify that the list of geo-redundant sites is identical on all geo-redundant sites of Services Gatekeeper.
An account configuration mismatch has been detected. Checksums for one or more stores are different.
Major
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.
Major
Check the logs for more information.
Failed to connect to Diameter server.
Minor
Check configuration of Parlay X 3.0 Payment/Diameter plug-in.
Check the logs for more information.
Failed to disconnect from Diameter server.
Minor
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.
Warning
Informational only.
The heatbeat service was able to contact the plugin-in.
Warning
Informational only.
The heatbeat service was unable to contact the plugin-in.
Warning
Informational only.
Services Gatekeeper was unable to start the plug-in.
Major
Check logs for more information. Possible issues: Services Gatekeeper was unable to locate the WorkContextMap; MBean-related exceptions.
Services Gatekeeper was unable to stop the plug-in.
Major
Check logs. Possible issues: MBean-related exceptions.
Services Gatekeeper was unable to activate the plug-in.
Major
Check the log for more information. Possible issues: The plugin-in is not ready or there is a duplicated Plugin-in ID.
Services Gatekeeper was unable to deactivate the plug-in.
Major
Check the log for more information. Possible issues: Services Gatekeeper is unable to find a plug-in with the given ID.
Services Gatekeeper was unable to update call status.
Warning
Check the log for more information. Make sure the storage service is available.Verify the database is running. Try to restart Services Gatekeeper.
Services Gatekeeper was unable to update call status.
Warning
Check the log for more information. Make sure the storage service is available.Verify the database is running. Try to restart Services Gatekeeper.
Services Gatekeeper was unable update call status.
Warning
Check the log for more information. Make sure the storage service is available.Verify the database is running. Try to restart Services Gatekeeper.
Services Gatekeeper was unable to update call status.
Warning
Check the log for more information. Make sure the storage service is available.Verify the database is running. Try to restart Services Gatekeeper.
Services Gatekeeper was unable to update call status.
Warning
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.
Services Gatekeeper was unable to invoke IpMultiPartyCall.getInfoReq
on the Parlay gateway.
Warning
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.
Services Gatekeeper was unable to invoke to invoke IpCallLeg.continueProcessing
on Parlay gateway.
Warning
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.
Services Gatekeeper was unable to invoke IpMultiPartyCall.createAndRouteCallLegReq
on Parlay gateway.
Warning
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.
Services Gatekeeper was unable to invoke IpMultiPartyCallControlManager.createCall
on Parlay gateway.
Warning
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.
Services Gatekeeper was unable to invoke IpCallLeg.eventReportReq()
on the Parlay gateway.
Warning
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.
Services Gatekeeper was unable to invoke IpCallLeg.getInfoReq()
on Parlay gateway.
Warning
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.
Services Gatekeeper was unable to invoke IpMultiPartyCall.release
on the Parlay gateway.
Warning
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.
Services Gatekeeper was unable to invoke IpCallLeg.routeReq
on the Parlay gateway.
Warning
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.
Services Gatekeeper was unable to invoke IpMultiPartyCall.createCallLeg
on the Parlay gateway.
Warning
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.
Major
Check the log for more information.
The Parlay MPCC plugin-in for the Parlay X 3.0 Call Notification communication service failed to activate.
Major
Check the log for more information.
The Parlay MPCC plugin-in for the Parlay X 3.0 Call Notification communication service failed to stop.
Major
Check the log for more information.
The Parlay MPCC plugin-in for the Parlay X 3.0 Call Notification communication service failed to deactivate.
Major
Check the log for more information.
Services Gatekeeper was unable to deliver a notification to the application.
Warning
Check the log for more information. Make sure the AT layer is available and that the notification URL is correct and available.
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.Warning
Not currently implemented.
Services Gatekeeper was unable to deliver the digits collected from the end user to the application.
Warning
Check the log for more information. Make sure the AT layer is available and that the notification URL is correct and available.
Services Gatekeeper was unable to delete a notification registration in the Parlay gateway.
Warning
Check the log for more information. Make sure the gateway is available. Use Oracle Access Manager methods to make sure the connection is alive.
Services Gatekeeper was unable to create a notification registration in the Parlay gateway.
Warning
Check the log for more information. Make sure the gateway is available. Use Oracle Access Manager methods to make sure the connection is alive.
Services Gatekeeper was unable to set a callback for a call leg in the Parlay Gateway.
Warning
Check the log for more information. Make sure the gateway is available. Use Oracle Access Manager methods to make sure the connection is alive.
Services Gatekeeper was unable to invoke continueProcessing
on the Parlay Gateway.
Warning
Check the log for more information. Make sure the gateway is available. Use Oracle Access Manager methods to make sure the connection is alive.
Services Gatekeeper was unable to create a call leg for the call session in the Parlay gateway.
Warning
Check the log for more information. Make sure the gateway is available. Use Oracle Access Manager methods to make sure the connection is alive.
Services Gatekeeper was unable to start the plug-in.
Major
Check the log for more information. Possible issues: unable to location WorkContextMap, MBean related exceptions.
Services Gatekeeper was unable to activate the plug-in.
Major
Check the log for more information. Possible issues: MBean related exceptions.
Services Gatekeeper was unable to change the state of the plug-in to active.
Major
Check the log for more information. Possible issues: the plugin-in is not ready; there are duplicate plugin-in IDs.
Services Gatekeeper was unable to change the state of the plug-in to inactive.
Major
Check the log for more information. Possible issues: the plugin-in with the ID specified cannot be found.
Services Gatekeeper was unable to update the status of the call.
Warning
Check the log for more information. Make sure that the database and the database connection are active.
Services Gatekeeper was unable to update the status of the call.
Warning
Check the log for more information. Make sure that the database and the database connection are active.
Services Gatekeeper was unable to update the status of the call.
Warning
Check the log for more information. Make sure that the database and the database connection are active.
Services Gatekeeper was unable to update the status of the call.
Warning
Check the log for more information. Make sure that the database and the database connection are active.
Services Gatekeeper was unable to update the status of the call.
Warning
Check the log for more information. Make sure that the database and the database connection are active.
Services Gatekeeper was unable to update the status of the call.
Warning
Check the log for more information. Make sure that the database and the database connection are active.
Services Gatekeeper was unable to update the status of the call.
Warning
Check the log for more information. Make sure that the database and the database connection are active.
Services Gatekeeper was unable to update the status of the call.
Warning
Check the log for more information. Make sure that the database and the database connection are active.
Services Gatekeeper was unable to invoke a method on the Parlay gateway.
Warning
Check the log for more information. Make sure the gateway is available. Use Oracle Access Manager methods to make sure the connection is alive. Make sure IpAppUICallRef is not null.
Services Gatekeeper was unable to invoke a method on the Parlay gateway.
Warning
Check the log for more information. Make sure the gateway is available. Use Oracle Access Manager methods to make sure the connection is alive. Make sure the UI session is valid.
Services Gatekeeper was unable to invoke a method on the Parlay gateway.
Warning
Check the log for more information. Make sure the gateway is available. Use Oracle Access Manager methods to make sure the connection is alive. Make sure the UI session is valid. Make sure the criteria are valid.
Services Gatekeeper was unable to invoke a method on the Parlay Gateway.
Warning
Check the log for more information. Make sure the gateway is available. Use Oracle Access Manager methods to make sure the connection is alive. Make sure the UI session is valid.
Services Gatekeeper was received an error message back from the Parlay Gateway.
Warning
Check the log for more information. Possible issues: the provided information (InfoId, InfoData, or InfoAddress) is invalid; improper response by call participant.
Services Gatekeeper was received an error message back from the Parlay gateway.
Warning
Check the log for more information. Possible issues: the provided information (InfoId, InfoData, or InfoAddress) is invalid; improper response by call participant.
Services Gatekeeper was received an error message back from the Parlay gateway.
Warning
Check the log for more information. Possible issues: invalid address or the call was not in a valid state for the requested operation.
Services Gatekeeper was received an error message back from the Parlay Gateway.
Warning
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.
Warning
Informational only.
Reactivation timer breached. Setting plug-in status to inactive.
Warning
Check the connection to the network element.
Services Gatekeeper was unable to start the plug-in.
Major
Check the log for more information.
Services Gatekeeper was unable to activate the plug-in.
Major
Check the log for more information.
Services Gatekeeper was unable to stop the plug-in.
Major
Check the log for more information.
Services Gatekeeper was unable to deactivate the plug-in.
Major
Check the log for more information.
Services Gatekeeper was unable to perform the “get” method call.
Warning
Check the log for more information.
Services Gatekeeper was unable to perform the “getProfile” method call.
Warning
Check the log for more information.
Services Gatekeeper was unable to establish a call session.
Major
Check the log for more information.
Services Gatekeeper was unable to retrieve information on a call.
Major
Check the log for more information.
Services Gatekeeper was unable to end a cal
Major
Check the log for more information.
Services Gatekeeper was unable to cancel a call request.
Major
Check the log for more information.
Services Gatekeeper was unable to initiate a call attempt for the first participant.
Major
Check the log for more information. Check the plug-in connection to the SS7 stack.
Services Gatekeeper was unable to initiate a call attempt for the second participant.
Major
Check the log for more information. Check the plug-in connection to the SS7 stack.
Services Gatekeeper was unable to continue call processing.
Major
Check the log for more information. Check the plug-in connection to the SS7 stack.
Services Gatekeeper was unable to terminate an INAP dialog.
Major
Check the log for more information. Check the plug-in connection to the SS7 stack.
Services Gatekeeper was unable to release a call session.
Major
Check the log for more information. Check the plug-in connection to the SS7 stack.
Services Gatekeeper was unable to activate the plug-in instance.
Major
Check the log for more information.
Services Gatekeeper was unable to deactivate the plug-in instance.
Major
Check the log for more information.
Services Gatekeeper was unable to send a push message.
Major
Check the log for more information.
Services Gatekeeper was unable to send a result notification message.
Major
Check the log for more information.
Could not connect to the SS7 stack.
Major
Check the network and try to reinitialize the stack connection using Terminal Server/MAP management operations.
The Terminal Status/MAP plug-in has connected to the SS7 stack.
Warning
Does not require action but may contain useful information. This plug-in has connected to at least one backend instance in the SS7 stack. Alarm 400403 may be useful in debugging this problem.
Dialog lost; the connection to at least one of the SS7 stack may be lost.
Major
Confirm that the SS7 stack process and its network connection are up and running.
Received remote user status from the SS7 stack.
Warning
Does not require action but may contain useful information. You can use this alarm to discover whether a remote terminal is available, unavailable, or busy. Useful for resolving alarm 400401.
It is not possible to create the anyTimeInterrogation
message in the Terminal Status/Map plug-in.
Minor
Check the network and try to reinitialize the stack connection using the using Terminal Server/MAP management operations. An exception is also thrown.
The SS7 network could not create (encode) the message.
Minor
An error occurred while the SS7 network attempted to encode the incoming message into the binary format that SS7 uses.
This could mean that:
The Terminal Status/MAP plug-in could not bind with the stack or the bind was lost. Make sure that the SS7 stack is running and that the CpUserId
value, and SS7 host/port/instance are correct.
The MBean was incorrectly configured. Confirm that it is being created and sent correctly.
That the SS7 network is throwing internal errors. Confirm that it is functioning correctly.
No answer (or a faulty answer) received from the SS7 stack.
Minor
This probably indicates a problem with the SS7 stack. Make sure that the GT/SPC/SSN are configured correctly in NetworkSelection
. Start a SS7 stack trace and check the ss7trace.log
file for information. See the SS7 documentation for more information.
Error in the connection with the SS7 stack.
Major
The connection with all SS7 backend instances has been lost. The Terminal Status/MAP plug-in tries to reconnect.
A server connection has been established.
Warning
Informational
A server connection has closed.
Major
Check the connections between Services Gatekeeper and the SMSC and applications.
A client connection has been established.
Warning
Informational
A client connection has closed.
Major
Check the connections between Services Gatekeeper and the SMSC and applications.
All client connections to this server service have been reset.
Warning
Informational
A client connection re-connection attempt has failed.
Major
Check the connection between Services Gatekeeper and the SMSC.
ChannelProcessor PeerConnectionIds are empty while connection-based routing is enabled.
The connection will be closed.
Major
Check the connections between Services Gatekeeper and the SMSC and applications.
Application-facing ChannelProcessor PeerPluginInstanceIds are empty while connection-based routing is disabled.
The server connection will be closed.
Major
Check the connections between Services Gatekeeper and the SMSC and applications.
PluginInstanceInfo ClientConnectionIds are empty while connection-based routing is disabled.
The status of the plug-in instance is UNBIND.
Major
Check the connections between Services Gatekeeper and the SMSC and applications.
PluginInstanceInfo ServerConnectionIds are empty while connection-based routing is disabled.
All client connections to the plug-in will be closed.
Major
Check the connections between Services Gatekeeper and the SMSC and applications.
Mobile-originated request failed because of an invalid local server connection with MO jumping disabled.
Minor
Check the address range configuration in the ApplicationSpecificSettings. See the "listApplicationSpecificSettings" operation in System Administrator's Guide, another document in this set.
Also check the connections between Services Gatekeeper and the SMSC and applications.
Mobile-terminated request failed because of an invalid local client connection.
Minor
Check the connections between Services Gatekeeper and the SMSC and applications.
Exception raised by submitSmResponse operation.
Warning
Check the connection between Services Gatekeeper and the application.
Exception raised by submitMultiResponse operation
Warning
Check the connection between Services Gatekeeper and the application.
Exception raised by cancelSmResponse operation.
Warning
Check the connection between Services Gatekeeper and the application.
Exception raised by querySmResponse operation.
Warning
Check the connection between Services Gatekeeper and the application.
Exception raised by replaceSmResponse operation.
Warning
Check the connection between Services Gatekeeper and the application.
Exception raised by deliverSm for MO operation.
Warning
Check the connection between Services Gatekeeper and the application.
Exception raised by bind operation.
Warning
Check the parameters in the bind PDU.
Check the connection between Services Gatekeeper and the SMSC.
Check the SMSC configuration.
Exception raised by submitSm operation.
Warning
Check the connection between Services Gatekeeper and the SMSC.
Exception raised by submitMulti operation.
Warning
Check the connection between Services Gatekeeper and the SMSC.
Exception raised by cancelSm operation.
Warning
Check the message id and source address in the database to verify that the message to be canceled exists.
Check the connection between Services Gatekeeper and the SMSC.
Exception raised by querySm operation.
Warning
Check the message id and source address in the database to verify that the message to be queried exists.
Check the connection between Services Gatekeeper and the SMSC.
Exception raised by replaceSm operation.
Warning
Check the message id and source address in the database to verify that the message to be replaced exists.
Check the connection between Services Gatekeeper and the SMSC.
Exception raised by deliverSmResponse for MO operation.
Warning
Check the connection between Services Gatekeeper and the SMSC.
Exception raised by delivertSmResponse for Delivery Receipt operation.
Warning
Check the connection between Services Gatekeeper and the SMSC.
An exception was thrown when the application attempted to submit a message to the network.
Warning
Check the log for more information.
An exception was thrown when the MMSC attempted to deliver a message using the incorrect .xsd.
Warning
Check the log for more information.
An exception was thrown when the MMSC attempted to deliver a delivery report using the incorrect .xsd.
Warning
Check the log for more information.
An exception was thrown when the MMSC attempted to deliver a read reply report using the incorrect .xsd.
Warning
Check the log for more information.
UCP has received more than 65536 bytes without an end of text (ETX). The "received bytes" buffer is reset to prevent buffer problems in the event that an ETX is never received.
Warning
Informational; if repeated, contact the application owner.
UCP has received more than 65536 bytes without an end of text (ETX). The "received bytes" buffer is reset to prevent buffer problems in the event that an ETX is never received.
Warning
Informational; if repeated, contact the application owner.
UCP is unable to release the TRN for acknowledgment on a client-side connection. This typically means that the request has timed out or that the acknowledgment contained a faulty TRN.
Warning
Informational; if repeated, contact the SMSC support staff.
UCP has received more than 65536 bytes without ETX. The "received bytes" buffer is reset to prevent buffer problems in the event that an ETX is never received..
Warning
Informational; examine data collected from the current context in the alarm.
UCP is unable to send a session management acknowledgment on a server-side connection.
Warning
Informational; examine data collected from the current context in the alarm.
UCP is unable to send a heartbeat acknowledgment on a server-side connection.
Warning
Informational; examine data collected from the current context in the alarm.
UCP is unable to forward to the plug-in an acknowledgment received on a server-side connection.
Warning
Informational; examine data collected from the current context in the alarm.
UCP is unable to forward to the plug-in an acknowledgment received on a server-side connection.
Warning
Informational; examine data collected from the current context in the alarm.
Native UCP encountered an exception processing a network-triggered acknowledgment.
Warning
Check alarms from the UCP Protocol Server Service for details.
Native UCP encountered an exception processing a network-triggered deliverSM request.
Warning
Check alarms from the UCP Protocol Server Service for details.
Native UCP encountered an exception processing a network-triggered deliveryNotification request.
Warning
Check alarms from the UCP Protocol Server Service for details.
Native UCP encountered an exception processing an application-initiated acknowledgment.
Warning
Check alarms from the UCP Protocol Server Service for details.
Native UCP encountered an exception processing an application-initiated submitSM request.
Warning
Check alarms from the UCP Protocol Server Service for details.
Native UCP encountered an exception processing an application-initiated openSession request..
Warning
Check alarms from the UCP Protocol Server Service for details.
The application did not find media to play at the referenced URI. Either the media does not exist, or it exists in a different location.
Major
Create a new media server resource using the Administrator Console.