PBX Integration
How to connect a DID to 3CX PBX
Use this guide to connect DIDfarm numbers to 3CX with a clear registration-based SIP trunk setup and predictable inbound and outbound routing.
3CX
Platform focus
GUI
Setup style
6 min
Guide length
Live
Connector status
3CX-first workflow
Built around the way 3CX admins actually create SIP trunks, assign DIDs, and validate call routing.
Inbound DID mapping
Connect the main DID and send each number to the right receptionist, queue, extension, or IVR.
Outbound rule check
Make sure outbound routes and caller ID formatting are correct before production use.
Before you begin
Make sure the PBX, network, and DIDfarm credentials are ready before you start the setup.
1
DIDfarm SIP credentials
Have the SIP server, auth ID, password, and your main DID ready before creating the trunk.
2
3CX admin access
You need the ability to create a trunk, set inbound routing, and adjust outbound rules.
3
DID list prepared
Decide which DIDfarm numbers will terminate on which users, ring groups, or IVRs.
4
Network access confirmed
Confirm the PBX can reach the DIDfarm SIP server and that firewall rules allow signaling and media.
Setup flow
1
Create the trunk
In 3CX, add a new SIP trunk and enter the DIDfarm server, authentication ID, password, and main DID.
2
Assign inbound routes
Choose the default inbound destination and add any extra DIDs that should ring elsewhere.
3
Configure outbound calling
Update outbound rules so calls leave through DIDfarm using the intended caller ID.
4
Test before launch
Place inbound and outbound calls, confirm registration status, and validate caller ID presentation.
Copy-paste example
Use this as the starter reference for your connector article or portal snippet output.
Example configuration
Provider: DIDfarm
Registrar / Server: sip.didfarm.com
Auth ID: {didfarm_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 default and specific DIDs.
- Outbound route order does not conflict with another provider.
- Caller ID formatting complies with destination-country rules.
Operational notes
| Check | What to confirm |
|---|---|
| Registration | Confirm the 3CX trunk shows as registered before testing DIDs. |
| Inbound routing | Test both the main DID and at least one secondary DID if configured. |
| Outbound CLI | Check that the expected DID is presented for outbound calls. |
| Failover | If you use multiple trunks, verify rule priority and fallback behavior. |
Make 3CX onboarding feel instant
A polished DIDfarm-to-3CX guide reduces setup friction and makes your SIP trunk offer feel implementation-ready.
Open PBX Integration →