How to connect a DID to 3CX PBX

PBX Integration · 6 min read 3CX GUI setup
Connect Cliqtel numbers to 3CX in minutes. This guide walks through a clean, registration-based SIP trunk in 3CX with predictable inbound DID mapping and outbound caller-ID routing — built around the way 3CX admins actually work.

Overview

3CX registers to the Cliqtel SIP server as a SIP trunk. Inbound calls to your DIDs arrive on that trunk, and you route each number to the right receptionist, queue, extension, or IVR. Outbound calls leave through Cliqtel using a caller ID you control. This article covers the trunk setup, inbound DID mapping, and the outbound rule check to run before you go live.

Before you begin

Make sure the PBX, network, and Cliqtel credentials are ready before you start.

  • Cliqtel SIP credentials — have the SIP server, auth ID, password, and your main DID ready before creating the trunk.
  • 3CX admin access — you need to be able to create a trunk, set inbound routing, and adjust outbound rules.
  • DID list prepared — decide which Cliqtel numbers terminate on which users, ring groups, or IVRs.
  • Network access confirmed — confirm the PBX can reach the Cliqtel SIP server and that firewall rules allow signalling and media.

Setup flow

1Create the trunk

In 3CX, add a new SIP trunk and enter the Cliqtel server, authentication ID, password, and main DID.

2Assign inbound routes

Choose the default inbound destination, then add any extra DIDs that should ring elsewhere — a receptionist, queue, extension, or IVR.

3Configure outbound calling

Update outbound rules so calls leave through Cliqtel using the caller ID you intend to present.

4Test before launch

Place inbound and outbound calls, confirm the trunk shows as registered, and validate caller-ID presentation.

Example configuration

Use this as the starter reference when you create the trunk in 3CX.

SIP trunk settings
Provider:            Cliqtel
Registrar / Server:  sip.cliqtel.com
Auth ID:             {cliqtel_auth_id}
Password:            {generated_secret}
Main DID:            {e164_main_number}
Transport:           UDP / TCP / TLS
What to verify:
  • Main DID format matches what 3CX expects.
  • Inbound destination is set for both the default and any specific DIDs.
  • Outbound route order does not conflict with another provider.
  • Caller-ID formatting complies with destination-country rules.

Operational notes

CheckWhat to confirm
RegistrationConfirm the 3CX trunk shows as registered before testing DIDs.
Inbound routingTest both the main DID and at least one secondary DID if configured.
Outbound CLICheck that the expected DID is presented for outbound calls.
FailoverIf you use multiple trunks, verify rule priority and fallback behaviour.

Make 3CX onboarding feel instant

Browse every connector on PBX Integration, or see the related guides below.

Open PBX Integration →
Related articles