OpenVox wireless gateways connect GSM, WCDMA, LTE, and SMS services with SIP-based communications, giving service providers, enterprises, and managed communication platforms a practical cellular access layer for voice and messaging.
SWG and GWP share the same gateway system, feature set, and API capability. The selection comes down to hardware architecture, rack density, expansion requirements, and SIM card management.
GWP uses a modular chassis architecture for projects that need serviceable hardware modules and a more flexible expansion path.
SWG uses an integrated appliance structure for deployments that want simpler hardware, fixed capacity, and a compact rack installation.
SWG provides higher rack density for projects that need more wireless ports in limited rack space, while GWP prioritizes modular capacity planning.
SWG supports one wireless port mapping to four SIM cards, enabling larger SIM pools for carrier selection, SIM rotation, and traffic policy needs.
Both series belong to the OpenVox wireless gateway portfolio. Choose SWG for integrated appliance density and multi-SIM switching, or GWP for modular chassis expansion.
Integrated appliance series
A compact integrated wireless gateway line for deployments that need fixed appliance capacity, higher rack density, and advanced SIM allocation options.
Choose SWG when the deployment values compact appliance hardware, high 1U density, and multi-SIM allocation more than field expansion.
Modular VoxStack series
A modular wireless gateway chassis line for projects that need plug-in hardware planning, serviceable expansion, and more flexible growth over time.
Choose GWP when the deployment values modular chassis planning, serviceable expansion, and long-term hardware flexibility.
SWG and GWP are two hardware paths within the OpenVox wireless gateway portfolio. They share the gateway system, core calling and messaging functions, routing and management workflows, and API capability set.
Same wireless gateway system for calling, messaging, routing, and device management
Aligned SMS, USSD, routing, remote management, and API workflows across both series
Series selection is driven by hardware architecture, density, SIM strategy, and expansion model
Wireless VoIP gateways sit between mobile networks and IP communications infrastructure. They convert wireless channels into SIP-accessible resources, so teams can route mobile voice traffic, operate SMS workflows, and manage cellular connectivity through gateway software.
The table below summarizes shared software capabilities and the hardware differences that should drive series selection.
| Specification | SWG Series | GWP Series |
|---|---|---|
| Shared Software Platform | ||
| Software platform | Unified wireless gateway software platform | |
| Feature list | Voice, SMS, USSD, routing, management, and monitoring | |
| API | HTTP SMS API and management API workflows | |
| Web UI | Web-based gateway management interface | |
| Hardware Architecture | ||
| Hardware design | Integrated appliance with simpler, more compact hardware | Modular chassis with more flexible expansion planning |
| Expansion model | Fixed integrated structure; users do not expand it themselves | Plug-in modular structure for more flexible hardware growth |
| Hardware complexity | Simpler hardware structure with better cost efficiency | More complex modular structure for flexible expansion |
| 1U port density | Up to 32 ports in 1U | Up to 20 ports in 1U |
| Maximum capacity | Up to 32 ports and 128 SIM cards in 1U | Up to 20 ports and 20 SIM cards in 1U |
| SIM card switching | Supports 1 port to 4 SIM cards; 32 ports can map to up to 128 SIM cards | Standard modular SIM layout; no 1-port-to-4-SIM switching model |
| Typical selection reason | Compact deployment, higher rack density, fixed capacity, and multi-SIM switching | Modular expansion, serviceable hardware planning, and flexible growth |
Start with SWG when the project needs compact integrated density and multi-SIM switching. Start with GWP when modular hardware expansion and long-term hardware flexibility are the priorities.
