Immix

overview iris+™ is irisity's ai powered, open architecture video analytics solution for security, safety, and business intelligence applications iris+ eliminates the need for continuous monitoring of surveillance cameras and helps customers uncover otherwise hidden events, insights, and information it automatically alerts you to security and safety incidents in real time, drawing your attention to an incident of interest and enabling effective responses, as events unfold the integration aims to receive and view iris+™ detected events or health events in the integrated system this guide serves as a reference point for the successful integration of iris+™ with immix the integration process requires steps to be performed in both the immix system environment and in the iris+™ portal iris+™ immix integration workflow we are ready to start integrating your iris+™ account into your existing immix deployment the following serves as a high level workflow explaining the main steps to set up 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 define integration target in iris+™ the integration targets in iris+™ are the system wide definitions required for iris+™ to integrate with your system you will define the endpoint that can receive the events sent by iris+™ define integration actions in iris+™ integration actions are 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 cameras or devices the folders to be selected are those that hold the cameras and devices that you intend to monitor identify iris+™ folders the iris+™ folders that you intend to monitor must be defined by a unique id these folders have corresponding sites in immix and the unique id is the s' number you documented for each of the sites identify iris+™ camera the iris+™ cameras that you intend to monitor can be defined by a unique id this may be required for the event created from this camera to be associated with the correct camera in immix 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 to learn more about event naming format, refer to event format in the immix chapter prepare your immix environment for integration before you start 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 to prepare your immix environment for integration with iris+™, do the following port setup port 465 or 587 should be open in the immix firewall as the irisity hosted solution is based on google cloud, 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 iris+™ sites you would like to monitor you can also edit an already existing site add a device for iris+™ with the following details enter a meaningful service account name such as “customer 1” enter a description (optional) device type iris+™ ip/host 34 90 111 200 (this is the ip address of the iris+™ hosted service) port leave empty 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+™ before you start the integration targets in iris+™ are the system wide definitions required for iris+™ to integrate with your system you will define the endpoint that can receive the events sent by iris+™ to define the integration target in iris+™, do the following log in to your iris+™ account from the top module bar, select settings select integration targets click the add button the integration target screen appears define the following target name define a meaningful name such as immix ensure the toggle switch is enabled type select immix host/port enter the host ip in the first field and the port number in the second field credentials these are not required as the alarms to immix use noauth (immix accepts these based on the ip whitelist and trusted domains @immixalarms com) click save the integration target is defined and is listed in the integration targets list define integration actions in iris+™ before you start integration actions are 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 the folders to be selected are those that hold the cameras and edge devices that you intend to monitor to define the integration action in iris+™, do the following select the administrator module in the hierarchy tree, select the relevant folder, which holds the cameras you are monitoring (remember you prepared a corresponding site in immix for this folder) from the menu bar, select integrations and click the add button a new integration action line entry appears expand the new integration action by clicking the arrow and define the following action name enter a meaningful name such as the type of events being monitored ensure the toggle switch is enabled type select whether to integrate a detection event or a health event target select the relevant integration target that you previously created click save identify iris+™ folders before you start the iris+™ folders that you intend to monitor must be defined by a unique id these folders have corresponding sites in immix and the unique id is the s' number you documented for each of the sites to identify the iris+™ folders, do the following open the windows date and time panel and select internet time click the change settings button from the menu bar, select settings 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 identify iris+™ cameras before you start each iris+™ camera may be defined by a unique id this may be required for the event created from this camera to be associated with the correct camera in immix to identify the iris+™ cameras, do the following select the administrator module in the hierarchy tree, select the folder you are planning to monitor select the relevant camera click edit in the external id field, enter the relevant immix camera unique id click save test the integration before you start 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 to test the integration for detected events, do the following as per the iris+™ training instructions, define a test rule for a camera in each of the monitored folders ensure that events are created in iris+™ under the monitor module open your integrated environment and ensure that the same events have also been received 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 status is "tamperalarm" in blocked/saturated/dark, or "videoloss" in all other health events the description is one of "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 status is "systemevent" the description is one of "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) status is "systemevent" the description is one of "no comm with cloud (iris+™ agent id nnnnnn)" "high latency (iris+™ agent id nnnnnn)" contact irisity support customer support technicalsupport\@irisity com mailto\ technicalsupport\@irisity com