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
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.
otmp2916712.2UnknownBuilt-inAs neededotmp operates on port 29167 and refers to Open Transport Messaging Protocol for distributed services.
sbcap2916812.2UnknownBuilt-inAs neededsbcap operates on port 29168 and enables Service-Based Configuration and Provisioning in telecom and IoT systems.
iuhsctpassoc2916912.2UnknownBuilt-inAs needediuhsctpassoc operates on port 29169 and supports SCTP association for IuH interfaces in LTE femtocell deployments.
bingbang2999912.2UnknownBuilt-inAs neededBingBang protocol potentially associated with high-speed messaging or gaming.
ndmps3000012.2UnknownBuilt-inAs neededndmps operates on port 30000 and is used for secure backups using the NDMP (Network Data Management Protocol) with additional features.
pago-services13000112.2UnknownBuilt-inAs neededpago-services1 operates on port 30001 and provides core transaction services for the Pago financial system.
pago-services23000212.2UnknownBuilt-inAs neededpago-services2 operates on port 30002 and supports online payment service communication in Pago service platforms.
kingdomsonline3026012.2UnknownBuilt-inAs neededkingdomsonline operates on port 30260 and enables multiplayer and backend game services for Kingdoms Online.
ovobs3099912.2UnknownBuilt-inAs neededovobs operates on port 30999 and is used by OpenView for observer process communication in system monitoring.
autotrac-acp3102012.2UnknownBuilt-inAs neededautotrac-acp operates on port 31020 and supports Autotrac ACP 245 for real-time vehicle tracking and fleet management communication.
yawn3102912.2UnknownBuilt-inAs neededyawn operates on port 31029 and handles notification or alert signals in lightweight or experimental network stacks.
xqosd3141612.2UnknownBuilt-inAs neededxqosd operates on port 31416 and manages QoS (Quality of Service) settings in experimental or extended networking platforms.
tetrinet3145712.2UnknownBuilt-inAs neededtetrinet uses port 31457. No additional documentation found.