> For the complete documentation index, see [llms.txt](https://doc1.antgst.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://doc1.antgst.com/ant-api/voice/call-code.md).

# Call code

外呼任务、群呼任务呼叫状态码说明。

### 1. 概述

#### 结果分类

按业务将所有结果码分类：

| 分类        | 含义             | 包含的 callCode                                          |
| --------- | -------------- | ----------------------------------------------------- |
| 成功        | 任务提交成功，呼叫已正常发起 | `110`                                                 |
| 提交失败      | 任务提交阶段即失败      | `101`                                                 |
| 状态未知      | 出现未知原因导致呼叫异常   | `104`、`204`                                           |
| 用户侧结果     | 由用户行为或状态导致的结果  | `111`、`122`、`123`、`121`、`135`、`124`、`126`、`226`、`227` |
| 坐席侧结果     | 由坐席行为或状态导致的结果  | `113`、`201`、`212`、`207`、`213`、`225`                   |
| 号码 / 线路结果 | 由号码或线路原因导致的结果  | `164`、`165`、`155`                                     |

### 2. 全量错误码速查表

下表按 `callCode` 数值升序排列，便于接入方快速查阅。

| callCode | 常量名                             | 说明                    |
| -------- | ------------------------------- | --------------------- |
| `101`    | `SUBMIT_FAIL`                   | 呼叫失败（任务提交失败）          |
| `104`    | `TRANSFER_BF_UNKNOWN`           | 用户通话失败                |
| `110`    | `SUBMIT_SUCCESS`                | 提交成功                  |
| `111`    | `USER_NOT_ONLINE`               | 用户不可达（网络、停机、未注册）      |
| `113`    | `SEAT_BUSY`                     | 坐席忙                   |
| `121`    | `FORCE_HANG_UP`                 | 强制挂断                  |
| `122`    | `USER_HUNG_UP`                  | 用户挂断                  |
| `123`    | `HUNG_UP`                       | 主叫挂断                  |
| `124`    | `USER_REJECT`                   | 用户拒接                  |
| `126`    | `USER_BUSY`                     | 用户忙                   |
| `135`    | `USER_NOT_ANSWER`               | 用户未接听                 |
| `155`    | `NETWORK_ERROR`                 | 网络 / 线路异常             |
| `164`    | `NUMBER_NOT_EXIST`              | 空号 / 号码不存在            |
| `165`    | `NUMBER_NOT_ROUTER`             | 号码无法路由（空号 / 停机 / 无线路） |
| `201`    | `SEAT_NOT_LINE`                 | 坐席不在线                 |
| `204`    | `TRANSFER_AF_UNKNOWN`           | 转接通话失败                |
| `207`    | `SEAT_REJECT`                   | 坐席拒接                  |
| `212`    | `SEAT_TEMP_UNAVAILABLE`         | 坐席暂时不可用               |
| `218`    | `SEAT_INCOMPATIBlE_DESTINATION` | 坐席路由不兼容               |
| `213`    | `SEAT_NOT_ANSWER`               | 坐席未接听                 |
| `225`    | `SEAT_HUNG_UP`                  | 坐席挂断                  |
| `226`    | `USER_HUNG_UP_AFTER_TRANSFER`   | 转接后用户挂断               |
| `227`    | `USER_HUNG_UP_BEFORE_TRANSFER`  | 转接前用户挂断               |

***

### 3. 与 `sipCode` 的关系

* `sipCode` 为底层 SIP 协议状态码，反映信令层面的结果（如 `200`、`486`、`480` 等）。
* `callCode` 为业务层面的结果码，由系统综合 SIP 状态与业务流程得出。
* 接入方在做精确归因时，可结合 `sipCode` 与 `callCode` 一起分析；日常统计与展示建议以 `callCode` 为主。

***


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://doc1.antgst.com/ant-api/voice/call-code.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.