STIR/SHAKEN Information in CDRs

The SBC adds CDR information to the appropriate RADIUS, Diameter and CSV call detail records documenting STIR/SHAKEN activity on the system. The attribute value pairs (AVP) the system uses to populate RADIUS and/or DIAMETER CDRs are similar in nature and data. You can also configure local CSV CDRs to collect and retain call data, including STIR/SHAKEN information.

For RADIUS, the system populates AVPs within extensions carried by VSA 249, a custom VSA used to carry multiple extensions. For DIAMETER, the system populates these AVPs within ACME-specific DIAMETER attributes for distribution by DIAMETER ACRs, according to DIAMETER protocol.

• Stir-Signed-Request (RADIUS VSA ID 249, ext 11 and ACME DIAMETER Attribute 104, and Local CDRs)—This AVP indicates that the SBC has sent the signing request to the STI-AS and received a response. Values for this AVP, applicable to INTERIM and STOP CDRs, mean:
  • 1— The SBC has signed the INVITE.
  • 0—The SBC has not signed the INVITE.
  • 2—Signing is not applicable for the INVITE.
• Stir-Signed-Request-Exception-Id (RADIUS VSA ID 249, ext 12 and ACME DIAMETER Attribute 105, and Local CDRs)—This AVP indicates that the SBC did not sign the INVITE because of a failure response from the STI-AS and uses this AVP to include the cause code or HTTP error response code in the CDR. The SBC supports this AVP for INTERIM and STOP CDRs.

• Stir-Verified-Request (RADIUS VSA ID 249, ext 13 and ACME DIAMETER Attribute 106, and Local CDRs)—This AVP indicates that the SBC has sent the verification request to the STI-VS and received a response. Values for this AVP, applicable to START, INTERIM and STOP CDRs, mean:
  • 1— The SBC has verified the request.
  • 0—The SBC has not signed verified the request.
  • 2—Request verification is not applicable for the call.

• Stir-Verified-Request-Exception-Id (RADIUS VSA - 249, ext 14 and ACME DIAMETER Attribute 107, and Local CDRs)—This AVP indicates that the SBC did not verify the request because of a failure response from the STI-VS. AVP values include the cause code or HTTP error response code. The SBC supports this AVP for START, INTERIM and STOP CDRs.

Note:

When determining how you want to configure CDR collection, bear in mind how XSR output changes when the cdr-output-inclusive parameter is enabled or disabled.

See the SBC Accounting Guide for further detail about CDR generation and output detail.

Note:

You can refine the verstat included in CDRs during verstat retrieval process using the verstat-delimiter option in a sti-server. Specifying this delimeter can ensure you include the verstat only, as opposed to the entire verstat response.

Verstat Delimiter

For custom or generic verstat values, the SBC uses the first 30 chars for the verstat as the value it inserts into the “Sti-Vs-Verstat” attribute in the CDR. The system stores 30 bytes and truncates the remaining part. You can further define the contents of the CDR by configuring the verstat-delimiter option in each sti-server. You can also use this option to ensure accurate matches during call rejection during verification procedures.

You configure this option by specifying your desired delimiter, such as a semi-colon.

ORACLE(sti-server)+options verstat-delimiter=;

This configuration example specifies that the CDR value includes verstat characters up to the first semi-colon. The examples below present population behavior by the SBC:

• Behaviors when you set the verstat-delimiter option:
  • If the sti-vs response has the verstat=TN-Validation-Passed

    The Sti-Vs-Verstat in the CDR would be “TN-Validation-Passed”

  • If the sti-vs response has the verstat=TN-Validation-Passed;attest=A;origid=1cab14fd-7c29-4c95-9177-a8317bb0bbbb

    The Sti-Vs-Verstat in the CDR would be “TN-Validation-Passed”

  • If the sti-vs response has the verstat= No-TN-Validation-Custom1234567891011

    The Sti-Vs-Verstat in CDR would be “No-TN-Validation-Custom1234567“

  • If the sti-vs response has the verstat=Custom-verstat;attest=A;origid=1cab14fd-7c29-4c95-9177-a8317bb0bbbb

    The Sti-Vs-Verstat in CDR would be "Custom-verstat”

• Behaviors when you do not set the verstat-delimiter option:
  • If the sti-vs response has the verstat=TN-Validation-Passed

    The Sti-Vs-Verstat in the CDR would be "TN-Validation-Passed"

  • If the sti-vs response has the verstat=TN-Validation-Passed;attest=A;origid=1cab14fd-7c29-4c95-9177-a8317bb0bbbb

    The Sti-Vs-Verstat in the CDR would be "TN-Validation-Passed;attest=A;"

  • If the sti-vs response has the verstat= No-TN-Validation-Custom1234567891011

    The Sti-Vs-Verstat in the CDR would be "No-TN-Validation-Custom1234567"