Problem Statement
Account administrators currently have no self-service method within the Admin Portal or Analytics to determine which party disconnected a call or why. When users report suspected "call drops," admins must open support tickets to have Tier 2 support pull backend session logs (Sonus-Disconnect-Initiator / Sonus-Call-Disconnect-Reason). In many cases, these inquiries turn out to be normal hangups rather than technical failures, resulting in unnecessary ticket volume and delayed answers for admins.

Proposed Feature
Expose call termination telemetry directly within the Admin Portal Call Logs and Analytics detailed view:
1. Disconnect Initiator: A field indicating who ended the call (e.g., Calling Party, Called Party, or System/Network).
2. Disconnect Reason: High-level human-readable disconnect reason codes (e.g., Normal Clearing, User Busy, Network Timeout).

Business Impact
Self-Service Troubleshooting: Empowers admins to independently verify whether a reported call drop was an intentional user hangup or a genuine network/platform issue.

Support Ticket Reduction: Significantly reduces incoming support cases related to call drop investigations.

Faster Resolution: Provides immediate answers for account admins without waiting for backend log extraction.