I think I've found a bug in the 15.5 build of 3cx. We often use ring groups to catch unanswered calls and this has always worked in the past but now we're getting some very strange behavior in the full 15.5 release. Example config: * Call comes into extension 1234 * Call is unanswered for 12 seconds and is forwarded to ring group 9001 * If call is unanswered by RG 9001 for 12 seconds go to extension 1234 voicemail This has worked since we first started using 3CX (v14) Currently what happens is: * Call comes into extension 1234 * If call is unanswered for 12 seconds, forward to ring group 9001 * All lines on RG9001 ring for a split second and then *one* of the extensions in the ring group show as connected on the "current calls" window and that extension shows as active. This is despite no one having answered that call and the phone of the extension in question showing no activity at all. The calling party hears ringback until the "ghost" connection happens and then it's just dead audio (but connected). This is a huge issue for us. I've tried recreating ring groups and restarting services/servers and it works consistently whenever you forward to a ring group. Inbound DIDs that route directly to a ring group work correctly until they are forwarded to a different ring group and then they have the same behavior.