Oduist Connect
Start free trial

Connect modules connect_telnyx

Provider integration

Connect Telnyx

Telnyx integration for Oduist Connect.

Full cloud telephony on Telnyx, controlled from Odoo: TeXML call flows and IVR, WebRTC and SIP phones, SMS, WhatsApp and RCS, call recordings, and provider-native AI voice assistants — with no PBX to run and no sidecar service to host.

Numbers, extensions, call flows, caller IDs, TeXML applications and SIP domains are Odoo records under the Telnyx menu, while calls, messages and recordings land in the shared Connect ledger alongside every other provider. Nothing is imported from another provider’s module, so Telnyx can run in the same database as Connect Twilio, FreeSWITCH or Asterisk, and each user picks the provider their click-to-call uses.

What makes it different from the other cloud backends is that voice AI is part of the provider rather than a separate stack: a Telnyx AI Assistant is an Odoo record whose prompt, language policy, voice, turn-taking plan and tool set are pushed to Telnyx and answered over the same TeXML routing application as ordinary calls. Webhooks are verified with the account’s Ed25519 public key, and each assistant’s Odoo tools use their own rotatable token.

What it offers

  • Numbers routed from Odoo

    Every Telnyx number is assigned in Odoo to a user, a call flow, a TeXML application or an AI assistant. SYNC TELNYX ACCOUNT imports the numbers, SIP domains and owned caller IDs of the account, creates the matching TeXML applications and wires the webhook URLs back to your Odoo instance.

  • Telnyx AI Assistants owned by Odoo

    Assistants are created and edited as Odoo records and published with Push to Telnyx, which also configures their signed dynamic-variable and tool webhooks. Contact lookup, internal notes, CRM leads and Helpdesk tickets are exposed to the assistant as tools when the matching Odoo apps are installed.

  • Receptionist modes and warm transfer

    An assistant answers either as a personal receptionist for one manager or as a company receptionist that replaces an IVR using department callflows. With Check Registration Before Transfer, Odoo queries GET /v2/sip_registration_status for each credential and only offers registered SIP or WebRTC devices as transfer targets.

  • Voice picked from your account catalog

    Voices come from the cached Telnyx text-to-speech catalog, filtered by language and provider and searchable by name, gender or Telnyx ID, so cloned voices appear under their own name. The speaker button plays a Telnyx-generated sample that validates the voice and speed combination before a caller ever hears it.

  • Turn taking you can tune

    Wait Before Speaking plus three endpointing values — pause without punctuation, after punctuation, and while digits are dictated — decide when the assistant treats a pause as the end of a turn. Caller Silence Timeout defaults to 60 seconds because Telnyx never ends a conversation on its own.

  • SIP domains and per-user credentials

    Creating a SIP domain provisions a Telnyx credential connection and reserves a <subdomain>.sip.telnyx.com subdomain on the routing TeXML application. Each user gets a Telnyx-issued SIP username and password readable with a copy button for hardphone provisioning, while the web phone authenticates with a short-lived token.

  • SMS, WhatsApp and RCS

    The sync creates an Odoo Connect messaging profile and attaches SMS-capable numbers to it. WhatsApp senders and templates are synced with their Meta approval status and new templates can be submitted from Odoo; RCS agents are synced read-only and send text with an optional SMS fallback.

  • Assistant recordings with a summary

    When assistant recording is on, the audio, conversation messages and the configured insight summary land on one Recordings row, with the audio pulled into an Odoo attachment before the signed Telnyx URL expires. The summary wording is the AI Summary Instructions field, and Telnyx stays the transcription provider so nothing is sent for a second transcription.

Scope of the current version

  • Odoo must be reachable on a public HTTPS URL — every Telnyx event arrives by webhook under /telnyx/webhook/* and the TeXML voice URLs are derived from the core Connect api_url.
  • The telnyx and nacl Python packages must be available in the Odoo environment.
  • Telnyx signs the webhook body byte for byte, so a reverse proxy in front of Odoo must forward the POST body without decoding and re-encoding it.
  • Telnyx only places calls to the countries whitelisted on the account's outbound voice profile, and a new profile allows US, CA only — the list is editable as Outbound Destinations in the settings.
  • Attended transfer from the web phone is not available yet, and the built-in Transfer tool gives the caller ringback rather than hold music while the recipient is briefed.
  • WhatsApp voice calling is not integrated and RCS is text plus SMS fallback — rich cards and carousels are not composed from Odoo.
  • Odoo is the source of truth for assistants: assistants created only in Telnyx Mission Control are never imported or changed.
  • Call cost is read from Telnyx detail records after the call and may lag behind completion.
Get Connect on GitHub Ask a question

Installs with full features free for 30 days; buy the license inside the module.

← All Connect modules