Integrating with a CRM, PBX, or application

Connect cloudnumbering to an existing communications platform or to software you build.

Choose the interface

What you need to do	cloudnumbering interface
Receive voice calls	SIP voice endpoint assigned to a number
Make voice calls	SIP trunk destination and allowed source IP
Receive SMS	HTTPS webhook or email endpoint
Send SMS	Customer API
Buy and manage numbers	Customer API or portal

Note: Your CRM, PBX, or middleware must support the interface you choose. cloudnumbering does not configure or host third-party software.

Plan the integration

Identify which voice, SMS, and number-management actions your application needs.
Confirm that your PBX or application supports the corresponding interface in the table.
Follow the setup article for each interface.
Test inbound and outbound traffic with a controlled workflow and test data that is safe to use in your environment.
Record request IDs, SIP Call-IDs, and UTC timestamps so you can trace failures.

CRM integrations

If your CRM does not support cloudnumbering directly, use middleware to translate between the CRM's events and the cloudnumbering API, webhook, or SIP interface. Store API credentials on the server, not in browser or mobile-app code.

PBX integrations

Use a voice endpoint for inbound calls. For outbound calls, send traffic to sip.cloudnumbering.com, allow the PBX's public source IP, and present a cloudnumbering number owned by the account as caller ID.

Troubleshooting

My product is not listed as a supported integration

Check whether it supports custom SIP trunks, HTTPS webhooks, or REST APIs. If it does not, you need middleware or a different communications platform.

An integration works inbound but not outbound

Treat the directions separately. Inbound traffic depends on the endpoint assigned to the number; outbound voice depends on the source IP and caller-ID ownership, while outbound SMS uses API authentication.