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
proshareaudio571312.2UnknownBuilt-inAs neededproshareaudio operates on port 5713 and supports ProShare Audio for audio streaming in ProShare conferencing.
prosharevideo571412.2UnknownBuilt-inAs neededprosharevideo operates on port 5714 and is used by ProShare Video for video conferencing in Intel ProShare systems.
prosharedata571512.2UnknownBuilt-inAs neededprosharedata operates on port 5715 and is used by ProShare Data for sharing data in ProShare environments.
prosharerequest571612.2UnknownBuilt-inAs neededprosharerequest operates on port 5716 and supports ProShare Request for initiating ProShare collaboration sessions.
prosharenotify571712.2UnknownBuilt-inAs neededprosharenotify operates on port 5717 and facilitates ProShare Notify for sending notifications in ProShare systems.
dpm571812.2UnknownBuilt-inAs neededdpm operates on port 5718 and supports Data Protection Manager control services for backups and restore.
dpm-agent571912.2UnknownBuilt-inAs neededdpm-agent operates on port 5719 and manages backup agent communication in Microsoft Data Protection Manager.
ms-licensing572012.2UnknownBuilt-inAs neededms-licensing operates on port 5720 and is used for terminal services client license validation in Windows environments.
dtpt572112.2UnknownBuilt-inAs neededdtpt operates on port 5721 and handles time synchronization messaging in distributed platforms.
msdfsr572212.2UnknownBuilt-inAs neededmsdfsr operates on port 5722 and provides file replication services in Microsoft Distributed File System Replication (DFS-R).
omhs572312.2UnknownBuilt-inAs neededomhs operates on port 5723 and supports messaging in Open Message Handling Systems for enterprise-grade data exchange.
omsdk572412.2UnknownBuilt-inAs neededomsdk operates on port 5724 and supports management communication for Open Management SDK-based systems.
ms-ilm572512.2UnknownBuilt-inAs neededms-ilm operates on port 5725 and supports synchronization and identity management in ILM (Identity Lifecycle Manager).
ms-ilm-sts572612.2UnknownBuilt-inAs neededms-ilm-sts operates on port 5726 and enables secure token services for Microsoft Identity Lifecycle Manager.
asgenf572712.2UnknownBuilt-inAs neededasgenf operates on port 5727 and supports event forwarding and management in ASG (Automated Systems Group) platforms.
io-dist-data572812.2UnknownBuilt-inAs neededio-dist-data operates on port 5728 and supports data distribution services in IO-Link based automation platforms.
io-dist-group572812.2UnknownBuilt-inAs neededio-dist-group operates on port 5728 and manages group communication in IO-based distributed systems.
openmail572912.2UnknownBuilt-inAs neededopenmail operates on port 5729 and supports general communication and administration for OpenMail enterprise messaging systems.
unieng573012.2UnknownBuilt-inAs neededunieng operates on port 5730 and facilitates engineering data communication within UNIENG infrastructure.
ida-discover1574112.2UnknownBuilt-inAs neededida-discover1 operates on port 5741 and enables discovery of IDA systems or services in industrial networks.

Was this information helpful?