OnGuard

overview integration of onguard with irisity's iris+™ offers a video analytics solution/service whereby events of interest are detected through real time analysis of multiple video sources and sent to onguard this guide outlines how to deploy and configure the integration of iris+™ and onguard onguard configuration verification the following onguard versions are supported onguard 7 6, 8 0, 8 1 and 8 2 the following license features are required onguard subscription software modules (swm xxx) partner integration (ipc 094 agntv01 b) verify that the following windows services are running in the onguard server ls communication server ls message broker ls open access enabling onguard integration in iris+™ portal before you start these steps assume that your iris+™ account has been set up and that folders, devices, and cameras have been configured if that is not the case, first access iris+™ tutorials from the iris+™ support hub to configure your account in iris+™, a service account is required to later link onguard to iris+™ the iris+™ service account provides a token, which is the identifier used to link the iris+™ account to onguard to generate an iris+™ service account token, perform the following browse to your iris+™ account, settings tab click the users tab click the add button, select create service account enter a meaningful service account name such as “customer 1” enter a description (optional) click create service account from the user's list, select the created service account user, click the arrow next to the edit button, and select get token define token expiration if required (by default the token never expires) click get token and copy and save the generated token (to be used in the iris+™ vms gateway configuration in the next chapter) close the window installing iris+™ vms gateway service the iris+™ vms gateway is a windows service connecting iris+™ to onguard, transferring the iris+™ generated events to onguard the service should be installed on a server connected both to onguard and to iris+™ edge device/s when installing the iris+™ vms gateway, or troubleshooting connectivity problems, it is important to understand that the gateway can be both a client and a server the gateway is a client of onguard when using edge integration, the gateway is a server to which iris+™ edge devices connect to push analytics events to the gateway when using core integration, the gateway is a client connecting to the iris+™ core service when installing the gateway and entering its configuration settings, or when opening ports in the firewall of the servers hosting the gateway and/or the vms server, it is important not to confuse the different functions and client/server incoming/outgoing call direction of the various ports and urls to install and configure the iris+™ vms gateway perform the following steps download the iris+™ vms gateway installer from this link https //bit ly/4bfjrfq https //bit ly/4bfjrfq run the installer on either the onguard server or on a separate windows server with connectivity to onguard if a previous version of the gateway is already installed, uninstall this version run the installer file as administrator two options are available for the gateway to integrate with iris+™ edge integration events are sent from iris+™ edge devices to the iris+™ vms gateway and then delivered to onguard core integration events are received by the iris+™ vms gateway from the iris+™ core and then delivered to onguard when the following window is displayed, populate the relevant fields vms settings (relevant for both edge and core integration options) vms type select onguard address ip address of the onguard server port port to communicate with onguard the default port is 8080 user username to log in to onguard password password to log in to onguard integration settings events integration type – select edge or core iris+™ url the default url ( https //api irisity io https //api irisity io ) is for an irisity cloud hosted deployment for a customer hosted deployment, replace this url with the applicable url assigned for your deployment iris+™ account token paste the token you have generated in the previous section events integration port applicable only for edge integration this is the iris+™ vms gateway port on the windows server the value is automatically populated with a default value and is editable events integration url – applicable only for edge integration the url field is read only and cannot be updated this is the ip address of the windows server on which the iris+™ vms gateway is being installed the value of the port number is automatically populated keep the ip address to be used later on when configuring an iris+™ integration target metadata integration port & metadata integration url not applicable click next to proceed with the installation until finished once the installation is complete, the service is started the gateway service will then connect to onguard to fetch cameras follow these steps to verify the gateway service successfully communicates with the vms wait one minute to allow the service to communicate with onguard open the file "c \program files (x86)\irisity ab\iris+ vms gateway\logs\vmsadapter log" see if it contains a list of camera names fetched from the vms, or otherwise error notifications indicating a problem possible errors wrong details were entered during the iris+™ vms gateway installation (examples ip, port number, credentials) to change any of the required parameters, refer to the “updating configuration parameters” section below wrong or incomplete configuration of the vms server (license, firewall, configuration, cameras not yet added, some vms services are down, etc ) connection is successful; however, a functional failure of the gateway occurs due to the refusal or failure of the vms to correctly respond to the gateway verify the installed gateway windows service has sufficient windows permissions if not, change the gateway service settings to log on as a windows user with the necessary permissions restart the service and verify (in the vmsadapter log) that the gateway service operates properly updating configuration parameters if you need to change any of the integration parameters following the installation, there is no need to uninstall and reinstall the iris+™ vms gateway a dedicated utility is available to update the parameters run the utility as administrator from the shortcut here "c \program files (x86)\irisity ab\iris+ vms gateway\iris+gateway service exe" following any relevant changes in iris+™ portal, iris+™ vms gateway, or onguard, restart the iris+™ vms gateway service for the changes to take effect port setup on iris+™ vms gateway service server for edge integrations port 8098 needs to be open for both tcp and udp traffic on the iris+™ vms gateway server to be able to receive events from iris+™ edge devices make sure that relevant edge devices have connectivity to the iris+™ vms gateway on this port onguard setup after installing the gateway, a “logical source” named “iris+” is automatically added to the onguard configuration for the received events to appear in the main alarm monitor, the iris+ logical source (and its ‘child’ logical devices) must be added to the monitor zone perform the following steps in onguard open onguard license administration select onguard subscription software scroll down until you see the partner integrations section ensure the displayed irisity partner integration appears open onguard system administration select video from the opened menu select digital video in the opened window, click add add a recorder populate the required fields and click ok a list of available monitor zones is displayed select the relevant monitor zone to add the recorder to the recorder is added to the video recorder section select monitoring from the opened menu select monitor zone click modify select logical sources select the device – click the device icon the device is marked click assign and then click ok the device is added to the right hand column onguard segments support the iris+™ vms gateway supports onguard segments in the following way on startup, it checks if segments are enabled in the onguard system (otherwise runs as before) and logs it example log dbg segmentation setting enabled it logs the available segment ids and names it also logs in which segment the gateway will add logical entities if not already added example log dbg segments list start dbg segment #0 'first segment' <== selected (auto) dbg segment #1 'second segment' dbg segments list end the gateway will automatically add logical entities in the first segment in the list, as in the example above but if the user wants the logical entities to be added in a specific segment, the user can do that by creating a file named "custom ini" in the iris+ vms gateway installation folder (typically c \program files (x86)\irisity ab\iris+ vms gateway) the content of that ini file should indicate the id of the segment to be selected example custom ini file contents \[onguard] segmentid=4 stop the gateway service delete the iris+ logical entities that were automatically added in the 1st segment (if any) start the gateway service again this will add the logical entities in the custom selected segment example log dbg segments list start dbg segment #0 'first segment' dbg segment #1 'second segment' <== selected (custom ini) dbg segments list end mapping onguard cameras in iris+™ each camera in onguard has a numeric channel number which needs to be mapped to the corresponding cameras in iris+™ to associate the selected camera with the corresponding camera defined in iris+™, do the following log in to your iris+™ account from the top module bar, select administrator in the device tree select the relevant camera in the device submenu click settings click the edit button enter the channel number in the external id field click save note if you integrate iris+™ to both genetec and onguard – place the genetec external id first to be followed by the onguard external id, separated by a comma configuration of edge integration in iris+™ the recommended method is to transfer the events to onguard via iris+™ core the edge integration should be used only if timing issues (delays) are encountered in event transfers for edge integration additional configuration is needed in the iris+™ system, see below define integration targets the integration targets in iris+™ are the system wide definitions specifying the endpoints that can receive the events sent by iris+™ for the onguard integeration, an integration target pointing to the iris+™ vms gateway server is needed to define this, 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 target name define a meaningful name such as onguard ensure the toggle switch is enabled type keep default values http and post uri paste the events integration url as specified by the iris+™ vms gateway installer, see the "installing iris+™ vms gateway service" section if the gateway and the edge devices are not on the same lan, then you should replace the internal ip in the uri with the public ip of the iris+™ vms gateway server make sure that any relevant iris+™ edge devices can reach this ip and that port 8098 is open, see the "port setup on iris+™ vms gateway service server" section click save the integration target is defined and is listed in the integration targets list define edge integrations in iris+™ the integration target needs to be enabled on each iris+™ edge device which should transfer events to onguard to do that follow these steps log in to your iris+™ account select physical view select the iris+™ edge for which you want to define the integration select integrations click edit enable events integration and select the integration target you have previously defined (in this example – onguard) click save advanced configuration it is possible to tweak certain configuration options using the custom ini file which is typically located here “c \program files (x86)\irisity ab\iris+ vms gateway” the iris+™ vms gateway will read the custom ini file during startup the following is an example of the file content \[onguard] segmentid=1 substringtofiltercameranames=iris+ timezonenamesubstring=eastern time logicalsourcename=iris+ all parameters are optional segmentid see the "onguard segments support" section above substringtofiltercameranames this parameter is used to identify cameras in onguard for which events will be sent from iris+™ to onguard add the string defined for this parameter to e g the end of the camera name in onguard for each defined camera that contains the string, iris+™ creates a logical device in onguard as a default, this parameter has no value, so events can be transferred to all onguard cameras timezonenamesubstring this is the onguard time zone for your deployment set the value to an onguard time zone matching your deployment time zone see a list of time zones in appendix a timezones logicalsourcename by default, the iris+™ vms gateway will create a logical source device in onguard with the name "iris+" this can be overridden using this parameter if you have made any changes to the custom ini file, restart the iris+™ vms gateway service for the changes to take effect troubleshooting the logs for the iris+™ vms gateway service are available as follows installer log name ” vmsgatewayinstall txt" installer log path “c \vmsgatewayinstallation\logs” iris+™ vms gateway service logs path “c \program files (x86)\irisity ab\iris+ vms gateway\logs” irisity customer support may ask for these logs for further troubleshooting contact irisity support customer support technicalsupport\@irisity com mailto\ technicalsupport\@irisity com