Skip to content
Free, open source, AGPL-3.0

Bridge Signal messenger calls 
to your own SIP/PBX

A native daemon connecting Signal’s private voice calling 
to a standard SIP/PBX system - self-hosted, end to end

Keep your existing PBX

Add Signal to Asterisk, FreePBX, or any SIP/PBX system as just another line - no need to replace anything.

Two-way reachability

Dial a Signal contact from a SIP extension, or receive a Signal call routed straight into your PBX.

Self-hosted, end to end

No third-party gateway ever sees your calls or your keys.

Encrypted everywhere

TLS/SRTP on the SIP leg, alongside Signal’s own end-to-end encrypted calling.

Multi-account

Any number of Signal accounts per daemon, each configured independently, each with its own SIP trunk if needed.

Manage it live

A terminal UI or a plain CLI - no daemon restart needed for config changes.

Proxy support

Route any account through a transparent TLS relay to reach Signal from a network where it’s blocked, same as the official app’s proxy feature.

🧪 Testing status: signal2sip has been tested live against real PBX hardware, across several configurations and call scenarios - but it hasn’t seen broad, independent testing yet. Found a bug, or has it worked well for you? Feedback is welcome - open an issue or PR on GitHub, or just email us.
Disclaimer: signal2sip is not affiliated with, endorsed by, or sponsored by Signal Messenger, LLC or Signal Technology Foundation.