Inbound Call reports not accurate Version 20.0 Update 9 (Build 670 Alpha)

[Flipper]

Investigating why calls are occasionally dropping when answered. I wanted to prove or disprove it being isolated to a single phone (Possible hook switch issue). Using inbound call reports to help determine it.

Is there an actual Cradle2Grave report. One that can shows call legs associated with a single call? I see calls come in but if transactions happen within a single second, they can be jumbled. and if you factor in Durations, the time entries are not accurate:

XXXXXX2507	Day DR (801)	Answered
XXXXXX2507	Reception, R (109)	Answered
XXXXXX2507	Incoming (800)	Redirected

[td width="48pt"]

16:52:46​

[/td]​

[td width="65pt"]

0:00:00​

[/td]​

[td width="48pt"]

0:01:01​

[/td]​

[td width="48pt"]

0:01:01​

[/td]​

[td width="48pt"]

16:53:47​

[/td]​

[td]

16:53:45​

[/td]​

[td]

0:00:02​

[/td]​

[td]

0:00:08​

[/td]​

[td]

0:00:10​

[/td]​

[td]

16:53:45​

[/td]​

[td]

0:00:00​

[/td]​

[td]

0:00:00​

[/td]​

[td]

0:00:00​

[/td]​

In this example Call come into a Digital receptionist at 16:52:47 for 1:01 which should put it at 16:53:47 But we lose two seconds when it gets introduce to the Ring group 800 ( shows 16:53:45) and this appears on the web page report as is, where 109 ( ring group member) appears higher than 800 ( ringroup).

and with some back to back testing the calls are somewhat on top of each other, so a callGUIID would be helpful to sort them out.

 

[SteveITS]

I would try a later version of u9...they are up to RC2.

 

[Kevin Attard Compagno]

If you want a full blow-by-blow of EVERYTHING that happened to a single call, it will have to be the Activity Log - you can select a specific Call ID and see all the transactions it went through. And, of course, more verbosity == more detail == more valium.

 

[AshishKushwaha]

@Flipper If your goal is to determine exactly where and why a call is dropping, having a true call journey or cradle-to-grave view can make the investigation much easier.

One challenge with standard call reports is that when multiple call events occur within the same second, it can be difficult to accurately correlate all call legs and understand the complete flow of a specific call. This becomes even more challenging when transfers, queues, ring groups, or multiple endpoints are involved.

We've addressed this in our VoIPSetu platform with the Call Journey feature, which provides a detailed, chronological view of the entire call path. It shows each call leg, routing decision, timestamps, durations, and call events in sequence, making it much easier to identify where a call was answered, transferred, disconnected, or failed. The timestamps are recorded accurately, allowing you to trace the complete lifecycle of a call without having to manually piece together multiple report entries.

For troubleshooting intermittent issues such as calls dropping after answering or verifying whether the issue is isolated to a specific phone, having that end-to-end visibility can significantly reduce the time required to identify the root cause.