1. Configuration Guide
  2. STIR/SHAKEN Client
  3. STIR/SHAKEN Client Statistics
  4. STIR/SHAKEN Information in CDRs

STIR/SHAKEN Information in CDRs

The ESBC 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 ESBC 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 ESBC has signed the INVITE.
    • 0—The ESBC 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 ESBC 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 ESBC 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 ESBC 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 ESBC has verified the request.
    • 0—The ESBC 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 ESBC 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 ESBC 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 ESBC Accounting Guide for further detail about CDR generation and output detail.