VoIP Infrastructure Guide

SIP Trunking vs PRI — Migration Guide

8 min read  ·  Updated April 2026

PRI (Primary Rate Interface) has been the enterprise voice backbone for decades. SIP trunking delivers the same PSTN connectivity over IP at lower cost with more flexibility. Here is a technical comparison and a practical migration path.

In this guide

1. SIP trunking vs PRI — key technical differences

FeaturePRI (ISDN)SIP Trunking
TransportPhysical T1/E1 copper circuitIP network (internet or MPLS)
CapacityFixed: 23 B channels (T1) or 30 (E1)Elastic: scales with concurrent calls
SignalingQ.931 (ISDN D channel)SIP (RFC 3261)
Audio qualityG.711 64kbps PCMG.711, G.729, G.722, Opus
FailoverManual — order backup circuitAutomatic DNS SRV or secondary trunk
Provisioning time2-6 weeks (physical install)Minutes to hours
Number portingSlow, carrier-dependentFaster, more carriers
EncryptionNone (physical security)TLS + SRTP available
Geographic flexibilityTied to physical locationAny internet-connected location

The fundamental shift: PRI is circuit-switched (dedicated bandwidth per call), SIP is packet-switched (shared bandwidth, elastic capacity). This makes SIP more cost-effective for businesses with variable call volumes but requires QoS to guarantee voice quality on shared networks.

2. Cost comparison

Typical cost comparison for a 23-channel T1 PRI equivalent:

Cost ComponentPRI (T1)SIP Trunking
Monthly line cost$400-800/month$20-100/month
Per-minute ratesBundled or $0.01-0.03/min$0.005-0.015/min
Hardware requiredT1 card + PRI gatewaySBC (or software)
Installation$500-2000 + tech visitSelf-service or minimal
Contract2-3 year typicalMonth-to-month common

Most businesses save 40-60% on monthly telecom costs switching from PRI to SIP. The savings are highest for businesses with variable call volumes — PRI charges for unused channels, SIP only charges for calls made.

3. Migration steps and planning

  1. Audit current PRI usage — concurrent call peak, average call volume, DIDs in use, fax lines, alarm lines
  2. Check PBX SIP support — confirm your PBX supports SIP trunking. Older Nortel/Avaya/Mitel systems may need a gateway or upgrade
  3. Assess network readiness — measure internet bandwidth, latency to carrier, and implement QoS before cutover
  4. Choose SIP carrier — evaluate based on call quality, E911 support, number porting, and contract terms
  5. Deploy SBC if needed — for CUCM, older PBX, or where TLS/SRTP is required
  6. Port numbers — initiate LNP (Local Number Portability) — allow 2-4 weeks
  7. Run parallel — keep PRI active while testing SIP. Route outbound calls to SIP, keep PRI for inbound until porting completes
  8. Cut over — once number porting confirms and SIP testing passes, deactivate PRI

Special considerations

4. PBX compatibility and codec considerations

PBX SIP trunk support

PBX PlatformSIP Trunk SupportNotes
AsteriskNativechan_sip or PJSIP
FreeSWITCHNativeSofia SIP gateway
Cisco CUCMNativeSIP trunk + SBC recommended
3CXNativeBuilt-in SIP trunk wizard
Avaya AuraVia SBCSBC required for most SIP trunks
Mitel MiVoiceVersion dependentNewer versions support SIP natively
NEC SV9100NativeSIP trunk license required

Codec matching

PRI uses G.711 exclusively. SIP trunks offer G.711, G.729, and potentially G.722 or Opus. For direct PRI replacement, use G.711 (PCMU/PCMA) on the SIP trunk — same quality, same bandwidth, no transcoding. G.729 reduces bandwidth but introduces slight quality reduction compared to PRI audio.

5. Common PRI to SIP migration issues

Issue 01
One-way audio after migration
NAT issue — the PBX was not configured for SIP NAT traversal because PRI doesn't require it. After migration, the PBX advertises its private IP in the SDP. Fix: configure external IP in PBX SIP transport settings, disable SIP ALG on router, optionally deploy SBC.
Issue 02
Fax failures
Analog fax over SIP G.711 often fails due to timing sensitivity. Enable T.38 fax relay on both the SBC and PBX. If T.38 is not available, use a dedicated cloud fax service (eFax, Fax.Plus) for reliability.
Issue 03
Call quality worse than PRI
Internet path to SIP carrier has insufficient quality. PRI quality was guaranteed by dedicated circuits — SIP quality depends on network path. Implement QoS (DSCP EF marking), check jitter and packet loss to carrier endpoints, and consider dedicated internet access or MPLS for high call volume sites.
Issue 04
Number format mismatch
PBX dialplan expects 4-digit extension DIDs but SIP carrier delivers full E.164 (+12025551234). Create translation patterns or inbound route rules to strip the trunk prefix and route to extensions. Update auto-attendant number matching.

6. Testing and cutover checklist

Before deactivating PRI, verify on the SIP trunk:

Frequently asked questions

What is the difference between SIP trunking and PRI?

PRI (Primary Rate Interface) is a physical T1/E1 circuit delivering 23 or 30 fixed voice channels using ISDN Q.931 signaling. SIP trunking delivers PSTN connectivity over IP using the SIP protocol with elastic capacity that scales with concurrent call demand. SIP trunks typically cost 40-60% less than PRI, provision in hours instead of weeks, and support encryption — but require network QoS to match PRI call quality.

How do I migrate from PRI to SIP trunking?

Migrate from PRI to SIP in stages: audit current PRI usage (channels, DIDs, fax lines), confirm PBX SIP support, assess network quality and implement QoS, choose a SIP carrier, initiate number porting (2-4 weeks), run parallel with PRI active while testing SIP, then cut over once porting completes and testing passes. Keep PRI active for inbound calls until number porting fully completes.

Will my fax lines work on SIP trunking?

Standard analog fax over SIP G.711 is unreliable due to timing sensitivity. For reliable fax over SIP, use T.38 fax relay — both your SBC/PBX and the SIP carrier must support T.38. If T.38 is not available, migrate fax lines to a dedicated cloud fax service. Security alarm and elevator lines require analog POTS lines or ATA adapters — they cannot run directly on SIP trunks.

Migrating from PRI to SIP or troubleshooting your new SIP trunk?

Paste your SIP trace into SIPSymposium. The analyzer identifies NAT issues, codec mismatches, number format problems, and call quality issues common in PRI-to-SIP migrations.

Analyze my trace Create free account
Related guides