1. Accounting Guide
  2. CDR Attribute Reference
  3. Oracle RADIUS Acme-Extended-Attributes VSAs
  4. STIR/SHAKEN Attributes

STIR/SHAKEN Attributes

This table lists and describes the STIR/SHAKEN attributes used for RADIUS CDRs. The table includes attribute name, attribute description, attribute value, attribute value type, and the list of CDR message types for which the value is captured.

Attribute Name Attribute Description Attribute Value Attribute Value Type Messages
Acme-Stir-Signed-Request

This AVP indicates that the SBC has sent the signing request to the STI-AS and received a response. Values for this AVP mean:

  • 1— The SBC has signed the INVITE.
  • 0—The SBC has not signed the INVITE.
  • 2—Signing is not applicable for the INVITE.
 249, extension 11 String

START

INTERIM

STOP
Acme-Stir-Signed-Request-Exception-Id This AVP indicates that the SBC did not sign the INVITE because of a failure response from the STI-AS. It includes the ATIS defined service and policy exception id (e.g. SVC4000, SVC4001, POL4050). 249, extension 12 String

START

INTERIM

STOP
Acme-Stir-Verification-Request

This AVP indicates that the SBC has sent the verification request to the STI-VS and received a response. Values for this AVP 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.
 249, extension 13 String

START

INTERIM

STOP
Acme-Stir-Verification-Request-Exception-Id This AVP indicates that the SBC did not verify the request because of a failure response from the STI-VS. It includes the ATIS defined service and policy exception id (e.g. SVC4000, SVC4001, POL4050). 249, extension 14 String

START

INTERIM

STOP
Stir-VS-Verstat The SBC populates this AVP with the verstat values the SBC includes in the SIP INVITE following the Stir Shaken trigger. Potential values include TN-Validation-Passed, TN-Validation-Failed or No-TN-Validation 249, extension 15 String

START

INTERIM

STOP
Stir-VS-Reason The SBC populates this AVP with received reason information. 249, extension 16 String

START

INTERIM

STOP
Stir-TN-Used-For-AS-VS-Request This AVP contains the TN number captured by the SBC. TN selection uses the following priority:
  1. From the Tel PAI (if present)
  2. From the SIP PAI (if present, and Tel PAI is not present)
  3. From the “From” header if both Tel and SIP PAI are not present.
 249, extension 17 String

START

INTERIM

STOP
Stir-Div-Signed-Request Upon sending the DIV signing request to the STI-AS and receiving a 200 OK successful response from STIR-AS, the SBC enumerates the results in this AVP as follows:
  • 1—indicates DIV signing the INVITE
  • 0—indicates no DIV signing the INVITE
  • 2—indicates DIV signing is not applicable on the INVITE
249, extension 18 String

START

INTERIM

STOP
Stir-Div-Verified-Request Upon sending the DIV verify request to the STI-AS and receiving a 200 OK successful response from STIR-VS, the SBC enumerates the results in this AVP as follows:
  • 1—indicates DIV verification the INVITE
  • 0— indicates no DIV verification the INVITE
  • 2—indicates DIV verification is not applicable on the INVITE
249, extension 19 String

START

INTERIM

STOP
Stir-VS-Invite-State

Indicated SBC action on call based on STIRVS rejection configuration.

  • Continued
  • Terminated
 249, extension 20 String

START

INTERIM

STOP

STIR/SHAKEN attributes are embedded under one extended Radius AVP.

  • type = 26 (vendor-specific)
  • length = ...
  • vendor-id = 9148 (acme)
  • vendor-type = 249 (extended-attributes)
  • vendor-length = ...
  • vendor-data = { x-attr-type (16-bit), x-attr-len (16-bit), x-attr-data (variable) }

An example of an AVP presenting the Acme-Stir-Signed-Request attribute indicating the SBC has signed the INVITE appears as follows: 

x-attr-type = 1 (Acme-Stir-Signed-Request) [1 byte]
x-attr-len = … [1 byte] 
x-attr-data = { version[1 byte], Acme-Stir-Signed-Request [depending on length]}