Appearance
Telephony Overview
Telephony is the layer that connects a real phone number, SIP trunk, or calling system to a CallMangal agent. It is what turns a workflow you have tested in your browser into something a real caller can dial, and something your agent can dial out on.
Test before you connect telephony
You do not need a phone number to build or test an agent. Build the workflow, then run a browser test over WebRTC first. Connect telephony once the workflow behaves the way you want on a real conversation.
What telephony covers
- Inbound calling — a caller dials a connected number and reaches an agent workflow. See Inbound Calling.
- Outbound calling — an agent calls out, individually or as part of a campaign. See Outbound Calling.
- SIP / custom infrastructure — connecting an existing SIP trunk, PBX, or carrier relationship instead of (or alongside) a supported cloud telephony provider. See SIP Connection.
- Webhooks & callbacks — what happens after a call, sent to your own systems. See Webhooks & Callbacks.
Provider categories
CallMangal is built to work with more than one kind of telephony setup, rather than locking you into a single carrier:
| Category | What it means |
|---|---|
| Global cloud telephony | Cloud calling platforms with wide international coverage. |
| India / local providers | Providers and carrier relationships common in Indian deployments. |
| SIP / custom infrastructure | Your own SIP trunk, PBX, or an existing carrier relationship, connected directly. |
The specific providers CallMangal supports, and the exact setup steps for each, are documented individually as each one is verified against the live product — see the provider pages linked from this section as they become available. Do not assume a provider not yet documented here works identically to one that is; confirm with the CallMangal team before committing to a specific provider for a deployment.
Provider vs. CallMangal responsibilities
However you connect, the division of responsibility is the same shape:
- Your telephony provider or SIP infrastructure handles carrier connectivity, phone number provisioning, and the underlying call routing between the public phone network and CallMangal.
- CallMangal handles the conversation itself — understanding the caller, running the configured workflow, capturing the call outcome, recording and transcribing where enabled, and triggering whatever happens next (a webhook, a CRM update, a human handoff).
Before you connect a number
- The workflow has been through at least one clean browser test.
- You know whether this is an inbound number, an outbound-only setup, or both.
- Your account has credits — telephony calls, like browser tests, draw against your balance.
Troubleshooting overview
Most telephony connection problems trace back to one of a small number of places:
- Authentication/registration — the connection between CallMangal and your provider or SIP trunk is not established.
- Number routing — the number is not pointed at the right agent or workflow.
- Network/firewall — SIP or media traffic is being blocked somewhere between your infrastructure and CallMangal, if you are connecting your own trunk.
Confirm a browser test still works cleanly first — that isolates whether an issue is in the workflow itself or in the telephony connection. If it is the connection, contact the CallMangal team with the provider, the number, and what you see (or do not hear) on a test call.