Hi Team,

I’d like to submit a feature request regarding how RingCentral handles call signaling when a terminating carrier fails to return an intercept message.

Current Behavior:
When calls are placed to numbers that are unassigned, disconnected, or otherwise unreachable, and the terminating carrier does not return a proper intercept message (e.g., “This number is not in service”), RingCentral simply passes through the signaling it receives. This may result in endless ringing or silence, causing confusion for users.

Requested Enhancement:
Implement a mechanism or fallback behavior to better handle cases where no intercept message is returned—such as:

Playing a generic message like “The number you are calling may be unreachable” after a defined timeout period.

Offering admin-configurable timeout settings or fallback behaviors when call signaling is incomplete or ambiguous.

Logging such events with clearer indicators in analytics or call logs.

Business Impact:
This would help users more clearly understand when a dialed number is inactive, reducing confusion, repeated call attempts, and potential customer support inquiries.