Product/Feature Brief
What's New
There is 1 new enhancement available in Call Reporting for the August 3, 2026 release:
Feature: CLIR (Calling Line Identification Restriction) Support in Call Reporting
Description: Call Reporting APIs now supports an optional CLIR indicator that identifies whether the caller requested their identity to be restricted. The new CLIR field is available when requested through the include_clir=true parameter and provides additional visibility into caller privacy settings. The enhancement is fully backward compatible and does not require changes to existing integrations unless partners choose to consume the new field.
Who It's For
This enhancement is specifically for Movius Carrier Partners and integration teams that:
Consume Call Reporting API data
Ingest CDR/QosInfo records
Build reporting, analytics, auditing, or compliance solutions using call detail records
Why It Matters (Customer & Business Value)
Enables visibility into caller identity restriction requests (CLIR)
Improves reporting and compliance capabilities for partner integrations
Maintains full backward compatibility with existing implementations
Supports future-proof integrations through optional and nullable field handling
Provides consistent CLIR information across both API responses and raw CDR/QosInfo feeds
Improves troubleshooting, reconciliation, and auditability of call records
Additional Implementation Notes
CLIR Values
| Value | Meaning |
|---|---|
| yes | Caller requested identity restriction (CLIR enabled) |
| no | Caller did not request identity restriction (CLIR disabled) |
| null / missing | CLIR status unknown; typically applies to historical records created before this feature was available |
Recommended Integration Approach
Support the optional include_clir=true request parameter.
Parse the clir field when present.
Treat missing or null values as unknown, not as no.
Consider storing CLIR as a discrete attribute with values:
yes
no
unknown
Preserve raw values for audit and troubleshooting purposes.
Backward Compatibility
Existing API integrations continue to function without modification.
The clir field is returned only when specifically requested.
Raw CDR/QosInfo feeds include CLIR as an additional key-value pair (clir=yes or clir=no) without any schema changes.
Historical records may not contain CLIR information and should be handled accordingly.
