Skip to main content

Documentation Index

Fetch the complete documentation index at: https://orbit-docs.devotel.io/llms.txt

Use this file to discover all available pages before exploring further.

​
ADR-002: Devotel softswitch is the sole outbound voice and SMS egress

Status: CURRENT Date: 2026-05-16

​
Context

Telnyx and DIDWW provide inbound DIDs. Their Call Control / Messaging API / SMS-MT surfaces were available for outbound, but dual-carrier outbound would fragment STIR/SHAKEN signing identity, billing reconciliation, and per-destination PSAP routing.

​
Decision

All outbound (MT) voice and SMS egress flows through Devotel’s wholesale softswitch (<devotel-softswitch-address> UDP). Telnyx and DIDWW are inbound-only on the DIDs we purchased from them. The drachtio sbc-sip pods in the devotel-voice-edge cluster are the actual SBC; Devotel itself is the softswitch, not an SBC.

​
Reason

Devotel owns the softswitch, so we own MT termination quality, STIR/SHAKEN signing identity, and per-destination PSAP routing. Aggregator splits would fragment regulatory posture, and we never built outbound integrations on Telnyx or DIDWW.

​
Consequences

  • Devotel is the “originating carrier” for FCC purposes (drives E911 and SPC decisions — see ADR-010).
  • Voice-edge IP allowlist locked at 4 /32s.
  • Calling Devotel an “SBC” is incorrect — it is the softswitch.
  • Invariant #45 enforces this in packages/messaging/src/router.ts and apps/voice-gateway/.

​
Source memos

  • invariants.md #45
  • [[reference_voice_edge_static_ips]]
  • [[provider_telnyx]]
  • [[provider_didww]]
  • [[decision_e911_2026_05_10]]
  • [[decisions_2026_05_12]] § D-E911-A / D-SS-A