Grandstream UCM is one of the most common PBXs in small offices in Kazakhstan. If you already have one, you can run call campaigns through it: from your numbers, through your carrier and at your own call rates.
These instructions follow the UCM63xx interface; on the UCM62xx the items have the same names, though the tab layout differs slightly between firmware versions.
How the call works
We start the call: the platform sends your UCM an invitation where the called number is the contact's number. The UCM must send this call out through your carrier trunk. If the scenario transfers the contact to an employee, a call to an extension arrives the same way.
Check this first. The main requirement for any PBX is being able to send out a call that came in from a trunk. On the UCM this can be configured (see step 3), but in some firmware versions trunk-to-trunk routing is restricted by policies. If your version doesn't have this option, don't spend a day trying settings: internal transfers will still work, and you can run call campaigns over our lines, in which case there is nothing to set up at all.
Connection settings
| Signaling address | pbx.autocall.kz |
| IP for the firewall | 109.233.108.218 |
| Port | 5060 — UDP,
5061 — TLS
|
| Voice (RTP) | subnet 109.233.108.208/28, ports 10000–20000 |
| Codec | PCMA (alaw) |
| Trunk type | Peer SIP Trunk, no registration |
Step 1. Firewall and access
If the UCM reaches the internet through a router, forward the SIP port and the voice range and allow traffic from our addresses. On the UCM itself, check that the enabled protection features (Fail2Ban, Static Defense) don't block our address. Add it to the whitelist, or after a few calls the PBX will start dropping them.
- signaling:
pbx.autocall.kz(IP109.233.108.218), port 5060/UDP (or 5061/TCP for TLS); - voice: subnet
109.233.108.208/28, ports 10000–20000/UDP.
Step 2. SIP trunk
Extension / Trunk → VoIP Trunks → Add SIP Trunk
- Type:
Peer SIP Trunk, since the platform doesn't register with you and calls from a known address; - Provider Name:
autocall; - Host Name:
pbx.autocall.kz; - Transport: UDP (or TLS if you chose encryption);
- Codec Preference: keep only
PCMA; - DTMF Mode:
RFC2833; - Outbound Caller ID: your number. The UCM will put it on calls going to the carrier.
No login and password are needed on the trunk. If you still want the platform to authenticate, enable authentication on the UCM side and enter the same login and password in the dashboard, and we will authenticate on every call.
Step 3. Routing
The goal: a call that came in from the autocall trunk for the contact's number must go out through your carrier trunk, with your CallerID.
On the UCM two places control this, and you need to check both:
- Inbound Routes for the
autocalltrunk: how incoming calls are handled. This is where you set what to do with a number that isn't among the extensions: keep handling it by the dialed number or send it on. - Outbound Routes: which trunk the call goes out on and its privilege level. The route's privilege level must be no higher than the one the call from our trunk arrives with, or the UCM won't let it through.
Also check that the dial pattern in the outbound route accepts numbers in the form we send them, +7XXXXXXXXXX, and if needed strip the + or add 8 with dialed number manipulation rules.
Transfers to extensions need no setup: the UCM finds the short number from the scenario among its extensions by itself.
Step 4. Encryption (optional)
The UCM supports TLS for signaling and SRTP for voice, both enabled in the trunk settings. If you enable SRTP, enable TLS too: the voice encryption key travels right inside the SIP message, and over open signaling it would go out in plain text next to the “encrypted” stream. In the dashboard, choose the TLS transport.
Step 5. Add the PBX in the dashboard
Go to “PBX” → “Connect a PBX”: the PBX's IP, port, transport, a login and password if needed, the limit of concurrent channels and the dialing rate. Set the limits no higher than your carrier allows, and we won't exceed them.
Once saved, the PBX status appears in the list. “Responding” means the UCM answers our connection checks. Then, when you create a call campaign, choose your PBX: 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 signaling port is closed on the router, or our address is blocked by the UCM's protection features.
- Calls arrive but don't go out to the contact. Routing from the trunk to the outbound route isn't set up (step 3), or the dial pattern doesn't accept a number with
+. - The carrier rejects calls. Your CallerID isn't being set: our “from” field holds an internal tag like
59336790(the call's number in our system). It's needed for matching CDRs and is not a phone number. - The call connects, but there's silence. The voice subnet isn't open, or the UCM is behind NAT without an external address set.
The UCM has a built-in SIP trace (Maintenance → Signaling Troubleshooting). If you need help, capture a trace during a test call and attach it to your support request: it shows right away whether the call arrived and what the PBX answered.
Which trunk type should I choose?
Peer SIP Trunk. A registration trunk won't work: the platform doesn't register with you, it calls your PBX's IP itself.
Why do calls arrive but never go out to the contact?
The call stayed in inbound processing and didn't reach an outbound route. Check the routing for the trunk and the privilege level of the outbound route.
Which codec should I keep?
Only PCMA (alaw). Extra codecs in the list lead to transcoding and load on the UCM.
Is encryption supported?
Yes, TLS and SRTP. Enable them together: SRTP over open signaling doesn't protect anything, since the key travels inside the SIP message.