Appearance
SIP Connection
A SIP connection lets you bring your own telephony infrastructure — a SIP trunk, a PBX, or an existing carrier relationship — and connect it directly to CallMangal, instead of (or alongside) a supported cloud telephony provider.
When a SIP connection makes sense
- You already have telephony infrastructure or a carrier relationship you want to keep, rather than provisioning numbers through a new provider.
- You need a specific regional or carrier setup that is not covered by a supported cloud telephony provider.
- You are connecting an existing PBX or on-premise system.
What a SIP connection generally requires
Exact fields and steps depend on your specific trunk and carrier, and are confirmed against the live CallMangal product as each setup is documented. In general terms, a SIP connection involves registering your trunk's connection details with CallMangal so that inbound calls can be routed in, and outbound calls can be routed out, over that trunk.
Verify before you commit
This page describes the concept, not a field-by-field setup walkthrough. If you are planning a SIP connection for a real deployment, confirm the exact requirements with the CallMangal team before relying on any assumption not written here.
SIP vs. a supported cloud provider
Both connect a real number to a CallMangal agent workflow; the difference is who manages the underlying carrier relationship:
| Supported cloud telephony provider | SIP connection | |
|---|---|---|
| Carrier relationship | Managed by the provider | Managed by you |
| Number provisioning | Through the provider | Through your existing trunk/carrier |
| Best fit | Getting started quickly, standard deployments | Existing infrastructure, specific regional/carrier needs |