Thousands of patients with T-Mobile unable to use our IVR (DTMF tones not transmitting, requires multiple calls)
I work for medical clinic with about 600 users. For almost 2 years now, we have been having issues where wireless callers from T-Mobile/Mint/Metro PCS and all of their MVNOs, have the inability to get through our IVR system. They will push options in our main auto attendant IVR and it will not register anything they press. Sometimes it will take multiple calls before finally, they are able to transmit tones. I am able to duplicate this issue on my T-Mobile test line on my iphone (signed up for the 90 day evaluation) as well as a test android phone. Wifi calling disabled, strong LTE or 5G signal. Issue happens all over our City, and some of the surrounding cities. Both phones (iphone 14 Pro Max and T-Mobile Revl and OnePlus N200, all the latest ios and carrier updates). Our support vendor for our phone system and our SIP carrier keep telling us the issue is on T-Mobile's side. I had worked with T-Mobile support for several weeks, and they tried to blame the issue on iPhone, stating that ever since iOS 13, the DTMF Long tones are no longer a thing, and to verify that our system can handle short tones. I don't buy the DTMF thing, because why would Verizon and AT&T iphones not have any issues with our IVR. Plus, I can duplicate the same issue, multiple times, on an Android phone. They have now proceeded to kick the can down the road and told me to have our patients reach directly out to their support. Ok, we have done that, for 8+ months, and it got us nowhere, except 100s of angry clients with T-Mobile. I know at least 50 of our patients have switched carriers because of this issue. I am literally at my wits end with this issue. Does anyone else out there have a similar experience or issue? If you did and solved it, please tell me what you did so we can try it. We have tried the whole Network reset, Wifi calling on and off, etc. I have made about 200 test calls in the past 72 hours, on both my T-Mobile phone, and another carrier. The other carrier, all 200 calls transmit DTMF without issue, the T-Mobile phones, its absolutely hit and miss.
samsung s21 ultra 5g ultra slow
About a week and a half ago I started noticing my phone going INSANELY slow. Like, 21 minutes into watching a 5 minute and 37 second YouTube video and I'm only 1 minute and 12 seconds in slow. Can't access anything on data, can't download anything on wifi. And it's not a location issue cuz none of my other devices are affected. My partners phone through t-mobile works fine. Every other device that uses wifi is fine. It's just this phone I've tried everything. Restarting the phone. Having only one app open at a time. Resetting all settings. Factory reset (that took me well over 4 hours cuz it's soooo slow) Ive included pics of an update ive been trying to download for hours, 0.36 mb/s with full mobile coverage and 0.00 mb/s with full wifi coverage. Before this issue that would have downloaded in less than a minute. I'm at my wits end idk what else to do?
data is active, but slow as all hell
I use an android phone and For the past 2 to 3 days, my data has been so slow that I can't access downloads on certain apps. I don't what it is, but its getting annoying. Usually, I would just chalk it up to t mobile tower troubles. However, I've had a history of my data coverage being so trashy. And it's because of one thing that still don't freaking understand and that: the carrier hub application. Someone explain to what the hell it does and why does my service always get worse when is have to mess for an update or permission or whatever. I've been dealing with this carrier hub bull crap for a few good years using t mobile and it still gets on my nerves.Samsung Galaxy S21 Ultra 5G
I have this phone IMEI: 353388682198652. I was told this device does not ask for an unlocking code when an incompatible sim card is inserted, and instead requires unlocking via a Device Unlock App. I am in Belize. Samsung Galaxy S21 Ultra 5G is actually locked to Sprint USASamsung Galaxy S21 Ultra 5G
I have this phone IMEI: 353388682198652. I was told this device does not ask for an unlocking code when an incompatible sim card is inserted, and instead requires unlocking via a Device Unlock App. I am in Belize. Samsung Galaxy S21 Ultra 5G is actually locked to Sprint USA
Phone is intermittently switching to "Emergency Calls Only"
I had a Samsung Galaxy S20+. It had worked properly until a month or two ago, when I noticed the phone would intermittently leave the T-Mobile network and only allow Emergency Calls. I was unable to receive or make calls and texts during those periods, which could last for 20-30 minutes at a time. Since I was due for an upgrade, I assumed that switching to a new phone would resolve the issue. I got a Galaxy Z Flip5. I migrated my data over from the old phone using Smart Switch, and noticed that the problem was occurring on my new phone. So I backed up everything on Samsung Cloud, performed a factory reset on the new phone, and restored the data (minus the settings, since I thought there might be a rogue setting causing this). This did not resolve the issue. I did another factory reset and deleted the e-sim, in the event that something in the SIM card was causing the issue. I replaced it with a physical SIM. No change. After the last factory reset, I restored everything from Samsung Cloud and then reset the mobile network settings. No change. I verified that there were no system updates available. I disabled 2G on the phone, as the T-Mobile reps suggested there could be a conflict between 5G and 2G. No change. In the access point names, I've verified that the APN is correct (fast.t-mobile.com - I'm in the US). In the Network Operators section, it is set to Select Automatically. I turned that off and attempted to register on T-Mobile, which works. But after a while the phone goes back to only allowing emergency calls. This happens everywhere I go, so it doesn't appear to be signal issue. My wife is not experiencing this issue with her phone, so it appears to be restricted to my phone/account in some way. I'm at a loss as to how to proceed.WHY is 5G connectivity so (Trash) unreliable on the T-Mobile network including their MVNO’s?!
I was making some updates to my device layouts and when testing the PTN associated with my tablet from another number, I noticed the text did not arrive. I double checked the number. I remembered then that I had 5G enabled on the device since it is primarily used for data only and tried an additional text. Still not delivered. The device had been "idle" on Wi-Fi, so the connection essentially "timed out" unbeknownst to me. I restarted the tablet, and the texts sent several minutes before came right through. I bust out laughing in frustration… Note: After X amount of time if your "data connection"(uplink to network) is not "refreshed"(Restart device, Toggle Airplane Mode, Place a Call, Use data on your end) then that communication sent to your device (voice/SMS/MMS/voicemail/data) will NOT be delivered to your device. I sent texts and left voicemails that never made there way to my device. Do I need to spell out the disaster this is - and the sad part is most people are not tech savvy, corporate shills, and/or iPhone users and have no idea this is happening. (The audacity to try and raise prices…) This issue has persisted for several years at this point; I first noticed the problems around the ~ S20 FE. Since this time a plethora of videos and posts both knowingly and unknowingly have been shared regarding the matter. The Issue: If you have 5G enabled on any device you will intermittently loose connection with the network/tower by way of transmission with voice/SMS/MMS/voicemail/data not being delivered to your device; often times unbeknownst to you(signal will show connected - other times SOS emergency calls only may appear). *This is not attributed to known technical limitations that have existed since cellular technology was introduced(signal interference, building materials, congestion, location, time of year, phone case, user error, device software/hardware(known bugs), etcetera) *These issues NEVER happened with prior generations of cellular technology. I never had to guess whether or not my device was connected, the signal software could be trusted, moreover, I never had to worry about the receipt of voice/SMS/MMS/Voicemail being delivered to my device, even when "off network"(roaming) a voicemail still would delver once the device reconnected to the network. *iPhone users mostly communicate with other iPhone users(blue bubble). iMessage works on a data connection (Wi-Fi or Mobile data). iPhone is not using SMS/MMS the same way Android users do. Cellphone users spend less time talking (voice) and more time texting(iMessage/Facetime; SMS/MMS; Other apps). "I called you" "I texted you" "911" "I called to offer you the job" "The hospital called so and so has been hurt" "I left you a voicemail before I took my last breath" just a few scenarios you won't even know took place because A) it never made it to your device B) people will assume you didn't answer/respond. Ignoring them, etcetera. I saw similar complaints on other carriers, so I don't believe it to be specific to T-Mobile's network, however, I haven't researched enough to know if it's a technology issue with 5G in general or specific to Magenta. Point being, it should not be happening. The current fix I have found for reliable voice/SMS/MMS/voicemail is to disable 5G on my cellular phones, and only use 5G on my data specific devices since getting SMS/MMS on them isn't my main use for them. I just thought it was funny to see the issue is STILL present. I've ran tests in multiple locations over different time periods. This isn't a SIM card issue. Unsure if it is hardware related at the SOC level/5G but again, the same SOC does not have these issues with 5G turned off. Somehow the devices are losing connection/timing out/idle when 5G is enabled causing the lack of transmission of voice/SMS/MMS/voicemails and needs to "reconnects" before these transmissions are delivered to your device. The issue is if you are unaware of this, you don't know it is happening. Don't let people gaslight you. I raised this issue internally directly as an internal customer, and externally as an external customer - Management is aware. Engineers are aware. I'm sure there are more technical jargon to explain why the packets are not being sent to the device and why it only sends with a connection "reboot".
