19231 - Received invalid M3UA message

Event Type:

SS7

Description:

The far-end has sent an invalid M3UA message to which the MP server has responded with an M3UA ERROR message.

Severity:

Info

Instance:

<LinkName> or <AssocName> Information about the type of error and the accompanying diagnostic data is included in the event additional information.

HA Score:

Normal

Throttle Seconds:

10

OID:

awpss7ReceivedInvalidM3uaMessageNotify

Recovery:

1. Examine the M3UA error code and the diagnostic information and attempt to determine why the far-end of the link sent the malformed message.
   • Error code 0x01 indicates an invalid M3UA protocol version. Only version 1 is supported.
   • Error code 0x03 indicates an unsupported M3UA message class.
   • Error code 0x04 indicates an unsupported M3UA message type.
   • Error code 0x07 indicates an M3UA protocol error. The message contains a syntactically correct parameter that does not belong in the message or occurs too many times in the message.
   • Error code 0x11 indicates an invalid parameter value. Parameter type and length are valid, but value is out of range.
   • Error code 0x12 indicates a parameter field error. Parameter is malformed (e.g., invalid length).
   • Error code 0x13 indicates an unexpected parameter. Message contains an undefined parameter. The differences between this error and "Protocol Error" are subtle. Protocol Error is used when the parameter is recognized, but not intended for the type of message that contains it. Unexpected Parameter is used when the parameter identifier is not known.
   • Error code 0x16 indicates a missing parameter. Missing mandatory parameter, or missing required conditional parameter.
   • Error code 0x19 indicates an invalid routing context. Received routing context not configured for any linkset using the association on which the message was received.
2. If the problem persists, it is recommended to contact My Oracle Support (MOS).