carrier
87 posts.
Lowering your per-minute carrier cost
Practical ways to cut what you pay your SIP carrier per minute without sacrificing call quality or compliance.
Read postEstimating your carrier (per-minute) cost
Carrier minutes are the variable line in any VICIdial budget. Here is how to estimate them from agents, dialing ratio, and per-minute rate.
Read postFrom signup to your first campaign on VICIfast
The exact path from creating an account to launching your first VICIdial campaign — sign up, provision, add leads, connect your carrier, and dial.
Read postBring your own carrier with VICIfast
VICIfast hosts the dialer but never sells minutes. You connect your own SIP trunk, so your carrier relationship stays yours.
Read postPorting your phone numbers when you move to VICIdial
Number porting when switching to VICIdial involves an LOA, your losing carrier, and a timeline measured in days not hours. Here is how to plan the port and avoid call center downtime.
Read postCloud IP reputation and your outbound calls
A fresh cloud IP address may carry a poor spam reputation from previous tenants, which can hurt your answer rates and STIR/SHAKEN attestation.
Read postKeeping carrier latency low from the cloud
Cloud region placement has a direct effect on RTP path length and call quality — here is how to reduce carrier latency for your VICIdial box.
Read postWhy your VICIdial cloud box needs a public IP
A cloud VICIdial server without a routable public IP will fail to exchange SIP and RTP traffic with carriers, leaving agents with no audio.
Read postChoosing a cloud region for your dialer
The cloud region where you deploy your VICIdial box affects call quality, data residency, and cost — here is how to pick the right one for your operation.
Read postSending a Test Call With a Custom Caller ID in VICIdial
The Send a Call With Custom CID page fires a single outbound call from a chosen server using any caller ID you set, as long as your carrier allows it.
Read postWhat HUC statuses (enhanced disconnect logging) tell you about failed calls
An HUCXXX status is an enhanced disconnect-logging level 3 record, where XXX is the carrier disconnect code that ended the call.
Read postWhat the PDROP status means and why it points at carrier behaviour
PDROP is a pre-routing dropped call, hung up the instant the Answer signal arrives, which is the fingerprint of a carrier false answer.
Read postWhy so many calls land on NA (no answer) and what it really means
NA is No Answer AutoDial, a catch-all for any outbound call that never gets an Answer signal, from ring-no-answer to congestion to plain errors.
Read postWhy calls ring but never connect to an agent
Calls that ring out, drop, or sit unanswered usually trace back to the hopper, agent availability, or a carrier that never sends a real answer.
Read postWhat CONGESTION means in VICIdial and how to stop it
CONGESTION means the carrier couldn't place the calls you sent. It's a capacity or route problem on their side, or you over-dialed. Here's how to confirm and back off.
Read postOne-way audio on VICIdial calls and how to find the cause
When one side hears and the other doesn't, RTP is flowing one direction only. Here is how to isolate the silent leg.
Read postDiagnosing carrier rejects: reading the codes your provider sends back
Use the Hangup Cause and Carrier Log reports to read your carrier's rejection codes, filter to a specific cause, and decide what to change.
Read postHow to read the Inbound DID Detail Report to trace a single inbound call
Use the Inbound DID Detail Report to follow one inbound call by DID and tell where it actually routed versus where the number points today.
Read postHow to read SIP hangup causes and translate them into plain English
The Dial Log Report groups calls by SIP hangup cause code and reason. Here is what the common codes really mean for your list and carrier.
Read postNo audio on VICIdial calls: first things to check
Total silence on both legs almost always means RTP media isn't flowing. Here is the ordered checklist to find where it stops.
Read postWhat CHANUNAVAILABLE means and why it's usually a line-count problem
CHANUNAVAILABLE means the dialer ran out of lines before it could hand the call to the carrier. It's a local capacity limit, not a carrier reject.
Read postWhat hangup cause 17 (user busy) tells you about your list
Cause 17 is a real busy signal, logged as the AB status. A high rate is usually a list-quality or redial-timing problem, not a system fault.
Read postWhat SIP Cause 18 (request timeout) means on your VICIdial calls
Cause 18 means the far end never answered in time. Here is what it tells you about your list and carrier, and what to check first.
Read postCalls placed but not connecting: a first-things-to-check guide
Calls dial out but never reach a person? Read the per-attempt SIP response codes in the Dial Log and Carrier Log reports to find the cause.
Read postWhat hangup cause 21 (call rejected) means and who's rejecting it
Cause 21 means something actively refused your call. Usually it's caller-ID reputation. Here's who rejects and what to change.
Read postDiagnosing false answer supervision with the SIP Event Report
The SIP Event Report lets you sort SIP messages by Ring-Time to spot False Answer Supervision — calls marked answered before a human picked up.
Read postHow to read the Dial Log Report and what the SIP codes mean
The Dial Log Report groups every placed call by its SIP response code. Here is how to read each column and turn a wall of codes into a real diagnosis.
Read postHow to read the SIP Event Report and spot false answers
The SIP Event Report sorts SIP messages by ring-time and other criteria. Here is how to enable it and use it to catch false answer supervision.
Read postThe VICIdial troubleshooting playbook: where to start when something breaks
A symptom-first guide that routes you from what's broken — dead dials, false answers, slow agent screens, drops on hold — to the exact VICIdial report that holds the answer.
Read postHow to read the Hangup Cause Report and find why calls drop
The Hangup Cause Report shows the carrier hangup causes for all outbound calls. Here is how to filter it to specific causes and find why calls drop.
Read postHow to read the Carrier Log Report when calls aren't going out
When calls won't connect, the Carrier Log Report shows every dial attempt and the response code the carrier returned. Here is how to read and download it.
Read postHow to use the Asterisk Debug Page to check SIP peers and registry
The Asterisk Debug Page surfaces live SIP peers, registry status, and the last 1000 CLI lines so you can confirm a trunk is registered without SSH.
Read postMonitoring call quality on a carrier
Track MOS, jitter, packet loss, and latency on every carrier route, set thresholds, and have a plan to switch carriers before bad audio costs you conversions.
Read postCodec mismatch with your carrier: how to fix it
A codec mismatch shows up as no audio or a 488 rejection. Pin the same codec on both ends and the call connects cleanly.
Read postOne-way audio on carrier calls: causes and fixes
One-way audio means signaling connected but RTP media is blocked one direction — almost always a NAT, public-IP, or RTP-port problem. Here is how to find it.
Read postCarrier rejecting calls (503/603): what it means
A 503 means the carrier could not take the call right now — overload, CPS limit, or no route. A 603 means it actively declined. Here is how to tell them apart and fix each.
Read postChoosing a carrier for international dialing
International dialing needs coverage, per-country rates, correct caller ID rules, and good routes. Here is how to pick a carrier that delivers.
Read postHow to connect SignalWire to VICIdial
Create a SignalWire SIP endpoint with credential or IP auth, then add the matching SIP carrier entry and dialplan in VICIdial.
Read postHow to connect SIPStation to VICIdial
Add a SIPStation by Sangoma SIP trunk to VICIdial using either IP authentication or registration, then verify the peer and place a test call.
Read postBuying DIDs from your carrier for inbound
How to buy or port DIDs from your carrier, choose local or toll-free numbers, and point each purchased DID at your trunk and an in-group.
Read postHow to test a new carrier trunk before going live
Stage the trunk inactive, flip it on, confirm the peer is up, then place one manual test call and check audio and caller ID before any campaign touches it.
Read postCarrier won't register: what to check
When a VICIdial carrier won't register, walk a short checklist: registration string typos, wrong host or port, NAT, credentials, and the firewall on 5060.
Read postSIP trunk vs SIP registration: which your carrier needs
Understand the difference between a SIP trunk on IP authentication and one that registers with credentials, and which your carrier expects.
Read postHow to connect DIDWW to VICIdial
DIDWW handles inbound DIDs worldwide plus outbound voice — wire it into VICIdial with IP auth or registration and verify with a test call.
Read postHow to choose a SIP carrier for VICIdial
What actually matters when picking a SIP carrier for VICIdial: IP-auth support, CPS and channel limits, the rate deck, caller-ID and attestation, and real support.
Read postPointing a carrier DID at a VICIdial in-group
Map a carrier DID to a VICIdial in-group under Admin then Inbound then DIDs, where the DID's route decides where each inbound call lands.
Read postHow to connect RingCentral to VICIdial
RingCentral is UCaaS, so you need its SIP trunk product before VICIdial can use it — here is how to get the credentials and add the carrier.
Read postHow many concurrent channels does your carrier allow
Your carrier's channel cap sets the ceiling on simultaneous calls — here's how it limits dial level and how to match it to your agents.
Read postSetting up a backup carrier
Add a second carrier and failover routing so calls reroute automatically when your primary trunk returns a 503 or congestion instead of completing.
Read postReading your carrier's rate deck for outbound dialing
A carrier rate deck is the per-destination price list for your outbound calls. Here is how to read one and pick the cheapest route.
Read postSetting up an inbound trunk from your carrier
Use context=trunkinbound on the carrier account entry so calls your carrier sends to your IP land in VICIdial's DID handling and reach an in-group.
Read postHow to connect Vitelity to VICIdial
Add a Vitelity (now part of the Voyant/Bandwidth lineage) SIP trunk to VICIdial with portal credentials, the right carrier block, and a verify test call.
Read postWhitelisting your VICIdial server IP with a carrier
How to set up IP authentication: hand your carrier your server's static public IP, configure the peer with no register line, and verify it.
Read postCalls-per-second (CPS) limits and your carrier
What CPS means, why carriers cap how fast you place calls, and what happens — 503s and congestion — when you push past the limit.
Read postThrottling calls-per-second to protect your carrier
Practical pacing to stay under your carrier's CPS cap: lower the auto dial level, ease pacing, and spread call placement across trunks.
Read postHow to connect Flowroute to VICIdial
Wire Flowroute into VICIdial with IP authentication: get your SIP domain, add the carrier, set the dialplan, and verify with a test call.
Read postAnswer supervision and false answers from carriers
Answer supervision is the signal that a call truly connected. False answers fake it, inflating your stats and breaking dialer pacing.
Read postLocal DIDs vs toll-free numbers for inbound
When to use local DIDs versus toll-free numbers for inbound VICIdial campaigns, and how the cost and answer-rate tradeoffs differ.
Read postEncrypting carrier traffic with TLS and SRTP
TLS encrypts your SIP signaling and SRTP encrypts the audio. Here is when carriers offer it and how to configure the peer.
Read postHow to connect Anveo to VICIdial
Wire Anveo Direct to VICIdial for outbound dialing and DID inbound using SIP trunk credentials, the carrier account block, and a verified test call.
Read postHow to switch carriers without dropping live calls
Add the new carrier alongside the old one, shift dial routing gradually, drain the old trunk, then deactivate it — a gentle migration with no hard cutover.
Read postOutbound calls failing at the carrier: first checks
When outbound calls fail at the carrier, run the first checks: trunk active, peer reachable, dial pattern correct, caller ID valid, and any 503 or 603 response.
Read postHow to connect Commio (thinQ) to VICIdial
Wire Commio, formerly thinQ, into VICIdial using IP authentication for outbound and inbound, then verify with sip show peers and a test call.
Read postHow to connect VoIP.ms to VICIdial
Set up a VoIP.ms sub-account, pick your POP, and add it to VICIdial with either registration or IP authentication, then verify with a test call.
Read postANI vs CNAM: what your carrier sends and shows
ANI is the number your call sends; CNAM is the name the far carrier looks up from that number. They are set in two different places.
Read postHow to connect CallWithUs to VICIdial
Add a CallWithUs SIP trunk to VICIdial using registration or IP auth, build the carrier account block and dialplan, and verify with a test call.
Read postHow to connect Skyetel to VICIdial
Skyetel authenticates by IP via endpoint groups. Whitelist your server, add the SIP carrier entry, and route DIDs into an in-group.
Read postReading a SIP trace to debug a carrier issue
A SIP trace shows the INVITE, the response codes, and the ACK in order — read it top to bottom and you can see exactly where a carrier call breaks.
Read postHow to connect Plivo to VICIdial
Create a Plivo Zentrunk, choose IP-ACL or credential auth, then add the SIP carrier entry and dialplan in VICIdial.
Read postHow to connect Bandwidth to VICIdial
Bandwidth trunks authenticate by IP. Whitelist your VICIdial server, add the SIP carrier entry, and route DIDs into an in-group.
Read postHow to connect Telnyx to VICIdial
Set up a Telnyx SIP Connection with IP or credential auth, then add the matching SIP carrier and dialplan in VICIdial.
Read postHow to connect Twilio to VICIdial
Connect a Twilio Elastic SIP Trunk to VICIdial: grab the SIP domain, whitelist your server IP, then add a SIP carrier and dialplan.
Read postGetting your numbers unblocked when carriers flag them
How outbound numbers get blocked or flagged, the remediation and registration paths to clear them, and how to keep watching your reputation afterward.
Read postBranded caller ID (CNAM) through your carrier
What CNAM is, how the called party's carrier looks your name up in LIDB, and what you register with your carrier or CNAM provider to control it.
Read postMaking sure your caller ID reaches the carrier
How VICIdial sends caller ID to your carrier, why it sometimes gets stripped or overwritten, and how to confirm the number you set is the one that goes out.
Read postCall attestation A, B, and C explained
What attestation levels A, B, and C mean, how they tie into STIR/SHAKEN, and why a higher level keeps your calls off the Spam Likely list.
Read postSetting up the STIR/SHAKEN API integration
How to wire VICIdial's outbound calls into the TILTX Call Shaper API so your calls get signed with the right attestation level.
Read postSTIR/SHAKEN and VICIdial: What You Need to Know
STIR/SHAKEN signs your caller ID so carriers can trust it. Here is what it is, why it affects your answer rates, and where VICIdial fits in.
Read postServer Trunks: Assigning Carrier Lines at the Server Level
VICIdial Server Trunks let you reserve and cap outbound lines per campaign so one busy campaign cannot starve the others on the same box.
Read postConf File Templates: Reusing Carrier Configuration
Stop pasting the same allow/disallow and codec lines into every carrier and phone. Conf File Templates let you define a block once and point everything at it.
Read postStripping or Adding Digits Before the Carrier Sees Them
VICIdial almost never sends the carrier exactly what was dialed. Here is how the dialplan strips and adds digits so your trunk gets the format it expects.
Read postActivating and Deactivating a VICIdial Carrier
The Active flag on a VICIdial carrier decides whether the trunk is written to the conf. Set it to Y to use the carrier, N to disable it cleanly.
Read postVICIdial Carrier Server IP: Which Server Uses the Trunk
The Server IP field on a VICIdial carrier decides which box runs the trunk. Set it to one server, or use 0.0.0.0 to put it on all of them.
Read postVICIdial Carrier Template ID and Conf File Templates
The Template ID field lets a VICIdial carrier reuse a shared conf template instead of a one-off account entry. Here is how it works and what to leave out.
Read postVICIdial Carrier Protocol: SIP vs IAX2 (and PJSIP)
The Protocol field on a VICIdial carrier picks SIP, PJSIP, or IAX. Here is what each one is, how to check peers, and which to choose.
Read postVICIdial Carrier Global String: What That Field Actually Does
The Global String field on a VICIdial carrier defines a dialplan variable for the trunk. Here is when you need it and when to leave it blank.
Read postAnswer Signal: when an inbound call is marked answered
The Answer Signal setting decides when VICIdial tells the carrier a call is answered, which affects billing and audio.
Read post