User Persona & Impact
Target Audience: Enterprise Customers with Hybrid Deployments (RingCentral + 3rd Party PBX like Cisco CUCM/Avaya).

Impacted Area: Cloud Connector / Inbound Routing Logic / Hybrid SIP Trunks.

Severity: High (Blocks migration/coexistence and causes routing failures).

Problem Statement
The current 10-range hard limit for Cloud Connector inbound call routing is insufficient for enterprise customers managing coexisting/split dial plans.

When migrating from an on-premise PBX (e.g., Cisco CUCM) to RingCentral, customers often have a single block of extensions where some numbers have migrated to RC, but the rest remain on the legacy PBX.

Because RingCentral currently lacks an "Exception" or "Exclude" mechanism within its routing ranges, a customer is forced to break a single extension block into multiple smaller fragments. This "Swiss cheese" routing model exhausts the 10-range limit almost immediately, resulting in inbound call failures for valid extensions.

Real-World Example (Case #31219138):
The client needs to route the extension range 54300–54399 to their CUCM via a hybrid SIP trunk.

However, extension 54315 is a active, live user assigned to RingCentral.

Current Behavior: The client is forced to create two separate ranges: 54300–54314 and 54316–54399. Doing this across multiple blocks quickly hits the 10-range ceiling, blocking their ability to map the rest of their corporate infrastructure.

Proposed Solutions (Product Enhancement Options)
We request Product Management and Engineering to evaluate one of the following long-term solutions:

Implement "Exclude/Exception" Logic (Highly Recommended):
Allow administrators to define a broad prefix range (e.g., 543XX) but add specific "Exclude" exceptions (e.g., Exclude: 54315) that should bypass the Cloud Connector and remain local to RC.

Adopt "Longest Match" Routing Principle:
Update the routing engine to prioritize specific endpoint assignments over broad ranges. If a broad range points to the Cloud Connector, but an individual extension is actively assigned to an RC user, the system should automatically route locally to the RC user first.

Increase / Customize the 10-Range Ceiling:
Increase the system-level limit (e.g., to 50 or 100 ranges), or introduce an account-level tier flag allowing support to lift this limit specifically for customers utilizing Hybrid SIP Trunks.

Business Justification
Enterprise customers rarely migrate thousands of users overnight; hybrid coexistence is standard for mid-to-large deployments. Restricting routing ranges to 10 limits RingCentral's compatibility with large-scale Cisco/Avaya environments, creates friction during onboarding, and directly hinders enterprise adoption.