Hello Mark, (I'll add user@ list due to the answer might be helpful for others)
The answer depends on the type of docker image you are using `full` version contains KMS, `min` - version doesn't According to the port 8888 This port can be opened (there is bundled watchdog to drop any connection created NOT by OM) But it also can be closed so all Media traffic will go through TURN server (need to be specified explicitly) The README at github was written by me, so it most probably incomplete and need corrections :) PRs are welcome :)) On Mon, 16 Mar 2020 at 19:24, Mark Struberg <strub...@yahoo.de> wrote: > > Hi Maxim! > > I have a question regarding OpenMeetings. Do you have a few minutes for me? > > I followed the instruction regarding Docker. And it tells me to also expose > the port 8888 which seems to be for the kurento media server. > But does the openmeetings docker also include kms? Or do i need to start it > as a new docker image in a separate vm? > > I followed those instructions and also came across the 8888 port. Which is > now blocked by openmeetings. > > Are the docs wrong and we must not expose the 8888 port on the openmeetings > docker instance? > Or did I miss something else? > > txs and LieGrue, > strub -- WBR Maxim aka solomax
