Self-Serve TelephonyQA Test Plan

The first create succeeds: toast "Provider created", row appears with Active status and 0 connections. The duplicate is rejected with an inline error on the name field saying the name is already in use, and no duplicate row appears. The Rename button is disabled while the name is empty or unchanged; after renaming, toast "Provider renamed" and the table updates.

Toasts "<name> deprecated." then "<name> reactivated."; the status badge flips Deprecated/Active and the kebab shows only the applicable action each time. While deprecated, the provider does NOT appear in the wizard's catalog select (active carriers only).

Table shows Name, Type (Carrier / Client endpoint badge), Status badge, Connections count, Actions kebab; empty state "No providers yet" if none exist. A non-zero count is a link that opens the connections list already filtered to that provider; zero counts are plain numbers.

Header shows "Manage providers" and "New connection" buttons (the latter only while the wizard is enabled). Columns: Organization, Provider, Path badge, Transport, Status badge, Numbers, Created, View. Active is green, pending verification is warning, disabled is gray. A deprecated provider shows a muted "Deprecated provider" sub-label in its cell.

The page URL updates as filters change (so a filtered view can be bookmarked) and rows filter correctly; a combination with no matches shows "No matching connections" with the clear-filters hint. Both the row click and the View button open the connection detail page.

Progress shows "Step N of 6". Collision step auto-runs and reports "No collisions found". IP-auth credentials step shows the "IP authentication" info with the platform addresses to whitelist (no username/password fields). Summary matches inputs. Provisioning then verifying phases appear, then per-check icons, then "Connection is active" with a "Go to connections" link. The new connection appears in the list as active with number count 1.

Both are blocked with field errors: a provider must be selected in catalog mode (if no active carriers exist, the muted "No active carriers in the catalog yet..." hint shows instead of the select); endpoint name is required in custom mode; at least one signaling address is required for IP auth.

Both cases show the warning "These addresses are already in use" and block Next: carrier copy says to edit that connection instead of creating another; client-endpoint copy says the address can only belong to one connection. The client-endpoint case is new in this release (it previously reported no collision, wrongly). Re-entering step 3 with a changed address re-runs the check and clears the warning.

Password under 12 chars is rejected. Taken username shows "This username is already in use. Choose another." on Next. With a fresh username the wizard proceeds. The helper notes the password is never retrievable after this step.

The numbers multi-select offers only unassigned and Org A numbers (the Org B number is absent), and the step is optional. Re-entering step 3 re-runs the collision check against the new address (no stale result). Back is disabled on step 1 and while provisioning/verifying. No duplicate connection is created by back-and-forth.

Failure state "Not verified yet" (or the timeout message "Verification timed out. The connection stays pending until every check passes."). The connection exists in the list as pending verification. Retry re-verifies the SAME connection: no duplicate row appears.

Title "{org} via {provider}" with status badge. Connection card shows organization, provider (with type badge), transport, created/updated. The Routing card matches the Path badge: "Platform SIP" connections show "Outbound setid" and "Inbound identity"; "LiveKit direct" connections show "Inbound trunk" and "Outbound trunk" (or "No inbound"/"No outbound" when not set). The made-up id shows a 404 page without errors.

The dialog offers only numbers with no connection AND (unowned OR owned by Org A); numbers linked elsewhere or dedicated to Org B are absent ("No provisioned numbers are available to link." when none qualify). Linking: toast "Number linked", the number appears in the Linked numbers table, the list page's Numbers count increments. Tab 2 shows the friendly inline error "This number cannot be linked to this connection. It may be dedicated to another organization or already linked elsewhere.", with no double link. Unlinking: the dialog warns the number stops routing until linked again; toast "{number} unlinked."; the row leaves the table.

Dialog warns calls stop routing immediately, linked numbers stay attached but become unroutable, and re-enabling requires verification. After confirming: status flips to Disabled, the Disable button disappears, linked numbers remain listed. If an error message appears instead of the status changing, capture it and report.

Unlinked numbers show a muted "Not linked". Linked numbers show a link labeled "{org} via {provider}" that opens the connection detail page; numbers linked to a pending-verification connection additionally show a "Pending" badge.

The picker offers "No connection" plus non-disabled connections (pending ones carry a "Pending verification" badge). Success toasts: "{number} registered and linked." with the row showing the connection link, or "{number} registered" with "Not linked". With an owner org set, only that org's connections are offered, and changing ownership kind or owner org resets a previously picked connection. In the staged-conflict case the number IS registered and a message explains the link failed and to link it from the numbers list; mark that step N/A if it cannot be staged.

The kebab shows "Link to connection" only when unlinked and "Unlink from connection" only when linked (never both). The link dialog filters candidates like DET-2 and shows "No eligible connections..." when none. Toasts "{number} linked" / "{number} unlinked.". The other actions behave as before and the Connection column stays correct afterwards.

The call connects, and the engineer confirms it went through the connection's route, not the number's built-in route.

In all four cases the call connects using the number's built-in route (engineer confirms each), and the link causes no errors. Unlinking and disabling take effect immediately, with no restart or waiting period.

Inbound behavior is unchanged for both (this release changes outbound routing; inbound must not regress). The shared-pool call completes and routes by the same rules as above (engineer confirms); a pool mixing linked and unlinked numbers causes no failures.

Every page redirects to the home page (or shows "not found" for the wizard); no telephony data is visible. The direct API request is rejected as unauthorized with no telephony data. With the wizard off, the page shows "not found" and the "New connection" button is absent. Mark the optional steps N/A in the notes if they cannot be arranged.

All three register as before; the ownership-specific fields (outbound access options and the organization pickers) look and behave as they did before this release.

The tabs are unaffected by this release: they load and paginate normally. The ordinary call works exactly as before the deploy.