Back to Details

telnyx-voice-ruby

Compare original and translation side by side

🇺🇸

Original

English
🇨🇳

Translation

Chinese
<!-- Auto-generated from Telnyx OpenAPI specs. Do not edit. -->
<!-- Auto-generated from Telnyx OpenAPI specs. Do not edit. -->

Telnyx Voice - Ruby

Telnyx 语音服务 - Ruby 版本

Installation

安装

bash
gem install telnyx
bash
gem install telnyx

Setup

配置

ruby
require "telnyx"

client = Telnyx::Client.new(
  api_key: ENV["TELNYX_API_KEY"], # This is the default and can be omitted
)
All examples below assume 
client
is already initialized as shown above.
ruby
require "telnyx"

client = Telnyx::Client.new(
  api_key: ENV["TELNYX_API_KEY"], # 这是默认配置，可以省略
)
以下所有示例都假设
client
已经按照上述方式完成初始化。

Error Handling

错误处理

All API calls can fail with network errors, rate limits (429), validation errors (422), or authentication errors (401). Always handle errors in production code:
ruby
response = client.calls.dial(
  connection_id: "7267xxxxxxxxxxxxxx",
  from: "+18005550101",
  to: "+18005550100"
)
puts(response)
Common error codes: 
401
invalid API key, 
403
insufficient permissions, 
404
resource not found, 
422
validation error (check field formats), 
429
rate limited (retry with exponential backoff).
所有API调用都可能失败，原因包括网络错误、速率限制(429)、校验错误(422)或认证错误(401)。生产环境代码中请务必处理错误：
ruby
response = client.calls.dial(
  connection_id: "7267xxxxxxxxxxxxxx",
  from: "+18005550101",
  to: "+18005550100"
)
puts(response)
常见错误码：
401
API密钥无效，
403
权限不足，
404
资源未找到，
422
校验错误（请检查字段格式），
429
触发速率限制（请使用指数退避策略重试）。

Important Notes

重要说明

  • Phone numbers must be in E.164 format (e.g., 
    +13125550001
    ). Include the 
    +
    prefix and country code. No spaces, dashes, or parentheses.
  • Pagination: Use 
    .auto_paging_each
    for automatic iteration: 
    page.auto_paging_each { |item| puts item.id }
    .
  • 电话号码必须采用E.164格式（例如
    +13125550001
    ），需要包含
    +
    前缀和国家代码，不能包含空格、横杠或括号。
  • 分页： 使用
    .auto_paging_each
    实现自动遍历：
    page.auto_paging_each { |item| puts item.id }
    。

Operational Caveats

操作注意事项

  • Call Control is event-driven. After 
    dial()
    or an inbound webhook, issue follow-up commands from webhook handlers using the 
    call_control_id
    in the event payload.
  • Outbound and inbound flows are different: outbound calls start with 
    dial()
    , while inbound calls must be answered from the incoming webhook before other commands run.
  • A publicly reachable webhook endpoint is required for real call control. Without it, calls may connect but your application cannot drive the live call state.
  • 呼叫控制是事件驱动的。调用
    dial()
    或接收入站webhook后，需要在webhook处理器中使用事件payload中的
    call_control_id
    来执行后续指令。
  • 外呼和入站流程不同：外呼从
    dial()
    开始，而入呼必须先在接收的webhook中应答，才能执行其他指令。
  • 要实现完整的呼叫控制，需要一个公网可访问的webhook端点。如果没有该端点，通话可能可以接通，但你的应用无法控制实时通话状态。

Reference Use Rules

参考使用规则

Do not invent Telnyx parameters, enums, response fields, or webhook fields.
  • If the parameter, enum, or response field you need is not shown inline in this skill, read references/api-details.md before writing code.
  • Before using any operation in 
    ## Additional Operations
    , read the optional-parameters section and the response-schemas section.
  • Before reading or matching webhook fields beyond the inline examples, read the webhook payload reference.
请勿自行编造Telnyx参数、枚举值、响应字段或webhook字段。
  • 如果你需要的参数、枚举值或响应字段没有在本教程中列出，请在编写代码前阅读references/api-details.md。
  • 在使用
    ## 其他操作
    中的任何接口前，请先阅读可选参数章节和响应结构章节。
  • 如果你需要读取或匹配的webhook字段超出了内置示例的范围，请先阅读webhook payload参考。

Core Tasks

核心任务

Dial an outbound call

拨打外呼电话

Primary voice entrypoint. Agents need the async call-control identifiers returned here.
client.calls.dial()
— 
POST /calls
ParameterTypeRequiredDescription
to
string (E.164)YesThe DID or SIP URI to dial out to.
from
string (E.164)YesThe 
from
number to be used as the caller id presented to t...
connection_id
string (UUID)YesThe ID of the Call Control App (formerly ID of the connectio...
timeout_secs
integerNoThe number of seconds that Telnyx will wait for the call to ...
billing_group_id
string (UUID)NoUse this field to set the Billing Group ID for the call.
client_state
stringNoUse this field to add state to every subsequent webhook.
...+48 optional params in references/api-details.md
ruby
response = client.calls.dial(
  connection_id: "7267xxxxxxxxxxxxxx",
  from: "+18005550101",
  to: "+18005550100"
)

puts(response)
Primary response fields:
  • response.data.call_control_id
  • response.data.call_leg_id
  • response.data.call_session_id
  • response.data.is_alive
  • response.data.recording_id
  • response.data.call_duration
主要的语音入口。调用方需要这里返回的异步呼叫控制标识符。
client.calls.dial()
— 
POST /calls
参数类型必填描述
to
string (E.164)是要拨打的DID或SIP URI
from
string (E.164)是展示给被叫方的主叫ID号码
connection_id
string (UUID)是呼叫控制应用的ID（之前也叫连接ID）
timeout_secs
integer否Telnyx等待呼叫接通的秒数
billing_group_id
string (UUID)否用于指定该通话所属的账单组ID
client_state
string否用于给后续所有webhook添加自定义状态
...还有48个可选参数，请查看references/api-details.md
ruby
response = client.calls.dial(
  connection_id: "7267xxxxxxxxxxxxxx",
  from: "+18005550101",
  to: "+18005550100"
)

puts(response)
主要响应字段：
  • response.data.call_control_id
  • response.data.call_leg_id
  • response.data.call_session_id
  • response.data.is_alive
  • response.data.recording_id
  • response.data.call_duration

Answer an inbound call

接听来电

Primary inbound call-control command.
client.calls.actions.answer()
— 
POST /calls/{call_control_id}/actions/answer
ParameterTypeRequiredDescription
call_control_id
string (UUID)YesUnique identifier and token for controlling the call
billing_group_id
string (UUID)NoUse this field to set the Billing Group ID for the call.
client_state
stringNoUse this field to add state to every subsequent webhook.
webhook_url
string (URL)NoUse this field to override the URL for which Telnyx will sen...
...+26 optional params in references/api-details.md
ruby
response = client.calls.actions.answer("v3:550e8400-e29b-41d4-a716-446655440000_gRU1OGRkYQ")

puts(response)
Primary response fields:
  • response.data.result
  • response.data.recording_id
主要的入站呼叫控制指令。
client.calls.actions.answer()
— 
POST /calls/{call_control_id}/actions/answer
参数类型必填描述
call_control_id
string (UUID)是用于控制通话的唯一标识符和令牌
billing_group_id
string (UUID)否用于指定该通话所属的账单组ID
client_state
string否用于给后续所有webhook添加自定义状态
webhook_url
string (URL)否用于覆盖Telnyx发送事件的默认URL
...还有26个可选参数，请查看references/api-details.md
ruby
response = client.calls.actions.answer("v3:550e8400-e29b-41d4-a716-446655440000_gRU1OGRkYQ")

puts(response)
主要响应字段：
  • response.data.result
  • response.data.recording_id

Transfer a live call

转接正在进行的通话

Common post-answer control path with downstream webhook implications.
client.calls.actions.transfer()
— 
POST /calls/{call_control_id}/actions/transfer
ParameterTypeRequiredDescription
to
string (E.164)YesThe DID or SIP URI to dial out to.
call_control_id
string (UUID)YesUnique identifier and token for controlling the call
timeout_secs
integerNoThe number of seconds that Telnyx will wait for the call to ...
client_state
stringNoUse this field to add state to every subsequent webhook.
webhook_url
string (URL)NoUse this field to override the URL for which Telnyx will sen...
...+33 optional params in references/api-details.md
ruby
response = client.calls.actions.transfer("call_control_id", to: "+18005550100")

puts(response)
Primary response fields:
  • response.data.result
常见的通话应答后控制流程，会触发后续webhook事件。
client.calls.actions.transfer()
— 
POST /calls/{call_control_id}/actions/transfer
参数类型必填描述
to
string (E.164)是要转接的目标DID或SIP URI
call_control_id
string (UUID)是用于控制通话的唯一标识符和令牌
timeout_secs
integer否Telnyx等待转接接通的秒数
client_state
string否用于给后续所有webhook添加自定义状态
webhook_url
string (URL)否用于覆盖Telnyx发送事件的默认URL
...还有33个可选参数，请查看references/api-details.md
ruby
response = client.calls.actions.transfer("call_control_id", to: "+18005550100")

puts(response)
主要响应字段：
  • response.data.result

Webhook Verification

Webhook 验证

Telnyx signs webhooks with Ed25519. Each request includes 
telnyx-signature-ed25519
and 
telnyx-timestamp
headers. Always verify signatures in production:
ruby
undefined
Telnyx使用Ed25519对webhook进行签名。每个请求都包含
telnyx-signature-ed25519
和
telnyx-timestamp
请求头。生产环境请务必验证签名：
ruby
undefined

In your webhook handler (e.g., Sinatra — use raw body):

在你的webhook处理器中（例如Sinatra — 请使用原始请求体）:

post "/webhooks" do payload = request.body.read headers = { "telnyx-signature-ed25519" => request.env["HTTP_TELNYX_SIGNATURE_ED25519"], "telnyx-timestamp" => request.env["HTTP_TELNYX_TIMESTAMP"], } begin event = client.webhooks.unwrap(payload, headers) rescue => e halt 400, "Invalid signature: #{e.message}" end

Signature valid — event is the parsed webhook payload

puts "Received event: #{event.data.event_type}" status 200 end
undefined
post "/webhooks" do payload = request.body.read headers = { "telnyx-signature-ed25519" => request.env["HTTP_TELNYX_SIGNATURE_ED25519"], "telnyx-timestamp" => request.env["HTTP_TELNYX_TIMESTAMP"], } begin event = client.webhooks.unwrap(payload, headers) rescue => e halt 400, "Invalid signature: #{e.message}" end

签名验证通过 — event是解析后的webhook payload

puts "Received event: #{event.data.event_type}" status 200 end
undefined

Webhooks

Webhooks

These webhook payload fields are inline because they are part of the primary integration path.
以下webhook payload字段是核心集成路径的一部分，所以直接内置展示。

Call Answered

通话已接听

FieldTypeDescription
data.record_type
enum: eventIdentifies the type of the resource.
data.event_type
enum: call.answeredThe type of event being delivered.
data.id
uuidIdentifies the type of resource.
data.occurred_at
date-timeISO 8601 datetime of when the event occurred.
data.payload.call_control_id
stringCall ID used to issue commands via Call Control API.
data.payload.connection_id
stringCall Control App ID (formerly Telnyx connection ID) used in the call.
data.payload.call_leg_id
stringID that is unique to the call and can be used to correlate webhook events.
data.payload.call_session_id
stringID that is unique to the call session and can be used to correlate webhook ev...
字段类型描述
data.record_type
enum: event标识资源类型
data.event_type
enum: call.answered触发的事件类型
data.id
uuid资源ID
data.occurred_at
date-time事件发生的ISO 8601格式时间
data.payload.call_control_id
string用于通过呼叫控制API发送指令的通话ID
data.payload.connection_id
string通话使用的呼叫控制应用ID（之前叫Telnyx连接ID）
data.payload.call_leg_id
string通话的唯一ID，可用于关联webhook事件
data.payload.call_session_id
string通话会话的唯一ID，可用于关联webhook事件

Call Hangup

通话已挂断

FieldTypeDescription
data.record_type
enum: eventIdentifies the type of the resource.
data.event_type
enum: call.hangupThe type of event being delivered.
data.id
uuidIdentifies the type of resource.
data.occurred_at
date-timeISO 8601 datetime of when the event occurred.
data.payload.call_control_id
stringCall ID used to issue commands via Call Control API.
data.payload.connection_id
stringCall Control App ID (formerly Telnyx connection ID) used in the call.
data.payload.call_leg_id
stringID that is unique to the call and can be used to correlate webhook events.
data.payload.call_session_id
stringID that is unique to the call session and can be used to correlate webhook ev...
字段类型描述
data.record_type
enum: event标识资源类型
data.event_type
enum: call.hangup触发的事件类型
data.id
uuid资源ID
data.occurred_at
date-time事件发生的ISO 8601格式时间
data.payload.call_control_id
string用于通过呼叫控制API发送指令的通话ID
data.payload.connection_id
string通话使用的呼叫控制应用ID（之前叫Telnyx连接ID）
data.payload.call_leg_id
string通话的唯一ID，可用于关联webhook事件
data.payload.call_session_id
string通话会话的唯一ID，可用于关联webhook事件

Call Initiated

通话已发起

FieldTypeDescription
data.record_type
enum: eventIdentifies the type of the resource.
data.event_type
enum: call.initiatedThe type of event being delivered.
data.id
uuidIdentifies the type of resource.
data.occurred_at
date-timeISO 8601 datetime of when the event occurred.
data.payload.call_control_id
stringCall ID used to issue commands via Call Control API.
data.payload.connection_id
stringCall Control App ID (formerly Telnyx connection ID) used in the call.
data.payload.connection_codecs
stringThe list of comma-separated codecs enabled for the connection.
data.payload.offered_codecs
stringThe list of comma-separated codecs offered by caller.
If you need webhook fields that are not listed inline here, read the webhook payload reference before writing the handler.
字段类型描述
data.record_type
enum: event标识资源类型
data.event_type
enum: call.initiated触发的事件类型
data.id
uuid资源ID
data.occurred_at
date-time事件发生的ISO 8601格式时间
data.payload.call_control_id
string用于通过呼叫控制API发送指令的通话ID
data.payload.connection_id
string通话使用的呼叫控制应用ID（之前叫Telnyx连接ID）
data.payload.connection_codecs
string连接启用的编解码器列表，用逗号分隔
data.payload.offered_codecs
string主叫方提供的编解码器列表，用逗号分隔
如果你需要的webhook字段没有在这里列出，请在编写处理器前阅读webhook payload参考。

Important Supporting Operations

重要支持操作

Use these when the core tasks above are close to your flow, but you need a common variation or follow-up step.
当上述核心任务和你的流程接近，但需要常见的变体或后续步骤时，可以使用这些操作。

Hangup call

挂断通话

End a live call from your webhook-driven control flow.
client.calls.actions.hangup()
— 
POST /calls/{call_control_id}/actions/hangup
ParameterTypeRequiredDescription
call_control_id
string (UUID)YesUnique identifier and token for controlling the call
client_state
stringNoUse this field to add state to every subsequent webhook.
command_id
string (UUID)NoUse this field to avoid duplicate commands.
custom_headers
array[object]NoCustom headers to be added to the SIP BYE message.
ruby
response = client.calls.actions.hangup("v3:550e8400-e29b-41d4-a716-446655440000_gRU1OGRkYQ")

puts(response)
Primary response fields:
  • response.data.result
从webhook驱动的控制流程中结束正在进行的通话。
client.calls.actions.hangup()
— 
POST /calls/{call_control_id}/actions/hangup
参数类型必填描述
call_control_id
string (UUID)是用于控制通话的唯一标识符和令牌
client_state
string否用于给后续所有webhook添加自定义状态
command_id
string (UUID)否用于避免重复执行指令
custom_headers
array[object]否添加到SIP BYE消息中的自定义请求头
ruby
response = client.calls.actions.hangup("v3:550e8400-e29b-41d4-a716-446655440000_gRU1OGRkYQ")

puts(response)
主要响应字段：
  • response.data.result

Bridge calls

桥接通话

Trigger a follow-up action in an existing workflow rather than creating a new top-level resource.
client.calls.actions.bridge()
— 
POST /calls/{call_control_id}/actions/bridge
ParameterTypeRequiredDescription
call_control_id
string (UUID)YesThe Call Control ID of the call you want to bridge with, can...
call_control_id
string (UUID)YesUnique identifier and token for controlling the call
client_state
stringNoUse this field to add state to every subsequent webhook.
command_id
string (UUID)NoUse this field to avoid duplicate commands.
video_room_id
string (UUID)NoThe ID of the video room you want to bridge with, can't be u...
...+16 optional params in references/api-details.md
ruby
response = client.calls.actions.bridge(
  "call_control_id",
  call_control_id_to_bridge_with: "v3:MdI91X4lWFEs7IgbBEOT9M4AigoY08M0WWZFISt1Yw2axZ_IiE4pqg"
)

puts(response)
Primary response fields:
  • response.data.result
在现有工作流中触发后续操作，而无需创建新的顶层资源。
client.calls.actions.bridge()
— 
POST /calls/{call_control_id}/actions/bridge
参数类型必填描述
call_control_id
string (UUID)是要桥接的目标通话的呼叫控制ID
call_control_id
string (UUID)是用于控制当前通话的唯一标识符和令牌
client_state
string否用于给后续所有webhook添加自定义状态
command_id
string (UUID)否用于避免重复执行指令
video_room_id
string (UUID)否要桥接的视频房间ID，不能和其他桥接目标同时使用
...还有16个可选参数，请查看references/api-details.md
ruby
response = client.calls.actions.bridge(
  "call_control_id",
  call_control_id_to_bridge_with: "v3:MdI91X4lWFEs7IgbBEOT9M4AigoY08M0WWZFISt1Yw2axZ_IiE4pqg"
)

puts(response)
主要响应字段：
  • response.data.result

Reject a call

拒接通话

Trigger a follow-up action in an existing workflow rather than creating a new top-level resource.
client.calls.actions.reject()
— 
POST /calls/{call_control_id}/actions/reject
ParameterTypeRequiredDescription
cause
enum (CALL_REJECTED, USER_BUSY)YesCause for call rejection.
call_control_id
string (UUID)YesUnique identifier and token for controlling the call
client_state
stringNoUse this field to add state to every subsequent webhook.
command_id
string (UUID)NoUse this field to avoid duplicate commands.
ruby
response = client.calls.actions.reject("call_control_id", cause: :USER_BUSY)

puts(response)
Primary response fields:
  • response.data.result
在现有工作流中触发后续操作，而无需创建新的顶层资源。
client.calls.actions.reject()
— 
POST /calls/{call_control_id}/actions/reject
参数类型必填描述
cause
enum (CALL_REJECTED, USER_BUSY)是拒接通话的原因
call_control_id
string (UUID)是用于控制通话的唯一标识符和令牌
client_state
string否用于给后续所有webhook添加自定义状态
command_id
string (UUID)否用于避免重复执行指令
ruby
response = client.calls.actions.reject("call_control_id", cause: :USER_BUSY)

puts(response)
主要响应字段：
  • response.data.result

Retrieve a call status

获取通话状态

Fetch the current state before updating, deleting, or making control-flow decisions.
client.calls.retrieve_status()
— 
GET /calls/{call_control_id}
ParameterTypeRequiredDescription
call_control_id
string (UUID)YesUnique identifier and token for controlling the call
ruby
response = client.calls.retrieve_status("v3:550e8400-e29b-41d4-a716-446655440000_gRU1OGRkYQ")

puts(response)
Primary response fields:
  • response.data.call_control_id
  • response.data.call_duration
  • response.data.call_leg_id
  • response.data.call_session_id
  • response.data.client_state
  • response.data.end_time
在更新、删除通话或做出控制流程决策前，获取当前通话状态。
client.calls.retrieve_status()
— 
GET /calls/{call_control_id}
参数类型必填描述
call_control_id
string (UUID)是用于控制通话的唯一标识符和令牌
ruby
response = client.calls.retrieve_status("v3:550e8400-e29b-41d4-a716-446655440000_gRU1OGRkYQ")

puts(response)
主要响应字段：
  • response.data.call_control_id
  • response.data.call_duration
  • response.data.call_leg_id
  • response.data.call_session_id
  • response.data.client_state
  • response.data.end_time

List all active calls for given connection

列出指定连接下所有活跃通话

Fetch the current state before updating, deleting, or making control-flow decisions.
client.connections.list_active_calls()
— 
GET /connections/{connection_id}/active_calls
ParameterTypeRequiredDescription
connection_id
string (UUID)YesTelnyx connection id
page
objectNoConsolidated page parameter (deepObject style).
ruby
page = client.connections.list_active_calls("1293384261075731461")

puts(page)
Response wrapper:
  • items: 
    page.data
  • pagination: 
    page.meta
Primary item fields:
  • call_control_id
  • call_duration
  • call_leg_id
  • call_session_id
  • client_state
  • record_type
在更新、删除通话或做出控制流程决策前，获取当前状态。
client.connections.list_active_calls()
— 
GET /connections/{connection_id}/active_calls
参数类型必填描述
connection_id
string (UUID)是Telnyx连接ID
page
object否统一分页参数（deepObject格式）
ruby
page = client.connections.list_active_calls("1293384261075731461")

puts(page)
响应结构：
  • 列表项: 
    page.data
  • 分页信息: 
    page.meta
主要列表项字段：
  • call_control_id
  • call_duration
  • call_leg_id
  • call_session_id
  • client_state
  • record_type

List call control applications

列出呼叫控制应用

Inspect available resources or choose an existing resource before mutating it.
client.call_control_applications.list()
— 
GET /call_control_applications
ParameterTypeRequiredDescription
sort
enum (created_at, connection_name, active)NoSpecifies the sort order for results.
filter
objectNoConsolidated filter parameter (deepObject style).
page
objectNoConsolidated page parameter (deepObject style).
ruby
page = client.call_control_applications.list

puts(page)
Response wrapper:
  • items: 
    page.data
  • pagination: 
    page.meta
Primary item fields:
  • id
  • created_at
  • updated_at
  • active
  • anchorsite_override
  • application_name
在修改资源前，检查可用资源或选择现有资源。
client.call_control_applications.list()
— 
GET /call_control_applications
参数类型必填描述
sort
enum (created_at, connection_name, active)否指定结果的排序顺序
filter
object否统一过滤参数（deepObject格式）
page
object否统一分页参数（deepObject格式）
ruby
page = client.call_control_applications.list

puts(page)
响应结构：
  • 列表项: 
    page.data
  • 分页信息: 
    page.meta
主要列表项字段：
  • id
  • created_at
  • updated_at
  • active
  • anchorsite_override
  • application_name

Additional Operations

其他操作

Use the core tasks above first. The operations below are indexed here with exact SDK methods and required params; use references/api-details.md for full optional params, response schemas, and lower-frequency webhook payloads. Before using any operation below, read the optional-parameters section and the response-schemas section so you do not guess missing fields.
OperationSDK methodEndpointUse whenRequired params
Create a call control application
client.call_control_applications.create()
POST /call_control_applications
Create or provision an additional resource when the core tasks do not cover this flow.
application_name
, 
webhook_event_url
Retrieve a call control application
client.call_control_applications.retrieve()
GET /call_control_applications/{id}
Fetch the current state before updating, deleting, or making control-flow decisions.
id
Update a call control application
client.call_control_applications.update()
PATCH /call_control_applications/{id}
Modify an existing resource without recreating it.
application_name
, 
webhook_event_url
, 
id
Delete a call control application
client.call_control_applications.delete()
DELETE /call_control_applications/{id}
Remove, detach, or clean up an existing resource.
id
SIP Refer a call
client.calls.actions.refer()
POST /calls/{call_control_id}/actions/refer
Trigger a follow-up action in an existing workflow rather than creating a new top-level resource.
sip_address
, 
call_control_id
Send SIP info
client.calls.actions.send_sip_info()
POST /calls/{call_control_id}/actions/send_sip_info
Trigger a follow-up action in an existing workflow rather than creating a new top-level resource.
content_type
, 
body
, 
call_control_id
请优先使用上述核心任务。下方的操作在此处列出了准确的SDK方法和必填参数；完整的可选参数、响应结构和低频webhook payload请查看references/api-details.md。 在使用下方任何操作前，请先阅读可选参数章节和响应结构章节，避免猜测缺失的字段。
操作SDK方法接口地址使用场景必填参数
创建呼叫控制应用
client.call_control_applications.create()
POST /call_control_applications
当核心任务无法覆盖需求时，创建或provision额外资源
application_name
, 
webhook_event_url
获取呼叫控制应用
client.call_control_applications.retrieve()
GET /call_control_applications/{id}
在更新、删除应用或做出控制流程决策前获取当前状态
id
更新呼叫控制应用
client.call_control_applications.update()
PATCH /call_control_applications/{id}
修改现有资源而无需重新创建
application_name
, 
webhook_event_url
, 
id
删除呼叫控制应用
client.call_control_applications.delete()
DELETE /call_control_applications/{id}
移除、解绑或清理现有资源
id
SIP转接通话
client.calls.actions.refer()
POST /calls/{call_control_id}/actions/refer
在现有工作流中触发后续操作，而无需创建新的顶层资源
sip_address
, 
call_control_id
发送SIP信息
client.calls.actions.send_sip_info()
POST /calls/{call_control_id}/actions/send_sip_info
在现有工作流中触发后续操作，而无需创建新的顶层资源
content_type
, 
body
, 
call_control_id

Other Webhook Events

其他Webhook事件

Event
data.event_type
Description
callBridged
call.bridged
Call Bridged
For exhaustive optional parameters, full response schemas, and complete webhook payloads, see references/api-details.md.
事件
data.event_type
描述
callBridged
call.bridged
通话已桥接
如需完整的可选参数、全量响应结构和完整的webhook payload，请查看references/api-details.md。