--- title: "Telephony Integration Overview" slug: "ai-agents-telephony-integration-overview" updated: 2026-11-02T11:41:55Z published: 2026-11-02T11:41:55Z canonical: "docs.sestek.com/ai-agents-telephony-integration-overview" --- > ## Documentation Index > Fetch the complete documentation index at: https://docs.sestek.com/llms.txt > Use this file to discover all available pages before exploring further. # Telephony Integration Overview A Voice Agent is an AI agent that answers phone calls. In the recommended integrations, calls reach SESTEK AI Agents through two components: - **SESTEK IVR**, the telephony gateway. It receives the call over SIP and carries its audio (RTP). - **Data Flow**, which does the audio work. It turns the caller's speech into text with conversational speech recognition (SR), and the Voice Agent's reply back into speech with text-to-speech (TTS). SESTEK IVR and Data Flow are connected over a WebSocket that carries the call audio and the call events in both directions. Data Flow sends what the caller said to the Orchestrator as text, over the Sync API, and receives the reply as text. The Orchestrator runs the project flow and never handles audio. ![virtual-agent-topology-IVR Topology.drawio.png](https://cdn.document360.io/9bca2910-6a3b-4224-9470-43f91f9a6d57/Images/Documentation/virtual-agent-topology-IVR%20Topology.drawio(3).png?sv=2026-02-06&spr=https&st=2026-11-21T18%3A43%3A31Z&se=2026-11-21T19%3A43%3A31Z&sr=b&sp=r&sig=uQpv0%2Bsc0ufgoyGk19XYLU715XZo4rs3hn94vPCpVYU%3D) --- ## Integration options | Option | What your telephony does | Where it connects | | --- | --- | --- | | **Option 1** | Your IVR keeps the call and sends the caller's audio to SESTEK IVR over a SIP session (RTP media). | SESTEK IVR | | **Option 2** | Your IVR or PBX transfers the call to SESTEK IVR over SIP. Without an IVR, calls can be routed straight to SESTEK IVR. | SESTEK IVR | | **Option 3** | Your IVR keeps the call and runs speech recognition and TTS itself, typically through MRCP. It sends the caller's words to the Orchestrator as text and plays the reply. See [Text-Based Integration](https://docs.sestek.com/docs/en/virtual-agent-text-based-integration). | Orchestrator (Sync API) | Options 1 and 2 are recommended for new integrations. Option 3 is still supported. In Options 1 and 2, each phone number (DID) is associated with one SESTEK AI Agents project, so the number the caller dials decides which project answers. In Option 3, your IVR names the project in each request. --- ## Deployment | Deployment | Where SESTEK IVR, Data Flow and SESTEK AI Agents run | How your telephony connects | Setup | | --- | --- | --- | --- | | **On-premises** | In your environment | A SIP trunk from your IVR or PBX to SESTEK IVR | [SIP Trunk Integration (On-Premises)](https://docs.sestek.com/docs/en/ai-agents-sip-trunk-integration-on-premises) | | **Cloud** | In the Sestek cloud | A SIP trunk from your telephony platform to the Sestek Cloud SBC | [SIP Trunk Integration (Cloud)](https://docs.sestek.com/docs/en/ai-agents-sip-trunk-integration-cloud) | Whichever you choose, create the SESTEK AI Agents project for the voice channel and publish it before you test calls.