- Joined
- Oct 21, 2011
- Messages
- 73
- Reaction score
- 63
For what it's worth, I have 2 tickets open with 3CX support on the matters (reports & logs) and they have acknowledged the problem, and that it has been escalated to R&D for further research. It's been my experience that when a ticket gets to this stage, it's going to get addressed. The timeframe with which this gets handled is anyone's guess, but I would assume that all stakeholders understand that this is a critically important component of the system that cannot wait until SP4 or 16.x. There needs to be a hotfix for this, and quickly.