Currently, when agents using RingCX attempt to transfer a call to a RingEX extension via the corporate directory, the system presents a misleading "congestion" error. This message suggests a network or capacity issue when the true cause is that transfers to RingEX extensions are not supported in RingCX.

This leads to agent confusion, unnecessary troubleshooting, and increased support tickets. We request a clearer, more accurate system message such as "Unsupported transfer destination" or "Transfers to RingEX extensions are not currently supported" to replace the generic "congestion" message in these cases.