Looking for advice on Bot Analytics API mismatch with BYOC Trunk Metadata

Architect & Flows
1

Looking for advice on why the /api/v2/conversations/bots endpoint returns null for sip_call_id when filtering by our APAC BYOC trunks. The standard voice analytics work fine, but the bot session correlation breaks during peak hours in Singapore.

Environment details:

  • 15 BYOC Trunks (SIP 2.0)
  • Genesys Cloud Region: APAC
  • SDK Version: 4.2.1
  • Error: 200 OK but sip_call_id is null for 40% of records

Is this a known limitation with how bot metadata merges with BYOC routing logic?