When you enable the man-compliance option and the reason-json-sip-translation parameter, the SBC can populate three additional data objects within its validation process for 3GPP deployments. The system uses these objects to collect verification detail, from which it can determine how to populate CDRs. The changes implemented by this configuration apply to all CDR types.

The SBC packs these objects in RADIUS, DIAMETER and Local CSV CDRs in compliance with the MAN 2.0 requirements. When you enable cdr-output-inclusive and the man-compliance option, the system populates CDRs in this section with the applicable data.

• Stir-VS-Attest—Populate the attest claim value from the STI-VS verification response within the JSON body for 3GPP deployments. If there is no attest claim in provided by the verification response, the system populates the Sti-VS-Attest field with empty values in all CDRs.
• Stir-Div-VS-Verstat—This object collects the values, enclosed in double quotes, for each verified div PASSporT, separated by commas. In addition:
  • If both verstatValue and divResult verstatValue are present:
    • Populate verstatValue with “stir-vs-verstat”
    • Populate divResult verstatValue with “stir-div-vs-verstat”
  • If only verstatValue is present with no divResult, but ppt=div is there:
    • Populate verstatValue with “stir-vs-verstat”
    • Populate verstatValue with “stir-div-vs-verstat”
  • If a verstatValue is present with no divResult, and ppt=div is not there, populate verstatValue with “stir-vs-verstat” only.
• Stir-Div-VS-Reason—This object collects the reason value with the concatenation of the "reasoncode" and "reasontext" obtained from each Div Verify result of JSON body. The system collects the reasoncode and reasontext for Div Verify result, even if they are same.

  The SBC also maintains its existing behavior when reasoncode or reasontext is missing in the JSON body. (Compare the current implementation of the Sti-VS-Reason CDR attribute with ATIS mode).