Telecom GatewayOperator planes
Operator-grade routing, compliance, and settlementper carrier
The Telecom Gateway is a dedicated plane that translates platform intents into operator-safe traffic with country rules, tenant constraints, delivery receipts, retries, and reconciliation events.
Compliance gate (per country + tenant)
Validate sender rules, residency constraints, consent requirements, and blocked routes before any side effects.
Deterministic retries + failover
Per-intent timeouts, retry budgets, and provider fallbacks. No silent dropseverything emits evidence.
Receipts + settlement events
Delivery receipts (DLR), call detail/quality records, and settlement/reconciliation events per operator.
Service boundaries
Telecom Gateway is treated as a separate plane from the public API. It enforces operator contracts and exposes only normalized events back to the platform.
- Ingress: authenticated intents only (tenant-scoped)
- Policy gate: must return allow/deny/needs_approval
- Operator adapter: protocol-specific (SMPP/SIP/HTTP)
- Receipts normalizer: unify DLR/CDR/quality
- Settlement emitter: invoice/reconcile events
Operator plane model
We model each operator as a plane so telemetry, compliance, and economics are measurable per carrier.
operatorPlane
operatorId • country • protocols • senderRules • qosProfiles • settlementTerms • failoverTargets