Dear Friend,

 

Due to personal reasons, Susheel is not available right now.  As suggested in 
his e-mail, in Red5.properties and config.xml of the installations, you could 
input the following:

 

1.     http://www.tutorreal.com:5080/platform/signin 

Ports: 5080, 1935

Database:  om_db1

 

Red5.properties

http.host=[server IP address]

http.port=5080

…

rtmp.port=1935

 

config.xml

<red5httpport>5080</red5httpport>

<rtmpport>1935</rtmpport>

<webAppRootKey>platform</webAppRootKey>  

<httpRootKey>/platform/</httpRootKey>


2.  http://www.tutorreal.com:5081/webmeetings/

Ports: 5081, 1936

Database:  om_db2 (a different database name)

 

Thank you.

 

Sincerely,

 

Hemant K. Sabat

 

Coscend Communications Solutions

Web site: www.Coscend.com <http://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 

 

 

 

From: Tech Developer [mailto:simatechdevelo...@gmail.com] 
Sent: Monday, August 22, 2016 12:55 AM
To: user@openmeetings.apache.org; susheel.jal...@coscend.com
Subject: Re: Share / Record Screen Issue

 

Hi Susheel Jalali,
  
I have installed 2 openmmetings in server   
1.  http://www.tutorreal.com:5080/platform/signin
2.  http://www.tutorreal.com:5080/webmeetings/
  I need a help, You mentioned that need to modify the configuration files to 
apply different port number for 2 om in same server.

How to i do this?

 

On Fri, Jul 22, 2016 at 11:02 PM, Susheel Jalali <susheel.jal...@coscend.com 
<mailto: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 <http://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

 

 

No virus found in this message.
Checked by AVG - www.avg.com <http://www.avg.com> 
Version: 2016.0.7752 / Virus Database: 4647/12854 - Release Date: 08/22/16

Reply via email to