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

# RingCentral Integration

> Connect RingCentral phone numbers to Famulor via Generic SIP IP Phone provisioning

<Warning>
  **Done for you — any region, any country (our EU partner carrier)**

  If you prefer not to configure a SIP trunk or import numbers yourself, our **EU partner carrier** can supply **local numbers in any region and any country**, set up the **SIP trunk**, and **import the connection into Famulor** for you. Provisioning runs **end-to-end through the partner** (carrier-side), so you skip DIY trunk and number import in Famulor.

  * **Custom number region / full-service onboarding:** [Famulor Custom Number Region form](https://tally.so/r/w4bN2Y)
  * **More detail or bespoke options:** [support@famulor.de](mailto:support@famulor.de)
</Warning>

# RingCentral Integration

> Connect a RingCentral number to Famulor by provisioning it as a Generic SIP IP Phone

RingCentral does not expose a true wholesale SIP trunk to retail customers, but it does support **Generic SIP IP Phone** provisioning — which is what Famulor uses to connect. You provision a virtual SIP endpoint in RingCentral, register it from Famulor with the credentials RingCentral generates, and route a DID to that endpoint.

<Warning>
  **Plan requirement:** Generic SIP IP Phone provisioning is only available on **RingCentral MVP / RingEX Standard or higher** — not on entry-level plans. Confirm in the Service Web before starting.
</Warning>

<Info>
  **Why this works as a "trunk":** Although RingCentral calls it an "IP phone", the Generic SIP option exposes a username, password and SIP domain that any standards-compliant SIP UA can register against. Famulor's LiveKit-backed SIP stack registers as that endpoint.
</Info>

## Step 1: Add a Generic SIP IP Phone in RingCentral

1. Sign in to the [RingCentral Service Web](https://service.ringcentral.com).
2. Go to **Phone System → Phones & Devices → User Phones**.
3. Click **Add Device → Existing Phone → Other Phone**, and choose **Generic SIP/Other phone (manual provisioning)**.
4. Assign a user (this is the user whose extension/DID will be answered by the AI).
5. Save — RingCentral generates SIP credentials.

<Note>
  Older Service Web layouts list this under **Phone System → Phones, Devices & Numbers → IP Phones / SIP**. The wording shifts over time; the option you want is always "Generic SIP" or "Other Phone".
</Note>

## Step 2: Pull the SIP credentials from RingCentral

In the new device's settings, find the **SIP Configuration / Setup details** panel. You need:

```
SIP Domain        e.g. sip.ringcentral.com   (or sipXX.ringcentral.com per region)
Outbound Proxy    e.g. sip.ringcentral.com:5060 (or 5096)
Authorization ID  long numeric ID
Username          long numeric ID (often same as Auth ID)
Password          generated by RingCentral
```

<Warning>
  **Use `sip.ringcentral.com`, not the regional `sip12.ringcentral.com` style hostname.** The regional host is for RingCentral's own desk phones — generic SIP clients should always hit the global gateway.
</Warning>

## Step 3: Import the number into Famulor

1. Open your Famulor dashboard and go to **Phone Numbers → Integrate SIP trunk**.

2. Fill in:

   ```
   Phone number:   The DID assigned to the user in RingCentral (E.164, e.g. +1 415 555 0123)
   Username:       Authorization ID from step 2
   Password:       Password from step 2
   ```

3. Outbound settings:

   ```
   SIP address:            sip.ringcentral.com
   Outbound number format: International (with +)
   ```

4. **Authorization type:** Username and password.

5. **Country:** the country of the assigned DID.

## Step 4: Wait for registration to propagate

RingCentral's antiflood logic takes 1–2 minutes to register a brand-new SIP endpoint. If your first test call returns `403` or `404`, wait two minutes and retry — repeated failed attempts during the propagation window can extend the lockout.

## Step 5: Verify

1. Assign the number to a `Receive phone calls` assistant. Call the DID — the AI should answer.
2. Create a `Make phone calls` assistant with the same number and trigger an outbound test call.

## Common issues

<AccordionGroup>
  <Accordion title="403 Forbidden after a fresh setup">
    Almost always RingCentral antiflood. Wait 2 minutes, then retry. If credentials were copied with a stray space, RingCentral will lock the endpoint for a longer cooldown — re-paste carefully.
  </Accordion>

  <Accordion title="Outbound calls work, inbound rings the user's softphone instead of the AI">
    Make sure the DID is routed to the **extension that owns the Generic SIP IP Phone**, and disable any "simultaneous ring" rules on that extension that would also ring desk apps.
  </Accordion>

  <Accordion title="One-way audio">
    Force PCMU/PCMA codecs. Disable G.722 in the device settings — RingCentral's media servers occasionally negotiate G.722 even when the SIP UA prefers G.711, which causes one-way audio when the upstream platform doesn't support it.
  </Accordion>
</AccordionGroup>

***

<Note>
  Need help with setup? Our support team can walk you through the exact Service Web path for your RingCentral plan.
</Note>

<Tip>
  Related pages: [SIP Integration](/en/provisioning/sip-ai/sip-integration) and [SIP Troubleshooting](/en/provisioning/sip-ai/sip-troubleshooting).
</Tip>