> ## 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.

# Vonage

> Prepare a Vonage SIP trunk, its regional domain, and authentication details for a future reviewed Threetone route.

Use this guide to prepare a Vonage SIP candidate. Threetone does not have a Vonage-specific phone import variant or a verified Vonage calling adapter. The generic SIP configuration must still pass a supported runtime review.

## Before you begin

Ask the Vonage administrator for the trunk's regional domain, number assignment, authentication method, and existing inbound destination. Keep the provider management credentials separate from SIP authentication.

Vonage's current [SIP technical details](https://developer.vonage.com/en/sip/technical-details) describe a dedicated regional trunk domain and authentication through SIP credentials or an access-control list. Account API credentials are not a substitute for those trunk credentials.

## Prepare the route

<Steps>
  <Step title="Confirm the trunk identity">Record the exact domain issued for your trunk and its region. Identify the caller and destination number formats expected by Vonage; its SIP guidance uses E.164 for these identities.</Step>
  <Step title="Map authentication by direction">For outbound requests, record the carrier destination and whether it expects digest credentials or an allowed source address. For inbound traffic, collect provider source ranges and the intended runtime ingress separately.</Step>
  <Step title="Compare transport and media">Review provider requirements against the [SIP reference](/agents-platform/deploy/telephony/sip-reference). Document transport, certificate domains, media encryption, and codecs instead of assuming the same settings apply in both directions.</Step>
  <Step title="Prepare the release test">Require a released ingress destination and credential handoff before changing the Vonage route. Plan answer, two-way audio, caller identity, hangup, and fallback checks with authorized test numbers.</Step>
</Steps>

## Failure handling

For authentication rejection, compare the trunk-specific credential or allowed source address with the actual deployment. For a call that answers without usable audio, inspect media negotiation and network reachability separately from SIP signaling. Preserve the existing provider route until the candidate passes review.

## Frequently asked questions

<AccordionGroup>
  <Accordion title="Should I send provider: vonage to the import API?" id="vonage-faq-import">No. The API has no such variant. A reviewed SIP candidate uses the generic SIP schema; saving it does not validate Vonage compatibility.</Accordion>
  <Accordion title="Can I reuse my Vonage API key as the SIP password?" id="vonage-faq-password">Do not substitute management credentials. Obtain the trunk's current authentication details from the Vonage administrator.</Accordion>
</AccordionGroup>


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