Live line acceptance check#

Prove that a real inbound call and a real inbound SMS complete end to end on a deployed demarc runtime, and record a redacted evidence file. The runner reads runtime state over read-only GET requests: it places no call, sends no message, and changes no number, carrier or runtime setting.

Before you start#

• A deployed runtime reporting production and a healthy /api/ready.
• The runtime API token, held in a protected file or secret manager.
• A checkout of the exact revision that is deployed.
• A demarc DID in E.164 form, using ai or fallback routing, with SMS auto-reply enabled and messaging compliance approved for its number type.
• A separate phone you can call and text from, also in E.164 form.
• About ten uninterrupted minutes in a quiet place.

The check exercises the receptionist and SMS auto-reply path. Incoming browser calls are not part of it.

Run the check#

1. Put the runtime API token in the process environment. Read it from a protected file rather than typing it into the command line, where it would enter shell history:

   Copy

   $env:DEMARC_AUTH_TOKEN = (Get-Content -Raw .\runtime-token.txt).Trim()

2. Start the runner against the deployed origin:

   Copy

   uv run python scripts/live_acceptance.py `
     --base-url https://runtime.example.com `
     --did '+1XXXXXXXXXX' `
     --caller '+1YYYYYYYYYY'

   The origin must be absolute HTTPS. The runner rejects a loopback address and any URL carrying credentials, a query or a fragment.

3. Wait for preflight to pass. The runner stops before any live action if the runtime is not in production, if database, schema, authentication, Telnyx signature or live voice readiness is incomplete, if operations status reports stale active calls, if the DID is absent from the number list, if the DID is not using ai or fallback routing, if SMS auto-reply is off, or if the number's messaging compliance status is not approved.

4. When preflight passes, the runner prints a one-time SMS marker and polls for the observation window. While it runs, perform only these live actions:

   1. Call the DID from the caller phone.
   2. Say the displayed acceptance phrase, hear a meaningful spoken reply, and hang up normally.
   3. Send the exact displayed marker by SMS to the DID.

5. Answer the two prompts with YES only if the call had intelligible two-way audio and the reply arrived on the caller phone. Any other answer records an incomplete result.

Clear DEMARC_AUTH_TOKEN from the shell when the run finishes.

Options#

Verify#

A passing run exits 0, prints ACCEPTANCE PASSED with an acceptance ID, and writes the redacted JSON evidence file. Open the file and confirm it records the preflight state, the correlated call and message identifiers, the transcript turn count and both operator attestations.

The evidence file stores per-run hashes instead of phone numbers, and it records no transcript text, no API token and no auto-reply body.

The runner accepts only records created after the run begins, matched on the exact caller, the exact DID and the printed marker, and it requires a completed call carrying both a caller turn and an assistant turn.

Warning An outbound message state of sent means the carrier accepted the request. It is not a delivery receipt, which is why the handset confirmation is required.

If it does not work#

A preflight failure is a configuration result, not acceptance evidence. Never treat a local smoke run or an incomplete artefact as a substitute for a passing live check.