Skip to content
CLIRoutes

Integration · Dialer

GoAutoDial setup for CLIRoutes

GoAutoDial v4 wraps VICIdial and Asterisk in the GoAdmin interface. Its carrier wizard writes the same account entry and dialplan VICIdial uses, so you can either fill the form or paste the advanced fields. This guide uses the manual carrier type, which gives full control over codecs and caller ID headers.

Tested on
GoAutoDial 4.0 · Asterisk 13
Channel driver
chan_sip
Auth
IP allow-list or registration
Signalling
sip.example-carrier.net:5060 UDP
Codecs
G.711 μ-law/a-law, G.729

Before you start

  • A GoAdmin account with the Administrator user group.
  • Your server public IP on the CLIRoutes endpoint, or SIP credentials from the portal.
  • Authorised caller IDs approved in the portal.
  • Firewall rules allowing SIP and RTP to and from the CLIRoutes networks (GoAutoDial ships with firewalld enabled).

Placeholders in angle brackets, such as <ACCOUNT_ID>, come from your portal. The host shown is a placeholder; use the one listed under Portal → Network.

Set up GoAutoDial

  1. 01

    Start the carrier wizard

    In GoAdmin open Telephony → Carriers and click Add New Carrier. Choose Manual as the carrier type so the advanced fields are editable.

  2. 02

    Enter the basics

    Use cliroutes as Carrier ID, a descriptive name, select your server IP and set Protocol to SIP. For authentication pick IP Based if your endpoint uses an allow-list, or Registration to enter the account ID and SIP password.

  3. 03

    Review the generated account entry

    Open the Advanced view. Make sure the entry matches the block below; GoAutoDial defaults some versions to allow=all, which can negotiate codecs you did not intend.

    Account Entry
    [cliroutes]
type=friend
host=sip.example-carrier.net
disallow=all
allow=ulaw
allow=alaw
allow=g729
dtmfmode=rfc2833
insecure=port,invite
qualify=yes
nat=force_rport,comedia
sendrpid=pai
context=trunkinbound
  4. 04

    Set the dial prefix and dialplan

    Enter 9 in Dial Prefix. The wizard generates a dialplan; replace it with the international pattern so lists can carry any destination.

    Dialplan Entry
    exten => _9X.,1,AGI(agi://127.0.0.1:4577/call_log)
exten => _9X.,n,Dial(SIP/cliroutes/${EXTEN:1},,tTo)
exten => _9X.,n,Hangup()
  5. 05

    Open the firewall

    Allow the CLIRoutes signalling and media ranges listed in Portal → Network. On the server shell, add them to a trusted zone and reload.

    firewalld
    firewall-cmd --permanent --zone=trusted --add-source=<CLIROUTES_SIGNALLING_RANGE>
firewall-cmd --permanent --zone=trusted --add-source=<CLIROUTES_MEDIA_RANGE>
firewall-cmd --reload
  6. 06

    Assign the campaign

    In Campaigns → [campaign] → Basic Settings set the dial prefix to 9 and the Campaign CallerID to an authorised number. Save, activate the carrier and place a manual test call to a phone you control.

Where GoAutoDial differs from plain VICIdial

  • The wizard hides the globals string; reference the peer directly as SIP/cliroutes in the dialplan.
  • Changes saved in GoAdmin can overwrite manual edits made in the classic VICIdial admin, so pick one interface and stay with it.
  • Some builds default to type=friend; that is fine for IP authentication but means inbound INVITEs from the carrier also match this peer, so keep context=trunkinbound.

Troubleshooting

SymptomLikely causeFix
Carrier shows UNREACHABLEFirewall blocking OPTIONS repliesAdd the signalling range to the trusted zone
403 ForbiddenIP not allow-listed or caller ID not authorisedCheck Portal → Endpoints and Caller IDs
Calls drop at 30–32 secondsACK lost behind NATKeep nat=force_rport,comedia and confirm externip in sip.conf

Last verified by the CLIRoutes routing team. Menus can change between releases; if a field has moved, tell us.

FAQ

GoAutoDial questions

Can’t find what you need? Our routing team answers within the hour, around the clock.

Can I use the GoAutoDial carrier wizard without the Advanced view?

Yes, but check the generated codecs and dialplan afterwards. The defaults assume US 10-digit numbers, which will fail on international destinations.

Does GoAutoDial support TLS to CLIRoutes?

GoAutoDial 4 runs chan_sip on Asterisk 13, which supports TLS with additional sip.conf settings. Most customers use UDP with IP authentication; contact routing if you need encrypted signalling.

How many channels should I configure?

Set the server Max Trunks to your CLIRoutes channel limit. Use the channel calculator to size it from agents, dial ratio and average handle time.

Will updates to GoAutoDial overwrite the carrier?

Carrier records live in the database and survive updates. Manual edits to generated .conf files do not, so keep all changes in GoAdmin.

Ready to connect GoAutoDial?

Open an account to get your endpoint, credentials and authorised caller IDs.

Open account