The card opens on an incoming call
A client calls and the right manager gets their card, deals and history. An unknown number creates a lead by itself, so no call is lost.
Asterisk ↔ CRM · an Adminz solution
Your manager calls from the client card. In the browser, on your own Asterisk.
Several companies in Uzbekistan connect Asterisk to Bitrix24 and amoCRM. None of them lets the manager talk in the browser: you need a desk phone or a separate softphone on every machine. That gap is what Adminz Connector is being built for.
The product is under development. What is built and what is not is spelled out below.
Why this does not exist yet
Browser calling is built only for the vendor’s own PBX
Carriers ship a browser softphone — but only for their own lines and their own minutes. Integrators connect Asterisk to a CRM — but you still talk into a handset. Bitrix24 documents that an ordinary application cannot carry the audio in the browser; the ones who get around it brought their own telephony. For someone else’s Asterisk, nobody does it.
Your PBX stays yours. Your trunk, your number, recordings on your server. We do not sit between you and your carrier, and we take no margin on minutes.
What it does
The four reasons people install it
Click the number to dial
The number in the card is a link. Click, and the PBX connects the call — nothing to type, no digit to get wrong.
The conversation in the browser
A headset and the CRM tab. No desk phone, no client software to install and configure on every machine.
Recording and outcome on the deal
When the call ends, the deal gets duration, outcome and the recording your own PBX already makes. Settling “what did we promise them” takes nobody’s time.
What separates this from a quick hookup
Five places where integrations like this lie
Connecting a PBX to a CRM is not the hard part. Making the sales team trust what the card shows is. We know these places first-hand: some from our earlier connector that ran on a client’s portal, some from our own mistakes in the neighbouring product.
| How it shows up | What we do instead |
|---|---|
| Ten “missed calls” from one person | A call is identified by its call id, not by channel: one call, one record, however many phones rang |
| An outgoing call is filed as incoming | Direction comes from where the call arrived, not from the channel name — the administrator chooses that name |
| “Client 101 is calling” — that is a colleague down the hall | Internal conversations never reach the CRM |
| The call is credited to the wrong person | The call is credited to whoever answered: in a ring group that is whoever got there first, and otherwise the per-manager report misstates who is working |
| “Four minutes on the call” when it was forty seconds | Duration is counted from the answer, so “how long we talked” does not become “how long they waited” |
All five are closed by design and by tests, not by whoever edits the code remembering them. Verified against a fake PBX and a fake portal; on your installation we have yet to see it together.
How it is built
One box on your server, next to the PBX
The connector listens to your PBX and talks to the CRM over its own API. Audio goes from the manager’s browser straight to your PBX, not through us: call events pass through us, the conversation does not.
CRMBitrix24 · amoCRM
Adminz Connectorcall events, not the conversation
Asteriskyour PBX, your trunk
So the rollout holds no surprises
What has to be in place before we install
The two halves of the product ask for different things, and blurring that would be dishonest: the CRM link installs on almost any PBX, while talking in the browser has conditions no amount of goodwill gets around. If something is missing, you hear it before the invoice, not after.
For calls to reach the CRM
- Asterisk and read access to it — the connector listens and changes nothing on the PBX.
- A Bitrix24 account where you can create a webhook. No app to install, no review to pass.
To call from the browser — additionally
- A domain name for the PBX and a trusted certificate — browsers refuse a self-signed one.
- A public IP address and open media ports.
- Asterisk with PJSIP and WebRTC enabled; FreePBX is fine.
- A TURN server — without it corporate networks break the call.
Money
Per server, not per seat
The subscription is per installation. Hire three more people in sales and the invoice does not move. Minutes you pay your carrier directly; we do not resell them.
We name the price for a first installation in conversation: it depends on the work your PBX needs, not on how many managers you have.
Where it stands
What is built and what is not
Built
- Reading PBX events: call direction, who answered, how long they talked — under test.
- Working with Bitrix24 is verified against a real portal: registering a call, closing it, attaching the recording, finding the client by number.
- The commercial platform — licence, organisations, invoices, closing documents — shared with Adminz Dialer.
Not yet
- Not one live call has gone through the CRM yet.
- The browser softphone is written but untested inside a real CRM portal.
- amoCRM comes after Bitrix24, not alongside it.
Next
We are looking for first installations — and for people who need this
If you run Asterisk with Bitrix24 or amoCRM and your managers still dial from a desk phone, write or call. We install the first ones ourselves and listen to what gets in the way: this is better built against your PBX than against our idea of it.