Unfortunately, you're not going to find anything in TCD or RCD about who hung up first, and I'm not seeing anything in the CVP logs to indicate one way or another... I don't know of any SIP messages that would indicate the caller or called party being the one to end the call.
One potential solution for this for future tracking:
Using the CVP post-call survey functionality, send all calls (technically all calls where the agent hung up on the caller) to a new DN and script.
In the new script, just apply a call type (perhaps something like "Agent_Hangup"), and then use a "CAP" microapp Network VRU Node to have ICM record that moment's call data into the TCDR. Follow that with a call termination.
With the above solution, you should be able to look at entries in the TCDR to see which calls did or didn't have Agent_Hangup call types on them. You can potentially setup custom reporting on this.
How would CVP know if someone is in the middle of talking? The RTP audio stream doesn't traverse the CVP server. A hangup "in the middle of a conversation" or at the end of a conversation looks exactly the same to every device involved.
If you wanted to find out if calls are ending in the middle of someone talking, the most appropriate solution would probably be call recording, together with someone listening to the recorded calls.
From the CVP logs, it can be determined which side disconnected the call first. For each call, CVP keeps track each call leg. From Inbound Gateway to CVP is INBOUND leg, rest are OUTBOUND leg. You can then look at which leg the SIP BYE message is received first.
Since you have very basic log enabled, you will not see the exact SIP message. But it can be determined by the outcome of the message. Here is the snippet of the log during the disconnect:
I'm not able to access my old voice mail messages all of a sudden. The recording says something like 'the message is currently not available'. This has never happened before in all the years I have been using this system. I have t...