The Bridge

VPX Gateway Nodes

The planned bridge between traditional telecom infrastructure and the VPX blockchain layer - designed to connect carriers to the ecosystem without replacing their existing stack. In development; part of the VPX Protocol, mainnet planned Q4 2026.

SIPVOICE PROTOCOLS
SMPP v3.4SMS PROTOCOL
Signalling-onlyMEDIA HANDLING
Up to 100,000 concurrent sessions per nodeCONCURRENT CALLS
Overview

What it
does

Gateway Nodes are the planned entry and exit points for the VPX Network. They are designed to bridge traditional telecom protocols - SIP, H.323 and SMPP - to the VPX blockchain layer, so carriers will be able to connect their existing infrastructure to the VPX Ecosystem without any forklift upgrade - a carrier with an existing SIP or H.323 switch connecting in hours, not months.

The Gateway Node performs bidirectional protocol translation: inbound traffic from traditional networks is translated into VPX routing request transactions, routed through the VPX Network and returned as standard SIP or H.323 signalling to the destination. From the carrier's perspective, the VPX Network looks like a standard interconnect - just one that happens to be decentralised, fraud-protected and quality-monitored.

Gateway Nodes also serve as the submission point for CDR data, quality events and fraud reports from connected carriers. Every call that transits a Gateway Node contributes to the shared network intelligence pool - improving routing quality, fraud detection and analytics for every other participant on the VPX Network.

Node Process

How the node operates

01

Carrier Interconnect

The carrier establishes a standard SIP or H.323 interconnect to the Gateway Node. Existing switch configuration - no new hardware required on the carrier side.

02

Protocol Translation (Inbound)

SIP INVITE or H.323 Setup is received and translated into a VPX routing request transaction. Called-party, calling-party, traffic class and quality requirements are encoded and signed.

03

VPX Network Routing

The routing request is submitted to the VPX Network. Routing Nodes apply quality-weighted LCR and return the selected egress path. Fraud Nodes validate the originating number against the blacklist.

04

Protocol Translation (Outbound)

The routing result is translated back to SIP or H.323 for delivery to the egress carrier. Media is handled directly between endpoints - Gateway Nodes process signalling only, not media.

05

CDR and Event Submission

On call completion, the Gateway Node submits a signed CDR and quality event to the VPX Network. Data is processed by Analytics Nodes and committed to VPX Protocol.

Capabilities

Engineered for network scale

01RFC 3261

SIP Gateway

Full SIP (RFC 3261) gateway with TLS transport. Connects to any SIP-capable switch, softswitch, or session border controller. No proprietary integration required.

02

H.323 Gateway

H.323 (H.225/H.245) to VPX Protocol translation. Connects H.323 networks and legacy switches directly to the VPX blockchain layer - supporting carriers with existing H.323 infrastructure.

03

SMPP SMS Gateway

SMPP v3.4 gateway for SMS traffic. Connects SMS aggregators and carrier SMS platforms to VPX Network routing, fraud validation and analytics.

04No forklift

Zero-Forklift Integration

Connect existing SIP trunks, H.323 gateways, or SMPP binds to the VPX Network with no changes to existing switch configuration. The Gateway Node handles all protocol translation.

05

Signalling-Only Processing

Gateway Nodes process signalling only - not media. Voice media flows directly between endpoints. This minimises latency, eliminates media transcoding and preserves existing carrier media paths.

06

Multi-Carrier Multiplexing

A single Gateway Node can serve multiple carrier interconnects simultaneously - acting as a shared infrastructure resource for smaller carriers who don't need dedicated node capacity.

Technical Specs

Under the hood

Voice ProtocolsSIP (RFC 3261, TLS) · H.323 (H.225/H.245)
SMS ProtocolSMPP v3.4
Media HandlingSignalling-only (media flows direct between endpoints)
Concurrent CallsUp to 100,000 concurrent sessions per node (hardware-dependent)
Translation Latency<5ms additional latency vs. direct interconnect
CodecsG.711a/u · G.729 · G.722 · AMR (passed through, not transcoded)
CDR SubmissionReal-time · Per-call · Signed · To Analytics Nodes
Minimum Node StakeSee current staking portal for requirements
Integration

Your existing interconnect, VPX-powered

Gateway Nodes connect via standard SIP, H.323 and SMPP - the same protocols your team already operates. No new skills, no new hardware, no forklift upgrade.

SIP trunk (RFC 3261)
H.323 peering
SMPP v3.4
TLS signalling
SRTP media path
CDR submission API
Node management portal
Real-time monitoring feed
Use Cases

Who participates in these nodes

Wholesale Telecoms

H.323 Carrier

Connect your H.323 network to the VPX Ecosystem via a Gateway Node without replacing your existing switch infrastructure. Access decentralised routing, fraud blacklists and analytics immediately.

VoIP / UCaaS

SIP Carrier / VoIP Provider

Point an existing SIP trunk at a Gateway Node to connect to the VPX Network. No configuration changes on your switch. Access VPX routing intelligence and fraud protection from day one.

Infrastructure

Gateway Node Operator

Operate Gateway Nodes to earn routing and CDR submission fee redistribution. Provide interconnect services to smaller carriers who share your Gateway Node capacity.

Join the Ecosystem

Ready to participate in Gateway Nodes?

Our VPX team typically responds within 48 business hours. Full whitepaper available for registered participants.

Get in Touch