How does it work?
Envoy will send a record of every visitor who signs in on your kiosk to C•CURE 9000 as Personnel and automatically create an identity in C•CURE.
You can configure Envoy to apply certain Clearances to visitors based on the tenant they are visiting. You can then use all of C•CURE’s features for your visitors, such as badge provisioning, security alerts, and more.
PREREQUISITES
For on-premises C•CURE 9000 to work with Envoy’s cloud solution, the internal IP address for the C-Cure instance must be NAT’d from a publicly accessible IP address or URL. Alternatively, a DMZ or proxy service may be used to ensure that the C•CURE instance is accessible to Envoy.
In order for the app to work and connect to your C•CURE 9000 instance, please allowlist the following IP addresses for inbound and outbound communication:
18.204.164.109
52.6.210.64
52.86.90.108
Validate the port for your C•CURE instance and confirm the port where traffic is expected to flow through is open. The standard secure port should be open (Port 443).
NOTE: C•CURE version 2.8 and lower do not accept secure HTTPS connections on Port 443 by default. A certificate must be provided and configured in IIS. More information here.
The victor Web Service for End-Users license must be enabled on the systems license to allow use of C•CURE’s RESTful API. For more information, please refer to Software House’s documentation here.
For this app to work, the Envoy integration driver needs to be installed along with the CC9WS-ENVOY option enabled on the systems license (please reach out to your C•CURE rep for pricing).
If your C•CURE Version is 2.8+, you will need to add an additional license. Please follow the instructions here. It may also be necessary to reach out to C•CURE support for assistance with the license.
To connect Envoy and your C•CURE instance, Envoy requires user authentication through an ‘Operator’ with ‘SYSTEM ALL’ permission. Operator must be a victor admin.
Occupancy dashboard metrics require CCURE 9000 v2.9 SP2. The API for polling badge events was introduced in this version.
Configuring the Envoy + C•CURE 9000 integration
The integration requires an ‘Operator’ with ‘SYSTEM ALL’ permission on the C•CURE account to complete this integration. Either become an administrator or ask your administrator for help before completing these steps.
Step 1: API Details
Go to Apps > All Apps.
Search for and click on C•CURE 9000 then click Install.
Enter your IP and port, or URL as mentioned in Pre-Requisite step 1.
Enter your C•CURE operator login credentials.
Select your C•CURE Version.
Step 2: Partition
Select the C•CURE partition Envoy should use for building Visitors.
Step 3: Clearances
Assign Tenants to a predefined C•CURE Clearance.
This allows certain Tenants to have pre-defined access to specific doors, turnstiles, or elevators once the visitor is checked in at the security desk.
Check to delete all CCURE Clearances when visitors sign out.
Select the Personnel Type for records generated through this integration.
Enable Credentials (Optional)
If this toggle is checked, QR code credentials will be generated.
Select the length of time signed-in visitors have valid credentials.
Select the length of time invited visitors will have their credentials turned on in advance of signing in.
Enter the Minimum Card number.
Enter the Maximum Card number.
If applicable, enter the facility code. If a facility code is not entered, it will default to 0000.
Select the appropriate CHUID format.
Select the Personnel Type for records generated through this integration.
Optional, enter a text to be included in the body of the QR code e-mail.
Embed QR Code in Badge (Optional)
This will embed the QR code in printed badges when enabled.
Step 4: Employee Clearance
Note: To collect tenant employee badge events for occupancy analytics, enable the toggle.
Assign Tenant Employees to a predefined C•CURE Clearance.
This allows Tenant employees to be mapped to specific C-Cure clearances when issuing temporary employee badges.
Select which readers to collect events from.
You can also choose to collect events from all readers
Select which readers to process auto sign-in events from.
You can also choose to use all readers for auto sign-in event processing.
Provide a duration for temporary employee badges.
If applicable, enter the facility code. If a facility code is not entered, it will default to 0000.
Select the appropriate CHUID format.
Enter the temporary badge min and max range
Select the Personnel Type for records generated through this integration.
(Optional) How to set up access control via QR codes
NOTE: The QR code will be encoded as FFFFNNNNNNNN.
FFFF is the facility code padded to four characters
NNNNNNNN is the card number padded to eight characters
Confirm that ‘Enable Credentials’ and ‘Enable QR Code in Badge’ checkboxes mentioned in Step 3 are checked
On the left-hand menu, navigate to Settings > Badges, and click ‘Edit’ next to Badge Display or click this link.
Find the dropdown at the bottom of the modal that says “QR code” and select “CCure Badge QR Code”
You can provide access control QR-codes to tenant visitors by sending them in invitation emails. Learn more here.
C-CURE 9000 Envoy integration looking for secure connection with victor web service
This issue should only occur with CCure 9000 systems which are version 2.8 or lower. Versions 2.9 and higher have fixed this issue.
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.
Select the Services and Applications directory and the Internal Information Services (IIS) Manager menu. Expand the directory to find the victorwebservice website. Click on the browse *.443 link to validate if HTTPS is working. This opens a browser and authenticates using TLS at the specified URL. If it’s blocked, the port is not set up.
To set up HTTPS on Port 443, Go to Default Web Site and click on Bindings.
Then select https (port 443) and click Edit. Open the SSL certificate list and select the appropriate certificate. The certificate allows authentication using secure ports (443).
Connect Occupancy Metrics
PREREQUISITES for Auto Check-in with Badge Swipe for Connect Occupancy Metrics:
C-CURE 9000 Version 2.9 SP4 or newer (The API for polling badge events was introduced in this version.)
Badging access points set up (doors) in the C-CURE system.
Personnel created/imported in the C-CURE system where the email matches an employee in the Envoy's Connect Employee Directory (emails must match)
The timezone of the CCURE instance must be set in Step 1 of the app configuration in the Envoy dashboard.
FAQ
What versions of C•CURE 9000 does the Envoy integration support?
2.7
2.8
2.9
3.0
What licenses are required by C•CURE?
Envoy integration driver needs to be installed along with the CC9WS-ENVOY option enabled on the systems license.
The victor Web Service for End-Users license must be enabled on the systems license to allow use of C•CURE’s RESTful API.
Version 2.8+ requires a license GUID specific to Envoy. This will need to be added to your C•CURE instance.
Injection Script:
InsertLicenseOption /U /V /S:"LOCALHOST" /N:"Envoy - Visitor Management - Integration" /A:"Envoy, Inc." /G:24f84d83-1428-4bad-a4ec-11e2e955ee80 /C:2 /P:0Watch this instructional video in order to add the license GUID
Please reach out to C•CURE support if you have issues with adding the GUID license.