Telephony for Bitrix24 and 1C-Bitrix

SIP Registration — Where Everything Breaks Down

The first thing that goes wrong when connecting telephony to Bitrix24 — the SIP trunk fails to register. The client sends credentials from the provider, you enter them in "Telephony → Telephony Settings → SIP Connector," and the status stays at "Awaiting Registration." Ports 5060/5061 for SIP and range 10000–20000 for RTP are blocked by the firewall — a classic scenario. Or the G.729 codec isn't supported, and G.711 consumes 87 kbps per line. With 20 simultaneous calls — do the math.

We connect and configure telephony so that calls aren't lost, routing follows business logic, and the CRM receives data automatically.

Cloud PBX

Cloud PBX — no hardware in the office, no capital expenditure on Asterisk or FreePBX. The provider maintains the infrastructure, you pay for lines.

Setup takes 1–2 days. A new extension — a couple of clicks in settings. Office relocation — nothing changes at all, it works over the internet from anywhere.

Providers and Their Specifics

SIP Trunks: Connecting Existing Telephony

You already have a contract with a carrier, changing numbers isn't an option. We connect to Bitrix24 via the SIP Connector (section "Telephony → SIP Connector PBX").

A SIP trunk is a virtual channel between your PBX (or carrier) and Bitrix24 over the SIP protocol. No physical wires needed, but you do need a stable connection: minimum 100 kbps per line for G.729, 87 kbps for G.711a.

Typical tasks:

• City numbers from any carrier — preserved when migrating to Bitrix24
• Toll-free 8-800 numbers for inbound calls — routing through CRM
• Multi-channel numbers with department-based distribution via IVR
• Analog lines through VoIP gateways from Grandstream or Linksys

Where it usually stalls:

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

Call Recording and Quality Control

How Recording Works

All inbound and outbound calls are recorded automatically. Storage — Bitrix24 cloud (limited by plan) or your own server via the voximplant module. Each recording is linked to a CRM record: contact, deal, lead.

Playback — directly from the deal timeline or contact card. Download — for archiving or review with legal.

What Actually Works for Quality Control

• Recording notification — mandatory under 152-FZ, configured in the IVR before connection
• AI transcription — speech recognition via the built-in CoPilot module or an external service. Converts the call to text, searchable by keywords
• Sentiment analysis — the system flags calls with negative tone. Not a replacement for listening, but filters out 90% of the routine
• Selective recording — inbound only, specific departments only (configured in "Telephony → Number Settings")
• Automatic duration monitoring — calls shorter than 15 seconds almost always indicate a problem: hung up, couldn't get through, agent didn't pick up

Managers see summary reports: call counts per agent, average duration, missed calls without callback. That last one is the most painful: a missed call without a callback task = a lost customer.

Routing: Where 70% of Errors Happen

Routing is the most fragile part. Set up "round-robin," but an agent logged in and went to lunch — the call rings for 40 seconds and drops. Or an IVR with five nesting levels — the customer hangs up on the third.

Working Distribution Scenarios

• By CRM owner — number found in the database, call goes straight to the assigned agent. Configured via "Telephony → Inbound Routing → Route to CRM Owner"
• Round-robin — even load distribution among agents with "Online" status
• By department via IVR — voice menu, two levels maximum. More than that — lost calls
• By schedule — business hours / after hours, weekends. Different scenarios for each
• By region — determined by area code, routed to local agents

What Happens on an Inbound Call

Number found in CRM:

• Call is routed to the assigned agent
• Pop-up card: name, company, open deals, interaction history
• If the agent doesn't answer within 15 seconds — forwarded to a colleague, then to a supervisor

Number not found:

• A lead is automatically created in CRM (setting: Telephony → CRM Integration → Create lead for unknown number)
• Call is distributed via round-robin
• All information is recorded for follow-up

CRM Integration

Pop-up Card

On an inbound call, the agent sees:

• Name, company, position
• Current deals with statuses
• Last 5 interactions — calls, emails, chats
• Notes about the customer
• Buttons: "Create Deal," "Assign Task," "Transfer Call"

Automation via Business Processes

Configured in "CRM → Robots and Triggers":

• Missed call → lead + callback task for the assigned agent
• Call ended → activity logged in the deal timeline
• Missed call without callback within 30 minutes → manager notification
• Inbound from a client with an overdue deal → escalation

Analytics

Section "Telephony → Balance and Statistics" + CRM reports:

• Call counts by agent, department, direction
• Average duration and hold time
• Missed call percentage with weekly trend
• Call-to-deal conversion — the most important metric for the sales team

Callback and Auto-dialing

Callback Widget

A "Call Me Back" button on the website — one field (phone number), nothing extra. The system dials the agent first, then the customer. Every request automatically creates a lead in CRM.

Anti-spam: request rate limiting per phone number. A/B testing of placement — a widget in the bottom-right converts better than the left, but depends on the design.

Auto-dialing

• Outbound calling by CRM segment — agent connects after the customer answers
• Robocall with voice message — order confirmations, appointment reminders
• IVR scenarios: "press 1 to confirm"
• Scheduling with timezone awareness — the module checks the region by area code

IVR (Voice Menu)

• Welcome message — company name, recording notification
• Department selection via DTMF (tone dialing) — 4–5 options maximum
• Hold queue with music and position announcement
• After-hours — voicemail or informational message

Professional voice-over recording makes sense for the greeting and main menu. Deeper levels — use text-to-speech, easier to update.

Timelines

We start with an audit of the current infrastructure — call volume, existing numbers, business processes. We often find "blind spots": missed calls without tasks, agents with "Online" status and zero calls, IVR branches that nobody ever reaches.