Do not force one universal cutover
Separate endpoint, line, trunk and PBX work before selecting the migration path.
Move traditional voice to VoIP in phases.
Modernize traditional voice services in manageable stages. Identify whether devices, the PBX or carrier access is driving the change, then follow the migration path that fits each dependency.
The migration starting point
Different systems need different migration paths.
An estate may combine analog phones, fax machines, PSTN lines, E1/T1 trunks and a traditional PBX.
A useful migration plan inventories these dependencies, separates the required interface paths and sequences change according to operational risk and business priority.
Analog devices
Phones or fax machines must stay
Start with FXS access and endpoint validation.
Legacy PBXThe PBX remains during migration
Start with analog, digital or SIP coexistence.
ISDN / PSTNCarrier trunks are changing
Start with switch-off readiness and trunk replacement.
POTS serviceA single analog service must continue
Start with device-by-device POTS replacement.
Interface-led migration
Classify first, then migrate by interface.
Use iAG800 V2 for the analog transition path and DGW-L302 for the digital trunk path, then continue into the narrower workflow that matches the retained estate.
- 01Analog devices and lines
FXS, FXO and retained POTS roles
- 02Digital trunks
E1, T1 or J1 carrier boundaries
- 03Traditional PBXs
Existing systems selected for coexistence
- 04iAG800 V2 / DGW-L302
Analog and digital migration boundaries
- 05SIP / selected UCP core
Target calling environment and migration path
Match the real interface boundary
Use the mapped gateway role instead of treating all traditional voice as one interface.
Continue into the narrower solution
Use this page as the decision guide and keep execution in the specialist migration pages.
Use the OpenVox layer that matches each interface.
The final architecture may combine several product families as the estate moves from traditional voice to SIP.
Documented roles for legacy interfaces.
This page is a migration overview; detailed compatibility and capacity remain interface-specific assessments.
Analog endpoint access
OpenVox FXS gateways and modules connect supported analog endpoints to SIP.
Proof chips
- FXS
Analog line and PBX access
OpenVox FXO products connect analog PSTN and PBX interfaces to SIP.
Proof chips
- FXO
E1/T1/J1 interworking
DGW-L302 supports documented two-span E1/T1/J1 trunk and signaling options.
Proof chips
- DIGITAL
Target network connection
UCP supports standard SIP trunks for IP-PBX, softswitch and IMS environments.
Proof chips
- SIP
Move traditional voice services to a future-ready VoIP architecture.
Share devices, lines, trunks, PBXs, sites, carrier requirements and target systems. OpenVox can define the right gateway roles and validation sequence.