Stuck on a weird SIP registration timeout issue while stress testing our BYOC edge setup. We are running JMeter 5.6.2 from a Singapore-based instance to simulate high-volume agent logins against Genesys Cloud BYOC Edge 24.1.0. The goal is to validate SIP trunk capacity before our peak season. When we ramp up to just 200 concurrent threads simulating REGISTER requests, we start seeing a significant number of 408 Request Timeout responses instead of the expected 200 OK. The JMeter config uses a simple HTTP Request sampler pointing to the SIP signaling port, with a connection timeout of 3000ms and a response timeout of 5000ms. Interestingly, if we reduce the concurrency to 50 threads, all requests succeed with 200 OK in under 200ms. The error logs on the Genesys side are sparse, just showing generic SIP transaction timeouts. I have checked the network latency between the JMeter runner and the Edge node, which is consistently under 15ms, so it is not a network issue. I am also verifying that the SIP credentials are correct and that the user accounts are active. Is there a specific rate limit or connection threshold for SIP REGISTER requests on the BYOC Edge that I am hitting? Or is this a known issue with how Genesys handles concurrent SIP handshake processing at scale? I have tried adding a constant timer of 500ms between requests, which helps slightly, but we need to support much higher concurrency. Any insights into the underlying SIP server capacity or recommended JMeter configurations for SIP load testing would be appreciated. We are essentially trying to find the breaking point for agent registration capacity.