Skip to content

docs: Luso8 + Voxtra integration architecture and roadmap - #1

Merged
byamasu-patrick merged 3 commits into
mainfrom
docs/luso8-integration-roadmap
Jun 21, 2026
Merged

docs: Luso8 + Voxtra integration architecture and roadmap#1
byamasu-patrick merged 3 commits into
mainfrom
docs/luso8-integration-roadmap

Conversation

@byamasu-patrick

Copy link
Copy Markdown
Contributor

Adds docs/luso8-integration-roadmap.md: how the three existing pieces assemble into one voice stack with Voxtra as the abstraction layer.

  • Voxtra (this repo) as the unified layer
  • luso8-telephony-core (Asterisk PBX on GCP) as the telephony core
  • kamailio fork as the SIP edge for scale

Contents

  • Verified current state: the Asterisk PBX VM (running, config from luso8-pbx-* secrets, carrier trunk still a placeholder, dialplan hands inbound to Stasis(voxtra), recordings to GCS); Voxtra's functional core + production Asterisk ARI adapter + STT/LLM/TTS pipeline; the luso8.backend voxtra_client + asterisk.py integration; LiveKit as today's primary AI-voice path.
  • Target architecture: Carriers → Kamailio → Asterisk → Voxtra (on GKE) → luso8 backend, with Voxtra fronting both Asterisk and LiveKit.
  • Phased roadmap: (1) Asterisk + Voxtra path live in parallel to LiveKit, (2) unify the backend telephony layer behind Voxtra, (3) Kamailio SIP edge for scale.
  • Integration seams, the env/secret map, verification per phase, and risks (the big one: media region locality, since the PBX is in africa-south1 and the main cluster is in us-central1).

Decisions baked in: Voxtra worker runs on GKE, a carrier trunk is available to configure. This is documentation only, no code or infra change. No em-dashes per house style.

Adds docs/luso8-integration-roadmap.md describing how Voxtra, the
luso8-telephony-core Asterisk PBX, and the Kamailio fork assemble into one stack
with Voxtra as the abstraction layer. Covers the verified current state, the
target architecture, a phased roadmap (Asterisk+Voxtra path live, backend
unification, Kamailio scale edge), the env and secret map, verification, and
risks (notably media region locality). Architecture and roadmap only; no code or
infra change.
The rexplore-ai/kamailio fork is vanilla upstream (no Luso8 config yet) but ships
every edge module needed. Flesh out Phase 3 with the role split (Kamailio SIP
edge, Asterisk media, Voxtra on GKE), the specific modules and their job
(dispatcher, registrar/usrloc, permissions, tls, rtpengine, topos/dialog,
htable/auth_db), the templated-config + Docker + CI build pattern mirroring
luso8-telephony-core, the luso8-kamailio-* secret map, and DID/domain routing.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant