The filter can act as a RTSP server that re-streams the streams received.
Example:
- the PC that will act as a RTSP "re-streamer", on which the application having RTSP filter instances running, has the IP 192.168.1.100
- the URL of the IP camera to re-stream is:
rtsp://192.168.1.25/axis-media/media.amp?videocodec=h264
- we want to re-stream this URL so the RTSP "clients" can connect to this PC to on the port 10000 with the URL path "live1":
rtsp://192.168.1.100:10000/live1
This can be activated:
- either as parameter at the end of the RTSP URL by adding:
>desturl=rtspsrv://192.168.1.100:10000/live1
rtsp://192.168.1.25/axis-media/media.amp?videocodec=h264>desturl=rtspsrv://192.168.1.100:10000/live1
- either programmatically by invoking:
DatasteadRTSPSourceConfig.SetStr ("RTSP_Dest_URL_str", "rtspsrv://192.168.1.100:10000/live1")
From the same application it is possible that several RTSP filter instances re-stream several IP cameras on different RTSP ports, e.g.:
rtsp://192.168.1.25/axis-media/media.amp?videocodec=h264>desturl=rtspsrv://192.168.1.100:10000/live1
rtsp://192.168.1.26/axis-media/media.amp?videocodec=h264>desturl=rtspsrv://192.168.1.100:10000/live2
rtsp://192.168.1.27/axis-media/media.amp?videocodec=h264>desturl=rtspsrv://192.168.1.100:12345/live1
rtsp://192.168.1.28/axis-media/media.amp?videocodec=h264>desturl=rtspsrv://192.168.1.100:12345/live2
The only constraint is that 2 applications (2 different executables) must not re-stream on the same RTSP port, otherwise the second executable may crash.