Skip to content
KODA VOICE Talk to sales

Software platforms

A licensed carrier behind your software platform: bring your own carrier

Koda Voice is a licensed U.S. voice carrier that sits behind your product: bring your own carrier (BYOC). Your platform keeps its brand and customer relationship; Koda supplies the SIP trunk and the phone numbers, signs calls originated on its network under its own STIR/SHAKEN Service Provider Code (583H), and vets the platform and the businesses calling through it.

Talk to sales Verify our credentials

The model

What bring-your-own-carrier means for a software platform

Bring your own carrier (BYOC) means your platform contracts directly with a licensed carrier for the voice under your product, instead of the telephony bundled into a communications platform. Your customers see your brand; Koda Voice is the licensed carrier behind them.

Question Koda as your carrier (BYOC) Bundled telephony
Licensed carrier Koda Voice LLC, Operating Company Number (OCN) 583H Whoever the vendor contracts with
Signing certificate Koda's own STI certificate, issued under Service Provider Code 583H, for calls originated on Koda's network The vendor's, or its upstream carrier's
End-customer vetting Koda vets the platform; the platform identifies each business calling through it and produces the record on request The vendor, on its own terms
Number ownership Your Koda account; portable in and out Set by the vendor's terms
Cost statement Stated on the rate deck and order form Folded into the platform price

Chain of custody

Why does the carrier's own identity matter for your customers' calls?

The carrier's identity matters because a call carries the carrier's credentials, not the platform's. Under Federal Communications Commission (FCC) rules (47 CFR § 64.6305), providers accept calls directly from a domestic voice service provider only if its filing appears in the Robocall Mitigation Database (RMD). The Secure Telephone Identity Governance Authority (STI-GA) sets the policy under which the STI Policy Administrator (STI-PA), iconectiv, clears a provider for STI certificates: a current Form 499-A on file, an assigned Operating Company Number (OCN), and an FCC certification with an RMD listing (STI-GA Policy Decision 001). Those are carrier credentials.

Koda Voice holds all three: Form 499 filed with the Universal Service Administrative Company (USAC) under Filer ID 839032, OCN 583H assigned by NECA, and an RMD listing. Calls originated on Koda's network are signed under Koda's own Service Provider Code (583H), not a reseller's certificate. Attestation follows the STIR/SHAKEN attestation framework (ATIS-1000074): A when the customer is verified and authorized to use the number, B when the customer is verified but number authorization cannot be confirmed, C otherwise.

A platform that sells calling to its own customers is itself a voice service provider. Under the same FCC rule (47 CFR § 64.6305), it must certify its own originated calls in the RMD, and Koda may accept its traffic directly only if that filing appears in the database. Koda confirms the listing at onboarding; Koda's signature covers calls originated on Koda's network and does not stand in for a downstream provider's own certification.

Interconnection

How does Koda connect to your platform? SIP trunks, IP allow-lists, credentials

Koda connects to a platform over standard SIP in four steps.

  1. 01

    Describe the platform and its traffic

    What sends the calls, where they terminate, which numbers you present and the businesses behind them: the Know-Your-Customer review of the platform.

  2. 02

    Exchange trunk parameters

    IP allow-list or SIP digest credentials, codecs, DTMF method, TLS and SRTP, per the Network page.

  3. 03

    Test calls, engineer to engineer

    Inbound and outbound test calls with a Koda engineer on the line: caller-ID presentation, signing and failure codes.

  4. 04

    Production with monitoring

    Answer-seizure ratio, call duration and failure codes watched per customer and per route from the first call.

Fit

Which platform types does this fit? CPaaS, phone systems, voice AI, vertical SaaS

Koda fits any product where a business makes and receives live calls inside your software.

  • CPaaS

    Communications Platform as a Service

    Products that expose calling to developers and need a licensed carrier behind the API: termination, origination and numbers per tenant.

  • Phone systems

    Business phone-system vendors

    Hosted PBX and unified-communications vendors that need trunks, local numbers, porting and caller-ID name under their own brand. See SIP trunking.

  • Vertical SaaS

    Vertical software as a service

    Home-services, real-estate brokerage and appointment-based tools where customer follow-up happens inside the product.

  • Voice AI

    Voice AI that assists a person

    Real-time agent assist and transcription on live calls, and inbound answering that hands the caller to a person. Outbound artificial-voice calling is outside Koda's conversational traffic profile.

Vetting

How does customer vetting work when you resell voice inside your product?

Customer vetting for a platform happens at two levels. At onboarding Koda runs a Know-Your-Customer (KYC) review of the platform itself: legal entity, address, the officer responsible, use cases, expected traffic profile and consent practices. Koda also requires the platform to identify each business that will call through the product, to keep the use-case and consent record that Koda's review asks for, and to produce it on request. Koda can ask for the identity behind any calling number at any time.

Koda's acceptable-use policy applies to every call regardless of tenant, and traffic-quality monitoring runs per customer and per route. Under FCC rules (47 CFR § 64.6305), an RMD certification commits a provider to respond within 24 hours to all traceback requests from the FCC, law enforcement and the Industry Traceback Group (ITG), the FCC-designated traceback consortium, so Koda must be able to name the customer behind any number. The carrier KYC guide lists what the review asks for; the robocall-mitigation page summarises the program.

Numbers

How are numbers provisioned and ported for your end customers?

Numbers for your end customers are provisioned on Koda under your platform account. Koda provisions local numbers across U.S. markets and ports existing numbers, so you can order a number for a new tenant, route its inbound calls to your SIP endpoint and release it when the tenant leaves. A port needs the losing carrier's account details and the number holder's authorization; the order form states the terms. Caller-ID name (CNAM) can be registered for numbers Koda provisions. More on the phone numbers page.

Operations

What operations support does a platform get from Koda?

Operations support for a platform means a person who can touch the network. Koda's network operations desk, noc@kodavoice.com, takes live-traffic issues: call failures, quality, routing and signing. Your engineer works with a Koda engineer during onboarding; after go-live the same desk handles escalations and maintenance notices. Koda is a new carrier, and that is part of the offer: a clean network, a short path to an engineer, and a Trust Center where your customers' vetting teams can verify Koda's credentials. Rates, billing increments and capacity are stated on the order form and rate deck; the SIP specification is on the Network page.

FAQ

Frequently asked questions

What is bring your own carrier (BYOC) for a software platform?

Bring your own carrier (BYOC) means a software platform routes its voice traffic over a carrier it chooses and contracts with directly, instead of the telephony bundled into a communications platform. The platform keeps its brand and customer relationship; the carrier supplies trunks, numbers, signing for the calls it originates and accountability in its own name.

Whose STIR/SHAKEN certificate signs a platform's calls on Koda?

Koda Voice's own certificate signs calls originated on Koda's network. Koda Voice is an authorized STIR/SHAKEN service provider with the STI Policy Administrator (STI-PA) under Service Provider Code 583H and holds an STI certificate from an approved STI Certification Authority. A platform that is itself a voice service provider keeps its own FCC certification obligations.

Who vets a platform's end customers, Koda or the platform?

Both parties vet. Koda Voice runs a Know-Your-Customer review of the platform at onboarding, and requires the platform to identify each business that calls through the product and to produce that record on request. Koda can ask for the identity behind any calling number, monitors traffic quality per customer and per route, and enforces its acceptable-use policy on every call.

Can a platform provision and port phone numbers for its customers?

Number provisioning and porting are both available to a platform. Koda Voice provisions local numbers across U.S. markets and ports existing numbers; a platform orders, assigns and releases numbers for its customers under its Koda account, with inbound calls routed to its SIP endpoint. Caller-ID name (CNAM) is available.

Put a licensed carrier behind your product.

Tell us what your platform sends and how you vet your customers. We reply with an interconnection plan and a rate deck.

Talk to sales Read the SIP specification