iphone 5 dialer can not successfully dial numbers after a programmed pause. The speed at which the dialer attempts to dial the remaining numbers is too slow. Does anyone else have a similar problem?

http://support.apple.com/kb/HT4515

It mentions that CDMA networks cannot hold calls. That could be your problem and also there is a feature called soft hold and hard hold make sure you are not confusing those.

Just piling on here. Apple, this needs to get fixed ASAP. Cannot do 5 to 7 conference calls a day with this bug! This is really bad that basic phone functionality bugs got through testing! ------- iPhone 5 64, Verizon, Problem exests in all speed dial situations. Calendar invite properly formatted, contact numbers, and using third party apps such as ApptDialer

As promised in my earlier post, now that I've met my Oct. 15th work deadlines, below is an update on my efforts to get this chain dialing problem fixed -- I urge anyone who hasn't given Apple feedback on this problem to do so; to do this go to:

www.apple.com/feedback

UPDATE: I had a Genius Bar appt in Apple's Manhattan Beach, CA store on 9/28/12. The Apple employee confirmed that I had entered the chain dialing sequence correctly and he could not make it work either. (It may work once or twice, but I've never been able to get chain dialing to work 3 times in a row -- it's hit or miss.)

On 9/28/12, the result of my Genius Bar appt was that an Apple case was created to refer the problem to Apple corporate. It has been 2 (nearly 3) weeks since my first Genius Bar appt on this issue and I hadn't heard anything from Apple, so I made another Genius Bar appt at the same store for today, Oct. 19.

At today's Genius Bar appt I was told there was nothing more the store could do, but wait for corporate to work on the case created on 9/28/12. It was suggested that I leave feedback, which I did today.

If you do a Google search, as I did, you will see that this problem existed in 2008! It may (or may not) be the SAME problem exactly, but I'm concerned that to get Apple to fix this we will need more feedback to Apple corporate than just a few of us. At this point, I feel it's a software problem (but I'm no expert). If it's not software and there is some "trick" to making it work, then Apple needs to reveal this work around. My hope is that with enough feedback, Apple will either fix iOS6 or provide better instrutions on how to really make chain dialing work.

Thank you for your time.

My wife's iphone 3 performs the auto dialing with pauses fine. I have tried numerous times to re enter the numbers with and without pauses and waits and still get the same result. One or two tones after first pause then nothing works.

Isn't amazing that speed dialing numbers with a cell phone is something almost all have need of yet after all this time Apple hasn't responded or fixed this serious issue for many users. Such arrogance is unbelievable.

SOLUTION that worked for me:

If I put a ";" semicolon after the phone number and before the passcode AND I put a "#" at the end, then when the phone number is called and it connects, and then I push the button to send the passcode, it SOUNDS LIKE it is dialing really slowly with two slow tones, but it actually sends the WHOLE numeric passcode and successfully connects to the teleconference.

This works reliably for me, even though it sounds like it's not working with the slow audible 2 beeps of the passcode, it actually works.

It is unacceptable the the comma does not work, but at least I can *edit* teleconference dial in info and automate it using the following pattern:

123-456-7890;9876543#

I hope that helps.

Can you please reply to this post if this works for you as well?

BillHahn wrote:

SOLUTION that worked for me:

123-456-7890;9876543#

I hope that helps.

Can you please reply to this post if this works for you as well?

That works for simple patterns, ie - ONE pause... And only if the system you are calling into is patient enough to wait during dead air long enough for the button to become active (initially it is there, but greyed out so you can't press the 9876543# button, despite needing to)...

However, this still doesn't work if you need to have several pauses... ie:

123-456-7890;*,123,456789#

My experience has been the same as HBINS. Chain dialing doesn't work.

Oh it works sometimes, but not reliably.

I'm not doing conference calling. I'm checking my landline voicemail, which needs 3 numbers: the dial-in, the landline telephone number followed by a pound sign, and my passcode followed by a pound sign. (See my earlier posts for what I've tried.)

The best I could do was connect twice in a row and the third time I tried it hung-up on me. No joy.

I'm still trying to get Apple to respond to my case (which the Genius bar submitted on 9/29/2012).

If/when I have anything new to report, I'll share with everyone here.

I was able to chain dial successfully with my iPhone 4s. When I upgraded to the iPhone 5, all of the problems other posters have already stated have occured --

I have numbers like 123-456-7890,,,987654321# -- which normally work, although it sounds like it isn't working. I will be joined into the conference and for a period of time still hear the button press tones beeping away (slowly).

And

123,456,7890,,,987654321#,,*,9876#,1# -- which doesn't work. I find when I dial this one, when it says "If you are the leader..." I quickly press 1 and even though the stupid phone is still methodically dialing (slowly) it is as if the host system doesn't "hear" them and I can then put my leader pin in and get the call going.

This is a major problem for me as I travel constantly and am often in my car when I need to join conference calls.

I do not have any solutions, just wanted to weigh in that this is a big problem.

I am in the same boat--4S worked perfectly, even after upgrading it to iOS6 and the i5 does not. I also travel constantly and have multiple conference calls per day along the same lines and it is killing me.

Noted in https://discussions.apple.com/thread/4441977 that someone on AT&T was able to use this functionality successfully but Verizon was not? I am on Verizon too--anyone know anyone on AT&T that could try it out and verifiy?

Also I found out some information from Apple Support today about this and that the engineers are not working on this and have no idea that this is an issue but they told me how to get attention for it which I posted to https://discussions.apple.com/thread/4329335.

I just installed iOS 6.01 on my Verizon iPhone 5 and chain dialing now works for me!! THANK YOU, APPLE!!!

To install the update, I went to Settings/General/Software Update and updated from version 6.0 to 6.01. It asked me to download an over-the-air installer and the usual "stuff" to say yes to accept Terms & Conditions. I note that the iOS update required me to be on a power cord, because my battery was under 50%, but otherwise, no problems installing.

So far, I've tried dialing my landline voicemail 5 times and, each and every time, the call was a a success. No more of those v--e--r--y s--l--o--w b--e--e--p--s. It just works! (Finally.)

To everyone who posted on this discussion: Thank you for sharing your comments -- very helpful. I hope the iOS update makes chain dialing work for all of you, too.

Yes 6.01 fixes it. Great.

Well if your going to complain on how poorly Apple was responding to this serious problem.... Have to thank them when they fix it... so far 6.01 fixes pause problem.... Thank you Apple if it's really fixed.... hopefully tomorrow it will continue to work.....