Thanks,
After the activation i will need to take it offline again (into the closed plasma-screen network). The license will still work, right? I can take the server once in a while online, but most of the time it will be offline.
ok, thanks, i got it
Hi Richard,
I have another question on the matter of this setup. The encoder sends stream to wowza on 2/2 mbps dedicated connection, at 650 kbps. When i try to pull the stream back to the encoder, for rtmp playback on a simple flex client, i sometimes get up to 30 sec. delay until i start getting the stream. After wowza restart, i’m getting the stream without an issue, 1-2 sec. delay tops. No other client is connected, besides the flex client on the encoder, and no other traffic was seen on the line, besides push to server -> pull from server.
What in your mind could be the reason for the delay?
Thanks,
Alex.
Hi,
Yes, this is the exact setup, only that one of the flash clients sits on the encoder itself. In the logs i see that sometimes the “connect” and “play” are simultaneous, ands sometimes there is a gap of 20 seconds between them.
Also, another question - in the final stage of the project there would be ~ 600 stations (rtsp or rtmp clients) that would need to connect to the stream simultaneously. I.e. they would receive a multicast command “play stream”, and by that command they would start playing the stream. What would be the best tuning for such an operation, to aquire the best performance, so that the stream would start simultaniously in all the places? There would be 4 hardware servers, and i will configure origin and edge servers, of course, but besides that?
Thanks a lot,
Alex
Hi Richard,
Of course i’m not expecting it to be “atomoc clock” accurate, and the command to connect to stream will be sent by another application, not through wowza. My question is - can i realistically expect that if a few hundreds rtsp clients will try to connect to the same server in the time interval of 3-4 seconds, they will all get the stream in 3-4 seconds, assuming that the hardware and the broadband is adequate?
Also, can you specify about the NetConnection? Maybe link to a guide?
Thanks for all your help,
Alex
Hi,
This is what we try to accomplish:
There is a live event that happens every 2 hours from 10 am to 10 pm, 5 days a week. We need to transmit this event to clients (big plasma tv-s) that will be posted in shopping malls all over the country. Right now there are only four, because we operate in pilot mode, but the plan is to have hundreds in a matter of 3-4 months. Each tv is connected to a computer, that runs an rtsp player, really similar to VLC player (rtmp client is being developed right now). The stream is started in the main filming studio, by way of an application that uses profiles of FME to connect to wowza, and start encoding. After a forced delay of 10 seconds the clients receive from the application a UDP command “start playing”, and then connect to the stream. Again, right now there are 4 independent udp packets that are being sent individually to each client, but the plan is to send a multicast command eventually. Each client has a VPN connection to the LAN containing the server, 2/2 mbits.
There is no multi-user functionality involved, the whole procedure is automatic after the initial configuration.
The question is - is it possible for many rtsp clients to connect to the server and start receiving streams immediately (of course, not “atomic clock” immediately, lets say that by 10-15 seconds from the moment of sending the udp command all the clients will try to connect to the server and start receiving the stream)? Can it be done for rtmp clients?
Thanks,
Alex
Richard,
Given that the RAM and the CPU will be adequate (we plan to purchase new and powerful servers), can wowza handle multiple simultaneous connections? What is the overhead for each connection? Also, for such a setup is it preferable to use rtsp or rtmp clients in your opinion?
Thanks a lot for all your time and answers.
Alex
Hi,
Also, i have a question about sudden disconnects of the client (i thought about posting here, instread of opening an alternative thread). This is what i see in the log (after the encoder has started the stream on wowza:
2011-01-11 11:29:13 GMT+02:00 connect rtsp
2011-01-11 11:29:13 GMT+02:00 create stream
2011-01-11 11:29:13 GMT+02:00 describe rtsp
2011-01-11 11:29:13 GMT+02:00 play stream
2011-01-11 11:29:13 GMT+02:00 play rtsp
…
2011-01-11 11:29:26 GMT+02:00 comment server WARN 200 - RTPStream.idle[845749252:paislive/definst:pais1]: Close RTSP/RTP session. Session timeout: 90000 - - - 418842.015 - - - - - - - - - - - - - - - - - - - - - - - - -
2011-01-11 11:29:26 GMT+02:00 stop stream INFO 200 pais1 - defaultVHost paislive definst 120.359 192.168.212.100 554 rtsp://192.168.212.18:1935/paislive/pais1 192.168.212.100 rtsp - - 845749252 2892454 0 8 10361 0 2892454 pais1 - - - - - rtsp://192.168.212.18:1935/paislive/pais1 rtsp://192.168.212.18:1935/paislive/pais1 - rtsp://192.168.212.18:1935/paislive/pais1 -
2011-01-11 11:29:26 GMT+02:00 destroy stream INFO 200 pais1 - defaultVHost paislive definst 120.359 192.168.212.100 554 rtsp://192.168.212.18:1935/paislive/pais1 192.168.212.100 rtsp - - 845749252 2892454 0 8 - 0 2892454 pais1 - - - - - rtsp://192.168.212.18:1935/paislive/pais1 rtsp://192.168.212.18:1935/paislive/pais1 - rtsp://192.168.212.18:1935/paislive/pais1 -
2011-01-11 11:29:26 GMT+02:00 disconnect rtsp INFO 200 845749252 - defaultVHost paislive definst 418842.015 192.168.212.100 554 rtsp://192.168.212.18:1935/paislive/pais1 192.168.212.100 rtsp - - 845749252 0 0 - - - - - - - - - - rtsp://192.168.212.18:1935/paislive/pais1 rtsp://192.168.212.18:1935/paislive/pais1 - rtsp://192.168.212.18:1935/paislive/pais1 -
before the “stop-destroy-disconnect” there is WARN 200 - RTPStream.idle[845749252:paislive/definst:pais1]: Close RTSP/RTP session. Session timeout: 90000
The client side apparently connects, and starts playing, although no picture is shown. Then there is WARN message, and timeout. What could possibly be a reason for such a timeout? The client does not stop playing, and does not disconnect.
Alex
Ok, thanks, we will try this. What is the condition under which the server writes a timeout log, and destroys the stream to the player? Can the server disconnect a “living” stream, and stop sending packets to the player without the player making any sort of “stop” action by its own?
Thanks, but i meant something else, i wanted to ask, is it possible, that the server “decides” under certain conditions to drop a playing connection on its own? if i (rtsp client) play a stream from wowza, and suddenly i get disconnected, and in the server logs show:
WARN 200 - RTPStream.idle[845749252aislive/_definst_ais1]: Close RTSP/RTP session. Session timeout: 90000
and then “stop-destroy-disconnect”, what could be the reason for such an error?
Alex