My configuration keeps failing correctly for the Bot Analytics API when querying sessions routed through our 15 APAC BYOC trunks. The /api/v2/conversations/bots endpoint returns null for sip_call_id, breaking our correlation logic despite voice analytics working fine.
- Verified SIP registration and failover logic on all trunks; no drops detected in Genesys Cloud logs.
- Confirmed outbound routing uses correct carrier credentials and number management settings for the APAC region.