Ccure 9000 Software Download
Skye Severy
I am curious as per why CC 9000 integration with Exacq failed "Soft Triggers" being that they (SWH and Exacq) are both owned by Tyco (now Johnson, next Fudruckers? :) ), hence rendering it a lame integration and useless solution. Our customer wanted ability to track false forced door alarms and be able to search based on Ccure Events, which is what is meant by the "Soft Trigger" functionality referenced at Exacq's web site product integration section.
Luckily I was able to make up for this deficiency by tricking ccure into thinking the Exaqc NVR was a Legacy AD Matrix Switch, Exacq's facility for POS and a Lantronix. I accomplished this by trial and error with little to no help from SWH. Exacq did help a tad with POS and Serial port configurations.
One of my biggest frustrations with our industry as an integrator is being an unappreciated beta tester for the manufacturers and taking heat from end users on one end of a problem and being treated like crap from the manufacturer on the other end!
I do not know the answer specifically to 'soft triggers' integration but I suspect that a big factor is that there are a lot of elements to integrate and it can be difficult to justify integrating them all save for a requirement on some large project. I do think TSP (Tyco Security Products or whatever they call it now that it is JCI) does very much want to deliver integration amongst all their security products and that Exacq has spent significant efforts in the past few years to that end (e.g., Exacq Adds Access and Intrusion Integration).
I feel your pain. We hit a fair number of problems when we do testing that clearly should have been identified and fixed before production release. If you have problems that cannot be solved, post them as a discussion or email us (e.g., in...@ipvm.com or jo...@ipvm.com, etc.).
I will also keep my name private (as I usually do), but I absolutely share your pain here. Software House specifically has devolved into a totally unmanageable beast that is impossible to work with and unwilling to even support their own products. I have absolutely all but stopped selling SWH because of this.
I don't pretend that anyone from SWH would read this and care, but I also work for a fairly large integrator that is a fairly large SWH partner, and I know for a fact that I am not the only one that feels this way at my company.
Is anyone collecting Audit and Activity events from the CCURE 9000 application? The logs are in a SQL DB so I assume using the DBConnect2 app is the way to go. I am interested in any advice on what and how to collect the data. Also, any information on the impact to the application caused by collecting the data.
DB performance is only a consideration on initial set-up and if you have a lot of historical.
That said, we brought-in some 10-15,000 transactions from CCURE9000 and it only took a few seconds to ingest when we set-up the DB Connect. We have ours on rising column against MessageUTC, set to run every 15 minutes.
We have not experienced any performance hits.
Im having the same problem getting data from CCure DB into Splunk. I saw a CCure plugin that interacts with the DBConnect app but it still lacks any information on how to create a SQL statement that will work with the CCure DB out of the box.
Problem with DBConnect is the input methods. You cant use "batch input" because it creates duplicates after every SQL run. Your left with Rising Input, which is also problematic because there is no column that is a good candidate for rising because that column should be incremental. Closest thing is some mathematical calculation of a few columns to create a proper timestamp, which Splunk does not recommend anyway due to a number of issues per the DBConnect docs. Not only that but "Rising method" of DBConnect requires the rising column name in the "where" clause which MSSQL does not support since the timestamp needs to be calculated and assigned an alias and aliases are not valid in "where" clause. Sigh...
We recommend companies identify key personnel and elevate their CFLs now as it will not impact their day to day access and is the most time- consuming part of this process. Creating events that can elevate and restore the CFLs of specific doors in a building, campus, or region can be done quickly in case of an emergency on an SAS by SAS basis. If you have more time, we recommend doing this on a site-by-site or campus basis so a standard is created that can be replicated globally. This way your GSOC, RSOC, or lobby operator can trigger this event as needed and you can nest the events for regional activations.
CCure 9000 Filter Levels can give security operations managers the flexibility they require to lock non-infrastructure employees out of the building without the heavy lift of disabling their badges or removing clearances.
The document is a user's manual for a C-Cure 9000 security monitoring system. It provides instructions for operating the monitoring station software, including how to log in, acknowledge and clear alarms, monitor camera feeds, view the activity log, check hardware statuses, and log messages. The manual describes the main interface windows and explains how to perform key tasks like responding to alarms, monitoring video, and initiating manual actions on security objects.Read less
A certificate must be provided and configured in IIS for the CCure 9000 victor web service to accept secure HTTPS connections on port 443. Contact CCure 9000 engineering and support resources to verify the CCure 9000 system is configured to enable secure communications.
Check if the port number (443) is configured to work with HTTPS on the CCure 9000 server. Go to the CCure 9000 server. From the Start menu, open the Windows Administrative Tools application and open the Computer Management menu.
The interface is based on a special integration module which is available from Software House.This article assumes that the reader is familiar with setup and operation of C-Cure 9000. Only points which are specific to ICX/AlphaCom and to its connected intercom stations are described.
To be able to create these tables, the account which is used by the 'AlphaCom Driver Service' needs to have the appropriate permissions. To check which account is used by the 'AlphaCom Driver Service'
Use 'Microsoft SQL Server Management Studio' to assign the appropriate permissions to the account. The 'AlphaCom Driver Service' must either have 'sysadmin' permissions to the database instance or 'db_owner' permissions to the 'ACVSCore' database.
The communication with ICX or AlphaCom is through TCP port 61112 or 61113. Make certain that one of these ports has been opened in the 'Filter page' in the Web interface.In an AlphaNet system all ICX/AlphaCom servers must have this same port opened.
AlphaCom with software prior to version 11.5.3.5 only offers the possibility to connect to 2 standalone or SAS servers. As from the software version 11.5.3.5 AlphaCom in an AlphaNet supports the possibility to connect to 10 standalone or SAS servers, as the ports 61112/61113 on each server are now independent of each other.As from ICX-AlphaCom version 1.1.3.5 ports 61112/61113 support multiple connections. A total of 120 stand-alone or SAS-servers can be connected.
As from integration module versions 2.80.009 and 2.90.006, it is possible to open doors during a conversation by pressing digit 6 on an operator intercom. Instead of operating a relay on the door station, a datastring is sent to CCure9000. To configure this, setup an event 'Door opening - during connection' and enter the following action string:
Setup of the ICX/AlphaCom connection in C-Cure 9000 is done in the C-Cure 9000 Administration Workstation. Note that some of the descriptions in the text below are dependent on choices which are made during setup, it may therefore be that the actual system being used operates slightly differently.
Note that in a partitioned system it is possible to select to which partition and hardware folder within that partition the ICX/AlphaCom connection shall be assigned to. It is possible to at a later stage move the ICX/AlphaCom connection to another partition and hardware folder by simply selecting the appropriate settings from the drop down lists under the TAB 'Partition and Folder'.
When 'Automatically Populate Devices' is disabled, neither nodes nor intercom stations will be discovered. It is also possible to only disable auto-discovery for intercom stations connected to a specific node. Right click on the node and select 'Edit' to access the node information.
A C-Cure 9000 Enterprise system consists of a MAS (Master Application Server) and 1 or more SAS's (Satellite Application Server). Each SAS must have its own connection to the AlphaNet (max 10 such connections are possible). The MAS will collect all device information from all to it connected SAS's. In such an Enterprise system it may be advisable to:
In this scenario, the intercom is used to handle calls and open doors. The command to open the door is sent to CCure9000, which in turn opens the door. In the TAB 'Intercom Settings' there are 2 fields that need be to considered:
By associating a door to an intercom station, it is possible to open that door by pressing digit 6 when an operator is in conversion with that door station (also see the paragraphs above). This functionality is available as from integration modules 2.80.009 and 2.90.006.In the 'Associations' TAB of the intercom station property editor it is possible to select the appropriate door from a drop down box. Note that the door needs to be configured in CCure9000 before it will appear in this drop down list.
The intercom icon has default images for each state. In the TAB 'State images' it is possible to assign a new image to a state. Simply double click on an existing image and browse to the new image file.
c80f0f1006