Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Jitsi-meet transport failures with persistent JIDs #17

Closed
bgrozev opened this issue May 29, 2015 · 3 comments
Closed

Jitsi-meet transport failures with persistent JIDs #17

bgrozev opened this issue May 29, 2015 · 3 comments

Comments

@bgrozev
Copy link
Member

bgrozev commented May 29, 2015

See http://lists.jitsi.org/pipermail/dev/2015-May/024269.html
@paweldomas
Copy link
Member

Fixed in 3d2323f

@paweldomas paweldomas changed the title Do not reuse MUC JIDs for identifiers in COLIBRI Jitsi-meet transport failures with persistent JIDs Jun 5, 2015
@paweldomas
Copy link
Member

We are going to keep on using MUC nickname as Colibri endpoint ID, because it saves us additional signaling work which would be required for other features like active speaker detection to work. Instead of changing endpoint ID allocation strategy Jicofo must make sure that Colibri transport is correctly disposed on the JVB when participant leaves the room.

@paweldomas paweldomas reopened this Jun 5, 2015
@bgrozev
Copy link
Member Author

bgrozev commented Jan 4, 2023

Outdated

@bgrozev bgrozev closed this as completed Jan 4, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@paweldomas @bgrozev