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.
102001 Geo redundancy service: Site configuration mismatch between sites
There is a site configuration mismatch between sites, sites are present in site-local configuration but not on remote site.
What to do
Create the sites on the remote site.
102002 Geo redundancy service: Site configuration mismatch between sites
There is a site configuration mismatch between sites, sites are present in remote site configuration but not on local site.
What to do
Create the remote sites on the local site.
102801 Alarm raised from policy rule file
An alarm was raised from the policy rule file.
What to do
See log for stacktrace.
102826 Policy service: Application does not exist or is not active
The application does not exist, or is in state inactive.
What to do
Create to application instance if it does not exist. Active the application in it is in state inactive.
102827 Policy service: Unable to get service provider and application information
The service provider or application could not be resolved.
What to do
Make sure that the service provider and application account exists.
102828 Policy service: Service Provider or Application request limit exceeded for service type
The request rate is higher than the rate stated in the Service Level Agreement for the service type.
What to do
Notify the service provider or update the SLA.
102829 Policy service: Service Provider or Application quota limit exceeded for service type
The quota for the service type stated in the Service Level Agreement is exceeded.
What to do
Notify the service provider or update the SLA.
102830 Policy service: All properties denied
Properties passed in by an application are not allowed.
What to do
Notify the service provider of the application behavior.
102831 Policy service: Parameter value is not allowed
The value of a parameter passed in by an application is not allowed.
What to do
Notify the service provider of the application behavior or update the SLA to allow the parameter value.
102832 Policy service: Request info is empty
The RequestInfo object is empty. Cannot proceed with the request.
What to do
Check the logs.
102833 Policy service: Accessing method is not allowed
An application tried to use a method that is not allowed according to the SLA.
What to do
Notify the service provider or update the SLA.
102834 Policy service: Accessing method is not allowed
An application tried to use a method that is not allowed according to the SLA.
What to do
Notify the service provider or update the SLA.
102835 Policy service: Exception thrown calling correlator
A service correlator threw an exception when it was invoked.
What to do
Examine the log files.
102836 Policy service: Exception thrown calling factory
The RequestFactory threw an exception when it was invoked.
What to do
Examine the log files.
102837 Policy service: No global or service provider node SLA found
Could not find a global node or service provider node SLA.
What to do
Update the node SLA.
102838 Policy service: Application or service provider group service contract is out of date
The service contract in the SLA for the service provider group or application group has expired.
What to do
Update the SLA.
102839 Policy service: Application or Service Provider group Service Type contract is out of date
The service contract for the service type in the SLA for the service provider group or application group has expired.
What to do
Update the SLA.
102840 Policy service: No Service Contract found
The service contract for the service type in the SLA for the service provider group or application group could not be found.
What to do
Update the SLA.
102841 Subscriber restrict all
Subscriber SLA defines to deny all request for/from the subscribe.
What to do
No actions required.
102842 Subscriber quota or rate limit reached
The subscriber quota or rate limit has been reached.
What to do
No action required.
102843 Application is not logged in
The application is not logged in.
What to do
Log into application.
102844 Policy Service: Application or Service Provider group Composed Service Contract is out of date
The composed service contract has expired.
What to do
Update the SLA.
102845 Policy Service: Service Provider/Application request limit exceeded for composed service
The request rate is higher than the rate specified in the composed service contract.
What to do
Notify the service provider or update the SLA.
102846 Policy Service: Service Provider/Application quota limit exceeded for composed service
The quota for the composed service contract has been exceeded.
What to do
Notify the service provider or update the SLA.
103001 Geo redundancy service: Configuration mismatch detected between sites
There is configuration mismatch between local and remote sites.
What to do
Compare the accounts and SLAs for the different sites and synchronize them.
103002 Geo redundancy service: Master site failed to replicate a configuration update onto a slave site
Could not replicate a configuration update from the master site to a slave site.
What to do
Check the connection between the sites.
110000 Corba: Servant is already active
Internal exception thrown when performing a Corba operation.
What to do
Send any log with stack trace to Oracle.
110001 Corba: Servant is not active
Internal exception thrown when performing a Corba operation.
What to do
Send any log with stack trace to Oracle.
110002 Corba: Wrong policy
Internal exception thrown when performing a Corba operation.
What to do
Send any log with stack trace to Oracle.
110003 Corba: Object is already active
Internal exception thrown when performing a Corba operation.
What to do
Send any log with stack trace to Oracle.
110004 Corba: Object is not active
Internal exception thrown when performing a Corba operation.
What to do
Send any log with stack trace to Oracle.
110005 Corba: Invalid policy
Internal exception thrown when performing a Corba operation.
What to do
Send any log with stack trace to Oracle.
110006 Corba: Adapter already exists
Internal exception thrown when performing a Corba operation.
What to do
Send any log with stack trace to Oracle.
110007 Corba: Generic CORBA exception
Internal exception thrown when performing a Corba operation.
What to do
Send any log with stack trace to Oracle.
110008 Corba: Exception when handling POA
Internal exception thrown when performing a Corba operation.
What to do
Send any log with stack trace to Oracle.
110100 JMX: NotCompliantMBeanException
Internal exception thrown when an MBean does not comply to the MBean specification.
What to do
Send any log with stack trace to Oracle.
110101 JMX: MalformedObjectNameException
Internal exception thrown when an MBean Object Name is malformed.
What to do
Send any log with stack trace to Oracle.
110102 JMX: MBeanRegistrationException
Internal exception thrown when an MBean fails to register.
What to do
Send any log with stack trace to Oracle.
110103 JMX: InstanceAlreadyExistsException
Internal exception thrown when an instance of an MBean already exists.
What to do
Send any log with stack trace to Oracle.
110104 JMX: InstanceNotFoundException
Internal exception thrown when a requested instance of an MBean does not exist.
What to do
Send any log with stack trace to Oracle.
110105 JMX: Default management error
Internal exception thrown when a management error severity fault happens.
What to do
Send any log with stack trace to Oracle.
110500 Plug-in Manager: Policy Denied exception in Plug-in Manager
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.
What to do
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.
110501 Plug-in Manager: A Plug-in with the same ID is already registered
A plug-in tries to register itself in the plug-in manager but one with that ID has already been registered.
What to do
Contact Oracle with the appropriate log file.
110502 Plug-in Manager: There is no plug-in available for this request
No plug-in appropriate for this request can be found.
What to do
Check that the plug-in is correctly deployed and running. Also make sure that a route exists to this plug-in.
110503 Plug-in Manager: There is no plug-in corresponding to This ID
The Plug-in Manager is asked to return a plug-in corresponding to this ID but none can be found.
What to do
Contact Oracle with the appropriate log file.
110504 Plug-in Manager: Plug-in Manager generic exception
An internal error occurred in the Plug-in Manager causing a generic exception thrown from the Plug-in Manager. The exception message explains the error.
What to do
Send any log with stack trace to Oracle.
110600 Plug-in SMS SMPP: Too many destination addresses in request
The number of destination addresses for the message exceeded the SMPP maximum (254).
What to do
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.
110601 Plug-in SMS SMPP: SMPP message send failure
An error occurred when a short message was sent to the SMSC.
What to do
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.
110602 Plug-in SMS SMPP: Unable to notify SMS reception
Services Gatekeeper was unable to notify the application of a network-initiated message.
What to do
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.
110603 Plug-in SMS SMPP: No matching notification for received SMS
Services Gatekeeper received a network-initiated message for which there was no registered notification.
What to do
Informational only.
Note:
This alarm may be triggered by either the SMS communication service or the binary SMS communication service.
110604 Plug-in SMS SMPP: Unable to notify delivery status
Services Gatekeeper was unable to notify the application of a network message delivery status.
What to do
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.
110605 Plug-in SMS SMPP: Unable to retrieve the notification service
Unable to create the needed service for calls from Services Gatekeeper to the application.
What to do
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.
110606 Failed to send heartbeat to SMSC
Failed to send heartbeat to SMSC.
What to do
Reestablish the connection.
110613 Plug-in SMS SMPP: Partial failure of submit multi request
Some of the multiple destinations to which the message was sent have failed to be delivered. This alarm is sent for each message failure.
What to do
Check the SMSC logs.
Note:
This alarm may be triggered by either the SMS communication service or the binary SMS communication service.
110614 Failed to start SMPP transmitter or receiver connection procedure
Failed to start SMPP transmitter or receiver connection procedure.
What to do
Check the links to the SMSC.
110615 Plug-in SMS SMPP: Segments are missing from the message
Services Gatekeeper has detected that segments from this message are missing.
What to do
Check the logs.
Note:
This alarm may be triggered by either the SMS communication service or the binary SMS communication service.
110616 Failed to bind to SMSC
Failed to bind to SMSC.
What to do
Check the links to the SMSC, and try re-connection.
110617 Connections successfully established with SMSC
Connections successfully established with SMSC.
What to do
No action required.
110618 Connection procedure ended without successful connection to SMSC
Connection procedure ended without successful connection to SMSC.
What to do
Check the links to the SMSC and try re-connection.
110619 Plug-in SMS SMPP: Illegal XParameter value
An illegal XParameter was passed.
What to d
Check the SOAP headers.
Note:
This alarm may be triggered by either the SMS communication service or the binary SMS communication service.
110680 Plug-in SMS SMPP (Binary SMS): Too many segments
Either there is a client error or the binary content is too large for Services Gatekeeper to handle.
What to do
Check the size of the binary content.
110901 Plug-in Presence SIP: Failed to handle a SIP NOTIFY message
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.
What to do
Provide logs with exception stack trace to Oracle.
110902 Plug-in Presence SIP: Failed to invoke client operation: notifySubscription. No retry will be made
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.
What to do
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.
110904 Plug-in Presence SIP: Failed to invoke client operation: makeStatusChangedCallback. No retry will be made
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.
What to do
Verify the client is running at the endpoint specified to receive future notifications.
110907 Plugin Presence SIP: Failed to invoke subscribePresence
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
What to do
Verify the following Presence SIP plug-in configurations in the Administration Console:
Make sure OCCAS is running and in good condition.
110908 Plug-in Presence SIP: Failed to invoke getUserPresence
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
What to do
Verify the client is running at the endpoint specified in the subscription; resubmit the current request after the authorization notification has been received.
110909 Plug-in Presence SIP: Failed to invoke startPresenceNotification
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
What to do
Verify the client is running at the endpoint specified in the subscription; resubmit the current request after the authorization notification has been received.
110910 Plug-in Presence SIP: Failed to invoke endPresenceNotification
An error occurred while the Presence SIP plug-in was processing a startPresenceNotification() request. Possible causes are:
What to do
Verify the database is running. Try to restart Services Gatekeeper. Provide logs with exception stack trace to Oracle.
110918 Plug-in Presence SIP: Failed to start
An internal error occurred when the Presence SIP plug-in was started. It will not function properly unless the underlying problems are corrected.
What to do
Try to restart Services Gatekeeper. Provide logs with exception stack trace to Oracle.
110922 Plug-in Presence SIP: Failed to perform OAM operation
An Oracle Access Manager operation error has occurred. This is most likely due to storage service errors.
What to do
Verify the database is running. Try to restart Services Gatekeeper. Provide logs with exception stack trace to Oracle.
111000 Budget Service: Configuration mismatch between sites
The budget service discovered a site configuration mismatch between geo-redundant sites.
What to do
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.
111001 Budget Service: Shutting down duplicate budget service master
Duplicate geo-redundancy masters were detected. The situation has been corrected.
What to do
Verify network connectivity between geo-redundant sites. This alarm is likely an indication of a previous network split between sites.
111002 Budget Service: Budget master unreachable
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.
What to do
Verify that network connectivity between geo redundant sites is operational and that the remote site is functioning.
111003 Budget Service: New budget master available for service
A new geo-redundancy master has been elected and activated.
What to do
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.
111004 Budget Service: One of the remote sites is unreachable
Services Gatekeeper was unable to reach one of the remote geo-redundant sites.
What to do
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.
111006 Budget Service: There is a budget configuration mismatch between sites. Please look in the log file for more information
A mismatch in budget configuration between geo-redundant sites has been detected.
What to do
Re-sync the slave site manually using the syncFromGeoMaster operation.
111007 Budget Service: Budget value is below 20% of max value
The value of the budget is below 20% of the maximum value.
What to do
Inform the service provider that the request limit is closing or update the SLA.
111100 Storage Service: Exception thrown during store database table entry expiration
An error occurred while the storage service was removing expired entries from the store database table.
What to do
Verify that the database is running and provide logs with exception stack trace to Oracle.
111101 Storage Service: Failed to initialize the Storage Service
An error occurred when the Storage Service was being activated.
What to do
Verify that the database is running and provide logs with exception stack traces to Oracle.
111102 Storage Service: Failed to initialize the cluster cache for the Storage Service
An error occurred when the Storage Service was being activated.
What to do
Verify that the database is running and that there is network connectivity within the cluster. Provide logs with exception stack traces to Oracle.
111103 Storage Service: Failed to perform one or more write behind operations for a Storage Service Store. The request change has been lost
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.
What to do
Verify that the database is running and provide logs with exception stack traces to Oracle.
111104 Storage Service: Storage exception
A generic storage exception was thrown in a communication service.
What to do
Provide logs with exception stack traces to Oracle.
111105 Storage Service: Query result was possibly truncated
The result of a query result was possibly truncated due to maximum query result size limit.
What to do
Provide logs with exception stack traces to Oracle.
111200 Plug-in MLP: MLP Server available
Succeeded in sending a heartbeat to the MLP Server. Plug-in status has been set to active.
What to do
Informational only.
111201 Plug-in MLP: MLP Server unavailable
Failed to send a heartbeat to the MLP Server. Plug-in status has been deactivated.
What to do
Check the MLP server to make sure it is available.
111202 Plug-in MLP: Start failed
The Terminal Location MLP plug-in failed to start.
What to do
Check the log for more information.
111203 Plug-in MLP: Stop failed
The Terminal Location MLP plug-in failed to stop.
What to do
Check the log for more information.
111204 Plug-in MLP: Activate failed
The Terminal Location MLP plug-in was not activated.
What to do
Check the log for more information.
111205 Plug-in MLP: Deactivate failed
The Terminal Location MLP plug-in was not deactivated.
What to do
Check the log for more information.
111206 Plug-in MLP: SendLocation request failed
The attempt to send a location request failed.
What to do
Make sure the MLP server is available. Check the log for more information.
111207 Plug-in MLP: Notify application that Location Notification has ceased failed
Services Gatekeeper was unable to notify the application that location notification has ceased.
What to do
Make sure the AT layer and the notification URL are available. Check the log for more information.
111208 Plug-in MLP: Notify application of a Location Error failed
Services Gatekeeper was unable to notify the application that a location error has occurred.
What to do
Make sure the AT layer and the notification URL are available. Check the log for more information.
111209 Plug-in MLP: Notify application of a Location Notification failed
Services Gatekeeper was unable to notify the application that a location notification has been received.
What to do
Make sure the AT layer and the notification URL are available. Check the log for more information.
111700 Plug-in MM7: Failed to send Multimedia Message
Services Gatekeeper was unable to send a multimedia message to the network.
What to do
Check the log for more information. Common problems: missing/invalid required parameters; configuration problems; storage errors.
111701 Plug-in MM7: Failed to get Multimedia Message Delivery Status
Services Gatekeeper was unable to get delivery status on a multimedia message from the network.
What to do
Check the log for more information. Common problems: invalid request identifier; storage errors.
111702 Plug-in MM7: Failed to poll received new Multimedia Messages
Services Gatekeeper was unable to send the list of received messages to the application.
What to do
Check the log for more information. Common problems: invalid MM7 configuration; storage errors.
111703 Plug-in MM7: Failed to get a Multimedia Message
Services Gatekeeper was unable to send a requested received multimedia message - including attachment - to the application.
What to do
Check the log for more information. Common problems: no attachment found; storage errors.
111704 Plug-in MM7: Failed to send MM7 Messages to network
Services Gatekeeper was unable to send an MM7 message to the network.
What to do
Check the log for more information. Common problems: MM7 Relay Server not ready or misconfigured.
111705 Plug-in MM7: Failed to activate the MM7 Plug-in
Services Gatekeeper was unable to activate the MM7 plug-in.
What to do
Check the log for more information. Common problems: Plug-in not ready; plug-in ID duplicated.
111706 Plug-in MM7: Failed to deactivate the MM7 Plug-in
Services Gatekeeper was unable to deactivate the MM7 plug-in.
What to do
Check the log for more information. Common problems: can't find the plug-in with the ID provided.
111707 Plug-in MM7: Failed to start the MM7 Plug-in
Services Gatekeeper was unable to start the MM7 plug-in.
What to do
Check the log for more information. Common problems: failed to located WorkContextMap; MBean-related exceptions.
111708 Plug-in MM7: Failed to stop the MM7 Plug-in
Services Gatekeeper was unable to stop the MM7 plug-in.
What to do
Check the log for more information. Common problem: MBean-related exceptions.
111709 Plug-in MM7: Failed to notify message reception
Services Gatekeeper was unable to notify the application that a message has been received from the network.
What to do
Check the log for more information. Common problems: no matching NotificationInfo; storage errors; unsupported address type; application not available.
111710 Plug-in MM7: Failed to notify message delivery receipt
Services Gatekeeper was unable to notify the application that a message delivery receipt has been received from the network.
What to do
Check the log for more information. Common problems: no matching messageinfo, recipient number not found; application unavailable.
111711 Plug-in MM7: Application is not available
Services Gatekeeper was unable to contact the application.
What to do
Check the availability of the application.
111712 Plug-in MM7: Recipient Number not found
The delivery acknowledgement does not have a recipient number that matches any of the destination addresses of the sent message. Uncommon.
What to do
Check the log for more information. Common problem: issue between Services Gatekeeper and the MMSC.
111713 Plug-in MM7: No matching MessageInfo found
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.
What to do
Check the log for more information. Common problem: Services Gatekeeper is not configured to request delivery reports but the MMSC is sending them anyway.
111714 Plug-in MM7: Unsupported address type
Services Gatekeeper does not support the address type attached to the multimedia message.
What to do
Check the log for more information and check the address type.
111715 Plug-in MM7: Failed to start message notification
Services Gatekeeper is unable to start message notification.
What to do
Check the log for more information. Common problems: duplicated correlator IDs; storage errors.
111716 Plug-in MM7: Failed to stop message notification
Services Gatekeeper is unable to stop message notification.
What to do
Check the log for more information. Common problems: Correlator ID doesn't exist; storage errors.
111717 Plug-in MM7: No application found for a mobile originated MMS
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.
What to do
Check the log for more information.
111718 Plug-in MM7: MM7 Relay Server responded with an error code
The SubmitResponse returned an error-code.
What to do
Look at the logs to see the specific status code and status text.
113300 Subscriber-centric Policy: Quota limit exceeded for subscriber
The budget quota for a subscriber with limitExceedOK set to true has been exceeded.
What to do
Informational only.
113400 CDR to Diameter: Failed to start the CDR to Diameter module
Services Gatekeeper was unable to start the CDR to Diameter module.
What to do
Check the logs for more information.
113401 CDR to Diameter: Failed to start the CDRDiameter node
Services Gatekeeper was unable to start the CDRDiameter node.
What to do
Check the logs for more information.Check the configuration of the CDR to Diameter module.
113402 CDR to Diameter: Failed to shutdown the CDRDiameter node
Services Gatekeeper failed to shut down the CDRDiameter node.
What to do
Check the logs for more information.
113403 CDR to Diameter: Failed to send Diameter ACR
A general exception occurred when sending Diameter ACR.
What to do
Check the logs for more information.
113404 CDR to Diameter: Failed to send Diameter ACR due to input/output
An input/output exception occurred when sending Diameter ACR.
What to do
Check the logs for more information.
113405 CDR to Diameter: Retrieved error code from Diameter response
The Diameter response contained an error.
What to do
Check logs for more information. The Diameter server might have denied request.
113406 CDR to Diameter: No Diameter connection available
No connection to the Diameter server is available, even though CDR to Diameter module is set to enable.
What to do
Check logs for more information. The Diameter server might be down.
113500 Credit Control Interceptor: Failed to reserve amount by sending INITIAL Diameter CCR
An I/O error occurred during the sending of the INITIAL Diameter CCR.
What to do
Check the logs for more information.
113501 Credit Control Interceptor: Failed to commit reservation amount by sending TERMINATE Diameter CCR
An I/O error occurred during the sending of the TERMINATE Diameter CCR.
What to do
Check the logs for more information.
113502 Credit Control Interceptor: Failed to start the credit control interceptor module
Services Gatekeeper failed to start the credit control interceptor.
What to do
Check the logs for more information.
113503 Credit Control Interceptor: Failed to start the Diameter node
The Diameter node failed to start.
What to do
Check the logs for more information. Check the credit control interceptor module's configuration.
113504 Credit Control Interceptor: Failed to shutdown the Diameter node
The Diameter node failed to shut down.
What to do
Check the logs for more information.
113601 Geo-Redundancy Service: Site Mismatch
A site configuration mismatch has been detected. Sites present in the site-local configuration are not in the remote site configuration.
What to do
Verify that the list of geo-redundant site is identical on all geo-redundant sites of Services Gatekeeper.
113602 Geo-Redundancy Service: Site Mismatch
A site configuration mismatch has been detected. Sites present in the remote site configuration are not in the site-local configuration.
What to do
Verify that the list of geo-redundant sites is identical on all geo-redundant sites of Services Gatekeeper.
113701 Geo-Storage Service: Configuration Mismatch
An account configuration mismatch has been detected. Checksums for one or more stores are different.
What to do
Re-sync the slave site manually using the syncFromGeoMaster operation.
113702 Geo-Storage Service: Failed to replicate a configuration data
The service failed to replicate a configuration update, either master to slave or slave to master.
What to do
Check the logs for more information.
114201 Plug-in Payment/Diameter: Failed to connect to Diameter server
Failed to connect to Diameter server.
What to do
Check configuration of Parlay X 3.0 Payment/Diameter plug-in.
Check the logs for more information.
114202 Failed to disconnect from the diameter server
Failed to disconnect from the diameter server.
What to do
Try to disconnect again.
114203 Failed to charge Amount
Failed to charge Amount.
What to do
Try to charge amount again.
114204 Failed to start AmountReservationTransaction
Failed to start transaction.
What to do
Try to start transaction again.
114205 Failed to update AmountReservationTransaction
Failed to update transaction.
What to do
Try to update transaction again.
114206 Failed to checkTransactionStatus
Failed to check the transaction status.
What to do
Check the OCSG logs for reasons.
114207 Failed to listTransaction
Failed to list the transaction.
What to do
Check the OCSG logs for reasons.
114208 Failed to charge
Failed to charge.
What to do
Check the OCSG logs for reasons.
114209 Plug-in Payment/Diameter: Failed to communicate with Diameter Server
Failed to communicate with Diameter server.
What to do
Check configuration of Parlay X 3.0 Payment/Diameter plug-in.
Disconnect Parlay X 3.0 Payment/Diameter plug-in and reconnect.
Check the logs for more information.
115001 An SLA is about to expire
An SLA is about to expire.
What to do
Check the SLA's valid period.
115002 Problem encountered during SLA expiration check
A problem was encountered during the SLA expiration check.
What to do
Check the SLA's valid period.
118100 Heartbeat Service: Timer expiration ignored, as Heartbeater is sending pings
Because the heartbeat service is sending pings, the expiration of the timer is ignored.
What to do
Informational only.
118101 Heartbeat Service: Heartbeat is alive. Set plug-in status to active
The heartbeat service was able to contact the plug-in.
What to do
Informational only.
118102 Heartbeat Service: Heartbeat failed. Set plug-in status to inactive
The heartbeat service was unable to contact the plug-in.
What to do
Informational only.
119000 Plug-in Third Party Call Parlay MPCC: Failed to start Third Party Call managed plug-in
Services Gatekeeper was unable to start the plug-in.
What to do
Check logs for more information. Possible issues: Services Gatekeeper was unable to locate the WorkContextMap; MBean-related exceptions.
119001 Plug-in Third Party Call Parlay MPCC: Failed to stop Third Party Call managed plug-in
Services Gatekeeper was unable to stop the plug-in.
What to do
Check logs. Possible issues: MBean-related exceptions.
119002 Plug-in Third Party Call Parlay MPCC: Failed to activate Third Party Call managed plug-in
Services Gatekeeper was unable to activate the plug-in.
What to do
Check the log for more information. Possible issues: The plug-in is not ready or there is a duplicated Plug-in ID.
119003 Plug-in Third Party Call Parlay MPCC: Failed to deactivate Third Party Call managed plug-in
Services Gatekeeper was unable to deactivate the plug-in.
What to do
Check the log for more information. Possible issues: Services Gatekeeper is unable to find a plug-in with the given ID.
119004 Plug-in Third Party Call Parlay MPCC: Failed to update call status upon receiving a callEnded event
Services Gatekeeper was unable to update call status.
What to do
Check the log for more information. Make sure the storage service is available.Verify the database is running. Try to restart Services Gatekeeper.
119005 Plug-in Third Party Call Parlay MPCC: Failed to update call status upon receiving a callLegEnded event
Services Gatekeeper was unable to update call status.
What to do
Check the log for more information. Make sure the storage service is available.Verify the database is running. Try to restart Services Gatekeeper.
119006 Plug-in Third Party Call Parlay MPCC: Failed to update call status upon receiving an eventReportRes event
Services Gatekeeper was unable update call status.
What to do
Check the log for more information. Make sure the storage service is available.Verify the database is running. Try to restart Services Gatekeeper.
119007 Plug-in Third Party Call Parlay MPCC: Failed to update call status upon receiving a getInfoRes Event
Services Gatekeeper was unable to update call status.
What to do
Check the log for more information. Make sure the storage service is available.Verify the database is running. Try to restart Services Gatekeeper.
119008 Plug-in Third Party Call Parlay MPCC: Failed to update call status when receiving a getInfoRes event upon IpAppCallLeg interface
Services Gatekeeper was unable to update call status.
What to do
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.
119009 Plug-in Third Party Call Parlay MPCC: Failed to invoke IpMultiPartyCall.getInfoReq() on parlayGW
Services Gatekeeper was unable to invoke IpMultiPartyCall.getInfoReq on the Parlay gateway.
What to do
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.
119010 Plug-in Third Party Call Parlay MPCC: Failed to invoke IpCallLeg.continueProcessing on Parlay gateway
Services Gatekeeper was unable to invoke to invoke IpCallLeg.continueProcessing on Parlay gateway.
What to do
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.
119011 Plug-in Third Party Call Parlay MPCC: Failed to invoke IpMultiPartyCall.createAndRouteCallLeg on Parlay gateway
Services Gatekeeper was unable to invoke IpMultiPartyCall.createAndRouteCallLegReq on Parlay gateway.
What to do
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.
119012 Plug-in Third Party Call Parlay MPCC: Failed to invoke IpMultiPartyCallControlManager.createCall on parlayGW
Services Gatekeeper was unable to invoke IpMultiPartyCallControlManager.createCall on Parlay gateway.
What to do
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.
119013 Plug-in Third Party Call Parlay MPCC: Failed to invoke IpMultiPartyCall.eventReportReq on Parlay gateway
Services Gatekeeper was unable to invoke IpCallLeg.eventReportReq() on the Parlay gateway.
What to do
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.
119014 Plug-in Third Party Call Parlay MPCC: Failed to invoke IpCallLeg.getInfoReq on Parlay gateway
Services Gatekeeper was unable to invoke IpCallLeg.getInfoReq() on Parlay gateway.
What to do
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.
119015 Plug-in Third Party Call Parlay MPCC: Failed to invoke IpMultiPartyCall.release on the Parlay Gateway
Services Gatekeeper was unable to invoke IpMultiPartyCall.release on the Parlay gateway.
What to do
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.
119016 Plug-in Third Party Call Parlay MPCC: Failed to invoke IpCallLeg.routeReq on the Parlay gateway
Services Gatekeeper was unable to invoke IpCallLeg.routeReq on the Parlay gateway.
What to do
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.
119017 Plug-in Third Party Call Parlay MPCC: Failed to invoke IpMultiPartyCall.createCallLeg on the Parlay gateway
Services Gatekeeper was unable to invoke IpMultiPartyCall.createCallLeg on the Parlay gateway.
What to do
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.
120100 Plug-in Parlay X 3.0 Call Notification Parlay MPCC: Failed to start Call Notification managed plug-in
The Parlay MPCC plug-in for the Parlay X 3.0 Call Notification communication service failed to start.
What to do
Check the log for more information.
120101 Plug-in Parlay X 3.0 Call Notification Parlay MPCC: Failed to activate Call Notification managed plug-in
The Parlay MPCC plug-in for the Parlay X 3.0 Call Notification communication service failed to activate.
What to do
Check the log for more information.
120102 Plug-in Parlay X 3.0 Call Notification Parlay MPCC: Failed to stop Call Notification managed plug-in
The Parlay MPCC plug-in for the Parlay X 3.0 Call Notification communication service failed to stop.
What to do
Check the log for more information.
120103 Plug-in Parlay X 3.0 Call Notification Parlay MPCC: Failed to deactivate Call Notification managed plug-in
The Parlay MPCC plug-in for the Parlay X 3.0 Call Notification communication service failed to deactivate.
What to do
Check the log for more information.
120104 Plug-in Parlay X 3.0 Call Notification Parlay MPCC: Failed to deliver notification to application
Services Gatekeeper was unable to deliver a notification to the application.
What to do
Check the log for more information. Make sure the AT layer is available and that the notification URL is correct and available.
120105 Plug-in Parlay X 3.0 Call Notification Parlay MPCC: Failed to deliver recorded message location to application
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.
What to do
Not currently implemented.
120106 Plug-in Parlay X 3.0 Call Notification Parlay MPCC: Failed to deliver collected digits to application
Services Gatekeeper was unable to deliver the digits collected from the end user to the application.
What to do
Check the log for more information. Make sure the AT layer is available and that the notification URL is correct and available.
120107 Plug-in Parlay X 3.0 Call Notification Parlay MPCC: Failed to delete notification in the Parlay gateway
Services Gatekeeper was unable to delete a notification registration in the Parlay gateway.
What to do
Check the log for more information. Make sure the gateway is available. Use Oracle Access Manager methods to make sure the connection is alive.
120108 Plug-in Parlay X 3.0 Call Notification Parlay MPCC: Failed to create notification in the Parlay gateway
Services Gatekeeper was unable to create a notification registration in the Parlay gateway.
What to do
Check the log for more information. Make sure the gateway is available. Use Oracle Access Manager methods to make sure the connection is alive.
120109 Plug-in Parlay X 3.0 Call Notification Parlay MPCC: Failed to set callback for call leg
Services Gatekeeper was unable to set a callback for a call leg in the Parlay Gateway.
What to do
Check the log for more information. Make sure the gateway is available. Use Oracle Access Manager methods to make sure the connection is alive.
120110 Plug-in Parlay X 3.0 Call Notification Parlay MPCC: Failed to continue processing the call leg
Services Gatekeeper was unable to invoke continueProcessing on the Parlay Gateway.
What to do
Check the log for more information. Make sure the gateway is available. Use Oracle Access Manager methods to make sure the connection is alive.
120111 Plug-in Parlay X 3.0 Call Notification Parlay MPCC: Failed to create a call leg
Services Gatekeeper was unable to create a call leg for the call session in the Parlay gateway.
What to do
Check the log for more information. Make sure the gateway is available. Use Oracle Access Manager methods to make sure the connection is alive.
121000 Plug-in Parlay X 3.0 Audio Call Parlay: Failed to start AudioCallManagedPlug-in
Services Gatekeeper was unable to start the plug-in.
What to do
Check the log for more information. Possible issues: unable to location WorkContextMap, MBean related exceptions.
121001 Plug-in Parlay X 3.0 Audio Call Parlay: Failed to activate AudioCallManagedPlug-in
Services Gatekeeper was unable to activate the plug-in.
What to do
Check the log for more information. Possible issues: MBean related exceptions.
121002 Plug-in Parlay X 3.0 Audio Call Parlay: Failed to stop AudioCallManagedPlug-in
Services Gatekeeper was unable to change the state of the plug-in to active.
What to do
Check the log for more information. Possible issues: the plug-in is not ready; there are duplicate plug-in IDs.
121003 Plug-in Parlay X 3.0 Audio Call Parlay: Failed to deactivate AudioCallManagedPlug-in
Services Gatekeeper was unable to change the state of the plug-in to inactive.
What to do
Check the log for more information. Possible issues: the plug-in with the ID specified cannot be found.
121030 Plug-in Parlay X 3.0 Audio Call Parlay: Failed to update UI call status upon receiving sendInfoRes
Services Gatekeeper was unable to update the status of the call.
What to do
Check the log for more information. Make sure that the database and the database connection are active.
121031 Plug-in Parlay X 3.0 Audio Call Parlay: Failed to update UI call status upon receiving sendInfoErr
Services Gatekeeper was unable to update the status of the call.
What to do
Check the log for more information. Make sure that the database and the database connection are active.
121032 Plug-in Parlay X 3.0 Audio Call Parlay: Failed to update UI call status upon receiving sendInfoAndCollectRes
Services Gatekeeper was unable to update the status of the call.
What to do
Check the log for more information. Make sure that the database and the database connection are active.
121033 Plug-in Parlay X 3.0 Audio Call Parlay: Failed to update UI call status upon receiving sendInfoAndCollectErr
Services Gatekeeper was unable to update the status of the call.
What to do
Check the log for more information. Make sure that the database and the database connection are active.
121034 Plug-in Parlay X 3.0 Audio Call Parlay: Failed to update UI call status upon receiving attachMediaRes
Services Gatekeeper was unable to update the status of the call.
What to do
Check the log for more information. Make sure that the database and the database connection are active.
121035 Plug-in Parlay X 3.0 Audio Call Parlay: Failed to update UI call status upon receiving attachMediaErr
Services Gatekeeper was unable to update the status of the call.
What to do
Check the log for more information. Make sure that the database and the database connection are active.
121036 Plug-in Parlay X 3.0 Audio Call Parlay: Failed to update UI call status upon receiving detachMediaRes
Services Gatekeeper was unable to update the status of the call.
What to do
Check the log for more information. Make sure that the database and the database connection are active.
121037 Plug-in Parlay X 3.0 Audio Call Parlay: Failed to update UI call status upon receiving detachMediaErr
Services Gatekeeper was unable to update the status of the call.
What to do
Check the log for more information. Make sure that the database and the database connection are active.
121060 Plug-in Parlay X 3.0 Audio Call Parlay: Failed to invoke IpUIManager.createUICall on Parlay gateway
Services Gatekeeper was unable to invoke a method on the Parlay gateway.
What to do
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.
121061 Plug-in Parlay X 3.0 Audio Call Parlay: Failed to invoke IpUICall.sendInfoReq on Parlay gateway
Services Gatekeeper was unable to invoke a method on the Parlay gateway.
What to do
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.
121062 Plug-in Parlay X 3.0 Audio Call Parlay: Failed to invoke IpUICall.sendInfoAndCollectReq on Parlay gateway
Services Gatekeeper was unable to invoke a method on the Parlay gateway.
What to do
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.
121063 Plug-in Parlay X 3.0 Audio Call Parlay: Failed to invoke IpUICall.release on Parlay gateway
Services Gatekeeper was unable to invoke a method on the Parlay Gateway.
What to do
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.
121064 Plug-in Parlay X 3.0 Audio Call Parlay: Received IpAppUI.sendInfoErr call from Parlay gateway
Services Gatekeeper was received an error message back from the Parlay Gateway.
What to do
Check the log for more information. Possible issues: the provided information (InfoId, InfoData, or InfoAddress) is invalid; improper response by call participant.
121065 Plug-in Parlay X 3.0 Audio Call Parlay: Received IpAppUI.sendInfoAndCollectErr call from Parlay gateway
Services Gatekeeper was received an error message back from the Parlay gateway.
What to do
Check the log for more information. Possible issues: the provided information (InfoId, InfoData, or InfoAddress) is invalid; improper response by call participant.
121066 Plug-in Parlay X 3.0 Audio Call Parlay: Received IpCallLeg.attachMediaErr call from Parlay gateway
Services Gatekeeper was received an error message back from the Parlay gateway.
What to do
Check the log for more information. Possible issues: invalid address or the call was not in a valid state for the requested operation.
121067 Plug-in Parlay X 3.0 Audio Call Parlay: Received IpCallLeg.detachMediaErr call from Parlay gateway
Services Gatekeeper was received an error message back from the Parlay Gateway.
What to do
Check the log for more information. Possible issues: invalid address or the call was not in a valid state for the requested operation.
125101 SOAP to SOAP: Reactivation timer fired
Reactivation timer fired. Setting plug-in status to active.
What to do
Informational only.
125102 SOAP to SOAP: Reactivation timer breached
Reactivation timer breached. Setting plug-in status to inactive.
What to do
Check the connection to the network element.
130100 Plug-in Subscriber Profile LDAP: Failed to start the Subscriber Profile managed plug-in
Services Gatekeeper was unable to start the plug-in.
What to do
Check the log for more information.
130101 Plug-in Subscriber Profile LDAP: Failed to activate the Subscriber Profile managed plug-in
Services Gatekeeper was unable to activate the plug-in.
What to do
Check the log for more information.
130102 Plug-in Subscriber Profile LDAP: Failed to stop the Subscriber Profile managed plug-in
Services Gatekeeper was unable to stop the plug-in.
What to do
Check the log for more information.
130103 Plug-in Subscriber Profile LDAP: Failed to deactivate the Subscriber Profile managed plug-in
Services Gatekeeper was unable to deactivate the plug-in.
What to do
Check the log for more information.
130104 Plug-in Subscriber Profile LDAP: Method call “get” failed
Services Gatekeeper was unable to perform the “get” method call.
What to do
Check the log for more information.
130105 Plug-in Subscriber Profile LDAP: Method call “getProfile” failed
Services Gatekeeper was unable to perform the “getProfile” method call.
What to do
Check the log for more information.
131001 TPC INAP Plug-in: Failed to establish call
Services Gatekeeper was unable to establish a call session.
What to do
Check the log for more information.
131002 TPC INAP Plug-in: Failed to get call information
Services Gatekeeper was unable to retrieve information on a call.
What to do
Check the log for more information.
131003 TPC INAP Plug-in: Failed to end call
Services Gatekeeper was unable to end a call.
What to do
Check the log for more information.
131004 TPC INAP Plug-in: Failed to cancel call request
Services Gatekeeper was unable to cancel a call request.
What to do
Check the log for more information.
131005 TPC INAP Plug-in: Failed to initiate call attempt for first participant toward the network
Services Gatekeeper was unable to initiate a call attempt for the first participant.
What to do
Check the log for more information. Check the plug-in connection to the SS7 stack.
131006 TPC INAP Plug-in: Failed to initiate call attempt for second participant toward the network
Services Gatekeeper was unable to initiate a call attempt for the second participant.
What to do
Check the log for more information. Check the plug-in connection to the SS7 stack.
131007 TPC INAP Plug-in: Failed to continue call processing towards the network
Services Gatekeeper was unable to continue call processing.
What to do
Check the log for more information. Check the plug-in connection to the SS7 stack.
131008 TPC INAP Plug-in: Failed to abruptly terminate an INAP dialog
Services Gatekeeper was unable to terminate an INAP dialog.
What to do
Check the log for more information. Check the plug-in connection to the SS7 stack.
131009 TPC INAP Plug-in: Failed to release a call
Services Gatekeeper was unable to release a call session.
What to do
Check the log for more information. Check the plug-in connection to the SS7 stack.
132100 EWS Push Message Plug-in: Failed to activate PushMessagePlug-inInstance
Services Gatekeeper was unable to activate the plug-in instance.
What to do
Check the log for more information.
132103 EWS Push Message Plug-in: Failed to deactivate PushMessagePluginInstance
Services Gatekeeper was unable to deactivate the plug-in instance.
What to do
Check the log for more information.
132104 EWS Push Message Plug-in: sendPushMessage method failed
Services Gatekeeper was unable to send a push message.
What to do
Check the log for more information.
132105 EWS Push Message Plug-in: sendResultNotificationMessage method failed
Services Gatekeeper was unable to send a result notification message.
What to do
Check the log for more information.
390002 Portal Server: Failed to connect to OCSG
Portal server failed to connect to Services Gatekeeper.
What to do
Check the configuration of the Portal server. Check log for more information.
390003 Portal Server: Failed to connect to the mail server
Portal server failed to connect to the email server.
What to do
Check the configuration of the Portal server and the Email server. Check log for more information.
390004 Portal Server: Got error response from the Analytics server
Portal server received an error response from the Analytics server.
What to do
Check the following:
-
Network connection between the Portal server and the Analytics server
-
Address of the Analytics Server in the System Configuration panel of Partner Manager Portal
-
Whether the Analytics Server is down.
400400 Terminal Status/MAP: Not connected to SS7 stack
Could not connect to the SS7 stack.
What to do
Check the network and try to reinitialize the stack connection using Terminal Server/MAP management operations.
400401 Terminal Status/MAP: Connected to SS7 stack
The Terminal Status/MAP plug-in has connected to the SS7 stack.
What to do
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.
400402 Terminal Status/MAP: Dialog lost, the connection towards at least one of the SS7 backends may be lost
Dialog lost; the connection to at least one of the SS7 stack may be lost.
What to do
Confirm that the SS7 stack process and its network connection are up and running.
400403 Terminal Status/MAP: Received remote user status from the SS7 stack
Received remote user status from the SS7 stack.
What to do
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.
400404 Terminal Status/MAP: Not possible to create the ATI message to the plug-in
It is not possible to create the anyTimeInterrogation message in the Terminal Status/Map plug-in.
What to do
Check the network and try to reinitialize the stack connection using the using Terminal Server/MAP management operations. An exception is also thrown.
400405 Terminal Status/MAP: Not possible to create and send the SS7 API message
The SS7 network could not create (encode) the message.
What to do
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.
400406 Terminal Status/MAP: No answer or a faulty message was received from the SS7 stack
No answer (or a faulty answer) received from the SS7 stack.
What to do
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.
400407 Terminal Status/MAP: Error in the connection towards the SS7 stack
Error in the connection with the SS7 stack.
What to do
The connection with all SS7 backend instances has been lost. The Terminal Status/MAP plug-in tries to reconnect.
400500 SMPP Server Service: Server port started
A server port has started.
What to do
Informational.
400501 SMPP Server Service: Server port stopped
A server port has stopped.
What to do
Informational.
400502 SMPP Server Service: Server connection established
A server connection has been established.
What to do
Informational.
400503 SMPP Server Service: Server connection closed
A server connection has closed.
What to do
Check the connections between Services Gatekeeper and the SMSC and applications.
400504 SMPP Server Service: Client connection established
A client connection has been established.
What to do
Informational.
400505 SMPP Server Service: Client connection closed
A client connection has closed.
What to do
Check the connections between Services Gatekeeper and the SMSC and applications.
400506 SMPP Server Service: Client connection reset
All client connections to this server service have been reset.
What to do
Informational.
400507 SMPP Server Service: Client connection reconnect failed
A client connection re-connection attempt has failed.
What to do
Check the connection between Services Gatekeeper and the SMSC.
400508 SMPP Server Service: ChannelProcessor PeerConnectionIds Empty
ChannelProcessor PeerConnectionIds are empty while connection-based routing is enabled.
The connection will be closed.
What to do
Check the connections between Services Gatekeeper and the SMSC and applications.
400509 SMPP Server Service: NorthChannelProcessor PeerPluginInstanceIds Empty
Application-facing ChannelProcessor PeerPluginInstanceIds are empty while connection-based routing is disabled.
The server connection will be closed.
What to do
Check the connections between Services Gatekeeper and the SMSC and applications.
400510 SMPP Server Service: PluginInstanceInfo ClientConnectionIds Empty
PluginInstanceInfo ClientConnectionIds are empty while connection-based routing is disabled.
The status of the plug-in instance is UNBIND.
What to do
Check the connections between Services Gatekeeper and the SMSC and applications.
400511 SMPP Server Service: PluginInstanceInfo ServerConnectionIds Empty
PluginInstanceInfo ServerConnectionIds are empty while connection-based routing is disabled.
All client connections to the plug-in will be closed.
What to do
Check the connections between Services Gatekeeper and the SMSC and applications.
400512 SMPP Server Service: MO Request Failed
Mobile-originated request failed because of an invalid local server connection with MO jumping disabled.
What to do
Check the address range configuration in the ApplicationSpecificSettings. See the "listApplicationSpecificSettings" operation in Oracle Communications Services Gatekeeper System Administrator's Guide, another document in this set.
Also check the connections between Services Gatekeeper and the SMSC and applications.
400513 SMPP Server Service: MT Request Failed
Mobile-terminated request failed because of an invalid local client connection.
What to do
Check the connections between Services Gatekeeper and the SMSC and applications.
400600 Native SMPP: Exception when processing a submitSmResponse in the plug-in
Exception raised by submitSmResponse operation.
What to do
Check the connection between Services Gatekeeper and the application.
400601 Native SMPP: Exception when processing a submitMultiResponse in the plug-in
Exception raised by submitMultiResponse operation.
What to do
Check the connection between Services Gatekeeper and the application.
400602 Native SMPP: Exception when processing a cancelSmResponse in the plug-in
Exception raised by cancelSmResponse operation.
What to do
Check the connection between Services Gatekeeper and the application.
400603 Native SMPP: Exception when processing a querySmResponse in the plug-in
Exception raised by querySmResponse operation.
What to do
Check the connection between Services Gatekeeper and the application.
400604 Native SMPP: Exception when processing a replaceSmResponse in the plug-in
Exception raised by replaceSmResponse operation.
What to do
Check the connection between Services Gatekeeper and the application.
400605 Native SMPP: Exception when processing a deliverSm for MO
Exception raised by deliverSm for MO operation.
What to do
Check the connection between Services Gatekeeper and the application.
400610 Native SMPP: Exception when processing a bind in the plug-in
Exception raised by bind operation.
What to do
Check the parameters in the bind PDU.
Check the connection between Services Gatekeeper and the SMSC.
Check the SMSC configuration.
400611 Native SMPP: Exception when processing a submitSm in the plug-in
Exception raised by submitSm operation.
What to do
Check the connection between Services Gatekeeper and the SMSC.
400612 Native SMPP: Exception when processing a submitMulti in the plug-in
Exception raised by submitMulti operation.
What to do
Check the connection between Services Gatekeeper and the SMSC.
400613 Native SMPP: Exception when processing a cancelSm in the plug-in
Exception raised by cancelSm operation.
What to do
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.
400614 Native SMPP: Exception when processing a querySm in the plug-in
Exception raised by querySm operation.
What to do
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.
400615 Native SMPP: Exception when processing a replaceSm in the plug-in
Exception raised by replaceSm operation.
What to do
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.
400616 Native SMPP: Exception when processing a deliverSmResponse for MO in the plug-in
Exception raised by deliverSmResponse for MO operation.
What to do
Check the connection between Services Gatekeeper and the SMSC.
400617 Native SMPP: Exception when processing a deliverSmResponse for DeliveryReceipt in the plug-in
Exception raised by delivertSmResponse for Delivery Receipt operation.
What to do
Check the connection between Services Gatekeeper and the SMSC.
401050 Native MM7 Plug-in: Exception thrown on submit request
An exception was thrown when the application attempted to submit a message to the network.
What to do
Check the log for more information.
401051 Native MM7 Plug-in: Exception thrown when the MMSC tried to deliver a network-triggered message using the incorrect xsd version
An exception was thrown when the MMSC attempted to deliver a message using the incorrect .xsd.
What to do
Check the log for more information.
401052 Native MM7 Plug-in: Exception thrown when the MMSC tried to deliver a delivery report using the incorrect xsd version
An exception was thrown when the MMSC attempted to deliver a delivery report using the incorrect .xsd.
What to do
Check the log for more information.
401053 Native MM7 Plug-in: Exception thrown when the MMSC tried to deliver a read reply report using the incorrect xsd version
An exception was thrown when the MMSC attempted to deliver a read reply report using the incorrect .xsd.
What to do
Check the log for more information.
400200 Native UCP Protocol Server Service [tryBuildPDU]: Data was thrown away because no terminating ETX was received
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.
What to do
Informational; if repeated, contact the application owner.
400201 Native UCP Protocol Server Service [handleAckNackOnServerSide]: Unable to release TRN for ack/nack received on a server side connection
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.
What to do
Informational; if repeated, contact the application owner.
400202 Native UCP Protocol Server Service [handleAckNackOnClientSide]: Unable to release TRN for ack/nack received on a client side connection
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.
What to do
Informational; if repeated, contact the SMSC support staff.
400203 Native UCP Protocol Server Service [Unable to send a nack]: Data was thrown away because no terminating ETX was received
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.
What to do
Informational; examine data collected from the current context in the alarm.
400204 Native UCP Protocol Server Service [sendSessionMgmtAck]: Unable to send ack on a session management, open session operation
UCP is unable to send a session management acknowledgment on a server-side connection.
What to do
Informational; examine data collected from the current context in the alarm.
400205 Native UCP Protocol Server Service [sendHeartbeatAck]: Unable to send ack on a heartbeat request on a server side connection
UCP is unable to send a heartbeat acknowledgment on a server-side connection.
What to do
Informational; examine data collected from the current context in the alarm.
400206 Native UCP Protocol Server Service [deliverServerSideAckNackPDUToPlugin]: Unable to call the plug-in north interface with ack/nack
UCP is unable to forward to the plug-in an acknowledgment received on a server-side connection.
What to do
Informational; examine data collected from the current context in the alarm.
400207 Native UCP Protocol Server Service [deliverClientSideAckNackPDUToPlugin]: Unable to call the plug-in south interface with ack/nack
UCP is unable to forward to the plug-in an acknowledgment received on a server-side connection.
What to do
Informational; examine data collected from the current context in the alarm.
400300 Native UCP SMS Plug-in [handleAckNack]: Exception when processing an MO ack/nack request in the plug-in
Native UCP encountered an exception processing a network-triggered acknowledgment.
What to do
Check alarms from the UCP Protocol Server Service for details.
400301 Native UCP SMS Plug-in [deliverSM]: Exception when processing an MO deliver SM request in the plug-in
Native UCP encountered an exception processing a network-triggered deliverSM request.
What to do
Check alarms from the UCP Protocol Server Service for details.
400302 Native UCP SMS Plug-in [deliveryNotification]: Exception when processing an MO delivery notification request in the plug-in
Native UCP encountered an exception processing a network-triggered deliveryNotification request.
What to do
Check alarms from the UCP Protocol Server Service for details.
400310 Native UCP SMS Plug-in [handleAckNack]: Exception when processing an MT ack/nack request in the plug-in
Native UCP encountered an exception processing an application-initiated acknowledgment.
What to do
Check alarms from the UCP Protocol Server Service for details.
400311 Native UCP SMS Plug-in [submitSM]: Exception when processing an MT submit SM in the plug-in
Native UCP encountered an exception processing an application-initiated submitSM request.
What to do
Check alarms from the UCP Protocol Server Service for details.
400312 Native UCP SMS Plug-in [openSession]: Exception when processing an MT openSession request in the plug-in
Native UCP encountered an exception processing an application-initiated openSession request.
What to do
Check alarms from the UCP Protocol Server Service for details.
406010 Audio Call/SIP: Media server resource not found
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.
What to do
Create a new media server resource using the Administrator Console.
88800001 Failed to execute Group Manager APIs
Group management default exception.
What to do
Check logs for more details.
88800002 Failed to execute Group APIs
Group default exception.
What to do
Check logs for more details.
88800003 Failed to execute Member APIs
Member default exception.
What to do
Check logs for more details.
981001 Failed to get email message delivery status
There was a failure in receiving the delivery status of a message sent to the email server.
What to do
Check the log for more information. Verify the request identifier and check for storage errors.
981002 Failed to poll received new mail
There was a failure to poll to receive the new mail.
What to do
Check the log for more information. Verify the registration identifier and check for storage errors.
981003 Failed to poll received email content
There was a failure to get the content of mail received.
What to do
Check the log for more information. Verify that there was an attachment and check for storage errors.
981004 Failed to send email messages to email server
There was a failure to send messages to the email server.
What to do
Check the log for more information. Verify that the email server is ready and correctly configured.
981005 Failed to deliver received email notification
There was a failure to deliver a notification on the email received.
What to do
Check the log for more information. Verify that the address type is supported and check for storage errors.
981006 Failure to deliver email delivery receipt
There was a failure to deliver the delivery receipt for an email.
What to do
Check the log for more information. Verify that there is matching message information, the recipient number exists, and the application is available.
981007 Failed to start email message notification
There was a failure to start email message notification.
What to do
Check the log for more information. Verify that the correlator used to identify the notification is unique and check for storage errors.
981007 Failed to start email message notification
There was a failure to start email message notification.
What to do
Check the log for more information. Verify that the correlator used to identify the notification is unique and check for storage errors.
981008 Failed to stop email message notification
There was a failure to stop the notification for an email message.
What to do
Check the log for more information. Verify that the correlator used to identify the notification exists and check for storage errors.
981009 Failed to connect to email server(SMTP)
There was a failure to connect to the email service through SMTP.
What to do
Check the log for more information. Verify that the email (SMTP) server is ready and correctly configured.
981010 Failed to connect to email server(IMAP)
There was a failure to connect to the email service through IMAP.
What to do
Check the log for more information. Verify that the email (IMAP) server is ready and correctly configured.
199900 Default: Default exception
A generic exception was thrown in a communication service.
What to do
Provide logs with exception stack traces to Oracle.
981011 Failed to connect to email server(POP3)
There was a failure to connect to the email service through POP3.
What to do
Check the log for more information. Verify that the email (POP3) server is ready and correctly configured.
98000001 Failed to connect to the diameter server
There was a failure to connect to the diameter server.
What to do
Try again. Check whether the parameters used to connect to diameter server was set up correctly, like “host,” ”port,” ”realm,”etc.
98000002 Failed to apply QoS
There was a failure to apply QoS.
What to do
Try again. Check whether the parameters of the request conform to the requirement of server.
98000003 Failed to get QoS status
There was a failure to get QoS status.
What to do
Try again. Check whether the request id returned with apply QoS request had been set correctly.
98000004 Failed to modify QoS
There was a failure to modify QoS.
What to do
Try again. Check whether the parameters of the request conform to the requirement of server and whether the request id returned with apply QoS request had been set correctly.
98000005 Failed to remove QoS
There was a failure to remove QoS.
What to do
Try again. Check whether the request id returned with apply QoS request had been set correctly.
98000006 Error on QoS expire
There was an error on QoS expire.
What to do
No action required.
98000007 Failed to register QoS notification
There was a failure to register QoS notification.
What to do
Try again. Make sure the parameters of the request not null, and no duplicate correlator or overlapping criteria.
98000008 Failed to unregister QoS notification
There was a failure to unregister QoS notification.
What to do
Try again. Make sure the correlator was not null and was registered.
98000009 Failed to disconnect to the diameter server
There was a failure to disconnect to the diameter server.
What to do
No action required.
