Download

system in monitoring multiple cameras, so you’ll actually have multiple configuration filesper camera.[ tail end of a default motion.conf file]Asterisk Hardware Ninjutsu • Chapter 11 349############################################################### Thread config files - one for each camera.# However, if there's only one camera, you only need this config file.# If you have more than one camera, you MUST define one thread# config file for each camera in addition to this config file.############################################################### Remember: If you have more than one camera, you must have one# thread file for each camera. Thus, two cameras require three files:# This motion.conf file AND thread1.conf and thread2.conf.# Only put the options that are unique to each camera in the# thread config files.; thread /usr/local/etc/thread1.conf; thread /usr/local/etc/thread2.conf; thread /usr/local/etc/thread3.conf; thread /usr/local/etc/thread4.confThe option we’ll be focusing on is a pre-thread configuration file, so once you have aworking configuration:# Command to be executed when a motion frame is detected (default: none); on_motion_detected valueThe idea is that when motion is detected, we can have Motion (the program) run a routine.When I leave town for an extended period of time, I want to know if motion isdetected within my home. I’m not as concerned about outside because false positives woulddrive me crazy. For example, cats or dogs that just happen to roam through my yard, I’m notinterested in.If an event happens inside the home and I know nobody is there, then I certainly wantto know! So, with the cameras that are internal, we’ll use the on_motion_detect option to runa routine that’ll call my cell phone and alert me to something or someone in my house. Wecan do this on a per-thread configuration file basis. So, for cameras that are outside, we won’tadd the on_motion_detect option.