Bob,
There are actually 2 parts here. The license for VDP itself is tied to the MAC address of the ethernet adapter on the machine you are working on. Depending on how many licenses you purchase you may use VDP to access more than one server. The initial purchase allows you to connect to 1 server when activated. However, you are able to deactivate a license on one server and activate it on another, you just can’t access both at the same time unless you purchase another license. So you would be able to develop on a test box and when everything worked the way you want you could unregister the test box and register on the production box and then deploy. This is assuming you have the same version of Asterisk, etc.
Now, the other thing is, that any code created in VDP is nothing more than standard asterisk dialplan code and can be written on one system and deployed on others just by taking the code generated and manually adding it to another server and modifying your contexts on that server to properly call your dialplan. So in theory you only need to use 1 license for VDP to create any code you want and then deploy it anywhere you want by manually integrating the generated code with your PBX. I have done this before and it works fine. You don’t HAVE to use VDP to deploy your finished product if you don’t want to. Last time I used Elastix it was basically just another distro of Asterisk with FreePBX and other components integrated in the system, so the above information should apply to Elastix as well. If I’m wrong I’m sure support will correct me. 🙂
Kevin
