Ports used by the DMP Intrusion Panel extension

Ports used by the DMP Intrusion Panel extension - DMP intrusion panel 4.3.0

DMP Intrusion Panel Extension Guide 4.3.0

Product

DMP intrusion panel

Content type

Guides > Plugin and extension guides

Version

4.3

Release

4.3.0

Language

English

Last updated

2023-09-08

Before installing the DMP Intrusion Panel extension, you must ensure that the required ports are open on all network switch routers and firewalls, and that no other applications are using these ports.

IMPORTANT: It is recommended that you keep the ports at their default values. If you make changes to user configurable ports, ensure that the inbound port number is correctly set, otherwise you might not receive events and state changes when activity happens on the panel.

Regular (PC Log) connection

Application	Inbound	Outbound	Configurable	Port usage
DMP panel command connection	-	TCP 2001	Yes	Network programming and intrusion command port
DMP event connection	Automatically selected	-	Yes	Event callback port NOTE: Your DMP panel must be able to connect to the intrusion manager on this port. This port must be unique per panel on the intrusion manager. Event port overlap is not allowed on the same intrusion manager.

Integrator path connection

Application	Inbound	Outbound	Configurable	Port usage
DMP panel command connection	-	TCP 8011	Yes	Network programming and intrusion command port
DMP event connection	TCP 8011	-	Yes	Event callback port NOTE: Your DMP panel must be able to connect to the intrusion manager on this port. This port must be unique per panel on the intrusion manager. Event port overlap is not allowed on the same intrusion manager.

Entré connection

Application	Inbound	Outbound	Configurable	Port usage
DMP panel command connection	-	TCP 2022	Yes	Network programming and intrusion command port
DMP event connection	TCP 2023	-	Yes	Event callback port NOTE: Your DMP panel must be able to connect to the intrusion manager on this port. This port must be unique per panel on the intrusion manager. Event port overlap is not allowed on the same intrusion manager.