从 Bandwidth 迁移 Voice
盘点 realm、凭据、入站路由优先级、端点权重、号码分配以及任何独立的 Programmable Voice 行为。如果涉及 AI 集成，请将运行时及其入站来源规则与运营商连接分开记录。
梳理呼叫行为
将出站客户端连接和入站号码路由作为独立操作分别梳理。保留你打算继续使用的 PBX（企业电话交换系统）或助手运行时中面向客户的呼叫行为。在迁移流量之前，确认认证、主叫身份和媒体设置会发生哪些变化。
如果应用的 SIP、认证和媒体要求匹配，你可以在保留应用的同时评估连接变更。有意识地重新配置连接，并验证来电和去电、主叫身份、音频和转接。现有的集成不能证明与新运营商路径的兼容性。
准备替代连接
创建 Bird 工作区、中继和呼叫身份，用于受控测试。启用目标并在客户端中配置认证和媒体设置。在评估新路径期间，保持现有号码路由不变。
号码携转不会迁移其背后的应用。确认每个国家和号码类型的可携性以及预期的切换流程。在依赖号码迁移之前，先准备好新的入站路由。
测试完整的客户旅程
使用你控制的号码，验证以下结果：
- 目标客户端完成认证，测试目的地振铃。
- 双向音频正常，通话正常结束。
- 语音提示和按键选择到达预期分支。
- 业务工具能区分成功、失败和不确定结果。
- 通话记录和事件与应用中的结果关联。
- 录音或转写（如有要求）生成预期的凭证。
除成功路径外，还要测试被拒绝的呼叫和不可用的业务依赖。仅凭请求被接受并不能证明替代方案可用。
有计划地迁移流量
确认容量、访问权限和最终号码路由。在评估初始流量期间，保留恢复先前路由的方式。保存历史供应商记录，并维护与应用中客户或任务身份的映射。
通话结束后核对计费成本。在比较新工作流时，纳入所有相关通话段以及任何独立的语音、录音或模型服务。
与编程代理协作
将此提示词粘贴到你的编程代理中，并附上要迁移的集成。编号流程从盘点开始，并明确标注生产环境变更。
代码示例
Help me evaluate a Voice migration from Bandwidth to Bird.
1. Read https://bird.com/docs/guides/voice/migrate/bandwidth.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 Bandwidth 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.