Contents

Title and Copyright Information

Preface

• Audience
• Documentation Accessibility
• Related Documents

1 Handling Alarms

• Interpreting alarms
• Alarm numbering overview
  • 2.2 Style (Legacy) Alarms
    • Protocol plug-in
    • Policy
    • SLEE
  • 3.0 Style (Current) Alarms

2 Resolving 2.2 Style Alarms

• 103827/1034 SLEE: Transaction limit violated
• 103833/1035 SLEE: Transaction limit reached 95% of the allowed value
• 103900/1100 SLEE charging: Charging data storage failed
• 103901/1101 SLEE charging: Charging service initialization failed
• 103902/1102 SLEE charging: Charging table creation failed
• 104000/1600 SLEE EDR service: 2.2 Listener execution time exceeded
• 104001/1601 SLEE EDR service: 2.2 style EDR listener removed
• 104100/7001 SLEE statistics: Failed to store statistics data
• 102700/22000 Plug-in OSA access: OSA gateway authentication failed
• 102701/22001 Plug-in OSA access: OSA gateway service manager unreachable
• 102702/22002 Plug-in OSA access: OSA gateway unreachable
• 102703/22003 Plug-in OSA access: No mapping available
• 102704/22004 Plug-in OSA access: Internal error when handling event
• 102800/3002 Policy service: Parsing of service-specific rule file failed
• 3003 Policy service: Various Policy Denials
• 102802/3005 Policy service: Request denied
• 102803/3006 Policy service: Runtime exception in policy rule
• 102804/3007 Service Provider Group SLA Added
• 102805/3008 Service Provider Group SLA Deleted
• 102806/3009 Service Provider Group SLA Updated
• 102807/3010 Application Group SLA Added
• 102808/3011 Policy service: Application Group SLA deleted
• 102810/3013 Policy service: Node SP SLA added
• 102811/3014 Policy service: Node SP SLA deleted
• 102812/3015 Policy service: Node SP SLA updated
• 102813/3016 Policy service: Node SLA added
• 102814/3017 Policy service: Node SLA deleted
• 102815/3018 Policy service: Node SLA updated when raised by Policy. Fail to find transaction number when raised by ESPA_messaging
• 102816/3019 Policy service: Application rules updated
• 102817/3020 Policy service: Node rules updated
• 102818/3021 Policy service: Service Provider rules updated
• 102819/3022 Policy service: Application rules deleted
• 102820/3023 Policy service: Node rules deleted
• 102821/3024 Policy service: Service Provider rules deleted
• 102822/3025 Policy service: Service Provider/Application quota limit exceeded
• 102823/3026 Policy service: Service Provider/Application request limit exceeded
• 102824/3027 Policy service: Global/SP NODE request limit exceeded
• 102825/3028 Policy service: Global or SP node service contract is missing or out of date

3 Resolving 3.0 and Higher Style Alarms

• 102001 Geo redundancy service: Site configuration mismatch between sites
• 102002 Geo redundancy service: Site configuration mismatch between sites
• 102826 Policy service: Application does not exist or is not active
• 102827 Policy service: Unable to get service provider and application information
• 102828 Policy service: Service Provider or Application request limit exceeded for service type
• 102829 Policy service: Service Provider or Application quota limit exceeded for service type
• 102830 Policy service: All properties denied
• 102831 Policy service: Parameter value is not allowed
• 102832 Policy service: Request info is empty
• 102833 Policy service: Accessing method is not allowed
• 102834 Policy service: Accessing method is not allowed
• 102835 Policy service: Exception thrown calling correlator
• 102836 Policy service: Exception thrown calling factory
• 102837 Policy service: No global or service provider node SLA found
• 102838 Policy service: Application or service provider group service contract is out of date
• 102839 Policy service: Application or Service Provider group Service Type contract is out of date
• 102840 Policy service: No Service Contract found
• 102844 Policy Service: Application or Service Provider group Composed Service Contract is out of date
• 102845 Policy Service: Service Provider/Application request limit exceeded for composed service.
• 102846 Policy Service: Service Provider/Application quota limit exceeded for composed service
• 103001 Geo redundancy service: Configuration mismatch detected between sites
• 103002 Geo redundancy service: Master site failed to replicate a configuration update onto a slave site
• 110000 Corba: Servant is already active
• 110001 Corba: Servant is not active
• 110002 Corba: Wrong policy
• 110003 Corba: Object is already active
• 110004 Corba: Object is not active
• 110005 Corba: Invalid policy
• 110006 Corba: Adapter already exists
• 110007 Corba: Generic CORBA exception
• 110008 Corba: Exception when handling POA
• 110100 JMX: NotCompliantMBeanException
• 110101 JMX: MalformedObjectNameException
• 110102 JMX: MBeanRegistrationException
• 110103 JMX: InstanceAlreadyExistsException.
• 110104 JMX: InstanceNotFoundException
• 110105 JMX: Default management error
• 110500 Plug-in Manager: Policy Denied exception in Plug-in Manager
• 110501 Plugin-in Manager: A Plugin-in with the same ID is already registered
• 110502 Plugin-in Manager: There is no plugin-in available for this request
• 110503 Plugin-in Manager: There is no plugin-in corresponding to This ID
• 110504 Plugin-in Manager: Plugin-in Manager generic exception
• 110600 Plugin-in SMS SMPP: Too many destination addresses in request
• 110601 Plugin-in SMS SMPP: SMPP message send failure
• 110602 Plugin-in SMS SMPP: Unable to notify SMS reception
• 110603 Plugin-in SMS SMPP: No matching notification for received SMS
• 110604 Plugin-in SMS SMPP: Unable to notify delivery status
• 110605 Plugin-in SMS SMPP: Unable to retrieve the notification service
• 110613 Plugin-in SMS SMPP: Partial failure of submit multi request
• 110615 Plugin-in SMS SMPP: Segments are missing from the message
• 110619 Plug-in SMS SMPP: Illegal XParameter value
• 110680 Plugin-in SMS SMPP (Binary SMS): Too many segments
• 110901 Plugin-in Presence SIP: Failed to handle a SIP NOTIFY message
• 110902 Plugin-in Presence SIP: Failed to invoke client operation: notifySubscription. No retry will be made
• 110904 Plugin-in Presence SIP: Failed to invoke client operation: makeStatusChangedCallback. No retry will be made
• 110907 Plugin Presence SIP: Failed to invoke subscribePresence
• 110908 Plugin-in Presence SIP: Failed to invoke getUserPresence
• 110909 Plugin-in Presence SIP: Failed to invoke startPresenceNotification
• 110910 Plugin-in Presence SIP: Failed to invoke endPresenceNotification
• 110918 Plugin-in Presence SIP: Failed to start
• 110922 Plugin-in Presence SIP: Failed to perform OAM operation
• 111000 Budget Service: Configuration mismatch between sites
• 111001 Budget Service: Shutting down duplicate budget service master
• 111002 Budget Service: Budget master unreachable
• 111003 Budget Service: New budget master available for service
• 111004 Budget Service: One of the remote sites is unreachable
• 111006 Budget Service: There is a budget configuration mismatch between sites. Please look in the log file for more information
• 111007 Budget Service: Budget value is below 20% of max value
• 111100 Storage Service: Exception thrown during store database table entry expiration
• 111101 Storage Service: Failed to initialize the Storage Service
• 111102 Storage Service: Failed to initialize the cluster cache for the Storage Service
• 111103 Storage Service: Failed to perform one or more write behind operations for a Storage Service Store. The request change has been lost.
• 111104 Storage Service: Storage exception
• 111105 Storage Service: Query result was possibly truncated
• 111200 Plugin-in MLP: MLP Server available
• 111201 Plugin-in MLP: MLP Server unavailable
• 111202 Plugin-in MLP: Start failed
• 111203 Plugin-in MLP: Stop failed
• 111204 Plugin-in MLP: Activate failed
• 111205 Plugin-in MLP: Deactivate failed
• 111206 Plugin-in MLP: SendLocation request failed
• 111207 Plugin-in MLP: Notify application that Location Notification has ceased failed
• 111208 Plugin-in MLP: Notify application of a Location Error failed
• 111209 Plugin-in MLP: Notify application of a Location Notification failed
• 111700 Plugin-in MM7: Failed to send Multimedia Message
• 111701 Plugin-in MM7: Failed to get Multimedia Message Delivery Status
• 111702 Plugin-in MM7: Failed to poll received new Multimedia Messages
• 111703 Plugin-in MM7: Failed to get a Multimedia Message
• 111704 Plugin-in MM7: Failed to send MM7 Messages to network
• 111705 Plugin-in MM7: Failed to activate the MM7 Plugin-in
• 111706 Plugin-in MM7: Failed to deactivate the MM7 Plugin-in
• 111707 Plugin-in MM7: Failed to start the MM7 Plugin-in
• 111708 Plugin-in MM7: Failed to stop the MM7 Plugin-in
• 111709 Plugin-in MM7: Failed to notify message reception
• 111710 Plugin-in MM7: Failed to notify message delivery receipt
• 111711 Plugin-in MM7: Application is not available
• 111712 Plugin-in MM7: Recipient Number not found
• 111713 Plugin-in MM7: No matching MessageInfo found
• 111714 Plugin-in MM7: Unsupported address type
• 111715 Plugin-in MM7: Failed to start message notification
• 111716 Plugin-in MM7: Failed to stop message notification
• 111717 Plugin-in MM7: No application found for a mobile originated MMS
• 111718 Plugin-in MM7: MM7 Relay Server responded with an error code
• 113300 Subscriber-centric Policy: Quota limit exceeded for subscriber
• 113400 CDR to Diameter: Failed to start the CDR to Diameter module
• 113401 CDR to Diameter: Failed to start the CDRDiameter node
• 113402 CDR to Diameter: Failed to shutdown the CDRDiameter node
• 113403 CDR to Diameter: Failed to send Diameter ACR
• 113404 CDR to Diameter: Failed to send Diameter ACR due to input/output
• 113405 CDR to Diameter: Retrieved error code from Diameter response
• 113406 CDR to Diameter: No Diameter connection available
• 113500 Credit Control Interceptor: Failed to reserve amount by sending INITIAL Diameter CCR
• 113501 Credit Control Interceptor: Failed to commit reservation amount by sending TERMINATE Diameter CCR
• 113502 Credit Control Interceptor: Failed to start the credit control interceptor module
• 113503 Credit Control Interceptor: Failed to start the Diameter node
• 113504 Credit Control Interceptor: Failed to shutdown the Diameter node
• 113601 Geo-Redundancy Service: Site Mismatch
• 113602 Geo-Redundancy Service: Site Mismatch
• 113701 Geo-Storage Service: Configuration Mismatch
• 113702 Geo-Storage Service: Failed to replicate a configuration data
• 114201 Plug-in Payment/Diameter: Failed to connect to Diameter server
• 114202 Plug-in Payment/Diameter: Failed to disconnect from Diameter server
• 118100 Heartbeat Service: Timer expiration ignored, as Heartbeater is sending pings
• 118101 Heartbeat Service: Heartbeat is alive. Set plugin-in status to active
• 118102 Heartbeat Service: Heartbeat failed. Set plugin-in status to inactive
• 119000 Plugin-in Third Party Call Parlay MPCC: Failed to start Third Party Call managed plugin-in
• 119001 Plugin-in Third Party Call Parlay MPCC: Failed to stop Third Party Call managed plugin-in
• 119002 Plugin-in Third Party Call Parlay MPCC: Failed to activate Third Party Call managed plugin-in
• 119003 Plugin-in Third Party Call Parlay MPCC: Failed to deactivate Third Party Call managed plugin-in
• 119004 Plugin-in Third Party Call Parlay MPCC: Failed to update call status upon receiving a callEnded event
• 119005 Plugin-in Third Party Call Parlay MPCC: Failed to update call status upon receiving a callLegEnded event
• 119006 Plugin-in Third Party Call Parlay MPCC: Failed to update call status upon receiving an eventReportRes event
• 119007 Plugin-in Third Party Call Parlay MPCC: Failed to update call status upon receiving a getInfoRes Event
• 119008 Plugin-in Third Party Call Parlay MPCC: Failed to update call status when receiving a getInfoRes event upon IpAppCallLeg interface
• 119009 Plugin-in Third Party Call Parlay MPCC: Failed to invoke IpMultiPartyCall.getInfoReq() on parlayGW
• 119010 Plugin-in Third Party Call Parlay MPCC: Failed to invoke IpCallLeg.continueProcessing on Parlay gateway
• 119011 Plugin-in Third Party Call Parlay MPCC: Failed to invoke IpMultiPartyCall.createAndRouteCallLeg on Parlay gateway
• 119012 Plugin-in Third Party Call Parlay MPCC: Failed to invoke IpMultiPartyCallControlManager.createCall on parlayGW
• 119013 Plugin-in Third Party Call Parlay MPCC: Failed to invoke IpMultiPartyCall.eventReportReq on Parlay gateway
• 119014 Plugin-in Third Party Call Parlay MPCC: Failed to invoke IpCallLeg.getInfoReq on Parlay gateway
• 119015 Plugin-in Third Party Call Parlay MPCC: Failed to invoke IpMultiPartyCall.release on the Parlay Gateway
• 119016 Plugin-in Third Party Call Parlay MPCC: Failed to invoke IpCallLeg.routeReq on the Parlay gateway
• 119017 Plugin-in Third Party Call Parlay MPCC: Failed to invoke IpMultiPartyCall.createCallLeg on the Parlay gateway
• 120100 Plugin-in Parlay X 3.0 Call Notification Parlay MPCC: Failed to start Call Notification managed plugin-in
• 120101 Plugin-in Parlay X 3.0 Call Notification Parlay MPCC: Failed to activate Call Notification managed plugin-in
• 120102 Plugin-in Parlay X 3.0 Call Notification Parlay MPCC: Failed to stop Call Notification managed plugin-in
• 120103 Plugin-in Parlay X 3.0 Call Notification Parlay MPCC: Failed to deactivate Call Notification managed plugin-in
• 120104 Plugin-in Parlay X 3.0 Call Notification Parlay MPCC: Failed to deliver notification to application
• 120105 Plugin-in Parlay X 3.0 Call Notification Parlay MPCC: Failed to deliver recorded message location to application
• 120106 Plugin-in Parlay X 3.0 Call Notification Parlay MPCC: Failed to deliver collected digits to application
• 120107 Plugin-in Parlay X 3.0 Call Notification Parlay MPCC: Failed to delete notification in the Parlay gateway
• 120108 Plugin-in Parlay X 3.0 Call Notification Parlay MPCC: Failed to create notification in the Parlay gateway
• 120109 Plugin-in Parlay X 3.0 Call Notification Parlay MPCC: Failed to set callback for call leg
• 120110 Plugin-in Parlay X 3.0 Call Notification Parlay MPCC: Failed to continue processing the call leg
• 120111 Plugin-in Parlay X 3.0 Call Notification Parlay MPCC: Failed to create a call leg
• 121000 Plugin-in Parlay X 3.0 Audio Call Parlay: Failed to start AudioCallManagedPlugin-in
• 121001 Plugin-in Parlay X 3.0 Audio Call Parlay: Failed to activate AudioCallManagedPlugin-in
• 121002 Plugin-in Parlay X 3.0 Audio Call Parlay: Failed to stop AudioCallManagedPlugin-in
• 121003 Plugin-in Parlay X 3.0 Audio Call Parlay: Failed to deactivate AudioCallManagedPlugin-in
• 121030 Plugin-in Parlay X 3.0 Audio Call Parlay: Failed to update UI call status upon receiving sendInfoRes
• 121031 Plugin-in Parlay X 3.0 Audio Call Parlay: Failed to update UI call status upon receiving sendInfoErr
• 121032 Plugin-in Parlay X 3.0 Audio Call Parlay: Failed to update UI call status upon receiving sendInfoAndCollectRes
• 121033 Plugin-in Parlay X 3.0 Audio Call Parlay: Failed to update UI call status upon receiving sendInfoAndCollectErr
• 121034 Plugin-in Parlay X 3.0 Audio Call Parlay: Failed to update UI call status upon receiving attachMediaRes
• 121035 Plugin-in Parlay X 3.0 Audio Call Parlay: Failed to update UI call status upon receiving attachMediaErr
• 121036 Plugin-in Parlay X 3.0 Audio Call Parlay: Failed to update UI call status upon receiving detachMediaRes
• 121037 Plugin-in Parlay X 3.0 Audio Call Parlay: Failed to update UI call status upon receiving detachMediaErr
• 121060 Plugin-in Parlay X 3.0 Audio Call Parlay: Failed to invoke IpUIManager.createUICall on Parlay gateway
• 121061 Plugin-in Parlay X 3.0 Audio Call Parlay: Failed to invoke IpUICall.sendInfoReq on Parlay gateway
• 121062 Plugin-in Parlay X 3.0 Audio Call Parlay: Failed to invoke IpUICall.sendInfoAndCollectReq on Parlay gateway
• 121063 Plugin-in Parlay X 3.0 Audio Call Parlay: Failed to invoke IpUICall.release on Parlay gateway
• 121064 Plugin-in Parlay X 3.0 Audio Call Parlay: Received IpAppUI.sendInfoErr call from Parlay gateway
• 121065 Plugin-in Parlay X 3.0 Audio Call Parlay: Received IpAppUI.sendInfoAndCollectErr call from Parlay gateway
• 121066 Plugin-in Parlay X 3.0 Audio Call Parlay: Received IpCallLeg.attachMediaErr call from Parlay gateway
• 121067 Plugin-in Parlay X 3.0 Audio Call Parlay: Received IpCallLeg.detachMediaErr call from Parlay gateway
• 125101 SOAP to SOAP: Reactivation timer fired
• 125102 SOAP to SOAP: Reactivation timer breached
• 130100 Plugin-in Subscriber Profile LDAP: Failed to start the Subscriber Profile managed plug-in
• 130101 Plugin-in Subscriber Profile LDAP: Failed to activate the Subscriber Profile managed plug-in
• 130102 Plugin-in Subscriber Profile LDAP: Failed to stop the Subscriber Profile managed plug-in
• 130103 Plugin-in Subscriber Profile LDAP: Failed to deactivate the Subscriber Profile managed plug-in
• 130104 Plugin-in Subscriber Profile LDAP: Method call “get” failed
• 130105 Plugin-in Subscriber Profile LDAP: Method call “getProfile” failed
• 131001 TPC INAP Plug-in: Failed to establish call
• 131002 TPC INAP Plug-in: Failed to get call information
• 131003 TPC INAP Plug-in: Failed to end call
• 131004 TPC INAP Plug-in: Failed to cancel call request
• 131005 TPC INAP Plug-in: Failed to initiate call attempt for first participant toward the network
• 131006 TPC INAP Plug-in: Failed to initiate call attempt for second participant toward the network
• 131007 TPC INAP Plug-in: Failed to continue call processing towards the network
• 131008 TPC INAP Plug-in: Failed to abruptly terminate an INAP dialog
• 131009 TPC INAP Plug-in: Failed to release a call
• 132100 EWS Push Message Plug-in: Failed to activate PushMessagePlugin-inInstance
• 132103 EWS Push Message Plug-in: Failed to deactivate PushMessagePluginInstance
• 132104 EWS Push Message Plug-in: sendPushMessage method failed
• 132105 EWS Push Message Plug-in: sendResultNotificationMessage method failed
• 400400 Terminal Status/MAP: Not connected to SS7 stack
• 400401 Terminal Status/MAP: Connected to SS7 stack
• 400402 Terminal Status/MAP: Dialog lost, the connection towards at least one of the SS7 backends may be lost
• 400403 Terminal Status/MAP: Received remote user status from the SS7 stack
• 400404 Terminal Status/MAP: Not possible to create the ATI message to the plug-in
• 400405 Terminal Status/MAP: Not possible to create and send the SS7 API message
• 400406 Terminal Status/MAP: No answer or a faulty message was received from the SS7 stack
• 400407 Terminal Status/MAP: Error in the connection towards the SS7 stack
• 400500 SMPP Server Service: Server port started
• 400501 SMPP Server Service: Server port stopped
• 400502 SMPP Server Service: Server connection established
• 400503 SMPP Server Service: Server connection closed
• 400504 SMPP Server Service: Client connection established
• 400505 SMPP Server Service: Client connection closed
• 400506 SMPP Server Service: Client connection reset
• 400507 SMPP Server Service: Client connection reconnect failed
• 400508 SMPP Server Service: ChannelProcessor PeerConnectionIds Empty
• 400509 SMPP Server Service: NorthChannelProcessor PeerPluginInstanceIds Empty
• 400510 SMPP Server Service: PluginInstanceInfo ClientConnectionIds Empty
• 400511 SMPP Server Service: PluginInstanceInfo ServerConnectionIds Empty
• 400512 SMPP Server Service: MO Request Failed
• 400513 SMPP Server Service: MT Request Failed
• 400600 Native SMPP: Exception when processing a submitSmResponse in the plug-in
• 400601 Native SMPP: Exception when processing a submitMultiResponse in the plug-in
• 400602 Native SMPP: Exception when processing a cancelSmResponse in the plug-in
• 400603 Native SMPP: Exception when processing a querySmResponse in the plug-in
• 400604 Native SMPP: Exception when processing a replaceSmResponse in the plug-in
• 400605 Native SMPP: Exception when processing a deliverSm for MO
• 400610 Native SMPP: Exception when processing a bind in the plug-in
• 400611 Native SMPP: Exception when processing a submitSm in the plug-in
• 400612 Native SMPP: Exception when processing a submitMulti in the plug-in
• 400613 Native SMPP: Exception when processing a cancelSm in the plug-in
• 400614 Native SMPP: Exception when processing a querySm in the plug-in
• 400615 Native SMPP: Exception when processing a replaceSm in the plug-in
• 400616 Native SMPP: Exception when processing a deliverSmResponse for MO in the plug-in
• 400617 Native SMPP: Exception when processing a deliverSmResponse for DeliveryReceipt in the plug-in
• 401050 Native MM7 Plug-in: Exception thrown on submit request
• 401051 Native MM7 Plug-in: Exception thrown when the MMSC tried to deliver a network-triggered message using the incorrect xsd version
• 401052 Native MM7 Plug-in: Exception thrown when the MMSC tried to deliver a delivery report using the incorrect xsd version
• 401053 Native MM7 Plug-in: Exception thrown when the MMSC tried to deliver a read reply report using the incorrect xsd version
• 400200 Native UCP Protocol Server Service [tryBuildPDU]: Data was thrown away because no terminating ETX was received
• 400201 Native UCP Protocol Server Service [handleAckNackOnServerSide]: Unable to release TRN for ack/nack received on a server side connection
• 400202 Native UCP Protocol Server Service [handleAckNackOnClientSide]: Unable to release TRN for ack/nack received on a client side connection
• 400203 Native UCP Protocol Server Service [Unable to send a nack]: Data was thrown away because no terminating ETX was received
• 400204 Native UCP Protocol Server Service [sendSessionMgmtAck]: Unable to send ack on a session management, open session operation
• 400205 Native UCP Protocol Server Service [sendHeartbeatAck]: Unable to send ack on a heartbeat request on a server side connection
• 400206 Native UCP Protocol Server Service [deliverServerSideAckNackPDUToPlugin]: Unable to call the plug-in north interface with ack/nack
• 400207 Native UCP Protocol Server Service [deliverClientSideAckNackPDUToPlugin]: Unable to call the plug-in south interface with ack/nack
• 400300 Native UCP SMS Plug-in [handleAckNack]: Exception when processing an MO ack/nack request in the plug-in
• 400301 Native UCP SMS Plug-in [deliverSM]: Exception when processing an MO deliver SM request in the plug-in
• 400302 Native UCP SMS Plug-in [deliveryNotification]: Exception when processing an MO delivery notification request in the plug-in
• 400310 Native UCP SMS Plug-in [handleAckNack]: Exception when processing an MT ack/nack request in the plug-in
• 400311 Native UCP SMS Plug-in [submitSM]: Exception when processing an MT submit SM in the plug-in
• 400312 Native UCP SMS Plug-in [openSession]: Exception when processing an MT openSession request in the plug-in
• 406010 Audio Call/SIP: Media server resource not found
• 199900 Default: Default exception