Skip to main content
Simple AI connects to Amazon Connect in one of two ways: a contact flow transfers the call to a number that routes to Simple AI, or you peer a SIP trunk to Simple AI through an Amazon Chime SDK Voice Connector. Amazon Connect keeps routing, queues, agent state, and reporting either way. Amazon Connect does not expose SIP trunking directly. On AWS, the Chime SDK Voice Connector is the SIP endpoint, and a Connect contact flow reaches it the same way it reaches any other destination.

What You Can Do

  • Inbound routing — a contact flow answers the call, runs your IVR logic, then hands the conversation to Simple AI.
  • Outbound campaigns — Amazon Connect outbound campaigns handle pacing and compliance, and transfer connected calls to Simple AI.
  • Direct outbound — Simple AI places calls through the Voice Connector with your existing caller ID.
  • Live agent escalation — Simple AI transfers back to a number claimed in Amazon Connect, whose inbound flow routes the call to the right queue.
  • Your numbers, your caller ID — calls run on numbers you provision in AWS rather than on Simple AI’s default telephony.

How It Connects

Option 1: Contact Flow Transfer

The simplest path. A Transfer to phone number block sends the call to a number that routes to Simple AI. There is no SIP configuration on your side, and no Voice Connector to run. Use this when Amazon Connect should stay the front door and you do not need your own numbers or trunk on the Simple AI side.

Option 2: Chime SDK Voice Connector

Peer a Chime SDK Voice Connector to Simple AI over SIP. Numbers you provision in AWS then reach Simple AI directly over SIP, with TLS and SRTP available, and Simple AI can place outbound calls through the same trunk using those numbers as caller ID.

What Neither Option Carries

Amazon Connect reaches Simple AI by dialing a number, in both options. A Transfer to phone number block places an ordinary telephone call, so the handoff to Simple AI is a telephone transfer even when the number belongs to a Voice Connector. That has one consequence worth planning around: Amazon Connect contact attributes do not travel with the call. Simple AI reads context from X- prefixed SIP headers on the incoming INVITE, and Amazon Connect does not attach custom SIP headers to a transfer. Attributes your flow set stay inside Amazon Connect. If the AI needs to know something the flow already learned, supply it out of band — have the flow invoke a Lambda that starts the call through the calls API with params, or look the caller up from the AI side using their number. Platforms that can set SIP headers on transfer, such as Genesys and NiCE CXone, do not have this constraint. The rest of this page covers the Voice Connector setup.

Prerequisites

  • An AWS account with access to the Amazon Chime SDK console.
  • A phone number provisioned in Amazon Chime SDK, or the ability to order one.
  • A Simple AI account with permission to manage phone numbers, and a voice agent already built.
  • Simple AI’s signaling networks, which you add to the Voice Connector’s allowlist. Ask your account team or support@usesimple.ai for the current ranges.
SIP connectivity is available on Enterprise plans.

Step 1: Create the Voice Connector

In the Amazon Chime SDK console, open Voice Connectors and create one: Encryption enabled means the Voice Connector speaks TLS for signaling and SRTP for media. Note which you chose — every later step on both sides has to match it. From the Voice Connector’s details page, save the Outbound host name. It looks like abcdef1ghij2klmno3pqr.voiceconnector.chime.aws and is the endpoint Simple AI sends outbound calls to.

Step 2: Assign Phone Numbers

Open the Voice Connector’s Phone numbers tab, choose Assign from inventory, select the numbers this trunk should serve, and confirm. If your inventory is empty, order numbers first under Phone number management → Orders → Provision phone numbers. Record every number in E.164 format, for example +14155552671. You will enter the same numbers in Simple AI, and they have to match exactly.

Step 3: Enable Termination for Outbound Calls

Termination governs calls that Simple AI originates through the Voice Connector. Skip this step if you only need inbound. On the Voice Connector’s Termination tab:
  1. Set Termination to enabled.
  2. Under Allowed hosts, add Simple AI’s signaling CIDRs. Calls from any other network are rejected.
  3. Under Calling plan, select the countries Simple AI is allowed to call.
  4. Optionally create Credentials — a username and password — for SIP digest authentication on top of the IP allowlist. Save both; you enter them in Simple AI in the next step.

Step 4: Connect the Trunk in Simple AI

In the Simple AI dashboard, go to SIP trunks → Connect SIP trunk and fill in the form with your Voice Connector’s values: The signaling source CIDRs are what let inbound calls in — Simple AI only accepts SIP INVITEs from the networks you list here. Look up the SIP signaling subnet for your region in the AWS Voice Connector network configuration reference. For example:
Connection settings are fixed once the trunk is saved. To change the endpoint, credentials, or numbers, unassign agents from the numbers, disconnect the trunk, and reconnect it with the new settings.
Save the form. Simple AI provisions routes for each number in the background; the trunk’s detail page shows Configured when a number is ready, and offers Retry setup if one fails.

Step 5: Configure Origination for Inbound Calls

Origination governs calls arriving from the PSTN that the Voice Connector forwards to Simple AI. On the Voice Connector’s Origination tab, set Origination status to enabled, then add an inbound route: Your Simple AI trunk’s detail page shows the same inbound domain under Finish inbound routing, so you can copy it from there. The Voice Connector sends the dialed number as the destination user in the SIP INVITE, which is how Simple AI matches the call to a number and its agent.

Step 6: Assign Agents and Test

Open each connected number from the trunk’s detail page, or from Numbers, and assign the voice agent that should answer it. Then place an inbound test call to that number — Amazon Chime SDK forwards it to Simple AI and the agent answers. If the trunk also handles outbound, place a test call through the API using one of its numbers as the caller ID. from_number_id is the number’s UUID, which you can read from its dashboard URL or from List Numbers:
Before moving production traffic, verify caller ID, audio quality, DTMF, and a live agent escalation back into Amazon Connect.

Routing Amazon Connect Calls to the Trunk

With the Voice Connector in place, point the contact flows that should use the AI at one of its numbers:
  • Inbound — add a Transfer to phone number block to the flow, targeting a number on the Voice Connector.
  • Outbound campaigns — configure the campaign’s connected-call handling to transfer to a Voice Connector number, so Amazon Connect keeps pacing, DNC, and answering machine detection.
  • Escalation back — claim a number in Amazon Connect, associate it with an inbound flow that transfers to the queue you want, and give Simple AI that number as the transfer destination. Transfer destinations are E.164 numbers or SIP URIs; a queue identifier is not dialable, so the queue has to sit behind a number.

Troubleshooting

For SIP-level detail, enable SIP logging on the Voice Connector’s Logging tab to get full message traces in CloudWatch.
Last modified on September 3, 2026