从 Plivo 迁移 Voice
盘点入站和出站中继、已分配的电话号码、访问控制列表、凭据列表、主用和备用 URI 以及安全媒体设置。记录所有在号码背后控制行为的独立 Plivo Voice API 应用。
梳理呼叫行为
分别梳理入站始发和出站呼叫。重建客户端连接和接收号码路由，然后验证传输、媒体和主叫身份要求。独立于 SIP 中继变更，单独审查所有 Voice API 呼叫指令。
使用 Bird 的接口约定重建目标连接。逐一映射方向、认证、入站目的地和媒体行为。名称相似的字段并不意味着具有相同的回退、超时或路由语义。
准备替代连接
创建 Bird 工作区、中继和呼叫身份，用于受控测试。启用目的地，并在客户端配置认证和媒体设置。在评估新路径期间，保持现有号码路由不变。
电话号码携转不会迁移其背后的应用。确认每个国家和号码类型的可携性及预期的切换流程。在依赖号码迁移之前，先准备好新的入站路由。
测试完整的客户旅程
使用您控制的号码，验证以下结果：
- 目标客户端完成认证，测试目的地振铃。
- 双向音频正常工作，通话正常结束。
- 语音提示和按键选择到达预期分支。
- 业务工具能够区分成功、失败和不确定的结果。
- 通话记录和事件与应用中的结果关联。
- 录音或转写（如有需要）产生预期的证据。
除了成功路径，还要测试被拒绝的呼叫和不可用的业务依赖。仅凭请求被接受并不能证明替代方案可用。
有计划地迁移流量
确认容量、访问权限和最终号码路由。在评估初始流量期间，保留恢复先前路由的方式。保存历史供应商记录，并维护与应用中客户或任务标识的映射关系。
在通话结束后核对计费成本。比较新工作流时，将所有相关通话段以及任何单独的语音、录音或模型服务纳入考量。
与编码代理协作
将此提示词粘贴到您的编码代理中，并附上您要迁移的集成。编号流程从盘点开始，并明确标注生产环境的变更。
代码示例
Help me evaluate a Voice migration from Plivo to Bird.
1. Read https://bird.com/docs/guides/voice/migrate/plivo.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 Plivo 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.