Telephony provider setup and credentials configuration #2

Open
opened 2026-04-04 16:33:21 -07:00 by pyr0ball · 0 comments
Owner

Sign up for SignalWire (preferred — Twilio-compatible API, lower cost, self-hostable path), configure outbound calling credentials, and wire credentials into the dialer stack. Currently blocked — see #1.

Provider decision

See circuitforge-plans/osprey/superpowers/specs/2026-04-04-telephony-backend-design.md for full analysis.

MVP: SignalWire (Twilio-compatible API, $3.50–$8.80/1K min, near-drop-in replacement)

Env vars needed

  • SIGNALWIRE_PROJECT_ID
  • SIGNALWIRE_API_TOKEN
  • SIGNALWIRE_SPACE_URL (e.g. your-space.signalwire.com)
  • SIGNALWIRE_PHONE_NUMBER

Fill from .env.example in /Library/Development/CircuitForge/osprey/.

Sign up for SignalWire (preferred — Twilio-compatible API, lower cost, self-hostable path), configure outbound calling credentials, and wire credentials into the dialer stack. Currently blocked — see #1. ## Provider decision See `circuitforge-plans/osprey/superpowers/specs/2026-04-04-telephony-backend-design.md` for full analysis. **MVP: SignalWire** (Twilio-compatible API, $3.50–$8.80/1K min, near-drop-in replacement) ## Env vars needed - `SIGNALWIRE_PROJECT_ID` - `SIGNALWIRE_API_TOKEN` - `SIGNALWIRE_SPACE_URL` (e.g. `your-space.signalwire.com`) - `SIGNALWIRE_PHONE_NUMBER` Fill from `.env.example` in `/Library/Development/CircuitForge/osprey/`.
pyr0ball added this to the Alpha — Pipeline milestone 2026-04-04 16:33:21 -07:00
pyr0ball changed title from Twilio account setup and credentials configuration to Telephony provider setup and credentials configuration 2026-04-05 21:38:21 -07:00
Sign in to join this conversation.
No labels
backlog
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference: Circuit-Forge/osprey#2
No description provided.