☎️ Redfire UCaaS
API-first, multitenant Class 5 PBX control plane for hosted providers
A new Class 5 application layer built around proven open-source telephony engines - Kamailio for the SIP edge, FreeSWITCH for media and applications, and RTPengine for WebRTC and NAT traversal - wrapped in a Rust control plane with a tenant-aware API, provisioning, and dialplan builder.
Sponsored by
Project Overview
🏢 Multitenant by Design
Domain-based tenant isolation, RBAC, and tenant-scoped API keys built in from the ground up. Reseller/sub-reseller hierarchy is specced for v1 but not yet built.
🧱 Proven Telephony Engines
Built on Kamailio, FreeSWITCH, and RTPengine rather than a from-scratch SIP stack, with a Rust control plane on top.
🔗 Contract-Driven Sibling Integration
Integrates with Redfire B/OSS for billing/OSS and the production Redfire Switch for carrier trunking and SMS/MMS, validated against shared schemas.
Platform Features
Redfire UCaaS is under active development. The cards below are split into what's actually built and verified today versus what's planned per the v1 architecture spec but not yet implemented - this page intentionally avoids marking planned work as shipped.
✅ Built Today
Domain-Based Tenant Isolation
Each tenant is isolated by SIP domain via Kamailio's domain module. Reseller/sub-reseller hierarchy is specced but not yet built.
RBAC & Scoped API Keys
Role-based access control with API keys scoped by tenant, role, and object/action type, enforced across the API.
Tenant Defaults & Overrides
Tenant-level defaults for ring timeout/strategy and voicemail delivery/retention, configurable through the admin UI.
Voicemail & Ring Groups
Voicemail and ring groups are built and running natively in Kamailio's routing layer.
Call Queues (Basic)
Sequential-dispatch call queues are working; hold music and agent-state tracking are not yet built.
Zero-Touch Provisioning (Fanvil/Yealink)
Fanvil and Yealink device provisioning is built and live-verified. The Poly/Cisco TAA-compliant tier is planned, not yet built.
WebRTC Registration
SIP-over-WebSocket registration for a browser softphone works today; audio calling itself is still in progress and explicitly out of scope for the current milestone.
ChangeSet Workflow
Admin changes apply through a propose/validate/simulate/approve/apply ChangeSet flow with rollback and audit logging.
Admin Dashboard
A web admin UI covers tenant, device, and dialplan-object management. A separate tenant-facing self-service dashboard is not yet built.
🔜 Planned (v1 Spec, Not Yet Built)
IVR
Auto-attendant / call-routing IVR is part of the v1 spec but has no implementation yet.
Conferences & Call Parking
Neither conferencing nor call parking has been built yet.
Blind & Attended Transfer
Call transfer is specced for v1 but not yet implemented.
Call Recording & Policy Engine
Always-on, user-controlled, policy-based, and per-call recording modes are all planned; no recording policy engine exists yet.
Embeddable Softphone Widget
A separate embeddable widget (beyond the user-portal softphone) is planned but not built.
Multi-Device Extensions & Hot Desking
Multiple devices sharing one extension, and hot desking/hoteling, are both planned but not implemented.
White-Labeling
A documented, planned commercial requirement with no implementation yet.
Poly & Cisco Provisioning (TAA Tier)
Planned for GovCon/SLED customers; not yet built.
LLM Assistant & MCP Tool-Call Support
LLM-assisted configuration and MCP-based admin automation are both planned for a later milestone; neither has started.
Architecture
┌─────────────────┐ ┌─────────────────┐ ┌─────────────────┐
│ SIP / WebRTC │ │ Kamailio │ │ FreeSWITCH │
│ Endpoints │◄──►│ SIP Edge/ │◄──►│ Media & Apps │
│ │ │ Auth/NAT │ │ (VM, Ring, Q) │
└─────────────────┘ └─────────────────┘ └─────────────────┘
│ │
┌─────────────────┐ ┌─────────────────┐
│ RTPengine │ │ Rust Control │
│ Media Bridge │ │ Plane │
└─────────────────┘ └─────────────────┘
│
┌─────────────────┐
│ PostgreSQL + │
│ Prometheus/Graf.│
└─────────────────┘
Platform Components
- Rust Control Plane - API, tenant model, provisioning, dialplan builder, diagnostics
- Kamailio - SIP edge, registration, auth, NAT traversal, WebSocket SIP, rate limiting
- FreeSWITCH - Media and application layer; voicemail and queues are built, IVR/conferences/transfers/recording are planned
- RTPengine - WebRTC media bridge, NAT traversal, SRTP/RTP bridging
- PostgreSQL - Tenants, users, devices, dialplan objects, provisioning, CDR metadata
- Prometheus + Grafana - System, SIP, media, and tenant-level monitoring
- Push Gateway - APNs/FCM bridge for backgrounded mobile softphones
Build Approach
Redfire UCaaS is built as thin, end-to-end vertical slices - each milestone adds demonstrable value - and proven at the smallest environment tier that can validate it before moving up.
🚧 T0 - Developer Laptop (Docker Compose)
- Kamailio, FreeSWITCH, RTPengine, PostgreSQL, Prometheus, Grafana, and the Rust control plane as containers
- Sibling systems (Redfire Switch, Redfire B/OSS) replaced by contract-driven fakes for fast, dependency-free iteration
- Tenant/dialplan foundation, domain-scoped auth, and live config publishing to Kamailio are done; current focus is call-handling features (IVR, transfer, conferencing, recording) and WebRTC audio
🔜 T1 - Single Colo VM (Staging)
- Real public IP, DNS, and Let's Encrypt certificates
- Real NAT/ICE traversal with coturn and at least one real hard phone
- Real Carrier One trunk to Redfire Switch and a real (or staging) Redfire B/OSS instance
🔮 T2 - Production High Availability
- Redundant Kamailio with a floating IP
- Multiple FreeSWITCH media nodes with drain and failover drills
- PostgreSQL replication
Get Access to Redfire UCaaS
Redfire UCaaS is under active development as a privately maintained platform, available to hosted providers and partners with commercial support.