Setting Up Outbound Telephony in Bitrix24

A manager clicks on a phone number in a contact card — and the call does not go through. Or it goes through, but the caller ID shows "Unknown Number". Or the call is recorded in the CRM but without conversation recording. Sound familiar? We encounter this every day. Setting up outbound telephony in Bitrix24 is not just about connecting a number, but a series of related decisions: which channel (WebRTC, SIP phone, desktop client), which CallerID to display, how to link calls to deals, where to save recordings, and how to charge. Let's break down each aspect with concrete examples. Our team has 10+ years of experience in telephony integration with Bitrix24 and has completed over 100 projects, guaranteeing a reliable setup.

Problems We Solve

Problem 1: Client does not see company number. If CallerID is not configured for each employee, outgoing calls may appear as unknown or with the portal's common number. This reduces trust and increases hang-ups. We set up individual CallerID: for sales managers — city number, for support — short number. Our experience shows that after this configuration, the answer rate increases by 25%.

Problem 2: Calls are not linked to CRM. Without proper linking, the manager wastes time manually creating activities, and deals lose context. When using a SIP trunk, the error "invalid SIP login" or "insufficient balance" often occurs. We verify account registration, synchronize numbers, and configure automatic activity creation with a link to the company and contact. We guarantee that every call appears in the right deal.

Problem 3: Call recordings are not saved or lost. Bitrix24 supports call recording, but only with correct server configuration and permissions. A typical mistake is not enabling the "Record conversations" checkbox in the number settings, or insufficient disk space on the cloud side. We set limits, configure automatic cleanup, and integrate with external storage (e.g., Amazon S3) so recordings are stored for years.

How We Do It: Case Study of SIP Trunk Configuration with Mango Telecom

One client — an online store with 50 managers. Needed to set up outbound telephony via a SIP trunk so that each manager calls from a unique city number, and recordings go to CRM and Google Drive for backup. We performed:

• Registered a SIP account with Mango Telecom supporting 50 concurrent lines.
• Configured external PBX in Bitrix24: Administration → Telephony → Connect PBX → SIP trunk.
• Specified parameters: server: sip.mango.ru, port: 5060, transport: UDP, auth: login/password.
• For each manager, set an individual CallerID from the number pool in telephony settings.
• Enabled automatic deal creation from calls and call recording with a 30-day rotation.
• Configured integration with Google Drive via app.bitrix24.ru for recording synchronization.

Result: managers call in one click, clients see the city number, deals are not lost, recordings are available in CRM and in the cloud. The project took 8 hours (including coordination with the operator). According to Bitrix24 Telephony Setup Guide, this configuration is optimal for medium business.

How to Set Up CallerID for Different Employees?

CallerID is the number that the client sees when an employee calls. In Bitrix24, you can set it for each user individually: Telephony → Employee settings → select user → field "Number for outgoing". If not specified, the portal's common number will be used. For departments, it is convenient to set a rule: "For sales department managers — 495xxxxxxx", "For support — 800xxxxxxx". Our team automates this using Bitrix24 agents, assigning numbers from the pool when new employees are added.

Why Is Call-to-CRM Linking Important?

Without linking, every outbound call is a "blind" event: the manager spends 2-3 minutes manually creating an activity, and may not remember which deal the call relates to. With correct configuration, the call automatically pulls up the company, contact, and deal, records the conversation, and creates a task for a callback if not reached. We always enable the "Create CRM activity" option in the number settings and verify that all managers have permissions to view/edit cards.

Process

What's Included

• Connecting cloud PBX or SIP trunk (choose operator, configure account)
• Configuring CallerID for all employees or departments
• Setting up WebRTC/Desktop client/SIP phone for each workstation
• Linking calls to CRM (create activities, attach recordings, connect with deals)
• Configuring call recording and its storage (cloud or local)
• Creating brief documentation for managers

Timeline (Estimated)

• Basic setup (1-2 numbers, WebRTC, CRM linking) — from 2 hours.
• Complex setup (5+ numbers, SIP trunk, different CallerID, Google Drive integration) — from 8 hours to 2 days.
• Pricing is calculated individually based on scope and complexity. We evaluate the project for free after analyzing your current settings.

Contact us for a telephony diagnostic. We will evaluate your current configuration and offer a turnkey setup plan. Get a free consultation.

Turnkey Telephony Setup: From SIP to CRM

SIP trunk not registering — the first problem when connecting telephony to Bitrix24. The client sends provider data, you enter it in "Telephony → Telephony Settings → SIP Connector", and the status hangs "Waiting for registration". Ports 5060/5061 for SIP and range 10000–20000 for RTP are blocked on the firewall — classic. Or codec G.729 is not supported, and G.711 consumes 87 kbit/s per line. For 20 simultaneous conversations — count yourself. We connect and configure telephony so that calls are not lost, routing works according to business logic, and CRM receives data automatically.

SIP (Session Initiation Protocol) — standard for voice communication over the internet. Our specialists have 5+ years of experience integrating with Bitrix24. Warranty on configured solutions — 1 year. Contact us for a free audit of your current infrastructure — we often find blind spots: missed calls without tasks, managers with status "On line" and zero calls, IVR branches that no one reaches.

How to Avoid Failures in SIP Registration and Connection?

Improper NAT, closed ports, or incompatible codecs — 90% of failures. We check codec support on the operator's side, configure keepalive and backup SIP servers. After setup, registration stays stable for months.

You already have a contract with an operator, and changing numbers is not an option. We connect to Bitrix24 via SIP connector. For stable operation, you need a channel: at least 100 kbit/s per line for G.729, 87 kbit/s for G.711a.

Typical tasks:

• City numbers from any operator — preserved when switching to B24
• 8-800 numbers for inbound — routing via CRM
• Multi-line numbers with department distribution via IVR
• Analog lines via Grandstream or Linksys VoIP gateways

Where it usually gets stuck:

• SIP/RTP ports are closed at the provider or router level
• NAT not forwarded correctly — one-way audio
• Different codecs on the PBX and Bitrix side — no audio at all

We solve these problems in 1–3 days, not weeks.

Step-by-step instructions for connecting via SIP trunk:

1. Check SIP (5060/5061) and RTP (10000–20000) ports are open on the firewall.
2. Agree on codecs: G.711 or G.729 — test both options.
3. Configure SIP connector in Bitrix24 admin: login, password, provider domain/IP.
4. Enable keepalive (30–60 second interval) for stable registration.
5. Test two-way audio with a test call.
6. Configure backup SIP server in case of primary failure.

Cloud PBX or SIP Trunk: Which to Choose?

Cloud PBX requires no hardware — set up in 1–2 days. SIP trunk retains your numbers and allows a hybrid scheme with an on-premise PBX. Cloud PBX is configured 2-3 times faster and saves up to 40% of budget compared to maintaining your own infrastructure. Compare providers based on real cases.

Why Do You Need Call Recording and How to Set It Up?

All incoming and outgoing calls are recorded automatically. Storage — Bitrix24 cloud (tariff limited) or your own server via the voximplant module. Each recording is attached to a CRM card: contact, deal, lead. Listening — from the deal timeline.

Control tools:

• Recording notification — mandatory under 152-FZ, configured in IVR
• AI transcription — speech recognition via built-in CoPilot module or external service. Converts calls to text, searchable by keywords
• Sentiment analysis — system flags negative calls. Not a replacement for listening, but filters 90% of routine
• Selective recording — only incoming, only specific departments
• Automatic duration control — calls shorter than 15 seconds almost always indicate a problem: dropped, not reached, manager didn't pick up

Manager sees summary reports: number of calls per manager, average duration, missed calls without callbacks. The last point is the most painful: a missed call without a callback task equals a lost client.

Typical Routing Mistakes

Routing is the most fragile part. Set up "in order", but the manager logged in and went to lunch — the call hangs for 40 seconds and drops. Or IVR with five nesting levels — the client hangs up on the third. We use working distribution scenarios:

• By CRM responsible — number found in database, call goes directly to manager
• In order — even load among operators with "On line" status
• By departments via IVR — voice menu, max two levels. More means lost calls
• By time — working/non-working hours, weekends
• By region — detected by number code, distributed to local managers

On incoming call, the system performs: Number found in CRM:

• Route to responsible manager
• Pop-up card: name, company, open deals, contact history
• If manager doesn't answer within 15 seconds — forward to colleague, then to supervisor

Number not found:

• Automatically creates a lead in CRM (setting Telephony → CRM Integration → Create lead for unknown number)
• Call distributed by queue
• All information recorded for later processing

How to Automate Work with CRM Integration?

Pop-up card on incoming call shows:

• Name, company, position
• Current deals with statuses
• Last 5 interactions — calls, emails, chats
• Customer comments
• Buttons: "Create deal", "Set task", "Transfer call"

Automation via business processes is configured in "CRM → Robots and triggers":

• Missed call → lead + callback task for responsible
• Call end → record activity in deal timeline
• Missed without callback within 30 minutes → notify supervisor
• Incoming from client with overdue deal → escalation

Analytics available in "Telephony → Balance and statistics" and CRM reports:

• Number of calls by manager, department, direction
• Average duration and hold time
• Missed call percentage with weekly trend
• Call-to-deal conversion — most important metric for sales

How to Increase Conversion with Callback, Auto-dialer, and Voice Menu?

"Call me back" widget on website — one field (phone), nothing extra. The system calls the manager first, then the client. Each request automatically creates a lead in CRM. Anti-spam: limit requests from one number. A/B testing placement — widget bottom right converts better than left, but depends on design. Callback reduces missed calls by up to 30% compared to manual dialing.

Auto-dialer:

• Dial segment from CRM — manager connects after client answers
• Robotic dial with voice message — order confirmations, appointment reminders
• IVR scenarios: "press 1 to confirm"
• Scheduled with time zone awareness — module checks region by number code

Building a voice menu:

• Welcome message — company name, recording notice
• Department selection via DTMF — max 4–5 items
• Music on hold with queue position
• Non-working hours — voicemail or informational message

Recording by professional voice actor — worthwhile for greeting and main menu. Deeper levels — speech synthesis, easier to update.

What's Included in Telephony Setup?

Deliverables after project completion:

• Configured SIP registration (cloud PBX or SIP trunk turnkey)
• Working call routing (by CRM, queue, IVR)
• Call recording with cloud or server storage
• CRM integration: pop-up cards, auto lead creation, business processes
• Callback widget on website
• Voice menu (IVR) with voice actor recording or synthesis
• Configuration documentation and staff training (2 sessions)
• Technical support for one month after launch

Everything included in the comprehensive setup — no hidden extras. Order telephony setup and get a ready-made infrastructure for working with clients.

Setup Timeline and Pricing

Pricing is calculated individually — depends on number of lines, routing complexity, and required integrations. Average budget for setup ranges from several thousand to tens of thousands in local currency depending on scope. We'll evaluate your project in 1 day. Start with a free audit of your current infrastructure — we often find blind spots: missed calls without tasks, managers with "On line" status and zero calls, IVR branches that no one reaches. Contact us for a consultation — we'll offer the optimal solution for your budget and business processes.