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 | G.711 a-law |
| 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
Option 1. Cisco Unified Communications Manager
SIP Trunk Security Profile
System → Security → SIP Trunk Security Profile. Create a separate profile: name autocall, inbound port 5060, accept inbound calls without authentication, Device Security Mode Non Secure (for TLS, Encrypted with a certificate).
SIP Trunk
Device → Trunk → Add New → SIP Trunk:
- Destination Address:
pbx.autocall.kz, port5060; - SIP Trunk Security Profile: the one created above;
- Inbound Calls → Calling Search Space: 🔴 the most important field: the CSS must include the partition that holds the route pattern to your carrier;
- Inbound Calls → Significant Digits:
All, otherwise CUCM will truncate the contact's number; - Media Resource Group List: no transcoders, if the region uses G.711 a-law;
- Region: in the Device Pool settings, make sure G.711 a-law is allowed between the trunk's region and the carrier trunk's region.
Route out
Call Routing → Route/Hunt → Route Pattern: a pattern for +7XXXXXXXXXX numbers in the partition visible from our trunk's CSS, pointing to your carrier trunk. In the same place, a Calling Party Transformation that 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.
Transfers to extensions work without extra setup: CUCM finds the short number from the scenario in the same CSS.
Option 2. Cisco CME and CUBE
On the IOS platform everything comes down to two dial-peers and one command, without which a call between two SIP legs is not allowed:
voice service voip ! without this, transit between SIP legs is not allowed allow-connections sip to sip sip bind control source-interface GigabitEthernet0/0 bind media source-interface GigabitEthernet0/0 ! calls coming from the platform voice class uri 100 sip host ipv4:109.233.108.218 dial-peer voice 100 voip description AutoCall.kz inbound session protocol sipv2 incoming uri via 100 codec g711alaw dtmf-relay rtp-nte no vad ! out, through your carrier dial-peer voice 200 voip description To operator destination-pattern ^\+?7[0-9]{10}$ session protocol sipv2 session target ipv4:CARRIER_IP codec g711alaw dtmf-relay rtp-nte no vad
Number override is a regular voice translation-rule on the outbound leg:
voice translation-rule 10 rule 1 /.*/ /7XXXXXXXXXX/ voice translation-profile SET-CLI translate calling 10 dial-peer voice 200 voip translation-profile outgoing SET-CLI
Encryption (optional)
CUCM secures signaling with TLS through the trunk security profile, and voice with SRTP in the device settings. On CUBE this is transport tls in voice class tenant and srtp on the dial-peer. In the dashboard, choose the TLS transport.
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
- CUCM answers 404 or 403. The call arrived, but the trunk's CSS can't see the right route pattern, or the number is truncated by significant digits.
- CME ends the call right away.
allow-connections sip to sipis missing, or the inbound dial-peer didn't match: checkdebug voip dialpeer. - The carrier rejects calls. Calling party override isn't set up.
- The call connects, but there's silence. The voice subnet isn't open, or there's a codec mismatch between regions: check that both sides agreed on G.711 a-law.
Cisco has many versions and builds, and menu item names differ between them. If your interface looks different, write to support and we'll help with your version.
Do I need a separate SIP Trunk Security Profile in CUCM?
Yes, it's easier to create a separate profile for this trunk: it holds the inbound port and the security mode. If you plan to use TLS, the profile is required, since that is where signaling encryption is enabled and the certificate is set.
Why does CUCM accept the call but never send it to the contact?
The trunk has no access to the right routes. A call from the trunk gets the Calling Search Space set in its inbound calls settings, and that CSS must include the partition with the route pattern to the carrier trunk. Otherwise the number simply isn't found.
How do I set my own number on the outbound call?
With Calling Party Transformation: on the route pattern or on the outbound trunk you set a transformation that replaces the platform's internal tag with your number. Without it, the carrier will reject the call.
What should I configure on Cisco CME instead of CUCM?
Two dial-peers: an inbound one for calls from the platform address and an outbound one to the carrier trunk, plus allow-connections sip to sip under voice service voip. Without this command, routing between two SIP legs is not allowed, and the call ends right away.