Migrate from v1 to v2 trunking
Update your firewall for the v2 SBCs and media gateways, flip the trunk version in the portal, and point your PBX at the new SRV record.
Last updated August 6, 2026
Our v2 SIP trunking infrastructure launched in 2024 and most partners have already moved. The legacy v1 platform still runs, but we are asking remaining customers to migrate for call quality and to stay aligned with current security standards.
Do the firewall work first
If you flip the trunk version before your firewall allows the v2 endpoints, calls will stop. Complete the first step below before you touch the portal.
Allow signaling from the v2 SBCs
Permit SIP signaling on port 5060 from each of these v2 endpoints.
| SBC | IP address |
|---|---|
| Neptune | 38.86.50.6 |
| Venus | 38.86.50.14 |
| Saturn | 38.101.249.111 |
| Jupiter | 38.101.249.112 |
| Pluto | 38.97.55.242 |
| Future / reserved | 198.102.104.16/28 |
Allow media from the gateways
Whitelist the media gateways below, including the future and reserved ranges. These need open RTP traffic on UDP ports 9000 to 20000. Skipping the reserved ranges is the usual cause of one-way audio after a migration.
| Media gateway | IP address | Ports |
|---|---|---|
| Misti (legacy, winding down) | 74.208.82.47 | 9000 – 20000 |
| Triniti (legacy, winding down) | 70.35.200.179 | 9000 – 20000 |
| Capri | 38.101.249.3 | 9000 – 20000 |
| Kiki | 38.86.50.3 | 9000 – 20000 |
| Heidi | 38.86.50.9 | 9000 – 20000 |
| Destini | 38.97.55.241 | 9000 – 20000 |
| Future / reserved | 38.101.249.7/31 | 9000 – 20000 |
| Future / reserved | 38.86.50.7/31 | 9000 – 20000 |
| Future / reserved | 198.102.104.16/28 | 9000 – 20000 |
Flip the trunk version
- 1Sign in to the Wiretap Portal and go to Manage Trunks → Trunks.
- 2Select the trunk you are upgrading.
- 3Scroll to the Trunk Version section and flip the switch from version 1 to version 2.
- 4Press Save and wait for the trunk to re-provision. This can take up to two minutes.
Update your SRV record
Point your PBX at the v2 host. On 3CX, go to Voice & Chat, scroll to Server Details in the general settings, and enter srv.globalsbc.core-trunk.com in the Registrar/Server field. Press Save.
Legacy 3CX installations
On some older 3CX installs the Registrar/Server and Outbound Proxy fields are locked or hidden, so you cannot enter the new SRV record. In that case you have to rebuild the trunk from the v2 template.
- 1Capture your current settings before deleting anything — DID routing, caller ID, and E-911 configuration.
- 2Remove the legacy trunk from your 3CX management console.
- 3Add a new SIP trunk from the v2 template you imported.
- 4Configure and save. The template unlocks the necessary fields and fills in the v2 endpoints.
- 5Re-link your DIDs to their destinations: extensions, IVRs, or ring groups.
Stuck?
If you are not sure which template to use, or registration fails after the rebuild, call support on 816 WIRETAP (816-947-3827) or open a ticket in the support portal.
Still stuck?
Our help desk answers on 816 WIRETAP, or open a ticket. Including the right details gets you a real answer on the first reply — see submitting support tickets.
Contact support