SIP trunks: connecting your IP PBX in Kazakhstan

What is a SIP trunk?

A SIP trunk connects your company’s IP PBX to an operator’s telephony service for incoming and outgoing calls. Employees continue using their PBX and compatible devices, while EURASIAN TELECOM provides the operator connection in the agreed configuration. SIP handles call setup and termination; a media stream carries the audio.

• A trunk does not replace a PBX: your PBX normally provides IVR, groups and queues.
• Channels and numbers are agreed separately. SIP support does not guarantee compatibility of every device model and version.

How incoming and outgoing calls work

For an incoming call, a customer dials your local number. The operator forwards the call to your PBX, whose rules select an employee, group or IVR. For outbound calling, the PBX sends the call to the operator. The recipient sees your assigned local number; we check caller ID before launch.

1. 01Customer dials a local number
2. 02EURASIAN TELECOM / SIP trunk
3. 03Your company’s IP PBX
4. 04Employee or group

Numbers, channels, trunks and extensions

These terms answer different questions: a number is what customers dial; channels describe concurrent call capacity; a trunk is the PBX-to-operator connection; an extension identifies an internal destination.

Example: an office with its own PBX

Illustrative example: a company has 12 employees, but they do not all make external calls simultaneously. Two incoming conversations plus one outgoing conversation represent three concurrent external conversations. Headcount alone does not determine capacity. This is an explanation, not a tariff or a capacity recommendation.

• Record incoming and outgoing load during peak periods.
• Consider waiting calls and forwarding: capacity usage depends on the setup. Agree the final capacity with a specialist.

Example: Almaty and Astana branches

A company needs local numbers in Almaty (+7 727) and Astana (+7 7172). Before connection, identify which PBX receives each number and which employees answer. A central PBX handles its own routing; separate PBXs require separate assessment of each connection. Number resources in a city do not confirm availability of a specific number.

SIP trunk, Cloud PBX or Bitrix24

Choose based on where call handling will be managed. A SIP trunk connects your own PBX. ETEL Cloud PBX provides a hosted PBX for employees and branches. Direct Bitrix24 telephony is a standalone service requiring neither ETEL Cloud PBX nor the SIP connector. These are different setups, not a mandatory combination.

Which PBX systems can be connected?

Existing customer connections include Asterisk, FreePBX, 3CX and Yeastar. We assess the specific model, version and topology before connection. A platform name alone does not guarantee support for every version, module or custom modification.

• Provide the PBX model, version and existing connection details.
• Our specialists help your technical specialist configure and jointly test the connection.

Technical parameters to agree

EURASIAN TELECOM supports G.711 and G.729 codecs and their variants. Keypad events can use RFC 2833/4733 or SIP INFO. TLS and SRTP are supported; encryption is configured by agreement according to your PBX capabilities. The specific profile is agreed before launch.

• Authentication, endpoints, dialling format, signalling and media parameters are supplied for your configuration. There are no universal public connection credentials.
• Your administrator checks router and firewall settings with our specialists. Do not expose the PBX to all addresses as a troubleshooting shortcut.

Local numbers and caller ID

EURASIAN TELECOM has number resources in 19 Kazakhstan cities. You can connect an existing EURASIAN TELECOM local number; keeping another operator’s number requires separate assessment. Outbound calls display your assigned local number. The service does not provide arbitrary caller ID substitution.

How a SIP trunk is connected

We prepare the connection with your technical specialist. Timing, capacity and commercial terms are agreed individually. We assess requirements and compatibility, supply agreed parameters, configure the PBX and test calling.

• Request: company, contact, cities, numbers, PBX model and version.
• Agreement: concurrent load, call directions, forwarding, codecs and DTMF.
• Configuration: trunk parameters and inbound/outbound PBX routing.
• Acceptance: joint checks before live operation.

Pre-launch checks

With the customer, we test incoming and outgoing calls, local caller ID and forwarding. We also test agreed PBX scenarios such as two-way audio, IVR keypad handling and busy handling. Features of the specific PBX are confirmed separately.

• If a call connects but audio is one-way, provide the time and call direction so a specialist can assess media handling and configuration.
• If keypad events fail, check the agreed DTMF mode. Record the existing configuration before changing settings.

Support, changes and security

Telephony fault support is included and available 24/7 via WhatsApp +7 707 326 99 90 and cs@etel.kz. Report the time, direction and symptoms of the problem. Do not post usernames, passwords or keys publicly or in an enquiry form.

• Forwarding to a mobile or another number can be configured; agree the scenario and terms in advance.
• Changes to the setup, capacity increases and additional work are agreed first. Do not disable PBX protection to test calling.