Sinch
Sinch forwards calls to Reception.ai over a SIP trunk. Your numbers stay on Sinch, and Sinch bills you for the minutes. Sinch uses one Voice app to send calls to Reception.ai and a second app to carry transfers back out.
Before you start
- A Sinch account with at least one phone number.
- Sinch’s SIP signaling IP ranges for your region, listed under IP allowlisting in Sinch’s documentation. Reception.ai only accepts calls from addresses you allow.
Setup
Add the SIP trunk in Reception.ai
Go to Integrations, select Add integration, and choose SIP Trunk. Under Inbound allowed addresses, add Sinch’s SIP signaling ranges for the regions you use. Leave the inbound username and password empty; Sinch’s SIP forwarding doesn’t send credentials.
Add the number
Go to Receptionists, select the Phone tile, enter your Sinch number with its country code, and select Add SIP Trunk number. Reception.ai shows the SIP servers and the request URI to use, over TCP or TLS.
Forward calls in Sinch
In the Sinch Build Dashboard, go to Voice and Video → Apps and open (or create) the app your number belongs to. Under Settings, set Handle call events with to SIP Forwarding and enter a forwarding URI that uses the Reception.ai SIP server, for example:
sip:{number}@SIP_SERVER:5061;transport=tls
Sinch replaces {number} with the number that was called. Use port 5060 with transport=tcp if you prefer TCP. Don’t leave out the transport parameter: Sinch uses UDP by default, which Reception.ai doesn’t accept.
Set up transfers
Your receptionist transfers calls by placing a new call through your outbound trunk. In Sinch, create a second app for SIP termination and note its Application Key and Application Secret. In the Reception.ai SIP trunk, set:
The full list of regional hosts is under Termination URIs in Sinch’s documentation.
The Application Secret lets anyone place calls billed to your Sinch account. Keep it out of shared documents, and regenerate it in Sinch if it leaks.