> ## Documentation Index
> Fetch the complete documentation index at: https://docs.threetone.in/llms.txt
> Use this file to discover all available pages before exploring further.

# Plivo

> Prepare Plivo Zentrunk inbound and outbound configuration, authentication, and fallback destinations for a future SIP route.

Plivo Zentrunk is a candidate carrier path for a future SIP deployment. Threetone has no Plivo-specific import variant or verified Plivo runtime adapter. Use the generic SIP contract only as a configuration review boundary.

## Before you begin

Collect the trunk IDs, number assignment, SIP domain, and authentication details from the Plivo administrator. Zentrunk separates inbound and outbound trunks. Its [trunk API reference](https://www.plivo.com/docs/sip-trunking/api/trunks) identifies an inbound primary URI and optional fallback URI; outbound trunks use IP access controls, credentials, or both.

## Review both directions

<Steps>
  <Step title="Identify the inbound destination">Record the primary URI and any fallback URI attached to the inbound trunk. Keep their priority and expected behavior in the release plan. Do not replace them with an assumed Threetone address.</Step>
  <Step title="Identify outbound authentication">Record the outbound trunk domain and the associated credential or IP access-control configuration. The source address must match the future deployed runtime, not a developer laptop.</Step>
  <Step title="Map the accepted fields">Compare transport, media policy, credentials, and codecs with the [SIP reference](/agents-platform/deploy/telephony/sip-reference). Keep Plivo management credentials separate from SIP username and password.</Step>
  <Step title="Prepare acceptance and rollback">Wait for a released runtime destination and credential handoff. Then test each direction independently and verify the provider's configured fallback behavior before expanding traffic.</Step>
</Steps>

## Failure handling

An outbound authentication error and an unreachable inbound URI require different fixes. Capture the trunk direction, provider call identifier, timestamp, and SIP result. If fallback is unexpectedly used, investigate the primary destination before removing the fallback. See [Plivo's Zentrunk documentation](https://www.plivo.com/docs/sip-trunking) for provider-side configuration.

## Frequently asked questions

<AccordionGroup>
  <Accordion title="Does an inbound trunk prove outbound calling works?" id="plivo-faq-directions">No. Zentrunk's inbound and outbound objects have different destinations and authentication requirements.</Accordion>
  <Accordion title="Will Threetone create the primary and fallback URIs?" id="plivo-faq-uris">No. Import does not provision provider resources. The deployment must supply and verify its actual supported runtime destinations.</Accordion>
</AccordionGroup>


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.