Ultima V2 Build Status

Added the controlled WebRTC device layer for extension 122203. An authenticated owner can provision one distinct Telnyx telephony credential, receive a short-lived browser JWT, and register or disconnect the browser without exposing SIP secrets. The device ledger saves only opaque provider IDs and connection state.

Added password sign-in with an email-link fallback, a server-controlled first-owner invitation, invite-only workspace membership, and a Team access panel in Telephony Admin. Invitation links activate each user once so they can create their own password. The Voice configuration, verification, readiness, extension, live-call, history, and detail APIs now require an authenticated active member; the signed Telnyx webhook remains provider-authenticated. Applying the additive owner-access migration and setting the owner environment values is the next operator step.

Read-only Telnyx verification confirmed that active number +1 (877) 818-0814 is assigned to the dedicated Ultima Phone connection. The Admin Numbers view now represents this real pilot rather than a placeholder. The connection remains free of browser device credentials and there are no live calls.

Configured the dedicated Ultima Phone credential connection with the verified Ultima Owner WebRTC Outbound Voice Profile and Ultima’s v2 signed Voice webhook. Read-only verification confirms the App, profile, browser connection, and webhook configuration. No DID was assigned, no device credential was created, and no call was placed.

Stored and read-only verified the enabled Ultima Owner WebRTC Outbound Voice Profile. Signed Voice events can now calculate call duration, match an existing normalized contact when available, and feed safe detail/live-call projections without exposing raw carrier payloads. No number, device, route, or call was activated.

Settings now accepts a dedicated Telnyx credentials-based SIP Connection ID for the future browser softphone, separately from the Voice App and existing 3CX connections. The ID is validated server-side before Ultima can create per-agent credentials. No SIP connection, device, route, or call was created by this change.

Read-only checks confirmed that the live Supabase API does not yet expose the canonical calls table and that the existing project uses an older user_id shape. Replaced the incompatible canonical-schema instruction with an additive, voice-only compatibility migration. This database work does not affect the Telnyx number, 3CX, devices, or calls.

Added non-mutating pilot readiness, tenant-scoped voice call-history, and owner-extension endpoints. The Telephony Control Center now shows whether the encrypted Telnyx configuration and database ledger are ready; the Dial Pad replaces its reference history only when real Telnyx projections exist. Extension 122203 can be recorded after the migration, but it cannot register a device or place a call.

The configured Telnyx Voice App passed Ultima’s read-only connection check. The pilot API and public signing keys are stored encrypted server-side and remain write-only in the Settings UI. No customer number was moved, no webhook event was accepted, and no call was placed.

Added a Telnyx Voice setup card to Settings for the pilot App ID, webhook URL, API key, and public signing key. The saved keys are encrypted in the server-side local store and are write-only from the UI. The card includes a no-call configuration check; real traffic remains disabled until the database migration and live policy are applied.

Added the unapplied Supabase migration and provider-neutral voice contracts. The model extends the existing call ledger with Telnyx session/leg/control identifiers, duplicate-event protection, idempotent command records, extensions, device metadata, number capabilities, and recording metadata. No carrier credential, public voice webhook, or real call API was enabled.

Added the agent-facing Dial Pad workspace with a keyboard, visual call states, mute/hold controls, warm transfer, conference, recent-call design, and Customer 360 context. It deliberately runs in design mode: no carrier call, voice route, or call-event data model has been activated yet.

Telephony is the next product build priority. The first implemented surface is the Owner/Admin Telephony Control Center for number inventory, extensions, routing, IVR, queues, recording policy, and team access. The Telnyx Voice + WebRTC backend remains planned next, preserving a provider boundary for a later Asterisk/ARI option.

Created this repository-aligned status board. It separates the current Next.js/Supabase/Telnyx/Zoho application from the prior dialer-core roadmap and documents the security baseline required before deployment.

Verified working product surfaces for SMS, contacts, tickets, settings, uploads, and provider integrations. Identified tenant-ID trust, secret exposure, unsigned webhooks, and unrestricted uploads as deployment-blocking gaps.

The previous board reports a port to a Next.js App Router repository. The current implementation contains a smaller, separate product surface and does not include the older tRPC/Asterisk/repository-layer code described by that board.