AW: OpenMeetings - File Handling

I can provide you a snippet out of the log (trying to upload a simple .txt file): DEBUG 05-07 08:50:07.438 o.a.o.c.d.f.FileProcessor:72 [Thread-3637] - file extension: txt DEBUG 05-07 08:50:07.446 o.a.o.c.d.f.FileProcessor:76 [Thread-3637] - isAsIs: false DEBUG 05-07 08:50:07.446 o.a.o.c.d.f.Fi

AW: OpenMeetings - File Handling

Yepp – even „helpers“ need to sleep and must have coffee. Take care of you – you are „important person“. I tested it out. If i upload a file that can not be converted, there’s an error but the original file is downloadable indeed. Currently every file fails in converting? Can this be a problem

Re: OpenMeetings - File Handling

Hello Peter, On Thu, 7 May 2020 at 12:22, Peter-Otto Weber wrote: > Hello Maxim, > > > > hope you had a long night and your first cup of „Admin-Drug“… > Unfortunately not, but I'm here to help :) > > > I wonder if it is possible to upload a file in „raw“ format – unconverted > to PDF? > > > >

AW: OpenMeetings - File Handling

Hello Maxim, hope you had a long night and your first cup of „Admin-Drug“… I wonder if it is possible to upload a file in „raw“ format – unconverted to PDF? The reason is simple – if you e.g. work in a document together with the customer you might want to upload the finished release so that th

Re: OpenMeetings <-> BigBlueButton

Hello Peter, On Wed, 6 May 2020 at 12:00, Peter-Otto Weber wrote: > Hello Maxim, > > > > we had the Problem with customers behind a Firewall. > > There, only „Standard Browsing“ on 80/443 was open. 5443 was blocked in > the Firewall. > > So they were not able to even get the web interface. > > >

Re: NAT Issue

Hello Partha, sorry for keeping silence, I'm a bit overloaded :( I have no experience with `reTurnServer`, used only coturn, was sure it is available for all distros :( You need to make sure - TURN is accessible from outside your NTA - TURN can communicate with KMS On Wed, 6 May 2020 at 23:34, P

RE: OpenMeeting 5.0.0 M5 (fix TimeZone Canadian)

[cid:banner1.jpg] Change your COUNTRY to Canada Martin Chamberland Technicien en informatique La Financière agricole du Québec 1400, boul. Guillaume-Couture Lévis (Québec) G6W 8K7 Téléphone : 418 838-5614, poste 6230 martin.chamberl...@fadq.qc.ca www.fadq.q

Re: OpenMeeting 5.0.0 M5 (fix TimeZone Canadian)

And I would also like to mention: Allez Montréal! Cheers Seb Sebastian Wagner https://www.linkedin.com/in/sebastianwagner/ On

Re: OpenMeeting 5.0.0 M5 (fix TimeZone Canadian)

When I change my users timezone to America/Montreal it doesn't show any AM/PM at all [image: image.png] I can create the meeting just fine. There is no error. This is current snapshot (maybe 2-3days since last sync) Thanks, Sebastian Sebastian Wagner https://www.linkedin.com/in/sebastianwagner

Re: NAT Issue

Hi As discussed I have installed turn in a different server. [root@demo reTurn]# netstat -npl | grep -i turn tcp0 0 0.0.0.0:34780.0.0.0:* LISTEN 8770/reTurnServer tcp6 0 0 :::3478 :::*LISTEN 8770/reTurnS

OpenMeeting 5.0.0-M4, import AD-users using LDAP-connection and admin.sh

Hi again, since the ldap-connection works fine, I was trying to import my users, using this connection. I was following the instructions from https://openmeetings.apache.org/LdapAndADS.html. Basically, I just started the test-import (without really importing), using the command sudo ./admin.sh

AW: OpenMeeting 5.0.0-M4, LDAP-connection recognizes "Deutschland" as "Andorra"

Hi Gerald, thanks, works like a charm. Mit vielen freundlichen Grüßen, Alexander Ninnig Rechnungshof Rheinland-Pfalz Gerhart-Hauptmann-Straße 4 67346 Speyer Phone: +49(0)6232/617-285 Fax:+49(0)6232/617-100 Mail: alexander.nin...@rechnungshof.rlp.de Web:https://rechnungshof.rlp.

AW: OpenMeeting 5.0.0-M4, LDAP-connection recognizes "Deutschland" as "Andorra"

Alexander, if I remember right you need to use c instead of co. Look at AD attributes under the user. c = DE With that the mapping will work in OM Gerald -Ursprüngliche Nachricht- Von: Ninnig, Alexander [mailto:alexander.nin...@rechnungshof.rlp.de] Gesendet: Mittwoch, 6. Mai 2020 15:0

OpenMeeting 5.0.0-M4, LDAP-connection recognizes "Deutschland" as "Andorra"

Hi, I managed to get a working LDAP-connection. But OpenMeetings gets the country wrong. All my users have the country "Deutschland", which is a drop-down-menue in Active Directory, so there's no chance of misspelling. This AD-attribute is "co". In my om_ldap.conf, the corresponding line is: "ld

RE: OpenMeeting 5.0.0 M5 (fix TimeZone Canadian)

[cid:banner1.jpg] Are you sure the problem come from moment.js ? From here, if we choose Canada French down the page https://momentjs.com/ Everything looks good in the format above. De : Maxim Solodovnik [mailto:solomax...@gmail.com] Envoyé : 5 mai 2020 22:33 À : Openmeetings user-list Objet

Re: OpenMeetings - switch to port 443

On Wed, 6 May 2020 at 17:04, Rohrbach, Gerald wrote: > Peter, > > > > thanks for the conclusion, with the fixes from Juan I was also able to get > it working on 443. > > > > As in your later posts commented a problem are company firewalls. > > They are much more restrictive. And in many companies

RE: OpenMeeting 5.0.0 M5 (fix TimeZone Canadian)

[cid:banner1.jpg] stop OM ./admin.sh -b -file ~/today_om_backup.zip mv /opt/om5 /opt/om5.backup untar om.version.download drop database / create database sudo ./admin.sh -v -i -file ~/today_om_backup --drop --skip-default-object start OM De : Maxim Solodovnik [mailto:solomax...@gmail.com] Envoyé

Re: OpenMeeting 5.0.0 M5 (fix TimeZone Canadian)

On Wed, 6 May 2020 at 17:49, Chamberland, Martin < martin.chamberl...@fadq.qc.ca> wrote: > [image: cid:banner1.jpg] > > > > I would go and check that. > > I have to say that there is still a strange behavior when I update Mx > release. > > All my LDAP user are still appearing in the web interface

RE: OpenMeeting 5.0.0 M5 (fix TimeZone Canadian)

[cid:banner1.jpg] I would go and check that. I have to say that there is still a strange behavior when I update Mx release. All my LDAP user are still appearing in the web interface of OpenMeeting (USERS), but if a user connect, a new one with the same name is create. What i have to do, I delete

AW: OpenMeetings - switch to port 443

Peter, thanks for the conclusion, with the fixes from Juan I was also able to get it working on 443. As in your later posts commented a problem are company firewalls. They are much more restrictive. And in many companies the firewalls are maintained by externals or Corporate IT. So it’s nearly