Quick question about SIP trunk stability under load in the Singapore region.
- Running JMeter 5.6 to simulate 200 concurrent SIP registrations via the platform API.
- Hitting 403 Forbidden errors on POST /api/v2/telephony/providers/edges after roughly 150 connections.
- The error payload returns
"errorCode": "invalid_authentication"even though the credentials are valid. - Verified the API rate limits in the admin console, but the requests are spaced out with a 500ms delay, well below the threshold.
- Switched to the US-East region and the same script works fine for 500 concurrent sessions without any 403s.
- Is this a regional limitation for the Asia/Singapore edge nodes regarding concurrent SIP registration attempts?
- Or is there a specific header missing in the request payload that is stricter in the APAC environment?
- The WebSocket connection for the initial handshake seems fine, it is purely the SIP trunk registration endpoint failing.
- Looking for any known issues or configuration tweaks for high-volume SIP trunk provisioning in this specific region.