Skip to content

Connect Telnyx

Rindee is bring-your-own-carrier. Your number stays on your Telnyx account; Rindee only handles the call leg. Nothing is ported, and you can stop calls reaching Rindee with a single switch.

Telnyx is the most automated of the three paths — you paste an API key and Rindee provisions the carrier side for you. Budget about 10 minutes.

  • A Telnyx account with at least one number on it.
  • A Telnyx API key (v2).
  • The Rindee dashboard open at app.rindee.ai.

In the Telnyx portal, open API Keys and create a key. Copy it — it starts with KEY.

Rindee stores the key encrypted and uses it to read the numbers on your account and to create the SIP connection in step 4. It is never exposed back to the browser after saving.

Open Numbers in the sidebar, then Manage ProvidersAdd Provider.

Choose Telnyx, give the account a Label (e.g. Main account — this is just for your own reference when you have several), paste the Telnyx API Key, and press Continue.

The Add Provider dialog on step one, Account, with Telnyx selected and an API key entered

Rindee reads the numbers on the account and lists them. Tick the ones you want to use, or Select all.

Each row shows whether the number already belongs to a Telnyx connection:

  • No connection — the number isn’t routed anywhere yet.
  • A connection name — the number is already attached to something on Telnyx. Selecting it here will move its inbound routing to Rindee.

If the list is empty, the account has no numbers on it — buy or port one in the Telnyx portal first, then come back.

Step two, Numbers, listing three numbers — one already on a Telnyx connection, two with no connection

Rindee needs an FQDN connection on your Telnyx account to receive calls. Either reuse one you already have (Use existing) or let Rindee make one (Create new).

There is no SIP username or password to set here, and that’s deliberate: Telnyx delivers inbound calls to Rindee’s SIP proxy over an FQDN connection and authenticates by source IP. Rindee allowlists Telnyx’s published signaling ranges for you.

Rindee fills in the connection’s destination and transport as part of this step — you don’t need to enter or change anything on the Telnyx side.

Step three, Connection, showing the source-IP notice, the connection mode toggle and the voice profile picker

A Telnyx outbound voice profile is what authorises outbound calls. Select an existing profile, or choose + Create new, name it, and press Create.

If you picked an existing connection that already has a profile attached, Rindee uses that one and won’t ask.

Press Add Provider to finish. Your numbers now appear on the Numbers page.

New numbers start with inbound off. This is a safety default so a number never takes live calls before you’re ready.

Flip the Inbound switch on each number you want answering. Turning it off again stops inbound calls immediately; outbound is unaffected.

The Numbers table with the Inbound switch on for two numbers and off for one, and an agent assigned to each

In the Inbound agent column, pick the agent that should answer that number. One number routes to one agent.

Ring the number from your own phone. The assigned agent should pick up with its greeting.

“No phone numbers found on this Telnyx account” The API key is valid but the account holds no numbers. Add one in the Telnyx portal, then reopen the wizard.

The number appears in Rindee but calls don’t reach an agent Check the two switches that gate inbound: the Inbound toggle is on, and an Inbound agent is assigned. A number with inbound on but no agent has nothing to hand the call to.

Outbound calls fail The connection has no outbound voice profile attached. Reopen Manage Providers and add one.

You changed numbers on Telnyx Open Manage Providers and press Sync on the account to pull the current list. You don’t need to re-add the provider.

  • Connect Twilio — same shape, but you choose the SIP credentials Rindee uses for outbound.
  • Connect a SIP trunk — any other SIP-capable carrier, configured by hand.