Call log
The call log under Voice > Calls lists every call your workspace placed and every call that arrived on one of its numbers, newest first. Each entry is a call detail record (CDR), including calls that connected, rang out, or were refused. Use it to inspect duration, the final SIP response, and cost.
Bird writes each record when the call ends, so every call in the log has a final outcome. The Live tab beside it holds the calls that are still up.
The call list
Each row is one call:
| Column | What it shows |
|---|---|
| Status | How the call ended (see Statuses) |
| From | The calling number, the caller ID your equipment presented |
| To | The number that was called |
| Direction | Outbound for the calls your equipment placed, inbound for the calls that arrived on your numbers |
| Duration | Total length of the call, from the moment Bird received it to hangup |
| Started | When Bird received the call |
The list is paginated, 25 calls per page. Select any row to open the call.
Live calls
The Live tab lists the calls up right now, and carries a count so you can see how many are up without opening it. A live call holds one of two statuses:
| Status | What is happening |
|---|---|
| Ringing | The call reached its destination, which has not picked up yet |
| In progress | The destination picked up, and the call is connected |
The columns match the call log except for Elapsed, which replaces Duration. It counts from the answer for a connected call and from the start for a ringing call. The tab refreshes every few seconds. When a call ends, it moves to the call log with its final outcome.
Searching and filtering
The page leads with a number search and its filters. They combine: a status filter plus a date range narrows to the calls matching both.
Search by number. The search box matches a number against either side of the call, so one query finds the calls to it and the calls from it.
Direction. Filter to outbound or inbound calls.
Status. Filter to one of answered, no answer, failed, rejected, or unknown. Each is defined in Statuses. On the Live tab the choices are ringing and in progress.
Date. On the call log, pick a preset (the last 24 hours, 7 days, or 30 days) or choose a custom range on the calendar.
Usage this month
The monthly summary contains three tiles for the current calendar month in UTC:
| Tile | What it counts |
|---|---|
| Calls | Completed call records in the month, including unanswered and refused ones |
| Total duration | Every call's full length added up, from the moment Bird received it to hangup |
| Billable time | Every call's answered time added up |
The difference between total duration and billable time is unanswered ring time. An unanswered call has no billable time.
Each destination rate rounds billable time to its billing increment. See Cost and billing for pricing details.
These tiles cover the whole month whatever you filter the list to.
Statuses
A call in the log ended with one of these outcomes:
| Status | What happened |
|---|---|
| Answered | The destination picked up. Billable time is answer to hangup |
| No answer | The call rang at its destination and was not answered before it timed out |
| Rejected | The call was refused rather than carried through |
| Failed | The call was attempted and did not work, and SIP response is what came back |
| Unknown | The outcome could not be determined, for example when no final response ever arrived |
Rejected covers two refusals, and the rejection reason separates them. Either Bird refused the call before a carrier was involved, in which case the reason names the check it failed, or the far end declined it outright, in which case SIP response carries its answer and there is no reason. An incoming call that the number it dialed turned away is Rejected with no reason too, because it failed no check: its Inbound route says what the number was set to do. See Rejected calls.
Failed is not a refusal. It means the call was attempted and did not work: a busy number is Failed with carrier response 486, and an unallocated one is Failed with 404.
If you read these values from your own tooling, match the ones you handle and treat any other as a status you do not handle rather than an error. The list also carries busy and canceled, reserved for incoming calls delivered to your own numbers. Neither is emitted yet, and both outcomes are reported as failed today.
Inspecting a call
Opening a call shows what Bird recorded about it:
| Field | What it tells you |
|---|---|
| Status | The call's outcome (see Statuses). A call Bird refused also shows the reason and what to do about it |
| SIP response | The call's final SIP code, for example 200 or 486. A call Bird refused carries 503, with no carrier involved |
| From / To | Both numbers, each copyable |
| Inbound route | On an incoming call, what the number it dialed was set to do: deliver to a trunk, forward, or reject. Links to that number |
| Trunk | The SIP trunk the call came in on, or was delivered to, useful when several sites share a workspace |
| Started | When Bird received the call |
| Answered | When the call was picked up, or Not answered |
| Ended | When the call was torn down |
| Call ID | The record's own id (vcl_…). Quote this to support, and use it to correlate with your own logs |
| Session ID | Shared by every leg of one call (vcs_…), so related records can be grouped. A forwarded call has two legs sharing one |
| Billing | Billable time, total duration, and the call's cost once it has been rated |
Inbound route appears on incoming calls only, and it says what the number was set to do rather than that it worked: a trunk route on a rejected call is a number pointed at a trunk that did not take the call. Receiving calls covers the three answers and what each one records.
Rejected calls
A rejected call was refused rather than carried through, and two different things produce that.
Bird refused it before a carrier was involved. Before dialing out, Bird checks the caller ID, destination, account limits, and wallet balance, and refuses a call that fails one of them. Your phone system receives SIP 503, while the authenticated call record stores the specific reason. This prevents unauthenticated callers from learning account details. Open the call to see the cause and a link to the relevant setting.
The number that was dialed turned the call away. An incoming call to a number set to reject, or to a number nobody has pointed anywhere, is rejected with no reason at all: it failed no check of ours. Inbound route is what says so. Receiving calls works through those refusals.
The reasons below are the first kind. They apply to incoming calls as well as outgoing ones, because the account limits and the wallet are checked either way.
Reasons you can fix
| Reason | What happened | What to do |
|---|---|---|
| source_not_allowed | The call arrived from an address the trunk's IP allow list does not cover | Add the address your phone system sends from to the trunk |
| caller_id_not_verified | The number in the From header is not a verified caller ID for this workspace | Verify that number, or present one already verified |
| destination_not_enabled | Calling to that country is switched off for your workspace | Turn the country on under Destinations |
| insufficient_balance | Your wallet did not cover the call, so Bird refused it up front | Top up, or turn on automatic top-ups so a low balance does not interrupt calling |
| daily_spend_exceeded | The call would have passed your organization's daily voice spend ceiling | Wait for the ceiling to reset at the start of the next UTC day, or ask Bird to raise it |
| concurrent_calls_exceeded | You have as many calls in progress as your account allows | Wait for a call to end, or contact support to raise the ceiling |
| calls_per_second_exceeded | You placed new calls faster than your account allows | Slow your dial rate, then retry. Retrying immediately gets the same answer |
| number_ownership_not_verified | You bought this number, but the country that issued it has not accepted the paperwork proving you own it | Complete what the number's ownership field asks for, then place the call again |
A campaign dialer can hit calls_per_second_exceeded while nowhere near the concurrent-call ceiling, so check which of the two you got before changing anything.
Reasons Bird resolves for you
These sit on Bird's side of the setup. Contact support and quote the Call ID from the record:
| Reason | What happened |
|---|---|
| routing_not_configured | Your workspace's routing is still being attached, which is expected while a new voice setup is being completed |
| no_route_found | Routing is attached, but it does not cover the number you dialed. Contact support with the call ID to check the route |
| destination_blocked | Bird's routing configuration blocks calls to that destination |
| call_not_permitted | Bird could not complete the call for your account, so it refused the call rather than place it on unknown terms |
How a refusal reads
Read the status and the rejection reason together:
- Rejected with a rejection reason. Bird refused the call, and the reason identifies the failed check. The SIP response is the 503 your phone system received. Follow the reason's account or routing resolution.
- Rejected with no rejection reason. On an outgoing call, the far end declined it outright and SIP response carries its code. On an incoming call, the number that was dialed turned it away, and Inbound route says what that number was set to do.
- Failed. The call was attempted and did not work, and SIP response contains the code that came back. A 486 means busy, while 404 means the number is unallocated. This usually points at the number rather than at your setup.
A call Bird cannot admit at all is turned away before a record exists, so it never reaches the log. Voice troubleshooting covers those calls.
Getting the records out
Four ways to work with these records outside the dashboard:
- Export CSV. Download CSV on the Call log tab exports every record matching your current filters across all pages. Use it for reconciliation and ad-hoc reporting.
- Read them over the API. GET /v1/voice/calls returns the filtered list, and GET /v1/voice/calls/{call_id} returns one record. Both require an API key with the voice scope at read level. Trunk, caller ID, and destination settings are not part of the public API.
- Read them from the terminal. The Bird CLI provides bird voice list, bird voice get, and bird voice stats. The MCP server exposes the same reads to agents.
- Subscribe to the events. voice_call.initiated, voice_call.answered, and voice_call.ended are pushed to your endpoint as calls happen, so your own systems stay current without polling. See Voice events.
Next steps
| Page | What it covers |
|---|---|
| Voice events | The three call events, their payloads, and how to consume them |
| Placing calls | What Bird expects on the INVITE, and how a call is priced |
| Receiving calls | Pointing a number at a trunk or a forward, and what it records |
| SIP trunks | The IP allow list, allowed API keys, and Digest settings |
| Voice destinations | Enabling countries, and what availability means |
| Errors | The API error envelope and its recovery fields |
Related resources
Continue with the documentation, guides and examples for this topic. Resources are in English.
Understand the conceptWhat is a voice API?Explore the capabilityVoiceImplementation guideVoice overview
Get an implementation brief