Connect RingCentral (cloud phone)

RingCentral connects using a "bring your own app" (BYO) model: instead of Omnifox using a shared app, each customer registers their own application in RingCentral and gives Omnifox that app's Client ID and Client Secret.

Requirements

• A RingCentral account (production or sandbox)
• An app registered at developers.ringcentral.com, of type REST API, with OAuth Authorization Code authentication
• That app's Client ID and Client Secret

Steps to connect

1. At developers.ringcentral.com, create a REST API app with OAuth Authorization Code authentication.
2. In Omnifox, go to Channels → Connect New Channel, pick RingCentral, and paste your app's Client ID and Client Secret.
3. Choose the environment: Production (platform.ringcentral.com) or Sandbox (platform.devtest.ringcentral.com), as appropriate.
4. Omnifox shows you a Redirect URI: copy it and register it in your app's OAuth settings on RingCentral.
5. Click Connect with RingCentral — you're redirected to log in and authorize access; once you're back, the channel is active.

Configuration

• Client ID / Client Secret: credentials for YOUR RingCentral app (not shared by Omnifox).
• Server: Production or Sandbox — must match where your real account lives.
• Access tokens last about an hour and the refresh token rotates roughly every 7 days; Omnifox renews them automatically.

Example

A customer calls your RingCentral number; the system runs a RingOut that first calls the agent's registered device and, once they answer, bridges the call to the customer's number. The event shows up in the Inbox as part of that conversation.

Tips

• If you're testing the integration, use Sandbox first — that way you don't risk your production line while validating the flow.
• Keep the Client Secret safe: RingCentral only shows it once, when the app is created.

Troubleshooting

• Authorization fails with "redirect_uri mismatch": confirm the Redirect URI registered in RingCentral matches exactly what Omnifox showed you, with no extra or missing trailing slash.
• The channel stops receiving events after a few days: the refresh token may have failed to rotate; reconnect the channel to re-authorize from scratch.