LightningArrows Voice — architecture
High level
Consumer SIP phone (Cisco MPP, Grandstream, …)
│
│ SIP (+ RTP)
▼
┌─────────────────────┐
│ LA Voice edge │ registration, NAT assist, ACL, TLS options
└──────────┬──────────┘
▼
┌─────────────────────┐
│ LA PBX core │ on LightningArrows cloud compute
│ multi-tenant │ extensions, dialplan, voicemail path
└──────────┬──────────┘
▼
┌─────────────────────┐
│ Carrier / DID │ numbers, porting, e911
└─────────────────────┘
lightningarrows.com cart (Snipcart)
→ order Desk / Office Voice
→ provision ticket + credentialsWhy not “here is a FreePBX root password”?
| DIY VPS PBX | LightningArrows Voice |
|---|---|
| Customer owns every exploit surface | We harden the edge |
| Customer finds a trunk | We provide a path |
| Customer invents 911 | e911 address is part of go-live |
| Support = internet forums | Support = LightningArrows |
You still get standard SIP for the handset — the product is the glue.
Tenancy model (MVP → growth)
| Stage | Model |
|---|---|
| MVP | Shared hardened platform + per-customer extensions |
| Growth | Isolated cores for Office / regulated customers |
| Power users | BYO trunk into LA edge (later tier) |
Pricing alignment
| SKU | Monthly | Daily | Seats |
|---|---|---|---|
la-voice-desk |
$7.50 | $0.25 | 1 |
la-voice-office |
$30.00 | $1.00 | up to 5 |
Same entry daily rate as Cloud Basic.
Security baseline
- No open anonymous relay
- Auth required for registration
- Rate limits / fraud watch on outbound
- TLS where client and plan support it
- e911 address collected before advertising full outbound
Phone onboarding
- Cart captures optional MAC + model
- Backend creates extension
- Customer receives SIP triple or provision URL
- Phone registers — see bolt-in guide
Dogfood
We validate on a real CP-8851-3PCC with static home IP — demo write-up.
Related
Architecture evolves; this page describes the 2026 product direction customers are buying into.