I have seen that trouble. The quintum is not getting the answer that is especting, and is sending a “storm” of requests.
It will not stop even if you power down the quintum. When you restore power, it start all over.
Do this test.Go to the radius config, change the radius user parameter “accountingtype” to cero.
Submit the entry and see if that stops the sending of data.
If that is the case, the Quintum is not getting the expected response from the raius billing , and keep trying for what seems to be hours.
The trouble is on the billing. When I got a good billing system, the trouble went away.
Now, I agree that it should be a timeout, something like 20 requests or so, but seems to be an unfixed bug on the Quintum tenors.