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.

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

PTT - UX and switching PTT on #300

Closed
fkwp opened this issue Apr 13, 2022 · 2 comments · Fixed by #356
Closed

PTT - UX and switching PTT on #300

fkwp opened this issue Apr 13, 2022 · 2 comments · Fixed by #356
Assignees
Milestone

Comments

@fkwp
Copy link
Contributor

fkwp commented Apr 13, 2022

  • As a room admin
  • I can decide whether my VoIP call will be in ‘radio’ mode or conference mode
  • So that the right functions can be applied, and so that regular VoIP calls do not have the undesirable PTT experience

Notes

  • Regular VoIP calls can still have the more straightforward ‘push-to-unmute’, but all of the functionality of this PRD, i.e. only one user being able to speak at once, beeps on pressing transmit, default-to-mute, etc must only be on a call that is deliberately set as a ‘radio’ call.
  • This setting should be somewhat buried as 90% of users will not be interested in it or understand it.
  • It should also be persistent - once a given VoIP room is set into radio mode it stays in that mode until an admin changes it.
@fkwp fkwp assigned fkwp and unassigned fkwp Apr 13, 2022
@fkwp fkwp mentioned this issue Apr 14, 2022
8 tasks
@dbkr
Copy link
Member

dbkr commented May 5, 2022

This is now the case (although not with final UI yet).

@fkwp fkwp added this to the Push-to-Talk milestone May 19, 2022
@dbkr
Copy link
Member

dbkr commented May 26, 2022

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants