How to connect SignalWire to VICIdial

To connect SignalWire to VICIdial you create a SignalWire SIP endpoint, choose credential or IP authentication, then add a SIP Carrier entry in VICIdial pointed at your SignalWire SIP domain. SignalWire gives each space its own SIP domain, so copy it off your own account.

Get the endpoint from SignalWire

In your SignalWire space, create a SIP endpoint under the SIP settings. SignalWire issues a username, a password, and a per-space SIP domain (the host you dial against). You can authenticate with those credentials or restrict by IP. Buy a number and route it to the SIP endpoint so inbound calls reach your server.

• Note your space's SIP domain (the per-account host) from the SIP settings page.
• Copy the endpoint username and password, or add your server IP if using IP auth.
• Route a purchased DID (direct inward dialing) to the SIP endpoint for inbound.

Add the carrier in VICIdial

Open Admin then Carriers then Add New Carrier. For credential auth, fill the Registration string as register => user:pass@<your-signalwire-sip-domain>. For IP auth, leave it blank and pin the host.

Account Entry:

• [signalwire] / disallow=all / allow=ulaw / type=friend / context=trunkinbound
• host=<your SignalWire SIP domain> / username=... / secret=... / dtmfmode=rfc2833

Set Protocol to SIP. SignalWire takes E.164, so dial the +1 number. With campaign Dial prefix 9, strip the 9 and prepend +1:

• exten => _91NXXNXXXXXX,1,AGI(agi://127.0.0.1:4577/call_log)
• exten => _91NXXNXXXXXX,2,Dial(SIP/signalwire/+${EXTEN:1},,tTor)

Set Server IP, set Active to Y, save, and wait about a minute for the conf files to regenerate.

Credentials or IP, and inbound routing

SignalWire's SIP endpoint can authenticate by credentials or restrict by source IP. On a server with a fixed public IP either works, but the credential path is the most common: VICIdial sends a REGISTER to your space's SIP domain, SignalWire marks the peer registered, and outbound calls flow without re-authenticating each one. If your IP is stable, IP restriction removes the credential round-trip, which is one fewer thing to break.

For inbound, route a purchased number to the SIP endpoint in your space. SignalWire then sends matching calls to your registered peer, the context=trunkinbound line passes them into VICIdial's DID (direct inward dialing) handling, and your DID entry under Admin then Inbound then DIDs forwards them to an Ingroup. Pin allow=ulaw so the Codec stays plain G.711 and SignalWire never has to transcode mid-call.

The call path

sequenceDiagram
  participant V as VICIdial
  participant S as SignalWire SIP Endpoint
  participant P as PSTN
  V->>S: REGISTER (credentials)
  V->>S: INVITE +1NXXNXXXXXX
  S->>P: route outbound
  P-->>S: answer + RTP
  S-->>V: 200 OK
  Note over S,V: inbound DID returns via trunkinbound

Verify it

Run sip show peers on the Asterisk CLI; a credential endpoint reads Registered, an IP-auth one reads reachable. Place a single test call from Campaign Detail, confirm clean two-way audio and correct caller ID, and map the DID (direct inward dialing) to an Ingroup under Admin then Inbound then DIDs for inbound.

The complete carrier field reference is in our VICIdial carrier integration guide, and the exact register => syntax is broken down in the registration string guide.

A VICIfast box gives you a static public IP for the IP-auth path and is live in under 40 seconds. See pricing and connect SignalWire.