DTMF Tone on IOS 13 issue

There is a new feature on IOS 13 on my iPhone X (I went into an Apple store and tested in on several phone models all using IOS 13) that shortens the DTMF tone. So when you press a number in a automated system it has a short beep instead of a long tone. Every number on a keypad has a different DTMF tone that is how automated systems recognize that you have pressed 1 for english. I have an iPhone 8 with IOS 12 and IOS 12 still has the long DTMF signals, so this is an IOS 13 issue The short beep is not an issue when I am dialing out, but is an issue when I am trying to accept collect calls through a 3rd party, automated system when I press zero to accept the call it drops it because the DMTF tone is too short for the automated system to capture it. Anyone else having this issue.?

iPhone X

Posted on Oct 19, 2019 2:07 PM

Reply
Question marked as Top-ranking reply

Posted on Jun 12, 2020 8:09 AM

FIX: switch to 4G by turning off LTE


I can say with a high level of confidence that if your having this issue it's not the iPhones fault. This is almost definitely an IVR setup/development issue.


I develop and integrate IVR systems and have had this issue personally. It's an issue with how the IVR is handling the touch tone, its not an issue with the iPhone. We had this issue on our IVR systems and resolved it, but since you can't control the IVR systems here's what you can do to get it working: turn off LTE and use 4G when calling into an IVR that doesn't recognize your DTMF's.


I was able to record the DTMF's that the IVR received from the iPhone (note: this does not mean the iPhone created this, it just means that by the time it got to our system it was represented as seen; there can be intermediary systems that affect this).


Results:

When using and iPhone on ATT LTE the touch tones look PERFECT. I mean perfect. They are to the spec, exactly. I've never seen any other touch tone come through so perfect. They were exactly the length required, were spaced out exactly as needed, etc etc. When switching to 4G the perfect touch tones degraded but looked like any other ones we get on the system. The touch tones on LTE did not work, 4G did.


In our case the touch tones were being sent to a speech recognizer that then sends back DTMFs if it detects them. Once we changed our setup to recognize OOB touch tones it worked (it didn't have to send them to the speech recognizer, the driver that we have recognized them correctly and we just changed the driver to send us the touch tones instead of relying on the speech recognizer). There are reasons for having the IVR setup this way and in some cases the fix won't be as simple as it was in ours.

124 replies

Feb 6, 2020 3:19 PM in response to tc-syr

I spoke to the Sr tech support yesterday who seemed to be confused at first. He didn’t want me to elaborate on the problem any further and cut me off from giving him further information as to where he can find others having the same problem. After almost an hour on the line he said he was sending the issue over to the engineering department and would get back to me in 1-2 days. I’ll update if he can get anywhere with the issue. Thanks

Jul 8, 2020 10:33 PM in response to Aussie Reader

I don’t see how it’s difficult to allow you to hold the button as long as you want. If you want a short touch, just touch the button quickly. If you want a longer touch press the button longer. How come it’s just one length on the iPhone? On a normal phone you can press the button as long as you want. It makes no sense to remove that option on a cellular phone.

Jul 13, 2020 5:35 AM in response to Dogcow-Moof

They do change stuff on a whim, though, don’t they? Nobody wanted 3D Touch and yet we got it. No one wanted to lose fingerprint ID and yet it’s gone. No one wanted to lose a headphone jack and yet there isn’t one. No one even asked for a redesign for iOS (which I actually love) but we still got it. They change stuff all the time, even if 99.999% of people didn’t care at all. That’s how complex development works.


Anyways - it should be an option. My experience with my new phone is significantly worse because I CANT LET PEOPLE IN MY GATE. Just - fix it Apple.

Jul 16, 2020 2:11 PM in response to Dogcow-Moof

So here is the thing. Carrier, IVR system, iPhone software be ******. It used to work on systems. Now all of a sudden it doesn’t. Rocket science or not I paid a **** fortune for this phone and I should be able to call an automated service and use it. We all paid a **** fortune for our Apple devices because we believed in a product and the quality that it professes and it historically has been. Well if I can’t make a call with my iPhone there seems to be an issue that will be calling an awful lot into question in the future. Capisce?

Aug 27, 2020 7:05 PM in response to TAGURIT02

I agree! I am also getting very tired of having problems pop up on Apple devices when iOS versions change. (The DTMF problem is not my only iPhone problem, but the way Apple is ignoring their role in this particular problem is more distressing than the technical issue.) I suspect, like you, my future question is: "Which non-Apple phone will I buy when my current iPhone becomes unusable?" (For me the answer is probably Samsung.) My next tablet will be non-Apple as well - the only reason we've stuck with Apple tablets/phones at our house for many years was to conveniently share a contact list and calendar. We can handle this with workarounds until all our Apple products get too old to use and we migrate off iOS forever.

Sep 2, 2020 6:36 PM in response to Dogcow-Moof

EEEEEEEEEEEEHHHHHHHK. WRONG.

Its absolutely Apple’s problem because my last iPhone worked fine and my Android phone opens it fine. Which means it’s either this phone or the most recent update(s).


If you don’t like people complaining because they’re having an issue that they can’t fix, don’t look through the community forums. That’s mostly what’s in these.


If the guy is upset it’s fine. He’s asking for a solution. If you don’t have an answer then kindly shut up.

Dec 13, 2020 1:14 AM in response to Danc0926

On inboard calls it's unclear where DTMF generation may be taking place; on outbound calls the phone is generating the LTE data for the equipment at the cell tower to generate the tones.


For example, on a call originating from a land line to a cell phone, I suspect it would be up to the switching equipment at the landline telephone company to create the data stream from the incoming audio.

This thread has been closed by the system or the community team. You may vote for any posts you find helpful, or search the Community for additional answers.

DTMF Tone on IOS 13 issue

Welcome to Apple Support Community
A forum where Apple customers help each other with their products. Get started with your Apple Account.