Is it necessary to have the voice mail (basic voice mail system) component from the IP office admin suite installed for VoiceMail Pro to function correctly? I currently have an old IP406 system with VoiceMail Pro V1.4 (disks are from 2003) and the pc running the manager and voice mail is having a hardware issue so i am trying to replace it with a different pc to get us by another year or so before replacing the entire system. I have the manager installed and communicating with the IP406 but when I tried to access voice mail it hits dead air but indicates connected according to call status and the phone placing the call. I installed VM Pro and removed the basic voice mail feature so I'm not sure if there are any dependencies there. According to the documentation I have on the old cd's it indicates it should not be installed. The VM Pro service is running on the pc. The IP's are static and the same as the old pc (which is currently off line). I can plug the old pc back in and reboot the IP Office and of course everything works so I'm sure it's configuration as I am by no means an Avaya expert. I am not sure if there is a way to test connectivity back from the 406 to the voice mail pc? I am able to edit in the manager and merge the config successfully. My old system lists the Voicemail IP Address as 255.255.255.255 (In the System Index -> Voicemail tab) instead of the IP so I assume that should work in my new system (I would think the actual IP would need to be in there). The old pc is Windows 2000 Pro and the new pc is XP Pro SP3. Any tips would be appreciated.
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!
Replacing VoiceMail Pro v1.4 PC
- Thread starter davidkr
- Start date
amriddle01
Programmer
No basic VM should not be on there and isn't required, dead air usually means port blobking, make sure any firewalls are off and disable AV to test, also yes enter the VM pc address rather than broadcast 
- Thread starter
- #4
- Thread starter
- #5
The firewall has been disabled so that wasn't the problem. I went ahead and changed the IP references from 255.255... to the IP of the vm pro to see if that would make any difference. It seems to be connecting now though the old one works fine with the broadcast. When I check my vm it assumes it's my first time and wants to set up passwords and greetings. I'm going to revert to the old server and work on it after business hours tonight. I appreciate the all the help.
- Thread starter
- #6
So i cut over and there seems to be a couple of issues. It does not pick up the VM Pro user settings and prompts for vm setup from any of the phones. I attempted to try and set mine up again and it let me set the password and next prompt was to record my greeting and it gets stuck in a loop. I'm not sure what is causing this. Should I be waiting x amount of time before i attempt to access the vm after cutting over to the new server and rebooting the switches? I have been waiting a few minutes after the system boots to attempt accessing vm. Any suggestions?
- Status
Similar threads