Skip to content

AEOS Integration

The AEOS integration component connects VisitorPass to Nedap AEOS. It runs as a Windows service on your AEOS server.

Network Requirements

The AEOS integration runs on your AEOS server beside the AEOS application server, which it talks to over SOAP on port 8443. From there it opens DIP connections on port 8001 to one or more AEpu door controllers, sends relevant carrier and badge changes out through your firewall to VisitorPass on port 443, and receives visitor provisioning and door badge events from VisitorPass on port 8888.

# From To Port Protocol Purpose
1 AEOS server Each AEpu door controller TCP 8001 Nedap DIP Opens doors
2 AEOS server VisitorPass (visitorpass.partisia.com) TCP 443 HTTPS Carrier & Badge Changes
3 VisitorPass (visitorpass.partisia.com) AEOS server TCP 8888 HTTPS Visitor Provisioning & Door Badge Events

To set them up:

  1. For each AEpu door controller, allow TCP 8001 from the AEOS server to the controller. If a controller sits behind its own router or 4G modem, set up a port forward to TCP 8001 on that modem.
  2. Allow outbound HTTPS (TCP 443) from the AEOS server to visitorpass.partisia.com.
  3. Make sure TCP 8888 is free on the AEOS server.
  4. Forward TCP 8888 from your public address to the AEOS server, and allow it in the firewall from visitorpass.partisia.com.
  5. Send Partisia:
    • the public address that TCP 8888 is forwarded from
    • the AEOS server's host name
    • the address of each AEpu door controller
  6. Give Partisia remote access to the AEOS server for installation, for example TeamViewer.

Notes:

  • The integration talks to AEOS on the same server, over port 8443.
  • The connections to the AEpu controllers stay open permanently and send heartbeats. Firewalls and modems should not close idle sessions on them.
  • Connection 3 is encrypted with a certificate Partisia issues for the AEOS server's host name.

What's Next