I can’t seem to figure out why the aggregated call detail records exported via the /api/v2/analytics/conversations/details endpoint are systematically excluding approximately 12% of our outbound calls that terminated with a 401 Unauthorized response during the SIP digest authentication handshake with our primary carrier in AP-SE-2. We are managing fifteen BYOC trunks configured for automatic failover, and while the real-time monitoring dashboard in the Admin UI correctly flags these authentication failures as distinct events with carrier-specific error codes, the historical analytics dataset returned by the API simply omits these records entirely when filtering by date range greater than seven days. This discrepancy is critical for our monthly reconciliation process with the carrier, as we need to distinguish between genuine network timeouts and credential mismatches. The environment is running on SDK v2.14.0, and we have verified that the trunk configuration includes the correct realm and nonce handling parameters. When querying the /api/v2/trunks endpoint directly, the SIP credentials appear valid and recently rotated without any latency issues noted in the audit logs. However, the analytics aggregation logic seems to drop these failed SIP transactions before they are persisted into the long-term storage buckets. We have tested this behavior across multiple regions, and the issue is isolated to AP-SE-2, suggesting a potential regional quirk in how the analytics engine parses SIP error codes for BYOC trunks specifically. The missing data affects our ability to generate accurate carrier performance reports, as the 401 errors are being silently discarded rather than categorized under the appropriate error bucket. We need to understand if there is a specific query parameter or filtering logic we are missing that would force the API to include these authentication failure records in the dataset, or if this is a known limitation of the analytics pipeline in this region that requires a workaround.