I have 2 IP Offices (10.1.3) connected via SCN. Voicemail pro is connected to Site A. Site B is centralized VM. In site B I cannot dial *17 and log into the voicemail. Ironically I can check messages using visual voicemail at site B. I can check messages for voicemail boxes for both systems when I dial *17 at site A. Site B has a ton of phantom mailboxes. They don’t want to use voicemail to email because apparently the employees checking the phantom mailboxes do not check emails on a regular basis. When I dial *17 at site B I get the voicemail login prompt. When I dial the extension (any extension at either site a or b) and enter the # sign I get a prompt immediately saying login incorrect. I didn’t even get a prompt to enter a password. Has anyone else seen this? As always, thank you in advance.
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 bkrike on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!
Can’t check messages with centralized voicemail
- Thread starter jinxs
- Start date
- Thread starter
- #3
This is an inherited customer. The customer had set up the two IP Offices with SCN and embedded voicemail on both sides. Since two embedded voicemails over SCN isn't supported with AVAYA, I advised we utilize voicemail pro and use centralized voicemail. I did upgrade both systems to 10.1. (one was from 8.1 and the other from 9.0). So to answer the question, I wouldn't know if it worked or not because they were not using centralized voicemail until yesterday.
intrigrant
Systems Engineer
Did you erase and rebuild the security setting during the upgrade?
in my experience upgrading from 9.x the security settings get corrupted which cause problems with VM Pro and other connections.
My advise is to defeult the security settings an reconfigure it, also set a password on the VM Pro connection and in the VMPro client as well.
That would be my first thing to do.
in my experience upgrading from 9.x the security settings get corrupted which cause problems with VM Pro and other connections.
My advise is to defeult the security settings an reconfigure it, also set a password on the VM Pro connection and in the VMPro client as well.
That would be my first thing to do.
- Status
