Transaction Metadata Recording for Integrated DIH (IDIH)

Integrated DIH (IDIH) can be used to capture detailed information about selected Diameter transactions, and transmit this information to DIH for further analysis.

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 DIH at an Answer Troubleshooting Trigger Point (TTP-IA or TTP-EA), the metadata for all of the messages in the transaction will be present.

The functions of IDIH are described in the Integrated DIH User's Guide and Help.

MD-IWF does not support IDIH.

DM-IWF will record the Application-specific metadata events described in Table 3-1.

Table 3-1 DM-IWF Metadata-Generating Events

DM-IWF Event	Metadata Fields			When Recorded
	Type	Scope	Instance Data
Diameter-to-MAP Transactions
Sent Egress Request to SS7-MP	SS7-MP Request sent	App Data	Transaction ID (such as 45631) Payload	Immediately before the egress Request is sent to ComAgent.
D-to-M Request discarded	Message Discarded	App Data	Discard Reason (such as DM-IWF PTR pool exhausted)	DM-IWF discards a Request message received from DRL.
Ingress Answer received from SS7-MP	SS7-MP Answer received	App Data	Transaction Id (such as 45631) SS7-MP IP address (such as 47.240.10.3) Payload	DM-IWF received an ingress Answer message from SS7-MP
A received Answer did not match a pending transaction	SS7-MP Answer Matching Failed	App Data	None	Immediately after PTR search fails
DM-IWF Routing Exception	DM-IWF Routing Exception	App Data	Routing Exception Type (such as Internal Processing Error) Routing Exception Action (such as Abandon Request)	When a routing exception is applied by DM-IWF
MD-IWF Routing Exception	MD-IWF Routing Exception	App Data	None	When DM-IWF applies Apply Unavailability Action routing exception on behalf of MD-IWF.
MAP-to-Diameter Transactions
Ingress Request received from SS7-MP	SS7-MP Request received	App Data	Transaction ID (such as 45631) SS7-MP address (such as 47.240.10.3) Payload	Immediately after a Request is received from SS7-MP.
Egress Answer sent to SS7-MP	SS7-MP Answer Sent	App Data	Transaction ID (such as 45631) SS7-MP address (such as 47.240.10.3) Payload	Immediately after DM-IWF sends a Diameter Answer to ComAgent successfully.
D-to-M Answer discarded	Message Discarded	App Data	Discard Reason (such as Failed to create IWF Answer)	DM-IWF discards an Answer message received from DRL.