Connect RingCentral to ElevenLabs Conversational AI Voice Agents

Real-Time Voice Processing

• Ultra-low latency voice AI with response times under 100ms
• Advanced speech recognition with natural language understanding
• Seamless turn-taking and interruption handling for natural conversations
• Eliminates the robotic delays that break conversational flow

Enterprise Telephony Integration

• Direct SIP trunk integration with RingCentral's cloud infrastructure
• Programmable call routing and control via RingCentral APIs
• Support for both inbound and outbound AI-driven calls
• Integration with existing PBX systems and call center infrastructure

Intelligent Call Routing & IVR Replacement

• Natural language intent recognition replaces traditional phone trees
• Dynamic call routing based on conversational context
• Seamless escalation to human agents with full conversation history
• Context-aware transfers using RingCentral's Call Control APIs

Live Transcription & Agent Assist

• Real-time conversation transcription with speaker diarization
• AI-powered agent assistance during live calls
• Automatic conversation summaries for seamless handoffs
• Rich analytics and insights from every interaction

Multilingual Voice Capabilities

• Native support for 25+ languages with authentic regional accents
• Language detection and automatic switching mid-conversation
• Custom voice personas and brand-aligned voice generation
• Culturally-aware conversation flows for global deployments

Step 1: Choose Your Integration Path

Option A: FreePBX/Asterisk SIP Bridge (Recommended)

A self-hosted server registers with RingCentral as a generic SIP IP phone device, then forwards calls to and from ElevenLabs' SIP endpoint. This is the most flexible option and keeps your numbers on RingCentral. Requires a VPS with a static IP and basic Linux administration.

Option B: RingOut API Integration (Outbound Only)

Use the RingCentral RingOut API to programmatically trigger calls from your RingCentral numbers. ElevenLabs handles the AI conversation; a SIP bridge you control connects the audio. Does not support inbound calls arriving at your AI agent. Best for teams building custom call automation workflows with developer resources available.

Option C: Third-Party Intermediary Service (Inbound Only, no porting):

A compatible third-party SIP service forwards your RingCentral calls to ElevenLabs via a direct SIP INVITE — no SIP REGISTER with ElevenLabs required. RingCentral call-forwards to a number on the intermediary service, which routes the call onward. No server to manage.

• 2Chat — Native ElevenLabs integration with a call flow builder that sends calls directly to your ElevenLabs agent SIP URI. See 2Chat's ElevenLabs guide.
• Any SIP proxy service that sends direct INVITE to a SIP URI — the requirement is that the service sends INVITE requests directly to sip:+1NXXNXXXXXX@sip.rtc.elevenlabs.io:5060 rather than attempting registration.

Note: Services that register as an IP phone extension on RingCentral and route calls to their own AI platform — such as Synthflow — do not connect to ElevenLabs agents. They are separate AI platforms, not SIP bridges.

Option D: Port Your Number (Recommended for Production)

Move your number from RingCentral to a provider with native ElevenLabs SIP compatibility. This eliminates the bridge layer entirely and gives you the simplest, lowest-latency setup. Choose this option if long-term reliability matters more than keeping your number on RingCentral. Confirmed compatible providers: Twilio, Plivo, SignalWire, DIDWW, or Telnyx.

Step 2: FreePBX Bridge Configuration (Option A)

This is the recommended path for production deployments requiring both inbound and outbound calls.

2.1 Install FreePBX

1. Download FreePBX Distro from freepbx.org/downloads
2. Install on a VPS with public IP (minimum 2 CPU, 2GB RAM)
3. Complete setup at http://<your-server-ip>/admin. You can also install Asterisk directly.

2.2 Configure RingCentral Trunk

1. Navigate to Connectivity → Trunks → Add SIP (chan_pjsip) Trunk
2. Set Trunk Name: RingCentral-Inbound
3. In pjsip Settings → General:
4. • Username: Your RingCentral SIP Username
   • Secret: Your RingCentral SIP Password
   • SIP Server: sip.ringcentral.com
   • SIP Server Port: 5090 (non-TLS) or 5096 (TLS)
5. In pjsip Settings → Advanced:
6. • Outbound Proxy: sip:sipXX.ringcentral.com:5090 (replace XX with your region)
7. In pjsip Settings → Registration:
8. • Register String: USERNAME:PASSWORD:AUTHID@sipXX.ringcentral.com:5090/USERNAME

Key RingCentral Fields Required:

RingCentral requires an Outbound Proxy and separate Authorization ID field. These are the fields ElevenLabs' SIP trunk configuration does not support, which is why a FreePBX bridge is necessary.

2.3 Configure ElevenLabs Trunk

1. Navigate to Connectivity → Trunks → Add SIP (chan_pjsip) Trunk
2. Set Trunk Name: ElevenLabs-Outbound
3. In pjsip Settings → General:
4. • SIP Server: sip.rtc.elevenlabs.io
   • SIP Server Port: 5060
   • Authentication: Use digest authentication with username and password.

2.4 Configure Call Routing

1. Navigate to Connectivity → Inbound Routing
2. Create route: RingCentral trunk → ElevenLabs trunk
3. Navigate to Connectivity → Outbound Routing
4. Create route: ElevenLabs trunk → RingCentral trunk

2.5 Import the number into ElevenLabs:

1. Go to Phone Numbers in the ElevenLabs dashboard.
2. Click Import a phone number and select SIP Trunk.
3. Enter your number in E.164 format, set transport to TCP, enter credentials for digest auth.
4. Make sure to configure both the Inbound and Outbound as shown in our SIP Trunking Guide.
5. Click Save, then assign an agent to the number.

Step 3: RingOut API Configuration (Option B - Outbound Only)

This option is for developers who want to programmatically trigger outbound calls through RingCentral without managing a SIP bridge server. Important: This approach requires significant custom development and does not allow you to import a RingCentral number directly into ElevenLabs.

What RingOut API Does:

RingOut API lets you programmatically initiate a phone call between two numbers. For example, you can tell RingCentral to "call this customer and connect them to this destination." The call happens entirely on RingCentral's infrastructure. This is essentially the same architecture as Option A, just initiated via API instead of receiving an inbound call.

3.1 When to Consider This Option:

• You want to programmatically trigger AI-driven outbound calls
• You have development resources to build a WebSocket/SIP bridge
• You're building a custom telephony application

3.2 Implementation Overview:

1. Create a RingCentral Developer App with RingOut permissions at developers.ringcentral.com
2. Build a SIP endpoint that receives calls from RingOut (your FreePBX server from Option A can serve this role)
3. Configure your SIP endpoint to route incoming RingOut calls to ElevenLabs' SIP trunk
4. Use your ElevenLabs Agent's configured number as the routing destination

For most users, Option A (FreePBX Bridge) or Option D (Port Number) provides a simpler path.

Step 4: Number Porting (Option D)

This option moves your phone number from RingCentral to a SIP trunking provider that has full compatibility with ElevenLabs. Porting is optional — you can keep your number on RingCentral and use Option A or C instead.

Compatible SIP Providers:

These providers offer full SIP trunking with ElevenLabs compatibility:

• Twilio — Programmable voice APIs, extensive developer resources
• Plivo — Cost-effective SIP trunking, straightforward setup
• SignalWire — SIP trunking with FreeSWITCH expertise
• DIDWW — Global SIP trunking coverage
• Telnyx — Global coverage, competitive rates

Porting Notes:

• Don't cancel your RingCentral service until the port is complete — this can cause the port to fail
• Toll-free numbers may take longer to port than local numbers
• If you have multiple numbers, you can port them all in a single request
• Your RingCentral service may continue with a new number if you have other services (fax, extensions, etc.)