OK - let’s allow for a non-nefarious use (active shooter call tree, where you want to get the word out ASAP, but not exceed the system’s per-whatever limit). What is the effect of over-limit on a “per second” basis? Is it a billing issue? Does the ITSP block your access? What granularity are they computing the call-rate at? Is it averaged over time (even if that time is, say, a minute or six-seconds)? Is limiting the system to concurrent calls going to get you close enough?
If I have 1000 ‘workers’ at a ‘facility’ and want to send out a Shelter-In-Place/Stay Home/Come Get Your Kids voice message, I could easily exceed capacity without some kind of limiter. On the other hand, there’s got to be a way to change the perspective on the process where it’s not completely intractable.
I was trying to build a system like this for one of the local archdiocese schools a couple of years ago and found that 20 concurrent calls worked out pretty well to get the word out “in spec”. Could changing the focus of the request get you to a solution?
Six starts per second is a lot, but six concurrent calls is not, even if they are all started at the same second. There’s got to be an approach or different perspective that gets you where you want to go.