Classify BYOC before comparing it with a carrier trunk
RingCentral's current service description calls BYOC software as a service for multinational customers. RingCentral supplies RingEX cloud-PBX capabilities, while the customer provides its local telecommunications carrier and purchases and owns the gateway through which PSTN calls travel. RingCentral expressly says it is not the voice or VoIP provider for that local service.
That ownership split is the starting point for selection and incident handling. Record the RingCentral tenant and Home Country, BYOC location, local carrier, carrier order, gateway model and software, access supplier, numbers, emergency owner and support contacts. Do not score RingCentral marketing as proof of the carrier-facing trunk.
Documented service facts
Reviewed 2026-10-09. Compare SIP trunk services →
SIP authentication
Not verifiedRingCentral's public service description identifies a customer-owned gateway between the local carrier and RingEX, while the support page says an account manager enables BYOC parameters and adds or changes gateways. The reviewed public pages do not define one universal source-address, digest, certificate, realm or mutual-trust profile. Preserve the approved design, exact gateway, each peer, certificate or secret owner and a sanitized successful exchange without copying another carrier or country configuration.
SIP registration
Not verifiedThe reviewed BYOC pages do not establish whether the RingCentral-facing or carrier-facing leg uses REGISTER, static peering, a certified SBC profile or another method for the selected deployment. Do not invent a registrar, Contact lifetime, qualification timer or connected indicator. Record each leg independently and distinguish a configured gateway from a reachable peer and an accepted call.
Inbound delivery
DocumentedRingCentral says all PSTN calls travel over the customer's local carrier through a customer-purchased and customer-owned gateway, and its support workflow lets the account manager add or change carrier phone numbers. That establishes the ownership path, not a delivered Request-URI, asserted identity, normalization, port state or destination. Retain the carrier order, RingEX assignment, gateway trace and answered destination as separate evidence.
Routing and failover
Not verifiedThe public overview describes phased migration and rollback flexibility, but the reviewed pages do not publish one customer's alternate gateway, carrier reroute, DNS behavior, health trigger, route priority, timer, access diversity, established-call treatment or restoration order. Migration rollback is not automatic call failover. Document and exercise the accepted new-call continuity design across RingEX, gateway, access and carrier failure domains.
Number and regional availability
DocumentedBYOC depends on an existing local-carrier relationship and a RingCentral-supported BYOC location. RingCentral's August 2026 release notes added Iceland and Bahrain, showing that country availability changes over time. A country announcement does not prove a requested address, number, port, carrier interconnect, emergency route or license is orderable. Obtain a dated qualification for every site and keep the Home Country requirement in the accepted order.
Audio codecs and DTMF
Not verifiedThe reviewed BYOC service, support and release pages do not publish a complete codec, packetization, DTMF, early-media, transcoding or media-address profile for the selected RingCentral-facing and carrier-facing legs. Obtain the current implementation handoff, preserve both SDP exchanges and any gateway translation, and validate decoded digits and two-way audio on the actual route.
T.38 fax
Not verifiedRingEX includes fax capabilities in its broader service portfolio, but the reviewed BYOC records do not establish T.38 or audio-fax entitlement, direction, switchover, redundancy, gateway and carrier compatibility or completed pages for a BYOC number. Treat fax, alarms and other non-voice devices as separate workflows with current RingCentral, gateway and carrier evidence.
Signaling and media encryption
Not verifiedThe BYOC service description says RingCentral is not responsible for the performance, security or availability of the local carrier service or customer gateway. The reviewed pages do not define a universal SIP TLS, certificate-validation, SRTP, keying or protected-leg profile for BYOC. Record signaling and media protection separately on the RingCentral-facing and carrier-facing legs and do not represent the complete PSTN path as end-to-end encrypted.
Concurrent calls and call starts
Not verifiedThe reviewed pages do not publish a universal BYOC simultaneous-call entitlement, calls-per-second limit, burst policy, gateway session count or carrier channel limit. Size RingEX licensing, carrier capacity, gateway sessions and transcodes, access bandwidth, firewall state and emergency reserve separately. A configured carrier number or gateway is not proof of accepted load.
Emergency calling
DocumentedRingCentral's BYOC service description says emergency calling may not be available in every country, custom solutions in countries without enabled local dialing may not connect emergency calls, and customers must provide alternative arrangements. It also says local dialing is unavailable in countries not formally launched. Confirm country, number, location, local-carrier route, callback identity, notifications and the provider-approved validation method; retain an independently powered alternative.
Pricing model
Not verifiedBYOC combines RingEX software, the customer's local-carrier service and a customer-purchased gateway. Public RingEX tiers do not establish the selected BYOC total. Bind user licenses, BYOC add-ons, carrier numbers and usage, gateway and support, access, implementation, taxes, term, renewal and termination to current RingCentral and carrier orders and invoices.
Administration and support
DocumentedRingCentral's support page directs customers to their account manager to enable BYOC parameters and add, change or remove gateways and carrier phone numbers. The legal description assigns the local carrier service and gateway to the customer and carrier rather than RingCentral. Maintain a responsibility matrix for RingEX, carrier, gateway, numbers, certificates or secrets, network, emergency records, monitoring, escalation and rollback.
SMS and MMS
Not verifiedRingCentral markets messaging in the RingEX application and its August 2026 release notes describe country-specific SMS licensing, but the reviewed BYOC pages do not establish SMS or MMS eligibility on every carrier-provided number, sender registration, API access, throughput, retention or price. Qualify messaging separately for the exact number, country, license and carrier route.
Treat every interface as its own acceptance boundary
The public support workflow says the RingCentral account manager enables BYOC parameters and adds or changes gateways and carrier numbers. It does not publish one universal authentication, REGISTER, static-peering, codec, DTMF, fax, TLS, SRTP or call-start profile for every BYOC deployment.
Obtain the current implementation handoff. Accept the carrier-to-gateway and gateway-to-RingCentral legs separately: peer or registration state, inbound delivery, outbound identity, offer and answer, two-way media, digits and hangup. A number visible in RingEX or a gateway saved by an account manager is configuration evidence, not a completed call.
Keep country release, carrier serviceability and number state separate
BYOC depends on an existing local-carrier relationship and on RingCentral having launched the relevant dial plan and capability. The August 2026 release notes added Iceland and Bahrain, demonstrating that the list changes. The legal description also ties BYOC to services purchased in the customer's Home Country.
For every site, preserve a dated RingCentral qualification and separate carrier records for service address, number inventory, portability, activation, local and international dialing, caller identity and regulatory eligibility. A RingCentral country announcement does not prove that a number or emergency route is available from the selected carrier.
Build continuity across four owners
The service crosses RingEX, the customer gateway, network access and the local carrier. RingCentral's overview describes phased migration and rollback flexibility, but that is not an automatic failover design. The reviewed public pages do not establish alternate gateways, carrier rerouting, access diversity, health timers, route priority, established-call survival or restoration.
Write one responsibility and failure-domain map. Then validate approved new-call cases in both directions, preserving the failure stimulus, observed route and restoration result. Keep RingCentral service status, gateway health, internet reachability and carrier trunk state as independent signals.
Close emergency calling per country and location
RingCentral's BYOC service description says emergency calling may not be available in all countries. Custom solutions in countries where local dialing has not been enabled may not connect an emergency call, and customers must provide alternative arrangements. The broader RingEX attachment also requires an alternative means of reaching emergency services for Global RingEX.
Before activation, confirm the country, exact carrier number, validated location, gateway route, callback identity, internal notification, outage behavior and permitted validation method. A saved emergency response location or a generally available dial plan does not prove that this BYOC path is dispatch-ready.
Join the commercial and operational records without merging them
The selected service combines RingEX licensing, BYOC enablement, a customer-owned gateway, local-carrier numbers and usage, connectivity, implementation and support. Public RingEX pricing does not establish that total, and RingCentral's legal boundary leaves local-service performance, security and availability with the customer and carrier.
Retain both current orders and invoices, named escalation paths, certificate and secret owners, gateway lifecycle, monitoring, changes and rollback. Qualify SMS, MMS, fax and non-voice devices separately for the exact country, number and carrier; application features elsewhere in RingEX do not automatically extend to every BYOC number.
Sources & applicability
Primary references for the technical details above. Operational examples and planning checklists are VoIP.info editorial guidance.
- RingCentral BYOC service description ↗
- Manage RingCentral BYOC gateways and carrier numbers ↗
- RingCentral BYOC overview ↗
- RingEX Core release notes — August 2026 ↗
- RingEX service attachment ↗
- RingCentral BYOC launch announcement ↗
Examples require adaptation to your topology. No live PBX or hardware testing is claimed.