Kazakhstan: SIP providers and connecting a number to the PBX

We do not issue numbers: the venue buys a Kazakhstani number from a local operator and brings it into its own PBX as a trunk. The steps that are the same everywhere — trunk modes, form fields, network and connectivity check — are described in the overview «Connecting a provider's number to the PBX»; this page covers only what is specific to Kazakhstan: whom to buy a number from, what that operator hands you and what of it goes into the admin panel.

In brief#

• Start with Kcell or Freedom Telecom. These are the only two operators in the country that publish the parameters for connecting a third-party PBX officially, and both let you choose between registration with a login and password or authorisation by your PBX's IP address. Our fields map one to one.
• A landline number almost always means Kazakhtelecom. It holds the main landline numbering of every region and sells a «Business trunk» for the customer's own mini-PBX, but the parameters come only with the contract.
• ⚠️ The main local catch is the Kazakhstani IP address. Beeline states it literally on its website: «The system works only with Kazakhstani IP addresses» and «SIP calls abroad from non-Kazakhstani IP addresses are blocked». Your dedicated PBX runs in a cloud outside Kazakhstan, so the first question to the account manager must be whether the operator will accept registration and calls from a foreign address. For Beeline the public answer is already «no».
• ⚠️ The second catch — Kazakhtelecom blocks «noisy» stations. Its SIP platform dislikes frequent keep-alive requests from a subscriber PBX; ours polls the provider once a minute by default. Discuss this with the operator's engineer when ordering the trunk (see «If it does not work»).
• ⚠️ The third — Tele2 / Altel sends the trunk login in the incoming call instead of the dialled number. The call is accepted, but with several numbers on one trunk the PBX cannot tell which line was called.
• Paperwork. The number is issued to a legal entity or a sole trader (Beeline Business requires the company's BIN as a mandatory field), and mobile numbers in Kazakhstan are tied to the subscriber's IIN. In any case a trunk only works on a dedicated PBX with a static IP — how the two trunk modes work is explained in the overview.

Numbers in the country#

Good news for routing. The PBX matches a line by the last seven digits of the number, and in Kazakhstan the subscriber number is exactly 7 digits. So the tail matches it perfectly both for a landline +7 727 XXX XX XX and for a mobile +7 777 XXX XX XX; the format you type into the «Number» field does not matter.

⚠️ A caveat when you have several numbers. Seven digits are not unique between regions: a landline in Almaty and a mobile number may end identically, and then two lines of the same venue become indistinguishable to the PBX. With two or more numbers, compare their endings when ordering and ask the operator for a different one.

Outbound, local operators accept both 8XXXXXXXXXX and +7XXXXXXXXXX (the outbound pattern in the Kcell and Freedom Telecom examples is +7XXXXXXXXXX). Which form to hand the provider is set by a prefix in the outbound rule.

Who issues a number with a SIP trunk#

The first four rows are operators whose trunk parameters are known, and each has a «What to enter in the admin panel» table below. Beeline gets a card of its own: the service exists, but it runs into the Kazakhstani IP address requirement. With the remaining local operators the trunk service is advertised while the host, port and authorisation method come only with the contract — talk to them using the checklist from «What to ask the provider».

Kcell / activ#

The country's second largest mobile operator (Kcell for business, activ for consumers). For business it sells a cloud PBX into which you are allowed to bring your own station — and together with Freedom Telecom this is the only case in Kazakhstan where the Asterisk connection parameters are printed in the operator's own manual.

How to get it: a contract with the corporate department; the cloud PBX subscription includes a bundle of minutes to all Kazakhstani mobile networks. The SIP login and password are taken from the cloud PBX account.

What to enter in the admin panel (Telephony → «Trunks and connections» → «Add provider» → the «SIP trunk (custom provider)» card):

Kcell's codecs are G.711 A-law, G.711 µ-law and G.729, DTMF is RFC 2833: our PBX speaks the first two and the same DTMF, so the pair is compatible.

What to set up at the provider. In the cloud PBX account: «More» → «Connecting other PBXs» → «Other SIP PBXs» → «Add PBX»; choose SIP registration (copy the server, login and password) or «Registration by IP» and enter your PBX's static IP as 1.1.1.1:5060 — the address is on the «Server» tab. Then list the internal numbers of your PBX so that the cloud PBX knows which calls to hand over, and write to support separately to have the required numbers routed to this connection and the outbound caller ID configured: by default the company's main number is shown.

Pitfalls ⚠️

• The short internal numbers of your PBX must not overlap with the internal numbers of the Kcell cloud PBX — otherwise the call goes to «their» subscriber instead of you.
• The account's built-in scenario is a «branch PBX reached by short numbers», not a trunk for a specific number: routing a particular landline or mobile number to you is arranged by a support request.
• In the IP mode the address is claimed exclusively: if it is already used by another customer, the account returns an error.

Source: connecting Asterisk/FreePBX to the Kcell cloud PBX, connecting external SIP PBXs — 09.09.2026.

Freedom Telecom#

The telecom arm of the Freedom group: a cloud PBX with landline, mobile and 8-800 numbers and CRM integrations. The account runs on the same engine as Kcell's, so the manual for connecting a third-party PBX matches it word for word — and is published by the operator just as openly.

How to get it: a contract and a cloud PBX plan; the employee's SIP settings are visible in the account.

What to enter in the admin panel

The codecs and DTMF are the same as at Kcell: G.711 A-law and µ-law (plus G.729, which we do not need) and RFC 2833.

What to set up at the provider. «More» → «Connecting other PBXs» → «Other SIP PBXs»; choose SIP registration or «Registration by IP» with your PBX's static address; list your station's internal numbers; in the «Numbers» section set the answering scheme for every purchased number and route it to this connection.

Pitfalls ⚠️ The same as at Kcell: overlapping short numbers, the exclusively claimed IP address, number routing through support. On top of that, the operator's manual documents a known defect — on outbound calls from inside the cloud PBX domain the ringback tone is lost; it is fixed on the cloud PBX side.

Source: connecting Asterisk (FreePBX) to the Freedom Telecom cloud PBX, external SIP PBXs — 09.09.2026.

Kazakhtelecom — iD Phone and Business trunk#

Kazakhtelecom is the fixed-line incumbent and the holder of the main landline numbering of every region. Two products matter to us: iD Phone (SIP telephony) and Business trunk — «connecting the customer's mini-PBX to the SIP platform, a multi-channel SIP connection with the option to assign several urban or rural numbers». The number of voice channels is not tied to the number of phone numbers, and the ratio of inbound to outbound channels may differ.

How to get it: a contract with the corporate division; the operator does not publish the parameters and hands them over with the contract.

What to enter in the admin panel

The platform's codecs are G.711 A-law and µ-law, DTMF is RFC 2833; that is enough for us. The values above come from published configurations of integrators who worked with this platform (the latest dated 28.11.2018), not from the operator's own page: do check them against what the engineer gives you.

What to set up at the provider. Sign a contract for iD Phone or Business trunk; obtain the login, the password and the regional SIP address; ask for the purchased landline numbers to be routed to this trunk; and clarify up front whether the platform blocks your PBX's address, since it sits outside Kazakhstan.

Pitfalls ⚠️

• The Kazakhtelecom platform blocks subscriber stations that send too many keep-alive requests: the public recommendation for Asterisk is to disable periodic availability checks and to spread accounts over separate ports. Our PBX polls the provider once a minute by default and retries registration every 30 seconds after a failure, so when ordering a Kazakhtelecom trunk write to our support — the polling mode for that trunk is configured on the server side.
• The operator has no technical documentation of its own, so treat every parameter as provisional until the contract is signed.

Source: Business trunk on the corporate customer portal — 09.09.2026.

Tele2 / Altel#

A merged mobile operator (the Tele2 and Altel brands). A mobile number can be brought into a third-party PBX over a SIP trunk: support issues the login and password on a request such as «Please provide a login and password to connect number [phone] to a cloud PBX under contract No. [number]». The operator has no landline numbers.

What to enter in the admin panel

The codecs are G.711 A-law and µ-law, DTMF is RFC 2833. The operator has no manual of its own: the parameters are known from the knowledge bases of cloud PBXs that connect Kazakhstani numbers, so check them against support's reply.

What to set up at the provider. Send a request for a login and password for the number; if inbound calls do not arrive, ask for calls to be routed to your PBX's IP address («Server» tab → «Static IP»); and clarify separately whether the operator accepts registration from a foreign address.

Pitfalls ⚠️

• In an incoming call the operator puts the trunk login into the address and leaves the dialled number only in the display name. The PBX recognises such a call as «a call from this provider» and accepts it, but with several numbers on one trunk it cannot tell which line was called. Use one trunk per number or route all numbers with a single rule — see «The provider sends its login instead of the number».
• The plus sign in the login is mandatory, otherwise inbound calls silently fail.
• Public guides quote two different server addresses — the only reliable source here is the operator's support.

Source: connecting a Tele2 Kazakhstan number (Sipuni knowledge base), Altel Business — services — 09.09.2026.

Beeline Kazakhstan#

The country's largest mobile operator. For business it offers «SIP TRUNK» / «PRI» — a service aimed exactly at a customer with their own PBX: provisioning takes «from one working week including the required testing», and the operator does not record calls (you do not need it to — your PBX does the recording). Applications go through Beeline Business and the company's BIN is mandatory. The operator does not publish the host, the port or the authorisation mode: an engineer hands them over with the contract, which is why there is no «what to enter» table here — ask the manager using the checklist from the overview. According to known configurations the trunk works without registration, by IP address: you will need to clear the «Register with the provider» checkbox and give the engineer your PBX's static IP.

Pitfalls ⚠️ — and this is the biggest risk in the country

• The Beeline cloud PBX page states plainly: «The system works only with Kazakhstani IP addresses» and «SIP calls abroad from non-Kazakhstani IP addresses are blocked». Your dedicated PBX runs in a cloud outside Kazakhstan, so until the operator confirms in writing that it will admit that address, treat the pairing as non-working. This is an operator restriction, not a setting you can work around in the admin panel.
• The Beeline cloud PBX does not suit you at all: it works only with Beeline's own corporate mobile numbers, does not accept numbers from other operators, and a landline number can only be forwarded to it.

Source: Beeline Business — cloud PBX and its comparison with SIP Trunk — 09.09.2026.

Other local operators#

International providers with Kazakhstani numbers#

If a local contract is impossible, a +7 7XX number can be bought from an international provider — but the choice here is noticeably narrower than in neighbouring countries:

• Zadarma — Kazakhstani numbers do exist: Almaty +7 727 and Astana +7 7172, plus dedicated plans for Kazakhstan. The Zadarma card is already in the catalogue when adding a provider — the server address and the mode are filled in for you. ⚠️ Zadarma's own restriction: from a connected Kazakhstani number you may call Kazakhstani numbers only from inside the country — for a venue whose outbound traffic goes to local numbers this may close the scenario.
• DIDWW — no Kazakhstani numbers at all: the country is absent from its public list.
• Telnyx, Twilio, Plivo, Bandwidth, Vonage, Sinch, Infobip, VoIP.ms, Sonetel — Kazakhstan is not confirmed in their public country lists (09.09.2026); check availability by searching for a number in the provider's portal.

⚠️ An international +7 7XX number is no substitute for a local one. Local operators filter by Kazakhstani addresses, while a number from an international provider is not legally tied to the venue and gives no access to the emergency 112. As the venue's only number it will not do.

Number porting#

• Mobile numbers can be ported between operators since 2016, but only within one region; inter-regional porting has been announced for 2026.
• A minimum term is being prepared: the ministry of digital development and the operators' association are discussing a ban on changing operator earlier than 60 days after the SIM is activated. As of 09.09.2026 this is a draft rather than a rule in force — check the current terms with the operator.
• Porting of landline numbers between fixed-line operators is not described publicly: in practice landline numbering belongs to Kazakhtelecom and its partners, and changing operator means changing the number.
• The number is issued to a business. Mobile numbers in Kazakhstan are tied to the subscriber's IIN, corporate ones to the company's BIN. A number registered to an employee becomes a problem when that employee leaves.
• Moving the venue does not break the number — the standard argument of every local SIP trunk provider: the number lives on the operator's platform, not on a wire in the wall.

Rules and paperwork#

If it does not work#

1. There is no registration and the operator mentions your address. The most common reason in Kazakhstan is the filter on Kazakhstani IP addresses: Beeline declares it openly, the others have to be asked. Your PBX runs in a cloud outside the country, so hand its static IP («Server» tab) to the operator and get a confirmation that a foreign address is accepted. Without that no admin panel setting will help.
2. A Kazakhtelecom trunk worked and then stopped. The operator's platform blocks stations that send frequent keep-alive requests. Write to our support so the polling interval for that trunk is lowered, and in parallel ask the operator's engineer to lift the block.
3. The call arrives but the wrong line's rule fires. Either two numbers share their last seven digits (see «Numbers in the country») or this is Tele2 / Altel, which sends the trunk login instead of the number. The fix is one trunk per number or a single routing rule for all numbers of that trunk.
4. No inbound calls at all on a Tele2 number. Check the login: it must be the number with a plus sign (+77XXXXXXXXX). A number without the plus or written with «8» is accepted at registration, but inbound calls will not work with it.
5. The operator offers only TLS and SRTP (as advertised, for example, by WorldLine). Our PBX works over UDP or TCP without encryption — ask for a plain unencrypted trunk; if the operator has none, the connection is not possible. Network and codec requirements are in «Network and compatibility».
6. Registration is up but no calls come in. The number is not routed to your trunk at the operator: at Kcell and Freedom Telecom routing a specific number to an external PBX is arranged by a support request, while by default the connection behaves as a «branch PBX reached by short numbers».

Causes that do not depend on the country are in «If calls do not go through»; the SIP trace in the trunk menu is described there too. Checking the address and port — «Check connectivity».

Frequently asked questions#

Why does everything with Kazakhstani operators come down to the IP address?#

Because the law obliges operators to keep service information inside the country, and they fence the perimeter the simple way — by addresses. Beeline says so on its website, the others have to be asked. Your PBX runs in a cloud outside Kazakhstan, so ask before signing the contract: «will you accept registration and calls from a foreign IP address?»

Which operator should I start with if I just need a working number?#

Kcell or Freedom Telecom: they publish the parameters for connecting a third-party PBX officially, either mode can be chosen, and the technical part on our side takes about twenty minutes. If the venue needs a landline number specifically, that means Kazakhtelecom, where everything has to be obtained from an engineer.

The operator offers its own cloud PBX — do I need it?#

No. Voice menus, queues, recording and call analysis are already in your «Telephony» section, and the operator's cloud PBX will conflict with them. Ask for a bare SIP trunk with the number routed straight to it. Separately: the Beeline cloud PBX only accepts their own corporate mobile numbers, so for a venue with a number from anyone else it is useless.

Can I take a Kazakhstani number from Zadarma and skip local operators?#

Almaty and Astana numbers are available at Zadarma and are provisioned within a day. But Zadarma has a restriction of its own: from a Kazakhstani number you may call Kazakhstani numbers only from inside the country — and such a number gives no access to 112. For receiving guest calls it works; as the venue's only number it does not.

What happens to call recordings?#

They are recorded just like in-app calls: the recording, the transcript and the analysis live in the «Calls» section, and the storage is outside Kazakhstan. Law No. 94-V requires databases with the personal data of the country's citizens to be stored on its territory; if that is critical for your business, call recording can be switched off in the location settings.

Sources#

All links checked on 09.09.2026.

Operators

• Kcell — connecting Asterisk/FreePBX to the cloud PBX: https://manual.kcell.kz/freepbx
• Kcell — connecting external SIP PBXs («Registration by IP»): https://manual.kcell.kz/sippbx
• Kcell — cloud PBX presentation: https://manual.kcell.kz/_media/vats_kcell.pdf
• Freedom Telecom — connecting Asterisk (FreePBX) to the cloud PBX: https://helpguide.vpbx.ftel.kz/freepbx
• Freedom Telecom — external SIP PBXs: https://helpguide.vpbx.ftel.kz/sippbx
• Freedom Telecom — configuring numbers: https://helpguide.vpbx.ftel.kz/numbers
• Kazakhtelecom — the «Business trunk» service for corporate customers: https://online.kz/korporativnye-klienty/telefonnaja-svjaz-cc/business-trunk-cc/
• Beeline Business Kazakhstan — cloud PBX, its comparison with SIP Trunk, the Kazakhstani IP requirement: https://business.beeline.kz/virtual-ats
• Beeline Kazakhstan — the «SIP TRUNK» service: https://beeline.kz/b2b/ru/products/tariffs/sip-trank
• Altel Business — services for business: https://business.altel.kz/ru/services/3
• KTS / Kaztekhnosvyaz — SIP trunk: https://kts.kz/sip-trank
• KazNetCom — SIP trunk: https://www.kaznetcom.kz/sip-транк
• ETEL / EURASIAN TELECOM — SIP trunk and SIP numbers: https://etel.kz/sip/
• A1 Telecom — SIP trunk: https://a1call.kz/sip-trunk
• SMARTNET — SIP trunk: https://smartnet.kz/sip-trunk
• WorldLine — SIP trunk: https://worldline.kz/sip-trunk/
• Orbicom — SIP telephony: https://orbicom.kz/sip
• Zadarma — Kazakhstani numbers (Almaty, Astana): https://zadarma.com/en/tariffs/numbers/kazakhstan/

Law and regulator

• Law of Kazakhstan «On Communications» of 05.07.2004 No. 567-II: https://adilet.zan.kz/rus/docs/Z040000567_
• Article 15 of the Law «On Communications» (storing service information inside Kazakhstan, as amended by Law No. 256-VIII of 09.01.2026): https://kodeksy-kz.com/ka/o_svyazi/15.htm
• Law of Kazakhstan «On Personal Data and Their Protection» of 21.05.2013 No. 94-V: https://adilet.zan.kz/rus/docs/Z1300000094
• The data localisation requirement (a review of article 12): https://online.zakon.kz/Document/?doc_id=39801023

Parameters and connection practice

• Connecting a Tele2 Kazakhstan number (Sipuni knowledge base): https://help.sipuni.com/articles/181-62-74--tele2-kazahstan/
• iD Phone, Tele2 and Kcell trunks in FreePBX (28.11.2018): https://linuxtaxi.blogspot.com/2018/11/freepbx-connect-to-idphone-tele2-and.html
• Asterisk and the Kazakhtelecom SIP platform: how to avoid being blocked (19.08.2016): https://linuxtaxi.blogspot.com/2016/08/asterisk-sip.html
• Telephone numbering plan of Kazakhstan: https://ru.wikipedia.org/wiki/Телефонный_план_нумерации_Казахстана
• Mobile number portability in Kazakhstan: https://profit.kz/tags/mnp/

Related pages#

• Connecting a provider's number to the PBX — the common steps, trunk modes, network, connectivity check.
• Setting up SIP phones — how to connect desk phones and DECT to extensions.