If you're using Wowza Streaming Engine for live streaming you will be publishing the live stream to the server which will use bandwidth. If you're using a .stream file or other MediaCaster stream then you can start/stop this stream in Wowza Streaming Engine Manager as shown in the
IP camera re-streaming tutorial
If you're only using IP camera sources for this application and only providing these streams to RTMP or RTSP based playback clients then you can edit the [Wowza-Install]/conf/AppName/Application.xml file and change the StreamType to "rtp-live" which will tell Wowza Streaming Engine to start the stream when the playback client connects. Note that HTTP based streaming protocols (Adobe HDS, Apple HLS, Microsoft SS and MPEG-DASH) require packetization and this means the stream needs to be constantly running. The auto-startup nature of using StreamType "rtp-live" makes this unsuitable so is limited to RTMP and RTSP playback.
When using an
origin/edge configuration, clients will connect to the edge to playback the live streams. If an edge server doesn't have any clients connected it will not stop pulling the source from the origin to save bandwidth between the origin and edge. When the first playback client connects, the edge will then start pulling the required source.
After making the changes to your application's configuration file, as Jason suggested, you should make sure that the IP camera stream is not published on your Wowza application if there are no playback clients. If the stream is not published, this particular stream name should not appear in the incoming streams list.
When a playback client requests the .stream file configured with the RTSP address of your IP camera, then Wowza will initiate the connection to that particular camera. When the last playback client disconnects, the incoming stream should be removed from the incoming stream list.
Can you perform this test and let us know the results?