Technical Feature Request: Enhanced Handling of Direct Transfers with "Enable Voicemail on Transfer" Disabled

Request Summary:
Refactor the call routing behavior for directly transferred calls to an agent when the "Enable Voicemail on Transfer" setting is disabled. The updated logic should prevent such calls from being routed to voicemail, ensuring they adhere to the intended configuration to continue ringing until disconnected or redirected.

Current Behavior and Observations:

Configuration: The "Enable Voicemail on Transfer" setting is unchecked, indicating voicemail should not be used for transferred calls.
Expected Behavior: Calls should continue ringing or reroute according to queue or fallback settings without being sent to voicemail.
Observed Behavior:
For direct transfers, calls are not returned to the queue or handled through alternative routing.
Instead, these calls are sent to voicemail if unanswered by the recipient agent.
Root Cause Analysis: The logic for voicemail handling in direct transfer scenarios does not honor the global "Enable Voicemail on Transfer" setting, leading to an unintended fallback to voicemail.
Proposed Technical Solution:

Routing Logic Update: Modify the direct transfer handling logic to ensure that the "Enable Voicemail on Transfer" setting is applied uniformly across all transfer types, including direct transfers.
Behavioral Adjustments:
When "Enable Voicemail on Transfer" is disabled:
Calls should continue ringing until disconnected by the caller.
Optionally, a configurable timeout should allow redirection to a queue, group, or fallback destination if unanswered.
When "Enable Voicemail on Transfer" is enabled, maintain the current behavior of routing to voicemail if unanswered.
Configuration Dependency: Ensure the behavior respects existing fallback and routing configurations defined in the admin portal, such as overflow and no-answer handling settings.
Technical Benefits:

Consistency: Aligns direct transfer behavior with system-wide voicemail configuration settings.
Flexibility: Enables admins to manage call flows more effectively and reduce voicemail dependency.
Customer Satisfaction: Resolves confusion and frustration caused by perceived configuration discrepancies.
Implementation Considerations:

Backward Compatibility: Ensure that the proposed changes do not disrupt existing configurations or workflows for users relying on current behavior.
Testing Requirements: Perform extensive QA testing for various transfer scenarios (e.g., direct transfers, blind transfers, attended transfers) to confirm expected behavior across all cases.
Performance Impact: Evaluate any potential latency introduced by new routing logic, especially in high-volume environments.