Use this quick decision flow first. It tells you exactly what to configure and what to skip.
Business User Start with apps, widgets, and calling access Use MediaSFU clients, downloads, or call widgets before you touch provider or API details. Open app-first path SIP Admin Start with prerequisites, trunks, and routing Focus on network requirements, provider setup, and the core SIP reliability checks first. Open provider path SDK / API Builder Start with the config object and control surfaces Jump into config fields, webhooks, HTTP APIs, and socket events when you need full control. Open builder path A) Basic Setup (Absolute Essentials)Basic Need a ready app now? Use the Calls tab on web or a platform app. Download official apps fromDownload Page . Need provider setup? FollowProvider Setup Guides andPrerequisites . 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.
Configure peer for inbound and outbound reliability. Outgoing additionally requires allowOutgoing. B) Detailed Setup (Advanced Control)Developer Use full sections forSIP Config ,Webhooks ,HTTP API , andSocket Events . Will you use AI?If No: skip AI credentials and AI agent sections.
If Yes: set AI credentials and configure autoAgent.
Need real-time control? Use Socket Events. Need backend control? Use HTTP API. Direct rule: No AI use case means no STT/LLM setup. TTS is only needed for dynamic spoken prompts.