> For a complete page index, fetch https://docs.synthflow.ai/llms.txt. For full documentation content, fetch https://docs.synthflow.ai/llms-full.txt. # RingCentral > Compare Synthflow's RingCentral integrations, the native RingCX IVA integration and the legacy RingEX SIP-extension setup. RingCentral has two products that connect to Synthflow in different ways. **RingCX**, RingCentral's contact center platform, routes voice queue calls into Synthflow natively. **RingEX**, RingCentral's business phone system, connects through a SIP-extension setup that is being sunset and is no longer recommended. For RingEX, we recommend forwarding your RingEX number over the PSTN to a [Synthflow number](/phone-numbers#buy-a-number) or a [Twilio number](/phone-numbers#bring-your-twilio-numbers). You can also use the RingCX integration, or [route calls directly to Synthflow](/route-sip-calls). Talk to your account manager to choose the right path. ## Integrations #### [RingCX](/ringcx) Run Synthflow as an Intelligent Virtual Agent (IVA) in RingCX voice queues. Recommended for RingCentral contact centers. #### [RingEX](/ringex) Legacy SIP-extension setup, kept for existing deployments while it is sunset. ## Comparison | | RingEX SIP extension (legacy) | [RingCX](/ringcx) | | -------------------------- | -------------------------------------------------------------------------------------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------- | | **What it is** | RingCentral's cloud business phone system (RingEX, formerly MVP) | RingCentral's contact center platform | | **Integration model** | Synthflow registers *to* RingCentral as a SIP IP phone (extension) | RingCX routes voice queue calls *into* Synthflow as an Intelligent Virtual Agent (IVA) | | **Synthflow number setup** | Add the number on the **Phone Numbers** page with RingCentral SIP credentials. The **Termination URI** is your RingCentral SIP domain. | Import the workflow channel number with **Phone Provider** set to **RingCX**. The **Origination URI** is filled in for you (`sip:sip.synthflow.ai:32681`). | | **RingCentral-side setup** | Provision a generic SIP IP phone in the Service Portal | Create an IVA integration and build a workflow in Workflow Studio | | **Call transfers** | Warm and cold transfers (SIP or PSTN) work normally | Not supported from Synthflow. Return the call with the **RingCX Handoff** action. | | **Other limits** | No outbound calling. Maximum 5 concurrent calls per extension. | Caller context is passed through a JavaScript node. Calls return to the RingCX workflow. | ## FAQ #### Why is the RingEX SIP-extension integration being sunset? The SIP-extension setup depends on RingCentral behavior outside Synthflow's control, so we can no longer guarantee its reliability. The [legacy setup](/ringex) stays documented for existing deployments, but we do not recommend it for new ones. #### Do these integrations require the Enterprise plan? Yes. SIP trunking and the RingCentral integrations are available on the Synthflow Enterprise plan. #### Can Synthflow make outbound calls on RingCentral? Not from a RingEX SIP extension. RingEX SIP extensions registered through Synthflow cannot place outbound calls, so use a [Synthflow number](/phone-numbers#buy-a-number) or a [Twilio number](/phone-numbers#bring-your-twilio-numbers) instead. With RingCX, Synthflow handles inbound voice queue calls routed from the RingCX workflow. > Choose between the RingCX integration and the legacy RingEX setup. ## Docs - [RingCX](https://docs.synthflow.ai/ringcx.md): Route RingCX voice queue calls to a Synthflow agent over SIP through an Intelligent Virtual Agent (IVA) integration. - [RingEX](https://docs.synthflow.ai/ringex.md): Legacy setup that registers Synthflow as a SIP extension on RingCentral RingEX, kept for existing deployments while it is sunset.