# Outbound Call Logs

Outbound call logs provide detailed records of outbound call activity. These logs are essential for monitoring,
analysis, and troubleshooting.

---

## Call Log Filters

Various filters are available to help you locate the exact call logs.

| **Filter Name** | **Description** |
| --- | --- |
| **Date / Time Start (UTC)** | Filter logs for specific time ranges: `Today`, `This week`, `This month`, `Previous month`, or `Custom Range`. |
| **Source** | Filter logs by specific source numbers using `Equals` or `Contains`. |
| **CLI** | Filter logs by specific Caller IDs using `Equals` or `Contains`. |
| **Destination Number** | Filter logs by specific destination numbers using `Equals` or `Contains`. |
| **Voice OUT Trunk** | Filter logs based on specific Voice OUT Trunks. |
| **Status** | Filter logs by call status: `Any Status`, `Success`, `Capacity Exceeded`, or `Failed`. |
| **Source Countries** | Filter logs by specific source countries. Multiple selections are allowed. |
| **Destination Countries** | Filter logs by specific destination countries. Multiple selections are allowed. |
| **Call Type** | Filter logs by call type: `International`, `Origin Based`, `Local`, or `Emergency`. |
| **P-Charge-Info** | Filter logs by the p-charge-info header using `Equals` or `Contains`. [Learn more about the P-Charge-Info header](../../voice/outbound-trunks/outbound-sip-information.html#service-termination-sip-details-p-charge-info). |
| **Call ID** | Filter logs by the system-generated Call ID using `Equals` or `Contains`. |

Tip

You can filter multiple values in call log filters, such as source numbers,
destination numbers, or other fields, by entering the values separated by commas
(`,`) or spaces. For example, enter `123,456` or `123 456` to filter
multiple entries in a single field.

[![Outbound Call Log Filters.](../../_images/fig112.png)](../../_images/fig112.png)


**Fig. 1.** Outbound Call Log Filters.

---

## Call Log Fields

The following fields are included in the outbound call logs:

| **Field Name** | **Description** |
| --- | --- |
| **Date / Time Start (UTC)** | The time when DIDWW received the call. |
| **Date / Time Connect (UTC)** | The time when the call was connected. |
| **Date / Time End (UTC)** | The time when the call ended. |
| **Status** | Indicates whether the call was successful or failed. |
| **Source** | The originating number from which the call was made. |
| **CLI** | The Caller ID from which the call originated. |
| **Destination Number** | The number to which the call was routed. |
| **Call / Billing Duration (sec)** | The call duration in seconds and the billed duration in seconds. |
| **Response** | The SIP response code for the call. |
| **Voice OUT Trunk** | The trunk through which the call was routed. |
| **Destination Country** | The country of the destination number. |
| **Network** | The network of the destination number. |
| **Call Type** | The type of call, determined by the destination country. |
| **Rate (USD)** | The rate charged for the call in USD. |
| **Charged (USD)** | The total charge for the call in USD. |
| **P-Charge-Info** | The value sent in the P-Charge-Info header. [Learn more about the P-Charge-Info header](../../voice/outbound-trunks/outbound-sip-information.html#service-termination-sip-details-p-charge-info). |
| **Call ID** | The system-generated identifier for the call. |

Billing Information

Call charges are calculated based on the total call duration, including milliseconds.
Any fraction of time that exceeds a full billing interval is automatically rounded up to the next interval.
This means that even a few milliseconds beyond a complete interval are counted as a full additional interval for billing
purposes.

For example, when the billing increment is `60/60`:

- If a call lasts `60.000` seconds, it is billed as `60` seconds (one interval).
- If a call lasts `60.001` seconds (where `0.001` represents milliseconds), it is billed as `120` seconds (two intervals).

[![Outbound Call Logs.](../../_images/fig216.png)](../../_images/fig216.png)


**Fig. 2.** Outbound Call Logs.

On this page