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

This is an old revision of the document!


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
v5ua567512.2UnknownBuilt-inAs neededv5ua operates on port 5675 and is used for transporting V5.2 interface messages over IP networks, enabling signaling between access and core telecom systems.
raadmin567612.2UnknownBuilt-inAs neededraadmin operates on port 5676 and supports RA Admin for remote administration services.
questdb2-lnchr567712.2Data basesBuilt-inAs neededQuestDB2-Lnchr manages secure launch and session control for Quest Software’s DB2 tools.
rrac567812.2UnknownBuilt-inAs neededrrac operates on port 5678 and supports remote RAC (Remote Access Controller) management.
dccm567912.2UnknownBuilt-inAs neededdccm operates on port 5679 and facilitates DCCM (Distributed Configuration and Control Manager) for system control.
auriga-router568012.2UnknownBuilt-inAs neededauriga-router operates on port 5680 and facilitates routing and control traffic in Auriga platform infrastructures.
ncxcp568112.2UnknownBuilt-inAs neededncxcp operates on port 5681 and is used by network-connected lighting or building control systems using NCXCP protocol.
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.

Was this information helpful?