Skip to main content
Osvi AI×Plivo
This guide explains how to connect your Plivo telephony infrastructure to Osvi AI’s conversational AI agents. Once connected, your Osvi agents can handle both inbound and outbound calls over Plivo’s global SIP network with real-time performance and multilingual support — without requiring migration of your existing Plivo SIP trunks or DIDs. The Plivo path uses Osvi’s standard SIP transport. From the platform’s perspective, SIP is vendor-agnostic — LiveKit terminates the trunk and routes the call to your agent identically regardless of which upstream SIP carrier you use, so onboarding mirrors the Ozonetel flow.

​
Prerequisites

​
From Plivo

​
Required Before Starting

Ensure the following details are available from your Plivo account:
  • Active Plivo account
  • SIP domain (endpoint or trunk URI)
    Example: sip.plivo.com or your provisioned trunk URI
  • Assigned DIDs / CLIs / phone numbers
  • SIP username and password for registration-based trunk
    (or the source IP whitelist if you’re using IP-based authentication)
  • Admin credentials and Plivo Console access
    https://console.plivo.com
  • Sufficient SIP channels procured
    • 1 channel = 1 concurrent call

​
From Osvi AI

​
Required Before Starting

Ensure the following is configured on the Osvi side:
  • Active Osvi AI account
    • SIP support is enabled by default
  • Add the SIP endpoint and phone number directly to the agent for outbound calling
  • Obtain UDP SIP server details from your Osvi account manager for inbound routing

​
Platform Configuration

Osvi AI supports simple SIP number configuration directly at the agent level. Supported connectivity method for Plivo:
  • SIP Configuration
This allows seamless integration with your existing Plivo infrastructure while enabling AI-powered inbound and outbound voice workflows. To add a SIP number for outbound, paste the SIP URL from Plivo and the phone number on the agent’s telephony settings. For inbound, get the forwarding URL from your Osvi FDE and point your Plivo application or trunk’s inbound route at it.
SIP supports authentication-based handshakes for more reliable connections.