5.5.2 Creating a Trace

Perform the following procedure to create a Trace:

1. Select Diameter, Troubleshooting with IDIH, and Configuration, and then Traces.
2. Click Insert. Navigate to Diameter, Troubleshooting with IDIH, and Configuration, and then Traces [Insert] screen appears.
3. Enter the Trace Name in the trace name field.

   The name must meet the following requirements:

   • Maximum length of 32 characters.
   • Valid characters are alphanumeric and underscore, must contain at least one alpha and must not start with a digit.
4. Select a Trace Location by selecting either Site Trace or the Network Trace.
5. Select a Content Type from the Content Type options.

   There are seven Content Types supported:

   1. Non-success answers
   2. Requests
   3. Answers
   4. AdHoc Requests
   5. Ad Hoc Answers
   6. User Identity
   7. Equipment Identity

   Table 5-4 Content type

   Field (* indicates a required field)	Description
   Content Type*	The Diameter message content to be matched for this trace. The combination of content type or content values specify the content elements and content values that a candidate message must match before the transaction that the message belongs to is sent to IDIH. Content Type: Non-success answers: answers with (Experimental) Result-Code>= 3000, or any message with the E-bit set. Ad Hoc Requests: any request that matches the specified content values. Ad Hoc Answers: any answer that matches the specified content values. User Identity - any message that contains the specified IMSI or MSISDN. AVPs searched for the specified IMSI/MSISDN value are automatically determined by the application ID(s) selected. Equipment Identity: any message that contains the specified IMEI. AVPs searched for the specified IMEI value are automatically determined by the application ID(s) selected. Range: Non-success answers, Requests, Answers, Ad Hoc, Requests, Ad Hoc Answers, User Identity, Equipment Identity. Default: -Select
   Content Values	After selecting the content type, the screen displays the content values for selecting content elements and entering content values.

   Table 5-5 Trace Scope

   Field (* indicates a required field)	Description
   Scope Type*	The scope used for this trace. Scope Type: Connection: Messages arriving or leaving on specified connection are candidates for tracing. Peer: Messages arriving or leaving on specified peer are candidates for tracing. DSR Application: Messages going to or returning from specified DSR application are candidates for tracing. All: - All messages are candidates for tracing. Range: Connection, Peer, DSR, Application, All. Default: Select
   Scope Value	The scope value used for this trace. Selection values will be populated based on the Scope Type selected.

   Table 5-6 Trace Duration

   Field (* indicates a required field)	Description
   Number of Matches*	Number of Matches: stops the trace, after matching this many messages. Range: 1-1000 Default: N/A
   Time of Duration*	Time: stop the trace after it has been active for this amount of time (HH:MM:SS). Range: 00:00:01 - 96:00:00 Default: N/A
   Notes	Descriptive information about the trace. Range: A 255-character string. Default: N/A

   The Content Type field determines what Content Values are available. If the Content Type is set to Non-success answers, then no other content values are available. If the Content Type is set to Requests, then you may select an Application-ID, Command-Code, Origin-Host, Origin-Realm, Destination-Host, and or Destination-Realm. Application-ID, and Command-Code option, which contain a pre-defined list of supported Diameter interfaces. Additionally, all other parameters may be left blank as wildcards.

   If the Content Type is set to Answers, then you may select an Application-ID, Command-Code, Origin-Host or Origin-Realm, Application-ID, and Command-Code option, which contain a pre-defined list of supported Diameter interfaces. Additionally, all other parameters may be left blank as wild cards.

   If the Content Type is set to Ad Hoc Requests, then you may select an Application-ID, Command-Code, Origin-Host, Origin-Realm, Destination-Host, and or Destination-Realm. An optional content value is available to select an AVP (Attribute Value Pair) to be checked. Application-ID and Command-Code options contain a pre-defined list of supported Diameter interfaces to which you may also add. Additionally, all other parameters may be left blank as wild cards.

   Note:

   • When the Content Type is set to Ad Hoc Requests or Ad Hoc Answers, an optional content value is available to select an AVP to be checked. This optional AVP is based on what AVPs are configured in the AVP Dictionary. For further information about the AVP Dictionary, see Oracle Communications Diameter Signaling Router Diameter User Guide
   • For a non-grouped AVP all operators for the specified data type are allowed. For a grouped AVP, exists and does not exist operators are allowed only for the parent AVP. Checking is not allowed for either grouped or non-grouped Child AVPs.

   If the Content Type is set to Ad Hoc Answers, then you may select an Application-ID, Command-Code, Origin-Host or Origin-Realm. Additionally, an optional content valueis available to select an AVP to be checked. Application-ID and Command-Code are selected from dropdown list and contain a pre-defined list of supported diameter interfaces to which you may also add. Additionally, all other parameters may be left blank as wild cards.

   If the Content Type is set to User Identity, you may select an Application-ID. The Application-ID option lists a pre-defined list of supported Diameter interfaces, although you cannot add anything new to the list.

   Note:

   After an Application-ID is selected, you can specify a user in the associate AVP as the criteria for selecting messages, which is identified by either IMSI or MSISDN.

   If the Content Type is set to Equipment Identity, then you may select an Application-ID. The Application-ID option lists a pre-defined list of supported Diameter interfaces, although you cannot add anything new to the MSISDN list.

   Note:

   After an Application-ID is selected, you can specify equipment in the associated AVP as the criteria for selecting messages, which is identified by IMEI.
   1. Select the Content Value with appropriate parameter, operator, and value.
   2. Select the Scope Type.

      The scope for a trace can be for a specific Connection, specified Peers, specified DSR Applications, or All messages.

   3. Select the Scope Value.

      The scope value is determined by which Scope Type is selected.

   4. Enter the Number of Matches.

      Note:

      A maximum of 1000 matches is permitted.
   5. Enter the Time Duration in HH:MM:SS format.

      Note:

      The duration can be up to 96 hours.
   6. Click Submit.