SIP trunking

The wires you know.
The control you wanted.

Dials terminates SIP from your existing trunk providers and exposes the same identity, routing, and audit primitives as the rest of the platform. No new dialect to learn.

Talk to usRead the API

At a glance

What SIP looks like on Dials.

Termination
Multi-provider
Terminate on any IETF-compliant trunk. Failover handled at the adapter.
Origination
Per-seat
Outbound SIP origination scoped to the seat, signed at the edge.
Codec
Opus · G.722 · PCMU
Negotiated per call, with codec-aware routing for media fidelity.
Security
TLS + SRTP
Encrypted signaling, encrypted media, key rotation per session.

Bring your own trunks

SIP, without the surprise.

Add a trunk by URL, credentials, and quota. Dials handles registration, keep-alive, codec negotiation, DTMF passthrough, and call accounting. The trunk is one row in your carrier matrix.

  • Per-trunk credentials
  • Per-trunk quota
  • Active-active failover
  • Per-trunk usage event
dials · trunks
trunk-east-01
sip.bulkvs.com:5061 · 1000 cps
Active
trunk-west-01
sip.example.com:5061 · 500 cps
Active
trunk-fallover
sip-fb.example.com:5061 · 200 cps
Standby

Encrypted by default

TLS signaling.
SRTP media.

Signaling rides TLS. Media rides SRTP. Keys rotate per session. The signing layer for STIR/SHAKEN is built into the egress path, so every outbound call carries an attestation by default.

  • TLS 1.3 signaling
  • SRTP media
  • STIR/SHAKEN signing
  • No PCMU in the clear
dials · sip security
SignalingTLS 1.3 · ECDHE
MediaSRTP · AES-CM-128
AttestationSTIR/SHAKEN A
Key rotationPer session
Replay window30 seconds

Wire your trunks.

Configure a trunk in mock mode and watch the call setup, the media path, and the usage event roll up the same audit ledger.

Open the consoleTalk to us