Monitoring JPEG Images From IP Cameras?

Hi, I’m looking to find the simplest method of transmitting still JPEG images (triggered by motion detection) from an existing IP camera network to an external FTP server without having to disturb the IT department too much. The issue I’m facing is if the existing camera is connected to the internal IT network, I first need to get the IT Department to approve transmitting images via FTP/SFTP from their internal network and add exceptions for the appropriate ports in the firewall, then discuss bandwidth and data requirements and usually wait weeks or months for them to implement.

For standalone networks where the IP camera network is separate, I’ve had success installing cellular modem/routers which take care of the image transmission process and bandwidth/data issues. This method is generally accepted by clients/IT departments. This also allows external access to the camera(s) to adjust/refine motion detection settings. Ideally, I would like to use this same method for cameras connected to a client’s existing IT network, but split the camera across both, allowing for the client to still retain recording of video on the local NVR, but have JPEG images transmitted out from the camera(s) via the cellular modem/router. I would see this involving either a dual WAN router, or possibly a managed switch or a combination. What are your thoughts?

Login to read this IPVM discussion.
Why do I need to log in?
IPVM conducts unique testing and research funded by member's payments enabling us to offer the most independent, accurate and in-depth information.

*** ********** ******** ***** *** ** ****** ******* ** ********, I’ve *** ******* ********** ******** *****/*******... *******, * ***** **** to *** **** **** ****** *** ******* ********* ** * client’s ******** ** *******, *** ***** *** ****** ****** ****...

**, ********** ***** *************** **** *** ** ** **** **** ***** * **** WAN ******** ******. ;)

**** ******* ** ******, *** *** *** ******* **** ***** ok **** ********** **************, *** *** ** *** ***** ** would ** ******* ***** ******** *** *** ******** *** ******** ramifications ** *** ******* ********** ******* ******* **** ******* ** outbound *** ****? ****** *** ***'* ******* **, *** **** we're ***** ***** *****....