How to connect Bandwidth to VICIdial

To connect Bandwidth to VICIdial you whitelist your server's public IP on a Bandwidth SIP trunk, then add a SIP carrier entry pointed at the Bandwidth host. Bandwidth trunks authenticate by IP authentication rather than registration, so there is no register line to fill in.

Get the trunk from Bandwidth

In the Bandwidth dashboard set up your voice account and a SIP peer. Bandwidth identifies your traffic by the source IP of your INVITEs, so the core step is registering your VICIdial server's public IP as an authorized host on the peer. Bandwidth gives you the host(s) to send outbound calls to; copy that off your own account page.

• Add your VICIdial server's public IP to the Bandwidth peer's allowed-host list.
• Copy the Bandwidth outbound host from your account; do not guess it.
• Order a DID (direct inward dialing) and point its inbound route at your server IP on port 5060.

Add the carrier in VICIdial

Open Admin then Carriers then Add New Carrier. Leave the Registration String blank — Bandwidth does not want a REGISTER. Pin the host in the Account Entry instead.

Account Entry:

• [bandwidth] / disallow=all / allow=ulaw / type=friend / context=trunkinbound
• host=<your Bandwidth outbound host> / dtmfmode=rfc2833 / insecure=port,invite

Set Protocol to SIP. Bandwidth routes 10-digit and E.164 numbers; a common pattern strips the campaign Dial prefix 9 and the leading 1 to send 10 digits. Adjust the strip to what your peer expects:

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

The ${EXTEN:2} strips the 91 and sends the 10-digit number. Set Server IP, set Active to Y, save, and wait about a minute for the conf to regenerate.

Route inbound DIDs into an in-group

The context=trunkinbound line is what makes inbound work. Bandwidth delivers a call for one of your numbers to your server IP on 5060, and trunkinbound hands it to VICIdial's DID (direct inward dialing) handling. Under Admin then Inbound then DIDs, create an entry whose DID matches the dialed digits Bandwidth sends (usually the 10-digit or +1 form) and point it at an Ingroup, a call menu, or an IVR. If inbound calls hit a fast busy, the number-format mismatch between what Bandwidth sends and what your DID expects is the first thing to check.

Bandwidth enforces a calls-per-second rate on outbound traffic. If your campaign ramps the dial level aggressively you can exceed that Calls per second (CPS) ceiling and see calls rejected, so keep the campaign's pacing in line with what the peer is provisioned for. The disallow=all then allow=ulaw pinning also matters here: G.711 ulaw is the safest Codec to send a US carrier, and pinning it avoids the carrier renegotiating to something your box did not offer.

The call path

flowchart TD
  A[VICIdial Server IP] -->|whitelisted| B[Bandwidth SIP Peer]
  B -->|outbound 10-digit| C[PSTN]
  C -->|inbound DID| B
  B -->|to server IP 5060| D[trunkinbound]
  D --> E[DID route to Ingroup]

Verify it

Run sip show peers on the Asterisk CLI. With IP auth the peer should read reachable even though no registration happens. Place a test call from Campaign Detail and confirm two-way audio. For inbound, map the DID (direct inward dialing) to an Ingroup under Admin then Inbound then DIDs so whitelisted calls land on agents.

Bandwidth is the textbook IP-auth carrier; the same approach covers most static-IP trunks. The full field reference is in our VICIdial carrier integration guide, and the IP-vs-register tradeoff is in register vs IP authentication.

A VICIfast box has a static public IP — the one thing Bandwidth needs — and provisions in under 40 seconds. Check pricing and bring your Bandwidth account.