Hi @fbartels,
What was happening to me was that when the user logged out webapp/closed browser window but didn’t logout from webmeetings (probably what a user will do every time) it stayed as online and never changed state to offline. With the proposed modification the user goes offline after 2 minutes if the server doesn’t received a status update in the meantime.

I changed the cast to the int(self.limit)*60 because without it I was getting the self.limit repeated 60 (eg “2*60=2222222222222222222222222…”) times instead of a numerical result (“2*60=120”). This way int(time.time()) - info['last_update'] > self.limit*60: would never return true.

For the record I’m running it in Ubuntu 16.04.4 with Python 2.7.12

@fbartels
After applying the following modifications I finally got it working with the email address as the login.

First in /usr/share/kopano-webapp/client/kopano-debug.js ( not sure but it seems the part I modified comes from kopano-webapp/client/zarafa/core/data/UserIdObjectFactory.js):

// Add ZARAFA specific fields to the object var recordEntryId = record.get('entryid'); var recordUsername = record.get('username'); var recordEmailAddress = record.get('email_address'); var recordSmtpAddress = record.get('smtp_address'); user.entryid = recordEntryId; // Try to be smart to find the username and email address. // Sometimes the username is available in the email_address field, // sometimes the email address is available in the username field, // and sometimes it is available in the smtp_address field. if ( Ext.isString(recordUsername) && recordUsername.indexOf('@')==-1 ){ user.username = recordUsername; } else if ( Ext.isString(recordEmailAddress) && recordEmailAddress.indexOf('@')==-1 ){ user.username = recordEmailAddress; }

In my debugging recordUsername is empty/undefined because record.get(‘username’); returns nothing as there’s no username in record, eg:

account: "" address_type: "ZARAFA" assistant: "" business2_telephone_number: "" business2_telephone_number_mv: "" business_telephone_number: "" comment: "" company_name: "" country: "" department_name: "IT" display_name: "User2 Adeus" display_type: 0 display_type_ex: 1073741824 email_address: "user2@adeus.pt" entryid: "00000000ac21a95040d3ee48b319fba753304425010000000600000072000000457949424c762f4471306d7069456e355873375a41513d3d00000000" fileas: "user2@adeus.pt" full_name: "Adeus, User2" given_name: "User2" home2_telephone_number: "" home2_telephone_number_mv: "" home_telephone_number: "" initials: "" locality: "" message_class: undefined mobile_telephone_number: "" object_type: 6 office_location: "" office_telephone_number: "" pager_telephone_number: "" postal_code: "" primary_fax_number: "" search_key: "5a41524146413a55534552324041444555532e505400" smtp_address: "user2@adeus.pt" state_or_province: "" street_address: "" surname: "Adeus" title: ""

Also noticed that email_address in record is populated with ldap_loginname_attribute.

So when you test else if ( Ext.isString(recordEmailAddress) && recordEmailAddress.indexOf('@')==-1 ){ user.username = recordEmailAddress; }, and are using an email as the login, it will fail and user.username will be empty. To make it work I changed it to else if ( Ext.isString(recordEmailAddress) { user.username = recordEmailAddress; }

The other file I modified was /usr/share/kopano-webapp/plugins/spreedwebrtc/jsspreedwebrtc-debug.js:

/** * Will either add or remove an email_address to the watch list * * @param {String} email_address The email address to remove or add * @param {String} remove optionally remove the user from the watch list * @private */ updatePresenceWatchingList: function(email_address, entryId, smtp_address, remove) { if (!email_address || 0 === email_address.length) { return; } // skip non-Kopano email addresses if (email_address.indexOf('@') > -1) { return; } var index = this.presenceWatchingList.indexOf(email_address);

Same issue here. Removed if (email_address.indexOf('@') > -1) { return; }
so I don’t get an empty watch list and subsequent empty presence request.

With this modifications presence works using either sAMAccountName or mail as ldap_loginname_attribute.

Keep in mind that I’m no software developer nor do I know if there are implications anywhere else in Kopano. Hope this helps you solve the issue.

That depends on a lot of factors, e.g. available bandwidth (everything is peer to peer) and CPU power.

We had stable meetings with more than ten users, but you usually you want to stay a four participants.

Was there a good audio equipment involved? Webmeetings with integrated micro/speaker is not a good idea - independent what kind of software you are using. It should be better, if both sides are using headsets or an USB connected microphone.

I made some audio and video conferences across the Atlantic (Germany/Mexico) - and it was working fine.

It’s possible if they run on different ports, but it makes no sense. I turn server is usually located in front of the firewall/NATGateway - the webapp should be protected behind the firewall.
It’s also a good idea to use the port 443 tcp and udp for the turn server. The https port is often open in firewalls, even if the UDP ports for webrtc are closed.

@robing THANK YOU SO MUCH @robing IT FINALLY WORKS THX

@bigcheese #solved

@bert64 have you solved the problem? because I’m running into the same thing

The link to https://servername.domain.com/webmeetings should show a Kopano page with the text “please join web meetings”,
0_1502273751399_31d76bed-51f7-48a1-94f5-e4508e243c93-grafik.png

if it’s the nginx start page, the location is not proper set in the nginx config. Like the documentation shows …

location /webmeetings {
proxy_pass http://127.0.0.1:8090;
proxy_http_version 1.1;
proxy_set_header Upgrade $http_upgrade;
proxy_set_header Connection $connection_upgrade;
proxy_set_header X-Forwarded-Proto $scheme;
proxy_set_header Host $http_host;
proxy_set_header X-Real-IP $remote_addr;
proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
}

any other chances to get webmeetings on ipad / iphone?

I ended up using screenshots of the “What’s new” dialog box. :)

At first glance it might be. However I have been unable to replicate the problem since… (Isn’t that always the case)

If/when the problem shows it head again, I try to verify that it is this specific bug.

There was suppose to be an image w/ the error message…
Anyway the error message is “Accessing the Kopano WebMeetings TURN authentication service failed.”

Hi!

Unfortunately this is not possible.

Every time you log out of Web Meetings your session is ended and cannot be recovered, when you log back in to Web Meetings a complete new session is created.

This is done intentionally for security reasons.

Kind regards,

Joost

Hello @Vogi,

Thanks for the notification, our devs are looking into the issue.

We will keep you posted.

-Joost

Problem solved with the new webmeetings package: webmeetings-0.29.5_1
kopano-webapp-plugin-meetings_3.0.0.81
kopano-webmeetings_0.29.5-1
WebApp 3.3.0.596-427.1

Have a nice day …

@mcostan

Thanks so much for your help! I plugged in the configuration and it works like a charm! The only 2 things i changed where the listening port (3478) and the cipher-list=“DEFAULT”

Again, I appreciate your assistance!

Gary

@fbartels

Yes that would be a good start, but one of the integrations between Outlook and Skype (Lync) is that you can click on the person in the email and instantly you start the meeting… Not sure whether that’s possible with web meetings, but obviously being able to launch it as you say form KOE is a good start.

Aah, so I see… 3 backquotes…

So I was able to run the command and now apt update works fine:

zarafa-meetings:~# curl https://USERNAME:PASSWORD@download.kopano.io/supported/core:/final/Ubuntu_16.04/Release.key | apt-key add - % Total % Received % Xferd Average Speed Time Time Time Current Dload Upload Total Spent Left Speed 100 3102 100 3102 0 0 507 0 0:00:06 0:00:06 --:--:-- 675 OK

I’m betting the problem is that a username/password is required to get the key so the basic apt-key command won’t work.

Thanks
Bob