RingSense: Reporting Issue
Currently, when a call hits an extension configured with Simultaneous Ringing (e.g., Ext 101), RingSense attributes the entire call session, AI summary, and metrics strictly to Ext 101. It does not record which user/extension physically answered the call.
Modify RingSense ingest logic to capture the answered_by SIP endpoint / user extension ID from the call session state rather than the initial target extension (Ext 101).
3
votes
Kevin
shared this idea