Simon Ball · Sep 17, 2014 at 03:58 PM ·
Automatically stop and start incoming streams
Hi, I can't find out if this is possible, I may just not have understood other threads I have read.
I am going to be running a live stream using a 3G connection so I want to keep bandwidth as low as possible. I will have a permanent live stream that users can log in and view when they need but there will be times when there will be no users connecting to the stream i.e. during the night.
What I would like is after a certain amount of idle time for wowza to stop connecting to the cameras so that they do not upload but will automatically start up again as quickly as possible if someone does log in. Any ideas on this or a link to another article would be very much appreciated.
On a slightly unrelated note, In the monitoring sections of wowza engine all of my graphs for network and connections are blank, any ideas on a fix for that?
If you find that you need additional assistance with this implementation, you can post a request to the
find a consultant forum
For the graph issue - please check logs for any errors regarding the db files, also check permissions on the stats folder. If nothing checks out there, please zip up your /conf and /log folders and send them to
firstname.lastname@example.org to open a ticket.
Yes, you can use a StreamType of
rtp-live-record (MediaCaster). Using this StreamType streams are started and stopped on demand based on client's viewing the stream. The publishing process is started the first time a client attempts to view a stream and stops 60 seconds after the last client has stopped viewing the stream.
This will work for RTSP as well as RTMP clients, but for HTTP clients there is no practical or built-in way to do this, because Wowza needs some lead time to start packetizing for HTTP clients.