Integrations

How to connect Panasonic KX-NS and KX-NSX 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 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

What you need

This article follows Web Maintenance Console for KX-NS500, KX-NS1000 and KX-NSX. Menu names differ slightly between firmware versions, but the steps are the same.

The trunk lives on the V-SIPGW virtual card. No physical card is needed, but the number of channels is limited by activated licenses: you get as many concurrent calls as you have licensed channels.

Step 1. Virtual card

Configuration → Slot: add V-SIPGW16 (or the card available on your model) to a free virtual slot and activate the number of channels you need.

Step 2. Port properties

Configuration → Slot → V-SIPGW → Port Property:

  • Provider Name: autocall;
  • SIP Server / Registrar / Proxy: pbx.autocall.kz, port 5060;
  • Register: off. We place the calls ourselves, so no registration is needed;
  • Authentication: leave empty if the PBX doesn't require authentication;
  • Codec: keep only G.711A;
  • DTMF: RFC2833.

Step 3. Routing: the key step

The goal: a call that arrives from the trunk for the contact's number must go out through your PSTN trunk with your CallerID.

  • ARS (Automatic Route Selection): a route for numbers like +7XXXXXXXXXX to your external line group. If needed, strip the + with a dialed number modification rule.
  • Class of service. A call from our trunk must have outbound calling rights and trunk-to-trunk call rights (a call from one line to another). Without them, Panasonic rejects the call even if the route is set up correctly.
  • Outgoing number (CLIP) on the PSTN trunk: 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 need no extra setup: the PBX finds the short number from the scenario on its own.

Step 4. Network and firewall

If the PBX is behind a router, forward the signaling port and the voice port range, and set the external address in the NAT settings. Otherwise Panasonic sends us its internal address in the media description, and the audio will be one-way.

Encryption (optional)

TLS and SRTP support depends on the model and firmware version. If your PBX supports them, turn both on 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 5. 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 V-SIPGW card is not activated.
  • Calls arrive but don't go out. There are no trunk-to-trunk call rights, or the number pattern in ARS doesn't match.
  • The carrier rejects calls. Your number is not set in CLIP.
  • Only one side can be heard. Classic NAT: the PBX external address is not set, or the voice subnet is not open.
  • Busy with several concurrent calls. V-SIPGW is out of channels. Lower the channel limit in the dashboard or activate more licenses.

Which card does a SIP trunk use on Panasonic KX-NS?

The V-SIPGW virtual card: you add it to a free slot in Web Maintenance Console, and it provides the channels you need. No physical card is required, but the number of channels is limited by activated licenses.

Does the call campaign platform need to register?

No. Registration is turned off in the port properties, and the platform address is set as the SIP server: we call your PBX ourselves, and identification is by IP.

Why does Panasonic accept the call but not send it out?

Trunk-to-trunk calls are not allowed. The class of service applied to calls from our trunk must have outbound calling rights, and ARS must have a route for the contact's number.

Which codec should I keep?

G.711A, also known as alaw, the standard for Kazakhstan networks: there is no transcoding, and the PBX doesn't waste resources.

How to connect AI to Panasonic KX-NS

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 (Panasonic KX-NS), 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 →