Primary Rate Interface (PRI) is a digital telephone service that carries many simultaneous calls over a single circuit. It is part of ISDN (Integrated Services Digital Network), a standard for digital phone lines, and was for decades the usual way to connect a business PBX to the public telephone network. A PRI is delivered on a T1 circuit with 23 voice channels in North America, or on an E1 circuit with 30 voice channels in Europe and most other regions, plus a channel for call signaling.
At a glance
- One PRI carries 23 (T1) or 30 (E1) simultaneous calls, each on a 64 kbps channel, plus one signaling channel.
- It connects an on-premises PBX to the carrier and supports caller ID and direct inward dialing (DID) number ranges.
- Capacity comes in whole circuits, so you pay for every channel whether you use it or not.
- Many carriers are reducing support for PRI and raising prices, and most new deployments use SIP trunking instead.
- Moving off PRI usually means SIP trunks for an existing PBX, or a hosted PBX or UCaaS service that replaces it.
What problem it solves
Before PRI, a business that wanted many outside lines needed many separate analog lines, each with its own wiring and limits on features. PRI put dozens of calls on one digital circuit with a dedicated signaling channel, which made features such as caller ID, DID number blocks and fast call setup reliable. Because each call had a reserved channel, quality was consistent and predictable.
That made PRI the standard trunk for mid-size and large phone systems, and it is still common in older PBXs, contact centers and sites where the phone system has not been replaced.
How it works
A PRI runs over a T1 (1.544 Mbps) or E1 (2.048 Mbps) circuit, usually delivered by the local carrier on copper or as a handoff from a fiber-fed device at the site. The circuit is split into fixed time slots:
- B (bearer) channels, each 64 kbps, carry the voice of one call.
- The D (data) channel carries signaling: who is calling, which number was dialed, and when the call starts and ends.
The PBX connects to the circuit through a PRI interface card. The carrier assigns a block of direct inward dialing (DID) numbers, so callers can reach individual extensions without an operator. Larger sites use several PRIs; some setups let multiple circuits share one signaling channel, freeing an extra voice channel on the others.
Because channels are fixed, a PRI cannot carry more calls than it has channels. Adding capacity means adding another circuit, with installation lead times, and a fault on the circuit can take all its calls down unless calls are routed to a backup.
When it matters for buyers
- When a carrier notice arrives about price increases, end of sale or migration of PRI service.
- When the PBX is being replaced, since the new system may not need PRI at all.
- When reviewing telecom spend. PRIs are often oversized for current call volumes, especially after staff moved to mobile and remote work.
- When resilience matters. A single PRI is a single point of failure; IP-based alternatives can spread calls across multiple paths and locations.
- When inheriting sites with undocumented PRIs, DID ranges and fax or alarm lines on the same system.
Questions to ask vendors
- What is your timeline for PRI support in our locations, and what happens to pricing in the meantime?
- How many concurrent calls do we actually use at peak, based on call records?
- Can our current PBX connect to SIP trunks directly, or do we need a gateway or upgrade?
- How will you port our DID ranges and main numbers, and how long will it take?
- How will emergency calls send the right address after the change?
- What redundancy and failover does the replacement service include?
- What devices behind the PBX (fax, alarm, paging, modems) need special handling?
How it differs from SIP trunking
SIP trunking does the same job, connecting a phone system to the public telephone network, but over an IP connection rather than a dedicated digital circuit. Capacity is usually sold per concurrent call or as a pool, so you can size it to actual use, and calls can fail over to other sites or carriers. The trade-off is that call quality depends on the IP network, so the connection needs enough bandwidth and quality controls. Many organizations moving off PRI keep their PBX and swap the PRI for SIP trunks; others replace the PBX with a hosted PBX or UCaaS service.
For a migration path, see our PRI replacement solution page.
Problems this helps with
- Our carrier is raising PRI prices or ending the service
- Paying for 23 call paths when we only use a few
- An old PBX that only connects to PRI
- Phones go down when the single circuit to the building fails
