How to connect VoIP.ms to VICIdial

Connecting VoIP.ms to VICIdial comes down to making a sub-account, picking the closest POP server, and adding a SIP carrier that authenticates either by Registration string or by IP authentication. VoIP.ms is a flexible VoIP provider that supports both, so you choose.

What to set up in the VoIP.ms portal

VoIP.ms routes voice through sub-accounts. Create one for your dialer and copy its credentials — don't guess hostnames, read them from your account.

• Create a sub-account with a username and SIP password.
• Pick a POP (point of presence) server geographically close to your dialer — VoIP.ms lists the SIP domain for each POP. Lower distance means less latency.
• Choose the auth mode: 'User/Password' for registration, or 'Static IP' to whitelist your server's public IP for IP auth.

Add the carrier in VICIdial

Open Admin → Carriers → Add New Carrier. If you chose registration, fill the Registration String with the register line VoIP.ms format expects — your sub-account user, password, and the POP SIP domain. Your dialer then talks to the SIP registrar to keep the trunk online. If you chose IP auth, leave the register line empty.

In the Account Entry, write the peer block for your Server trunk:

• disallow=all then allow=ulaw to pin the codec.
• type=friend so calls flow both directions.
• host=dynamic with a register line, OR host=<the POP SIP domain> for IP auth.
• context=trunkinbound so inbound calls land in DID handling.

Set Protocol to SIP. In the Dialplan Entry, strip the Dial prefix and add the country code so numbers go out in E.164 format. Set Server IP to the right Asterisk box, then set Active=Y.

How the pieces connect

flowchart TD
  A[VoIP.ms Sub-Account] --> B[POP SIP Domain]
  B --> C{Auth Mode}
  C -->|Register| D[Registration String]
  C -->|Static IP| E[IP Authentication]
  D --> F[VICIdial Carrier]
  E --> F
  F --> G[Campaign Calls]

Verify the trunk

Run sip show peers on the Asterisk CLI. A registered or reachable peer confirms VoIP.ms is talking to your dialer. Then place a single test call from Campaign Detail, listen for clean two-way audio, and check the caller ID. Once that connects, you can route inbound numbers to an Ingroup under Admin → Inbound → DIDs.

Two VoIP.ms specifics catch people out. The POP you pick sets your call quality — choosing a server far from your dialer adds latency that shows up as delay and choppy audio, so always select the nearest one. And VoIP.ms accounts have a default concurrent-call limit; if you're running a busy campaign, raise that limit in the portal before you scale up, or the dialer will start getting calls rejected when it hits the ceiling. Both are quick portal settings, but skipping them produces problems that look like a broken trunk when the carrier entry is actually fine.

For the full carrier walkthrough, read the VICIdial carrier integration guide, and for the exact register syntax see the registration string explainer.

VICIfast gives you a dedicated dialer with a static IP in under 40 seconds, which makes VoIP.ms Static IP mode the simplest path. Check pricing and bring your VoIP.ms account along.