Voicemail password problems
bluestar
Contributor - Level 1

For the past few days my phone won't accept my voicemail password.  I'm constantly informed that I've entered the incorrect password despite the fact that the password is correct.  A call to tech support resulted in their changing my password which worked twice before reverting to the incorrect password warning.  All my own attempts to reset my password online and on the phone itself have been unsuccessful.  At this point the only reliable way to enter my password and retrieve my messages is to call my cell number from a land line.  Obviously this is not always an available option.  Is anyone else experiencing this?  Any ideas about a remedy?

0 Likes
1 Solution

Correct answers
Re: Voicemail password problems
bluestar
Contributor - Level 1

I finally figured this out! Entering my voicemail password on the dialer screen (either to retrieve my messages or reset my password) was always somehow interpreted as something different than what I had actually punched in, hence the constant warning that I had entered the incorrect password.  Even though the password numbers appeared correctly on the screen. So I changed my password using my land line, dialing my cell number and following the prompts. Then I applied the password bypass procedure (described by JerryF above) and so far, so good, this workaround seems to have, for the moment at least, done the trick.

View solution in original post

0 Likes
Re: Voicemail password problems
JerryF
Specialist - Level 1

Bluevolume,

Did you try this?  From the home screen touch settings>call settings>voice mail>voicemail number so you can enter your password here.  NOTE,  you must touch voicemail number and then touch ?#+ to get to the pause comma.

Mine looks like this  *86,xxxxx where the X's would be my password. 

Then, on your home screen, touch  the ICON for Voice Mail so you get an auto connect and auto entry of your password to see if this works.  If it does not work either your password is wrong or your phone is not working correctly.

If this did not fix your problem place phone under right front tire of your car and roll over it 3 or 4 times.  Problem fixed.  JUST KIDDING

JerryF

0 Likes
Re: Voicemail password problems
bluestar
Contributor - Level 1

Thanks, Jerry.  I've tried this several times but the problem is my phone won't recognize the correct password no matter how many times or ways I've entered it.  When accessing my cell's voicemail from a land line, the password works fine.  So I may be heading for your final solution, namely sudden exposure to my car's right front tire.

0 Likes
Re: Voicemail password problems
JerryF
Specialist - Level 1

Bluestar,

For your info, when I touch the icon for Voice Mail then on the screen comes up I then touch "Call Voice Mail."  A lady's voice says, "Please enter your password and goes silent.  In about 5 or so seconds she says "You have no messages" or she says you have one message and so forth. 

NOTE: on my phone, most of the time, she only says "please enter your pass" and goes silent for a couple of seconds.  The word password is cut off and I only hear pass.

Probably won't work but try this.  Go in and delete your entire voice mail number.  I mean the *86,xxxxx

Then reboot your phone by holding the on/off button.  Then go in and re-enter the *86,xxxxx

Make sure you enter the pause properly.  Don't just use a comma

Other than this I'm out of ideas for now.

JerryF

0 Likes
Re: Voicemail password problems
bluestar
Contributor - Level 1

I finally figured this out! Entering my voicemail password on the dialer screen (either to retrieve my messages or reset my password) was always somehow interpreted as something different than what I had actually punched in, hence the constant warning that I had entered the incorrect password.  Even though the password numbers appeared correctly on the screen. So I changed my password using my land line, dialing my cell number and following the prompts. Then I applied the password bypass procedure (described by JerryF above) and so far, so good, this workaround seems to have, for the moment at least, done the trick.

0 Likes