Geutebruck Camera Compatibility
Danel Potvin
We offer a range of server and computer models that can be configured to suit your system requirements, fully in line with your needs. You can opt for stationary or mobile devices. Our special hardware components allow you to build in fail-safe technology to the exact level you require, helping to reduce downtime. Our hardware is tailored for optimum compatibility with our software products to provide a fully comprehensive service.
Want more? No problem! You can opt to extend the warranty for your security camera system to four or five years and offer full CCTV camera maintenance. Why do we do this? The answer is simple: Because we want to give you an extra level of security and enable you to plan more effectively.
If you wish to view the full ZM Documentation, I recommend viewing it through the PDF view, as the sphinx website is not efficient and requires javascript. PDF View: you want a hard copy, you can order the documentation through a self publishing service like lulu.com
On the learning curve: It can be some work (depending on how complex your system is), but you will become a proficient gnulinux sysadmin if you familiarize yourself with ZM and its many features. If you buy an off the shelf DVR you won't learn nearly as much (if anything). Additionally, these skills are valuable for 'any' Unix-based server (DB, website, email server, kiosk, etc).
I recommend you start with an early Axis. They are well documented and easy to setup. Old ones go for $10-20. Follow the instructions on either the Zoneminder Hardware compatibility list,on ispyconnect's url list, or in the user manual for the camera. Any respectable camera will document it's RTSP and MJPEG / JPG paths for you to access. ONVIF is also an option to find the path for RTSP cameras. This is covered in more detail in Finding Camera Stream Paths.
Follow the instructions in the Hardware Compatibility List for parametersfor setting up a camera the first time. If you have an error, look at the logs. FFMPEG and VLC can be used to test that the streams are valid. e.g. from terminal: ffmpeg -i rtsp://username:password@:554/path output.mp4 This is faster than using ZM.
If the camera requires authorization, consult the user manual, or you can try adding the username and password before the ip like so username:password@ipaddress This is an alternative to 192.168.1.5?username=root&pwd=mypass which most guides tell you to do. Both will work, however the former is easier.
2010's and newer cameras: These cameras use h264 (or h265) compression. They serve it on an RTSP server. h264 means less bytes, so you end up using less HDD space than compared with MJPEG. H264 is recommended when possible.
High-end server hardware will perform better than desktop, or low end server hardware. I have seen this firsthand between two servers: KFSN4-DRE and the KGPE-D16. The latter runs ZM with 25+ cameras, not breaking a sweat. The former reaches a limit at about 10. Another limitation is HDD size.
I currently recommend buying Axis (new is expensive, so you'll probably purchase used), although many do not have IR. This is not a problem, as outdoors IR on cameras attracts spider webs, and external IR is recommended. Another recommended brand is Hikvision. Hikvision can be bought new for a lower price if warranty is an issue (for business clients that can't afford Axis). The cameras work well with ZM, and are configurable without Windows, Otherwise, any respectable name brand camera will work. Look through the hardware compatibility list. Read the user manual before you purchase the camera, and look for the following: Outdoors/indoors, IR/no-IR, Resolution. IR can be supplemented with external appliances. You can also put pesticide on the cameras to deter bugs... (although I wouldn't).
There is an option to use a coax to ethernet adapter. You need two pieces. One is the sender, one is the receiver. They may or may not be identical. These allow the use of IP Cameras over coax. Search ebay. Altronix ebridge ones are about $120 for a pair or adapters (you need a pair for each camera). If this is too much money, you may keep the old coax cameras. See: IP Video Encoders [1]. Honestly, just run ethernet if you have a chance. Customers expect HD these days.
You can make fully customizable pages i.e. make an html file on a remote machine with the following code embedded in an img tag. Adjust monitor ID as needed.How to stream from another ZoneMinder installation. Also an easy way to embed video in a website (img tag). See Dedicated SBC Camera Monitor for an example of a computer that only displays the streams. [[2]] has the HTML code for API/non-API usage.
One note: If you have alternative high/low resolution cameras (motion detect on the low res, record on the high res). You might not want customers to view the low res cameras. In this case, make a group of the high res cameras, and set that to be the default view.
By doing this you will get a low res live view and analysis, but the recorded videos will be full res when watched. This is the easiest way to setup ZM. You can also use linked monitors or have multiple streams, but neither of those options are worth the trouble. Note that there may be a warning in ZM about the stream not matching the resolution but that can be ignored (it is a warning, not an error). This has been discussed on the forums, search there for further details.
The challenge of all surveillance systems lies in its motion detection analysis (thus the 'zone' in zoneminder, being the motion detection zones). See: Understanding Zoneminder's Zoning system for Dummies. Zones have their gotchas, and you may want to consider ZMES. Like AI, expect 90% but do not ever expect 100%. You will need hardware motion sensors for 100%.
Start out with Best, High Sensitivity. Change to pixels instead of percent, and start around 500 (or even 200 depending on whether you are around 640x480 or 320x240). This is a good start, but it may still require ZMES. For bounding boxes, you should try to use rectangles or squares. I believe someone in the forum mentioned this will save on calculation of the CPU, but regardless, it just looks better. Use the boxes in the bottom to line up X and Y appropriately. See image.
The convergence of software solutions brings benefits in all areas of an organization, including physical security. Video surveillance makes a valuable contribution to the protection of people and assets, especially when the video management software (VMS) is integrated with other security systems. Third party software manufacturers can interact seamlessly with a VMS via interfaces and develop individual solutions.
Interfaces serve as a bridge between different systems and enable smooth communication and data exchange. The integration of VMS with other systems and devices such as cameras, access control, intrusion detection technology and analysis tools offers many advantages.
Operators receive immediate and standardized situational awareness in the event of an incident to react in a targeted manner. Automated system responses reduce operator workload and increase efficiency. The standardized documentation of all system processes simplifies forensic analyses and strengthens compliance and data protection.
Interfaces are the basis for complete solutions that are tailored to the individual requirements and preferences of the user. They increase investment security, as existing infrastructure can be enhanced with new technologies without having to rebuild the security architecture.
Interfaces promote innovation by enabling the development of new applications based on the VMS. Integration with analytics tools in particular, but also with ERP or warehouse management systems, opens up the potential to provide users with valuable additional benefits in their value chains.
SDKs contain a collection of tools, libraries and documentation for the development of an interface. They allow deep integration and full control over functionality and performance. However, updates and upgrades of the interconnected systems may require adjustments in the developed interface.
This is why many VMS providers offer integration modules that form a stable intermediate layer between their own and third-party software, such as G-Connect from Geutebrck. Video management and third-party software can evolve while compatibility is maintained.
Web APIs, standardized methods for data exchange via IP networks based on web browser technologies, are relatively new. They enable cross-platform integration and the development of applications that can access a VMS remotely.
The options described enable technology partners to jointly offer innovative solutions and meet the changing requirements of users. Integrations combine a high level of specialization in various areas to create software solutions that maximize customer benefit. Synergies through customized interfaces with video management software drive customer value and are the basis for growth and success of our industry.
If an Argus security robot or the perimeter detection system from Security Robotics detects an unauthorized person, the VMS in the control center displays the alarm message, site plan overview and all relevant video cameras in a unified interface. If required, security staff can also activate drones at the click of a mouse for a better on-site overview. The images from all cameras, whether permanently installed, robot eyes or drone cameras, are stored in the G-Core VMS for forensic analysis after an incident.
The solution is based on the Geutebrck WebAPI and the ACUDA integration platform. Robots, cameras, sensors and IoT devices from Security Robotics are seamlessly networked with each other, and other third-party systems can be easily integrated. There are also potential applications in existing security systems. The simple integration of autonomous robotics and the ACUDA platform with Geutebrck video management solutions ensures high-performance real-time surveillance with increased efficiency and minimized personnel deployment.
c80f0f1006