[kilo13]

will this new version work with the current 3cx phone system V9?

[VAD_Support]

Yes, it works. And deployment is much simpler now. You just need to choose the PBX version (8, 9 or 10) and the Web Server type (IIS, Abyss, Cassini). Then, every deployment setting will be automatically configured.

[Energie]

As for deployment,
I got a production server and a development server. They don't talk to each other, therefore how can I deploy the VAD Project to the production server. I cannot install VAD onto the prod. server.
Can I copy/paste the compiled folder for this project (in my dev. IIS) from the dev. to the prod?
There must be a way of doing this?

Thanks

[VAD_Support]

The VAD can be installed remotely, and then you deploy the project to any 3CX server. You don't need to move the VAD to other machine.
You may need to do some changes to the configuration to allow remote deployments. It is explained in the user's manual.

[Energie]

It doesn't work.
Like I said those two machines are not talking to each other and cannot do remote access.
On my Dev. machine I got everything for development 3CX PhoneSystem and also VAD with which I can create my VAD Project and deploy it locally.
On my Prod. machine I only have installed 3CX Phone System and I want to deploy my VAD Project developed on the dev. machine but Remote Access IS NOT Allowed. I can only copy file on that prod. machine or do some CD Installation. It is not on the same network at all.

Allowing remote access to the configuration
After you have installed 3CX VAD in a remote computer, you need to allow remote access to the configuration of 3CX Phone System:
1.
In the computer where 3CX Phone System is installed open the file 3CXPhoneSystem.ini usually located in C:\Program Files\3CX PhoneSystem\Bin.
2.
Find the setting “confNIC” and change its value to “0.0.0.0”:
confNIC=0.0.0.0
3.
Restart the service 3CX Configuration Service

[VAD_Support]

You need to be able to connect to the remote server where 3CX is installed. Check firewalls, etc. in order to make the connection possible.

There is no way to register the app without the VAD deployment process. You can copy the files, but you can not create the Digital Receptionist that points to those files... So you need to deploy the project using the VAD...

[Energie]

Thanks, I'll try to convince the IT staff

[VAD_Support]

There is a way to register the callflow programmatically, using the .NET library "3cxpscomcpp2.dll" (that's what the VAD does to register the callflow), but there is no documentation about it, so I would not recommend that. But if you have no other choices, maybe you can go with that...