SIP Trunking Services: Cost, Bandwidth and Compliance
Copper phone lines in the US are being switched off on a carrier timetable. The FCC streamlined that process in March 2026. SIP trunking services are the standard replacement for PRI and analog lines. The decision now carries a date, set by the carrier rather than the buyer. Vendor guides on this topic rarely mention that timetable.
Three questions decide the purchase: bandwidth, cost, and emergency calling. SIP trunking providers price the same service in two different ways. Bandwidth depends on codec and concurrency, which is simple arithmetic. Emergency calling is governed by federal rules with fixed compliance dates. Each is answered below with the numbers and statutes named.
What Are SIP Trunking Services?
SIP trunking services replace physical voice circuits with a connection over IP. SIP stands for Session Initiation Protocol, defined in RFC 3261. The protocol sets up, modifies, and ends each call session. Voice audio itself travels separately over RTP. The trunk terminates calls onto the PSTN.
A trunk is provisioned with numbers and a channel count. DID numbers give each extension a dialable outside number. Those numbers follow the E.164 international format. Caller ID presentation is configured per trunk or per number. A business VoIP platform can replace the PBX entirely instead.
A SIP trunk requires a phone system capable of SIP signaling. IP PBX platforms such as FreePBX and 3CX support it natively. Legacy TDM systems need a gateway to convert signaling. Without a PBX worth keeping, a trunk is the wrong purchase. That scenario points to a hosted platform instead.
A provisioned trunk typically includes:
Concurrent call channels, provisioned as a trunk group
DID number ranges and number blocks
Inbound and outbound call routing rules
Caller ID and CLI presentation control
Emergency call routing with a registered location
Fax support over T.38 where offered
Call detail records for usage reporting
Failover destinations for outage conditions
Why Are US Businesses Replacing Copper Lines Now?
Interconnected VoIP passed 79% of US retail fixed voice connections by December 2024. That share was 58% in 2018, according to FCC reporting. Switched-access lines fell to 15.0 million by June 30, 2025. That count has declined about 17.9% per year since mid-2022. These are FCC-measured figures, not industry forecasts.
The FCC adopted Report and Order 26-19 on March 26, 2026. It streamlined copper retirement and legacy service discontinuance. Carriers discontinuing voice no longer must offer a standalone replacement. A bundled alternative now satisfies that obligation. AT&T grandfathered copper voice ordering across 18 states on October 15, 2025.
Grandfathering stops new orders before it stops existing service. Retirement notices then set the migration window for affected lines. Elevator, alarm, and fire-panel lines are affected alongside desk phones. Voice quality then depends on the business internet provider underneath. Replacing voice without reviewing that circuit moves the problem rather than solving it.
SIP Trunk vs PRI vs Hosted PBX: Which One Fits?
The SIP trunk vs PRI question is about capacity and billing granularity. One North American T1 PRI carries 23 bearer channels plus 1 signaling channel. That fixes capacity at 23 concurrent calls per circuit. A SIP trunk adds or removes channels without new physical circuits. A hosted PBX replaces the phone system itself, not just the lines.
Existing numbers move to the new trunk through number porting. FCC local number portability rules require carriers to support that transfer. Simple ports complete faster than ports involving many numbers or circuits. Porting is requested from the gaining carrier, not the losing one. Service should not be cut over before the port confirms.
Failover routing is the capability a PRI cannot match. Calls can divert to a mobile number or an alternate site. A PRI outage simply stops calls at the circuit. The SIP trunk vs PRI comparison therefore includes continuity, not only price. A hosted PBX suits businesses with no PBX worth retaining.
A migration runs in seven steps:
Audit current lines, channel usage, and peak concurrency
Confirm the PBX supports SIP, or specify a gateway
Size bandwidth from codec and concurrent call paths
Order the trunk and register emergency locations
Submit the port request to the gaining carrier
Test inbound, outbound, and 911 calls before cutover
Cut over, then decommission the legacy circuit
How Much Bandwidth Do SIP Trunking Services Need?
SIP trunking bandwidth requirements follow two variables only. Those variables are the codec and the number of concurrent call paths. Ten simultaneous calls need ten channels of capacity. Channel count should be sized to peak concurrency, not to headcount. Erlang B calculations convert call volume into required channels.
The G.711 codec uses 64 kbps of payload in each direction. IP, UDP, RTP and Layer 2 overhead raise that in practice. A planning figure of 100 kbps per concurrent call covers that overhead. G.729 compresses to 8 kbps payload, roughly 32 kbps with overhead. SIP trunking services carry either codec, subject to provider support.
Ten concurrent G.711 calls therefore need 1 Mbps in each direction. Adding 20% to 30% headroom brings that to roughly 1.3 Mbps. SIP trunking bandwidth requirements are symmetric, because calls send and receive. Jitter and packet loss degrade calls even when raw bandwidth is sufficient. A dedicated internet access circuit with QoS protects voice traffic.
SIP Trunking Security and E911 Compliance
SIP trunking security rests on encryption and a controlled network edge. A session border controller sits between the trunk and the internal network. It enforces policy, hides topology, and normalizes SIP signaling. TLS encrypts the signaling, and SRTP encrypts the media stream. Unencrypted trunks expose call content and registration credentials.
Toll fraud converts a compromised trunk into billable international calls. Attackers use stolen SIP credentials to dial premium-rate international destinations. International dialing restrictions and per-trunk call caps limit the loss. IP access control lists restrict which hosts may register. Providers differ on whether fraud losses are credited back.
E911 compliance is a federal obligation, not a provider feature. Kari’s Law requires direct 911 dialing without a prefix on multi-line systems. RAY BAUM’S Act Section 506 requires a dispatchable location with each call. Both sit in 47 CFR Part 9, Subpart F. Fixed systems compiled from January 6, 2021, non-fixed from January 6, 2022.
How Much Do SIP Trunking Services Cost?
SIP trunking cost follows one of two billing models. Per-channel pricing charges a flat monthly fee for each concurrent call path. Metered pricing charges per minute, with no channel fee. SIP trunking services with steady, predictable volume suit per-channel billing. Variable or bursty traffic costs less on metered billing.
Published channel rates cluster between $15 and $30 monthly for unlimited domestic calling. Telnyx publishes lower tiers on its own rate card. Its inbound channels run $12 monthly for the first ten. That falls to $8 per channel above 250 channels. SIP trunking cost at that tier reflects volume, not a standard retail price.
SIP trunking providers publish per-minute rates that differ by direction. Telnyx lists $0.005 outbound and $0.0032 inbound for the US. Twilio Elastic SIP lists $0.01 outbound and $0.0034 inbound. Bandwidth, the carrier, lists $0.01 outbound and $0.0055 inbound. These are list rates from September 2026 and change with volume tiers.
Telnyx lists emergency calling at $1.50 per number monthly.
Conclusion
The copper timetable is set by carriers, so the migration window is finite. SIP trunking services replace the lines, but bandwidth and 911 obligations move with them. Sizing from codec and concurrency, then registering locations, prevents the common failures. Defend My Business provides these services, from provider selection through migration. The next step is auditing peak concurrency on the current circuit.
Comments
Post a Comment