DRDialStop Reseller Preview User Guide
Back to Dashboard

Platform operating guide

The practical steps for preparing an account, running campaigns, handling transfers, and using SIP clients.

Before the first campaign

  1. Confirm the account has an active plan and enough balance.
  2. Open Caller IDs and create or import the caller ID pool for the destination.
  3. Prepare one audio file and a contacts file containing international-format numbers.
  4. For Press-1 campaigns, choose 3CX or Inbound SIP under Transfer Setup. Press-2 callback campaigns do not require transfer setup.
For Canadian numbers, choose Canada as the destination. Canada and USA both use country code +1, so this selection keeps routing and rates correct.

Campaigns

  1. Select New Campaign and choose Press 1, Press 2 Callback, or both.
  2. Add a name, audio, and contacts. Numbers should include the country code and should not include a leading plus sign.
  3. Choose a saved, fresh, or custom caller ID pool for this campaign.
  4. Set concurrency and destination. Transfer controls appear only when Press 1 is enabled.
  5. Review the campaign totals and select Start.

Inputs and callbacks

Press 1 sends the call to the configured transfer destination. Press 2 records a callback request, sends the Telegram alert, and adds the lead to the web Callback Inbox. Optional callback audio can confirm the request before the call ends.

Managing a campaign

Use Pause to stop new dialing while keeping the campaign available to resume. Use Stop to end the run. Retry Unreached queues failed or unanswered contacts. Retry Voicemail manually queues numbers whose latest result is voicemail; voicemail retries never start automatically.

Caller IDs

The Caller IDs tab stores the account pool used by SIP outbound and available for campaign snapshots. During campaign creation, choose that saved pool, generate a fresh campaign-only pool, or paste a custom pool.

  • Each campaign rotates through its own saved pool.
  • Changing the account pool later does not change an existing campaign.
  • Pause a campaign before replacing its caller IDs in Campaign Settings.

SIP outbound and 3CX

Softphone registration

  1. Open SIP Outbound and create the account if credentials are not present.
  2. Enter the username, password, and server in Zoiper, PortSIP, or another SIP client.
  3. Dial in international format. The platform selects the configured country route and charges the account rate.

Set up 3CX outbound calling

Use the IP-to-IP tab to connect your 3CX server. You need active DialStop Reseller Preview access, calling credit, and permission to manage trunks and outbound rules in 3CX. Field names may vary between 3CX versions.

1. Add your 3CX public IP in DialStop Reseller Preview

  1. Open IP-to-IP. Select Activate IP-to-IP if shown.
  2. Enter a connection name and the fixed public IPv4 address that your 3CX server sends SIP traffic from. For hosted 3CX, this is the PBX server's address, not your laptop, phone, or office IP.
  3. Choose UDP and A-law + U-law for this setup.
  4. Choose your caller-ID setting below, then select Add connection. Confirm that it appears under Approved connections.
Two different IPs: save your 3CX server's public IP in DialStop Reseller Preview. Enter 66.248.205.37 as the provider server in 3CX. Calls from the saved IP use this DialStop Reseller Preview account's balance. One public IP cannot be shared between different DialStop Reseller Preview IP-to-IP accounts.

2. Create the outbound trunk in 3CX

In the 3CX Admin Console, open Voice & Chat / SIP Trunks and add a trunk. Choose Generic and the IP-based SIP trunk option where available. Name it DialStop Reseller Preview Outbound. Keep your existing inbound and Press-1 transfer settings in place.

3CX fieldValue
Registrar / Server / Gateway66.248.205.37
SIP port5060
TransportUDP (matches the DialStop Reseller Preview connection)
Type of authenticationDo not require - IP Based
RegistrationOff; no SIP username or password is required
Outbound proxyLeave empty unless your template requires it; then use 66.248.205.37:5060
Audio codecsG.711 A-law (PCMA) and G.711 U-law (PCMU)
Main trunk number, if requiredA number your business owns or is authorised to use, in international format. This does not provision an inbound DID.

3. Add an outbound rule

  1. Open Outbound Rules and create DialStop Reseller Preview Outbound.
  2. Select the users, extensions, or department allowed to use this route.
  3. For a UK test, match numbers beginning with 44. Add rules for other destination country codes as needed.
  4. Set Route 1 to DialStop Reseller Preview Outbound, Strip digits to 0, and leave Prepend empty.
  5. Place the rule above another rule that would match the same call. Dial the country code and subscriber number as digits only, with no plus sign, spaces, or national leading zero.
Send the destination in international format, with the country code. Leave Prepend empty. If you intentionally use a local outside-line digit, strip only that digit before sending the international number.

4. Choose which caller IDs to use

  • Use DialStop Reseller Preview caller IDs on: prepare your authorised numbers in the Caller IDs tab. DialStop Reseller Preview selects from that pool for this connection.
  • Use DialStop Reseller Preview caller IDs off: set your authorised outbound caller ID in 3CX. DialStop Reseller Preview uses the number your PBX supplies. Do not send an extension number or anonymous identity as your outbound number. The optional DialStop Reseller Preview fallback is used when no valid caller ID is supplied.

5. Make one test call

Call a number you control from an extension covered by your outbound rule. Check ringing, two-way audio, and the displayed caller ID. In DialStop Reseller Preview, the connection's Last activity and SIP Outbound call history help confirm that the call reached the platform. An IP-based trunk does not register, so a registration indicator alone does not prove it can place calls.

  • No call or activity appears: check the outbound rule, the actual public source IP, the server/port, and that the connection is active.
  • Registration / authentication error: confirm the trunk is IP-based and is not trying to register with softphone credentials.
  • A call appears but fails: check access, balance, destination format, and caller ID. Send support your username, called number, time, and the error shown.
  • Call connects but audio is missing: check matching codecs, NAT, and the 3CX Firewall Checker.

3CX trunk and outbound-rule documentation · 3CX IP-based authentication

Receiving Press-1 transfers in 3CX

Outbound setup does not configure incoming Press-1 transfers. Connect the 3CX domain in the Telegram bot, then open 3CX Transfers on the website, save each queue or agent extension, and choose the destination when creating a campaign. Extension 1000 remains the default for older campaigns.

For separate systems, follow Two campaigns, two 3CX systems.

Bring Your Own SIP

Add the provider under My SIP Trunks, including its dial prefix when required. Campaigns using that trunk are sent through the user's provider; the provider handles its own call charges.

Two campaigns, two 3CX systems

Use one DialStop Reseller Preview account and a separate registered trunk for each 3CX system. Each campaign saves its own destination. You do not need to change the account default between campaigns.

CampaignConnectionReceives Press-1 calls
Campaign ATeam AQueue on 3CX system A
Campaign BTeam BQueue on 3CX system B

1. Prepare your account

You need active DialStop Reseller Preview access, calling credit and administrator access to both 3CX systems. In the DialStop Reseller Preview bot, open Transfer Setup, choose 3CX and finish the initial connection if needed. Keep an existing working connection unchanged.

2. Create both connections in DialStop Reseller Preview

  1. Open app.dialstop.net and select 3CX Transfers.
  2. Under Separate 3CX connections, enter Team A as the queue label and select Create registered trunk.
  3. Repeat with Team B. Each entry has its own username, password and main trunk number. Keep these details private.
Choose the right section: the ordinary Add destination form saves an extension on your existing connected PBX. It does not add another 3CX server. Use Create registered trunk for separate systems.

3. Configure 3CX system A

In the 3CX administration console, open Voice & Chat / SIP Trunks and add a Generic SIP / Generic VoIP trunk. Labels vary by 3CX version. Select Registration / Account-based authentication, not IP-based authentication.

3CX settingValue
NameDialStop Reseller Preview Team A
Registrar / server66.248.205.37
SIP port and transport5060, UDP
Authentication ID / usernameTeam A's generated username
Authentication passwordTeam A's generated password
Main trunk numberTeam A's generated number, exactly as shown
CodecsG.711 A-law and G.711 U-law
Incoming destinationThe queue, ring group or extension for Team A

Keep the generated main trunk number as the incoming number. Select your queue extension as the destination inside 3CX; do not substitute it for the generated trunk number. Check office-hours and closed-hours routing.

4. Configure 3CX system B

Repeat on the second system using Team B's generated details and its intended queue. Both systems connect to port 5060. Separate credentials identify the connections.

Never reuse the same credentials on two systems. Each trunk allows one registration contact. A second system using the same credentials can replace the first. These trunks receive Press-1 transfers; they are not your SIP Outbound credentials.

5. Choose the destination on each campaign

  1. Return to 3CX Transfers and check that both connections show ONLINE. Check any merely registered or offline connection before use.
  2. Create Campaign A with Press 1 enabled and select Team A - registered queue as its 3CX destination.
  3. Create Campaign B and select Team B - registered queue.
  4. For an existing campaign, pause it first, open Settings, choose its 3CX destination, save and resume.
  5. Test each campaign with a number you control. Press 1 and confirm the intended team receives the call with two-way audio before starting a larger run.

Each campaign keeps its chosen trunk and destination. Changing the account default does not retarget existing campaigns. Caller ID settings are separate from the transfer destination.

Troubleshooting

  • Connection section missing: finish the initial 3CX transfer setup in the bot, then refresh the website.
  • Registration rejected: check credentials, registration-based authentication, server and port. If this PBX already has another DialStop Reseller Preview connection, contact support. Do not delete working trunks or change firewall rules blindly.
  • Only one system receives calls: check for reused credentials and confirm both campaigns' saved destinations.
  • Wrong queue rings: check the receiving trunk's incoming destination and office-hours rules inside 3CX.
  • Cannot remove a trunk: first retarget or remove campaigns that use it. Deletion is blocked while a campaign references that registered trunk.

Send DialStop Reseller Preview Support your username, campaign name, connection label, test time and displayed error. Do not post passwords in group chats.

Official 3CX trunk setup reference

Inbound Team

Create agent credentials in Inbound Team and register each agent's softphone. Set the team as the transfer destination when Press-1 calls should enter the queue.

  • An available agent rings immediately.
  • Busy agents are skipped while they are on another call.
  • Queued calls remain available for another agent according to the configured queue timeout.

Payments and renewal

  1. Open Payments to renew access, top up calling balance or purchase a concurrency upgrade.
  2. Choose the payment network, create the invoice and send the exact crypto amount before its timer expires.
  3. The invoice changes from detected to confirming, then paid. The selected subscription or account credit is applied automatically.

Active weekly and monthly renewals extend the current expiry date. Expired access begins again when payment is confirmed.

Telegram bot

The bot and website use the same account. The bot can show account status, create top-up or subscription invoices, manage campaigns, generate caller IDs, and return SIP details. A change made in either place is reflected in the other.

Keep the web credentials somewhere safe. Telegram access should not be the only way to reach the account.

Call and campaign statuses

StatusMeaning
DialingThe outbound attempt has been created but is not ringing yet.
RingingThe destination is being alerted.
AnsweredThe destination answered and billable timing has started.
TransferredThe call entered the configured transfer path.
Congestion / FailedThe carrier or destination rejected the attempt before answer.
PausedNo new contacts are dialed until the campaign is resumed.
CompletedThe campaign has no remaining contacts in its current run.

Troubleshooting

Campaign will not start

Check the active plan, balance, contacts, audio, concurrency, and transfer destination. Correct the missing item and start again.

Calls fail immediately

Confirm international number formatting and the selected destination. For +1 numbers, explicitly choose USA or Canada.

SIP says Unauthorized

Re-enter the generated username and password. For 3CX, confirm its current public IP is saved against the correct account.

Transfers do not reach an agent

Confirm the agent is registered, the Inbound Team is selected as transfer destination, and at least one agent is available.

Still blocked

Send the username, campaign name, destination number, and approximate call time to DialStop Reseller Preview Support.