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 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 | G.711A |
| 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
First, an honest word about age
Nortel CS1000, BCM and Mitel MiVoice are platforms of different generations, and the connection depends on whether your specific version supports a SIP trunk, not on the brand. There are two paths from here, and both work.
Path 1. The PBX supports SIP
Nortel CS1000. The trunk is set up as a SIP gateway through the routing server: add a node with the address pbx.autocall.kz (IP 109.233.108.218), create a routing entry for numbers like +7XXXXXXXXXX and check that calls from this direction are allowed out on your external lines.
Nortel BCM. In the telephony settings, create a SIP trunk with the platform address, without registration, and add a routing rule that sends the contact's number to your carrier line.
Mitel MiVoice Business (3300) and MiVoice Office. Create a SIP Peer Profile with our address, then ARS entries that send the number to the carrier trunk. Make sure the peer has a class of service with trunk-to-trunk call rights. Without it, a call from the trunk won't get out.
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.
Common to all three: G.711A codec, no registration, and be sure to check your licenses, since these platforms usually limit the number of concurrent SIP sessions. Set the channel limit in the dashboard no higher than the licensed one, and we will never exceed it.
Path 2. The PBX has no SIP or hits a license limit
This is a common case: the platform works, nobody plans to replace it, and a SIP trunk is either unsupported or costs as much as half a new PBX. Then a gateway goes in front of the PBX, and for the call campaign platform it becomes your PBX.
A cheap and predictable option is a small server with Asterisk: it accepts our trunk and connects to your PBX over whatever the PBX understands: SIP, E1 or an FXO card. The trunk setup itself is covered in detail in the article on Asterisk and FreePBX; the gateway connects to the PBX like any neighboring node.
A bonus of such a gateway is that it also takes care of old codecs, encryption and troubleshooting: diagnosing SIP on Asterisk is far easier than on a closed platform from twenty years ago.
Encryption
On old platforms, TLS and SRTP are usually either missing or need separate licenses. If you need encryption, put it on the gateway: it talks to us over TLS and to the PBX in whatever way the PBX supports.
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.
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
- No reply to connectivity checks. The signaling port is closed, or the PBX listens on a different interface.
- The call is rejected right away. There is no right to transit from the trunk to the outside, or no routing rule matches the contact's number.
- Busy after a few calls. You hit the licensed limit of concurrent sessions. Lower the channel limit in the dashboard.
- Connects, but silence. The voice subnet is not open, or the PBX negotiated a codec it doesn't actually have.
Nortel and Mitel menu names change between releases more than on any other platform. If everything looks different on yours, write to support: we will advise for your version or help you build a gateway.
Can an old Nortel PBX be connected to a modern call campaign service?
Yes, if it supports a SIP trunk: on CS1000 it is a SIP gateway through the routing server, on BCM a SIP trunk in the telephony settings. If your version doesn't support SIP or needs licenses for it, it is cheaper to put a small SIP gateway in front of the PBX.
What if the PBX doesn't support SIP at all?
Put a gateway in front of it: an inexpensive server with Asterisk accepts our trunk and connects to the PBX over an interface it understands: SIP, E1 or FXO. For the call campaign platform, the gateway then becomes your PBX.
Do I need licenses for the trunk?
On Nortel CS1000 and Mitel MiVoice, the number of concurrent SIP sessions is usually licensed. In the dashboard, set the concurrent channel limit no higher than the number of available sessions, and the platform will never try to use more.
Which codec should I choose?
G.711A, also known as alaw, the standard for Kazakhstan networks, and it involves no transcoding.