Skip to main content

Delphi v0.9.17-patch2

Delphi Team
KI Kombinat GmbH

Delphi v0.9.17-patch2 reduced unnecessary work in the SIP edge's periodic reconciliation, added exact searches for structured flow and TOBi conversation IDs, corrected trunk health probe replies and result storage, and closed remaining audit-display and telemetry-redaction gaps. It also improved targeted AI flow edits, tool-code validation, realtime transcript timing and call transitions, and made error alarm attributes as searchable as informational events. These follow-up fixes were not included in patch1.

Platformv0.9.17-patch2Recommended SDKv0.1.5Supported SDK range>=0.1.3 <0.2.0

Highlights​

  • Idle TelPro reconciliation reused deployed Redis settings and stopped launching temporary Redis-client containers. Fresh configuration is still fetched for actual refresh or recovery work.

  • Trace Debug found flowDefinitionId and tobiConversationId in structured attributes, including legacy forms, even when the IDs were absent from log bodies.

  • SIP OPTIONS monitoring recorded successful carrier replies and timeouts correctly, with valid From addresses and compact Redis results.

  • Password-reset audit rows showed the affected email separately from the requester, including anonymous reset requests.

  • Phone masking honored the configured trailing-digit count in shared application logs. Legacy DTMF fields, embedded digit messages and duplicate SIP INFO copies were scrubbed when redaction was active.

  • Unstructured API, Web and Ops log entries received a default severity instead of an empty label.

Flow Builder and conversations​

  • Targeted assistant edits preserved unrelated provider settings, tools and canvas layout. Provider requests respected the configured proxy.
  • Generated and pasted tool code was checked against the same sandbox API described by the editor before publication. Keypad collection returns digits, valid and reason; code using the unsupported result.collected field must be corrected before publishing.
  • Inline tools retained precedence when loading flows. Realtime transitions avoided an extra response from the outgoing node, and late transcripts no longer restarted the response watchdog.
  • OpenAI and Azure realtime transcripts used the matching speech-start event for timeline placement when available, with receipt time as fallback. Existing recordings and historical call rows were not rewritten.
  • OpenAI model selection added gpt-realtime-2.1, including reasoning-effort and parallel-tool controls. Existing defaults and saved configurations were unchanged. Azure deployment selection was unchanged.

See AI Flow Builder and OpenAI provider settings.

Operations and diagnostics​

The background worker included the runtime dependencies needed for flow-code validation, preventing a startup failure after the update.

Error and recovery alarm records exposed the same searchable alarm.*, event.name and resource identifiers. Errors retained their nested context, and audit records retained their existing searchable fields. Severity labels remained uppercase; use alarm.state for availability. Existing retained logs were not rewritten.

The reconciler retained its 30-second timer, health checks and maintenance protections. Dialog and media counters now use the correct totals; failed probes remain unknown instead of implying a completed drain. This removes unnecessary idle work but does not promise a particular CPU reduction on every installation.

Use flowDefinitionId: <full-id> or tobiConversationId: <full-id> for exact application-ID searches. Named searches avoid unrelated raw-SIP scans. Bare IDs also search those attributes. Select the original call's time range; expired or previously unrecorded data cannot be backfilled. See Trace Debug search.

Trunk probe error labels changed from no reply / status N to no_reply / status_N. Update monitoring queries that match those strings. Internal trunks are excluded from probes and health alarms. The result schema, probe interval and transaction timeout are unchanged. See SIP trunk logs.

Upgrade action

Run the normal TelPro service initialization so the native redis-tools package is installed. The host needs access to its configured package repositories. Install the matching images and configuration bundle, including the web application that serves Trace Debug; updating only the voice service will not deliver the search fix.

See Access Logs for reset requester/target identities and PII redaction for phone and DTMF controls.

Upgrade checklist​

  • Update from patch1 using the standard image/configuration rollout; no new database migration is required.
  • Test existing flow drafts before publishing. Correct invalid sandbox tool code reported by validation; installing the release does not automatically repair or republish saved flow definitions.
  • Check continuing edge heartbeats and the absence of idle cloud-configuration fetches or temporary Redis-client containers.
  • Recreate Web and Ops application containers with the matching configuration so MSISDN_UNMASKED_DIGITS reaches them, and refresh the API/Web/Ops/Voice/TelPro collector configurations.
  • Check successful and timed-out trunk probes, then search a known flow ID and TOBi conversation ID within their retained time range.
  • Keep customer-environment acceptance and load/capacity testing separate from the targeted regression checks.

The recommended SDK remains 0.1.5, supported range >=0.1.3 <0.2.0. The TelAPI OpenAPI and public SDK contracts are unchanged from patch1.