Telephony setup brief

Connect SIP/PSTN to MediaSFU without wandering through the manual.

Use this page to connect a phone provider, verify a number, route calls, and decide whether each call goes to a room, an AI agent, IVR playback, callback flow, or a human operator.

Inbound support

Route callers into a room, AI agent, or operator queue.

Use this when a public number should answer customer calls and escalate cleanly.

Outbound calls

Let staff, apps, or campaigns place PSTN calls.

Use this when MediaSFU needs a verified peer, caller ID, and provider trunk.

AI phone agents

Connect SIP calls to STT, LLM, TTS, and handoff.

Use this when calls should be automated but still observable and transferable.

Shortest production path

Do these in order.

  1. Pick a SIP provider and collect domain, port, transport, username, password, and DID.
  2. Allow MediaSFU gateway traffic in the provider firewall or trunk policy.
  3. Create the SIP config in MediaSFU and verify the phone number.
  4. Decide the route: room, human operator, IVR/audio playback, AI agent, or callback.
  5. Test inbound and outbound calls, DTMF, recording, transcripts, and fallback behavior.
Mode: Basic keeps the path short. Detailed unlocks API fields, events, and call-control reference.

Start Here: Basic Setup or Detailed Setup?

A) Basic Setup (Absolute Essentials)Basic
  1. Need a ready app now? Use the Calls tab on web or a platform app. Download official apps fromDownload Page.
  2. Need provider setup? FollowProvider Setup GuidesandPrerequisites.
  3. Will you use AI voice agents?
    If No: skip AI credentials and keep a non-AI flow.
    If Yes: add TTS first, then optional STT/LLM for full AI conversations.
  4. Configure peer for inbound and outbound reliability. Outgoing additionally requires allowOutgoing.
B) Detailed Setup (Advanced Control)Developer
  1. Use full sections forSIP Config,Webhooks,HTTP API, andSocket Events.
  2. Will you use AI?
    If No: skip AI credentials and AI agent sections.
    If Yes: set AI credentials and configure autoAgent.
  3. Need real-time control? Use Socket Events. Need backend control? Use HTTP API.