Running a JMeter 5.6 load test to validate SIP trunk capacity on Genesys Cloud US1. The goal is to simulate 100 concurrent outbound calls using SIP trunks. After 5 minutes of steady state, getting 408 Request Timeout errors on 20% of INVITE requests.
Setup:
- JMeter 5.6 with SIP plugin
- 100 concurrent threads
- 2-second ramp-up
- Genesys Cloud US1 region
- SIP trunk configured with 200 concurrent call limit
Error log:
2023-10-27 14:32:15,432 INFO o.a.j.p.s.sip.Sampler - INVITE sip:[email protected] SIP/2.0
2023-10-27 14:32:18,432 ERROR o.a.j.p.s.sip.Sampler - 408 Request Timeout
The SIP trunk shows 200 concurrent calls in Genesys Cloud admin console during the test. No errors in SIP trunk logs in Genesys Cloud. The issue seems to be related to API rate limits or WebSocket connection limits.
Has anyone seen similar 408 timeouts during high-concurrency SIP load tests? Is there a way to increase the SIP trunk capacity or adjust the rate limits? Need to validate call capacity planning for a client.
Any suggestions on JMeter config or Genesys Cloud settings to avoid these timeouts? Looking for best practices for SIP load testing at scale.