SignalWire is a Twilio-API-compatible carrier from some of the original FreeSWITCH folks. The APIs line up closely with Twilio's, and our SMS gateway has SignalWire wired in directly — set your Space URL, project ID, and API token and outbound SMS should work.
Same three pieces as Twilio — outbound calls, inbound numbers, and SMS — but configured through a SignalWire Space rather than the Twilio console. Migration from Twilio is mostly a credential swap.
Configure a voice endpoint in your SignalWire Space, point it at MyDaddy.io, and add it as a Provider in the admin portal. Per-call billing on SignalWire's side.
Buy or port numbers in SignalWire and route them to MyDaddy.io via the voice endpoint. Per-number workspace assignment under Inbound Routing in the portal.
Our SMS gateway figures out the SignalWire endpoint from your Space URL automatically. Set the three credential keys and you're sending.
You'll need a SignalWire Space (free to create) with at least one project and one purchased phone number.
SignalWire console: SIP → SIP Endpoints → Add. Set username/password, or allow your MyDaddy.io server's IP. Note the endpoint URI — it'll look like username@<your-space>.sip.signalwire.com.
Portal: Settings → Providers → Add Provider. Set Host to <your-space>.sip.signalwire.com, transport UDP or TLS, leave audio preferences on the default. Paste credentials. Add destination prefixes.
SignalWire console: for each phone number, set the Voice Settings handler to your voice endpoint. Inbound calls now arrive on MyDaddy.io. Assign numbers to workspace inbound profiles in the MyDaddy.io portal.
Portal: Settings → Integrations → SMS Provider → SignalWire. Set Space URL (e.g., https://your-space.signalwire.com), Project ID, and API Token. Set the inbound webhook on each SignalWire number to https://<your-domain>/api/v1/sms/signalwire-inbound.
Make an outbound test call from the browser phone. Call your SignalWire number and confirm it rings. From the SMS tab, send a message to your own mobile and confirm delivery in the SignalWire Messaging logs.
Stored under your workspace's namespace. The portal writes these for you.
| Key | Purpose | Example |
|---|---|---|
providers.<id>.host | SignalWire voice endpoint host | your-space.sip.signalwire.com |
providers.<id>.username | Endpoint username | mydaddy-prod |
providers.<id>.password | Endpoint password | ••••• |
providers.<id>.codecs | Audio preference | PCMU,PCMA,opus |
organizations.<org>.signalwire-space-url | Your Space URL | https://your-space.signalwire.com |
organizations.<org>.signalwire-project-id | Project ID for SMS | UUID |
organizations.<org>.signalwire-api-token | API token for SMS | PT... |
organizations.<org>.signalwire-from-number | Default From number | +15551234567 |
SMS delivery uses SignalWire's REST API under the hood; the URL is derived from your Space URL automatically.
SignalWire's API is largely Twilio-compatible and the call flow is the same, so swapping providers is usually the bulk of the work.