从 Vonage 迁移 Voice
盘点 NCCO 生成、应答和事件 webhook、REST 呼叫控制操作、号码路由及客户端集成。记录应用程序在通话开始后修改通话的位置。
梳理通话行为
将提示音、音频和按键决策转换为所选的 Bird 通话工作流。分别检查对话、连接、录音和输入语义。在对应的客户旅程通过真实的受控通话测试之前，保留原始路由。
NCCO 以 Vonage 的格式描述通话行为。逐一转换每个动作的预期结果，然后验证输入处理、webhook 时序、录音来源及任何多方通话行为。仅匹配动作名称不足以确认行为等效。
准备替代连接
为受控测试创建 Bird 工作区、中继和呼叫身份。启用目标并在客户端中配置认证和媒体设置。在评估新路径期间保持现有号码路由不变。
号码携转不会迁移其背后的应用程序。确认每个国家和号码类型的可携性及预期的切换流程。在依赖号码迁移之前先准备好新的入站路由。
测试完整的客户旅程
使用你控制的号码，验证以下结果：
- 目标客户端完成认证，测试目的地振铃。
- 双向音频正常工作，通话正常结束。
- 提示音和按键选择到达预期分支。
- 业务工具能区分成功、失败和不确定的结果。
- 通话记录和事件与应用程序中的结果关联。
- 录音或转写（如需要）生成预期的证据。
除成功路径外，还要测试被拒绝的通话和不可用的业务依赖。仅凭请求被接受不能证明替代方案可正常工作。
有计划地迁移流量
确认容量、访问权限和最终的号码路由。在评估初始流量期间保留恢复先前路由的方式。保存历史供应商记录，并维护与应用程序中客户或任务标识的映射关系。
在通话结束后核对计费成本。比较新工作流时，纳入所有相关通话段以及任何单独的语音、录音或模型服务。
与编码代理协作
将此提示粘贴到你的编码代理中，并附上要迁移的集成。编号流程从盘点开始，并明确标注生产环境变更。
代码示例
Help me evaluate a Voice migration from Vonage to Bird.
1. Read https://bird.com/docs/guides/voice/migrate/vonage.md. Use the .md alternatives of linked Bird guides for the steps below.
2. Check for a connected Bird MCP server or an installed, signed-in Bird CLI. Use whichever is available and discover its tools or command help. If neither is available, follow https://bird.com/docs/ai/set-up-your-agent.md. Do not invent operation names or install a second integration.
3. Perform a read-only inventory of my current call sites, numbers, SIP configuration, call-control instructions, event handlers, recordings, speech services and business tools. Identify secrets without printing them. Show the dependencies that stay with Vonage and the ones that need replacement.
4. Read https://bird.com/docs/guides/voice/sip-trunks.md, https://bird.com/docs/guides/voice/placing-calls.md and https://bird.com/docs/guides/voice/receiving-calls.md. Prepare the replacement connection and caller-identity requirements. Use https://bird.com/docs/guides/voice/call-sequences.md for defined menus and https://bird.com/docs/ai/voice-conversations.md for a conversational runtime. Verify each operation against the connected surface before proposing an executable step.
5. Prepare a test of one complete journey: setup, audio in both directions, keypad input, unanswered and failure paths, handoff where needed, and business-tool results. Show the exact target, configuration and expected cost before placing a call or recording audio; wait for my approval. Do not buy numbers, submit a port, change production routing or stop the existing provider without my explicit approval.
6. Use https://bird.com/docs/guides/voice/events.md and https://bird.com/docs/guides/voice/call-log.md to reconcile the outcome. Keep missing evidence and uncertain results visible. A spoken confirmation is not proof that a business action succeeded.
7. Return the integration differences, test evidence, unresolved requirements and rollback plan. Keep the current service running until I approve cutover. If a number port needs support, inspect the available support command or tool, prepare the exact request and ask for approval before submitting it. Return the ticket reference if authorized; a ticket does not schedule or complete a port.