Is it possible to override the default SIP trunk concurrent call limits within the Architect flow for high-volume load testing scenarios? We are seeing dropped calls when hitting 200 simultaneous sessions on a single trunk configuration.
Running JMeter 5.6 against a US1 region environment. The setup uses a simple queue with predictive routing disabled to isolate the trunk capacity. Errors appear as SIP 486 Busy Here after the threshold is crossed.
Need to validate if this is a hard platform limit or a configurable setting. Any insights on scaling SIP trunk throughput for performance benchmarks would be appreciated.