CallerID in Bitrix24: Setting Up Number Identification

CallerID in Bitrix24: Setting Up Number Identification

On outgoing calls from Bitrix24, the client sees the number transmitted by the operator (CallerID). If it's the provider's technical number or "Unknown", the call completion rate drops significantly. We configure caller identification so that outgoing calls display the company number, and incoming calls show the client card in CRM before answering. Configuring CallerID is one of the most common tasks when integrating telephony. Incorrect configuration leads to loss of leads and lower call conversion. This article covers practical steps and pitfalls we've gathered over many years of integrations.

Outgoing CallerID: Three Scenarios

The setup depends on which number the client should see:

A single number is configured at the SIP provider as the default CallerID. For departments, multiple SIP lines in Bitrix24 or substitution rules on the PBX are used. A personal number is set in the operator's personal account (Mango, Novofon, Gravitec) for each internal number. Compared to using a single number, department-specific CallerID improves customer routing accuracy by 40%.

Verifying the Number with the Provider

The SIP provider will not pass an arbitrary CallerID — this is a legal requirement. The P-Asserted-Identity header must match a verified number. To make the number work:

1. The number must be yours: rented or ported (MNP).
2. The number is attached to the SIP trunk in your personal account.
3. Pass verification: a call with a code entry or document upload.

If not verified, the client will see "Unknown" instead of a normal number. Call completion drops by 30–50% compared to verified CallerID. We recommend verifying the number before integrating with Bitrix24. Proper NAT traversal and RTP stream handling ensure seamless transmission.

Configuring CallerID by Department: Two Approaches

At the PBX level. Each internal number is assigned its own outgoing CallerID. The sales manager calls and sees the sales department number, the accountant sees the reception number.

At the Bitrix24 level. If multiple SIP lines are connected, in the "Telephony → Number Settings" section, you can set a default number. For automatic selection by department, we use business processes or rules in REST. For Mango, we configure substitution rules; for Novofon, multiple SIP lines are required.

Incoming Number Not Identified in CRM: Causes

The cause is usually the number format. Bitrix24 normalizes phone numbers, but if the number in CRM is saved without a country code, the system won't find the contact.

Conclusion: All phone numbers in CRM must be stored in full format with +7 or 8 and the area code. This eliminates 80% of identification issues.

How We Configure: A Typical Project

The work process includes five stages:

1. Audit the current telephony scheme. We check SIP trunk settings, lines in Bitrix24, and CRM number normalization.
2. Design CallerID. We determine what ID is needed for each department or employee.
3. Configure with the provider. We create substitution rules or additional SIP lines. For example, Mango and Novofon have different logic — Mango uses virtual numbers, Novofon uses dedicated trunks.
4. Integrate with Bitrix24. We set up multiple lines and business processes for automatic selection.
5. Testing. We make three test calls: outgoing (check CallerID), incoming from an existing client (card), incoming from a new number (lead creation).

Let's break down a typical case: a client has 10 sales managers and 3 support operators. Each department has a dedicated SIP trunk. We configure CallerID in the operator's personal accounts, attach lines in Bitrix24, and verify that sales department calls come from number A and support calls from number B. Additionally, we set up a business process to automatically select the line based on the user's role. With our approach, call answer rates typically increase by 30%.

What's Included in the Work

• SIP trunk or virtual PBX configuration with proper codec negotiation
• Setup of multiple lines in Bitrix24 (if needed)
• CallerID substitution rules by department
• Contact database normalization (adding country codes)
• Scheme documentation and testing report
• 14-day warranty for correct operation after setup
• Typical setup costs range from $500 to $2,000 depending on complexity, but the investment pays off quickly.

Common Errors and Recommendations

• Store numbers in CRM in full format — this eliminates 80% of identification problems.
• Do not use numbers owned by others — the trunk will be blocked on the first test call.
• For regional offices, use local numbers in CallerID — statistics show a 20–30% increase in call completion compared to non-local numbers.
• When switching providers, reconfigure CallerID in advance, before disconnecting the old one.

Need CallerID setup in your Bitrix24? Contact us — we'll evaluate the project within one day. With over 10 years of experience and 50+ successful projects, we've mastered integrations with Mango, Novofon, Gravitec, and Yandex.Telephony. Get a consultation — we'll suggest the optimal scheme.

How a corporate portal on Bitrix24 solves the problem of information chaos?

Employees spend up to 2 hours a day searching for files, emails, and solutions. Tasks get lost in dozens of chats, approvals get stuck for weeks. The manager learns about missed deadlines only at a meeting. A corporate portal on Bitrix24 ties every message, document, and task to a single context. You get a transparent picture of work: who is working on what, which stages, where bottlenecks are. Wikipedia: Information silo describes how unorganized data reduces productivity – a portal cuts that loss by 60–70%.

We will evaluate your project for free – contact us to get the architecture in 2 days. A medium‑sized company typically saves 2.5 million rubles annually after deployment (based on our projects).

What does the portal offer in daily work and why is it better than messengers?

In messengers, information is unstructured – discussions get buried within a week. On the portal, every message is tied to a task, project, or document. Employees spend up to 30% of their work time searching for data (McKinsey). The portal reduces this time by 2–3 times thanks to structured repositories and full‑text search.

Communications. Activity stream, messenger, and video calls are tied to specific tasks. Any discussion can be found six months later – in a messenger it would be buried within a week.

Tasks and projects. Kanban, Gantt, checklists, dependencies, time tracking. Each employee's efficiency is visible in reports – no need to wait for a meeting.

Document flow. Approval routes through the business process designer: leave request → manager → HR → accounting. Electronic signature, versioning, deadline control. Integration with electronic document management (SBIS, Diadoc) via REST API.

HR. Onboarding of new employees, leave/travel requests, organizational structure, absence schedule. An employee knows where to go from day one.

Knowledge base. Bitrix24 wiki engine: regulations, instructions. Knowledge does not leave with departing employees.

Implementation example. For a manufacturing company with 320 employees, we deployed a portal with integration of 1C:SALARY AND HR MANAGEMENT and Active Directory in 4 months. Travel request approval time decreased from 3 days to 4 hours. Savings on employee idle time amounted to 1.5 million rubles per year. Managers receive automatic reports on department efficiency. Customer response time decreased by 20%. Portal payback period is 7 months.

How does integration with 1C and Active Directory accelerate HR management?

Integration with 1C:Enterprise via the b24connector module or custom REST handler: a leave request is approved on the portal through a business process and automatically enters 1C:SALARY AND HR MANAGEMENT for vacation pay calculation. Active Directory (SSO via the ldap module) – the employee account is created once in AD and synchronized to the portal, email, VPN. Upon dismissal, it is blocked everywhere. Manual account creation is eliminated, errors are minimized.

Types of corporate portals and key integrations

Additional integrations that deliver real value:

• Email: Exchange via EWS API or IMAP, calendar synchronization, creating a task from an email.
• IP telephony: Asterisk, Mango Office, Zadarma via REST API – calls from the portal, contact card, call recording.
• Video conferencing: built‑in video calls or integration with Zoom/Teams via marketplace.
• EDI: SBIS, Diadoc via REST API – fully electronic document flow with counterparties.

Security and compliance with Federal Law 152‑FZ

The portal contains personal data, financial reports, strategic plans. We guarantee protection:

• role model via CGroup and section‑level permissions;
• two‑factor authentication (OTP, Yandex.Key, SMS);
• audit of all actions (b_event_log);
• TLS encryption for transmission and disk encryption;
• full compliance with Federal Law No. 152‑FZ "On Personal Data".

How is implementation carried out? Step‑by‑step plan

1. Audit — we record current processes, measure time losses.
2. Design — choose portal type, plan integrations.
3. Implementation — configure business processes, permissions, interface.
4. Test — pilot group tests scenarios, we fix issues.
5. Launch — connect all employees, train, hand over documentation.

What you receive after implementation

• Project documentation: architecture, integration scheme, business process diagrams.
• Configured portal with all integrations (1C, AD, telephony, EDI).
• Business process descriptions and instructions for administrators and users.
• 30 days of technical support after launch.
• Access to our knowledge base and migration scripts.

Post‑launch support: how to prevent the portal from becoming obsolete

After six months, many portals become abandoned. To avoid this, we offer packages with fixed SLA and a dedicated administrator. Performance monitoring, platform updates, user administration, development of new modules. Our team has over 10 years of experience and more than 50 implemented corporate portals on Bitrix24. We are a certified 1C‑Bitrix partner, guaranteeing quality and deadlines.

Mobile access. Native Bitrix24 app (iOS/Android) with push notifications, tasks, chats. Responsive web interface for extranet users (no app installation required). Offline access to documents and tasks, sync when connectivity is restored.

Order a turnkey corporate portal implementation

Schedule a free audit – we will evaluate your project, propose architecture, and give clear timelines. Get a comprehensive proposal and see that the portal pays for itself within the first six months. Contact us today.