Delphi v0.9.16

Delphi v0.9.16 strengthens authentication and Super Admin controls, adds Microsoft Entra SSO, and gives operators config versioning & backups for platform domains. Voice deployments gain SIP trunk health monitoring, richer flow logging, TOBi sensitive-storage controls, and clearer recording/transcript storage behaviour. Integrators should plan for TelPhi SDK 0.1.4.

Platformv0.9.16·Recommended SDKv0.1.4·Supported SDK range>=0.1.3 <0.2.0

Highlights

• Microsoft Entra SSO — optional Entra sign-in with pre-linked Delphi accounts; authorization stays in Delphi.
• Super Admin management — unified user UI, challenged role changes, session revocation, and Access log coverage.
• Config versioning & backups — per-row history, whole-platform backups, and JSON export/import for Super Admin config domains.
• SIP trunk health monitoring — probe and alarm path for trunk availability.
• API credential jail — temporary block after repeated API key / webhook auth failures.
• TOBi Application Metadata — per-bot VGW attributes in create-conversation channelData, independent of SIP header rules.
• TOBi privacy & DTMF — sensitive storage for transcripts/logs; inter-digit timeout and collection improvements.
• SDK 0.1.4 — text chat, text↔voice handoff, and read-aloud playback lifecycle.
• Deployment-scoped Secrets Manager paths — platform/team secrets use NAMESPACE / PLATFORM_SECRETS_NAMESPACE so shared AWS accounts do not overwrite each other.

Security and Sessions

Deployments can enable Microsoft Entra ID for login while keeping team and platform roles in Delphi. Super Admins manage users from a unified surface; elevating or demoting platform roles requires a short challenge and invalidates affected sessions. Concurrent session limits and password-expiry reminders continue to apply for credential accounts. Failed logins, lockouts, and role changes appear in Access logs; audit rows default to a 180-day retention cleanup. Security events can be exported from SigNoz for SIEM ingestion — see Security event export.

TelWeb and Localization

Team admins can allow or deny Members can publish Apps. VIEWER remains read-only. Members can open Notifications. Side-menu branding was corrected.

Voice, SIP, and WebRTC

SIP trunk health monitoring helps operators detect unavailable trunks. Managed TOBi flows can send predefined Application Metadata (environment, conversation/call IDs, TelPro/Voice IPs, caller/callee) into create-conversation channelData separately from SIP header forwarding — configure under Flow Builder → Managed TOBi and publish the flow. See TOBi managed LLM → Application Metadata. Bots can also suppress transcript/log persistence via sensitive-storage channel data, and can update DTMF collection (including inter-digit timeout) at runtime. Azure TTS supports SSML when enabled. Transfer and hangup callback actions remain documented in Managed callback actions. When Recording is on, STT/TTS segment artefacts and transcript sidecars are stored with the call recording — see Recording and transcript storage.

Flow Builder and Conversations

Conversations Debug supports search by Trace ID and header value. Flow publish permissions follow the team Member publish setting and server-side checks.

API and SDK

TelAPI can jail credentials after repeated auth failures (API_CREDENTIAL_JAIL_* on the API host) — see API keys. Pin TelPhi SDK 0.1.4 for text chat, session handoff, and read-aloud events. SDK 0.1.3 remains usable for clients that do not need those APIs yet.

Observability and Operations

Application and integration flow logging coverage for TelPro and RTPEngine is documented under Application flow logging. Super Admins use Config versioning & backups for recoverable platform config changes. Graceful service refresh continues to support TelPro/config rollouts with drain — see TelPro operations and the restart matrix.

Platform and team AWS Secrets Manager paths are deployment-scoped via PLATFORM_SECRETS_NAMESPACE / NAMESPACE / ENVIRONMENT on TelWeb and TelAPI — see Platform settings and Team default secrets.

Operators

Upgrade action

Run database migrations (voiceai-db-migrate or your standard deploy pipeline) before serving traffic on v0.9.16. Migrations include config versioning, Super Admin auth foundation, Entra account linking, team Member publish permission, and SIP trunk health.

Secrets Manager paths

After upgrade, confirm Admin Settings → Platform Settings → Namespace shows your deployment namespace (not voiceai/local) before writing platform secrets. Teams that still use a shared key such as delphi/teams/.../variables should update the Secrets Manager key so environments sharing one AWS account do not overwrite each other. See the env var index for PLATFORM_SECRETS_NAMESPACE and NAMESPACE.

Microsoft Entra

If enabling SSO, set AUTH_WITH_MICROSOFT and the Entra client/issuer variables, then pre-link each user’s Entra Object ID before they sign in. See Microsoft Entra SSO.

Password expiry mail

Ensure Tasker PASSWORD_EXPIRY_CHECK and notification delivery are healthy, and that NEXTAUTH_URL matches the public TelWeb URL. See Password expiry.

SIP ladder export

SIP ladder text export from Conversations Debug is not part of v0.9.16 (merged then reverted in this window).

Upgrade checklist

1. Run DB migrations, then restart application services in your usual order. Use MIGRATION_DATABASE_URL for the migrate one-shot and runtime DATABASE_URL (optionally DATABASE_SECRET_ARN) for day-2 services — see Database credentials.
2. Confirm Super Admin recovery / Access logs after migrate.
3. Optionally enable Entra SSO and pre-link users.
4. Review team Members can publish Apps settings.
5. Tune API_CREDENTIAL_JAIL_* on TelAPI if needed.
6. Point Super Admins at Admin Settings → Backups / History for config versioning.
7. Upgrade integrator SDKs to 0.1.4 when adopting text chat or handoff.
8. Verify SIP trunk health monitoring and recording/transcript S3 paths in staging before production. For SIPp / lab trunks that must receive media on a private address, do not mark the trunk as external so RTPEngine does not advertise an unreachable public IP.
9. Confirm TelWeb/TelAPI receive NAMESPACE (and optional PLATFORM_SECRETS_NAMESPACE); verify Platform Settings namespace and team secret keys are unique per deployment.

SDK compatibility

Component	Version
Platform	v0.9.16
Recommended TelPhi SDK	0.1.4
Supported SDK range	>=0.1.3 <0.2.0