Sebastian, >From my experience: it happens more often when SIP user is in the room, but also we observed similar behavior without him too.
We can help you if you would like to try it. Just let me know and let's discuss convenient time for this. SIP integration is currently configured on our demo server (demo.dataved.ru) so that you can call to the room from some software phone (we deal with linphone). Regards, Irina. -----Original Message----- From: [email protected] [mailto:[email protected]] Sent: Wednesday, February 13, 2013 12:31 PM To: Maxim Solodovnik Cc: dev Subject: Re: Issue with OM per user streams Is this a problem that only happens with SIP integration or also standalone? I will have to test that first. It sounds a bit weird, but I can't test it as I don have 5-7 pc's. And using a single pc makes no sense when testing audio/video. We have two rtmp connection per stream, but that would still not explain your issues with the id. Which Id are your refering to exactly? broadCastId or streamId ? broadcastId would be the name of the stream under which the user publishs (aka NetStream) streamId is the rtmp connection (aka NetConnection), you connect to: rtmp://blabla:1935/openmeetings/ And each client will publish his webcam+micro in one stream, with the name of the "broadCastId". The StreamId can stay the same, for example if you re-publish your settings, the NetConnection will always stay, but each time your webcam is published a new "broadCastId" is requested from the server. (See ScopeApplicationAdapter::getBroadCastId()). It is better to use a fresh broadCastId each time you make a new NetStream. "setSipTransport" and "streamPublishStart" are new only methods that invoke "newStream" as event in the client. Sebastian 2013/2/13 Maxim Solodovnik <[email protected]> > Hello Sebastian, > > sorry for double post, but I would like to gain your attention at the > following problem: > > > if there is lot of users lots of users in the room (5-7) some of them > can't hear some others until "reload" of streams on the client. > Timur told me that according to the log of red5sip there is weird queue of > method calls: newStream gets called twice. Additionally if user has stream > with id 24 and select "reload" the following methods are gets called: > closeStream(25) // NOTE 25 not 24 > then > newStream(25) > > Maybe you can say what is wrong? > > -- > WBR > Maxim aka solomax > -- Sebastian Wagner https://twitter.com/#!/dead_lock http://www.webbase-design.de http://www.wagner-sebastian.com [email protected]
