How the call works
Calls go one way: we start the call. The platform sends your PBX a SIP INVITE where the called number is the contact's number. The PBX handles it like a number dialed from an internal phone and sends it out through your carrier. If the scenario transfers the contact to an employee, the call to the extension arrives over the same trunk.
The whole setup follows from this, and the PBX has to meet exactly two requirements: accept a trunk without registration, by IP, and send a call from that trunk to an outbound route. The second one is where PBXs trip up when their routing is hard-wired to a specific inbound number.
Connection settings
| 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 | 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 it, enter the login and password in the dashboard |
| Call direction | both ways: the platform calls through your PBX, and the PBX sends inbound calls to us |
Firewall
Signaling comes from one address and voice from a subnet: on our side these are different servers. Open both, or you get the classic case of “the call connected, but the line is silent”.
# signaling udp dport 5060 ip saddr 109.233.108.218 accept tcp dport 5061 ip saddr 109.233.108.218 accept # voice udp dport 10000-20000 ip saddr 109.233.108.208/28 accept
Step 1. Trunk
PBX → Trunks → Add (on P-Series: Extension and Trunk → Trunks → Add).
- Trunk Type:
Peer Trunk(calledService Providerin some firmware versions), the option without registration; - Trunk Name:
autocall; - Hostname / IP:
pbx.autocall.kz, port5060; - Transport: UDP (or TLS if you turn on encryption);
- Codec: keep only
alaw; - DTMF Mode:
RFC4733 / RFC2833; - Enable Outbound Proxy: off;
- Max Concurrent Calls: the same number you set in the dashboard.
The trunk needs no login or password. If you want the platform to authenticate, turn on authentication on the Yeastar side and enter the same login and password in the dashboard. We will then authenticate on every call.
Step 2. Routing: the key step
The goal: a call that arrives from the autocall trunk for the contact's number must go out through your carrier trunk with your CallerID.
In Yeastar, this is handled by the outbound route (Call Control → Outbound Routes). Check three things in it:
- the dial pattern accepts numbers in the format we send them:
+7XXXXXXXXXX; if needed, strip the+with a dialed number rule; - the call source includes the
autocalltrunk: depending on the series and firmware, this is a list of extensions and trunks allowed to use the route, or a separate option for transit calls between trunks; - the outbound CallerID sets your number.
CallerID override is required. In our call, the “from” field holds our internal identifier, the call's number in our system, for example 59336790. It makes it easy to match your call log against our export. It consists of digits, but it is not a phone number: your outbound route must replace it with your number, or the carrier will reject the call. The same identifier is duplicated in the X-AutoCall-Call-Id header.
You don't need to set up transfers to extensions: the PBX finds the short number from the scenario among its extensions on its own.
Step 3. Encryption (optional)
In the trunk settings, turn on TLS for signaling and SRTP for voice, and select the TLS transport in the dashboard.
SRTP works only together with TLS. The voice encryption key travels right inside the SIP message: over unencrypted signaling it would go out in plain text next to the “encrypted” stream. That only looks like protection, so we don't allow this combination. At the same time, TLS without SRTP is a normal option: in Kazakhstan many PBXs and phones have SRTP stripped from the firmware while TLS works.
Step 4. Add the PBX in the dashboard
Go to “PBX” → “Connect a PBX”. You will need:
- the PBX's IP address and port;
- transport, UDP or TLS, and voice encryption if you enabled it;
- login and password, only if your PBX requires authentication;
- the limit of concurrent channels and the dialing rate: set them no higher than your carrier allows, and we won't exceed them.
Once saved, the PBX status appears in the list: “Connected” means it answers our connection checks. Then, when you create a call campaign, choose your PBX in the “Call through” field: the estimate is calculated right away at the discounted per-second rate, and retry attempts through your own PBX are free.
If calls don't go through
- The dashboard shows “Not responding”. The port on the router is closed, or the PBX's built-in protection blocked our address. Add it to the allow list.
- Calls arrive but don't go out. The outbound route doesn't accept calls from the platform trunk, or the dial pattern doesn't match the number format.
- The carrier rejects calls. Your CallerID is not being set.
- Connects, but silence. The voice subnet is not open, or the PBX is behind NAT with no external address set.
Yeastar has built-in traffic capture (Maintenance → Troubleshooting → Network Capture). If you need help, take a capture during a test call and attach it to your support request.
Which trunk type should I choose on Yeastar?
Peer Trunk, also called Service Provider: the option without registration, where the PBX identifies the other side by IP address. A register trunk won't work: the platform doesn't register with you, it calls the PBX address itself.
Why do calls arrive but never reach the contact?
The call stayed in inbound handling. On Yeastar you need to allow trunk-to-trunk routing: the outbound route must accept calls that come from the platform trunk, not only from extensions.
Which codec should I keep?
alaw (G.711A). The platform offers opus and alaw, but every Yeastar model has alaw: there is no transcoding, and the PBX doesn't waste resources.
Does Yeastar support encryption?
Yes, TLS for signaling and SRTP for voice are turned on in the trunk settings. Turn them on together: SRTP over open signaling gives no protection, because the key travels inside the SIP message.