These log messages refer to the GTPINSPECTION category.
2.18.1. [ID: 1519] GTP-U bearer creation completely rejected by[...]
- Log Categories
- GTPINSPECTION
- Log Message
- GTP-U bearer creation completely rejected by endpoint.
- Default Log Severity
- Notice
- Parameters
- sessionid, cause, flow
- Explanation
- All of the request to create GTP-U bearer was rejected by endpoint.
- Gateway Action
- Discard
- Action Description
- None
- Proposed Action
- None
2.18.2. [ID: 1536] GTP-U bearer creation rejected by endpoint
- Log Categories
- GTPINSPECTION
- Log Message
- GTP-U bearer creation rejected by endpoint.
- Default Log Severity
- Notice
- Parameters
- sessionid, bearerid, cause, flow
- Explanation
- The other endpoint rejected the request to create GTP-U bearer.
- Gateway Action
- Discard
- Action Description
- None
- Proposed Action
- None
2.18.3. [ID: 1528] GTP-U bearer deletion completely rejected by[...]
- Log Categories
- GTPINSPECTION
- Log Message
- GTP-U bearer deletion completely rejected by endpoint.
- Default Log Severity
- Notice
- Parameters
- sessionid, cause, flow
- Explanation
- All of the request to delete GTP-U bearer was rejected by endpoint.
- Gateway Action
- Discard
- Action Description
- None
- Proposed Action
- None
2.18.4. [ID: 1512] GTP-U bearer deletion rejected by endpoint
- Log Categories
- GTPINSPECTION
- Log Message
- GTP-U bearer deletion rejected by endpoint.
- Default Log Severity
- Notice
- Parameters
- sessionid, bearerid, cause, flow
- Explanation
- The other endpoint rejected the request to delete GTP-U bearer.
- Gateway Action
- Discard
- Action Description
- None
- Proposed Action
- None
2.18.5. [ID: 1522] GTP-U bearer modification completely rejected[...]
- Log Categories
- GTPINSPECTION
- Log Message
- GTP-U bearer modification completely rejected by endpoint.
- Default Log Severity
- Notice
- Parameters
- sessionid, cause, flow
- Explanation
- All of the request to modify GTP-U bearer was rejected by endpoint.
- Gateway Action
- Discard
- Action Description
- None
- Proposed Action
- None
2.18.6. [ID: 1534] GTP-U bearer modification rejected by endpoint
- Log Categories
- GTPINSPECTION
- Log Message
- GTP-U bearer modification rejected by endpoint.
- Default Log Severity
- Notice
- Parameters
- sessionid, bearerid, cause, flow
- Explanation
- The other endpoint rejected the request to modify GTP-U bearer.
- Gateway Action
- Discard
- Action Description
- None
- Proposed Action
- None
2.18.7. [ID: 1521] G-PDU dropped due to empty T-PDU
- Log Categories
- GTPINSPECTION,VALIDATE
- Log Message
- G-PDU dropped due to empty T-PDU.
- Default Log Severity
- Notice
- Parameters
- flow, user, userid
- Explanation
- G-PDU message dropped due to empty T-PDU.
- Gateway Action
- Drop
- Action Description
- None
- Proposed Action
- None
2.18.8. [ID: 1538] Flow closed
- Log Categories
- GTPINSPECTION
- Log Message
- Flow closed.
- Default Log Severity
- Information
- Parameters
- flow
- Explanation
- A flow using GTP inspection was closed.
- Gateway Action
- Close
- Action Description
- None
- Proposed Action
- None
2.18.9. [ID: 1524] Flow failed
- Log Categories
- GTPINSPECTION
- Log Message
- Flow failed.
- Default Log Severity
- Notice
- Parameters
- reason, originator, flow, rule
- Explanation
- An error occurred that caused the GTP inspection flow to be aborted.
- Gateway Action
- Abort
- Action Description
- None
- Proposed Action
- None
2.18.10. [ID: 1523] Flow opened
- Log Categories
- GTPINSPECTION
- Log Message
- Flow opened.
- Default Log Severity
- Information
- Parameters
- flow
- Explanation
- A flow using GTP inspection was opened.
- Gateway Action
- Open
- Action Description
- None
- Proposed Action
- None
2.18.11. [ID: 1567] Bearer ID does not exist
- Log Categories
- GTPINSPECTION
- Log Message
- Bearer ID does not exist.
- Default Log Severity
- Notice
- Parameters
- sessionid, version, messagetype, teid, flow
- Explanation
- The received GTP-C message containing a NSAPI/EPS bearer ID for which no GTP-U bearer exist.
- Gateway Action
- Drop
- Action Description
- None
- Proposed Action
- None
2.18.12. [ID: 1624] Bearer ID does not exist
- Log Categories
- GTPINSPECTION
- Log Message
- Bearer ID does not exist.
- Default Log Severity
- Notice
- Parameters
- sessionid, version, messagetype, teid, flow
- Explanation
- The received GTP-C message containing a NSAPI/EPS bearer ID for which no GTP-U bearer exist.
- Gateway Action
- Strippiggyback
- Action Description
- None
- Proposed Action
- None
2.18.13. [ID: 1561] Bearer lacks F-TEID
- Log Categories
- GTPINSPECTION
- Log Message
- Bearer lacks F-TEID.
- Default Log Severity
- Notice
- Parameters
- sessionid, version, messagetype, teid, flow
- Explanation
- The GTP-C message does not contain a F-TEID for a GTP-U bearer.
- Gateway Action
- Drop
- Action Description
- None
- Proposed Action
- None
2.18.14. [ID: 1598] Bearer lacks F-TEID
- Log Categories
- GTPINSPECTION
- Log Message
- Bearer lacks F-TEID.
- Default Log Severity
- Notice
- Parameters
- sessionid, version, messagetype, teid, flow
- Explanation
- The GTP-C message does not contain a F-TEID for a GTP-U bearer.
- Gateway Action
- Strippiggyback
- Action Description
- None
- Proposed Action
- None
2.18.15. [ID: 1565] TEID of bearer should not be zero
- Log Categories
- GTPINSPECTION
- Log Message
- TEID of bearer should not be zero.
- Default Log Severity
- Notice
- Parameters
- sessionid, version, messagetype, teid, flow
- Explanation
- The GTP-C message contained a zero F-TEID for a GTP-U bearer.
- Gateway Action
- Drop
- Action Description
- None
- Proposed Action
- None
2.18.16. [ID: 1632] TEID of bearer should not be zero
- Log Categories
- GTPINSPECTION
- Log Message
- TEID of bearer should not be zero.
- Default Log Severity
- Notice
- Parameters
- sessionid, version, messagetype, teid, flow
- Explanation
- The GTP-C message contained a zero F-TEID for a GTP-U bearer.
- Gateway Action
- Strippiggyback
- Action Description
- None
- Proposed Action
- None
2.18.17. [ID: 1564] Could not add proposed GTP-U bearer
- Log Categories
- GTPINSPECTION
- Log Message
- Could not add proposed GTP-U bearer.
- Default Log Severity
- Notice
- Parameters
- sessionid, version, messagetype, teid, flow
- Explanation
- The system could not create a new GTP-U bearer.
- Gateway Action
- Drop
- Action Description
- None
- Proposed Action
- None
2.18.18. [ID: 1634] Could not add proposed GTP-U bearer
- Log Categories
- GTPINSPECTION
- Log Message
- Could not add proposed GTP-U bearer.
- Default Log Severity
- Notice
- Parameters
- sessionid, version, messagetype, teid, flow
- Explanation
- The system could not create a new GTP-U bearer.
- Gateway Action
- Strippiggyback
- Action Description
- None
- Proposed Action
- None
2.18.19. [ID: 1573] Could not delete GTP-U bearer
- Log Categories
- GTPINSPECTION
- Log Message
- Could not delete GTP-U bearer.
- Default Log Severity
- Notice
- Parameters
- sessionid, version, messagetype, teid, flow
- Explanation
- The system could not delete a GTP-U bearer.
- Gateway Action
- Drop
- Action Description
- None
- Proposed Action
- None
2.18.20. [ID: 1600] Could not delete GTP-U bearer
- Log Categories
- GTPINSPECTION
- Log Message
- Could not delete GTP-U bearer.
- Default Log Severity
- Notice
- Parameters
- sessionid, version, messagetype, teid, flow
- Explanation
- The system could not delete a GTP-U bearer.
- Gateway Action
- Strippiggyback
- Action Description
- None
- Proposed Action
- None
2.18.21. [ID: 1559] Could not finalize GTP-U bearer
- Log Categories
- GTPINSPECTION
- Log Message
- Could not finalize GTP-U bearer.
- Default Log Severity
- Notice
- Parameters
- sessionid, version, messagetype, teid, flow
- Explanation
- The system could not finalize the creation of a new GTP-U bearer.
- Gateway Action
- Drop
- Action Description
- None
- Proposed Action
- None
2.18.22. [ID: 1614] Could not finalize GTP-U bearer
- Log Categories
- GTPINSPECTION
- Log Message
- Could not finalize GTP-U bearer.
- Default Log Severity
- Notice
- Parameters
- sessionid, version, messagetype, teid, flow
- Explanation
- The system could not finalize the creation of a new GTP-U bearer.
- Gateway Action
- Strippiggyback
- Action Description
- None
- Proposed Action
- None
2.18.23. [ID: 1552] Could not set proposed values on GTP-U bearer
- Log Categories
- GTPINSPECTION
- Log Message
- Could not set proposed values on GTP-U bearer.
- Default Log Severity
- Notice
- Parameters
- sessionid, version, messagetype, teid, flow
- Explanation
- The GTP-U bearer could not be updated with the values in the received GTP-C message.
- Gateway Action
- Drop
- Action Description
- None
- Proposed Action
- None
2.18.24. [ID: 1606] Could not set proposed values on GTP-U bearer
- Log Categories
- GTPINSPECTION
- Log Message
- Could not set proposed values on GTP-U bearer.
- Default Log Severity
- Notice
- Parameters
- sessionid, version, messagetype, teid, flow
- Explanation
- The GTP-U bearer could not be updated with the values in the received GTP-C message.
- Gateway Action
- Strippiggyback
- Action Description
- None
- Proposed Action
- None
2.18.25. [ID: 1585] Disallowed GTP version
- Log Categories
- GTPINSPECTION
- Log Message
- Disallowed GTP version.
- Default Log Severity
- Notice
- Parameters
- sessionid, version, messagetype, flow
- Explanation
- The GTP-C message with a version that is not allowed by the configuration.
- Gateway Action
- Drop
- Action Description
- None
- Proposed Action
- Reconfigure the sender to use a supported GTP version.
2.18.26. [ID: 1566] Duplicate Bearer ID
- Log Categories
- GTPINSPECTION
- Log Message
- Duplicate Bearer ID.
- Default Log Severity
- Notice
- Parameters
- sessionid, version, messagetype, teid, flow
- Explanation
- The received GTP-C message contained a NSAPI/EPS bearer ID for which a GPT-U bearer already exist.
- Gateway Action
- Drop
- Action Description
- None
- Proposed Action
- None
2.18.27. [ID: 1616] Duplicate Bearer ID
- Log Categories
- GTPINSPECTION
- Log Message
- Duplicate Bearer ID.
- Default Log Severity
- Notice
- Parameters
- sessionid, version, messagetype, teid, flow
- Explanation
- The received GTP-C message contained a NSAPI/EPS bearer ID for which a GPT-U bearer already exist.
- Gateway Action
- Strippiggyback
- Action Description
- None
- Proposed Action
- None
2.18.28. [ID: 1587] Zero size extension header
- Log Categories
- GTPINSPECTION
- Log Message
- Zero size extension header.
- Default Log Severity
- Notice
- Parameters
- sessionid, version, messagetype, teid, flow
- Explanation
- The received GTP-C message contained an empty extension header.
- Gateway Action
- Drop
- Action Description
- None
- Proposed Action
- None
2.18.29. [ID: 1580] Failed to read IE
- Log Categories
- GTPINSPECTION
- Log Message
- Failed to read IE.
- Default Log Severity
- Notice
- Parameters
- sessionid, version, messagetype, teid, ie, flow
- Explanation
- The system could not read an information element from the received GTP-C message.
- Gateway Action
- Drop
- Action Description
- None
- Proposed Action
- None
2.18.30. [ID: 1602] Failed to read IE
- Log Categories
- GTPINSPECTION
- Log Message
- Failed to read IE.
- Default Log Severity
- Notice
- Parameters
- sessionid, version, messagetype, teid, ie, flow
- Explanation
- The system could not read an information element from the received GTP-C message.
- Gateway Action
- Strippiggyback
- Action Description
- None
- Proposed Action
- None
2.18.31. [ID: 1562] Incorrect optional IEs
- Log Categories
- GTPINSPECTION
- Log Message
- Incorrect optional IEs.
- Default Log Severity
- Notice
- Parameters
- sessionid, version, messagetype, teid, flow
- Explanation
- The received GTP-C message contained an incorrect optional information element.
- Gateway Action
- Drop
- Action Description
- None
- Proposed Action
- None
2.18.32. [ID: 1628] Incorrect optional IEs
- Log Categories
- GTPINSPECTION
- Log Message
- Incorrect optional IEs.
- Default Log Severity
- Notice
- Parameters
- sessionid, version, messagetype, teid, flow
- Explanation
- The received GTP-C message contained an incorrect optional information element.
- Gateway Action
- Strippiggyback
- Action Description
- None
- Proposed Action
- None
2.18.33. [ID: 1636] Invalid Bearer ID
- Log Categories
- GTPINSPECTION
- Log Message
- Invalid Bearer ID.
- Default Log Severity
- Notice
- Parameters
- sessionid, version, messagetype, teid, flow
- Explanation
- The received GTP-C message contained an invalid EPS bearer ID, due to spare bits being non-zero.
- Gateway Action
- Drop
- Action Description
- None
- Proposed Action
- None
2.18.34. [ID: 1635] Invalid Bearer ID
- Log Categories
- GTPINSPECTION
- Log Message
- Invalid Bearer ID.
- Default Log Severity
- Notice
- Parameters
- sessionid, version, messagetype, teid, flow
- Explanation
- The received GTP-C message contained an invalid EPS bearer ID, due to spare bits being non-zero.
- Gateway Action
- Strippiggyback
- Action Description
- None
- Proposed Action
- None
2.18.35. [ID: 1584] Invalid extension header content
- Log Categories
- GTPINSPECTION
- Log Message
- Invalid extension header content.
- Default Log Severity
- Notice
- Parameters
- sessionid, version, messagetype, teid, flow
- Explanation
- The received GTP-C message contained an extension header with invalid data.
- Gateway Action
- Drop
- Action Description
- None
- Proposed Action
- None
2.18.36. [ID: 1568] Invalid mandatory IE
- Log Categories
- GTPINSPECTION
- Log Message
- Invalid mandatory IE.
- Default Log Severity
- Notice
- Parameters
- sessionid, version, messagetype, teid, flow
- Explanation
- The received GTP-C message contained an invalid mandatory information element.
- Gateway Action
- Drop
- Action Description
- None
- Proposed Action
- None
2.18.37. [ID: 1612] Invalid mandatory IE
- Log Categories
- GTPINSPECTION
- Log Message
- Invalid mandatory IE.
- Default Log Severity
- Notice
- Parameters
- sessionid, version, messagetype, teid, flow
- Explanation
- The received GTP-C message contained an invalid mandatory information element.
- Gateway Action
- Strippiggyback
- Action Description
- None
- Proposed Action
- None
2.18.38. [ID: 1558] Invalid optional IE
- Log Categories
- GTPINSPECTION
- Log Message
- Invalid optional IE.
- Default Log Severity
- Notice
- Parameters
- sessionid, version, messagetype, teid, flow
- Explanation
- The received GTP-C message contained an invalid optional information element.
- Gateway Action
- Drop
- Action Description
- None
- Proposed Action
- None
2.18.39. [ID: 1604] Invalid optional IE
- Log Categories
- GTPINSPECTION
- Log Message
- Invalid optional IE.
- Default Log Severity
- Notice
- Parameters
- sessionid, version, messagetype, teid, flow
- Explanation
- The received GTP-C message contained an invalid optional information element.
- Gateway Action
- Strippiggyback
- Action Description
- None
- Proposed Action
- None
2.18.40. [ID: 1578] GTP-C sender IP is invalid
- Log Categories
- GTPINSPECTION
- Log Message
- GTP-C sender IP is invalid.
- Default Log Severity
- Notice
- Parameters
- sessionid, version, messagetype, teid, flow
- Explanation
- GTP-C sender IP address was invalid.
- Gateway Action
- Drop
- Action Description
- None
- Proposed Action
- None
2.18.41. [ID: 1607] GTP-C sender IP is invalid
- Log Categories
- GTPINSPECTION
- Log Message
- GTP-C sender IP is invalid.
- Default Log Severity
- Notice
- Parameters
- sessionid, version, messagetype, teid, flow
- Explanation
- GTP-C sender IP address was invalid.
- Gateway Action
- Strippiggyback
- Action Description
- None
- Proposed Action
- None
2.18.42. [ID: 1621] Main message blocked due to invalid piggyback
- Log Categories
- GTPINSPECTION
- Log Message
- Main message blocked due to invalid piggyback.
- Default Log Severity
- Notice
- Parameters
- sessionid, flow
- Explanation
- According to setting the piggy back message was dropped, and with it the main message was blocked.
- Gateway Action
- Block
- Action Description
- None
- Proposed Action
- None
2.18.43. [ID: 1583] Message in wrong direction
- Log Categories
- GTPINSPECTION
- Log Message
- Message in wrong direction.
- Default Log Severity
- Notice
- Parameters
- sessionid, version, messagetype, teid, flow
- Explanation
- The receive GTP-C message was sent in the wrong direction.
- Gateway Action
- Drop
- Action Description
- None
- Proposed Action
- None
2.18.44. [ID: 1597] Message in wrong direction
- Log Categories
- GTPINSPECTION
- Log Message
- Message in wrong direction.
- Default Log Severity
- Notice
- Parameters
- sessionid, version, messagetype, teid, flow
- Explanation
- The receive GTP-C message was sent in the wrong direction.
- Gateway Action
- Strippiggyback
- Action Description
- None
- Proposed Action
- None
2.18.45. [ID: 1574] Message too short
- Log Categories
- GTPINSPECTION
- Log Message
- Message too short.
- Default Log Severity
- Notice
- Parameters
- sessionid, paylen, flow
- Explanation
- The received GTP-C message was too short.
- Gateway Action
- Drop
- Action Description
- None
- Proposed Action
- None
2.18.46. [ID: 1625] Message too short
- Log Categories
- GTPINSPECTION
- Log Message
- Message too short.
- Default Log Severity
- Notice
- Parameters
- sessionid, paylen, flow
- Explanation
- The received GTP-C message was too short.
- Gateway Action
- Strippiggyback
- Action Description
- None
- Proposed Action
- None
2.18.47. [ID: 1575] Missing Conditionally Present IE
- Log Categories
- GTPINSPECTION
- Log Message
- Missing Conditionally Present IE.
- Default Log Severity
- Notice
- Parameters
- sessionid, version, messagetype, teid, ie, flow
- Explanation
- The GTP-C message did not contain a mandatory information element.
- Gateway Action
- Drop
- Action Description
- None
- Proposed Action
- None
2.18.48. [ID: 1618] Missing Conditionally Present IE
- Log Categories
- GTPINSPECTION
- Log Message
- Missing Conditionally Present IE.
- Default Log Severity
- Notice
- Parameters
- sessionid, version, messagetype, teid, ie, flow
- Explanation
- The GTP-C message did not contain a mandatory information element.
- Gateway Action
- Strippiggyback
- Action Description
- None
- Proposed Action
- None
2.18.49. [ID: 1563] Missing mandatorily present IE
- Log Categories
- GTPINSPECTION
- Log Message
- Missing mandatorily present IE.
- Default Log Severity
- Notice
- Parameters
- sessionid, version, messagetype, ie, flow
- Explanation
- The GTP-C message did not contain a mandatory information element.
- Gateway Action
- Drop
- Action Description
- None
- Proposed Action
- None
2.18.50. [ID: 1603] Missing mandatorily present IE
- Log Categories
- GTPINSPECTION
- Log Message
- Missing mandatorily present IE.
- Default Log Severity
- Notice
- Parameters
- sessionid, version, messagetype, ie, flow
- Explanation
- The GTP-C message did not contain a mandatory information element.
- Gateway Action
- Strippiggyback
- Action Description
- None
- Proposed Action
- None
2.18.51. [ID: 1572] Needs both GTP-U IP and TEID
- Log Categories
- GTPINSPECTION
- Log Message
- Needs both GTP-U IP and TEID.
- Default Log Severity
- Notice
- Parameters
- sessionid, version, messagetype, teid, flow
- Explanation
- The IP address or the TEID for the GTP-U bearer was not known.
- Gateway Action
- Drop
- Action Description
- None
- Proposed Action
- None
2.18.52. [ID: 1622] Needs both GTP-U IP and TEID
- Log Categories
- GTPINSPECTION
- Log Message
- Needs both GTP-U IP and TEID.
- Default Log Severity
- Notice
- Parameters
- sessionid, version, messagetype, teid, flow
- Explanation
- The IP address or the TEID for the GTP-U bearer was not known.
- Gateway Action
- Strippiggyback
- Action Description
- None
- Proposed Action
- None
2.18.53. [ID: 1553] Did not find outstanding request for response[...]
- Log Categories
- GTPINSPECTION
- Log Message
- Did not find outstanding request for response message.
- Default Log Severity
- Notice
- Parameters
- sessionid, version, messagetype, teid, flow
- Explanation
- The system received a GTP-C response message for which it had not received a corresponding request message.
- Gateway Action
- Drop
- Action Description
- None
- Proposed Action
- None
2.18.54. [ID: 1601] Did not find outstanding request for response[...]
- Log Categories
- GTPINSPECTION
- Log Message
- Did not find outstanding request for response message.
- Default Log Severity
- Notice
- Parameters
- sessionid, version, messagetype, teid, flow
- Explanation
- The system received a GTP-C response message for which it had not received a corresponding request message.
- Gateway Action
- Strippiggyback
- Action Description
- None
- Proposed Action
- None
2.18.55. [ID: 1613] Unknown message type
- Log Categories
- GTPINSPECTION
- Log Message
- Unknown message type.
- Default Log Severity
- Notice
- Parameters
- sessionid, version, messagetype, teid, flow
- Explanation
- The received GTP-C message type messagetype is not supported by the system.
- Gateway Action
- Drop
- Action Description
- None
- Proposed Action
- None
2.18.56. [ID: 1555] Unknown message type
- Log Categories
- GTPINSPECTION
- Log Message
- Unknown message type.
- Default Log Severity
- Notice
- Parameters
- sessionid, version, messagetype, teid, flow
- Explanation
- The received GTP-C message type messagetype is not supported by the system.
- Gateway Action
- Allow
- Action Description
- None
- Proposed Action
- None
2.18.57. [ID: 1615] Unknown message type
- Log Categories
- GTPINSPECTION
- Log Message
- Unknown message type.
- Default Log Severity
- Notice
- Parameters
- sessionid, version, messagetype, teid, flow
- Explanation
- The received GTP-C message type messagetype is not supported by the system.
- Gateway Action
- Strippiggyback
- Action Description
- None
- Proposed Action
- None
2.18.58. [ID: 1570] Unsupported GTP version
- Log Categories
- GTPINSPECTION
- Log Message
- Unsupported GTP version.
- Default Log Severity
- Notice
- Parameters
- sessionid, version, flow
- Explanation
- Received a GTP packet with a unknown or unsupported version.
- Gateway Action
- Drop
- Action Description
- None
- Proposed Action
- Reconfigure the sender to use a supported GTP version.
2.18.59. [ID: 1586] Out of sequence IE
- Log Categories
- GTPINSPECTION
- Log Message
- Out of sequence IE.
- Default Log Severity
- Notice
- Parameters
- sessionid, version, messagetype, teid, flow
- Explanation
- The received GTP-C message contained information elements that were not in increasing order.
- Gateway Action
- Drop
- Action Description
- None
- Proposed Action
- None
2.18.60. [ID: 1633] Out of sequence IE
- Log Categories
- GTPINSPECTION
- Log Message
- Out of sequence IE.
- Default Log Severity
- Notice
- Parameters
- sessionid, version, messagetype, teid, flow
- Explanation
- The received GTP-C message contained information elements that were not in increasing order.
- Gateway Action
- Strippiggyback
- Action Description
- None
- Proposed Action
- None
2.18.61. [ID: 1551] Repeated IEs
- Log Categories
- GTPINSPECTION
- Log Message
- Repeated IEs.
- Default Log Severity
- Notice
- Parameters
- sessionid, version, messagetype, teid, ie, flow
- Explanation
- The GTP-C message contained to many information elements of the same type.
- Gateway Action
- Drop
- Action Description
- None
- Proposed Action
- None
2.18.62. [ID: 1623] Repeated IEs
- Log Categories
- GTPINSPECTION
- Log Message
- Repeated IEs.
- Default Log Severity
- Notice
- Parameters
- sessionid, version, messagetype, teid, ie, flow
- Explanation
- The GTP-C message contained to many information elements of the same type.
- Gateway Action
- Strippiggyback
- Action Description
- None
- Proposed Action
- None
2.18.63. [ID: 1533] GTP-C session created
- Log Categories
- GTPINSPECTION
- Log Message
- GTP-C session created.
- Default Log Severity
- Notice
- Parameters
- sessionid, version, origip, origteid, termip, termteid, flow
- Explanation
- A GTP-C session has been successfully created.
- Gateway Action
- Open
- Action Description
- None
- Proposed Action
- None
2.18.64. [ID: 1532] GTP-C session deleted
- Log Categories
- GTPINSPECTION
- Log Message
- GTP-C session deleted.
- Default Log Severity
- Notice
- Parameters
- sessionid, origip, origteid, termip, termteid, reason
- Explanation
- A GTP-C session has been successfully deleted.
- Gateway Action
- Close
- Action Description
- None
- Proposed Action
- None
2.18.65. [ID: 1638] TEID of session should not be zero
- Log Categories
- GTPINSPECTION
- Log Message
- TEID of session should not be zero.
- Default Log Severity
- Notice
- Parameters
- sessionid, version, messagetype, teid, flow
- Explanation
- The GTP-C message contained a zero F-TEID.
- Gateway Action
- Drop
- Action Description
- None
- Proposed Action
- None
2.18.66. [ID: 1637] TEID of session should not be zero
- Log Categories
- GTPINSPECTION
- Log Message
- TEID of session should not be zero.
- Default Log Severity
- Notice
- Parameters
- sessionid, version, messagetype, teid, flow
- Explanation
- The GTP-C message contained a zero F-TEID.
- Gateway Action
- Strippiggyback
- Action Description
- None
- Proposed Action
- None
2.18.67. [ID: 1527] GTP-C session updated
- Log Categories
- GTPINSPECTION
- Log Message
- GTP-C session updated.
- Default Log Severity
- Notice
- Parameters
- sessionid, origip, origteid, termip, termteid, flow
- Explanation
- A GTP-C session has been successfully updated.
- Gateway Action
- Adjust
- Action Description
- None
- Proposed Action
- None
2.18.68. [ID: 1549] Message header should have sequence number
- Log Categories
- GTPINSPECTION
- Log Message
- Message header should have sequence number.
- Default Log Severity
- Notice
- Parameters
- sessionid, version, messagetype, teid, flow
- Explanation
- The received GTP message should contain a sequence number in its GTP header.
- Gateway Action
- Drop
- Action Description
- None
- Proposed Action
- None
2.18.69. [ID: 1577] Message header should have TEID
- Log Categories
- GTPINSPECTION
- Log Message
- Message header should have TEID.
- Default Log Severity
- Notice
- Parameters
- sessionid, version, messagetype, flow
- Explanation
- The received GTP message should contain a Tunnel Endpoint Identifier (TEID) in its GTP header.
- Gateway Action
- Drop
- Action Description
- None
- Proposed Action
- None
2.18.70. [ID: 1608] Message header should have TEID
- Log Categories
- GTPINSPECTION
- Log Message
- Message header should have TEID.
- Default Log Severity
- Notice
- Parameters
- sessionid, version, messagetype, flow
- Explanation
- The received GTP message should contain a Tunnel Endpoint Identifier (TEID) in its GTP header.
- Gateway Action
- Strippiggyback
- Action Description
- None
- Proposed Action
- None
2.18.71. [ID: 1554] Message header should not have TEID
- Log Categories
- GTPINSPECTION
- Log Message
- Message header should not have TEID.
- Default Log Severity
- Notice
- Parameters
- sessionid, version, messagetype, flow
- Explanation
- The received GTP message should not contain a Tunnel Endpoint Identifier (TEID) in its GTP header.
- Gateway Action
- Drop
- Action Description
- None
- Proposed Action
- None
2.18.72. [ID: 1605] Message header should not have TEID
- Log Categories
- GTPINSPECTION
- Log Message
- Message header should not have TEID.
- Default Log Severity
- Notice
- Parameters
- sessionid, version, messagetype, flow
- Explanation
- The received GTP message should not contain a Tunnel Endpoint Identifier (TEID) in its GTP header.
- Gateway Action
- Strippiggyback
- Action Description
- None
- Proposed Action
- None
2.18.73. [ID: 1560] Too many bearers
- Log Categories
- GTPINSPECTION
- Log Message
- Too many bearers.
- Default Log Severity
- Warning
- Parameters
- sessionid, version, messagetype, teid, max, flow
- Explanation
- The limit for the configured number of GTP-U bearers was exceeded.
- Gateway Action
- Drop
- Action Description
- None
- Proposed Action
- Review the limits configured in the GTP inspection profile used.
2.18.74. [ID: 1599] Too many bearers
- Log Categories
- GTPINSPECTION
- Log Message
- Too many bearers.
- Default Log Severity
- Warning
- Parameters
- sessionid, version, messagetype, teid, max, flow
- Explanation
- The limit for the configured number of GTP-U bearers was exceeded.
- Gateway Action
- Strippiggyback
- Action Description
- None
- Proposed Action
- Review the limits configured in the GTP inspection profile used.
2.18.75. [ID: 1579] Too many piggy back messages
- Log Categories
- GTPINSPECTION
- Log Message
- Too many piggy back messages.
- Default Log Severity
- Notice
- Parameters
- sessionid, version, messagetype, teid, flow
- Gateway Action
- Drop
- Action Description
- None
- Proposed Action
- None
2.18.76. [ID: 1629] Too many piggy back messages
- Log Categories
- GTPINSPECTION
- Log Message
- Too many piggy back messages.
- Default Log Severity
- Notice
- Parameters
- sessionid, version, messagetype, teid, flow
- Gateway Action
- Strippiggyback
- Action Description
- None
- Proposed Action
- None
2.18.77. [ID: 1576] Too many sessions
- Log Categories
- GTPINSPECTION
- Log Message
- Too many sessions.
- Default Log Severity
- Warning
- Parameters
- sessionid, version, messagetype, teid, max, flow
- Explanation
- The limit for the configured number of GTP-C sessions was exceeded.
- Gateway Action
- Drop
- Action Description
- None
- Proposed Action
- Review the limits configured in the GTP inspection profile used.
2.18.78. [ID: 1591] Too many sessions per IP
- Log Categories
- GTPINSPECTION
- Log Message
- Too many sessions per IP.
- Default Log Severity
- Warning
- Parameters
- sessionid, version, messagetype, teid, max, flow
- Explanation
- The limit for the configured number of GTP-C sessions per source IP was exceeded.
- Gateway Action
- Drop
- Action Description
- None
- Proposed Action
- Review the limits configured in the GTP inspection profile used.
2.18.79. [ID: 1620] Too many sessions per IP
- Log Categories
- GTPINSPECTION
- Log Message
- Too many sessions per IP.
- Default Log Severity
- Warning
- Parameters
- sessionid, version, messagetype, teid, max, flow
- Explanation
- The limit for the configured number of GTP-C sessions per source IP was exceeded.
- Gateway Action
- Strippiggyback
- Action Description
- None
- Proposed Action
- Review the limits configured in the GTP inspection profile used.
2.18.80. [ID: 1619] Too many sessions
- Log Categories
- GTPINSPECTION
- Log Message
- Too many sessions.
- Default Log Severity
- Warning
- Parameters
- sessionid, version, messagetype, teid, max, flow
- Explanation
- The limit for the configured number of GTP-C sessions was exceeded.
- Gateway Action
- Strippiggyback
- Action Description
- None
- Proposed Action
- Review the limits configured in the GTP inspection profile used.
2.18.81. [ID: 1617] Unexpected IE
- Log Categories
- GTPINSPECTION
- Log Message
- Unexpected IE.
- Default Log Severity
- Notice
- Parameters
- sessionid, version, messagetype, teid, ie, name, flow
- Explanation
- The received GTP-C message contained an information element of type ie that was not expected for the message type messagetype or for the current state.
- Gateway Action
- Drop
- Action Description
- None
- Proposed Action
- None
2.18.82. [ID: 1571] Unexpected IE
- Log Categories
- GTPINSPECTION
- Log Message
- Unexpected IE.
- Default Log Severity
- Notice
- Parameters
- sessionid, version, messagetype, teid, ie, name, flow
- Explanation
- The received GTP-C message contained an information element of type ie that was not expected for the message type messagetype or for the current state.
- Gateway Action
- Allow
- Action Description
- None
- Proposed Action
- None
2.18.83. [ID: 1626] Unexpected IE
- Log Categories
- GTPINSPECTION
- Log Message
- Unexpected IE.
- Default Log Severity
- Notice
- Parameters
- sessionid, version, messagetype, teid, ie, name, flow
- Explanation
- The received GTP-C message contained an information element of type ie that was not expected for the message type messagetype or for the current state .
- Gateway Action
- Strippiggyback
- Action Description
- None
- Proposed Action
- None
2.18.84. [ID: 1556] Unexpected GTP signaling message
- Log Categories
- GTPINSPECTION
- Log Message
- Unexpected GTP signaling message.
- Default Log Severity
- Notice
- Parameters
- sessionid, version, messagetype, teid, flow
- Explanation
- A GTP-C message of type messagetype was not expected at this time.
- Gateway Action
- Drop
- Action Description
- None
- Proposed Action
- None
2.18.85. [ID: 1630] Unexpected GTP signaling message
- Log Categories
- GTPINSPECTION
- Log Message
- Unexpected GTP signaling message.
- Default Log Severity
- Notice
- Parameters
- sessionid, version, messagetype, teid, flow
- Explanation
- A GTP-C message of type messagetype was not expected at this time.
- Gateway Action
- Strippiggyback
- Action Description
- None
- Proposed Action
- None
2.18.86. [ID: 1627] Unknown IE
- Log Categories
- GTPINSPECTION
- Log Message
- Unknown IE.
- Default Log Severity
- Notice
- Parameters
- sessionid, version, messagetype, teid, ie, flow
- Explanation
- The received GTP-C message contained an unknown information element of type ie.
- Gateway Action
- Drop
- Action Description
- None
- Proposed Action
- None
2.18.87. [ID: 1581] Unknown IE
- Log Categories
- GTPINSPECTION
- Log Message
- Unknown IE.
- Default Log Severity
- Notice
- Parameters
- sessionid, version, messagetype, teid, ie, flow
- Explanation
- The received GTP-C message contained an unknown information element of type ie.
- Gateway Action
- Allow
- Action Description
- None
- Proposed Action
- None
2.18.88. [ID: 1610] Unknown IE
- Log Categories
- GTPINSPECTION
- Log Message
- Unknown IE.
- Default Log Severity
- Notice
- Parameters
- sessionid, version, messagetype, teid, ie, flow
- Explanation
- The received GTP-C message contained an unknown information element of type ie.
- Gateway Action
- Strippiggyback
- Action Description
- None
- Proposed Action
- None
2.18.89. [ID: 1582] Unknown GTP signaling message
- Log Categories
- GTPINSPECTION
- Log Message
- Unknown GTP signaling message.
- Default Log Severity
- Notice
- Parameters
- sessionid, version, messagetype, teid, flow
- Explanation
- The received GTP-C message was of an unknown message type.
- Gateway Action
- Drop
- Action Description
- None
- Proposed Action
- None
2.18.90. [ID: 1611] Unknown GTP signaling message
- Log Categories
- GTPINSPECTION
- Log Message
- Unknown GTP signaling message.
- Default Log Severity
- Notice
- Parameters
- sessionid, version, messagetype, teid, flow
- Explanation
- The received GTP-C message was of an unknown message type.
- Gateway Action
- Strippiggyback
- Action Description
- None
- Proposed Action
- None
2.18.91. [ID: 1550] Wrong packet version of piggy back message
- Log Categories
- GTPINSPECTION
- Log Message
- Wrong packet version of piggy back message.
- Default Log Severity
- Notice
- Parameters
- sessionid, version, messagetype, teid, flow
- Explanation
- The piggybacked message contained the wrong GTP version. A piggybacked initial message is a message that is concatenated to
a response message and shares its UDP header.
- Gateway Action
- Drop
- Action Description
- None
- Proposed Action
- None
2.18.92. [ID: 1631] Wrong packet version of piggy back message
- Log Categories
- GTPINSPECTION
- Log Message
- Wrong packet version of piggy back message.
- Default Log Severity
- Notice
- Parameters
- sessionid, version, messagetype, teid, flow
- Explanation
- The piggybacked message contained the wrong GTP version. A piggybacked initial message is a message that is concatenated to
a response message and shares its UDP header.
- Gateway Action
- Strippiggyback
- Action Description
- None
- Proposed Action
- None
2.18.93. [ID: 1588] GTP-U bearer created
- Log Categories
- GTPINSPECTION
- Log Message
- GTP-U bearer created.
- Default Log Severity
- Notice
- Parameters
- sessionid, bearerid, origip, origteid, termip, termteid, flow
- Explanation
- A new GTP-U bearer has been created for the GTP-C session.
- Gateway Action
- Open
- Action Description
- None
- Proposed Action
- None
2.18.94. [ID: 1589] GTP-U bearer deleted
- Log Categories
- GTPINSPECTION
- Log Message
- GTP-U bearer deleted.
- Default Log Severity
- Notice
- Parameters
- sessionid, bearerid, origip, origteid, termip, termteid, reason
- Explanation
- A GTP-U bearer has been deleted from the GTP-C session.
- Gateway Action
- Close
- Action Description
- None
- Proposed Action
- None
2.18.95. [ID: 1537] GTP-U bearer modified
- Log Categories
- GTPINSPECTION
- Log Message
- GTP-U bearer modified.
- Default Log Severity
- Notice
- Parameters
- sessionid, bearerid, origip, origteid, termip, termteid, flow
- Explanation
- A GTP-U bearer had one or both of its endpoints modified.
- Gateway Action
- Adjust
- Action Description
- None
- Proposed Action
- None
2.18.96. [ID: 1518] Message received after GTP-U End Marker
- Log Categories
- GTPINSPECTION,VALIDATE
- Log Message
- Message received after GTP-U End Marker.
- Default Log Severity
- Warning
- Parameters
- sessionid, origteid, termteid, flow, user, userid
- Explanation
- Message was dropped due to End Marker was previously received.
- Gateway Action
- Drop
- Action Description
- None
- Proposed Action
- None
2.18.97. [ID: 1511] Failed to validate GTP-U message
- Log Categories
- GTPINSPECTION,VALIDATE
- Log Message
- Failed to validate GTP-U message.
- Default Log Severity
- Warning
- Parameters
- messagetype, flow, user, userid
- Explanation
- Malformed GTP-U message.
- Gateway Action
- Drop
- Action Description
- None
- Proposed Action
- Investigate sending GTP node.
2.18.98. [ID: 1641] Missing mandatorily present IE
- Log Categories
- GTPINSPECTION,VALIDATE
- Log Message
- Missing mandatorily present IE.
- Default Log Severity
- Notice
- Parameters
- messagetype, ie, flow, user, userid
- Explanation
- The GTP-U message did not contain a mandatory information element.
- Gateway Action
- Drop
- Action Description
- None
- Proposed Action
- None
2.18.99. [ID: 1546] GTP-U message should have sequence number
- Log Categories
- GTPINSPECTION,VALIDATE
- Log Message
- GTP-U message should have sequence number.
- Default Log Severity
- Warning
- Parameters
- messagetype, flow, user, userid
- Explanation
- Message should have contained a sequence number but does not.
- Gateway Action
- Drop
- Action Description
- None
- Proposed Action
- Investigate sending GTP node.
2.18.100. [ID: 1642] Out of sequence IE
- Log Categories
- GTPINSPECTION,VALIDATE
- Log Message
- Out of sequence IE.
- Default Log Severity
- Notice
- Parameters
- messagetype, teid, flow, user, userid
- Explanation
- The received GTP-U message contained information elements that were not in increasing order.
- Gateway Action
- Drop
- Action Description
- None
- Proposed Action
- None
2.18.101. [ID: 1595] Repeated GTP-U IEs
- Log Categories
- GTPINSPECTION,VALIDATE
- Log Message
- Repeated GTP-U IEs.
- Default Log Severity
- Notice
- Parameters
- messagetype, teid, ie, flow, user, userid
- Explanation
- The GTP-U message contained to many information elements of the same type.
- Gateway Action
- Drop
- Action Description
- None
- Proposed Action
- None
2.18.102. [ID: 1539] GTP traffic inside a GTP tunnel detected
- Log Categories
- GTPINSPECTION,VALIDATE
- Log Message
- GTP traffic inside a GTP tunnel detected.
- Default Log Severity
- Warning
- Parameters
- flow, user, userid
- Explanation
- GTP traffic detected inside a GTP tunnel.
- Gateway Action
- Allow
- Action Description
- None
- Proposed Action
- Investigate the source of this GTP traffic.
2.18.103. [ID: 1513] GTP traffic inside a GTP tunnel detected
- Log Categories
- GTPINSPECTION,VALIDATE
- Log Message
- GTP traffic inside a GTP tunnel detected.
- Default Log Severity
- Warning
- Parameters
- flow, user, userid
- Explanation
- GTP traffic detected inside a GTP tunnel.
- Gateway Action
- Drop
- Action Description
- None
- Proposed Action
- Investigate the source of this GTP traffic.
2.18.104. [ID: 1545] Message is dropped due to internal error
- Log Categories
- GTPINSPECTION,VALIDATE
- Log Message
- Message is dropped due to internal error.
- Default Log Severity
- Error
- Parameters
- flow, user, userid
- Explanation
- Message is dropped due to internal error.
- Gateway Action
- Drop
- Action Description
- None
- Proposed Action
- None
2.18.105. [ID: 1540] Invalid GTP header
- Log Categories
- GTPINSPECTION,VALIDATE
- Log Message
- Invalid GTP header.
- Default Log Severity
- Warning
- Parameters
- reason, flow, user, userid
- Explanation
- Incoming GTP-U packet has invalid GTP header.
- Gateway Action
- Drop
- Action Description
- None
- Proposed Action
- Incoming packet is malformed. Investigate why GTP traffic sent is invalid.
2.18.106. [ID: 1514] Invalid Recovery IE value
- Log Categories
- GTPINSPECTION,VALIDATE
- Log Message
- Invalid Recovery IE value.
- Default Log Severity
- Warning
- Parameters
- type, flow, user, userid
- Explanation
- Recovery IE must be set to 0 by a sending peer.
- Gateway Action
- Drop
- Action Description
- None
- Proposed Action
- Investigate sending GTP node.
2.18.107. [ID: 1526] Invalid GTP-U message type
- Log Categories
- GTPINSPECTION,VALIDATE
- Log Message
- Invalid GTP-U message type.
- Default Log Severity
- Warning
- Parameters
- flow, user, userid
- Explanation
- Incoming GTP-U packet has invalid message type in it's GTP header.
- Gateway Action
- Allow
- Action Description
- None
- Proposed Action
- Received GTP-U has an unsupported message type. Supported message types are Echo Request, Echo Response, Encapsulated T-PDUs,
Error Indication, Supported Extension Headers Notification and End Marker.
2.18.108. [ID: 1529] Invalid GTP-U message type
- Log Categories
- GTPINSPECTION,VALIDATE
- Log Message
- Invalid GTP-U message type.
- Default Log Severity
- Warning
- Parameters
- flow, user, userid
- Explanation
- Incoming GTP-U packet has invalid message type in it's GTP header.
- Gateway Action
- Drop
- Action Description
- None
- Proposed Action
- Received GTP-U has an unsupported message type. Supported message types are Echo Request, Echo Response, Encapsulated T-PDUs,
Error Indication, Supported Extension Headers Notification and End Marker.
2.18.109. [ID: 1520] Invalid GTP version
- Log Categories
- GTPINSPECTION,VALIDATE
- Log Message
- Invalid GTP version.
- Default Log Severity
- Warning
- Parameters
- flow, user, userid
- Explanation
- Incoming GTP-U packet has unsupported GTP version.
- Gateway Action
- Drop
- Action Description
- None
- Proposed Action
- GTP-U is only supported in GTPv1.
2.18.110. [ID: 1542] No matching GTP-U bearer
- Log Categories
- GTPINSPECTION,VALIDATE
- Log Message
- No matching GTP-U bearer.
- Default Log Severity
- Warning
- Parameters
- teid, flow, user, userid
- Explanation
- GTP-U packet did not match any active bearers.
- Gateway Action
- Drop
- Action Description
- None
- Proposed Action
- None
2.18.111. [ID: 1531] GTP packet dropped
- Log Categories
- GTPINSPECTION
- Log Message
- GTP packet dropped.
- Default Log Severity
- Notice
- Parameters
- sessionid, reason, flow
- Explanation
- A GTP message was rejected by GTP inspection.
- Gateway Action
- Drop
- Action Description
- None
- Proposed Action
- None
2.18.112. [ID: 1609] GTP packet dropped
- Log Categories
- GTPINSPECTION
- Log Message
- GTP packet dropped.
- Default Log Severity
- Notice
- Parameters
- sessionid, reason, flow
- Explanation
- A GTP message was rejected by GTP inspection.
- Gateway Action
- Strippiggyback
- Action Description
- None
- Proposed Action
- None
2.18.113. [ID: 1547] GTP packet notice
- Log Categories
- GTPINSPECTION
- Log Message
- GTP packet notice.
- Default Log Severity
- Notice
- Parameters
- sessionid, reason, flow
- Explanation
- A GTP message that failed GTP inspection validation was forwarded.
- Gateway Action
- Allow
- Action Description
- None
- Proposed Action
- None
2.18.114. [ID: 1517] GTP-C session update rejected by endpoint
- Log Categories
- GTPINSPECTION
- Log Message
- GTP-C session update rejected by endpoint.
- Default Log Severity
- Notice
- Parameters
- sessionid, bearerid, cause, flow
- Explanation
- The other endpoint rejected the request to update GTP-C session.
- Gateway Action
- Discard
- Action Description
- None
- Proposed Action
- None
2.18.115. [ID: 1515] GTP-C session creation rejected by endpoint
- Log Categories
- GTPINSPECTION
- Log Message
- GTP-C session creation rejected by endpoint.
- Default Log Severity
- Notice
- Parameters
- sessionid, cause, flow
- Explanation
- The other endpoint rejected the request to create GTP-C session.
- Gateway Action
- Discard
- Action Description
- None
- Proposed Action
- None
2.18.116. [ID: 1541] GTP-C session deletion rejected by endpoint
- Log Categories
- GTPINSPECTION
- Log Message
- GTP-C session deletion rejected by endpoint.
- Default Log Severity
- Notice
- Parameters
- sessionid, cause, flow
- Explanation
- The other endpoint rejected the request to delete GTP-C session.
- Gateway Action
- Discard
- Action Description
- None
- Proposed Action
- None
2.18.117. [ID: 1530] GTP-C session update rejected by endpoint
- Log Categories
- GTPINSPECTION
- Log Message
- GTP-C session update rejected by endpoint.
- Default Log Severity
- Notice
- Parameters
- sessionid, cause, flow
- Explanation
- The other endpoint rejected the request to update GTP-C session.
- Gateway Action
- Discard
- Action Description
- None
- Proposed Action
- None
2.18.118. [ID: 1590] Unexpected GTP-U IE type
- Log Categories
- GTPINSPECTION,VALIDATE
- Log Message
- Unexpected GTP-U IE type.
- Default Log Severity
- Warning
- Parameters
- ie, flow, user, userid
- Explanation
- Unexpected GTP-U IE type found.
- Gateway Action
- Allow
- Action Description
- None
- Proposed Action
- Investigate the source of this GTP traffic.
2.18.119. [ID: 1596] Unexpected GTP-U IE type
- Log Categories
- GTPINSPECTION,VALIDATE
- Log Message
- Unexpected GTP-U IE type.
- Default Log Severity
- Warning
- Parameters
- ie, flow, user, userid
- Explanation
- Unexpected GTP-U IE type found.
- Gateway Action
- Drop
- Action Description
- None
- Proposed Action
- Investigate the source of this GTP traffic.
2.18.120. [ID: 1594] Unknown GTP-U IE type
- Log Categories
- GTPINSPECTION,VALIDATE
- Log Message
- Unknown GTP-U IE type.
- Default Log Severity
- Notice
- Parameters
- ie, flow, user, userid
- Explanation
- An unknown IE was encountered in the message, but was allowed due to settings.
- Gateway Action
- Allow
- Action Description
- None
- Proposed Action
- Investigate why the endpoints are sending unknown IEs.
2.18.121. [ID: 1592] Unknown GTP-U IE type
- Log Categories
- GTPINSPECTION,VALIDATE
- Log Message
- Unknown GTP-U IE type.
- Default Log Severity
- Warning
- Parameters
- ie, flow, user, userid
- Explanation
- An unknown IE was encountered in the message.
- Gateway Action
- Drop
- Action Description
- None
- Proposed Action
- Investigate why the endpoints are sending unknown IEs.