Considering it appears to be more of a widespread problem, any ideas on how to get T-Mobile's attention? Anyone have any contacts or a way to escalate to their netops or engineering team?
I thought about posting to nanog, but figured they would redirect me here. I'm not sure nanog would be the right place? Gabe On Mon, Jan 31, 2022 at 12:17 PM Carlos Alvarez <[email protected]> wrote: > A few people have reported this as a fault on our end. But I've also > heard it from friends who use T-Mobile and the complainers agree it > sometimes happens to numbers that are not ours. The complaints originate > from Los Angeles, Vegas, Phoenix, and others. So it's just more > T-Mobile/Sprint idiocy all over. > > > On Mon, Jan 31, 2022 at 12:21 PM Alex Balashov <[email protected]> > wrote: > >> I’ve experienced this as a T-Mobile customer in Georgia, at least calling >> my parents locally who are on Verizon. I get +/- 1 ringback tone and then >> dead air until they answer. I was wanting to ask the list if this is a >> “thing” or just a peculiarity of our area. >> >> > On Jan 31, 2022, at 2:05 PM, Gabriel Kuri via VoiceOps < >> [email protected]> wrote: >> > >> > I'm not sure if this has come up here before, I couldn't find anything >> specific, but I'm seeing an issue where calls originating from T-Mobile to >> other carriers are not generating ringback. The call is indeed ringing on >> the other end, but on the T-Mobile phone, it's just dead air until the >> person on the other end answers the call. It's not all calls, but it is >> reproducible to certain phone numbers and reproducible using various >> T-Mobile customers. It's not limited to a single phone T-Mobile >> number/customer. Further troubleshooting has shown that calls from other >> providers (ie AT&T, Verizon Wireless) do not have this problem to the same >> numbers the issue can be reproduced from T-Mobile. It's only calls from >> T-Mobile numbers to other phone numbers outside of T-Mobile so far. >> > >> > The no ringback issue seems to occur whether you're on wifi calling or >> on a cell tower. All of the T-Mobile users we can reproduce the issue with >> are in Southern California. Not sure if any of this matters. >> > >> > I tried to deal with customer service and opened a ticket that >> supposedly was escalated to engineering, but of course that fell on deaf >> ears and the response I got was basically "Can't reproduce, it's not our >> problem" 8-/ ... >> > >> > Any T-Mobile engineers on this list that could help or any >> recommendations on how to raise attention to this problem to someone at >> T-Mobile with a clue? >> > >> > Gabe >> > >> > >> > _______________________________________________ >> > VoiceOps mailing list >> > [email protected] >> > https://puck.nether.net/mailman/listinfo/voiceops >> >> -- >> Alex Balashov | Principal | Evariste Systems LLC >> >> Tel: +1-706-510-6800 / +1-800-250-5920 (toll-free) >> Web: http://www.evaristesys.com/, http://www.csrpswitch.com/ >> >> _______________________________________________ >> VoiceOps mailing list >> [email protected] >> https://puck.nether.net/mailman/listinfo/voiceops >> > _______________________________________________ > VoiceOps mailing list > [email protected] > https://puck.nether.net/mailman/listinfo/voiceops >
_______________________________________________ VoiceOps mailing list [email protected] https://puck.nether.net/mailman/listinfo/voiceops
