vMCD questions

[ucx]

We are looking at moving to a virtual MCD solution here at the office from a 3300 ICP and a few questions have been raised from management. I've looked for answers but haven't found anything that references it, I wonder if you could help me.
The questions are:

• Can we backup our current system and restore to the virtual system, thereby keeping all our users/devices, groups and routing, or will it be necessary to enter it all from scratch?
• Can we run the system up on a test server, then move to a production server without affecting the licensing?
• If we use version 4.1 (the version on the virtual license file in the AMC), can we upgrade to 4.2 or 5.0 (when it comes out) without re-building/re-licensing?

Many thanks

[brantn]

1.) Yes it acts just like another controller so you can move your data you might have to tweek it some as there are certain forms that no longer exist such as voicemail.

2.) Yes however you must be careful in the move as the licensing goes off the MAC of the original NIC you can copy this to the new server once in production if for some reason it is messed up you can always have the app record cleared and resync the new server.

3.) Yes you can upgrade just like any other controller within certain limitations.

[ucx]

Awesome, thanks for the info!

[martyn]

Just remember though that you will lose voice mail when you go virtual, so you will need to look at going to NuPoint at the same time (if anyone has an easy way to shift the recordings across from embedded to NuPoint I'd love to hear).

[ucx]

Yes, that was one of management's issues as well, but we were able to get them to arrange Nupoint licenses (et al.) for us. The plan is to set it up on a test server with our current 3300 running as normal, and then over a frantic weekend swap them all over.

[wiseguy]

Couple of extra pointers: Software version 5.0 will have Embedded Voice Mail support for vMCD. If you are planning to change from CX/CXI or MXe to vMCD then best to remove all TDM hardware and Software before backup is made. If your current system is Licensed pre 4.1 then make sure that your vMCD is also started with a base packet at 4.0
Bear in mind you might want to swap licences over from on to the other. The License challenge is gone at 5.0 aswel as you can setup a license manager over multiple systems.
PS. vMCD is great! 

[martyn]

Couple of extra pointers: Software version 5.0 will have Embedded Voice Mail support for vMCD.

Hmm thanks for the info, didn't know about that! It could well just help us with an issue that we are trying to find a way to overcome.