Kopano WebMeeting and Plugins vs Kopano Meet

fbartels

@ansib said in Kopano WebMeeting and Plugins vs Kopano Meet:

Specially the functionality to easyily integrate WebMeeting Invitations into an E-Mail is important.

Yes, we see this as important as well and have actually already started working on this. I cannot give an ETA at the moment, but it also depends on the below part.

@ansib said in Kopano WebMeeting and Plugins vs Kopano Meet:

Are there any plans to integrate this in Kopano Meet too, when the integration of external users is finished?

That functionality is actually already in the master download, but the release for customers is pending on documentation feedback. The documentation is available from (currently not linked from within the documentation). Feedback is appreciated.

https://documentation.kopano.io/kopano_meet_manual/special_configuration.html
And
https://documentation.kopano.io/kopano_meet_manual/advanced_settings.html

@ansib said in Kopano WebMeeting and Plugins vs Kopano Meet:

Even it was only a test for you, it is appreciated to get an integration into mattermost like an invitation link or something else.

Generally speaking it should be not problem to use both at the same time. For Mattermost we are thinking about doing a link based integration with Meet (similar how it’s done in Mattermost for Zoom and Jitsi), but Mattermost is currently not very high on our priority list.

ansib

@fbartels said in Kopano WebMeeting and Plugins vs Kopano Meet:

Yes, we see this as important as well and have actually already started working on this. I cannot give an ETA at the moment, but it also depends on the below part.

sounds great :)

@fbartels said in Kopano WebMeeting and Plugins vs Kopano Meet:

Generally speaking it should be not problem to use both at the same time. For Mattermost we are thinking about doing a link based integration with Meet (similar how it’s done in Mattermost for Zoom and Jitsi), but Mattermost is currently not very high on our priority list.

sounds also good for me.

@fbartels said in Kopano WebMeeting and Plugins vs Kopano Meet:

That functionality is actually already in the master download, but the release for customers is pending on documentation feedback. The documentation is available from (currently not linked from within the documentation). Feedback is appreciated.

@fbartels i am able to configure konnectd and kwmserver properly with the documentation.

the only thing missing is the meet.json as refered in the documentation under /usr/share/kopano-kweb/www/config/kopano/meet.json and so i am not able to login into meet without an account, am i right?

the configuration file is missing in my installation. i upgraded the kopano-meet-packages to the master. the other config files are here, only this one is missing.

It always appears the login screen, if i open https://domain.de/meet/r/group/Meetup#guest=1&name=john

fbartels

@ansib ah yes, that is a good point. If you need/want to modify it you need to create the file first. An example is in the docs directory (/usr/share/doc/kopano-meet-webapp/config.json.in).

ansib

@fbartels said in Kopano WebMeeting and Plugins vs Kopano Meet:

@ansib ah yes, that is a good point. If you need/want to modify it you need to create the file first. An example is in the docs directory (/usr/share/doc/kopano-meet-webapp/config.json.in).

found it. thank you.

Unfortunatly i am not able to get a session without login. does i miss a configuration? i always have to signin, i checked the konnectd and kwmserver config twice and changed the necessary config. I got an 403 for the logon of the guest user for this url: https://domain.de/api/kwm/v2/guest/logon

and in the log files i have following messages:

level=error msg="inner authorize request failed" desc="GuestIdentityManager: required scope missing" error=login_required

which scope is missing?

The “Share group” button is also deactivated in my session, maybe that’s the reason?

i tried a room with this url
https://domain.de/meet/r/group/public/customer-a#guest=1

What does the kpop- in front of the https mean in the konnectd-identifier-registration.yaml?

clients:
id: kpop-https://kopano.dev/meet/

I also get a lot of requests per second for this message in the console and in the network tab also:

oidc setup complete {popup: true, popupWindowTarget: “kpop-oidc-sign-in-yqmlz”, popupWindowFeatures: “location=no,toolbar=no,width=500,height=580”, appBaseURL: “https://domain.de/meet/”, redirectURL: “https://domain.de/meet/#oidc-callback”, …}

is this correct or does i malconfigured my proxy?

ansib

feature requests:

overview of created groups (internal as well as external/public groups) in the right navbar for registered users.

fbartels

@ansib said in Kopano WebMeeting and Plugins vs Kopano Meet:

which scope is missing?

Sounds a bit like the yaml file is either not correctly set up or passed to kwmserver and Konnect. Kan you enable debug logging in bit services and provide a bigger logging excerpt?

@ansib said in Kopano WebMeeting and Plugins vs Kopano Meet:

What does the kpop- in front of the https mean

That is the name of our react component library: https://stash.kopano.io/projects/KAPP/repos/kpop/browse

It’s a hard coded prefix.

@ansib said in Kopano WebMeeting and Plugins vs Kopano Meet:

is this correct or does i malconfigured my proxy

How have you configured your proxy? And what kind of proxy are you using? Not kweb I guess?

@ansib said in Kopano WebMeeting and Plugins vs Kopano Meet:

overview of created groups (internal as well as external/public groups) in the right navbar for registered users

This is not possible since this information is not stored at all on the server. But as the user this information will be kept in your recent call history (which in turn is synchronised between your sessions).

ansib

@fbartels said in Kopano WebMeeting and Plugins vs Kopano Meet:

Sounds a bit like the yaml file is either not correctly set up or passed to kwmserver and Konnect. Kan you enable debug logging in bit services and provide a bigger logging excerpt?

ok i have no idea, but it is working now… i restarted the server one more time and after it, it works … sry…

i think the documentation is complete and works correctly (only the hint with the meet.json would be useful).

@fbartels said in Kopano WebMeeting and Plugins vs Kopano Meet:

That is the name of our react component library: https://stash.kopano.io/projects/KAPP/repos/kpop/browse
It’s a hard coded prefix.

thanks for this information

@fbartels said in Kopano WebMeeting and Plugins vs Kopano Meet:

How have you configured your proxy? And what kind of proxy are you using? Not kweb I guess?

cause we have only one public static ip address we are routing everything through one virtual machine. on the kopano virtual machine i am using the kweb daemon. I think the requests in the console is a keep alive message and everything is configured correctly. i am able to call my devices inside the network.

There is only one problem left:

The “Share Group” button is still deactivated. Which log files do you need here? What is the purpose of this button?

fbartels

@ansib said in Kopano WebMeeting and Plugins vs Kopano Meet:

The “Share Group” button is still deactivated. Which log files do you need here?

If it’s really activated then I’d guess (since it’s all local javascript) the only place where this could come up is the local javascript console. What browser are you using?

What is the purpose of this button?

It copies the URL of the room into the clipboard.

ansib

@fbartels said in Kopano WebMeeting and Plugins vs Kopano Meet:

It copies the URL of the room into the clipboard.

ok, i have to take back my statement, because the button works. i did not thought, that this is the purpose of the button, because you use the slide button design.

Maybe you can change the design of the button or put a “Copied to Clipboard” message to the button. Hopefully i am the only one who was confused by this button.

ansib

@fbartels maybe i can get your help one more time… thank you in advance!

At the moment i am not able to start the server:

Apr 10 12:59:24 systemd[1]: Starting Kopano KWM Server...
Apr 10 12:59:24 systemd[1]: Started Kopano KWM Server.
Apr 10 12:59:24 kopano-kwmserverd[1318]: level=info msg="serve start"
Apr 10 12:59:24 kopano-kwmserverd[1318]: level=info msg="using external TURN service: https://turnauth.kopano.com/turnserverauth/"
Apr 10 12:59:24 kopano-kwmserverd[1318]: Error: turn-service-credentials file not found: stat 1318turn_service_credentials: no such file or directory
Apr 10 12:59:24 systemd[1]: kopano-kwmserverd.service: Main process exited, code=exited, status=1/FAILURE
Apr 10 12:59:24 systemd[1]: kopano-kwmserverd.service: Unit entered failed state.
Apr 10 12:59:24 systemd[1]: kopano-kwmserverd.service: Failed with result 'exit-code'.

what is the correct configuration for the kwmserverd? if i comment out the turn_service_credentials part the server can start correctly.

# TURN settings

# TURN service URL.
# URL to a TURN service API to request TURN credentials. For example Kopano
# provides this for customers. Defaults to the public URL of the Kopano TURN
# service at `https://turnauth.kopano.com/turnserverauth/`.
turn_service_url = https://turnauth.kopano.com/turnserverauth/

# TURN service authentication credentials.
# Path to a file with 'username:password' style credentials. If set, kwmserverd
# tries to obtain TURN settings via external TURN service configured as
# `turn_service_url`. Not set by default.
turn_service_credentials = /etc/kopano/kwmserverd-turnservice.secret

# Space separated list of TURN serve uris to be set to clients. This is not set
# default, but is required for production use to let clients in restricted
# environments successfully connect. Either provide your own TURN server or
# use a TURN service with the settings above.
#turn_uris =

# Path to a file containing the shared secret to be used to create TURN server
# user credentials. When set, kwmserverd creates user credentials for TURN. Not
# set by default.
#turn_server_shared_secret = /etc/kopano/turn-server-shared-auth.secret

in the file /etc/kopano/kwmserverd-turnservice.secret i put the username:password.

ansib

This post is deleted!

ansib

found it. this commit from @fbartels is missing in the master repo of kwmserderd:

https://github.com/Kopano-dev/kwmserver/commit/c30cbbe0b14cca53d6552e1e6993de0b5a6d27d4

this surplus $ is still in my binscript under /usr/sbin

unfortunatly there is still no video media data, only a blue screen, if i start a call.

fbartels

@ansib said in Kopano WebMeeting and Plugins vs Kopano Meet:

this surplus $ is still in my binscript under /usr/sbin

Yes, I was already thinking it was something like that. I don’t think we have meanwhile tagged a new release, therefore it’s not yet in the packages.

@ansib said in Kopano WebMeeting and Plugins vs Kopano Meet:

unfortunatly there is still no video media data, only a blue screen, if i start a call.

Debugging turn is a bit more difficult. I would recommend to get in direct contact with our support so they can look at it in a remote session.