# Vonage Video

> Vonage Video API sessions, through the Video Connector. Blocked in pipedog: not ported yet.

Source: https://polvallverdu.github.io/pipedog/docs/transports/vonage/



{/* Generated by scripts/generate-providers.ts from data/providers.ts. */}

<Callout type="warn" title="Blocked">
  Vonage Video is blocked: there is no viable JS path for it today.

  **Why.** Upstream uses a native, Python-only SDK. Vonage lists Node.js as coming soon. The Vonage voice (Audio Connector) serializer is a different thing and is already ported.

  **What would unblock it.** Unblocked when Vonage ships its Node SDK.

  Sources: [Vonage Video AI connectors](https://developer.vonage.com/en/video/ai-connectors/overview).
</Callout>

## What it is [#what-it-is]

Vonage Video API sessions, through the Video Connector.

Upstream, it's this class: `VonageVideoConnectorTransport`, in
[`transports/vonage/video_connector.py`](https://github.com/pipecat-ai/pipecat/blob/main/src/pipecat/transports/vonage/video_connector.py).

Its pipedog package will be `@pipedog/transport-vonage`.

* [Pipecat's Vonage Video page](https://docs.pipecat.ai/api-reference/server/services/transport/vonage)

## Get it ported [#get-it-ported]

* [Search the issues](https://github.com/polvallverdu/pipedog/issues?q=is%3Aissue+Vonage+Video) for a request, and upvote it with a reaction.
* If there's none, [open a port request](https://github.com/polvallverdu/pipedog/issues/new?template=feature_request.yml\&title=Port+Vonage+Video+%28VonageVideoConnectorTransport%29\&kind=Port+an+upstream+module\&upstream=src%2Fpipecat%2Ftransports%2Fvonage%2Fvideo_connector.py).
* Or port it yourself: the [contributing guide](https://polvallverdu.github.io/pipedog/docs/contributing.md) explains how modules are ported,
  test by test. The [porting status](https://polvallverdu.github.io/pipedog/docs/contributing/status.md) lists what's done.

Until then, see what is ported in [Transports](https://polvallverdu.github.io/pipedog/docs/transports.md).