Plivo Connector

A Plivo connector streams live audio from a Plivo call into a Zero Runtime room using Plivo Audio Streaming. You point a Plivo application at the connector, and Plivo opens a bidirectional WebSocket that carries the call audio into the room. No SIP trunk is required. Setup takes three steps: create the connector, configure your Plivo application, and route the call to a room. If you are new to connectors, read the Connectors Overview first.

How It Works

A caller dials your Plivo number.
Plivo sends an Answer URL request to your connector’s webhook URL.

Zero Runtime resolves routing and responds with Plivo XML that tells Plivo where to stream the audio:

<?xml version="1.0" encoding="UTF-8"?>
<Response>
  <Stream bidirectional="true" audioTrack="inbound" contentType="audio/x-mulaw;rate=8000" keepCallAlive="true">wss://ingest.videosdk.live/plivo?ref=<callRef></Stream>
</Response>

Plivo opens that WebSocket and streams audio. Zero Runtime claims the call, joins the room, and bridges audio in both directions.

You do not implement the WebSocket protocol; Plivo handles it. Audio is G.711 μ-law (audio/x-mulaw) at 8 kHz, in 20 ms frames of 160 bytes, and the call is identified by Plivo’s CallUUID.

Prerequisites

A Zero Runtime account with an API key and secret from the Zero runtime Dashboard. The Server SDK signs and attaches its own management token on every request, so you never set an Authorization header yourself.
An active Plivo phone number.
Your Plivo Auth ID and Auth Token, from the Plivo Console.

Install the Server SDK for your language:

npm install @videosdk.live/server-sdk

go get github.com/videosdk-live/videosdk-server-sdk-go

cargo add videosdk-server-sdk
cargo add tokio --features rt-multi-thread,macros

The Server SDK requires Node.js 18+, Go 1.23+, or Rust 1.75+. Keep your secret on the server — it signs tokens, so it must never reach a browser or mobile app.

Step 1: Create a Connector

Create the connector with a single Server SDK call. Setting the fallback roomId here is the fastest path to a working call, since every call then joins that room.

import { VideoSDK } from "@videosdk.live/server-sdk";

const client = new VideoSDK({
  apiKey: process.env.VIDEOSDK_API_KEY!,
  secret: process.env.VIDEOSDK_SECRET!,
});

const connector = await client.connectors.create({
  provider: "plivo",
  roomId: "abcd-efgh-ijkl",
});

console.log(connector.webhookUrl); // set this as the Plivo Answer URL

client, err := videosdk.NewClient(
	videosdk.WithAPIKey(os.Getenv("VIDEOSDK_API_KEY")),
	videosdk.WithSecret(os.Getenv("VIDEOSDK_SECRET")),
)
if err != nil {
	log.Fatal(err)
}
ctx := context.Background()

connector, err := client.Connectors.Create(ctx, videosdk.CreateConnectorParams{
	Provider: videosdk.ConnectorPlivo,
	RoomID:   "abcd-efgh-ijkl",
})
if err != nil {
	log.Fatal(err)
}

fmt.Println(connector.WebhookURL) // set this as the Plivo Answer URL

use videosdk::{Client, ConnectorProvider, CreateConnectorParams};

let client = Client::builder()
    .api_key("YOUR_API_KEY")
    .secret("YOUR_SECRET")
    .build()?;

let connector = client
    .connectors()
    .create(CreateConnectorParams {
        provider: Some(ConnectorProvider::PLIVO),
        room_id: Some("abcd-efgh-ijkl".into()),
        ..Default::default()
    })
    .await?;

println!("{:?}", connector.webhook_url); // set this as the Plivo Answer URL

connectors.create accepts the following options.

Option	Required	Description
`provider`	Yes	Must be Plivo: `"plivo"` in Node.js, `videosdk.ConnectorPlivo` in Go, `ConnectorProvider::PLIVO` in Rust.
`name`	No	A label to help you recognize the connector later.
`roomId`	No	Fallback room that calls join when no routing rule matches. Set this for the simplest setup. It is returned on the connector as `defaultRoomId`.
`defaultRuleId`	No	Fallback routing rule ID, for dynamic routing.
`region`	No	Pins the media and ingest region (e.g., `us002` or `in002`). When omitted, the region is derived from the caller.

The call returns the connector, including the webhookUrl you need for the next step.

Field	Type	Description
`id`	string	Connector ID, prefixed with `cn_`. Use it to fetch, rotate, or delete the connector.
`provider`	string	Telephony provider — `plivo` here.
`name`	string	Display name.
`webhookUrl`	string	The URL you set as the Plivo Answer URL in the next step. It embeds the secret webhook key (`whk_...`).
`defaultRoomId`	string	Fallback room used when no routing rule resolves.
`defaultRuleId`	string	Routing rule applied by default.
`region`	string	Region call ingestion is pinned to.
`createdAt`	string	Creation timestamp (ISO-8601).

Copy the webhookUrl. You will use it as the Answer URL in Step 2.

Keep the webhook URL private. Anyone who has the webhook URL can route calls into your room, because the key is part of the URL. If it leaks, rotate the key to invalidate the old URL.

Step 2: Configure Plivo

Plivo routes calls through an application. Point the application’s Answer URL at the webhookUrl from Step 1, then assign your number to that application.

Open your Plivo XML application

In the Plivo Console, go to Voice > Applications > XML and create or edit an application.

Set the Answer URL

Set the Answer URL to the webhookUrl, with the method set to POST, and save the application.

Assign your number to the application

Go to Phone Numbers > Numbers, open your number, set its Plivo Application to the application you just configured, and save.

That is the entire provider-side setup. When the number rings, Plivo posts to the Answer URL and Zero Runtime replies with the <Stream> XML automatically.

Step 3: Route the Call

Routing decides which room a call joins. You have three options, from simplest to most flexible:

Connector default. The roomId you set in Step 1 sends every call to one fixed room. Best for a single destination or for testing.
Per-call override. Append a roomId query parameter to the Answer URL (...whk_xxx?roomId=<roomId>) to target a specific room for that number.
Routing rules. For different callers or numbers landing in different rooms, or to attach an AI agent, create a routing rule and reference it with defaultRuleId.

If you set roomId in Step 1, you can skip this step and move straight to testing.

Step 4: Test an Inbound Call

Add a participant or AI agent to the target room, so there is audio to exchange.
Call your Plivo number from any phone.
Confirm that the caller hears the room and the room hears the caller.

If you registered lifecycle webhooks, you will see call-started, then call-answered, and finally call-hangup when the call ends. These are the quickest way to confirm the flow end to end.

Manage the Connector

List your connectors, or fetch a single one by ID:

await client.connectors.list();
await client.connectors.get(connectorId);

client.Connectors.List(ctx)
client.Connectors.Get(ctx, connectorID)

client.connectors().list().await?;
client.connectors().get(connector_id).await?;

Rotate the Webhook Key

Rotating the key invalidates the current webhook URL immediately and returns a new one. Update the Plivo Answer URL right after, or calls will stop reaching Zero Runtime.

await client.connectors.rotateKey(connectorId); // invalidates the old webhook URL

client.Connectors.RotateKey(ctx, connectorID) // invalidates the old webhook URL

client.connectors().rotate_key(connector_id).await?; // invalidates the old webhook URL

Delete a Connector

await client.connectors.delete(connectorId);

client.Connectors.Delete(ctx, connectorID)

client.connectors().delete(connector_id).await?;

Lifecycle Webhooks

To track calls on your server, register a webhook URL and listen for events such as call-started, call-answered, and call-hangup. Each request carries a videosdk-signature header (a base64 RSA-SHA256 signature of the body) so you can verify it. Connectors use the same webhook system as SIP, so see SIP Webhooks for the full event list, payloads, and registration.

Troubleshooting

Symptom	Likely cause and fix
Call connects but there is no audio	No one is in the target room, or the fallback `roomId` is wrong. Add a participant or agent and verify the room ID.
Call hangs up right after answering	The number is not assigned to the application, or the Answer URL method is not POST. Recheck the application configuration and number assignment.
The stream never starts	The claim expired (more than 90 seconds), or routing resolved no room. Confirm the Answer URL is the current webhook URL and that a room is resolved.
Connector calls fail with 401 or 403	The API key or secret passed to the Server SDK client is missing or wrong. Check them in the Zero runtime Dashboard.
Audio works but quality is low	Telephony audio is 8 kHz narrowband μ-law by design. This is expected for PSTN calls.

Get started

SIP Connect

Websocket Connectors

Managing Calls

Call Routing

Integrations

How It Works

Prerequisites

Step 1: Create a Connector

Step 2: Configure Plivo

Step 3: Route the Call

Step 4: Test an Inbound Call

Manage the Connector

Rotate the Webhook Key

Delete a Connector

Lifecycle Webhooks

Troubleshooting

Reference

​How It Works

​Prerequisites

​Step 1: Create a Connector

​Step 2: Configure Plivo

​Step 3: Route the Call

​Step 4: Test an Inbound Call

​Manage the Connector

​Rotate the Webhook Key

​Delete a Connector

​Lifecycle Webhooks

​Troubleshooting

​Reference

How It Works

Prerequisites

Step 1: Create a Connector

Step 2: Configure Plivo

Step 3: Route the Call

Step 4: Test an Inbound Call

Manage the Connector

Rotate the Webhook Key

Delete a Connector

Lifecycle Webhooks

Troubleshooting

Reference