Unified access and call control
Host the selected service modules, SIP control and approved application roles on the central platform.
Carrier Voice Interconnection & SIP Access
Bring carrier access, call control and selected voice applications into one governed SIP environment. Add each access type according to interface, capacity and operational ownership requirements.
Carrier access requirements
Bring access, call control and selected applications into one governed platform.
Carrier environments may combine E1/T1/PRI, PSTN, cellular, radio or audio trunks with SIP phones, software clients, paging and other endpoints.
UCP2120 provides the central modular platform. External gateways extend a specific access type only when capacity, placement or operational ownership sits outside the chassis.
External trunk gateway
Use GWP or DGW only where cellular or E1/T1 access terminates outside UCP2120.
External analog endpoint access
Use iAG rack or ATA products when retained FXS or FXO endpoints require an external boundary.
SIP endpoint and service layer
Keep routing, numbering, security and application ownership explicit for every connected endpoint.
Integrated provider access
Place UCP2120 at the center of access, control and applications.
UCP2120 can host the selected calling application and service modules, while external gateway families remain optional boundaries for digital, wireless, analog or ATA access.
- 01UCP2120
Unified access, call control and selected application platform
- 02Carrier networks
E1, T1, PRI, PSTN and approved cellular or audio access
- 03Optional access gateways
Wireless, digital, FXS, FXO or ATA boundaries
- 04SIP endpoints and applications
Phones, software clients, intercom and paging
- 05Provider operations
Routing, policy, security and service management
Make UCP2120 the primary platform
Define which access modules, calling applications and service roles run on the UCP chassis.
Add external gateways only when needed
Use a matching gateway family when capacity, location or interface ownership sits outside the UCP chassis.
Keep provider policy explicit
Confirm signaling, routing, security and operational ownership for every connected network.
Design from the handoff toward the service edge.
A provider deployment should document interfaces, signaling and capacity before gateway selection, then prove the complete call path under operating conditions.
Inventory access networks
Record digital trunks, cellular channels, analog endpoint counts, sites and ownership boundaries.
Map each gateway role
Assign DGW, SWG and UScale IAD only where their documented interfaces match the handoff.
Define the SIP service edge
Document addressing, registration, routing ownership and the softswitch or IMS relationship.
Validate signaling and routing
Test inbound, outbound, failover and restoration behavior for every approved access path.
Start with UCP2120, then add only the gateway families the edge requires.
Final selection follows module capacity, signaling, cellular standard, endpoint count, placement and the applications approved for the UCP platform.
Primary product
UCP2120
Unified carrier-access, call-control and application platform shown in the approved architecture
View productOptional when needed
GWP2120
External wireless access gateway family
Use when: Use when cellular access is delivered through an external gateway instead of UCP modules.
View productOptional when needed
DGW-L302
External E1, T1 or J1 digital access gateway
Use when: Use when digital trunks terminate on an external gateway.
View productOptional when needed
iAG800 V2
External FXS or FXO analog gateway family
Use when: Use when analog extensions or trunks terminate on a rack gateway.
View productOptional when needed
iAG200 FXS
ATA access for a small number of retained analog endpoints
Use when: Use only where a small endpoint group requires FXS ATA access.
View productA traceable role for the platform, modules and external gateways.
Application compatibility, carrier certification, operator approval, regional signaling and final capacity remain project-specific validation items.
Modular service platform
OpenVox documentation defines a 2U UCP chassis with two control-board slots and configurable service modules.
Proof chips
- UCP2120
Multiple telephony interfaces
UCP service modules and external gateways cover selected digital, analog, cellular, audio and radio access roles.
Proof chips
- ACCESS
Endpoint and application boundary
The architecture connects phones, software clients and selected applications through explicit SIP roles.
Proof chips
- SIP
Routing and security ownership
Provider routing, policy, security and management responsibilities remain explicit throughout the design.
Proof chips
- OPERATIONS
Map your carrier access edge with OpenVox.
Share trunk types, signaling, cellular standards, endpoint counts, application requirements and site ownership. OpenVox can help define the UCP2120 modules, optional gateways and validation plan.