Hey, yea absolutely - this has been a really tricky issue since we see reports of voice comms problems and we know it’s happening sporadically (it happens to us too) but we haven’t as yet been able to reproduce the exact conditions in order for us to identify the root cause..
tl;dr it may be any number of things (or a combination of things) but until we can confidently identify what they are we can’t be certain anything we’re trying will be a permanent fix, or solve part of the problem, or make something else worse.
Not a lot to go on, I know, but we haven’t been intentionally “silent” on the issue, we just don’t (yet) have anything new to say beyond that our programming team is continuing to work to identify the cause.