Document private provider sources and prepare capture tool on test host

2026-10-04 08:23:39 +08:00
parent 3bf0ac628d
commit 5ab4cbb3be
2 changed files with 8 additions and 2 deletions
@@ -25,9 +25,14 @@ The test host's address and raw logs are omitted from committed evidence.
 - A replay of the already applied revision 12 returned to `(12,0,0)` with an empty control queue and unchanged managed-config and verified-state file modification times; no second native write/reload was needed. RabbitMQ publisher confirms only broker acceptance; the separate Agent/Asterisk readback and Dispatcher checkpoint established this isolated application's handling. Neither the publisher confirm nor the local Mock response proves external SaaS receipt or production readiness. A transient user-service startup delay was treated as unready rather than inventing a loaded revision. With lingering disabled, this test does **not** verify service availability after logout or reboot.
 - Restricted test certificates, environment files, raw logs and snapshots remain outside the repository; committed evidence contains no credential, service IP, caller identity, audio, or transcript. The test made **no call**, registration, media capture, or active-call reload.

+## Capture-tool preflight — 2026-10-04
+
+- On the same pinned Debian 13 test host, `rogee` now passes noninteractive `sudo -n true`. With explicit user authorization, installed Debian `tcpdump` **4.99.5-2** and `libpcap0.8t64` **1.10.5-2**; tcpdump executable SHA-256 `0d426e2571a22de0d30996fd01bb44c1f267f33065023abea092c88bad16d2d2`.
+- `sudo -n tcpdump -D` reported **8 interfaces**. This is only a capability check: **no packet capture or call** was started. Asterisk ARI/HTTP config is still absent on this rebuilt host, the business call executable remains Mock-only, and a real provider/task snapshot has not been signed off. At inspection Asia/Shanghai was **08:15**, before the authorized 09:00 opening; installation of tcpdump alone is not dialing permission.
+
 ## Still required before a real call or production acceptance

 1. Verify the effect of endpoint updates **during an active authorized call** separately; SIP-only does not enable business dialing. Unsupported authentication/REGISTER and transport changes must continue to fail closed, and provider-side authentication, registration, routing and capacity remain unverified.
 2. Obtain carrier-confirmed authentication, transport and registration requirements for each real line, provide approved real line configuration, and arrange each whitelist trial (trunk, original number, time, attempt count). The fixed Asia/Shanghai 09:00–20:00 gate and per-number daily cap remain mandatory.
-3. Establish RabbitMQ/OSS/AI real integrations and nonproduction call-evidence capture. `deploys/test/nonprod-call-evidence.sh` requires root or the required capture capabilities; this host's `rogee` currently has no sudo. If tcpdump, logger, or ARI/PJSIP state is unavailable, do not dial.
+3. Establish the approved task/provider snapshots, real ASR/TTS/recording chain and nonproduction call-evidence capture. One isolated Bailian LLM request and one unique-object OSS PUT succeeded independently ([evidence](real-ai-oss-one-shot-20261003.md)); neither proves a phone call or SaaS application receipt. tcpdump and passwordless sudo are now present, but `deploys/test/nonprod-call-evidence.sh` still targets a system-level Asterisk service rather than this host's `rogee` user service. Update and verify that diagnostic entry, ARI/HTTP config, PJSIP logger, and pre-dial capture before any call; any unavailable step fails closed.
 4. Enable `rogee` user lingering and verify reboot-persistent `enabled+active` before claiming production readiness. Complete the host/network/dependency diagnostics and external signoffs separately; local `make check` cannot replace them.