14 docs tagged with "observability"

How to prove a bot-initiated BYE or transfer made it end to end from the voice PBX through the SIP edge to the carrier, and which alerts to build on that chain.

What TelSys, TelPro, and RTPEngine log during a call, how log levels are used, and how to correlate application logs with SIP signaling.

What Delphi records as audit and security events — the per-event fields required by BSR 4.1.1/4.1.2 (time, type, origin IP, user ID), the actor-context block, and which platform actions emit which event.

One summary log record per call — timing, bot context, provider identifiers, latency, error/fallback, and correlation IDs — queryable in SigNoz and persisted to AppLog.

Read-only history of background jobs — status, attempts, results, and errors.

How Delphi scrubs PII — DTMF digits, phone numbers, transcripts, and secrets — across three layers: the in-process logger, the DTMF-aware logDTMF helper, and the OTel collector transform processors.

How Delphi services send logs, traces, metrics, health signals, and call debugging data through OTel collectors into SigNoz.

Export Delphi security and audit events from SigNoz into external SIEM or observability systems.

What each Delphi service logs, where the logs land (SigNoz via OTLP and stdout filelog), and the full TelWeb and TelPhi log inventories — server-side structured logs, call/telephony events, CDR, AI/DB spans, audit/auth events, route-handler logs, and client-side console output.

SigNoz observability backend on static private IP 10.0.1.10 — Foundry deploy, version upgrades, legacy migration, alert sync, and troubleshooting.

What Kamailio and TelSys log for SIP — capture points, methods (OPTIONS, CANCEL, PRACK), response codes (481, 487), and how records reach the Debug SIP ladder.

Catalog of SIP trunk health logs emitted by TelPhi and TelAPI — when each fires, what it means, and which payload fields appear.

How super-admins search retained SigNoz telemetry by trace ID, call ID, or SIP header value from the TelWeb Trace Debug view — friendly header mode and raw ClickHouse SQL mode.

How the TOBi transactionId propagates from the managed LLM provider through TelAPI, Redis, Kamailio, TelSys, and OTel spans so every event in a conversation can be correlated under one stable id.