1. Configuration Guide
  2. STIR/SHAKEN Client
  3. HTTP Client Operating Modes
  4. Operating Under the 3GPP Mode

Operating Under the 3GPP Mode

As discussed, the STIR/SHAKEN Client Operation section applies in full to ATIS mode operation. To a great extent, those behaviors also apply to 3GPP mode. But there are several differences between 3GPP and ATIS mode. Use this section as a compliment to STIR/SHAKEN Client Operation when reviewing 3GPP mode.

The SBC creates and processes SHAKEN as well as DIV PASSporT(s) when configured as an authentication entity, and you set the http-rest-type parameter within the applicable sti-server to 3GPP. DIV PassporTs apply to call flows with diversion. When configured for 3GPP and STIR verification, the SBC ignores and passes any PASSporT type that it cannot identify as SHAKEN or DIV.

Categories of operational differences between 3GPP and ATIS include:

  • Available configuration parameters
  • Identifying SHAKEN and DIV passports

    Note:

    The PASSporT type is specified by the “ppt=…” tag". The SBC allows tag formatting that uses either no quotes or double quotes.
  • Behavior when presented with both SHAKEN and DIV passports
  • Behavior when processing DIV passports

When you set the http-rest-type to 3GPP within a sti-server, the SBC:

  • Implements behavior supporting both Shaken and DIV verification requests per 3GPP TS 24.229.
  • Implements behavior supporting both Shaken and DIV authentication requests per 3GPP TS 24.229.
  • Sends and receives version TS 24.229 format SHAKEN and DIV PASSporT messages, including:
    • Authentication Requests to the STI-AS
    • Authentication Responses from the STI-AS
      • During authentication of an INVITE that includes call diversion, the SBC creates SHAKEN as well as DIV PASSporT(s)
    • Verification Requests to the STI-VS
    • Verification Responses from the STI-VS
  • Uses the following configuration parameters in the sti-config to support 3GPP servers:
    • tn-retargeting—Values include disable (Default) or enable
    • verstat-comparison—Values include TN-Validation-Passed (Default), No-TN-Validation, TN-Validation-Failed, empty, or a list of values.
    • dest-comparison—Values include Request-URI (Default), andTo
    • check-duplicate-passports—Values include disable (Default) or enable