The current Openpath Jira and Confluence instances will be migrated to the MSI On-Premise solution from August 9th-11th, the current platform will be set to read-only and all future usage will be in the Avigilon Instance. Please ensure access to MSI Jira & MSI Confluence, both are accessible through OKTA. For additional information and details please refer to the Atlassian migration page
Mobile Gateway Overview
Mobile Gateway allows the Avigilon Alta system to sit in front of the legacy access control system and communicate via the Wiegand protocol. The legacy system will still be the final authority and authenticate credentials and manage all reporting. Avigilon Alta looks like a reader to the legacy system already installed.Â
This requires a jumper from the Avigilon expansion board to the legacy panel (AUX1 - D0, AUX2 - D1, GND- GND). For more information on configuring the AUX I/O, refer to How to wire Wiegand devices to Core Series hardware.
4-Port board example:
To use an SDC put the jumpers between the SDC and the legacy panel as follows, D0 - D0, D1 - D1, GND - GND.
SDC example:
Â
Mobile Gateway Configuration
This section outlines three configuration options.
Generic Gateway: Where user unlock attempts are authenticated and authorized by the Smart Hub, which then sends a default Wiegand ID to the legacy panel.
Modify the Wiegand Device within Entry Management to configure it for Output (Gateway) Mode.
Pass-through: Where Wiegand credentials pass directly through the Smart Hub’s output port, without being authenticated by the Avigilon Smart Hub ACU. All access control decisions are determined by the legacy panel and credentials will not need to be programmed in Avigilon Alta.
User-specific Gateway: This requires the user to have a prox card added as a credential and the Use for Gateway flag set to Enabled. This will convert the Avigilon Mobile Credential to Prox ID that gets transmitted via the Wiegand interface with the legacy system.
High-Level Overview of Mobile Gateway
Â
Â