docs(agents): bring your own number, import via SIP trunk - #147
Conversation
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
|
Preview deployment for your docs. Learn more about Mintlify Previews.
💡 Tip: Enable Workflows to automatically generate PRs for you. |
|
Important Review skippedDraft detected. Please check the settings in the CodeRabbit UI or the ⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Pro Plus Run ID: You can disable this status message by setting the Use the checkbox below for a quick retry:
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
|
BYO SIP PR set:
Deploy order: fish-agent -> platform-api -> platform-web; docs merge at launch. |
Summary
Customer-facing guide for BYO SIP number import: new
agents/telephony/byo-sippage (how it works, the SIP origination endpoint, import via console and API with the full field table, inbound authentication choices, Twilio Elastic SIP Trunking and Asterisk walkthroughs, outbound/transfer capability matrix, in-placesip-configediting, zero-telephony-fee billing, release semantics), navigation entry, and cross-references from the phone numbers and transfers pages.All API examples mirror requests exercised against the implementation (local real-stack E2E plus the platform-api test suite).
Draft until the feature ships: merge together with the platform-api / fish-agent / platform-web BYO SIP PRs (linked in comments). The API reference pages pick up the new endpoint automatically once
update:openapipulls the deployed spec.🤖 Generated with Claude Code
Need help on this PR? Tag
@codesmith-botwith what you need. Autofix is disabled.