dhaggar

Hi, I upgraded my IP403 from 1.3 to 2.1 (via 1.4 and 1.99) after the upgrade I installed VMPro 2.1 and it refuses to speak. When I dial *17 ... silence. The licences show as valid and the service is running.
The log created by 'interact with desktop' has an RxAbort while trying to TFTP something from the IP403. when I dial *17 the log shows access denied. Does anyone have any suggestions. Thanks

IPGuru

restart th VM Pro Service.

ALso make sure that you are using V2.1 manager to make any changes or you will get corruption of licences & strang things happening.

__________________
Universal Plan B: - When all else fails CHEAT!

PBXtech.info

 

dhaggar

Have done all that... many many times. Service is running and if I stop the service I get busy tone when I try to access VM. The key server sees the dongle, although that took some doing. PCI parallel port, had to download Sentinel drivers and configure. The switch was 1.3, I rebuilt (clean build) the Manager/VM Pro/Key Server PC and installed Manager 2.1 and then did the recommended upgrades... 1.3 to 1.4 to 1.99 to 2.1. I then installed VM Pro 2.1 It is currently a clean build of VM Pro, I have not copied the old Accounts. Greetings and WAVS directories. Next time I'm on site I'll capture the log and post it here. Thanks

sizbut

Ahh... a clean build.

Start the Voicemail Pro Client GUI and click the "Save & Make Live" icon.

When installed out of the box the VMPro doesn't have a runtime callflow to work from (root.vmp) until you do the above.

Early VMPro used to install with a default root.vmp file but people complain when that overwrote their existing root.vmp when they were upgrading.

dhaggar

Well, we got it going. RTFM. VMPro needs a password to login to the switch. I missed that. Copied the greetings and all is well. Thanks for the advice. :)