Inconsistency in the duration of the conversation between the data from the billing of the opsos and the testimony of the android?

Question

Android

Help me figure out the story that happened last month with my sister and her android phone with an MTS SIM card.
We are talking about the phone LG Optimus One - the latest official firmware, non-rooted, android 2.3.
Studying the details (yes, once a month I do this for all relatives) I came across a 15-minute call to another area. I wrote to my sister about the fact that MTS has the appropriate options that should be connected if she is going to call to another region. I received a surprised answer: "calls with such a duration were not made." Yes, there was a call in another area to the phone number of a company (terrible, terrible company, why was it only recommended) that installs windows and its duration was about a minute.
Please double-check the duration of the conversation in the history of the phone - 67 seconds.
A week later, I solve the problem radically, I put CM7 on the phone with a more recent version of android.
But a couple of days ago, still decided to figure out what could happen. I looked inside the backup from the android (which was made before installing the new firmware) - I did not learn anything new.
Screenshot of the file from the backup and lines from the detail.
I am considering two options - an MTS error or an android error.
He advised me to call the MTS help desk (it’s still fun: it turns out that in order to communicate with the operators in the voice menu, you need to select the item about the emergency) and ask what can be done with the problem described above. At the very least, I expected them to file a claim and do some sort of investigation. But the answer turned out to be different: since the details say that the duration of the call was 15 minutes, then the duration of the call was 15 minutes. And there's nothing to be done.
Well, now I'm in the process of exploring the second option. I looked through the forums, the android bug tracker, perverted with requests to Google. There are all sorts of problems with time zones, with the time of the call, with the inability to see the current duration of the call. But there are no problems with taking into account the duration of the call (I did not look at the messages about the old versions of the android).
The following options immediately come to mind:
The phone at the time of the conversation could synchronize the system time, because of which what happened happened. But as far as common sense tells me, in android this situation should be handled correctly.
And another option with the fact that the call was accidentally put on hold, instead of dropping the call. And as a result of this, the wrong time was written to the log. A kind of bug in the caller. This option is still under study. There is another problem in that a new version of android is now installed.
The plans are to compare the data from the log with the details, to look for other anomalies.
You can also call the number you called; find out what they have in their logs. But that would be an odd call.
In defense of MTS - immediately after discovering the problem, I tried to find messages on the forums about similar problems. Nothing.
I want to hear the opinion of the habrasocommunity, where is the dog buried here? In which direction to dig?

Answer 1

Do you know what time you called? Logs are logs, and any sane person can distinguish one minute from 15 =)

Answer 2

I remember in the subscriber's memo, which was attached to the SIM card many, many years ago, when I connected, there was a clause, something like that, they say billing is done according to the duration of the connection from the switching node, and this data, sometimes, can differ significantly from cell phone readings.
However, alas, now I can’t find the proof, no matter how old I am, I couldn’t.
Still, I think you should hardly appeal to the readings of the device, even if the device is flawless.

Answer 3

Guys, on the switchboard, the duration of the call can be LESS than on the air, but not more. If the session is alive on the switch, but it has already died on the air, this is a malfunction in the operator's network, and it is very clearly visible when comparing two logs: the switch and the BS