Looking for some advice on troubleshooting this persistent timeout issue when using a Data Action to enrich conversation attributes with carrier-specific SIP headers from our BYOC trunks. We are operating 15 trunks in the AP-Southeast-1 region. The Architect flow triggers a Data Action immediately after SIP ingress to fetch metadata from an internal REST endpoint. While the endpoint responds in under 200ms locally, the Genesys Cloud platform returns a 504 Gateway Timeout after exactly 10 seconds. The internal logs show the request was never received, suggesting the traffic is dropping within the Genesys boundary. We have verified outbound connectivity from the tenant and confirmed no firewall blocks on the destination IP. The payload includes the trunk_id and conversation_uuid. Has anyone encountered similar latency or blocking issues with Data Actions calling external endpoints from the AP-Southeast-1 region? Below is the JSON payload being sent:
{
"trunk_id": "b9c8d7e6-f5a4-3b2c-1d0e-9f8a7b6c5d4e",
"conversation_uuid": "12345678-abcd-efgh-ijkl-1234567890ab",
"sip_headers": {
"P-Asserted-Identity": "+6512345678",
"From": "<sip:[email protected]>"
}
}
The Data Action configuration uses HTTPS with default timeout settings.