Is it possible to configure Genesys Cloud to handle higher SIP INVITE rates without triggering 408 Request Timeout errors?
Running JMeter 5.6 with a custom SIP plugin to validate trunk capacity on US1 region. Setup involves 200 concurrent threads sending SIP INVITEs to a specific SIP trunk endpoint. The goal is to stress-test the inbound call routing logic in Architect.
With 50 threads, calls connect successfully. At 150 threads, latency spikes to >2000ms. At 200 threads, receiving consistent 408 Request Timeout responses from the Genesys Cloud SIP proxy. No 429 rate limits observed, just pure timeout. The backend application server handling the call logic is responsive and has no CPU spikes.
Environment details:
- Genesys Cloud US1
- JMeter 5.6
- SIP Trunk: Standard SIP trunk, no special codecs enforced
- Architect Flow: Simple flow with one IVR node and transfer to agent
The timeout suggests the SIP stack is dropping packets or unable to process the handshake fast enough. Is there a configuration limit on SIP INVITE processing rate per trunk that needs adjustment? Or is this a known limitation of the free/standard tier SIP capacity? Looking for any admin settings that might help stabilize the connection under load.