Source note · Robocall mitigation and RMD obligations
Webex Calling reads the STIR/SHAKEN verification result from the verstat parameter in the SIP P-Asserted-Identity header, with values TN-Validation-Passed, TN-Validation-Failed and No-TN-Validation, and maps attestation levels A, B and C to Verified Caller, Possible Spam and Potential Fraud.
Checked 2026-09-16
- Vendor
- Cisco
- Product
- Webex Calling
- Subsystem
- caller ID validation
- Deployment
- multi-tenant
- Region
- united states and canada
- Release range
- current as of access date
- Checked
- 2026-09-16
Sources
- Secure Calling and Spam mitigation — Cisco Systems, Inc. (help.webex.com) · tier 2 current vendor documentation · Secure calls and spam mitigation - caller ID validation section
Cite this note
APA
WarmTransfer. (2026, September 16). Robocall mitigation and RMD obligations: source note robocall-mitigation-webex-verstat. WarmTransfer. https://warmtransfer.net/knowledge/claims/robocall-mitigation-webex-verstat
BibTeX
@misc{warmtransfer-claim-robocall-mitigation-webex-verstat,
title = {Robocall mitigation and RMD obligations: source note robocall-mitigation-webex-verstat},
author = {{WarmTransfer}},
year = {2026},
url = {https://warmtransfer.net/knowledge/claims/robocall-mitigation-webex-verstat},
note = {Source note robocall-mitigation-webex-verstat, checked 2026-09-16}
}