The Connectivity add-on lets you route calls from your Ringover IVR (voice menu) to an external platform over SIP — most often an external AI voice agent / voicebot (for example Retell, ElevenLabs, Vapi or Amelia) or another third-party voice tool. It gives you multiple options: connect one of the AI agents offered through the add-on, or route to your own external tool via a SIP endpoint.

Prerequisites

This add-on can only be activated by administrators and/or super administrators of the account.
You must have a Ringover Business account to benefit from the add-on.
The Connectivity add-on activated from the Marketplace.
The SIP connection details for your external tool (SIP URI, and — if required — credentials and transport type).

What the Connectivity add-on does

Is this a SIP trunk?

Ringover does not provide a traditional, bidirectional SIP trunk. Connectivity gives you a one-way (outbound) SIP endpoint inside your IVR: Ringover places the SIP call out to your external tool. If you’ve been asked to set up “an inbound and outbound SIP trunk” or “BYOC”, this add-on covers the outbound-to-external-tool part of that request.

Common use cases

Connecting a Ringover number or IVR to an external AI voice agent / voicebot .
Piloting on a single switchboard (standard) first, then extending to more lines once validated.

1. Activate the Connectivity add-on

The Connectivity add-on gives you access to preconfigured IVR scenarios for external connections, such as a SIP endpoint (to connect your phone system to another platform via SIP), and the ability to enable additional bots.

Go to your Dashboard.
Navigate to Store > Marketplace

2. Enable your AI agent (if you use one)

If you’re connecting an AI agent, some agents must first be enabled from Integrations after the Connectivity add-on is purchased. Enable the agent you want to use there, then it becomes available as a scenario on your IVR page.

Once activated, it will appear in the integration's page
Select one of the bots offered by Ringover (if you want to add others beyond those enabled by default).

Skip this step if you’re only routing to your own external tool via the SIP endpoint.

3. Configure the SIP endpoint

Set up your voice menus to properly integrate your third-party tools into your incoming call flow.

Go to your IVR's page.
Locate the scenarios corresponding to the “SIP endpoint” scenario.
Fill in the fields below.

Only the SIP URI is required. Every other field depends on what your external provider asks for.

Field	Required?	What to enter
Votre URI SIP (Your SIP URI)	Mandatory	The address Ringover sends the call to, provided by your external tool — e.g. sip:33110001000@phone.ringover.com.
Transport Type	Depends on provider	How the SIP signalling is carried: UDP, TCP or TLS. Match what your provider specifies (see below).
Login	Optional	Only if your external provider requires authentication. Leave blank if it does not.
Password	Optional	The password that goes with the Login above. Only if the provider requires authentication.
Custom Headers	Optional	Only if your provider requires specific SIP headers to be sent with the call. Leave blank otherwise.

Choosing a Transport Type

UDP — the traditional default for SIP : Connectionless and low-overhead, so it’s fast, but it has no delivery guarantee and no encryption. Fine on stable networks.
TCP — connection-oriented and reliable: it guarantees ordered delivery and handles retransmission, which helps on less stable networks or with larger SIP messages. Not encrypted.
TLS — TCP with encryption: It secures the SIP signalling so credentials and call information aren’t sent in clear text. Choose this when your provider requires secure signalling.

If you’re unsure, use the transport type your external provider specifies.

Technical specifications

Parameter	Specification
Directionality	Unidirectional — outbound only (from Ringover to your endpoint). Inbound SIP requests into Ringover are not supported.
Call handling	Ringover sends a SIP INVITE to your endpoint and waits for a standard SIP response (e.g. 200 OK). Ringover does not accept incoming SIP traffic.
Transport	UDP / TCP / TLS (selectable per external provider).
Authentication	Optional Digest authentication (Login / password) carried in the INVITE — used only when the external provider requires it.
Media codecs	Both PCMA and PCMU are supported. Codecs are not configurable — no action needed on your side.

Limitations

Outbound only. Ringover initiates the call; it will not receive SIP INVITEs sent into Ringover.
This is not a full bidirectional SIP trunk and not classic BYOC number hosting.
NOT Supported Call transfer via REFER (inbound/outbound).

Troubleshooting & FAQ

Do you offer SIP trunks?

Not a classic bidirectional trunk. We offer the Connectivity add-on — an outbound SIP endpoint from your IVR to external tools. It covers connecting AI voice agents and third-party voice platforms.

I get “407 Proxy Authentication Required” when connecting

A 407 means the digest authentication handshake didn’t complete. Check the Login / password on the SIP endpoint scenario and confirm the credentials are being sent with the INVITE.

My external tool can’t call into Ringover.

That’s expected — the connection is outbound only. Ringover places the call out; it does not accept SIP calls coming in. If you need to transfer back to a Ringover IVR, it would have to be done via traditional Call Forwarding.

🎉 You now know how to configure your SIP connections!