Standalone service workspace

LinkVeris

Shape what callers hear, where messages land, and what is live right now without digging through backend details or vendor control panels.

Tenant lsdaf-test-tenant

Portal portal.linkveris.dev

Call test Call path staged

Voice

SKYETEL

vpm

Database

do_db_cluster

provider_runtime

Assets

do_spaces

provider_runtime

Web access

dns published edge serving

portal.linkveris.dev

Live bundle

publication-646d7ba2a5baf343

runtime

Tenant context

Current workspace: lsdaf-test-tenant

Start here

Pick the tenant you want to update.
Change the call flow, voicemail, or prompts.
Review web access, then publish when the draft feels right.

Draft changes ready Live now Call path staged

Advanced routing, raw JSON, provider details, and DNS internals stay tucked away until you need them.

Why some items still say pending

Skyetel execution stays in VPM, not in this portal.
DO DB Cluster, DO Spaces, and Cloudflare DNS stay in VPM.
Asterisk only runs generated output.
Anything that touches a real test number still needs a human-approved check.

Current bundle: publication-646d7ba2a5baf343
Bundle target: /var/lib/3in1/linkveris/runtime/pbx/asterisk/bundles/publication-646d7ba2a5baf343
Included in current bundle: Yes

activatedlistedselected

Editable revision: rev-lsdaf-test-stage1-v3
Menus: 4
Voicemail boxes: 2
Last publish: Not recorded yet

Publishing promotes the current working draft, refreshes the live bundle, and immediately opens a fresh next draft for later edits.

No rendered artifacts recorded for the current live revision.

Draft menus: 4
Audio assets: 10
Portal route: dns published edge serving
DNS boundary: ready

Publishing is safe without public DNS, but the public rollout is not complete until the DNS boundary is ready.

Voice path: provider boundary ready
Human approval: Not currently flagged
Portal route: dns published edge serving

The current live voice path is staged through VPM. A human test can happen once the approved test boundary is opened.

External connect stays outside LinkVeris and falls back locally when needed.

The live database path is provider-managed through VPM.

Asset object access stays provider-managed through VPM while LinkVeris keeps metadata and publication intent.

Zone lookup and DNS record changes belong to VPM. The UI only reports readiness and intent.

Advanced publish details

Deploy commit: 98e47fa59df524418b5202f18aec508acbe4a0f9
Deployed at: 2026-03-16T06:50:24Z
Published at: Not recorded