Skip to content

Conversation

@danxuliu
Copy link
Member

Fixes #3203

This still needs more work, as currently it applies to all conversations. It should be configurable somehow, and also handled by mobile applications.

The participant call flags are now honoured as media constraints when
joining a call. Therefore, now only the media specified in the flags is
allowed to be sent (although whether it is sent or not depends on the
available media).

Signed-off-by: Daniel Calviño Sánchez <[email protected]>
Signed-off-by: Daniel Calviño Sánchez <[email protected]>
If the participant can not send media or screenshare it is now hidden
from the call view.

Note that currently it is not possible to know if a guest is a regular
guest or a guest moderator, so any type of guest is hidden.

Signed-off-by: Daniel Calviño Sánchez <[email protected]>
Guests can not fetch the full participant list, so until now the
participants store was only populated with the guest itself. However,
the conversation data also includes a list of the users (but no guests)
in the conversation, so the participants store can be populated with
that data. This will make possible to know if a message is sent by a
moderator or not.

Note that when the external signaling server is used guests can also
know which other guests are in the conversation from the participants
update signaling message. However, that data is not used to populate the
participants store because the conversation data is enough to know the
moderators and to keep a consistent behaviour when using the internal
and the external signaling servers.

Signed-off-by: Daniel Calviño Sánchez <[email protected]>
Copy link
Member

@PVince81 PVince81 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I added a few comments.

Would be good to have a checkbox list to know what's missing.

}
}
const participantIndex = this.$store.getters.getParticipantIndex(this.token, { participant: this.model.attributes.userId })
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

we have a participant mixin, not sure if we can use it or extend it ?

},
isSendingMediaOrScreensharingAllowed() {
return this.participant.participantType === PARTICIPANT.TYPE.OWNER
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

deja vu

I wonder if we should move this to a property and let the callview do this check and tell all sub-components what's allowed or not ?

* provided both audio and video are available. Otherwise only the specified
* media will be allowed to be sent.
*
* Note that the flags are constraints, but not requeriments. Only the specified
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

typo "requeriments"

currentUser = getCurrentUser()
}

if (!currentUser || !currentUser.uid) {
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

add comment to clarify that for guest users we need to explicitly fetch the list (the if statement isn't very clear that we're targetting guests)

@PVince81
Copy link
Member

It should be configurable somehow, and also handled by mobile applications.

I guess it makes sense to add this per room.
So it will need a new backend attribute in the room structure, configurable in the conversation settings dialog and also exposed to clients.

@danxuliu
Copy link
Member Author

danxuliu commented Jun 1, 2021

Closed in favour of #5693

@danxuliu danxuliu closed this Jun 1, 2021
@danxuliu danxuliu deleted the send-media-streams-in-calls-only-by-moderators branch June 1, 2021 04:53
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

One to many video / audio streams

4 participants