Connect VICIdial to VOS3000
VICIdial sends calls to VOS3000 like any other customer. Set it up as an IP-authenticated mapping gateway, cap its bursts, and point a VICIdial carrier at the switch.
Updated · By the VOS3000 Web team
Quick answer: To VOS3000, VICIdial is a customer with a fixed IP: give it an account with a rate group, a mapping gateway with the VICIdial server's IP, and a Line limit and Rate limit that suit dialer bursts. On VICIdial, add a carrier whose SIP peer points at the VOS3000 IP and a dialplan entry that strips the campaign's dial prefix.
- VOS3000 side
- Account, rates, mapping gateway
- Caps for dialers
- Line limit and Rate limit
- VICIdial side
- Carrier: account entry and dialplan entry
- DTMF
- dtmfmode=rfc2833
VICIdial is an open-source contact-centre dialer built on Asterisk. To VOS3000 it is a customer with a fixed IP that sends a lot of calls, many of them short or unanswered. The setup has two halves: VOS3000 has to recognise and bill the dialer, and VICIdial needs a carrier that sends calls to VOS3000.
On VOS3000: rates, account and mapping gateway
- Rates: in Rate management, create a rate group with the destinations the campaigns will call.
- Account: in Account management, add an account for the dialer with that rate group and a balance or overdraft limit.
- Mapping gateway: add a mapping gateway with the VICIdial server's public IP in Ip, the dialer's account in Account id, and a Line limit. In Additional settings, allow the codecs VICIdial will offer. See mapping gateway.
- Firewall: allow the VICIdial IP on the SIP firewall of the VOS3000 server.
Limits for dialer traffic
A dialer starts calls in bursts, often several per agent. Two settings keep that in check:
- Line limit on the mapping gateway: the number of concurrent calls the gateway may have.
- Rate limit in the mapping gateway's Additional settings > Others: limits how many calls can be set up in a period, which is your calls-per-second cap. See CPS limit.
Set the routing gateway towards the carrier to what the carrier allows, using the same two settings. With Rate limit on, Online routing gateway shows the current Call per second. Ask the carrier before sending dialer traffic: many routes are not meant for it.
On VICIdial: the carrier
In the VICIdial admin, add a carrier under Admin > Carriers. Leave Registration String empty, set Protocol to SIP, pick the Server IP of the dialer and set it active. The Account Entry holds the SIP peer, in chan_sip format:
| Line | What it does |
|---|---|
| [vos3000] | The peer name, used in the dialplan. |
| type=peer | Calls go out to this peer; it does not register. |
| host=203.0.113.10 | The VOS3000 server's IP. |
| port=5060 | The VOS3000 SIP port, if you changed it. |
| disallow=all | Clears the codec list first. |
| allow=ulaw | G.711; add allow=g729 if the dialer has G.729. |
| dtmfmode=rfc2833 | Sends DTMF as RFC 2833 events, the usual choice with VOS3000. |
| insecure=port,invite | Accepts calls from VOS3000 without a password challenge. |
| context=trunkinbound | Where calls from VOS3000 land, for inbound campaigns. |
| qualify=yes | Sends OPTIONS to see whether VOS3000 is reachable. |
Builds that use PJSIP instead of chan_sip need the same values in PJSIP syntax.
The dialplan entry
Campaigns dial with a Dial Prefix, 9 by default. The Dialplan Entry catches that prefix, logs the call and strips the 9 before sending the number to VOS3000:
| exten => _9X.,1,AGI(agi://127.0.0.1:4577/call_log) |
| exten => _9X.,n,Dial(SIP/vos3000/${EXTEN:1},,tTo) |
| exten => _9X.,n,Hangup() |
If your carrier needs a technical prefix, add it on VOS3000 with a rewrite rule on the routing gateway, not in VICIdial, so every customer is handled the same way.
Test the route
On the dialer, asterisk -rx "sip show peer vos3000" should show the peer as OK. Place a manual call and open it in Recent CDR on VOS3000. CallAuthenticationFailure (-6) means the call came from an IP that is not on the mapping gateway. If the call connects but audio is missing, see SIP ALG and NAT problems.
Questions about this topic
Does VICIdial need to register to VOS3000?
No. The usual setup is IP authentication: VOS3000 recognises VICIdial by its IP on the mapping gateway, so the carrier's Registration String stays empty.
Why does VOS3000 reject calls from VICIdial with CallAuthenticationFailure?
The calls come from an IP that is not on the mapping gateway. Check the VICIdial server's public IP, especially if it sits behind NAT or has more than one address.
How do I stop VICIdial from overloading my carrier?
Set a Line limit and a Rate limit on the mapping gateway for VICIdial, and on the routing gateway set the limits your carrier allows.
Which codec should VICIdial use with VOS3000?
Use one both sides allow, normally G.711 (ulaw or alaw) or G.729, and keep it the same end to end to avoid transcoding.
Run VOS3000 without the server work
Pick a VOS3000 server hosted by us, or have us install VOS3000 on your own server. VOS3000 Web and the Android app come with it.
Keep reading
Add a mapping gateway
Set up a customer gateway: types, IPs, line limits, prefixes and billing.
Codecs and DTMF
Auto or specified codecs, transcoding, G729 modes, RFC2833 and SIP INFO.
Desktop, SIP and CDR firewalls
Allow trusted IPs, change the SIP port and unban addresses.
Wholesale setup, step by step
From an empty switch to a first billed call: rate group, rates, account, mapping and routing gateway.