TOBi managed LLM

TOBi (type vodafone_tobi) is a managed LLM integration, not a modular STT/TTS vendor. The platform hosts the conversational brain; your flow configures how Delphi forwards SIP context to the bot and which managed actions (transfer, hangup) the bot may trigger.

Rendered on the canvas as the Managed LLM node.

⚑Feature required: additionalProviders

This feature is gated. Operators enable it per deployment in the Delphi Portal; if the flag is off, the surface described below is hidden from the UI and rejected by the API. See Feature flags for the full registry.

Pipeline role

Stage	TOBi
STT / TTS / Realtime	Not configured here — handled by the managed integration
LLM	vodafone_tobi in pipeline LLM slot or Managed LLM node

Key fields

Field	Description
Base URL	Vodafone chatbot API host (with or without /v1/chatbot path suffix)
Client ID / Client Secret	OAuth-style credentials via team variables
Bot name	Managed bot identifier
Callback / response paths	Advanced routing for bot callbacks
Channel Data Forwarding	SIP header → bot context rules — see SIP header context rules
Application Metadata	Optional VGW metadata attributes sent to TOBi at conversation creation.
DTMF defaults	Managed DTMF collection defaults for the integration

Managed transfer and hangup actions are configured on the Managed LLM / Managed action inspectors and validated at runtime against platform egress and transfer restrictions.

TOBi often sends multiple text messages before hangup; pipeline mode plays them in order and defers hangup until speech finishes. See Speech playback and hangup.

Application Metadata

The Managed TOBi panel includes an Application Metadata section (SCRUM-793 / VGWK-124). Select only the VGW attributes the bot should receive; Delphi sends nothing by default until a flow opts in. Selected attributes are merged into create-conversation channelData together with SIP header forwarding rules, but the attribute list is independent of those rules.

Attribute	Value source
VGW-Environment	VGW_ENVIRONMENT, then ENVIRONMENT, then OTEL_DEPLOYMENT_ENVIRONMENT.
VGW-ConversationID	TOBi/managed conversation identifier when available.
VGW-IpTelpro	TelPro edge IP propagated by TelPro.
VGW-IpVoice	Voice instance IP.
VGW-CallId	SIP Call-ID / Delphi call correlation ID.
VGW-Callee	Called number or endpoint.
VGW-Caller	Caller number.
VGW-CallerHost	Caller host from SIP signaling when available.

Application metadata is separate from Channel Data Forwarding. Internal Delphi headers, including TelPro-provided VGW helper headers, are not forwarded through channelDataRules, but they can still be resolved into selected Application Metadata attributes.

Publish required

After changing Application Metadata checkboxes (or related Channel Data rules), publish the flow. Draft-only changes are not served to live endpoints, so metadata will not appear in channelData until publish.

Set optional VGW_ENVIRONMENT on the Voice host when VGW-Environment should be a deployment label distinct from generic ENVIRONMENT — see the environment variable index.

Screenshotguide/users/flow-designer/tobi-application-metadataplaceholder

Managed TOBi Application Metadata section with selectable VGW attributes

Highlight: Application Metadata checkboxes for environment, call ID, caller/callee, and TelPro/Voice IPs

Sensitive storage (transcripts and logs)

TOBi can request that Delphi treat a session as sensitive so transcript / log persistence is suppressed or restored mid-call. The bot sends this via channel data / runtime commands (sensitiveInfoOnStorage / update_sensitive_storage). Delphi applies the update in arrival order so older protected text is not written after a later enable.

Use this when a conversation must not retain STT/TTS transcript artefacts even if the app Recording toggle is on. See also Recording and transcript storage.

DTMF collection

Managed DTMF defaults (max digits, timeouts, inter-digit timeout, terminator) are configured on the TOBi panel and can be updated live with the update_dtmf_config callback action (interDigitTimeoutMs, timeoutMs, and related fields). Field reference: Managed callback actions.

API reference

Bot callback payloads (transferTarget, hangupSipHeaders, failover, and related fields) are documented in Managed callback actions.

See also

• Speech playback and hangup — multi-message TTS queue and hangup timing for managed integrations
• SIP header context rules
• Managed callback actions
• Providers overview
• Egress trunks — outbound transfer routing