> ## Documentation Index > Fetch the complete documentation index at: https://doc.khcolo.com/llms.txt > Use this file to discover all available pages before exploring further. # Integrating 3CX with Bitrix24 CRM: Full Setup Guide > Connect 3CX to Bitrix24 for click-to-call, automatic call logging, screen pops, and full call history inside your CRM deal and contact cards. Bitrix24 is one of the most popular CRM and collaboration platforms used by businesses in Cambodia, and its native integration with 3CX is one of the deepest available. Once connected, your sales and support teams can dial contacts directly from Bitrix24 with a single click, have every call automatically logged to the relevant deal or contact card, and see incoming caller information before they even pick up the phone. This guide walks you through the complete setup from the Bitrix24 Marketplace through to verifying the integration is working. ## What You Will Get After Integration | Capability | Description | | --------------------------------- | ------------------------------------------------------------------------------------------------------------------- | | **Click-to-Call** | Dial any contact or lead phone number from Bitrix24 with one click — no manual dialing. | | **Automatic Call Logging** | Every inbound and outbound call is logged automatically as a CRM activity with duration, direction, and agent name. | | **Screen Pops** | When a known contact calls in, their Bitrix24 record opens on the agent's screen before they answer. | | **Call Recordings in Deal Cards** | Recordings attach directly to the relevant deal or contact in Bitrix24 for easy review. | | **Call History** | Full call history visible inside Bitrix24 contact timelines — no need to check 3CX separately. | *** ## Prerequisites Before starting, confirm you have: * A running 3CX installation with a valid license (see [Deployment Guide](/3cx/deployment)) * Administrator access to both your 3CX Management Console and your Bitrix24 account * Your 3CX server's **public IP address or FQDN** (e.g., `pbx.yourcompany.com.kh`) * Your 3CX **API Key** — found in the 3CX Management Console under **Settings > API** *** ## Integration Steps Log in to your Bitrix24 account as an administrator. In the left navigation menu, click **Applications** (or navigate to the **Marketplace** section, depending on your Bitrix24 version). In the Marketplace search bar, type **3CX** and locate the official **3CX Phone System** application. Click **Install** and accept the permissions prompt. Bitrix24 will add the 3CX integration module to your account. The 3CX app is available for both cloud-hosted Bitrix24 (bitrix24.com) and self-hosted Bitrix24 installations. The setup steps are identical for both. After installation, Bitrix24 will redirect you to the 3CX configuration screen. Enter the following details: | Field | What to Enter | | ----------------------- | --------------------------------------------------------------------------------------- | | **3CX PBX IP / FQDN** | Your server's public IP (e.g., `203.0.113.10`) or FQDN (e.g., `pbx.yourcompany.com.kh`) | | **Authentication Port** | The 3CX management HTTPS port — default is `5001` | | **API Key** | The API key copied from your 3CX Management Console | To generate or copy the API Key in 3CX, navigate to **Settings > API** in the Management Console. If no key exists yet, click **Generate** and copy the value before leaving the page — it will not be shown again in full. Click **Connect** (or **Save**). Bitrix24 will attempt to reach your 3CX server and confirm a successful handshake. A green status indicator confirms the connection is live. If the connection fails, verify that port `5001` (or your custom management port) is open on your firewall and accessible from the internet. Bitrix24's cloud servers need to reach your 3CX management interface to complete the handshake. If you are on a self-hosted Bitrix24, check that your Bitrix24 server can also reach your 3CX server. With the server connection established, navigate to the **Users / Extensions** mapping section within the 3CX app settings in Bitrix24. Bitrix24 will retrieve the list of extensions from your 3CX system. Map each 3CX extension to the corresponding Bitrix24 user account: | 3CX Extension | Bitrix24 User | | ------------- | ----------------------------------------------------------------- | | 101 | [sothea.chan@yourcompany.com](mailto:sothea.chan@yourcompany.com) | | 102 | [dara.kim@yourcompany.com](mailto:dara.kim@yourcompany.com) | | 103 | [linda.prak@yourcompany.com](mailto:linda.prak@yourcompany.com) | Once mapped, Bitrix24 recognizes which physical device or softphone belongs to each CRM user. This is what enables click-to-call to ring the correct agent's phone and attribute call logs to the right user account. Extensions that are not mapped will still log calls in Bitrix24, but the activity will be attributed to a generic "unknown agent" entry. Map all active extensions for accurate reporting. In the 3CX app settings within Bitrix24, review the **Click-to-Call** configuration: * **Default Click Action:** Set to *Call via 3CX* so clicking a phone number in any Bitrix24 contact or deal card triggers a call from the agent's mapped 3CX extension. * **Outbound Caller ID:** Confirm the outbound caller ID passed to 3CX matches the number you want contacts to see when agents call them. Run through each of the following tests to confirm everything is working end to end: **Test 1 — Click-to-Call:** Open any Bitrix24 contact that has a phone number. Click the phone icon next to the number. Your mapped 3CX extension should ring within a few seconds. Answer the call — it should connect to the contact's number. **Test 2 — Inbound Screen Pop:** From an external phone, call one of your DID numbers using a number that is saved as a Bitrix24 contact. On the answering agent's screen, the contact's Bitrix24 record should appear automatically. **Test 3 — Call Log:** After completing a test call, open the Bitrix24 contact record and check the **Timeline** tab. A call activity entry should appear with the call duration, direction (inbound/outbound), and the agent's name. **Test 4 — Recording in Deal Card:** If call recording is enabled on the agent's extension (see [Call Recording guide](/3cx/call-recording-crm)), verify that the recording file is accessible from the call activity entry in Bitrix24. If screen pops are not appearing, ensure the agent is logged into the 3CX Web Client or desktop app and that the Bitrix24 browser tab is open. The screen pop uses a browser notification mechanism that requires an active browser session. *** ## Troubleshooting Common Issues | Symptom | Likely Cause | Resolution | | -------------------------- | ---------------------------------- | --------------------------------------------------------------------- | | Connection failed at setup | Port 5001 blocked | Open port 5001 in your firewall for Bitrix24's IP ranges | | Click-to-Call not ringing | Extension not mapped | Re-check the extension-to-user mapping in Bitrix24 | | No call logs appearing | API Key expired or invalid | Regenerate the API Key in 3CX and re-enter it in Bitrix24 | | Screen pop not showing | Agent not logged into 3CX client | Ensure agent has an active 3CX Web Client or desktop app session | | Recordings not in Bitrix24 | Recording not enabled on extension | Enable call recording at Extensions > Forwarding Rules > Record Calls |