Event ID#30053 Call loop way around

[midwest1]

Since v20, several of my servers have started triggering ID#30053 -"A call placed by Ext.*** was terminated due to a loop detected. Please verify call routing settings."
I have several ring groups triggered to receive door alarms; staff. It's not call forwarding, it's just a ring group/s where these calls sometimes can be ringing for more than 60 seconds ringing or loop to another ring group. I'm looking forward to a way to disable or tweak the parameter that triggers #loop detection well as a clear understanding of how to see in deep details how it was triggered.

• In V18, your ring groups could ring internally or externally with different timeouts; V20 enforces stricter loop detection. If a call is forwarded between ring groups in a way that creates a loop, 3CX now immediately stops the call with the 30053 warning
• The default behavior is to detect loops based on routing hops (e.g., RG1 → RG2 → RG1), and then block the call after hitting the loop threshold.

 

[paulodagraca]

Hello @midwest1,

Can you not just move to a queue, where the call can be waiting for mutch longer?
Would that work for your setup, or is there some other limitation?

Paulo

 

[midwest1]

Hello @midwest1,

Can you not just move to a queue, where the call can be waiting for mutch longer?
Would that work for your setup, or is there some other limitation?

Paulo

Great idea! I will duplicate the case scenario using "Queue" instead standard RG. -- Thanks,