Does Open work with Sinch Voice API SVAML?

Yes. Use a `connectSip` action in your SVAML response to send the call leg to Open.

Does Open work with Sinch SIP Trunking?

Yes. Add Open as the termination URI in the Sinch portal and route inbound DIDs to it.

Can I keep my Sinch numbers and bundles?

Yes — DIDs and regulatory bundles stay on Sinch.

What does this cost on top of Sinch?

Sinch invoices carrier minutes at their published rate. Open charges per resolved conversation with no markup.

Can the AI transfer to a human?

Yes — SIP REFER and PSTN bridging are both supported.

Is the SIP signaling secure?

TLS and SRTP are both supported.

How do I route different Sinch numbers to different AI agents?

Map them in the Open dashboard, or pass a routing header from your SVAML.

How long does setup actually take?

Inbound is typically under 15 minutes — Sinch portal navigation adds a couple of extra minutes vs. pure CPaaS providers.

CPaaS · Voice API

Open for Sinch

Point a Sinch Voice application or SIP trunk at Open and the AI picks up — across Sinch's global PSTN reach.

Try now

Setup time: Under 15 minutes
Auth: Digest credentials or IP allowlist
Directions: Inbound · Outbound · Call transfer
Pricing: Included with Open

01 — Overview

Can I use AI with my Sinch Voice or SIP Trunking setup?

Yes. Sinch keeps the carrier-of-record role; Open is the SIP destination Sinch routes calls to when you want AI to answer.

Sinch stays your voice provider. Numbers, regulatory bundles, and the global PSTN reach Sinch is known for all stay where they are. Open is a SIP endpoint your Sinch Voice application or SIP trunk forwards calls to. When a call should be handled by AI, Sinch sends the INVITE to Open, the AI picks up, and the rest of the conversation runs over the same SIP/RTP path.

For inbound, the typical path is a Sinch Voice application callback that returns an SVAML connectSip action targeting the Open SIP URI. If you're on Sinch SIP Trunking, you instead configure a termination route in the Sinch portal that sends inbound DIDs to Open — same effect, less code.

For outbound, Open opens a SIP session against your Sinch SIP termination URI using digest credentials. Calls land in your Sinch CDRs the same way as today, with whatever caller IDs Sinch has approved on the trunk. AI-driven outbound campaigns run from Open while staying on the Sinch carrier leg.

What the AI does on the call: it listens, reasons over your knowledge base and connected tools, and acts — looking up records, creating tickets, sending payment links, or warm-transferring to a human via SIP REFER with the live transcript and detected intent attached. Every call is recorded and trace-logged.

Billing stays predictable. Sinch bills carrier minutes at their published rate; Open never marks them up. Open charges per resolved conversation, not per agent or per seat.

What stays the same on Sinch

Sinch numbers and bundles
DIDs, regulatory bundles, and Sinch invoice don't move.
SVAML applications
Voice application callbacks and routing logic stay intact. Open is a `connectSip` destination.
Approved caller IDs
Outbound presents Sinch-verified caller IDs.
Global PSTN reach
Sinch handles the carrier leg in every country it already reaches.

What's new with Open

A SIP destination on Sinch
Open's SIP URI becomes a `connectSip` target or a Trunking termination route.
AI handles the conversation
The AI greets, listens, calls your tools, and replies in natural speech.
Transfers carry context
Human agents receive the live transcript and detected intent on SIP REFER.
Pricing model
You pay Open per resolved conversation. Carrier minutes stay invoiced by Sinch.

02 — Why this works

The native Sinch experience

Native SIP — no middleware
Open registers as a SIP endpoint your Sinch Voice or Trunking platform talks to directly.
Bring your own Sinch numbers
Keep DIDs and bundles on Sinch. Map any number to a specific AI agent.
Voice + Trunking, both work
Whether you use Sinch's Voice API SVAML callbacks or Sinch SIP Trunking, Open slots in as a destination.
Multi-region SIP endpoints
Pick US, EU, APAC, or global auto-route to align with Sinch's global footprint.

03 — Setup guide

Wire up Sinch in under 15 minutes

Two trunks — one inbound, one outbound. Both configurable from Settings → SIP in the Open dashboard.

1
Open Settings → SIP
Open the inbound trunk configuration in OpenCX.
2
Pick a SIP region
Choose Global, US, EU, or APAC.
3
Copy the SIP credentials
Grab the SIP endpoint, username, and password.
4
Return SVAML with connectSip
In your Sinch Voice application callback, return `{"action":{"name":"connectSip","destination":{"type":"sip","endpoint":"sip:open-uri"}}}` for calls you want AI to answer.
5
Or configure Sinch SIP Trunking
In the Sinch portal, set Open's SIP endpoint as the termination URI for the inbound numbers you want AI'd.
6
Add your Sinch numbers to Open
Register each Sinch DID under Phone Number (DID).
7
Assign numbers to an AI agent
Channels → Phone → Agents → assign DIDs.
8
Place a test call
Dial a Sinch number and confirm Open answers.

04 — Configuration

Settings → SIP, at a glance

A real inbound trunk for Sinch looks something like this. Yours are generated when you open Settings → SIP.

Inbound trunk · Sinch

Sample

SIP endpoint: sip.eu.opencx.comEU region
Transport: TLSrecommended
Username: open_inbound_snch…
Password: ••••••••••••••••
SVAML action: connectSip → sip:open-uri

05 — Security

Encrypted, audited, refundable

SIP over TLS for signaling, SRTP for media. Every call is logged with full reasoning traces. SOC 2 Type II, GDPR-aligned, HIPAA- and PCI-ready. Backed by the Open $2M Refund Guarantee.

06 — FAQ