RingCentral does not sell SIP trunking. It is a UCaaS platform: RingEX bundles the phone system, the numbers, and the calling into one per-seat cloud subscription — $20–$35 per user per month billed annually as of August 2026 — and its acceptable-use policy expressly forbids trunking or forwarding RingCentral numbers to a PBX. The search term describes a product the company deliberately doesn’t offer.
If you typed “RingCentral SIP trunk” into a search bar, you almost certainly want one of three specific things — and RingCentral’s product pages answer none of them head-on. This guide does, quoting the company’s own published documents throughout.
The three things “RingCentral SIP trunk” searchers actually want
Intent one: connect an existing PBX or dialer to RingCentral as the carrier. You own a 3CX, FreePBX, Asterisk, or VICIdial box and want RingCentral to carry its calls the way a trunk provider would. This is the one RingCentral explicitly prohibits — the policy language is quoted in full below.
Intent two: trunk-style pricing. You’ve seen metered per-minute rates elsewhere and want to know whether RingCentral sells capacity that way instead of per-seat licenses. It doesn’t: every published RingEX price is per user per month, calling bundled in.
Intent three: “RingCentral BYOC.” RingCentral does publish a real BYOC program — its Bring Your Own Carrier service description covers connecting your existing local voice carrier’s PSTN service into RingEX’s cloud PBX, aimed at multinational deployments in countries where RingCentral lacks native PSTN coverage, with its own emergency-calling and availability limits. Note the direction: your carrier feeds their cloud PBX. It is the inverse of what trunk shoppers usually want — RingCentral selling you a SIP trunk for a PBX or dialer you control, which it does not offer.
What RingCentral actually sells
RingEX is a cloud phone system sold in three per-seat tiers. Published pricing as of August 21, 2026:
| Plan | Annual billing | Monthly billing | Bundled usage |
|---|---|---|---|
| Core | $20/user/mo | $30/user/mo | Unlimited domestic calling, 100 toll-free min, 25 SMS/user/mo |
| Advanced | $25/user/mo | $35/user/mo | 1,000 toll-free min, 100 SMS/user/mo |
| Ultra | $35/user/mo | $45/user/mo | 10,000 toll-free min, 200 SMS/user/mo |
Two footnotes matter for outbound-heavy buyers. SMS requires registering with The Campaign Registry before messages flow, and high-volume SMS is metered separately, starting at $0.0119 per message. Neither is unusual — TCR registration is an industry-wide requirement — but both sit outside the flat per-seat price.
That model is coherent on its own terms. An office team gets phones, apps, meetings, and calling as one predictable line item, with no PBX to run. The per-seat bundle is the product; the trunk is an internal detail RingCentral keeps to itself.
RingCentral’s outbound rules, in its own words
The clearest evidence that RingCentral isn’t a trunk provider is its Acceptable Use Policy. Section B prohibits, verbatim:
“Perform auto-dialing or ‘predictive dialing’; trunk or forward your RingCentral phone or fax number to other numbers that handle multiple simultaneous calls or to a private branch exchange (PBX) or a key system; or use the Services in any way that is inconsistent with typical human operation, including automate use of the RingCentral RingEX Services (e.g. use of desktop automation software or similar tools) …”
Read that as three separate walls. No predictive or auto-dialing. No trunking RingCentral numbers into a PBX or key system. No automation that departs from “typical human operation.” That isn’t fine print to route around — it’s the product boundary. RingEX seats are engineered and priced for humans placing human volumes of calls, and the policy protects that assumption.
This is worth stating without any bashing: their model fits distributed office teams that want zero telecom operations. Dialer traffic — thousands of short-duration attempts per agent per day — needs a carrier relationship that is built for it, priced for it, and contractually permits it.
The two paths from here
Once you know the product boundary, the decision collapses into two honest options.
Path one: stay inside RingCentral’s world
If what you really wanted was to keep your existing SIP hardware, RingCentral accommodates that — for phones, not PBXes. Per RingCentral’s support documentation, third-party BYOD deskphones can be registered onto RingEX: it publishes an overview for provisioning third-party phones, instructions for getting SIP settings for manual provisioning, and manual provisioning guides for brands like Yealink and Mitel.
The distinction matters. A deskphone registering to RingCentral’s cloud is an endpoint on their platform, still licensed per seat and still governed by the AUP above. It is not a trunk. Your call control, routing, and policies all live in RingCentral’s cloud, and that is the point of the product.
Path two: a real SIP trunk from a carrier
If intent one or two brought you here — your own PBX or dialer, capacity priced by usage — you want an actual trunking provider. What SIP trunking is and how it works is covered in our explainer; the short version is that a trunk delivers calls to equipment you control, and three things change immediately:
- Pricing flips from per-seat to per-use. You stop paying $20–$45 per user for bundled calling and start paying for trunks, numbers, and minutes. Our SIP trunk pricing guide shows how to compare those rates honestly, including billing increments.
- The PBX or dialer is yours. Routing, recording, IVR, and campaign logic run on your platform — with the operational responsibility that comes with owning it.
- Signing and attestation become a conversation you can have. On a trunk from an FCC-licensed carrier like SIPNEX, which signs outbound calls with its own STIR/SHAKEN certificate at A-level attestation, you can ask directly how your calls get signed and why the level matters. Inside a UCaaS seat, that layer is invisible to you.
Our SIP trunking service page covers what carrier-direct trunking looks like in practice.
When each one is right
Choose RingCentral-style UCaaS when the seats are humans having conversations: sales offices, distributed teams, professional services. The bundled price is predictable, there is nothing to host, and the AUP restrictions will never touch how you actually use the phones.
Choose a SIP trunk when you own the platform or the traffic profile is automated: a PBX you intend to keep, a contact center, or any predictive-dialer operation — which RingCentral’s acceptable-use policy excludes by design, as shown above. The broader architectural trade-off between renting the platform and owning it is mapped in our hosted PBX vs. SIP trunking comparison — this page won’t re-litigate it.
The one wrong answer is the hybrid people search for: forcing trunk-shaped traffic through seat-shaped service. The policy forbids it, and the per-seat economics were never built for it.
Frequently asked questions
Does RingCentral offer SIP trunking?
No. RingCentral sells RingEX, a per-seat cloud phone system ($20–$35/user/mo billed annually as of August 2026); no SIP-trunk product appears on its site, and its acceptable-use policy expressly prohibits trunking or forwarding RingCentral numbers to a PBX or key system. If you need a trunk for equipment you control, buy one from a carrier that sells trunks.
Can I connect my own PBX or dialer to RingCentral?
Not as a trunk destination. RingCentral’s acceptable-use policy bars auto-dialing, “predictive dialing,” and trunking its numbers to a PBX. What it does support, per its own documentation, is registering third-party BYOD SIP deskphones — individual endpoints, still licensed per seat — onto RingEX. A PBX or dialer needs a SIP trunking carrier instead.
What does “RingCentral BYOC” actually get you?
The inverse of a trunk purchase. RingCentral’s BYOC service description (verified August 2026) lets you connect your existing local carrier’s PSTN service into RingEX’s cloud PBX — built for multinational deployments where RingCentral lacks native coverage, with emergency-calling and country-availability limits. Your carrier feeds their PBX; RingCentral still doesn’t sell a SIP trunk for a PBX or dialer you control.
Is a SIP trunk cheaper than RingCentral?
For usage-heavy operations, usually — but they price different things. RingCentral bundles calling into per-user seats — $20–$45/user/mo depending on tier and billing — which suits ordinary office volumes. A trunk prices trunks, numbers, and metered minutes, so cost tracks traffic instead of headcount. High-volume outbound floors generally come out ahead on metered trunking; a ten-person office making occasional calls often doesn’t.
Keep reading.
The carrier built by operators, for operators.
FCC-licensed carrier with its own STIR/SHAKEN SP certificate. Operator-owned. SIP trunks built for operators who dial at volume.