🔧 Feature Title:
Enable Remote Visibility of Locally Configured Call Forwarding on Physical Desk Phones

📋 Current Behavior:
Currently, call forwarding settings configured directly on desk phones (e.g., Poly Edge E320) are not visible in the RingCentral Admin Portal or app. These settings are stored locally on the phone and are not synced with the platform.

⚠️ Issue Description:
Customers and administrators have no visibility into locally applied call forwarding settings on physical phones. This results in confusion and troubleshooting delays when call routing does not behave as expected, but no forwarding is seen in the user’s extension profile.

🎯 Requested Behavior:
Provide a way for system administrators to remotely view and manage any call forwarding configurations made directly on supported desk phones, either via the RingCentral Admin Portal or through API integration with device management.

👥 Customer Use Case:
An end user had unintentionally enabled call forwarding to their mobile number on their Poly Edge E320. The administrator could not detect this through the Admin Portal and had to rely on manual device inspection by the user. If administrators had visibility of this setting, it would streamline support and reduce issue resolution times.

🔐 Security/Permissions Impact:
Access to device-level call forwarding visibility should be restricted to Admin roles to maintain privacy and control.

📎 Related Case:
Case #28163802

🕒 Priority:
Medium – Impacts admin efficiency and user support experience.