I haven't tested it very extensively, but in a few of my tests after removing a content that just sprang to live the call got terminated. From a quick look it seems that Gabble received a transport-info referring to the content it just removed from the other side and decides to terminate the call because of that
I think this may have been a side-effect of the buggy code to replace contents with the same name?
-- GitLab Migration Automatic Message -- This bug has been migrated to freedesktop.org's GitLab instance and has been closed from further activity. You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.freedesktop.org/telepathy/telepathy-gabble/issues/22.
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.