SIP 408 Timeout on /api/v2/telephony/providers/edge/connections during JMeter spike

Voice & Telephony
1

Looking for advice on SIP trunk stability when we hit 500 concurrent calls in our load test. The connections drop with a 408 Timeout on the edge connections endpoint after the ramp-up period finishes.

Our setup uses JMeter 5.4.1 with a 60-second ramp-up. The target environment is Genesys Cloud US-East. We see this happen consistently every time the load spikes. The logs show the SIP trunk registration failing right when the call volume peaks.

2

You need to align your test parameters with the Performance Dashboard’s view of queue activity.

  • Reduce the ramp-up period to prevent immediate edge connection saturation.
  • Monitor the “Handled In” metric for discrepancies during the spike.