A VICIdial SIP trunk built around your operation.

Your existing VICIdial server remains responsible for agents, lists and campaigns. The SIP carrier provides the route to the agreed telephone networks. Keeping these roles separate lets you retain your installation while reviewing routing, commercial terms or connectivity. Moving to Dial24 is not a prerequisite.

We do not need the contents of your lead lists to discuss connectivity. More useful details are your VICIdial and Asterisk versions, public server IP, operating location and whether the deployment has one server or several diallers. Do not include passwords in the general contact form.

Agent count alone does not describe trunk requirements. Predictive campaigns create outbound attempts while other calls are ringing or connected. Concurrent channels describe simultaneous use; CPS describes the rate of new call attempts. Both must fit campaign control and the approved route.

Tell us the expected peak load, destinations, typical call duration and dialling mode. Capacity and call-attempt rate are agreed before launch rather than advertised as unlimited. A controlled ramp-up after the initial test campaigns can form part of the activation plan.

Connectivity involves the VICIdial carrier entry and the associated Asterisk dialplan. Authentication, SIP destination, transport, codecs and dial-prefix handling must match the connection parameters. A configuration example found online is not a reliable template for every installation.

Testing covers the called number and the From and P-Asserted-Identity headers. The agreed caller ID must be a number you are entitled to use. This service is not an offer for arbitrary caller ID spoofing or bypassing number restrictions.

A successful call setup is only part of acceptance testing. Busy responses, no answer, early media, two-way audio and clean hangup also matter. For one-way audio, for example, advertised media addresses and actual RTP paths need examination separately from SIP signalling.

For a specific issue, provide a timestamp with time zone, SIP Call-ID and a clearly defined symptom. Technical call examples should use an agreed transfer channel. ASR, ACD and PDD need interpretation in the context of destinations and campaigns, not as promises of a particular success rate.

We start by agreeing technical and commercial requirements. Connection parameters are then provided, agreed test destinations are checked and results reviewed together. Approval follows for the agreed traffic profile. The migration plan should also cover caller IDs, callbacks and existing inbound paths.

The offer is based on your requirements rather than an unsuitable generic flat rate. Tell us whether you are launching a new deployment, evaluating a second carrier or replacing an existing connection. That gives the VICIdial SIP trunk a clear role in your operation.