Dealing with IP Cam Live streams
Posted: Wed Dec 07, 2022 12:55 pm
This is a weird requirement I'm trying to achieve with ZM, but here we go
I have a public streaming based on IP Cam Live
https://www.ipcamlive.com/62a77f39855df
I'm trying to pick the m3u8 stream and monitor and record it on my server.
But obviously, they are using an auth code that changes occasionally to avoid this. Still I need to do this for a friend.
I'm uncertain if someone may have a better idea than mine, but here it is:
1. First I create a scrapper script that scraps the page, and picks the player URL and stores it somewhere
By the time I'm writing this, the URL is:
https://www.ipcamlive.com/player/player ... DfBxJpQ%3D
As you see the player URL is the alias (which is the ID) and the token which changes occasionally
2. If the token has changed compared to the one I have stored, then the m3u8 stream will have also changed.
3. I pick the new m3u8 stream, and send a Source URL change request through ZM API.
Theoretically, every time I generate a new ZM API call ZM will pick this as a new event, stop the previous one (set the monitor on RECORD for continuous recording) and create a new one with the new source URL.
In my mind, this may work. But I was thinking if there is a better alternative. I don't have direct access to the RTSP stream of such cam.
I have a public streaming based on IP Cam Live
https://www.ipcamlive.com/62a77f39855df
I'm trying to pick the m3u8 stream and monitor and record it on my server.
But obviously, they are using an auth code that changes occasionally to avoid this. Still I need to do this for a friend.
I'm uncertain if someone may have a better idea than mine, but here it is:
1. First I create a scrapper script that scraps the page, and picks the player URL and stores it somewhere
By the time I'm writing this, the URL is:
https://www.ipcamlive.com/player/player ... DfBxJpQ%3D
As you see the player URL is the alias (which is the ID) and the token which changes occasionally
2. If the token has changed compared to the one I have stored, then the m3u8 stream will have also changed.
3. I pick the new m3u8 stream, and send a Source URL change request through ZM API.
Theoretically, every time I generate a new ZM API call ZM will pick this as a new event, stop the previous one (set the monitor on RECORD for continuous recording) and create a new one with the new source URL.
In my mind, this may work. But I was thinking if there is a better alternative. I don't have direct access to the RTSP stream of such cam.