Hello Andre, which guide are you referring to? On Sat, Jul 23, 2016 at 3:11 PM, Andre Wruszczak <wruszc...@web.de> wrote:
> Hey, > > > > I’ve made a similar mistake (not changing the context path name) I think > the guides should be updated, telling you to change “localhost:5080” to > your servers name if needed, as clients can’t connect to the screen sharing > app otherwise. > > Or write a more exhaustive description in the configuration for the > context path. In my opinion this would help greatly ( this rather small > mistake ) took me quite a while to figure out! > > Cheers > Andre > > > > *Von:* Tech Developer [mailto:simatechdevelo...@gmail.com] > *Gesendet:* Saturday, July 23, 2016 8:17 AM > *An:* user@openmeetings.apache.org > *Betreff:* Re: Share / Record Screen Issue > > > > Hi, > Thank you for your reply, the above issue resolved. The error occured > as I didn't change the context path name. Now I am able to access > "Openmeetings > Screen Sharing Applet" in both the openmeetings. > > You mentioned that "we need two different port numbers, one for each > instance of the OM application to listen to at HTTP level, as well as RTMP > level." > > But am able to run both the open meetings at the same time using the same > port number without any 404 errors. > > Now, please tell me whether Is it mandatory to apply two different port > numbers for the two different open meetings ? > If it is mandatory, it will be helpful if you could also tell me how to > apply the information in the configuration files i.e. (Thus, as an example, > if OM-1 listens to HTTP port 5080, OM-2 could listen on 5079. Again, if > OM-1 listens to RTMP port 1935, OM-2 could listen on 1936.) > > > > > > > > On Fri, Jul 22, 2016 at 11:02 PM, Susheel Jalali < > susheel.jal...@coscend.com> wrote: > > Dear Tech Developer, > > Are you running both OM-1 and OM-2 concurrently (at same time) on the same > server? > > If so you will notice that while the first one gives sign-in page, the > second OM-2 does not even start and gives HTTP 404. > > You need two different port numbers, one for each instance of the OM > application to listen to at HTTP level, as well as RTMP level. > Thus, as an example, if OM-1 listens to HTTP port 5080, OM-2 could listen > on 5079. > Again, if OM-1 listens to RTMP port 1935, OM-2 could listen on 1936. > > You need to modify the configuration files as mentioned in installation > instructions. > > For launching the recording application, you need to have supported > version of Java (7 or 8 usually), then allow the download of JNLP file to > complete, ensure you have the coorrect URL with port number > added to your Java Control Panel Security settings and then launch the > JNLP file, and agree to the security warning (risk), then RUN it. > > -- > Sincerely, > > Susheel Jalali > Coscend Communications Solutions > www.Coscend.com > ---------------------------------------------------------------- > CONFIDENTIALITY NOTICE: See 'Confidentiality Notice Regarding E-mail > Messages from Coscend Communications Solutions' posted at: > http://www.Coscend.com/Terms_and_Conditions.html > > > > On 07/22/16 10:49, Tech Developer wrote: > > Hi sir, > > I have installed 2 openmmetings in server > 1. http://www.tutorreal.com:5080/platform/signin > 2. http://www.tutorreal.com:5080/webmeetings/ > > For 2nd om i am able to get recording option in webinar and > conference rooms also.Screen Sharing Applet opened - Here I have no problem. > > But I have an issue in Share / Record option of Webinar, Conference > rooms in 1st om. I have attached log file and screen shot of this issue. > Recently I changed the name of openmeetings as platform. So Application can > be accessed from here http://www.tutorreal.com:5080/platform > > But when we click on the screenshare / record option in 1st OM it tries to > open the "Openmeetings Screen Sharing Applet" using the below url > > http://www.tutorreal.com:5080/openmeetings/screenshare/openmeetings-screenshare-3.1.1.jar > > How could i solve this issue? Please let me know > > > > > -- WBR Maxim aka solomax
