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

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. Description
  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.
  4. DSL protocols — protocols described in the DSL language and connected to DPI as a separate module, without reinstalling the software or causing traffic interruption. Unlike custom protocols, a DSL protocol is a finite state machine that analyzes the first N packets of a flow against defined conditions (ports, AS numbers, payload bytes, DSL expressions) and determines whether the flow matches the protocol.
    DSL protocols are created by VAS Experts specialists upon client request to Technical Support.

ProtocolIDDPI versionProtocol groupProtocol typeUpdateDescription
brightcore568212.2UnknownBuilt-inAs neededBrightCore protocol used in smart building, HVAC, or IoT automation platforms.
coap568312.2UnknownBuilt-inAs neededcoap operates on port 5683 and is the default port for the Constrained Application Protocol used in IoT device communications.
ggz568812.2UnknownBuilt-inAs neededggz operates on port 5688 and supports communication in the GGZ Gaming Zone, an online multiplayer gaming infrastructure.
qmvideo568912.2UnknownBuilt-inAs neededqmvideo operates on port 5689 and supports QM Video for video streaming or management in QM systems.
rbsystem569312.2UnknownBuilt-inAs neededrbsystem operates on port 5693 and supports RBSystem for resource or backup system communication.
kmip569612.2UnknownBuilt-inAs neededkmip operates on port 5696 and supports key management operations in KMIP-compliant systems for cryptographic infrastructure.
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.

Was this information helpful?