NetBird
voice_stats_by_response_code
Call counts grouped by final SIP response code, the "how are my calls ending" view. Successes are rows too (`200` is one), so the rows sum to the whole period rather than to failures, and each row's `share` is against `period_total_calls`. Calls that got no final response collect under a null code. Capped at `limit` (default 50, max 200). This reports SIP outcomes; a call Bird itself refused carries no SIP code that distinguishes the cause, so read `rejection_reason` on the call record with `voice_get`.
Remote bird/mcp
Remote (network-hosted)
Other tools also called voice_stats_by_response_code?
See providers with this name
Input Schema
{
"type": "object",
"properties": {
"to": {
"type": "string",
"description": "End date (inclusive) in YYYY-MM-DD, interpreted as a calendar day in timezone (a UTC day when timezone is omitted). Defaults to today in that timezone when omitted. Window may not exceed 365 days."
},
"from": {
"type": "string",
"description": "Start date (inclusive) in YYYY-MM-DD, interpreted as a calendar day in timezone (a UTC day when timezone is omitted). Defaults to 30 days before to when omitted."
},
"limit": {
"type": "integer",
"description": "Maximum number of rows to return, ranked by call count descending. The response's total reports how many rows existed before this cap."
},
"timezone": {
"type": "string",
"description": "IANA timezone identifier used to group statistics, for example Asia/Kathmandu. The default is UTC. Day and hour boundaries, including the default window when from and to are omitted, follow this timezone. When this parameter is set, pass from and to as calendar days or Z instants instead of timestamps with explicit UTC offsets."
},
"direction": {
"type": "string",
"examples": [
"inbound",
"outbound"
],
"description": "When set, limits the statistics to call legs in this direction. Omit to include all legs."
}
}
}