What might be needed is something like voice-packet across voice-network tracing/logging... sort of like, given a voice connection ID, tag packets going through

What might be needed is something like voice-packet across voice-network tracing/logging... sort of like, given a voice connection ID, tag packets going through it in a certain way, when routers or forwarding equipment en route see this tag, then send back an "I received the packet at <timestamp>" message, or something like that. If something like that already exists, then T-Mobile should know exactly where the network is failing, and why. If not, then maybe it, or something like it would be good to have... I have learned from many years of software engineering that a working system is NOT proof that the system will continue to work into the future, that good logging/tracing of all system components is a necessity not a nicety, and that if you can't tell exactly when/where/why/how your system failed within 5 minutes of looking at log files -- you need to revamp your logging system so that that becomes possible. If it takes T-Mobile more than 5 minutes to accurately diagnose the root cause of this by looking at log files, then that is proof (to me, as an Engineer) that their logging system ranges from suboptimal to non-existent, and that fixing that so that this never happens again (via fixing their logging system) -- should be their absolute first corporate priority -- after whatever is causing this is fixed. Just one man's opinion. I will now entertain disagreements and flames...