Need some troubleshooting help with a 503 Service Unavailable error when pushing traffic through our BYOC Edge setup.
I am running JMeter 5.6.2 from Asia/Singapore to test our Genesys Cloud BYOC edge capacity. The goal is to simulate a spike of 100 concurrent inbound calls using the SIP plugin. With 10 threads, everything works fine. Calls connect, ringbacks are received, and the flow in Architect triggers correctly. However, as soon as I ramp up to 25 threads, the JMeter sampler starts returning 503 errors immediately after the INVITE is sent. The edge logs show the requests hitting the load balancer but no corresponding SIP dialogs are established in Genesys Cloud. I checked the network connectivity and latency to the edge IP, which is stable at 45ms. The JMeter config uses a constant throughput timer to space out the requests, but the 503s seem to happen regardless of the pacing. Is there a specific connection limit on the BYOC edge for concurrent SIP INVITEs that I am hitting? Or could this be a DNS resolution issue on the edge side? I am not seeing any 429 rate limit headers, just the generic 503. The environment is a standard BYOC deployment with no custom firewall rules blocking SIP ports. Any insights on how to diagnose if this is an edge capacity issue or a misconfiguration in my JMeter script would be appreciated.