Connect your PBX to AutoCall.kz, and your campaigns will call from your numbers, through your carrier and at your own calling rates. From us you get a powerful voice platform: complex IVR scenarios, voice AI agents, speech recognition, text-to-speech, reports, integration with CRM and more.
Try it free →| BRONZE | SILVER | GOLD | |
|---|---|---|---|
| Automated calls per second | 0.20 ₸ | 0.10 ₸ | 0.05 ₸ |
| AI agent per second | 1.65 ₸ | 1.15 ₸ | 0.95 ₸ |
| One speech synthesis | 7 ₸ | 5 ₸ | 3 ₸ |
| One speech recognition | 9 ₸ | 7 ₸ | 5 ₸ |
| Call recording | 5 ₸ | 3 ₸ | 0.50 ₸ |
| SMS up to 70 characters | 37.30 ₸ | 23.25 ₸ | 18.95 ₸ |
You pay your carrier for call minutes. Retry attempts through your own PBX are free.
The same campaign through AutoCall.kz numbers and through your PBX. Plug in your own contact list.
Retries through your PBX cost nothing extra.
11 692 ₸ (82%) less than through AutoCall.kz numbers
You pay your carrier for call minutes at its rates, and we charge only for the campaign. The Silver plan applies with a top-up of 30 000 ₸ or more.
Get startedYour PBX with limited features gets every capability of the AutoCall.kz platform without buying expensive vendor hardware and licenses.
A live voice conversation: the agent answers questions, clarifies details and records the result itself. No PBX can do this, and no amount spent on licenses will change that.
Branching by keypress and by what is said out loud, contact variables, conditions and jumps. Built with the mouse in the builder instead of editing the dialplan in a console.
Right during the call, the service queries your API: it looks up a balance, an order status or stock availability and reads the answer aloud. The call result goes back to you with a GET or POST request.
A voice for your task with each customer's data filled in, plus recognition of what the contact said instead of “press one”.
Results instead of CDRs: who answered what, what data they gave, the call transcript and export, in columns you define yourself.
No fees for voice ports, no per-agent licenses, no hardware to buy. Per-second billing for what was actually played.
Features are only part of it: it also changes whose numbers make the calls and who gets the callbacks
The number is set by your PBX and your carrier. Customers see your numbers they already know, not unfamiliar service numbers from AutoCall.kz.
The contact taps “call back” in their call log and reaches your PBX: your queue, your operator, your rules.
You already buy minutes from your carrier, often cheaper than any service resells them. All that's left for us is the voice platform.
The call passes through your PBX, so you can record it on your side with your own retention rules. Our recording stays optional.
A scenario can connect the contact with an operator on an extension and continue after the call: quality rating, branching by result.
Signaling over TLS and voice over SRTP are available. For banks and government organizations, an IPSec or WireGuard channel is an option.
Four steps to get AutoCall.kz features on your PBX
Set up a SIP trunk on your PBX to our address. We recognize a PBX with a static IP by its address, and one without a static IP by the login and password from the dashboard.
Point this trunk to your outbound routes so calls from us go out the same way as your employees' calls.
Upload a list, build a scenario or pick an AI agent, and choose to call through your PBX.
Our server sends your PBX a call to the contact's number, your PBX dials it through your carrier, and the AutoCall.kz platform runs the conversation.
AutoCall.kz dashboard
You launch a campaign
AutoCall.kz Voice/AI servers
The agent runs the conversation
Your PBX
The call goes out from your numbers
Your SIP provider
At your rates
Contact
Sees the company number
AI needs no separate integration with the PBX: the voice agent works over the same SIP trunk
The AI agent calls customers from your numbers and through your carrier, and holds a live conversation: it answers questions, clarifies details, records the call outcome.
The contact asks for a real person, and the agent connects them to an extension on your PBX or a manager's mobile. The call goes through the same PBX.
Connect your PBX in the “PBX” section, create an agent by describing the task in plain words, and launch a campaign through your PBX.
Step by step, with ready-made config snippets
Have a different PBX? Any PBX works if it supports a SIP trunk by IP and routing from the trunk to the outside. The settings below are the same for all.
This is all any VoIP engineer needs to connect your PBX to AutoCall.kz
| Signaling address | pbx.autocall.kz |
| IP for the firewall | 109.233.108.218 |
| Port | 5060 for UDP (PBXs in Kazakhstan), 5061 for TLS (Kazakhstan and CIS)
|
| Voice (RTP) | subnet 109.233.108.208/28, ports 10000–20000
|
| Codec | opus or alaw: we offer both, opus first. If your PBX doesn't support opus, keep only alaw
|
| Number format | +7XXXXXXXXXX; in the dashboard you can choose 7…, 8… and local numbers without the area code |
| Registration | not needed for a PBX with a static IP; without one, the PBX registers with us |
| Authentication | optional: if your PBX requires a login and password, enter them in the dashboard and we will authenticate on every call |
| Encryption | Optional: UDP or TLS for signaling, SRTP (SDES) for voice only with TLS enabled. TLS 1.2 and 1.3 only. |
| Direction | both ways: we call through your PBX, and it sends inbound calls to us |
Just two things: accept a SIP trunk without registration, by IP, and route a call from that trunk to its outbound route. The second one is the real requirement: it is where PBXs trip up when the route is hard-wired to a specific inbound number.
Route calls from your PBX or SIP account to AutoCall.kz, and an AI agent, a voice menu or your employees in the browser will answer them. Your PBX stays in place: only the calls you route come to us. Price: from 3 to 10 ₸ per call, plus whatever works during the call: AI agent per second, recognition, synthesis, recording.
Cloud call center with an AI agent →No separate integration is needed: connect your PBX over a SIP trunk in the “PBX” section, create a voice AI agent and launch a campaign through your PBX. The agent calls customers from your numbers through your carrier, and if the contact asks for a real person, it connects them to an extension or an employee's mobile through the same PBX.
Any PBX that can accept a SIP trunk without registration, by IP address, and route a call from that trunk to an outbound route. Tested on Asterisk, FreePBX, FreeSWITCH and Grandstream UCM; Cisco, Avaya, Yeastar and other enterprise PBXs connect the same way.
No. There are three ways to connect: a PBX with a static IP, a SIP account from your provider (then you need no PBX at all), or a PBX without a static address that registers with us using a login and password.
Yours. The number is set by your PBX and your carrier, we are not involved. That is why people call you back directly.
From 0.05 to 0.20 ₸ per second depending on the plan, this is the platform price. You pay your carrier for call minutes under your own contract. Retry attempts through your own PBX are free, while through our lines they are billed. An inbound call through your PBX costs from 3 to 10 ₸ per call.
Yes: TLS for signaling and SRTP for voice. We allow SRTP only together with TLS: the encryption key travels inside the SIP message, and over open signaling that would only look like protection. If your PBX supports TLS but not SRTP, that is fine, there is a lot of such equipment in Kazakhstan.
Only TLS 1.2 and TLS 1.3 are supported: versions 1.0 and 1.1 are obsolete and we reject them. If a TLS connection fails, check the TLS method on the PBX. It is a transport setting, not a trunk setting (in FreePBX: TLS Method = tlsv1_2; older builds default to tlsv1). Turn off server certificate verification (verify_server).
We know this restriction. At banks and government organizations, traffic goes out through the unified internet access gateway (ESHDI) or through their own DPI equipment. Such a gateway cannot read the contents of TLS and SRTP, but it sees the session itself and blocks it by policy. The issue here is not the strength of the encryption, it is that the channel is not approved.
We cannot put the platform inside your perimeter: it is not a boxed product but a service on our infrastructure that is updated as a whole and continuously.
So we take a different path: instead of hiding the channel from DPI, we make it approved. We are ready to sign an NDA, pass your security team's reviews and set up a dedicated L2TP/IPsec or WireGuard tunnel between your PBX and our site. Then signaling and voice do not go “somewhere outside” but over a channel with known addresses at both ends: it is described in your regulations and explicitly allowed on the gateway. Write to support: the setup is worth discussing before you start the paperwork.
That is by design. Our SIP node is closed by default and answers only addresses it already knows. Your IP gets on that list by itself as soon as you add the PBX in the “PBX” section. Nothing to approve and nothing to wait for: the rule appears a few seconds after you save.
Exactly one port opens, the one that matches the chosen transport: 5060/udp for UDP or 5061/tcp for TLS. Change the transport in the dashboard, and the rule changes while the old port closes. The allowlist opens nothing beyond this port, so ping proves nothing here: ICMP has nothing to do with SIP and says nothing about signaling reachability in either direction. Test with the transport your signaling will use.
Yes. The scenario has a step that connects to an extension on your PBX. Nothing needs to be set up on the PBX side, and the scenario continues after the conversation: you can ask for a quality rating or branch by result.
Yes. Create an inbound line in the dashboard for your PBX or SIP account and choose who answers: the AI agent, a voice menu or employees. We take the calls your PBX sends to us on that line.
As many as you set yourself: the PBX settings define the limit of concurrent channels and the dialing rate. Keep them no higher than your carrier allows, and we will not exceed them.
The campaign will not stop and you will not be charged for calls that were not placed: failed attempts are marked as errors, and the reserved amount returns to your balance when the campaign ends. The dashboard shows the PBX status: whether it responds to our connectivity checks or not.
How different businesses take calls with an AI agent, remind customers and verify phone numbers
Sign-up takes a minute. Set up a SIP trunk and give your PBX the features of AutoCall.kz.
Sign up free →