Bring-your-own SIP trunk for the cloud PBX.

This integration exists because the underlying service offers capabilities that complement the CloudIP platform.
The SIP Trunking integration is part of the standard CloudIP subscription — it is not a partner-tier add-on or a separate billing line. Authentication, rate limiting, and error handling are managed inside the platform, and any change in the SIP Trunking state of the world propagates to the relevant CloudIP module without operator intervention.
For most customers, the integration is invisible after the initial connection: records appear in the carrier module they belong to, and downstream workflows — reports, audit trail, exports — see the same data the rest of the platform sees. The integration honours the tenant.dataResidency choice you make at provisioning, so SIP Trunking traffic respects the same boundary as your own records.
If you eventually outgrow the SIP Trunking integration, the data it touches stays inside CloudIP — the integration is a connector, not a system of record. That means swapping SIP Trunking for an alternative does not require a data migration; it requires reconnecting the source.
Yes. The SIP Trunking integration is part of the platform; there is no per-integration fee or premium tier required to use it. You bring your own SIP Trunking account where applicable, and CloudIP handles the connection.
See how CloudIP and its integrations work together on real data.