Genesys Cloud - Main

STIR/SHAKEN attestation is generated by the originating carrier and typically passed through the SIP signaling (for example in the Identity header).

Genesys Cloud itself does not currently expose the STIR/SHAKEN attestation level as a native attribute in Architect or interaction details. Because of that, it's usually not possible to directly use the attestation level inside a flow to validate whether a caller ID might be spoofed.

If your carrier or SBC supports STIR/SHAKEN, sometimes the attestation information can be inspected in SIP headers before the call reaches Genesys, or handled at the SBC level for screening or tagging calls.

So in practice, spoofing detection is typically handled by the carrier or SBC rather than by Genesys itself.

STIR/SHAKEN attestation is generated by the originating carrier and typically passed through the SIP signaling (for example in the Identity header).

Genesys Cloud itself does not currently expose the STIR/SHAKEN attestation level as a native attribute in Architect or interaction details. Because of that, it's usually not possible to directly use the attestation level inside a flow to validate whether a caller ID might be spoofed.

If your carrier or SBC supports STIR/SHAKEN, sometimes the attestation information can be inspected in SIP headers before the call reaches Genesys, or handled at the SBC level for screening or tagging calls.

So in practice, spoofing detection is typically handled by the carrier or SBC rather than by Genesys itself.