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
ezproxy2626012.2Tunneling, secure, ssl, pkiBuilt-inAs neededEZproxy is a web proxy server developed by OCLC, used by libraries to provide off-campus access to licensed electronic resources.
ezmeeting2626112.2UnknownBuilt-inAs neededezmeeting operates on port 26261 and facilitates EZMeeting for video conferencing and collaboration.
k3software-svr2626212.2UnknownBuilt-inAs neededk3software-svr operates on port 26262 and serves as the server-side component of the K3 Software Suite, handling incoming client requests.
k3software-cli2626312.2UnknownBuilt-inAs neededk3software-cli operates on port 26263 and is part of a client-server architecture used for communication within the K3 Software Suite.
exoline-tcp2648612.2UnknownBuilt-inAs neededexoline-tcp operates on port 26486 and supports ExoLine TCP for device communication in Exosite IoT platforms.
exoline-udp2648612.2UnknownBuilt-inAs neededexoline-udp operates on port 26486 and facilitates ExoLine UDP for lightweight IoT data exchange (shared port).
exoconfig2648712.2UnknownBuilt-inAs neededexoconfig operates on port 26487 and is used by ExoConfig for configuration management in Exosite systems.
exonet2648912.2UnknownBuilt-inAs neededexonet operates on port 26489 and supports ExoNet for network communication in Exosite ecosystems.
imagepump2734512.2UnknownBuilt-inAs neededimagepump operates on port 27345 and facilitates multimedia or image data distribution in enterprise systems.
jesmsjc2744212.2UnknownBuilt-inAs neededjesmsjc operates on port 27442 and is used for job scheduling and coordination in JES/MSJC batch environments.
kopek-httphead2750412.2Web browsingBuilt-inAs neededKopek HTTP Head Port, registered 2002-07
ars-vista2778212.2UnknownBuilt-inAs neededars-vista operates on port 27782 and provides remote management and data synchronization for ARS Vista building automation systems.
astrolink2787612.2UnknownBuilt-inAs neededastrolink operates on port 27876 and provides satellite or terrestrial communication for Astrolink data services.
tw-auth-key2799912.2UnknownBuilt-inAs neededtw-auth-key operates on port 27999 and handles authentication key exchange in Taiwan-based secure application frameworks.
nxlmd2800012.2UnknownBuilt-inAs needednxlmd operates on port 28000 and provides license management services for NX software in design or simulation tools.
pqsp2800112.2UnknownBuilt-inAs neededpqsp operates on port 28001 and supports PQSP (Priority Queue Service Protocol) for prioritized data queuing.
a27-ran-ran2811912.2UnknownBuilt-inAs needed3GPP protocol for inter-RAN communication in cellular networks.
voxelstorm2820012.2UnknownBuilt-inAs neededvoxelstorm uses port 28200. No additional documentation found.
siemensgsm2824012.2UnknownBuilt-inAs neededcuseeme operates on port 7648 and provides video conferencing over IP in legacy CU-SeeMe environments.
sgsap2911812.2UnknownBuilt-inAs neededsgsap operates on port 29118 and facilitates SGSAP (S-GW Service Area Protocol) for LTE service area management.