17 STIR/SHAKEN Client

STIR/SHAKEN is a framework of interconnected standards the ESBC can use for authenticating calling parties in VoIP calls. To support STIR/SHAKEN, the ESBC implements a STIR/SHAKEN REST Client, which, upon receiving an initial out-of-dialog SIP INVITE, sends a REST request to a STIR server for attestation or verification of the calling party identification. When you enable the STIR/SHAKEN entitlement, you can configure the ESBC to perform the associated functions. The ESBC performs the functions of its STIR/SHAKEN client when triggered by the SIP INVITE method only.

Note:

The STIR/SHAKEN acronym combines the Secure Telephony Identity Revisited (STIR) and Secure Handling of Asserted information using Tokens (SHAKEN) standards acronyms to create this solution framework name.

You configure the STIR/SHAKEN REST Client functionality by creating server objects with the sti-server and the sti-server-group parameters and applying them to session-agent, sip-interface and realm-config elements, using this order to determine server selection precedence. In addition, the session-agent, sip-interface and realm-config elements provide parameters that allow some customization.

You configure and obtain operational statistics via the ACLI, ACP (and Oracle's session control management tools) and REST. You can also access client operational information via the HDR functionality, logs, and alarms on the ESBC, as well as from SNMP walks, SNMP traps and Syslog configurations. Finally, the ESBC also provides calling party authentication in CDRs.