twinkle problems with conference call

After having combined 2 lines to a conference call, the audio quality for the remote peers is quite bad. It's not possible to hang up a line or to end the conference. Twinkle needs to be killed -9 for getting out at all.

Jun 28 '18 17:06 zbx1392

I assume the UI is nonresponsive in that situation, which would explain why you cannot end the call? If so, have you tried using the command line with twinkle --cmd bye?

Also, does Twinkle consume 100% of the CPU by any chance? (You can check this with top, for instance.) If so, which audio codecs are in use on both lines?

Finally, I take it that you are using kill -9 because a simple kill does not work?

Jul 03 '19 08:07 fbriere

After having combined 2 lines to a conference call, it's not possible to hang up a line or to end the conference. Twinkle needs to be killed.

Ubuntu 18.04.4 LTS

Apr 09 '20 08:04 olegbelousov77

@olegbelousov77 Twinkle used to either freeze or crash (depending on the "Hang up both lines" setting) when ending a conference call. This was fixed in #166 and #180, both merged last February; unfortunately, these fixes are not in Ubuntu yet.

Apr 09 '20 22:04 fbriere

Answering my own questions after the fact:

I assume the UI is nonresponsive in that situation, which would explain why you cannot end the call? If so, have you tried using the command line with twinkle --cmd bye?

This was not a UI issue; rather, it's the process of hanging up the call that made Twinkle freeze.

Finally, I take it that you are using kill -9 because a simple kill does not work?

Twinkle catches and handles SIGTERM on its own; if it freezes for any reason, it can only be terminated with SIGKILL.

Apr 09 '20 23:04 fbriere