Troubleshooting
Learn how to test, debug, and optimize your integration using Caller ID Name (CNAM) in RiskOS™.
Common errors
The table below outlines common errors that may occur when using Caller ID Name (CNAM) in RiskOS™. These issues can result from configuration gaps, carrier limitations, or outdated CNAM data. Understanding these patterns can help you fine-tune workflows, reduce false positives, and apply appropriate fallback strategies.
| Issue | Explanation | Suggested fix |
|---|---|---|
| CNAM not available in workflow | CNAM may not be enabled for your account. | Contact your Account Manager to have CNAM enabled. |
| Invalid API key error | The API key provided is incorrect, malformed, or expired. | Confirm you are using the correct RiskOS™ API key. Remove typos, extra spaces, or old keys. |
Empty or missing callerName | Some carriers do not support CNAM; mobile or VoIP numbers may not return it. | This is expected in limited coverage areas. Use fallback strategies when caller name is missing. |
Incorrect or unexpected callerName | CNAM databases may be outdated or differ across providers. | Cross-check CNAM with other RiskOS™ enrichments or alternate data sources. |
Updated 5 months ago