As far as I remember, when I received "Multimedia server is inaccessible" the Kurento mediaserver was running. But I'm going to check again next time.
If you want to determine what was it caused by you need to examine the logs, and OM should run in DEBUG mode. And you need to know how OM works, how the network/communication protocols work. But Maxim and all our friends are working on this. I'm sure this great SW will improve quickly. The technology has just changed; we are in the transition phase now which means Flash is being replaced by WebRTC. <https://www.googleadservices.com/pagead/aclk?sa=L&ai=DChcSEwj9ksvZ84zuAhWsEAYAHapkB0MYABABGgJ3cw&ae=2&ohost=www.google.com&cid=CAASEuRoR0cInceXxVkpobzNpKgy1w&sig=AOD64_0OvFQXxMVbT1F4SmOOS9mn3ASLJA&q&adurl&ved=2ahUKEwjxqMTZ84zuAhUQ3IUKHRfICOwQ0Qx6BAgGEAE> But as mentioned OM is great. Armen Ambartsumyan (Jira) <[email protected]> ezt írta (időpont: 2021. jan. 8., P, 15:36): > > [ > https://issues.apache.org/jira/browse/OPENMEETINGS-2549?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17261374#comment-17261374 > ] > > Armen Ambartsumyan commented on OPENMEETINGS-2549: > -------------------------------------------------- > > Thanks for Your guidance Maxim, > > I followed the link you provided with the commands to check the KMS. > > It passes all the commands but it gives an error on the last one when I do > {code:java} > curl \ > > --include \ > > --header "Connection: Upgrade" \ > > --header "Upgrade: websocket" \ > > --header "Host: 127.0.0.1:8888" \ > > --header "Origin: 127.0.0.1" \ > > http://127.0.0.1:8888/kurento > > {code} > It returns > {code:java} > curl: (56) Recv failure: Connection reset by peer > {code} > !KMS TEST.png! > > > > I think this could be the problem, but the another problem is I don't know > how to fix it lol :)))) Sorry I a very new to this and trying to make sense > of it. Sorry for so many questions. > > can you let me know what steps should I take next to fix that error? > > > > Thank you, > > > > Armen > > > Multimedia server is inaccessible-Open Meetings > > ----------------------------------------------- > > > > Key: OPENMEETINGS-2549 > > URL: > https://issues.apache.org/jira/browse/OPENMEETINGS-2549 > > Project: Openmeetings > > Issue Type: Task > > Environment: CENTOS 7 > > Reporter: Armen Ambartsumyan > > Assignee: Maxim Solodovnik > > Priority: Major > > Attachments: KMS TEST.png, KMS.png, Multimedia Server is > inaccessible.png > > > > > > Hi There, > > I have followed the instructions here [Installation OpenMeetings 5.1.0 > on Centos 7.pdf| > https://cwiki.apache.org/confluence/download/attachments/27838216/Installation%20OpenMeetings%205.1.0%20on%20Centos%207.pdf?version=2&modificationDate=1608041318000&api=v2] > and [Installation > SSL certificates and Coturn for OpenMeetings 5.1.0 on CentOS 7.pdf| > https://cwiki.apache.org/confluence/download/attachments/27838216/Installation%20SSL%20certificates%20and%20Coturn%20for%20OpenMeetings%205.1.0%20on%20CentOS%207.pdf?version=2&modificationDate=1608632656000&api=v2] > to > install the OpenMeetings. > > > > However now I am running into an issue with the Video and Audio > features: As soon as I click in Camera and Microphone icons I > get Multimedia server is inaccessible > > > > After a research I checked my kms it seems to be installed. Does anyone > else have the same issue. I have been spending the last 2 days to try to > fix this :( > > I have attached the screenshot that shows that kms is installed > > Does anyone know what may cause this? > > > > Thank you, > > > > Armen > > > > -- > This message was sent by Atlassian Jira > (v8.3.4#803005) >
