Get started

SignalWire (bring your own number)

The SignalWire connection lets a ThunderPhone agent handle calls on a production number routed through your SignalWire SIP trunk. SignalWire continues to supply the number and telephony connection. ThunderPhone supplies the agent configuration, including the prompt, call-direction settings, attached knowledge, and tools.

What the SignalWire connection does on ThunderPhone

ThunderPhone's current documentation marks direct SignalWire onboarding as coming soon. For now, connect through Manual SIP configuration, the documented path for any SIP trunk. This establishes call transport between the trunk and ThunderPhone; it should not be read as a native data integration with the rest of a SignalWire account.

The manual form accepts the SIP domain or URI, optional username and password, port, transport, and an optional allowed-source-IP list. The setup-guide generator produces provider-specific instructions for the trunk side. ThunderPhone then tests the connection end to end before saving it.

Once connected, import the number you want the agent to use. A round-trip verification checks inbound reachability and outbound authorization. A successful check activates the number for inbound and outbound agent assignments. If the two directions serve different purposes, each can use a different deployed agent configuration.

Typical call flows

Overflow answering

When the primary team cannot take a call, routing on the SignalWire side can send it through the connected trunk to a ThunderPhone inbound agent. The agent follows the deployed prompt to identify the caller's need, answer supported questions, collect details, or route the call. This can form part of an overflow call-handling plan.

Urgent-call routing

An inbound agent can screen the request and follow explicit escalation rules. Where the imported production number is eligible to place an outbound SIP leg, an attended warm transfer can privately brief the recipient before connecting the caller. If the recipient declines, does not answer, or reaches voicemail, the agent can return to the caller with the outcome. Test this path against the live trunk configuration before relying on it for urgent-call routing.

Outbound follow-up

ThunderPhone can place an outbound call through the verified imported number. The outbound agent follows its assigned prompt and configured voicemail policy. Endpoint-based webhooks can notify your server about call events and retry non-successful deliveries; that automation is separate from the SIP connection itself.

Setup outline

  1. In SignalWire, identify the SIP trunk and number to connect. Confirm the routing and outbound authorization required for the intended call directions.
  2. Open Connections → VoIP in ThunderPhone, select New connection, and choose Manual SIP configuration.
  3. Enter the SIP domain or URI, authentication when required, port, and transport. Configure allowed source IPs if your trunk uses an IP allowlist.
  4. Use Generate AI Setup Guide and apply the provider-specific instructions to the SignalWire trunk.
  5. Select Test & Save Connection. If the test reports a failure, correct the indicated trunk assignment, reachability, source restriction, or outbound authorization issue and retry.
  6. Import the number from Phone Numbers → Add number → Connect VoIP provider, then run the inbound and outbound verification.
  7. Assign the agents, test inbound and outbound calls, and deploy any pending agent draft before launch.

Keep the SIP credentials and routing current as your provider configuration changes. Telephony charges and number costs remain dependent on the SignalWire setup. Because provider-specific onboarding status can change, check the current ThunderPhone VoIP screen before beginning.

Related reading