Integration Problems
Hi everyone, I have OpenMeetings 2.1 on RedHat installed and use it within an application with the API to login directly, creating a room, creating hash and opening the application in an iframe. Now I have 2 clients in one room. I can see my own video, but not the video of the other person. If I change the video settings by increasing the resolution, my application freezes. In one case, when I changed the resolution of my video the other user was redirected to the normal landing page where you can see "My rooms", "Chat", "How to conference" and the user details. The red5.log shows some errors about languageservice; Header is null; Decoding error etc. The openmeetings.log has a ton of DEBUG messages and just like: "77 PublicSID: 7146f09e4b1b5f394ab634950ced6d7b UserId: 5 isScreenClient: false flvRecordingId: null screenPublishStarted: false flvRecordingMetaDataId: null isRecording: false isAVClient: false broadCastID: 69 avsettings: av server: null". The error.log is empty. We use SSL and RTMPS. I need to figure out what is causing those issues, but don't know where to start looking. Can you please help me? Thanks, Daniela
Re: Integration Problems
Thanks Maxim, I will try that. On 2013-07-05, at 10:42 PM, Maxim Solodovnik wrote: > Hello Daniela, > > can you please try if you issues are reproducible with just release 2.1.1 > version? > if yes you can try to increase log level (by editing conf/logback.xml) maybe > it can shed some light on it > Additionally I would try to check if the problem is reproducible without SSL > > > On Fri, Jul 5, 2013 at 11:05 PM, Daniela Kirsch > wrote: > Hi everyone, > > I have OpenMeetings 2.1 on RedHat installed and use it within an application > with the API to login directly, creating a room, creating hash and opening > the application in an iframe. > Now I have 2 clients in one room. I can see my own video, but not the video > of the other person. If I change the video settings by increasing the > resolution, my application freezes. In one case, when I changed the > resolution of my video the other user was redirected to the normal landing > page where you can see "My rooms", "Chat", "How to conference" and the user > details. > The red5.log shows some errors about languageservice; Header is null; > Decoding error etc. > The openmeetings.log has a ton of DEBUG messages and just like: "77 > PublicSID: 7146f09e4b1b5f394ab634950ced6d7b UserId: 5 isScreenClient: false > flvRecordingId: null screenPublishStarted: false flvRecordingMetaDataId: null > isRecording: false isAVClient: false broadCastID: 69 avsettings: av server: > null". > The error.log is empty. > We use SSL and RTMPS. > > I need to figure out what is causing those issues, but don't know where to > start looking. Can you please help me? > > Thanks, > Daniela > > > > > -- > WBR > Maxim aka solomax
RTMPS Setup for 2.1
Hi, we are trying to set up RTMPS with Open Meetings 2.1. There are 2 documents that we found: https://code.google.com/p/openmeetings/wiki/RTMPSandHTTPS http://openmeetings.apache.org/RTMPSAndHTTPS.html They are almost identical, however both say Open Meetings 1.9 is required. So are the settings the same for 2.1? If not, is there some other documentation? In the red5.log we get a few error messages on server startup (8443 is the port we want to use): 2013-07-31 14:14:20,424 [main] ERROR o.a.coyote.http11.Http11NioProtocol - Failed to initialize end point associated with ProtocolHandler ["http-nio-8443"] java.net.BindException: Address already in use 2013-07-31 14:14:20,425 [main] ERROR o.a.catalina.core.StandardService - Failed to start connector [Connector[org.apache.coyote.http11.Http11NioProtocol-8443]] org.apache.catalina.LifecycleException: Failed to initialize component [Connector[org.apache.coyote.http11.Http11NioProtocol-8443]] 2013-07-31 14:14:20,427 [main] ERROR o.a.coyote.http11.Http11NioProtocol - Failed to start end point associated with ProtocolHandler ["http-nio-8443"] java.net.BindException: Address already in use 2013-07-31 14:14:20,428 [main] ERROR o.r.server.tomcat.rtmps.RTMPSLoader - Error initializing RTMPS server instance org.apache.catalina.LifecycleException: Failed to start component [Connector[org.apache.coyote.http11.Http11NioProtocol-8443]] When we disable port 1935 lots of problems occur and we can't use the application. Thanks, Daniela
Re: RTMPS Setup for 2.1
Hi, netstat only shows one line for port 8443 when OpenMeetings is started, it doesn't list anything when ended: tcp0 0 0.0.0.0:84430.0.0.0:* LISTEN However I did search a bit and found that it could be caused when red5 isn't shut down properly, meaning when you kill the process it might not release the ports. So the suggestion was to use red5-shutdown.sh That script is a little confusing, do we have to change it? It's the following right now: # port, username, password export RED5_OPTS=" red5user changeme" export RED5_MAINCLASS=org.red5.server.Shutdown exec $RED5_HOME/red5.sh But if we were to change that line with port, username, password, what would it be? Thanks, Daniela On 2013-07-31, at 4:19 PM, Maxim Solodovnik wrote: > Hello Daniela, > > http://openmeetings.apache.org/RTMPSAndHTTPS.html is the most recent > document. According to my observations all need to be done is to follow this > instruction step by step :) > > "Address already in use" usually means some other application is using same > port (can be checked with netstat) > > > On Thu, Aug 1, 2013 at 5:32 AM, Daniela Kirsch > wrote: > Hi, > > we are trying to set up RTMPS with Open Meetings 2.1. > > There are 2 documents that we found: > https://code.google.com/p/openmeetings/wiki/RTMPSandHTTPS > http://openmeetings.apache.org/RTMPSAndHTTPS.html > > They are almost identical, however both say Open Meetings 1.9 is required. So > are the settings the same for 2.1? If not, is there some other documentation? > > In the red5.log we get a few error messages on server startup (8443 is the > port we want to use): > 2013-07-31 14:14:20,424 [main] ERROR o.a.coyote.http11.Http11NioProtocol - > Failed to initialize end point associated with ProtocolHandler > ["http-nio-8443"] > java.net.BindException: Address already in use > > 2013-07-31 14:14:20,425 [main] ERROR o.a.catalina.core.StandardService - > Failed to start connector > [Connector[org.apache.coyote.http11.Http11NioProtocol-8443]] > org.apache.catalina.LifecycleException: Failed to initialize component > [Connector[org.apache.coyote.http11.Http11NioProtocol-8443]] > > 2013-07-31 14:14:20,427 [main] ERROR o.a.coyote.http11.Http11NioProtocol - > Failed to start end point associated with ProtocolHandler ["http-nio-8443"] > java.net.BindException: Address already in use > > 2013-07-31 14:14:20,428 [main] ERROR o.r.server.tomcat.rtmps.RTMPSLoader - > Error initializing RTMPS server instance > org.apache.catalina.LifecycleException: Failed to start component > [Connector[org.apache.coyote.http11.Http11NioProtocol-8443]] > > When we disable port 1935 lots of problems occur and we can't use the > application. > > Thanks, > Daniela > > > > -- > WBR > Maxim aka solomax
Re: RTMPS Setup for 2.1
No, we use 7443 for HTTPS and 8443 for RTMPS. In our red5.properties: policy.port=843 http.port=5080 https.port=7443 rtmp.port=1935 rtmps.port=8443 rtmpt.port=8088 On 2013-08-01, at 9:51 AM, Maxim Solodovnik wrote: > Is it possible you have chosed 8443 for both RTMPS and HTTPS? OM 2.1 requires > 2-3 _different_ ports > > > On Thu, Aug 1, 2013 at 10:14 PM, Daniela Kirsch > wrote: > Hi, > > netstat only shows one line for port 8443 when OpenMeetings is started, it > doesn't list anything when ended: > tcp0 0 0.0.0.0:84430.0.0.0:* > LISTEN > > However I did search a bit and found that it could be caused when red5 isn't > shut down properly, meaning when you kill the process it might not release > the ports. So the suggestion was to use red5-shutdown.sh > That script is a little confusing, do we have to change it? It's the > following right now: > > # port, username, password > export RED5_OPTS=" red5user changeme" > export RED5_MAINCLASS=org.red5.server.Shutdown > exec $RED5_HOME/red5.sh > > But if we were to change that line with port, username, password, what would > it be? > > Thanks, > Daniela > > On 2013-07-31, at 4:19 PM, Maxim Solodovnik wrote: > >> Hello Daniela, >> >> http://openmeetings.apache.org/RTMPSAndHTTPS.html is the most recent >> document. According to my observations all need to be done is to follow this >> instruction step by step :) >> >> "Address already in use" usually means some other application is using same >> port (can be checked with netstat) >> >> >> On Thu, Aug 1, 2013 at 5:32 AM, Daniela Kirsch >> wrote: >> Hi, >> >> we are trying to set up RTMPS with Open Meetings 2.1. >> >> There are 2 documents that we found: >> https://code.google.com/p/openmeetings/wiki/RTMPSandHTTPS >> http://openmeetings.apache.org/RTMPSAndHTTPS.html >> >> They are almost identical, however both say Open Meetings 1.9 is required. >> So are the settings the same for 2.1? If not, is there some other >> documentation? >> >> In the red5.log we get a few error messages on server startup (8443 is the >> port we want to use): >> 2013-07-31 14:14:20,424 [main] ERROR o.a.coyote.http11.Http11NioProtocol - >> Failed to initialize end point associated with ProtocolHandler >> ["http-nio-8443"] >> java.net.BindException: Address already in use >> >> 2013-07-31 14:14:20,425 [main] ERROR o.a.catalina.core.StandardService - >> Failed to start connector >> [Connector[org.apache.coyote.http11.Http11NioProtocol-8443]] >> org.apache.catalina.LifecycleException: Failed to initialize component >> [Connector[org.apache.coyote.http11.Http11NioProtocol-8443]] >> >> 2013-07-31 14:14:20,427 [main] ERROR o.a.coyote.http11.Http11NioProtocol - >> Failed to start end point associated with ProtocolHandler ["http-nio-8443"] >> java.net.BindException: Address already in use >> >> 2013-07-31 14:14:20,428 [main] ERROR o.r.server.tomcat.rtmps.RTMPSLoader - >> Error initializing RTMPS server instance >> org.apache.catalina.LifecycleException: Failed to start component >> [Connector[org.apache.coyote.http11.Http11NioProtocol-8443]] >> >> When we disable port 1935 lots of problems occur and we can't use the >> application. >> >> Thanks, >> Daniela >> >> >> >> -- >> WBR >> Maxim aka solomax > > > > > -- > WBR > Maxim aka solomax
Re: RTMPS Setup for 2.1
Hi, I've been checking the logs again and here's what I get from red5: 2013-08-09 13:58:56,293 [main] INFO o.r.s.net.rtmp.RTMPMinaTransport - RTMP Mina Transport bound to /0.0.0.0:1935 2013-08-09 13:58:56,387 [main] INFO o.r.s.net.rtmp.RTMPMinaTransport - RTMP Mina Transport bound to /0.0.0.0:8443 2013-08-09 13:58:56,897 [main] INFO o.a.coyote.http11.Http11Protocol - Initializing ProtocolHandler ["http-bio-0.0.0.0-7443"] 2013-08-09 13:59:07,223 [main] INFO o.a.coyote.http11.Http11Protocol - Starting ProtocolHandler ["http-bio-0.0.0.0-7443"] 2013-08-09 13:59:09,697 [main] INFO o.a.coyote.http11.Http11NioProtocol - Initializing ProtocolHandler ["http-nio-8088"] 2013-08-09 13:59:09,704 [main] INFO o.a.coyote.http11.Http11NioProtocol - Starting ProtocolHandler ["http-nio-8088"] 2013-08-09 13:59:11,998 [main] INFO o.a.coyote.http11.Http11NioProtocol - Initializing ProtocolHandler ["http-nio-8443"] 2013-08-09 13:59:12,004 [main] INFO o.a.coyote.http11.Http11NioProtocol - Stopping ProtocolHandler ["http-nio-8443"] 2013-08-09 13:59:12,004 [main] INFO o.a.coyote.http11.Http11NioProtocol - Starting ProtocolHandler ["http-nio-8443"] So it actually does sound like for some reason we do use 8443 for both. We've been through the configuration now a few times. One part I don't understand is this: Edit red5/conf/jee-container.xml file: Comment Tomcat without SSL enabled section UNComment Tomcat with SSL enabled section I didn't actually do the setup but a colleague did that and he said: "After certain version of Openmeetings, jee-container.xml doesn't have the tomcat commented sections anymore. Instead, there are 2 xml files - jee-container.xml and jee-container-ssl.xml. To enable SSL, I think I only had to rename the jee-container to another name. And the one with the ssl to jee-container.xml." So reading the above I'm thinking there's an issue in our jee-container.xml. But which section exactly would I have to comment? Would it be the whole section of or just some part of it? There's also a section for RTMPT, should that be active? Thanks, Daniela On 2013-08-01, at 9:51 AM, Maxim Solodovnik wrote: > Is it possible you have chosed 8443 for both RTMPS and HTTPS? OM 2.1 requires > 2-3 _different_ ports > > > On Thu, Aug 1, 2013 at 10:14 PM, Daniela Kirsch > wrote: > Hi, > > netstat only shows one line for port 8443 when OpenMeetings is started, it > doesn't list anything when ended: > tcp0 0 0.0.0.0:84430.0.0.0:* > LISTEN > > However I did search a bit and found that it could be caused when red5 isn't > shut down properly, meaning when you kill the process it might not release > the ports. So the suggestion was to use red5-shutdown.sh > That script is a little confusing, do we have to change it? It's the > following right now: > > # port, username, password > export RED5_OPTS=" red5user changeme" > export RED5_MAINCLASS=org.red5.server.Shutdown > exec $RED5_HOME/red5.sh > > But if we were to change that line with port, username, password, what would > it be? > > Thanks, > Daniela > > On 2013-07-31, at 4:19 PM, Maxim Solodovnik wrote: > >> Hello Daniela, >> >> http://openmeetings.apache.org/RTMPSAndHTTPS.html is the most recent >> document. According to my observations all need to be done is to follow this >> instruction step by step :) >> >> "Address already in use" usually means some other application is using same >> port (can be checked with netstat) >> >> >> On Thu, Aug 1, 2013 at 5:32 AM, Daniela Kirsch >> wrote: >> Hi, >> >> we are trying to set up RTMPS with Open Meetings 2.1. >> >> There are 2 documents that we found: >> https://code.google.com/p/openmeetings/wiki/RTMPSandHTTPS >> http://openmeetings.apache.org/RTMPSAndHTTPS.html >> >> They are almost identical, however both say Open Meetings 1.9 is required. >> So are the settings the same for 2.1? If not, is there some other >> documentation? >> >> In the red5.log we get a few error messages on server startup (8443 is the >> port we want to use): >> 2013-07-31 14:14:20,424 [main] ERROR o.a.coyote.http11.Http11NioProtocol - >> Failed to initialize end point associated with ProtocolHandler >> ["http-nio-8443"] >> java.net.BindException: Address already in use >> >> 2013-07-31 14:14:20,425 [main] ERROR o.a.catalina.core.StandardService - >> Failed to start connector >> [Connector[org.apache.coyote.http11.Http11NioProtocol-8443]] >>
Re: RTMPS Setup for 2.1
We tried that now, but that actually resulted in Open Meetings not even starting up. We are running v2.1 but downloaded jee-container.xml from version 2.1.1, commented the RTMPT part and uncommented RTMPS. If we use jee-container-ssl.xml from v2.1.1 it does start up but we believe it doesn't use RTMPS at all (there's nothing in the logs saying anything about RTMPS, everywhere it says RTMP). What is the proper way to set it up? Also, the documentation says: Edit red5/webapps/openmeetings/public/config.xml and set 5443 , yes and best However there's no config.xml in that folder, it is in red5/webapps/openmeetings/ (no public in the path). Is that just because the documentation was for v1.9? Thanks, Daniela On Tue, Aug 13, 2013 at 8:04 AM, Maxim Solodovnik wrote: > I would recommend not to use jee*ssl.xml > but comment > > and uncomment > > > sorry for the late response :( > > > > > On Sat, Aug 10, 2013 at 3:32 AM, Daniela Kirsch > wrote: > >> Hi, >> >> I've been checking the logs again and here's what I get from red5: >> >> 2013-08-09 13:58:56,293 [main] INFO o.r.s.net.rtmp.RTMPMinaTransport - >> RTMP Mina Transport bound to /0.0.0.0:*1935* >> 2013-08-09 13:58:56,387 [main] INFO o.r.s.net.rtmp.RTMPMinaTransport - >> RTMP Mina Transport bound to /0.0.0.0:*8443* >> >> 2013-08-09 13:58:56,897 [main] INFO o.a.coyote.http11.Http11Protocol - >> Initializing ProtocolHandler ["http-bio-0.0.0.0-*7443*"] >> 2013-08-09 13:59:07,223 [main] INFO o.a.coyote.http11.Http11Protocol - >> Starting ProtocolHandler ["http-bio-0.0.0.0-*7443*"] >> 2013-08-09 13:59:09,697 [main] INFO o.a.coyote.http11.Http11NioProtocol >> - Initializing ProtocolHandler ["http-nio-*8088*"] >> 2013-08-09 13:59:09,704 [main] INFO o.a.coyote.http11.Http11NioProtocol >> - Starting ProtocolHandler ["http-nio-*8088*"] >> 2013-08-09 13:59:11,998 [main] INFO o.a.coyote.http11.Http11NioProtocol >> - Initializing ProtocolHandler ["http-nio-*8443*"] >> 2013-08-09 13:59:12,004 [main] INFO o.a.coyote.http11.Http11NioProtocol >> - Stopping ProtocolHandler ["http-nio-*8443*"] >> 2013-08-09 13:59:12,004 [main] INFO o.a.coyote.http11.Http11NioProtocol >> - Starting ProtocolHandler ["http-nio-*8443*"] >> >> So it actually does sound like for some reason we do use 8443 for both. >> We've been through the configuration now a few times. One part I don't >> understand is this: >> >> *Edit red5/conf/jee-container.xml file:* >> *Comment Tomcat without SSL enabled section* >> *UNComment Tomcat with SSL enabled section* >> >> I didn't actually do the setup but a colleague did that and he said: >> "After certain version of Openmeetings, jee-container.xml doesn't have >> the tomcat commented sections anymore. Instead, there are 2 xml files - >> jee-container.xml and jee-container-ssl.xml. To enable SSL, I think I only >> had to rename the jee-container to another name. And the one with the ssl >> to jee-container.xml." >> >> So reading the above I'm thinking there's an issue in our >> jee-container.xml. But which section exactly would I have to comment? Would >> it be the whole section of >> > init-method="init" destroy-method="shutdown" depends-on="context.loader"> >> or just some part of it? There's also a section for RTMPT, should that be >> active? >> >> Thanks, >> Daniela >> >> >> On 2013-08-01, at 9:51 AM, Maxim Solodovnik wrote: >> >> Is it possible you have chosed 8443 for both RTMPS and HTTPS? OM 2.1 >> requires 2-3 _different_ ports >> >> >> On Thu, Aug 1, 2013 at 10:14 PM, Daniela Kirsch > > wrote: >> >>> Hi, >>> >>> netstat only shows one line for port 8443 when OpenMeetings is started, >>> it doesn't list anything when ended: >>> tcp0 0 0.0.0.0:84430.0.0.0:* >>> LISTEN >>> >>> However I did search a bit and found that it could be caused when red5 >>> isn't shut down properly, meaning when you kill the process it might not >>> release the ports. So the suggestion was to use red5-shutdown.sh >>> That script is a little confusing, do we have to change it? It's the >>> following right now: >>> >>> # port, username, password >>> export RED5_OPTS="* red5user changeme*" >>> export RED5_MAINCLASS=org.red5.server.Shutdown >>> exec $RED5_HOME/red5.sh >>> >>> B
Video Frozen - OpenMeetings/Red5 stuck
Hi,
we are running into a serious issue. While being in a room with video and audio
(2 people in a normal moderated conference room) it happens that the video of
the other person freezes (audio is gone as well).
Once the video is frozen, the entire application is unusable. Meaning, if I
open a browser and go to the site all I get is a blank page. There's nothing,
not even a "Loading..." displayed. This is for everyone who's trying to use it,
not just the person who had the frozen video.
In the red5.log we have this:
2013-09-05 14:39:13,289 [NioProcessor-33] DEBUG
o.red5.server.net.rtmp.RTMPHandler - Invoke: Invoke: Service: null Method:
connect Num Params: 1 0: false
2013-09-05 14:39:13,289 [NioProcessor-33] DEBUG
o.red5.server.net.rtmp.RTMPHandler - call: Service: null Method: connect Num
Params: 1 0: false
2013-09-05 14:39:13,289 [NioProcessor-33] DEBUG
o.red5.server.net.rtmp.RTMPHandler - connect
2013-09-05 14:39:13,289 [NioProcessor-33] DEBUG
o.r.server.net.rtmp.BaseRTMPHandler - url:
rtmps://my.domain.com:8443/openmeetings/hibernate
2013-09-05 14:39:17,818 [Red5_Scheduler_Worker-3] WARN
o.r.server.net.rtmp.RTMPConnection - Closing RTMPMinaConnection from 1.1.1.1 :
39724 to my.domain.com:8443 (in: 3729 out 4878 ), with id 16 due to long
handshake
2013-09-05 14:39:17,819 [Red5_Scheduler_Worker-3] DEBUG
o.r.s.net.rtmp.RTMPMinaConnection - RTMP state: RTMP [state=connected,
debug=false, encrypted=false, lastReadChannel=3, lastWriteChannel=0,
readHeaders={3=Header [channelId=3, dataType=20, timerBase=0, timerDelta=0,
size=407, streamId=0, extendedTimestamp=0, isGarbage=false]}, writeHeaders={},
readPacketHeaders={3=Header [channelId=3, dataType=20, timerBase=0,
timerDelta=0, size=407, streamId=0, extendedTimestamp=0, isGarbage=false]},
readPackets={3=null}, writePackets={}, writeTimestamps={}, liveTimestamps={},
readChunkSize=128, writeChunkSize=128, encoding=AMF0]
The only way to get it all going is by restarting Open Meetings. However we
were hoping there's a way around that, something that would free whatever is
stuck there.
What can we do?
Thanks,
Daniela
Re: Video Frozen - OpenMeetings/Red5 stuck
I'll try to answer your questions:
What version of OpenMeetings are you using (2.0, 2.1, 2.1.1, 3.0 etc)?
2.1
On what OS are you running OpenMeetings. E.g. Windows 7, Windows Server
2008, Ubuntu server 12, Debian (5/6/7), Centos, etc?
RedHat Enterprise
How did you get OpenMeetings, from what repository? Did you download the
compiled version or did you down load the source and compile it locally on
the server?
Downloaded the compiled version from the websites download link.
What installation instructions did you follow to build the environment in
which you are running OpenMeetings? Are all the prerequisite packages
installed?
We didn't install ffmpeg. Not sure what instructions have been used.
Possibly quite a few different ones, we did start out with v1.9 or even
earlier, we've been on this for over 1 year to find a version that actually
does work for our needs.
What ports are you using for OpenMeetings (e.g. netstat -anp | grep java),
and I guess all firewall ports are open otherwise people would have been
able to start the meeting.
7443 for the web interface (SSL), 8443 for RTMPS. Ports are open on the
firewall.
Is the server a dedicated server for OpenMeetings or are other red5
applications also running on the server?
It's the only red5 application, but we also have Apache, Node, MySQL and a
bunch of other things running, all on their own ports though.
On Fri, Sep 6, 2013 at 4:18 PM, George Kirkham wrote:
> Daniela,
>
> ** **
>
> Sorry I cannot help you with this problem as we have never experienced it,
> however others may be able to give you some assistance.
>
> ** **
>
> To help other assist you, can you give us more detail, please.
>
> ** **
>
> What version of OpenMeetings are you using (2.0, 2.1, 2.1.1, 3.0 etc)?
>
> ** **
>
> On what OS are you running OpenMeetings. E.g. Windows 7, Windows Server
> 2008, Ubuntu server 12, Debian (5/6/7), Centos, etc?
>
> ** **
>
> How did you get OpenMeetings, from what repository?
>
> ** **
>
> Did you download the compiled version or did you down load the source and
> compile it locally on the server?
>
> ** **
>
> What installation instructions did you follow to build the environment in
> which you are running OpenMeetings? Are all the prerequisite packages
> installed?
>
> ** **
>
> What ports are you using for OpenMeetings (e.g. netstat -anp | grep java),
> and I guess all firewall ports are open otherwise people would have been
> able to start the meeting.
>
> ** **
>
> Is the server a dedicated server for OpenMeetings or are other red5
> applications also running on the server?
>
> ** **
>
> Thanks,
>
> ** **
>
> George Kirkham
>
> ** **
>
> ** **
>
> *From:* Daniela Kirsch [mailto:dkir...@excelsystems.com]
> *Sent:* Saturday, 7 September 2013 1:18 AM
> *To:* user@openmeetings.apache.org
> *Subject:* Video Frozen - OpenMeetings/Red5 stuck
>
> ** **
>
> Hi,
>
> ** **
>
> we are running into a serious issue. While being in a room with video and
> audio (2 people in a normal moderated conference room) it happens that the
> video of the other person freezes (audio is gone as well).
>
> Once the video is frozen, the entire application is unusable. Meaning, if
> I open a browser and go to the site all I get is a blank page. There's
> nothing, not even a "Loading..." displayed. This is for everyone who's
> trying to use it, not just the person who had the frozen video.
>
> ** **
>
> In the red5.log we have this:
>
> 2013-09-05 14:39:13,289 [NioProcessor-33] DEBUG
> o.red5.server.net.rtmp.RTMPHandler - Invoke: Invoke: Service: null Method:
> connect Num Params: 1 0: false
>
> 2013-09-05 14:39:13,289 [NioProcessor-33] DEBUG
> o.red5.server.net.rtmp.RTMPHandler - call: Service: null Method: connect
> Num Params: 1 0: false
>
> 2013-09-05 14:39:13,289 [NioProcessor-33] DEBUG
> o.red5.server.net.rtmp.RTMPHandler - connect
>
> 2013-09-05 14:39:13,289 [NioProcessor-33] DEBUG
> o.r.server.net.rtmp.BaseRTMPHandler - url:
> rtmps://my.domain.com:8443/openmeetings/hibernate
>
> 2013-09-05 14:39:17,818 [Red5_Scheduler_Worker-3] WARN
> o.r.server.net.rtmp.RTMPConnection - *Closing RTMPMinaConnection from
> 1.1.1.1 : 39724 to my.domain.com:8443 (in: 3729 out 4878 ), with id 16
> due to long handshake*
>
> 2013-09-05 14:39:17,819 [Red5_Scheduler_Worker-3] DEBUG
> o.r.s.net.rtmp.RTMPMinaConnection - RTMP state: RTMP [state=connected,
> debug=false, encrypted=false, lastReadChannel=3, lastWriteChannel=0,
> readHeaders={3=Header [channelId=3, dataType=20, timerBase=0, timerDelta=0,
> size=407, streamId=0, extendedTimestamp=
Re: Video Frozen - OpenMeetings/Red5 stuck
Thanks John, I did see that email but as you now know we don't have a
solution. I'm hoping someone can help us.
Daniela Kirsch
Web Developer
ExcelSystems Software Development Inc.
101 - 9274 4th St.
Sidney, BC V8L 2Y7
Phone: (250) 655 1882 ext: 209
Email: dkir...@excelsystems.com
On Fri, Sep 6, 2013 at 4:27 PM, John Tran wrote:
> I experienced the same issue. It seem like the issue occurs when it's in
> SSL configuration. If you notice, it looked like Danella configuration in
> SSL mode. I post the same issue back on August 27th "More Disconnect on
> ssl connection than non ssl
> connection<http://mail-archives.apache.org/mod_mbox/openmeetings-user/201308.mbox/ajax/%3CCAOq_-sy0gp-f_LEaB8MBgzuvuot70xySkw2h%2BugcG%2BvnnNm3XQ%40mail.gmail.com%3E>"
> hoping someone like yourself or Maxim to respond but no luck.
>
>
>
>
> On Fri, Sep 6, 2013 at 4:18 PM, George Kirkham wrote:
>
>> Daniela,
>>
>> ** **
>>
>> Sorry I cannot help you with this problem as we have never experienced
>> it, however others may be able to give you some assistance.
>>
>> ** **
>>
>> To help other assist you, can you give us more detail, please.
>>
>> ** **
>>
>> What version of OpenMeetings are you using (2.0, 2.1, 2.1.1, 3.0 etc)?***
>> *
>>
>> ** **
>>
>> On what OS are you running OpenMeetings. E.g. Windows 7, Windows Server
>> 2008, Ubuntu server 12, Debian (5/6/7), Centos, etc?
>>
>> ** **
>>
>> How did you get OpenMeetings, from what repository?
>>
>> ** **
>>
>> Did you download the compiled version or did you down load the source and
>> compile it locally on the server?
>>
>> ** **
>>
>> What installation instructions did you follow to build the environment in
>> which you are running OpenMeetings? Are all the prerequisite packages
>> installed?
>>
>> ** **
>>
>> What ports are you using for OpenMeetings (e.g. netstat -anp | grep
>> java), and I guess all firewall ports are open otherwise people would have
>> been able to start the meeting.
>>
>> ** **
>>
>> Is the server a dedicated server for OpenMeetings or are other red5
>> applications also running on the server?
>>
>> ** **
>>
>> Thanks,
>>
>> ** **
>>
>> George Kirkham
>>
>> ** **
>>
>> ** **
>>
>> *From:* Daniela Kirsch [mailto:dkir...@excelsystems.com]
>> *Sent:* Saturday, 7 September 2013 1:18 AM
>> *To:* user@openmeetings.apache.org
>> *Subject:* Video Frozen - OpenMeetings/Red5 stuck
>>
>> ** **
>>
>> Hi,
>>
>> ** **
>>
>> we are running into a serious issue. While being in a room with video and
>> audio (2 people in a normal moderated conference room) it happens that the
>> video of the other person freezes (audio is gone as well).
>>
>> Once the video is frozen, the entire application is unusable. Meaning, if
>> I open a browser and go to the site all I get is a blank page. There's
>> nothing, not even a "Loading..." displayed. This is for everyone who's
>> trying to use it, not just the person who had the frozen video.
>>
>> ** **
>>
>> In the red5.log we have this:
>>
>> 2013-09-05 14:39:13,289 [NioProcessor-33] DEBUG
>> o.red5.server.net.rtmp.RTMPHandler - Invoke: Invoke: Service: null Method:
>> connect Num Params: 1 0: false
>>
>> 2013-09-05 14:39:13,289 [NioProcessor-33] DEBUG
>> o.red5.server.net.rtmp.RTMPHandler - call: Service: null Method: connect
>> Num Params: 1 0: false
>>
>> 2013-09-05 14:39:13,289 [NioProcessor-33] DEBUG
>> o.red5.server.net.rtmp.RTMPHandler - connect
>>
>> 2013-09-05 14:39:13,289 [NioProcessor-33] DEBUG
>> o.r.server.net.rtmp.BaseRTMPHandler - url:
>> rtmps://my.domain.com:8443/openmeetings/hibernate
>>
>> 2013-09-05 14:39:17,818 [Red5_Scheduler_Worker-3] WARN
>> o.r.server.net.rtmp.RTMPConnection - *Closing RTMPMinaConnection from
>> 1.1.1.1 : 39724 to my.domain.com:8443 (in: 3729 out 4878 ), with id 16
>> due to long handshake*
>>
>> 2013-09-05 14:39:17,819 [Red5_Scheduler_Worker-3] DEBUG
>> o.r.s.net.rtmp.RTMPMinaConnection - RTMP state: RTMP [state=connected,
>> debug=false, encrypted=false, lastReadChannel=3, lastWriteChannel=0,
>> readHeaders={3=Header [channelId=3, dataType=20, timerBase=0, timerDelta=0,
>> size=407, streamId=0, extendedTimestamp=0, isGarbage=false]},
>> writeHeaders={}, readPacke
Re: Error while calling RoomWebService
Did you check all the parms are submitted? According to the documentation
http://openmeetings.apache.org/RoomService.html#addRoomWithModerationAndExternalTypeAndStartEnd
and comparing to what I see in your code you're missing a few.
You can also try building the URL by hand and go to it in the browser directly
to see if it at least should work outside of any other program and language.
On 2013-09-07, at 6:57 PM, Pradeep D wrote:
> -- Forwarded message --
> From: "Pradeep D"
> Date: 8 Sep 2013 00:17
> Subject: Error while calling RoomWebService
> To: ,
> Cc:
>
> Hi All,
>
> I download the latest openmeeting 2.1.1m We are calling RoomWebService.
> addRoomWithModerationAndExternalTypeAndStartEnd
> method which is throwing the below exception,
> http://localhost:5080/openmeetings/services/RoomService
> Exception in thread "main"
> com.sun.jersey.api.client.UniformInterfaceException: GET
> http://localhost:5080/openmeetings/services/RoomService returned a response
> status of 500 Internal Server Error
> at com.sun.jersey.api.client.WebResource.handle(WebResource.java:686)
> at com.sun.jersey.api.client.WebResource.get(WebResource.java:191)
> at
> openmeetingtest.OpenMeetingService.addNewRoomWithModeratorLimitedTime(OpenMeetingService.java:109)
> at openmeetingtest.OpenMeetingTest.main(OpenMeetingTest.java:26)
>
> Below is the code for calling the REST service
>
> SimpleDateFormat dfDate = new SimpleDateFormat("dd.MM.");
> SimpleDateFormat dfTime = new SimpleDateFormat("mm:hh");
>
> Client client = new Client();
> WebResource webResource =
> client.resource(openMeetingServiceUrl+"/RoomService");
>
> MultivaluedMap queryParams = new MultivaluedMapImpl();
> queryParams.add("SID",sessionResponse.getSession_id());
> queryParams.add("name","Meeting_"+meetingId);
> queryParams.add("roomtypes_id","1");
> queryParams.add("numberOfPartizipants",numberOfUsers.toString());
> queryParams.add("ispublic","false");
> queryParams.add("appointment","false");
> queryParams.add("isDemoRoom","false");
> queryParams.add("isModeratedRoom","true");
> queryParams.add("externalRoomType","ebox");
> queryParams.add("validFromDate",dfDate.format(new Date()));
> queryParams.add("validFromTime",dfTime.format(new Date()));
> queryParams.add("validToDate",dfDate.format(new Date()));
> queryParams.add("validToTime",dfTime.format(new Date()));
> queryParams.add("isPasswordProtected","false");
> queryParams.add("reminderTypeId","1");
> queryParams.add("redirectURL","1");
>
>
> webResource.path("addRoomWithModerationAndExternalTypeAndStartEnd").queryParams(queryParams);
> System.out.println(webResource.getURI());
> String buffer = webResource.get(String.class);
>
> System.out.println("response:"+buffer);
>
> ResponseHandler handler = (ResponseHandler)
> SAXParserHelper.parse(buffer,ResponseHandler.class);
>
> Kindly help me in identifying the problem.
>
> Thanks
> Pradeep D
Re: Video Frozen - OpenMeetings/Red5 stuck
So we got around to testing this version as well. The best we got was 5 seconds of video working before it froze, however it didn't crash the server... We won't try non-SSL with this version. If I understand correctly 2.2 will have the updated Red5 server or is this 2.2? Sorry a little confused as to what version it is now. On 2013-09-11, at 2:51 PM, John Tran wrote: > Maxim - > > I am not getting video/audio on SSL/RTMPS connection from the far end and > vice versa. I logged in fine and enter a room, and start a conference. I > get a black screen from far end and vice versa. Local video is fine. I > hangs when logging out. "Loading..." in red just stays there, > > Will try this non SSL/RTMPS mode if it i experience these issues. > > -john- > > > On Wed, Sep 11, 2013 at 10:50 AM, Maxim Solodovnik > wrote: > red5 server was updated in 2.2. > I need help in testing of this major change. > If this build will be considered more stable I'll update the instructions. > I haven't checked SSL yet. Hopefully will check this week > > > On Thu, Sep 12, 2013 at 12:43 AM, John Tran wrote: > Oh, Ok. "keystore" file I have, just not "keystore.screen" > I finally got it working, or at least up and accessible via SSL web interface > and RTMPS port listening. > > Can you clarify the below for me? > > I did not have to comment out the below on the 2.1 build/installtion > > > Why now on the 2.2 build for it to work? > > Secondly, why is the jee-container-ssl.xml missing on the 2.2 build. The > existing jee-container.xml that comes with the build not not seem work when > you try to access the page via https. I had to copy it jee-container-ssl.xml > from the 2.1 build and rename to jee-container.xml in order to access the > page via https successfully. > > Thank again Maxim for your guidance. > > -john- > > > > On Wed, Sep 11, 2013 at 10:00 AM, Maxim Solodovnik > wrote: > you need to create it as you have created "keystore" file (as stated here: > http://openmeetings.apache.org/RTMPSAndHTTPS.html) > > > On Wed, Sep 11, 2013 at 11:58 PM, John Tran wrote: > Where would I get that? keystore.screen is no where to be found when I do a > search. I just finish a build from scratch from an svn checkout installation. > > > On Wed, Sep 11, 2013 at 9:54 AM, Maxim Solodovnik > wrote: > keystore.screen is necessary for screensharing via RTMPS > > > On Wed, Sep 11, 2013 at 11:09 PM, John Tran wrote: > Thanks Maxim. My setting are identical int he config.xml except that values > are different. > > As for the red5-core.xml setting. I did't comment out the below > > > - > > + > > I left as is like I did in all of my 2.1 set up configuration. I will > comment out on the 2.2 build and see if it works. > > As for the ../conf directory, I don't have a keystore.screen file. I just > have keystore file that I created and keystore.jmx file that is already there. > > > > -- > WBR > Maxim aka solomax > > > > -- > jt > > John Tran > Northern California, CA > findingj...@gmail.com > ICQ IM: 27741710 > AOL IM: find1ngj0hn > Yahoo! IM: findingj0hn >MSN IM: findingj...@hotmail.com > > > > -- > WBR > Maxim aka solomax > > > > -- > jt > > John Tran > Northern California, CA > findingj...@gmail.com > ICQ IM: 27741710 > AOL IM: find1ngj0hn > Yahoo! IM: findingj0hn >MSN IM: findingj...@hotmail.com > > > > -- > WBR > Maxim aka solomax > > > > -- > jt > > John Tran > Northern California, CA > findingj...@gmail.com > ICQ IM: 27741710 > AOL IM: find1ngj0hn > Yahoo! IM: findingj0hn >MSN IM: findingj...@hotmail.com
Re: Video Frozen - OpenMeetings/Red5 stuck
Hi John, we got video once from the other end for about 5 seconds. We did also have that black video window, or a frozen video basically from the start. The local video was always working. Not sure if the browser makes any difference, but we did use Safari on Mac and Firefox on Windows 7. So it wasn't really any kind of success. We did install apache-openmeetings-2.2.0.r1522507-12-09-2013_0953. It's setup with SSL and RTMPS. On another note, we use the direct login and set up rooms with the REST APIs (OM runs in an iframe in our application). Don't think it makes any difference though. I'm wondering, could it make any difference to the disconnects in 2.1 when you're on Wifi compared to wired network? We weren't able to pin point what causes it, except when I let the screensaver start. Thanks, Daniela On 2013-09-12, at 10:40 PM, John Tran wrote: > Daniela, you are actually getting audio/video from the other end? I still > cant it on the latest 2.2 build (2.2.0-SNAPSHOT 1522507) on SSL and non SSL > mode and all of my build are from scratch and bare bone installation of the > OS and OM2.2. > > > > > On Thu, Sep 12, 2013 at 3:57 PM, Daniela Kirsch > wrote: > So we got around to testing this version as well. The best we got was 5 > seconds of video working before it froze, however it didn't crash the > server... > > We won't try non-SSL with this version. > > If I understand correctly 2.2 will have the updated Red5 server or is this > 2.2? Sorry a little confused as to what version it is now. > > > On 2013-09-11, at 2:51 PM, John Tran wrote: > >> Maxim - >> >> I am not getting video/audio on SSL/RTMPS connection from the far end and >> vice versa. I logged in fine and enter a room, and start a conference. I >> get a black screen from far end and vice versa. Local video is fine. I >> hangs when logging out. "Loading..." in red just stays there, >> >> Will try this non SSL/RTMPS mode if it i experience these issues. >> >> -john- >> >> >> On Wed, Sep 11, 2013 at 10:50 AM, Maxim Solodovnik >> wrote: >> red5 server was updated in 2.2. >> I need help in testing of this major change. >> If this build will be considered more stable I'll update the instructions. >> I haven't checked SSL yet. Hopefully will check this week >> >> >> On Thu, Sep 12, 2013 at 12:43 AM, John Tran wrote: >> Oh, Ok. "keystore" file I have, just not "keystore.screen" >> I finally got it working, or at least up and accessible via SSL web >> interface and RTMPS port listening. >> >> Can you clarify the below for me? >> >> I did not have to comment out the below on the 2.1 build/installtion >> >> >> Why now on the 2.2 build for it to work? >> >> Secondly, why is the jee-container-ssl.xml missing on the 2.2 build. The >> existing jee-container.xml that comes with the build not not seem work when >> you try to access the page via https. I had to copy it >> jee-container-ssl.xml from the 2.1 build and rename to jee-container.xml in >> order to access the page via https successfully. >> >> Thank again Maxim for your guidance. >> >> -john- >> >> >> >> On Wed, Sep 11, 2013 at 10:00 AM, Maxim Solodovnik >> wrote: >> you need to create it as you have created "keystore" file (as stated here: >> http://openmeetings.apache.org/RTMPSAndHTTPS.html) >> >> >> On Wed, Sep 11, 2013 at 11:58 PM, John Tran wrote: >> Where would I get that? keystore.screen is no where to be found when I do a >> search. I just finish a build from scratch from an svn checkout >> installation. >> >> >> On Wed, Sep 11, 2013 at 9:54 AM, Maxim Solodovnik >> wrote: >> keystore.screen is necessary for screensharing via RTMPS >> >> >> On Wed, Sep 11, 2013 at 11:09 PM, John Tran wrote: >> Thanks Maxim. My setting are identical int he config.xml except that values >> are different. >> >> As for the red5-core.xml setting. I did't comment out the below >> >> >> - >> >> + >> >> I left as is like I did in all of my 2.1 set up configuration. I will >> comment out on the 2.2 build and see if it works. >> >> As for the ../conf directory, I don't have a keystore.screen file. I just >> have keystore file that I created and keystore.jmx file that is already >> there. >> >> >> >> -- >> WBR >> Maxim aka solomax >>
Re: addRoomWithModeration SOAP issue
Hi Sam,
I'd try to pass values for those parms instead of NULL. Just assuming that
there might be issues if the API wants a boolean but gets NULL.
Did you check the logs for any errors?
Daniela
On 2013-10-21, at 9:56 PM, Sam Hagen wrote:
> Howdy,
>
> I'm attempting to add a group with the OpenMeetings SOAP API. I saw on the
> documentation
> (http://code.google.com/p/openmeetings/wiki/SoapMethods#addRoom) that addRoom
> is obsolete and that it's best to use addRoomWithModeration.
>
> However upon attempting to use it, I was met with an empty request and
> response from the API.
>
> Below is my code:
> $params = array('SID'=>$sid, 'name'=>$_POST['project_name'],
> 'roomtypes_id'=>1, 'comment'=>NULL, 'numberOfPartizipants'=>5,
> 'ispublic'=>NULL, 'appointment'=>NULL, 'isDemoRoom'=>NULL, 'demoTime'=>NULL,
> 'isModeratedRoom'=>NULL);
> var_dump($params);
> $room=$SOAP->addRoomWithModeration($params);
>
> print "\n";
>
> print "\n Request:
> ".htmlspecialchars($SOAP->__getLastRequest());
>
> print "\n Response:
> ".htmlspecialchars($SOAP->__getLastResponse());
>
> print "";
>
> die();
>
> And here is what I get out of it:
>
> array(10) {
> ["SID"]=>
> string(32) "45f406ce94c5ad362d4a793e03faedd5"
> ["name"]=>
> string(10) "Project Name"
> ["roomtypes_id"]=>
> int(1)
> ["comment"]=>
> NULL
> ["numberOfPartizipants"]=>
> int(5)
> ["ispublic"]=>
> NULL
> ["appointment"]=>
> NULL
> ["isDemoRoom"]=>
> NULL
> ["demoTime"]=>
> NULL
> ["isModeratedRoom"]=>
> NULL
> }
>
> Request:
>
> Response:
> As you can see, I'm properly logging in and getting a session ID, I just
> can't even get so much as an error message out of addRoomWithModeration.
>
> Any ideas would be (as always) greatly appreciated.
>
> Best,
>
> Sam
Re: RTMPS / HTTPS support in 2.0
We have tried it a lot too. And it did work on a Mac client. However it wasn't stable, so we also dropped it for now and will try again with 3.0. On Mon, Feb 24, 2014 at 7:19 AM, Artur Neumann [ICT Projects, INF/N] < ict.proje...@nepal.inf.org> wrote: > I've tried RTMPS with 2.1 and 2.2 in Oct 2013 with no luck. Maxim helped > a lot to investigate that problem. But we could not fix it so I, had to > drop the project of running OpenMeetings in our organization for now as > we required a secure connection. > > I will try again with 3.0 when I find time as we still need a solution. > > Artur Neumann, INF/N IT Projects > International Nepal Fellowship > Web: http://www.inf.org > Skype: artur.n. > > Am 24.02.2014 08:46, schrieb Sanjay Rao: > > Couldn't find a definitive answer to - is rtmps and/or https supported > > in 2.0 on a Mac client? There are too many conflicting answers to > > this. Appreciate if somebody can answer this question. I have followed > > published instructions and also done enough research on configuration > > but still can't get it to work. > > > > Thanks > > Sanjay > > > >
