An execution trigger defines a Triggering Point within the message processing logic. When the triggering point is reached, the mediation operations (Rule Sets) associated with that triggering point are executed. The type of the Trigger defines whether the triggering point is part of the request or the answer processing. The Rule Set can be defined to be executed as a part of the Actions of another Rule Set, or it can be triggered at some specific point of the message processing. A Trigger is executed during an ingress and egress message.
Associations of a Trigger with new Rule Sets can be added, existing associations can be removed, and the sequence of the Rule Set Name list can be changed to modify the MP behavior based on the Rule Set execution. The behavior of an MP is exactly the same with and without a Trigger if no Rule Set is associated with the Trigger.
Rule Sets that are associated with a Trigger are executed in the sequence in which they are listed under the Trigger name on the Diameter > Mediation > Triggers page.
Execution Trigger Name | Message Type | Triggering Point |
---|---|---|
Diameter request message received from connection | Request | Request Trigger Point 1; occurs upon receipt of a request (RTP1) |
Diameter request message ready to be forwarded to connection | Request | Request Trigger Point 10; occurs just before forwarding the request upstream (RTP10) |
Diameter answer message received from connection | Response | Answer Trigger Point 1; occurs upon receipt of an answer (ATP1) |
Diameter answer message ready to be forwarded to connection | Response | Answer Trigger Point 10; occurs just before forwarding the answer downstream (ATP10) |
Diameter request message attempted for re-route | Request | Request Trigger Point 11 (RTP11); occurs just prior to re-routing the request upstream. |
The data stored as an Internal Variable or a linking AVP at one of the DCL triggers is valid only inside of the current trigger and can not be accessed by other triggers. The Triggers described in Table 2 are available for Diameter Mediation.
Execution Trigger Name | Message Type | Triggering Point |
---|---|---|
CER message received from connection | Request | Capabilities- Exchange-Request Trigger Point 1; occurs upon receipt of a CER message (CER1) |
CER message ready to be sent | Request | Capabilities- Exchange-Request Trigger Point 10; occurs just prior to sending the CER message (CER10) |
CEA message received from connection | Response | Capabilities- Exchange-Answer Trigger Point 1; occurs upon receipt of a CEA message (CEA1) |
CEA message ready to be sent | Response | Capabilities- Exchange-Answer Trigger Point 10; occurs just prior to sending the CEA message(CEA10) |
DWR message received from connection | Request | Device-Watchdog-Request Trigger Point 1; occurs upon receipt of a DWR message (DWR1) |
DWR message ready to be sent | Request | Device-Watchdog-Request Trigger Point 10; occurs just prior to sending the DWR message (DWR10) |
DWA message received from connection | Response | Device-Watchdog-Answer Trigger Point 1; occurs upon receipt of a DWA message (DWA1) |
DWA message ready to be sent | Response | Device-Watchdog-Answer Trigger Point 10; occurs just prior to sending the DWA message (DWA10) |
DPR message received from connection | Request | Disconnect-Peer-Request Trigger Point 1; occurs upon receipt of a DPR message (DPR1) |
DPR message ready to be sent | Request | Disconnect-Peer-Request Trigger Point 10; occurs just prior to sending the DPR message (DPR10) |
DPA message received from connection | Response | Disconnect-Peer-Answer Trigger Point 1; occurs upon receipt of a DPA message (DPA1) |
DPA message ready to be sent | Response | Disconnect-Peer-Answer Trigger Point 10; occurs just prior to sending the DPA message(DPA10) |
Execution Trigger Name | Message Type | Triggering Point |
---|---|---|
Diameter request message ready to be forwarded to application | Request | Request Trigger Point 4; occurs just prior to the invocation of a DSR application (RTP4) |
Diameter request message received from application | Request | Request Trigger Point 6; occurs immediately after exiting a DSR application (RTP6) |
Diameter answer message ready to be forwarded to application | Response | Answer Trigger Point 4; occurs just prior to the invocation of a DSR application (ATP4) |
Diameter answer message received from application | Response | Answer Trigger Point 6; occurs immediately after exiting a DSR application (ATP6) |
The Diameter > Mediation > Triggers [Insert] page opens to associate a new Rule Set with the Trigger. See Associating a Rule Set with a Trigger.
The association of the Rule Set with the Trigger can be removed, and the Rule Set Name is deleted from the list for the Trigger. See Removing the Association of a Rule Set with a Trigger