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

Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 6 Next »

Firewall

An Ethernet connection with DHCP must be used to connect the Smart Hub (ACU) or Single Door Controller (SDC) to the Local Area Network (LAN). You also need to configure firewall settings to communicate with the Avigilon Alta system. Avigilon Alta uses the following outbound ports:

  • TCP port 443

  • UDP port 123

NOTE: If using an external DNS server, outbound UDP port 53 must also be open.

To support Wi-Fi unlocking from the mobile app, the ACU/SDC's inbound TCP port 443 must be available from within the LAN. Inbound port forwarding on the router, firewall, or NAT device is not required.

We do not allow HTTPS certificate rewriting or TSL/SSL inspection.

IP Address

Currently, we do not provide an IP range or FQDN list of Avigilon Alta hostnames. Most hostnames resolve to dynamic IPs and the hostnames themselves change during provisioning and configuration update processes. If you wish to segregate traffic from your Openpath controllers, you can enable a DMZ for the controllers to separate their traffic.

  • No labels