Telephony Integration
Bring your own carrier (BYOC) and point any number you own at a Rymi agent. One gateway handles Plivo, Twilio, Vonage, and Telnyx behind a common set of routes, so the carrier you pick only changes which credentials you paste and which audio codec runs.
BYOC Billing Model
Self-serve PSTN usage is split into two bills:
- Rymi platform minutes: Charged at the agent's per-minute rate. That is its managed SKU price, or for a custom agent the stack's component cost plus the flat $0.02/min platform fee.
- Carrier pass-through: Your connected Plivo, Twilio, Vonage, or Telnyx account bills PSTN minutes, number rental, taxes, and optional carrier add-ons directly.
Rymi does not sell or purchase phone numbers directly in self-serve. Provision numbers in your connected provider account, then use Rymi to attach registered BYOC numbers to agents. Enterprise plans can bundle telecom under a custom agreement.
For cost planning, add the carrier's per-minute rate to the Rymi agent's per-minute rate for PSTN legs. As a U.S. local outbound example, published April 2026 rates are $0.0115/min on Plivo and $0.014/min on Twilio before taxes and optional add-ons. WebRTC-only calls do not add PSTN carrier minutes.
Unified Route Structure (For BYOC)
Instead of carrier-specific endpoints, use the following patterns:
| Provider | Inbound Hook URL (Answer URL) | WebSocket URL |
|---|---|---|
| Plivo | https://gateway.rymi.live/inbound/plivo?agent_id=ID | wss://gateway.rymi.live/ws/plivo/ID |
| Twilio | https://gateway.rymi.live/inbound/twilio?agent_id=ID | wss://gateway.rymi.live/ws/twilio/ID |
| Vonage | https://gateway.rymi.live/inbound/vonage?agent_id=ID | wss://gateway.rymi.live/ws/vonage/ID |
| Telnyx | https://gateway.rymi.live/inbound/telnyx?agent_id=ID | wss://gateway.rymi.live/ws/telnyx/ID |
Carrier Setup
For Twilio, Plivo, Telnyx, and Vonage, Rymi sets the inbound webhook for you when you import or attach a number in the dashboard, and shows the result in the Numbers table. The manual steps below are only needed for a BYO-application setup, or if auto-configuration reports failed.
Plivo
Auto-configured: Rymi finds-or-creates a "Rymi Inbound" application, keeps its answer URL current, and links your number to it. To set it manually, point your number's Answer URL at the inbound hook URL above, or use TwiML XML:
<Response>
<Connect>
<Stream url="wss://gateway.rymi.live/ws/plivo/AGENT_ID" />
</Connect>
</Response>Twilio
Auto-configured: Rymi sets the number's voice URL directly. To set it manually, point the number's A call comes in webhook at the inbound hook URL above. Rymi returns the required TwiML <Connect><Stream> response.
Vonage
Auto-configured: Rymi finds-or-creates a Voice application, keeps its answer URL current, and links your number to it. This needs the four required Vonage credentials (API Key, API Secret, Voice Application ID, Voice Private Key). To set it manually, point your application's Answer URL at the inbound hook URL above. Rymi returns the required NCCO (JSON) to open a high-fidelity 16kHz WebSocket.
Telnyx
Auto-configured: Rymi sets the TeXML application's voice_url and assigns the number to that connection. The Connection ID must be a TeXML application — Rymi validates this at connect time and rejects a non-TeXML ID. To set it manually, point your TeXML Application's Answer URL at the inbound hook URL above. Connect credentials are your Telnyx API Key and Connection ID; an optional webhook signing secret enables Ed25519 verification of inbound callbacks.
Audio Specifications
Rymi automatically optimizes the stream for each carrier:
- Plivo/Twilio/Telnyx: 8kHz μ-law (G.711)
- Vonage: 16kHz L16 (Linear PCM)
- WebRTC: 16kHz - 48kHz (Adaptive)

