What’s the best way to handle SIP trunk 408 Request Timeout errors when the Genesys Cloud Data Action attempts to create a ServiceNow incident record before the media session is fully established?
The Architect flow triggers the Data Action on the call_connected event, but the ServiceNow REST API call introduces a 2-second latency that causes the SIP INVITE to time out at the carrier level. The webhook payload arrives, but the call drops before the screen pop can occur.
Is there a specific timeout configuration in the Data Action settings or a recommended pattern to defer the ServiceNow ticket creation until after the SIP session is stable?