Integrations

How to connect Avaya IP Office and Aura to AutoCall.kz

← All articles

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.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

Option 1. Avaya IP Office

SIP Line

In IP Office Manager: Line → Add → SIP Line.

  • ITSP Domain Name: pbx.autocall.kz;
  • Send Caller ID: Diversion Header is not needed, leave None;
  • Transport → ITSP Proxy Address: pbx.autocall.kz, Layer 4 Protocol: UDP or TLS, port 5060;
  • Incoming Group ID and Outgoing Group ID: set an unused group number, you will need it for the route;
  • SIP URI: an entry with Local URI, Contact and Display Name set to *, so the line accepts any called number;
  • VoIP → Codec Selection: only G.711 ULAW/ALAW, keep G.711A; Re-invite Supported on.

Route to the outside: the key step

An Incoming Call Route with the Incoming Group ID of our line. As the destination, set a short code that runs Dial to your carrier's line group. Then the contact's number that comes from us is dialed through your trunk.

A typical short code: Code: ?, Feature: Dial, Telephone Number: ., Line Group ID: your carrier's group. The outgoing number override is set in the same place, in the short code or in the carrier line settings.

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.

Option 2. Avaya Aura

In Aura, the connection is built from three entities:

  • SIP Entity for the address pbx.autocall.kz with the type SIP Trunk and an Entity Link to Session Manager (UDP/TLS, port 5060);
  • Routing Policy and Dial Pattern for numbers like +7XXXXXXXXXX that send the call to Communication Manager;
  • in Communication Manager, a regular route pattern to your carrier's trunk and public-unknown-numbering to set your number.

Transfers to extensions need no separate setup: the short number from the scenario is routed by your existing rules.

Codecs and encryption

Keep only G.711A on the line. TLS is enabled by the line transport (IP Office) or the Entity Link (Aura), SRTP by the media profile. In the dashboard, select the TLS transport as well.

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

  • The line doesn't come up. Check the firewall and that SIP URI is set to *: with a strict Local URI the PBX rejects calls to an unknown number.
  • The call arrives and ends right away. No Incoming Call Route matches the Incoming Group ID, or the short code has no access to the carrier's line group.
  • The carrier rejects calls. The outgoing number is not overridden.
  • Connects, but silence. The voice subnet is not open, or Direct Media gets in the way. Try turning it off on the line.

The IP Office and Aura interfaces differ noticeably between releases. If your menu items have other names, write to support and we will sort it out for your version.

Which line type should I create on Avaya IP Office?

A SIP Line with the platform's IP address and UDP or TLS transport. No registration is needed: the platform calls the PBX address itself, and it is identified by its address.

How do I send a call from the line out to the carrier in IP Office?

With an Incoming Call Route whose destination is a short code that runs Dial to your carrier's line group. Then the contact's number that came from our line is dialed through your trunk.

What do I configure in Avaya Aura?

A SIP Entity and an Entity Link to the platform address in Session Manager, then a Routing Policy and a Dial Pattern that send numbers like +7XXXXXXXXXX to Communication Manager, and there a regular route pattern to the carrier trunk.

Is encryption supported?

Yes: TLS for signaling and SRTP for voice. Turn them on together. The voice encryption key travels inside the SIP message, so over open signaling the protection would only be for show.

How to connect AI to Avaya

You don't need to connect AI to your PBX separately: the SIP trunk you set up above also works for the voice AI agent. The agent calls customers through your PBX (Avaya), from your numbers and through your carrier, and holds a real conversation: answers questions, clarifies details and logs the outcome of the call.

  1. Connect your PBX in the “PBX” section and confirm it with a test call.
  2. Create an AI agent and describe the task in plain words.
  3. Start a call campaign and choose your PBX in it.

If the contact asks for a person, the agent connects them to an extension on your PBX or to an employee's mobile, and the call goes through the same PBX. Inbound calls work too: create an inbound line for your PBX in the dashboard, and the AI agent will answer the calls your PBX sends to us.

Call from your own numbers through your own PBX

Connection details and prices are on the “Connect your own PBX” page.

Try it free →