Stuck on a discrepancy in the Quality Management reporting data when our primary BYOC trunks failover to secondary carriers in the Asia/Singapore region. The issue manifests as incomplete interaction data in the /v2/analytics/conversations/summary endpoint, specifically missing call disposition codes for interactions routed through the secondary trunk during the failover window.
Steps to reproduce:
- Initiate a controlled failover from the primary BYOC trunk (Carrier A) to the secondary BYOC trunk (Carrier B) in the Singapore region.
- Generate 50 concurrent inbound calls routed through the secondary trunk during the transition period.
- Query the /v2/quality/interactions endpoint for interactions created within the last 15 minutes.
- Compare the returned interaction list with the raw SIP call detail records (CDRs) from the carrier.
The API response shows a 10% loss in interaction records, with missing disposition codes defaulting to ‘unknown’. This impacts our real-time quality monitoring dashboards. We are using Genesys Cloud API v2 and have verified that the SIP registration status remains stable on the secondary trunk. Is this a known limitation with BYOC failover affecting quality data ingestion, or is there a configuration tweak in the outbound routing or number management settings that we might be missing? The latency spike seems to correlate with the SIP re-registration delay.