AEOS (Nedap) - ICX-AlphaCom integration

This article describes the integration between AEOS (Nedap) and ICX-AlphaCom. The main content is written by our platinum partner Elbo, with updates from Patrick Castelein.

Functional Specifications

The AEOS <-> AlphaCom interface is a bi-directional connection, based on the Socket interface on the AEOS side and a EDO/EDI connection on the AlphaCom side. The link is actualized on the basis of local intercom server ICX-500/ICX-Core to AEOS, without the inclusion of AlphaNet.

It is also possible to log in directly to the AEpu (door controller), but this is not included in this document. The functionalities below become available with this interface:

1. Opening doors in AEOS environment during an intercom conversation (ICX-AlphaCom to AEOS) after providing the “open door” command in ICX-AlphaCom and playing a prerecorded audio message on the intercom when the door is opened by AEOS. By default, this involves pressing the “6” key during an intercom conversation.
2. Play a prerecorded audio message in an intercom station or make a call when an access key or badge is authorized or denied (AEOS to ICX-AlphaCom).

Requirements Zenitel

Compatability list

• AlphaCom XE AMC version 11.2.3.11 (or higher).
• ICX 500/ICX-core Server FW 1.2.3.9. (or higher).
• AlphaPro 11.7 when using AC XE
• AlphaPro 12.1.3 (or higher) for AC ICX 500/ICX-CORE.

Zenitel (ICX-AlphaCom) License for Interfacing

• 1002602400 ILI-IF Interface Enabling license for ICX 500/ICX-CORE.
• 1002604000 (basic) or 1002604100 (enhanced) Audio Messaging License for ICX 500/ICX-core (Depending on the desired number of audio messages).
• 1009648500 (basic) or 1009648501 (enhanced) Audio Messaging License for AlphaCom XE (Depending on the desired number of audio messages).

Requirements AEOS

Compatibility list Nedap

• AEOS version 2021.X (or higher)
• System user credentials

Nedap (AEOS) License for Interfacing

• No additional License(s) needed.

Communication from ICX-AlphaCom to AEOS

The following relates to a test setup, but can be used as a template for the solution in a production environment.

Login

To establish a connection with the Socket interface in AEOS, the ICX-AlphaCom needs to log in to AEOS. An event must be created in the Event Handler to log in. The commands below are sent to AEOS.

String: EDO 1 "login(socketuser,socketpw)\x3B\r\n"

Login =login command Socketuser =username Socketpw =user password

String: EDO 1 "setRmiCommandConnection(true)\x3B\r\n"

setRmiCommandConnection = activate commands to the socket interface

String: EDO 1 "setRmiEventConnection(true)\x3B\r\n"

"setRmiEventConnection(true) = enable receiving events from the socket interface

Door control (opening)

During a conversation, a main intercom station can activate the door control by pressing digit “6” during the conversation. The command below is sent by ICX-AlphaCom to the socket interface of AEOS to establish door opening.

EDO 1 "executeArgs(provideAccess\,[]\,\"aepu1:frontdoor\")\x3B\n\r"

Aepu1 = The name of the AEpu (door controller “Hostname” in AEOS ) frontdoor = The service name / Display text of door on the Aepu1 (“Access Point” in AEOS)

Messages from AEOS to ICX-AlphaCom

When an access control badge is denied or allowed, one or more actions can be performed using the link. Likely actions are a call to reception in the event of an expired or blocked badge, or a welcome message when access has been granted. The connection from AEOS is also verified on heartbeat. When no heartbeat is determined, ICX-AlphaCom will attempt to log in again once per minute.

The string from the AEOS is made up of several fields, each separated by one “|”. E.g.:

Event:GE|40|AEOS|210|nvc2522aepu1:voordeur|1015|20240105|154723|NedapXS Cards 3|Pietje Puk||0||#003;

Field numbers: Event: -- 1 -- | -- 2 -- |-- 3 -- |-- 4 -- |-- 5 -- |-- 6 -- |-- 7 -- |-- 8 -- |-- 9 -- |-- 10 -- | -- 11 -- |#003;

In the ICX-AlphaCom event handler, the various fields are filtered from the string and the desired action is performed based on the content.