Skip to content
KODA VOICE Talk to sales

Network & interconnection

Koda Voice network: SIP trunk specifications, security and operations

Koda Voice interconnects over standard SIP trunks. Trunks authenticate by IP allow-list or SIP digest credentials, carry G.711 audio with RFC 4733 DTMF, and can run signaling over TLS with SRTP media. Calls originated on Koda's network are signed under Koda's own STIR/SHAKEN Service Provider Code (583H). The Network Operations Center (NOC) answers at noc@kodavoice.com.

Signaling

Which SIP transports, ports and signaling conventions does Koda use?

Koda's SIP signaling follows RFC 3261 on the standard ports. Koda Voice LLC interconnects as a carrier in its own right, under its own Operating Company Number (OCN) 583H, assigned by NECA (National Exchange Carrier Association) and verifiable from the Trust Center. The values below are Koda's standard profile; the interconnection sheet issued at onboarding is authoritative for your trunk and carries the actual addresses.

ItemKoda profile
TransportsUDP, TCP, TLS
Ports5060 for UDP and TCP; 5061 for TLS
AddressesPrimary and secondary, issued at onboarding; use the secondary on timeout or 503
Number formatE.164 with a leading plus (+1 and ten digits) in Request-URI, To, From and P-Asserted-Identity
Caller identityP-Asserted-Identity (RFC 3325) carries the number Koda signs; Privacy: id honored
RegistrationOptional on credential trunks; not used on IP-authenticated trunks
Identity headerAdded at origination on calls Koda signs; received headers pass unaltered

Media

Which codecs, DTMF and media options are supported?

Koda's media profile is G.711 audio with RFC 4733 DTMF over RTP, or SRTP on TLS trunks. Koda carries G.711 natively across its network; offer it first in the SDP so no transcoding step is added at Koda's edge.

ItemKoda profile
Audio codecsG.711 μ-law (PCMU) preferred; A-law (PCMA) accepted; others by arrangement on the order form
DTMFRFC 4733 telephone-event (formerly RFC 2833), payload type negotiated in SDP
Media transportRTP over UDP; SRTP with SDES key exchange (RFC 4568) on TLS trunks
Media addressesRanges on the interconnection sheet; allow-list them on your firewall
TranscodingNone when G.711 is offered first; handling of any other codec is set on the order form

Authentication

How are endpoints authenticated? IP allow-list and digest credentials

Koda authenticates a trunk by IP allow-list or by SIP digest credentials; a trunk can switch between them with a ticket.

  • IP allow-list

    You register the static public IP addresses or CIDR blocks that send SIP; Koda accepts INVITEs only from them. Best for softswitches, session border controllers and fixed-egress platforms.

  • SIP digest credentials

    Koda issues a username and secret; your phone system authenticates each request with digest (RFC 3261) and may register. Best where source addresses change.

Security

How are signaling, media and the network itself secured?

Koda's security posture covers the trunk and the systems behind it.

  • TLS for signaling. SIP over TLS on port 5061, TLS 1.2 or later, so INVITEs, credentials and caller identity are encrypted between your edge and Koda's.
  • SRTP for media. On TLS trunks, media runs as SRTP with keys exchanged in the SDP (RFC 4568), encrypting audio between your edge and Koda's.
  • Least privilege, allow-lists and change control. Koda's operating policy limits administrative access to the engineers who operate each system, allow-lists management access by source address, and routes production changes through recorded change control with a rollback plan.
  • Lawful intercept and CPNI. Interception follows the Communications Assistance for Law Enforcement Act (CALEA) plan the Federal Communications Commission (FCC) accepted and, under 47 U.S.C. 1004, requires a court order or other lawful authorization. Customer Proprietary Network Information (CPNI) follows Koda's CPNI policy.

Vulnerability reports: security@kodavoice.com.

STIR/SHAKEN

How does Koda sign calls? STIR/SHAKEN in the SIP path

Koda Voice is an authorized STIR/SHAKEN service provider with the STI Policy Administrator (STI-PA), iconectiv, under Service Provider Code 583H, with an STI certificate issued by an approved STI Certification Authority; calls originated on Koda's network are signed under that identity.

On calls Koda originates, the PASSporT is inserted as the SIP Identity header before the call leaves the network. Its attestation value is A, B or C (RFC 8588; ATIS-1000074): A when the customer is verified and authorized to use the number, B when verified but number authorization cannot be confirmed, C otherwise. Koda assigns the level; customers do not select it.

Identity headers received on inbound calls are passed on unaltered for the terminating carrier to verify; policy detail is on the STIR/SHAKEN page and the levels are explained in attestation levels.

Response codes

How should a platform handle Koda's SIP response codes?

Koda returns standard SIP response codes. Retry storms after a 4xx or 5xx trip traffic monitoring; back off to protect your route and number reputation.

CodeMeaning on a Koda trunkRecommended action
403 ForbiddenSource not allow-listed, credentials rejected, or caller ID not authorizedCheck source IP and caller ID, then open a ticket
480 / 486Called party unavailable or busyRetry later, not in a loop
503 Service UnavailableKoda's edge or the route cannot take the call nowFail over to the secondary address, then contact the NOC
603 DeclineRejected by policy, for example a do-not-originate numberDo not retry; ask compliance

Operations

What does the NOC do? Monitoring, tickets and escalation

The Network Operations Center (NOC) is the desk that touches the network; the engineer who brings up your trunk is the engineer who answers your ticket.

  • Monitoring

    Koda monitors answer-seizure ratio, call duration and SIP failure codes per customer and per route from the first call.

  • Opening a ticket

    Email noc@kodavoice.com with the trunk name, Call-IDs or number pairs with timestamps and time zone, the SIP response, and a trace if available.

  • Escalation

    Every ticket gets a reference and an owner; reply "escalate" on a stalled live-traffic issue and the responsible engineer joins. Traceback and regulatory matters go to compliance@kodavoice.com.

  • Maintenance notices

    Planned work is announced in advance to the technical contact on file, with a window and expected impact, outside business hours where possible.

Go-live

How do interconnection testing and go-live work?

Interconnection is an engineering conversation, not a self-serve form: Koda is a new carrier with a clean network and an engineer on every onboarding.

  1. 01

    KYC review

    You describe the business, the sending platform, the numbers you will present and the expected traffic profile; Koda reviews it under its Know-Your-Customer policy (what a carrier asks).

  2. 02

    Interconnection sheet

    Koda issues signaling and media addresses, the authentication method, codec and DTMF settings, and the order form's concurrent-call limit.

  3. 03

    Test calls

    Calls both ways to numbers you control, with a Koda engineer reading the SIP trace: authentication, codec negotiation, DTMF, caller ID and the Identity header.

  4. 04

    Go-live with monitoring

    Traffic is enabled at the agreed profile. Per-route monitoring runs from the first call and the NOC thread stays open.

FAQ

Frequently asked questions

What SIP ports and transports does Koda Voice support?

SIP signaling on Koda's network runs over UDP and TCP on port 5060 and over TLS on port 5061, following RFC 3261. Media is RTP over UDP, or SRTP on TLS trunks. The signaling and media addresses to allow-list are issued on the interconnection sheet at onboarding, with a secondary address for failover.

Can I authenticate by IP address instead of SIP registration?

IP allow-list authentication is the default for any platform with fixed public egress addresses: Koda accepts SIP only from the addresses you register and rejects the rest at the edge. SIP digest credentials, with optional registration, cover phone systems and cloud platforms whose source addresses change. A trunk can move between the two methods with a ticket.

Where is the STIR/SHAKEN Identity header added and verified?

The Identity header is added by Koda at origination, before a call Koda signs leaves its network, using Koda's own STI certificate under Service Provider Code 583H. The attestation level follows the SHAKEN framework and is assigned by Koda, not chosen by the customer. Identity headers received on inbound calls are passed on unaltered for the terminating carrier to verify.

Does Koda Voice support TLS 1.2 and SRTP on SIP trunks?

TLS 1.2 or later on port 5061 encrypts SIP signaling between your edge and Koda's, and media on a TLS trunk runs as SRTP with keys exchanged in the SDP under RFC 4568. Both are available on IP allow-list and digest-credential trunks; the interconnection sheet states which transport your trunk was provisioned with.

How do I reach the Koda Voice NOC and what is the escalation path?

The Network Operations Center (NOC) is reached at noc@kodavoice.com. Send the trunk name, Call-IDs or number pairs with timestamps and time zone, the SIP response and a trace. Every ticket receives a reference and an owner; replying "escalate" on a stalled live-traffic issue brings in the responsible engineer. Traceback matters go to compliance@kodavoice.com.

What testing happens before a Koda Voice interconnection goes live?

Test calls run in both directions to numbers you control while a Koda engineer reads the SIP trace, checking authentication, codec negotiation, DTMF, caller ID presentation and the STIR/SHAKEN Identity header. Traffic is then enabled at the profile agreed on the order form, with per-route monitoring active from the first call and the NOC thread left open.

Ready to bring up a trunk?

Send the platform, source addresses and the numbers you will present; an engineer replies with the interconnection sheet.

Start an interconnection See SIP trunking