List of protocols [Документация VAS Experts]

List of protocols

  1. Built-in protocols — updated along with the SSG software version. Installing a new version requires a DPI reboot, which causes traffic interruption.
    If needed, they can be supplemented with up-to-date attributes from the VAS Cloud. This is only necessary for complex protocols, but the option is available for all.
  2. Cloud protocols created by VAS Experts — are periodically updated from the VAS Cloud. This ensures that popular applications remain up-to-date as their behavior changes.
  3. Custom (user-defined) protocols — protocols created by users via the GUI using VAS Cloud tools. These have higher priority than those loaded from the VAS Cloud, and within them, IP:PORT takes precedence over IP and CIDR. It is possible to add a protocol based on IP, SNI, or AS. Guide.
ProtocolIDDPI versionProtocol groupProtocol typeUpdateDescription
amcs876612.2UnknownBuilt-inAs neededAdvanced Metering Control System for utility and energy monitoring networks.
dpap877012.2UnknownBuilt-inAs neededdpap operates on port 8770 and supports printing and media sharing via Digital Photo Access Protocol on Apple devices.
msgclnt878612.2UnknownBuilt-inAs neededmsgclnt operates on port 8786 and handles messaging between client components in distributed systems.
msgsrvr878712.2UnknownBuilt-inAs neededmsgsrvr operates on port 8787 and enables centralized messaging in distributed enterprise applications.
acd-pm879312.2UnknownBuilt-inAs neededacd-pm operates on port 8793 and is used for performance monitoring in Automatic Call Distribution systems.
truecm880412.2UnknownBuilt-inAs neededtruecm operates on port 8804 and facilitates control and data exchange for TrueCM communication platforms.
dxspider887312.2UnknownBuilt-inAs neededdxspider operates on port 8873 and facilitates DXSpider for amateur radio DX cluster communication.
galaxy4d888112.2UnknownBuilt-inAs neededgalaxy4d operates on port 8881 and is used in Galaxy 4D platforms for high-resolution rendering or data processing.
secure-mqtt888312.2UnknownBuilt-inAs neededsecure-mqtt operates on port 8883 and facilitates Secure MQTT for encrypted Message Queuing Telemetry Transport in IoT.
ddi-tcp-1888812.2UnknownBuilt-inAs neededddi-tcp-1 operates on port 8888 and supports DDI TCP 1 for device driver interface communication (instance 1).
ddi-udp-1888812.2UnknownBuilt-inAs neededddi-udp-1 through ddi-udp-7 operate on ports 8888–8894 and are used for distributed device interface communication over UDP in automation systems.
ddi-tcp-2888912.2UnknownBuilt-inAs neededddi-tcp-2 operates on port 8889 and is used by DDI TCP 2 for device driver interface communication (instance 2).
ddi-udp-2888912.2UnknownBuilt-inAs neededddi-udp-2 operates on port 8889 and provides device communication over UDP in Distributed Device Interface (DDI) systems.
ddi-tcp-3889012.2UnknownBuilt-inAs neededddi-tcp-3 operates on port 8890 and supports DDI TCP 3 for device driver interface communication (instance 3).
ddi-udp-3889012.2UnknownBuilt-inAs neededddi-udp-3 operates on port 8890 and supports command and control operations in DDI-enabled industrial networks.
ddi-tcp-4889112.2UnknownBuilt-inAs neededddi-tcp-4 operates on port 8891 and enables command, monitoring, and configuration communication in TCP-based DDI networks.
ddi-udp-4889112.2UnknownBuilt-inAs neededddi-udp-4 operates on port 8891 and enables event or data transfer services in DDI UDP-based environments.
ddi-tcp-5889212.2UnknownBuilt-inAs neededddi-tcp-5 operates on port 8892 and supports DDI TCP 5 for device driver interface communication (instance 5).
ddi-udp-5889212.2UnknownBuilt-inAs neededddi-udp-5 operates on port 8892 and is used for status and telemetry messaging in Distributed Device Interface systems.
ddi-tcp-6889312.2UnknownBuilt-inAs neededddi-tcp-6 operates on port 8893 and supports secure data transmission and control in Distributed Device Interface (DDI) systems over TCP.

Was this information helpful?