Well, they closed it and told you to discuss it in the forums. Which, lets be honest, will lead nowhere. So I guess you should just move to confbridge or find a new PBX software.
I don't get it. They can't replicate for whatever reason, yet you and I both can make it occur repeatedly without fail. I will be on break for Christmas in a few weeks. I'll spin up a current release and test and installing an older freepbx version, updating it to current release, and see if the issue shows up. If it does, I'm going to be pretty annoyed with this whole situation.
And here I though ticketing systems were made for reporting bugs in software. I don't know what more they want short of telling them "here is the problem and how to fix it". I mean, it's pretty straight forward what is going wrong here and what the problem relates to. It's right in the "random" log. And instead of saying, "can you provide this or that" they rather just close it and pretend the issue(s) don't exist.
I don't know what has been going on since the Sangoma merger but reporting anything as a bug seems to be greeted with a closing of the ticket and nothing being addressed. I'm STILL having UCP Node issues after updates even though it was "supposedly" fixed. But they don't want to hear it and obviously it must be something I'm doing wrong (since running module updates seems to be a problem for FreePBX now). Vanilla installations (a whole bunch of them actually) all with the same exact problem, multiple people STILL posting they have the problem in the forums, but it's not a bug...umk.
Yea, I'm a bit pissed off, I am. I've spend good money towards the FreePBX project. I just spend over 2k in commercial module licenses during the cyber sale alone. But whatever, I'm just going to give up on submitting anything as it is a waste of my time (what little I actually have).