Immix

this guide will help you set up the integration between irisity iris+ ™ cm and immix to enable sending alarms generated in the irisity system to immix once completed you should be able to correlate alarms in the irisity system with the right device in immix as a prerequisite, you should have installed at least one camera and set it up in both systems integration workflow overview to set up the integration, follow the below steps each step is detailed in its own section further down in this document prepare your immix environment define an integration target in iris+ define integration actions in iris+ set the immix external id for iris+ folders set the immix external id for iris+ cameras test the integration prepare your immix environment for integration to monitor iris+ folders and the detected events or health events created by these folders, you will need to create a corresponding site in immix additionally, an iris+ device must specify the origin point of iris+ events immix setup dashboard prepare your immix environment port setup port 465 or 587 should be open in the immix firewall the irisity hosted solution is run in the google cloud platform, these are the only ports supported by google keep these ports open for iris+ incoming events in immix setup , select add a site and fill in the relevant details perform this step for each of the irisity sites you would like to monitor you can also edit an already existing site 3\ select the site and click manage devices and alarms in the right column 4\ click add device in the bottom right corner of the list 5 add a device for iris+ device type video devices => innovi ip/host 34 90 111 200 (this is the ip address of the iris+™ hosted service) leave the rest of the fields empty 6 for each of the sites you have created, locate and document the relevant unique system number (s number) at the end of the site setup process, select view summary the setup report appears write down and keep the identifier (s number) in this example, the identifier to keep is 599 define integration target in iris+ integration targets in iris+ are used to define outgoing endpoints, where to send alarms and health alerts to immix exists as a custom build and supported integration, making setup very easy define the immix integration target in iris+ log in to iris+ from the top menu bar, select settings select integration targets click the add button the integration target screen appears 5\ name the integration and enter the details relevant for your immix installation typically, user name and password are not required since immix accepts alarms without authentication based on ip whitelisting 6\ click save the integration target is defined and is listed in the integration targets list define integration actions in iris+ integration actions are account level or folder specific actions in iris+ these actions define what type of events are sent to the integrated system whether it is detected events showing the video clip of a breached rule or health events alerting to health issues for camera or edge devices define an integration action please note that it is possible to set up multiple integration actions with different configurations this means that you can choose to send some alarm types from some folders and other alarm types from others configure integration actions select the administrator tab in the tree in the left sidebar, either select the top node (the account ) to send everything from the system to immix select a folder or subfolder only alarms from cameras and devices in this folder will be sent to immix from the menu bar, select integrations and click the add button a new integration action line entry appears enter the details name enter a meaningful name such as the type of events being monitored leave mode to automatic type select whether to send detection events (video alarms) or health alerts (system monitoring issues) target select the integration target you created and named above, for example "immix" optionally use the right section to filter what object types, behavior types and severities you want to send to immix by default, no filtering is applied and everything is sent click save set s number for iris+ folders the iris+ folders you intend to monitor should have the external id field set these folders have corresponding sites in immix and the external id is the s number you documented for each site to set the folder external id select the administrator tab select the right folder in the left sidebar click the edit button in the external id field, enter the s number you documented in immix for the corresponding site in our example – it is 599 click save set alarm number for iris+ cameras each iris+ camera may be defined with its own external id, alarm number in immix this may be required for the event created from this camera to be associated with the correct camera in immix to set the camera external id select the administrator module in the hierarchy tree, select select the relevant camera click edit in the external id field, enter the relevant immix alarm number, above "12345" this would make the full immix id s599 a12345 click save test the integration an integration test is a way to ensure that events for monitored folders are being received by the integrated system when creating a test rule or test events, make sure you choose cameras under the monitored folder each analytics rule can be tested to test the integration set up one or more video analytics rules in administration => rules for a single camera click the send a test alarm and verify alarms are showing up in immix trigger an actual event from the camera and the rule in question and make sure the event shows up in iris+ under the monitor tab technicalmake sure the alarm shows up in immix technical reference appendix event format in immix the following sections list the iris+ event status and the corresponding status that appears in immix for both detected events and health events detection events format iris+ status immix status innovi unknowns objectdetected innovi unknowns unknown objectdetected innovi unknowns vegetation objectdetected innovi unknowns cloud objectdetected innovi unknowns object objectdetected innovi people persondetected innovi people person standing persondetected innovi people person on the ground persondetected innovi people person overhead persondetected innovi vehicle vehicledetected innovi vehicle car vehicledetected innovi vehicle car compact vehicledetected innovi vehicle car suv vehicledetected innovi vehicle bus vehicledetected innovi vehicle school bus vehicledetected innovi vehicle mini bus vehicledetected innovi vehicle city bus vehicledetected innovi vehicle pickup truck vehicledetected innovi vehicle van vehicledetected innovi vehicle truck vehicledetected innovi vehicle truck small vehicledetected innovi vehicle truck medium vehicledetected innovi vehicle truck semitrailer vehicledetected innovi vehicle tractor vehicledetected innovi vehicle night vehicledetected health event format cameras "tamperalarm" in blocked/saturated/dark "videoloss" in all other health events "frame rate is too low (iris+ camera id nnnnnn)" "frame rate is too high (iris+ camera id nnnnnn)" "scene is blocked (iris+ camera id nnnnnn)" "scene is saturated (iris+ camera id nnnnnn)" "scene is too dark (iris+ camera id nnnnnn)" "communication failed (iris+ camera id nnnnnn)" "general error (iris+ camera id nnnnnn)" "rtsp error (iris+ camera id nnnnnn)" "incompatible video (iris+ camera id nnnnnn)" "resolution error (iris+ camera id nnnnnn)" edge devices "systemevent" "high latency (iris+ edge id nnnnnn)" "overloaded (iris+ edge id nnnnnn)" "no comm with cloud (iris+ edge id nnnnnn)" iris+ (edge software handling multiple cameras) "systemevent" "no comm with cloud (iris+ agent id nnnnnn)" "high latency (iris+ agent id nnnnnn)"