iphone voicemail issues iOS 10

Ok i rebooted the phone and now it works, the other issue i noticed is when new voicemail comes in i dont get notification on the lock screen, it used to say missed call and voicemail now it just says missed call. Does anyone alse have this issue

Last Friday after I hung up with a 3rd calls from Apple's Corporate Executive Relations (representative from Tim Cook) and it didn't go anywhere. I was just wanted to give it a last try on my iPhone 7 Plus by did a "Erase All Content and Settings". Guess what? I haven't had the voicemail issue since Friday. Today is Tuesday and all the voicemail issue was gone! I'm still on 10.2.1.

I don't know why but just keep my finger cross that the problem won't come back. This doesn't make sense at all. I have replaced my phone 3 times and every time I set it up as a new iPhone and when I put my sim in there, the voicemail issue was there. No I did not change my sim on Friday.

Anyway, I will keep you posted.

I have been having the same problem! Completely frustrating. I think that I figured it out now- go to the bottom of your messages and click on "deleted messages". I had 857 messages there. Then click on "clear all" at the top of this list. After I did that, the new (and old) messages in my voicemail played fine on one touch of the play button!

I have been having this problem on an iphone SE. It does seem to be related to viz voicemail, but there is no rhyme or reason. Sometimes it works and most other times it does not. I have tried all the suggestions. At one point Verizon thought they had it fixed, but the problem reared its ugly head again. I have been on 10.2.1 and just now seeing there is an update available 10.3. REEEEALLY hoping this bug gets fixed with the new update.

In the mean time, keeping my deleted messages folder cleared seems to help. I have a tendency to accumulate messages. Now I am down to 5 in the inbox and zero in deleted.

Yes, I am experiencing the same exact issue. No voicemail notification on lock screen. Have been to apple three times. All solutions, including wiping the phone completely, seem to work temporarily and stop again after a few days. This is a new iPhone 7 which I have had for a little less than a month. Very frustrating.

Hey I am having the exact issue too with T-Mobile.

Not receiving notifications anymore when I get a voicemail. This has become a serious issue since i have no clue if a missed call has left me a voicemail.

T-mobile has said the issue is on Apple's end and they double checked all their back end systems to verify that voicemails were being properly delivered.

After working with Senior Apple Care specialist and running diagnostics for their engineers to review I was told that they are aware of this issue and it will be fixed in iOS 10.3.2.

Hopefully....

For what it's worth, I contacted my carrier (AT&T) and the rep turned on the Short Message Service (SMS) setting on his end. The problem disappeared immediately— no phone reset was required.

That said, I see that another respondent did something similar with Verizon, but the fix turned out to be only temporary. So I will wait and see if the problem comes back.

Brand new iPhone 7 ... switched to Verizon. I get voicemail but I DON'T get a notification (banner or alert.) I've checked everything I can think of. Could it be that Verizon does not send alerts?

Does anyone have any ideas about notifications?

This must be affecting all carriers. I was told that it's a bug in iOS 10.3.1 and should be fixed in the next big software release.

I am currently on tmobile and I've read about people with att also having this problem.

I totally agree with you. A phone at that cost should work, especially for something as simple as voicemail.

The good news is that Apple has released iOS 10.3.2 today so hopefully, this resolves this Voicemail bug.

Apple usually doesn't list out bug fixes for minor updates 10.3.x (as an example) but i can confirm the voicemail notification has been fixed for me so i recommend you update your phone and have someone leave you a VM as a test.

Sometimes they will list all the fixes made however those details or normally reserved for developers and not for the general public since most people won't understand the terminology.

Thanks for this. I usually wait a few days before I do an update. Having been a software engineer for 30 years we tell this riddle all the time:

Q: How do you know who the software pioneers are?

A: They are the ones with the arrows in their backs!

But this time I'll 'take a chance' and do the update early and will report back here.

I just ran the update and did a test. I did not get a VM notification that woke the lock-screen

I then powered down, tested, same result as before.

I finally did a hard reset (For iPhone 7 hold the sleep/wake switch and the lower ringer button down for 10 secs) and did another test and.... FINALLY, IT WORKED. The voice mail woke the iPhone and gave me a notification.

Well, I spoke too soon. Now the Verizon voice mail is NOT waking the iPhone. I do get the notification when I unlock the phone but I don't get a pop up and a beep when the phone is sleeping (normal state.)

I get a nice pop-up an tone on email, and on calendar events... but not VM.

Any ideas before I waste half a day on the phone with Verizon, although I doubt it is their fault since I do get a notification upon unlocking the phone with the finger print facility. (I'm wondering it that might be an issue? Or maybe a passcode? I'm trying to remember if I've gotten a VM wake-up since adding Apple Pay and passcode/finger print... and I just don't know.)

I'm not sure why that is happening now.

I just did a test myself and there was no notification for a voicemail. I tried again and finally, one came through for a new message but not the first one l tested.

It seems like the issue was partially fixed. No need to go back to Verizon, this is an iOS issue for not delivering visual voicemail properly to the phone.

Only time will tell if this is resolved. There is a new software update that is in beta, 10.3.3 that was released just after 10.3.2

Hopefully, that resolves and fixes more of these issues.