we are not asking you to troubleshoot this for 'us.' It is the opposite, you are asking 'us' to troubleshoot this for you. This may very well end up being a bug that we need to fix. It may also just as likely be an external influence or change present on just some systems. Until root cause is found, we won't know.
However, we tested this in the lab and we couldn't reproduce it. So I'll ask you a similar question: What more should we have done? Some of our option are, leave the ticket open but ignore it since we couldn't reproduce it, leaving you the impression that somehting is being done. That one doesn't sound great. Should we contact you and see if we can get on your system to determine if we can see what's going on since you can reproduce it? Maybe, we do that, quite frequently as I've indicated, once we've seen enough clear evdience that there is something 'systemic' going on and it's not just possibly one or two individuals, who, for all we know happen to have both installed the same 'third party add on' of some sort which cause the problem.
How about we suggest the issue get's brought up in the forums. What might the outcome be here. Well for starters, maybe there's a discussion which leads to you finding out that you would be better using app_confbridge and your immediate problem goes away. Hmm, not to bad. In the process, we find out that we messed up by leaving incorrect infromation about app_confbridge in the tolltip that justifiably made you nervous to use it when in fact, app_meetme should have gone away and that was our bad for missing that. So far, not a bad start. And, hmm, multipe developers from the project plus knwowledgable outside contributors are providing data like possible tickets it may be related to and their own ability to reproduce the problem. That sounds pretty useful as well, and that sort of dialog is not something that occurs in the ticket system.
What else might happen. Well maybe ten other people come along, vs. one other, and say hey that happens to me also. That has happened before, sometimes resulting in a solution from the community as a result of the open source process which we love because it's one less thing we have to solve. Or sometimes resulting in us seeing the type of data that I indicated, and thus further leading to take the time to get onto an outside system where the problem does occur so we can try to track down the issue since we can't in the lab. That is sometimes the outcome, and has repeated itself countless times in the past, and is one of the many reasons it is so useful to bring such discussions to the forums.
And lastly, whether the problem ends up as a bug that we utlimately fix, or whether it ends up being user error, external components, or many other influences, it often gets solved and the solutions expressed in the forum and then, guess what, all that energy that was expended by the various people who contibuted to help solve the problem gets indexed by google and the next person show comes along with the same problem and searches for a solution has a very strong chance of finding the help that they need as a result of the community efforts to help each other.
So ... sorry for the slight "attitude" here that I clearly expressed, but comments like "us troubleshoot this for you" need to be put in a bit of perspecitve. But I also hope you can see through your frustration, which I'm truly sorry that you have gone through, and realize that there are reasons and good intentions for such requests, and some pretty descent outcomes as well.