How 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.
Connecting RingCentral to VICIdial works only if you have a SIP trunking product from RingCentral, not just a regular RingCentral phone plan. RingCentral is mainly UCaaS (unified communications), so the desk-phone and app service won't hand VICIdial a raw SIP trunk — you need their SIP trunk offering.
What to get from RingCentral
From your RingCentral SIP trunk admin area, copy the connection details exactly as shown. Don't guess at hostnames.
- The SIP domain or host RingCentral assigns to your trunk.
- Your trunk username/password, or the option to authorize your server by IP.
- The DID numbers on the trunk so you can route them inbound later.
Add the carrier in VICIdial
Open Admin → Carriers → Add New Carrier. If the trunk uses credentials, fill the Registration String with the register line built from your username, password, and the RingCentral SIP host. That keeps your SIP (Session Initiation Protocol) trunk authenticated against their registrar. In the Account Entry, write the peer block:
- disallow=all then allow=ulaw to pin the codec.
- type=friend so the peer handles inbound and outbound calls.
- host=dynamic with a register line, or host=<the RingCentral SIP host> for IP auth.
- context=trunkinbound so inbound calls feed into VICIdial's DID handling.
Set Protocol to SIP. In the Dialplan Entry, strip your campaign Dial prefix and add the country code, then dial the digits out. Set Server IP to the Asterisk box this trunk lives on, and set Active=Y.
How inbound and outbound route
flowchart LR
A[RingCentral SIP Trunk] -->|Inbound DID| B[trunkinbound]
B --> C[VICIdial DID Match]
C --> D[In-Group Agent]
E[VICIdial Campaign] -->|Outbound| F[SIP Carrier]
F --> AVerify the trunk
Run sip show peers on the Asterisk CLI and confirm the peer is reachable. Then place a single test call from the Campaign Detail screen, listen for two-way audio, and verify the caller ID. To route inbound numbers, point each DID (direct inward dialing) at an in-group under Admin → Inbound → DIDs once the test call is clean.
Worth setting expectations: RingCentral is built around hosted handsets and apps, not raw trunking, so the connection details for a SIP trunk are sometimes tucked away or only available on certain plan tiers. If your admin area doesn't expose a SIP domain and trunk credentials at all, you likely have a standard UCaaS subscription and need to talk to RingCentral about adding their SIP trunk product. Once that's in place, ask whether the trunk supports IP authentication — on a box with a fixed public IP that's the cleaner route than registration, because there are no credentials to expire and the dialer reconnects faster after any restart.
For the field-by-field picture, read the carrier integration guide, and this note on SIP vs IAX explains why SIP is the right protocol here.
VICIfast provisions a dedicated VICIdial server with a static public IP in under 40 seconds, which is exactly what a RingCentral SIP trunk wants to whitelist. See pricing to bring your trunk to a box that's ready for it.
About VICIfast LLC
VICIfast LLC operates a managed VICIdial hosting + BYOI service for outbound and inbound call centers. We run the dialers, the carriers, the recordings pipeline, and the compliance plumbing so operators don’t have to.
Citing this article
VICIfast Engineering. “How to connect RingCentral to VICIdial”. VICIfast LLC, June 24, 2026. Retrieved from https://vicifast.com/blog/connect-ringcentral-to-vicidial
Have questions?
Related posts
You might be interested in
VICIfast newsletter
Liked this? Get the next one in your inbox.
We ship the kind of stuff you just read — concrete, numbers-first, no drip. One email when a new post goes live. Unsubscribe in one click.
Comments
No comments yet — be the first.