Inbound DID routing
Map any DIDHub DID to a 3CX extension, queue, IVR, or auto-attendant via a single inbound rule.
Connect 3CX to DIDHub in five minutes. SIP trunk template included, inbound and outbound rules configured, numbers from 80+ countries — all from the 3CX management console.
3CX is one of the most-deployed business phone systems globally — both as a self-hosted PBX and as 3CX-hosted. DIDHub plugs in as a standard SIP trunk provider with the official 3CX SIP trunk template, no special drivers or modules required. Once connected, every DIDHub DID behaves like a native 3CX extension target: route inbound to queues, IVRs, and ring groups; send outbound with the right Caller ID per number; record calls; bridge to softphones and the 3CX mobile app.
3CX users typically come to DIDHub for one of three reasons: (1) international expansion — adding country DIDs (UK, DE, FR, IL, JP, AU, BR…) without negotiating a separate carrier per market, (2) cost reduction — flat per-DID pricing meaningfully cheaper than 3CX-bundled SIP trunks at scale, or (3) regulatory coverage — getting numbers in countries 3CX's bundled providers don't cover (Israel, India, Saudi Arabia, etc.).
DIDHub uses the standard 3CX SIP trunk template. Five steps from signup to first call.
Create a DIDHub account at didhub.io. Pick a number in any country. Activates instantly on most markets.
In 3CX Management Console: SIP Trunks → Add SIP Trunk. Pick country = (your DID's country), provider = Generic SIP Trunk.
DIDHub provides a credentials block (host, username, password, registrar, port). Paste into the 3CX template.
Map the DIDHub DID to a 3CX extension, queue, or IVR. Set DID → destination.
Create an outbound rule that uses the DIDHub trunk for the DID's country. Set the outbound Caller ID to the DIDHub DID.
Call out from a 3CX extension; call inbound to the DID. Both legs route via DIDHub.
The exact trunk values DIDHub provisions for your account. Pre-fill these in the 3CX trunk-config UI:
# DIDHub SIP trunk values — 3CX Generic SIP Trunk template Registrar / Server: sip.didhub.io Port: 5060 (UDP/TCP) or 5061 (TLS — recommended) Username: didhub_xxxxxx (provisioned per trunk) Auth ID: didhub_xxxxxx (same as username) Password: (provisioned per trunk; rotate via dashboard) Outbound Proxy: edge.didhub.io Public IP / NAT: enabled (3CX → STUN-managed) Codec preference: G.711 a-law / μ-law, OPUS optional DTMF: RFC2833 (default)
DIDHub strongly recommends TLS + SRTP for production trunks (port 5061, transport TLS, SRTP=Required). Plain UDP works for testing but exposes credentials and call audio.
Map any DIDHub DID to a 3CX extension, queue, IVR, or auto-attendant via a single inbound rule.
Per-trunk or per-extension Caller ID — match the calling extension to the right country DID.
3CX-native recording works on DIDHub trunks. Server-side recording on DIDHub edge available too (separate channels per leg).
DIDHub signs every US/CA outbound call with attestation A — Caller ID arrives unspamflagged.
SMS-capable DIDHub DIDs can deliver inbound SMS to 3CX via webhook + the 3CX SIP MESSAGE/Chat connector.
Add as many trunks as you have countries — each gets its own SIP credentials and routing rules.
Yes. The 3CX hosted offering uses the same SIP trunk template as on-prem; DIDHub plugs in identically.
All currently-supported 3CX versions (V18, V20, V20 SP1+). DIDHub uses standard SIP — no version-specific quirks.
Strongly recommended. DIDHub provides SIP TLS + SRTP on the 5061 trunk. Plain UDP transmits credentials in clear text and is fraud-prone.
Yes — via 3CX's Teams integration, calls bridge through 3CX. For pure Teams Direct Routing without 3CX, see Teams Direct Routing.
Each DIDHub DID has its own outbound trunk (or shared via inbound headers). 3CX's outbound rules let you select the trunk per extension or per dialed prefix.
FreePBX · Asterisk · FusionPBX · Teams Direct Routing · Softphones
Pick a DID in 80+ countries from $1.99/month. Activates instantly on most numbers.