What do you need from our dialer?
The details we ask for before connecting, and why each one matters.
The bot runs alongside ViciDial and Morpheus dialers over a SIP trunk. Your dialer places the call, and once someone answers it hands the call to the bot. Before we can connect, we need:
- The IP address of every dialer server that will send calls. Calls from any other address are refused.
- Your dialer's address and SIP port. We do not assume the standard port.
- The campaign ID the bot will work.
- An unused carrier dial prefix on your dialer, which we use to route calls to the right bot.
- The in-group or queue where qualified transfers should land, and a number on your dialer that routes to it. Outbound-only dialers often need these created first.
- Optionally, a dialer API user, so outcomes and do-not-call entries can be written back automatically.
Allowlisting works both ways
We allow your dialer's addresses in, and you allow ours, so that outcomes can be written back and the connection test can reach you. If one side is missing, the usual symptom is bot seats sitting READY while the campaign dials and drops.
More than one dialer
Each dialer install is its own connection. You can have several, and the dashboard, reports and call list can all be filtered by dialer.