Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations Mike Lewis on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Upgrade to 9.1.7 voicemail issue

Status
Not open for further replies.

mojoputter

Technical User
Oct 11, 2005
1,123
US
Upgraded our demo IPO to 9.1.7 it was 9.1.6 and after upgrading the VMPro to 9.1.7 I can't get voicemail to work, its on a Windows 10 box. When I'm logged into the VMPro it shows that I'm connect to the right IP address but it is showing no users. I dial *17 it say Unobtainable, press the Message button it says VM is not running. The VM service is running though. System Status is saying Voicemail Type=none. Firewall is turned off. Seems like my Windows box may be blocking something, just don't know what

Capture0_wdmtoo.png
 
Looks like you're not completely connected, unless the name of your system is IP Office. I have noticed it takes a while to get VM Pro and the IPO to talk in this version. It will come up with the IP and a few minutes later get the name and start working.

Dermis and feline can be divorced by manifold methods.*
*(Disclaimer for all advise given)--'Version Dependent'
 
I didn't notice that, but it has been about a half hour since its been connected.
 
Just talked to the tech that installed the initial demo IPO and VM, they changed the VM password and didn't let any of us know, once I got them matching the sum bee-aach came right up.
 
any vendor that would change our passwords and not tell us would no longer be our vendor
 
Of course Avaya could bring some kind of prompt up to indicate a password mismatch as oppose to just giving a confusing partial connection.....if they could be arsed :)

 
Try erasing security settings, usually does the trick.
 
Funny thing is Joe2938, we are the vendor and this issue was with our demo IPO, just an absent minded tech that created a VM password and didn't let the rest of know.
 
MoJoPutter are you sure it was a Tech?

I have recently seen an upgrade where I had to set the VM Password afterwards & I know it was not changed by the eng during the upgrade.


Do things on the cheap & it will cost you dear
 
Indeed, upgrades and downgrades corrupt the security settings just for shits and giggles these days :)

 
Hey if it all worked perfectly us techs would be out of work ;-)


Do things on the cheap & it will cost you dear
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top