The Diameter Routing Function and invoked DSR Applications record detailed information about each Diameter transaction - called transaction metadata. Each metadata record describes an important event in the lifetime of a Diameter transaction. Metadata appears in the Trace Transaction Record (TTR) in the order that the metadata-generating events actually occurred. Together, all of the metadata records combine to document the processing performed on the entire transaction, and can later be used to provide diagnostic information when performing troubleshooting. Metadata is recorded to a TTR for each transaction so that, even if the transaction is selected to be sent to IDIH at an Answer Troubleshooting Trigger Point (TTP-IA or TTP-EA), the metadata for all of the messages in the transaction will be present.
FABR will record the Application-specific metadata events described in Table 1.
| Event | Instance Data | When Recorded |
|---|---|---|
| Address Resolution Match found |
|
After FABR searches and finds a valid Routing Entity address in an ingress Request message using a prioritized set of AVPs associated with the highest priority Routing Entity Type assigned to the Address Resolution order pair (Diameter Application ID, Command Code). |
| DP Query Event Sent to DP for processing |
|
When FABR sends a DP query event to the DP for Destination address resolution. |
| DP Response Event Received from DP |
|
When FABR receives a response to a previous DP query. |
| Routing Exception |
|
After any Routing Exception is encountered. |
| DP Query Failure |
|
After any DP Query failure other than a response timeout is encountered. |
| DP Response Timed out |
|
When FABR times out waiting to receive a response from the DP to a previous Destination address resolution query. |