Can’t quite understand why the /api/v2/analytics/conversations/details/realtime endpoint omits carrierId metadata for bot-initiated sessions on our AP-SE-2 BYOC trunks.
The payload structure mirrors standard human-agent interactions, yet the carrier-specific tags vanish once the conversation enters the AI bot flow.
SIP registration is stable, and outbound routing logs confirm the traffic traverses the correct trunk before handoff to the bot engine.
Any insight into whether this is a known limitation for bot analytics in this region?
Check the JMeter sampler for includeBotData=true. The realtime analytics endpoint often strips carrier metadata for bot sessions unless explicitly requested. Also verify the BYOC trunk ID matches the routingAddress in the SIP INVITE.
| Parameter |
Value |
| Endpoint |
/api/v2/analytics/conversations/details/realtime |
| Query Param |
includeBotData=true |
| Trunk ID |
Must match SIP INVITE routingAddress |
If the payload still lacks carrierId, check for 429s on the analytics API during your load spike. The Singapore edge has strict rate limits for concurrent analytics queries.