Skip to content
KODA VOICE Talk to sales

SIP trunking · Bring your own carrier

SIP trunking for phone systems, contact operations and software platforms

Koda Voice provides SIP trunks that connect your phone system, contact platform or software product to the public telephone network through a licensed U.S. carrier. Trunks authenticate by IP allow-list or SIP digest credentials, can run signaling over TLS and media over SRTP, and are set up with a Koda engineer rather than a self-serve form.

Talk to sales Interconnection specs

Overview

What is a Koda Voice SIP trunk?

A Koda Voice SIP trunk is a Session Initiation Protocol (SIP) connection between your equipment and Koda's network that carries inbound and outbound calls over IP instead of physical phone lines. It replaces PRI circuits and analog lines. It also replaces the trunk a reseller would hand you from another carrier's network, because Koda Voice LLC holds its own carrier credentials.

Your phone system, contact platform or software product keeps its own features. Koda supplies the carrier layer: local phone numbers, voice termination to the United States and Canada, and STIR/SHAKEN signing under Koda's own identity.

Carrier, not a reseller

Carrier or reseller: what changes when the trunk provider holds its own credentials?

Many SIP trunks on the market are resold. The difference is whose name is on the registries a vetting team checks.

Credential What it shows Koda Voice Verify
FCC Registration Number (FRN) Registered with the Federal Communications Commission (FCC) in its own name. Held in Koda's own name FCC CORES public search
USAC Form 499 Filer ID Files with the Universal Service Administrative Company (USAC) in its own name. Filed in Koda's own name FCC Form 499 Filer Database
Operating Company Number (OCN) Assigned by NECA; needed to obtain numbering resources (NANPA). Assigned to Koda by NECA NECA company codes
Robocall Mitigation Database (RMD) Certifies its own robocall-mitigation program with the FCC. Listed since July 2026 FCC RMD public listings
STI Policy Administrator (STI-PA) authorization and STI certificate Signs STIR/SHAKEN calls under its own Service Provider Code (SPC). Authorized, with Koda's own Service Provider Code iconectiv authorized service providers

The certificate row is the one a reseller cannot fill without its own registrations. Under the Secure Telephone Identity Governance Authority (STI-GA) SPC Token Access Policy, the STI Policy Administrator (STI-PA) clears a provider for its own STI certificate only when it has a current Form 499-A, an assigned OCN and a Robocall Mitigation Database listing (STI-GA Policy Decision 001). A provider without those three items signs, if at all, under its upstream carrier's identity. The Trust Center repeats every identifier with its issuing registry; how to verify a VoIP carrier walks through the same checks.

Who connects

Which phone systems and platforms connect to Koda?

Any system that speaks standard SIP connects to Koda: on-premises and hosted PBXs, session border controllers, contact platforms and CPaaS or software products that bring their own carrier.

  • Phone systems

    Business phone systems

    On-premises IP PBXs, hosted PBX platforms and session border controllers that need a carrier for numbers and outbound calling. Microsoft Teams connects through a session border controller you operate, which then registers or peers with Koda.

  • Contact operations

    Contact platforms

    Inbound and conversational outbound for customer-contact teams: support callbacks, appointment confirmations, customer follow-up and prospecting conversations.

  • Software platforms

    Bring your own carrier

    Phone-system vendors, CPaaS and customer-engagement tools, and vertical software that need a licensed carrier behind their own product. Koda is the carrier of record and you are Koda's vetted customer; the product stays yours.

Settings are on the network page; see also contact operations and software platforms.

Security

How is a Koda trunk authenticated and secured?

Koda trunk specifications, stated so you can check them against your system before the first call.

Layer Koda Voice trunk
Signaling SIP over UDP, TCP or TLS; IPv4 signaling addresses.
Media RTP, or SRTP when signaling runs over TLS.
Authentication IP allow-list for systems with fixed addresses; SIP digest credentials for systems that register.
Codecs G.711 µ-law (PCMU) preferred, A-law (PCMA) accepted; others by arrangement on the order form.
DTMF RFC 4733 telephone-event.
Caller ID P-Asserted-Identity and From headers; the number presented must be one you are authorized to use.

TLS keeps signaling from being read in transit; SRTP does the same for the audio. Both are set per trunk, so a system that cannot run them yet is not locked out. The full specification and the Network Operations Center (NOC) contact are on the network page.

Call flow

How are inbound and outbound calls handled on a Koda trunk?

  • Inbound

    Numbers route to your SIP destination

    Local numbers you provision from or port to Koda are pointed at the SIP address you specify. Ask at onboarding if you need a secondary destination; routing is agreed before go-live.

    Phone numbers and porting →

  • Outbound

    Calls originate on Koda's network, signed by Koda

    Calls originate on Koda's network and terminate to the United States and Canada, signed under Koda's own Service Provider Code 583H. Attestation follows the STIR/SHAKEN framework and depends on whether Koda has verified your right to use the calling number.

    How Koda signs calls →

Capacity and billing

How does Koda size capacity and bill trunk usage?

Koda sets concurrent-call capacity per trunk on the order form, based on the traffic profile you describe at onboarding, and raises it as your traffic history proves out. Capacity is a conversation with an engineer, not a slider: a sudden change in call volume is one of the signals Koda watches per customer.

Billing model How it meters What to check
Per channel A fixed monthly charge for each concurrent call path, regardless of minutes carried. The number of simultaneous calls you need at peak, and what happens when every channel is busy.
Per minute Usage charged on the minutes carried, rounded up by the billing increment. The increment and any minimum duration, which change the cost of short calls more than the headline rate does.

Koda's rate deck and order form state which model applies to your trunk, the increments and the concurrent-call capacity. The website does not publish rates. Increments often matter more than the headline rate, so read how billing increments work before comparing offers.

Onboarding

What does onboarding look like? KYC, test calls, go-live

Koda is a new carrier with a clean network. Engineer-to-engineer onboarding keeps it that way.

  1. 01

    Describe the traffic

    Legal name and address, an officer's identity, the platform sending the calls, the numbers you will present and what the conversations are about. What KYC asks.

  2. 02

    Accept the policy, receive credentials

    You accept the acceptable-use policy. Koda allow-lists your addresses or issues digest credentials; the order form sets capacity and increments.

  3. 03

    Test calls with an engineer

    Inbound and outbound test calls with a Koda engineer on the line. Codec negotiation, DTMF, caller-ID presentation and signing are checked, not assumed.

  4. 04

    Go live, monitored

    Answer-seizure ratio, call duration and failure codes are watched per customer and per route from the first call. Live-traffic issues go to noc@kodavoice.com.

FAQ

Frequently asked questions

What is SIP trunking and what does it replace?

SIP trunking is a voice connection that carries phone calls between your phone system and a carrier over an IP network using the Session Initiation Protocol. It replaces physical PRI circuits and analog lines. From a licensed carrier such as Koda Voice, it also replaces a trunk resold from another company's network.

How can I tell whether a SIP provider is a carrier or a reseller?

A carrier holds its own Operating Company Number (OCN), files its own FCC Form 499 with the Universal Service Administrative Company (USAC) and signs calls under its own STIR/SHAKEN certificate. Every voice service provider, carrier or reseller, must appear in the FCC Robocall Mitigation Database. Koda Voice publishes each identifier in its Trust Center.

Can I use the same trunk for inbound numbers and outbound calls?

One Koda Voice trunk carries both directions. Local numbers provisioned from or ported to Koda route inbound calls to the SIP destination you specify. Outbound calls originate on Koda's network, are signed under Koda's own Service Provider Code 583H and terminate to the United States and Canada.

Is Koda SIP trunking priced per channel or per minute?

Koda Voice states the billing model, increments and rates for your traffic profile in the rate deck and order form you receive after the first conversation, and sets concurrent-call capacity per trunk there. The website does not publish rates; the billing-increments guide explains how increments change a call's cost.

Talk to Koda about your traffic.

Tell us what you send, where it goes and what platform it comes from. We'll come back with an interconnection plan and a rate deck for your profile.

Talk to sales See the Trust Center