---
sidebar_position: 5
title: Call Logs, Transcriptions & Messaging Logs
description: Audit Call Detail Records (CDRs), queue metrics, SIP hangup codes, AI call transcriptions with RAG citations, and SMS/MMS delivery logs.
---

# Call Logs, Transcriptions & Messaging Logs

Firetell captures end-to-end telemetry across every voice call, queue leg, AI conversation, and SMS/MMS message in your workspace—giving supervisors, QA analysts, and VoIP engineers a single source of truth for SLA reporting and troubleshooting.

---

## Call Logs (CDRs)

Open **Console → Call Center → Call Logs** to search, filter, and inspect **Call Detail Records (CDRs)** across inbound PSTN/SIP trunks, outbound carrier calls, WebRTC client sessions, internal extension-to-extension calls, and Voice AI conversations.

### 1. Anatomy of a Firetell CDR

Each call record tracks the complete lifecycle of the session from initial signaling through media connection to call hangup:

| CDR Field | Values / Format | Description |
| :--- | :--- | :--- |
| **Call ID** | `call_...` | Globally unique identifier used across CDRs, recordings, transcripts, credit ledger entries, and webhooks. |
| **Direction & Type** | `Inbound`, `Outbound`, `Internal` • `Audio`, `Video` | Distinguishes external customer calls from internal agent/extension transfers. |
| **Origin / Channel** | `Client / SIP`, `Agent Portal`, `REST API` | Indicates whether the call originated via PSTN/SIP/SDK client, the Agent Softphone Portal, or a programmable REST API call. |
| **From & To Parties** | Caller & Callee identities | Displays resolved caller/callee names, E.164 numbers or extension digits, and external PSTN trunk numbers. |
| **Status** | `Completed`, `Missed`, `Busy`, `Failed`, `Active` | Final outcome of the call session. |
| **Total vs. Billable Duration** | Seconds | **Total Duration** measures elapsed time including ringing/IVR setup; **Billable Duration** (`billsec`) measures actual connected media time after answer. |
| **Queue Telemetry** | Wait time, Answered flag, Exit outcome | For queued calls, records wait seconds and exit reason: `Answered`, `Abandoned` (caller hung up in queue), `Timeout`, or `Overflow`. |
| **Transfer & Routing Context** | Call Flow, Rung Agents, Transfer Target | Shows which Call Flow handled the call, every agent/extension rung, who answered, and any warm/blind transfer target and reason. |
| **Cost** | USD (`$`) | Exact per-call telecom/usage deduction reconciled in **Settings → Billing → Credit Transactions**. |

### 2. SIP Hangup Codes & Troubleshooting Reference

Click into any CDR's **Event Timeline** to inspect the SIP status code, hangup cause, and disconnecting party (`Caller` vs. `Callee`):

| SIP Code & Hangup Cause | Typical CDR Status | Root Cause | Recommended Fix |
| :--- | :--- | :--- | :--- |
| **`200` — `NORMAL_CLEARING`** | `completed` | Call connected normally and ended cleanly via SIP `BYE`. | Check `hangup_source` (`caller` vs `callee`) if investigating premature disconnects; if calls drop at exactly ~30s, disable **SIP ALG** on your router. |
| **`487` — `ORIGINATOR_CANCEL`** | `missed` | Caller hung up while the phone was still ringing or waiting in queue (`abandoned`). | Shorten IVR greetings or reduce queue ring timeouts so callers reach an agent or Voice AI fallback faster. |
| **`480` — `NO_ANSWER` / `NO_USER_RESPONSE`** | `missed` | Target extension, softphone, or mobile app did not answer within the ring timeout—or SIP device lost NAT registration. | Enable VoIP Push (APNs/FCM) for mobile agents, verify SIP keep-alives (`30s`), and configure a **No-Answer Fallback** in your [Call Flow](/use-guides/call-center/call-flow-builder). |
| **`486` — `USER_BUSY`** | `busy` | Target agent set status to DND/Busy or remote PBX/PSTN line rejected the call as busy. | Route to an [Agent Team](/use-guides/getting-started/extensions-and-teams) with `Round Robin` or overflow to a Voice AI receptionist. |
| **`403` — `CALL_REJECTED` / `FORBIDDEN`** | `failed` | Inbound IP not in Firetell ACL, invalid Outbound Gateway digest credentials, or unverified outbound Caller ID rejected by carrier. | Verify **SIP Trunks → ACLs & Gateways**, outbound Caller ID ownership, and [Firewall & IP Whitelisting](/use-guides/sip-and-devices/sip-trunking-byoc#firewall--ip-whitelisting). |
| **`404` — `UNALLOCATED_NUMBER`** | `failed` | Dialed number is invalid/non-existent or missing E.164 country prefix (`+`). | Always format outbound destinations in full E.164 format (e.g., `+14155550199`, `+12125550123`). |
| **`488` — `INCOMPATIBLE_DESTINATION`** | `failed` | Audio codec or SRTP/RTP encryption mismatch between your PBX/SBC and Firetell. | Enable `PCMU` (`G.711 u-law`), `PCMA` (`G.711 a-law`), and `Opus` on your SIP trunk or endpoint. |
| **`503` — `NORMAL_TEMPORARY_FAILURE`** | `failed` | Downstream customer PBX/gateway unreachable, workspace concurrent call limit reached, or insufficient prepaid credit balance. | Check PBX reachability, [Workspace Limits & Quotas](/use-guides/administration-and-billing/billing-and-quotas#workspace-limits--quotas), and credit balance. |

---

## AI Call Transcriptions

From **Call Logs**, click **Transcriptions** in the top toolbar (or open **Console → Call Center → Call Transcriptions**) to browse post-call speech intelligence across both human agent calls and Voice AI sessions.

### What Every Transcription Captures
- **Speaker-Diarized Dialogue Turns**: Separates **Caller**, **Agent** (human or Voice AI), and **System** events across stereo channels with per-turn confidence scores, durations, and clickable playback timestamps.
- **Executive Summary**: Concise paragraph distilling caller intent, troubleshooting steps, and final resolution—ideal for CRM ticket notes.
- **Caller Sentiment**: Automatic classification into **`Positive`**, **`Neutral`**, or **`Negative`** so QA managers can filter and prioritize negative-sentiment calls immediately.
- **Extracted Action Items & Entities**: Bullet-point follow-up tasks (e.g., *"Send revised invoice to billing@client.com by Friday"*) plus structured named entities (dates, amounts, order numbers).
- **Voice AI Tool & RAG Traceability**: On Voice AI calls, individual dialogue turns display metadata showing which built-in or webhook tool executed and which [Knowledge Base](/use-guides/voice-ai-and-sms/knowledge-bases) source documents and relevance scores grounded the agent's reply.

### Data Privacy & Retention Controls
- Full-text keyword search works across all languages in your workspace (`en`, `vi`, and 30+ languages).
- Workspace Owners and Admins can select individual or multiple transcripts (or [Call Recordings](/use-guides/call-center/call-supervision-and-recordings)) and execute **Bulk Delete** to satisfy GDPR/CCPA erasure requests. Deletions permanently purge the transcript content and write an immutable data-privacy entry to [Workspace Audit Logs](/use-guides/administration-and-billing/security-and-audit-logs#workspace-audit-logs).

---

## Messaging Logs (SMS & MMS)

Navigate to **Console → Call Center → Messaging Logs** to audit every inbound and outbound text or multimedia message across your workspace:

### Delivery Lifecycle & Sender Attribution
- **Sender Attribution**: Pinpoints whether a message was sent by an external **Customer**, a human **Agent**, an autonomous **Voice AI Agent** (via `send_sms`), or an automated **REST API / System** workflow.
- **Delivery Status Progression**:
  - **Outbound**: `queued` → `sending` → `sent` → `delivered` (or `undelivered` / `failed`).
  - **Inbound**: `received`.
- **Media & Error Diagnostics**: Displays attached MMS media previews, per-message carrier cost, and detailed carrier error codes/messages when filtering blocks delivery (for example, unregistered US 10DLC campaigns, invalid landline recipients, or opted-out `STOP` numbers).

For two-way inbox setup and programmable messaging, see **[Two-Way SMS Messaging](/use-guides/voice-ai-and-sms/sms-messaging)** and the **[Messages REST API](/developers/rest-api/workspace-api/messages)**.
