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.
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
v0.9.15 adds an Application Metadata section to the Managed TOBi panel. Select only the VGW attributes the bot should receive; Delphi sends nothing by default until a flow opts in.
| 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.
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