Can't dial out or receive calls intermittently with 3GS and 3.1

Same issue... after updating, I sometimes try to make a call, and it says "dialing", but just sits there, doing nothing. Had to power-cycle before it would work again. Next time I'll try the Airport Mode toggle though, hopefully that will work.

I'm having the same issue reported by the OP but with a 3G phone, not a 3GS -- this morning I couldn't call out despite all signal bars, full battery, etc., and *no warning* of any kind on the display or in the phone. A little experimenting showed that I also could not receive calls: they went straight to ATT voicemail. I didn't think to check whether the voicemail was working normally. A hard reset cleared the problem but leaves me with deep distrust of the phone for this kind of "zombie" state. Since moving up to 3.1, I have had two other curious incidents: first, when trying to use the iPod program, the screen displayed "Accessory Attached" and would not move beyond that. A soft reset fixed that. Secondly, at one point when I tried to sync and charge the phone, it was mis-recognized as a "new phone" and I had to reinstall from a back-up. Something's wrong.

Yea im having the same problem as well. After i upgraded to 3.1 its been all downhill. Called iPhone and they told me to just reset the phone. I did that and about 5 hours later it started doing it again. I find myself trying to make 611 calls every 10 minutes to make sure im connected to the network. Im going to try and get a new sim tomorrow, and see if that solves the problem but im prolly going to rip a new one into apple.

Message was edited by: habib77fm

Having the same problem since I updated my iPhone last week. Does anyone have a solution?

Since I got a new SIM card from AT&T about 36 hours ago I have not had the problem.

Similar prob. iPhone 3G, OS 3.1

Symptoms:
- Full bars, 3G.
- Dialing a number, nothing happens for a long time, then "failed"
- Calling the iPhone from a landline -- endless ringing (no voice mail)

I tried all kinds of stuff, and finally did a restore from backup, then all was right.

Took a long time, I hope this never happens when I am out/traveling/away from the PC.

My initial thought was this was a local problem with my AT&T cell, but then I found this and other threads.

Do any of you having this problem have bluetooth turned on or also use a bluetooth connection to a headset or other device? This problem cropped up for me coincidentally with my getting a new stereo bluetooth headset (Motorola S9) that also has a phone mode (mic and headset). I have it paired with the phone for audio use. But it occurs to me this morning that if it were somehow to have been connected to the phone, and the phone was incorrectly left in an "off hook" state, then the two symptoms we've experienced (calls don't complete outbound; go straight to voicemail inbound) would be happening. I also am showing more phone "usage" for the current period than I can account for. Next time this happens, I'm turning bluetooth off to see what that does.

caa100 wrote:
Similar prob. iPhone 3G, OS 3.1

Symptoms:
- Full bars, 3G.
- Dialing a number, nothing happens for a long time, then "failed"
- Calling the iPhone from a landline -- endless ringing (no voice mail)

I tried all kinds of stuff, and finally did a restore from backup, then all was right.

These are actually AT&T issues; the restore you did probably just coincided with a time of lower demand on the network.

I've had other cell phones and phones with other carriers that acted the same way for the same reasons, usually at events with a lot of people (music festivals, crowded days at amusement parks, etc.)

Just because you have full signal bars (strength) doesn't mean the cell or network aren't overloaded.

Happened to me again tonight. Reboot fixed it. I've been waiting for my girlfriend to call for the past hour so we can hang out. Now I realize she probably called but couldn't get through to my zombie phone. I finally found out it was my phone when I tried to text her and it failed on full bars. This did not happen before 3.1. What the **** Apple?

I had the same issue myself... after many calls to att i finally got an apple rep on the phone. They had me RESET ALL under the config setting. and do a complete restore. After 2.5 hrs my phone continues to function now. We'll see tomorrow i guess. I am a little concerned about the battery life as it seems the battery runs down alot faster now not sure why yet thou.

If you have maximum bars and it stays there thats a sure indication for me that my iphone had crashed (atlest as far as communicating to ANYTHING). ATT has such bad service if you ever get full bars thats would be suspicious. And sure enough a reboot would fix that for a few hrs (if i was lucky). ATT was completely un-helpful trying to make me believe that rebooting my phone at least once a week was standard practice. If it was a Mickey$oft product i might have believed it.

It's definitely not at AT&T issue.
I am in Blighty on O2 and my iPhone has started doing both the 'Coma' mode trick, along with me not getting any calls and only knowing someone's called me when my voicemail pings to tell me I have a message. This has only happened since I went to V3.01.

However, I notice it happens when I'm travelling alot (so on the train) - which makes me think it's something to do with it roaming between Cell sites and it getting disconnected. Also, the Data, especially on 3G, seems to have got exceptionally slow, but that might just be O2's network 😀

I am having the same problem and it is ******* me off. Can't make or receive calls and the iphone is sitting there with 4 bars!. Have they stopped testing their firmware? You know apple some of us use our phones for business and you are beginning to make me regret moving to the iphone.