Well, according to my experience all corporate admins use the following principle: "Close everything, then open all what is necessary by request" :))) OM now requires lots of ports :( there was an idea of "bullet proof" network configuration (port 443 only) but I haven't tested it yet :( (and it was only a high level description only ... :(( )
On Fri, 16 Oct 2020 at 22:10, Denis Noctor <[email protected]> wrote: > Hi there Maxim... you’ve really got my interest and attention here... :) > Can you explain a little more why this might not be an ultimate solution? > Thanks a lot. > > Sent from my iPhone > > On Oct 16, 2020, at 9:17 AM, Maxim Solodovnik <[email protected]> > wrote: > > well > > you can set TURN to use TCP (just add `?transport=tcp` to TURN URL) > unfortunately this is not ultimate solution :( > > On Thu, 15 Oct 2020 at 23:48, Denis Noctor <[email protected]> wrote: > >> I suppose this all boils down to UDP being usually blocked by most >> private corporate networks. Only solution I can recommend is that UDP is >> unblocked on a public network. >> >> Sent from my iPhone >> >> Begin forwarded message: >> >> *From:* Denis Noctor <[email protected]> >> *Date:* October 15, 2020 at 1:29:35 AM CDT >> *To:* [email protected] >> *Subject:* *General and Corporate User... (Off Topic... Sorry)* >> >> Hi there Maxim... and everyone out there, >> >> I know this email might be considered a little off topic... but resonates >> an issue that may have been overlooked in the overall application of OM at >> a corporate level. >> >> Let me try to explain. At present OM is browser based... thankfully >> Chrome and Firefox support WebRTC etc. I am aware of the Safari issues >> being discussed regarding audio and vid etc. >> >> The majority of users I have are experiencing a relatively fluid >> experience regarding OM... however I have encountered 2 scenarios over the >> last few months that contradict each other... though it is not an OM >> issue... but maybe someone out there might be able to give some insight. >> >> Company “A” (via it’s corporate WiFi network) was able to access a >> room... ... see room interactions (for example switching from whiteboard to >> whiteboard... typing onscreen etc) but could not share or receive audio/mic >> and video of other users. Clearly there were restrictions (firewall or >> others) on their side. However, when users used the public access >> network... everything was fine. Sweet. No problem now. >> >> However, I have encountered a similar situation with Company “B”... and >> have asked them to use their “public” network... but they can’t experience >> incoming nor outgoing audio or cam. >> >> Can you recommend a permissions checklist that they could follow to give >> them full access and functionality to OM? >> >> One user from company “B” brought their computer home... logged in and >> they had no problem with audio/mic/cam.... so obviously there are >> restrictions on a corporate level. >> >> Can anyone recommend a permissions checklist that company “B” needs to >> follow (grant access to)... without compromising their network or security? >> >> Company “B” has used Zoom, Microsoft Teams without issue... but of >> course, these are downloaded apps (and not necessarily browser based). >> >> @Maxim... I now this is going to cause you a headache... and I apologize >> in advance... but may open a few other discussions. >> >> Any help, suggestions would be appreciated. >> >> I know this is a huge request... but might shape future releases. >> >> All the best, >> >> Denis. >> >> Sent from my iPhone >> >> > > -- > Best regards, > Maxim > > -- Best regards, Maxim
