I am running Ubuntu 18.04.2 LTS, and use the Web App on Chromium 75.0.3770.100, and I work with computer audio. Since the last update of GoToMeeting my attendees are no longer able to hear me, although I could hear them. The audio settings looked normal, but I wasn't shown as one of the current speakers during the meeting, nor the attendees could hear a word from me. I would appreciate your help in order to solve this issue.
Dear @AshC :
Thanks for your answer. I tried looking at the padlock as you explained, but everything seems to be normal. Here you can see a screen-capture:
Only cookies are blocked, and the website only asked for permission in relation to notifications, which was accepted. Is there something wrong there, or anything else I can do?
I apologize for the trouble there.
Since the problems began, have you identified any recurring attendees reporting the behavior?
Do you know exactly how they are connecting, through which device or browser?
Thanks! There seems be no pattern in terms of the Go To Meeting account used or users. The users that seem to be impacted the most are those who are using teleconferencing equipment and less frequently those who call in using the VoIP desk phone and smartphone. Also, the issue occurs even when no browser is used. For example, callers use their phones and only call into the meeting and no one (including the meeting organizer) launches Go To Meeting. Therefore, it seems it is not browser or device dependent either.
@Gwen1 That behavior should not happen regardless of how the attendees join. We can investigate VoIP issues some time after a failure occurs, but unfortunately with telephone problems we need to know the Caller ID, Conference ID, and GoTo phone number dialed within 24 hours in order to trace the issue back to its source.