Build 3659

[SWSDEV]

I finally instaleld build 3659, but it installed the old version still. Where is a working link for the newest build of the VAD?

 

[VAD_Support]

Yes, you're right. I will let you know when the link is fixed. Sorry about this.

 

[VAD_Support]

Now the installer has been updated. The new MSI file is 8Mb aproximately.
Thanks for reporting the problem!

 

[Energie]

Problem with deployment.
Just upgrade from the previous release and cannot deploy anymore?
Could not connect to the deployment URI. Verify that 3CX Phone System has the 3CX Voice Application Designer Server Components installed. Also verify the PbeploymentUri property for the project.
The remote server returned an error: (404) Not Found.

What should I do now since it was working before?

 

[VAD_Support]

Hi,

Please, check the Server type property. You need to select IIS or Abyss. Maybe the default type is not what you're using.

Can you give it a try and let me know?

Thanks,

 

[Energie]

I Select IIS which is what I run.
My OS is Windows Server 2008 R2 Foundation
Installed successfully 3CX Phone System with IIS as web server
Installed succesfully the previous VAD and now the new build 3659
Deployement was fine with previous rbuild and not anymore with this build

Try to deploy the Sample (SimpleDialer)
PbxConfigurationPort 5485
PbxServer localhost
PbxWebServerType IIS

 

[VAD_Support]

Are you using 3CX v9? Or the v10 beta1?

 

[Energie]

V9.
Can I Download v10 if if yes where and is it reliable for production yet?

 

[VAD_Support]

No, v10 is in beta yet, not suggested for production right now.
I will test your scenario and let you know.

 

[Energie]

Thank you to let me know asap since I just got my VAD license and have to show my client a solid demo also using the external Code Execution model using dotnet library.
In that regard, should I use framework 2 or 4. I would preffer 4 but I think that only 2 is supported for the IVR web deployment?

 

[VAD_Support]

Actually, the VAD outputs ASP.NET source code, so it can be compiled to .NET 2.0 or .NET 4.0 seamlessly. If using .NET 4.0, you need to configure IIS accordingly.

 

[VAD_Support]

Hi,

I was reading again the error message, and it does not belong to the latest version. The message refers to "PbeploymentUri property", and that message has been changed, since that property does not exist any more. Can you check the installed version from the About box?

Also, can you check into the file C:\Program Files\3CX PhoneSystem\Data\Ivr\Cfg\3CXIvr.cfg the value of "client.vxmlURL". Is it "http://localhost/ivr/ivr_start.aspx"?

Thanks,

 

[Energie]

As for IIS and Application Pool for Framework 4 - It does not seems to be really good either with Classic or Integrated mode.

As for the Version I do run a brand new install of VAD build 3659 and yes it is the message I got
My Settings for deployment:
Try to deploy the Sample (SimpleDialer)
PbxConfigurationPort 5485
PbxServer localhost
PbxWebServerType IIS



client.vxmlURL VXIString http://localhost:5484/ivr_start.aspx
I try with this http://localhost/ivr/ivr_start.aspx but it is the same

 

[VAD_Support]

Hi,

I have been investigating this, and this is probably a bug in the VAD working with IIS. We're going to fix it asap. We need to release a new VAD version that works with v10 very soon, so this fix will be included then.

Can you please try the previous version until this is fixed? The new version should be available during next week.

Sorry about the inconvenience.

Thanks,

 

[Energie]

Would you be able to send me a link of the previous build, I override it with this one.
Also when you say "The new version should be available during next week." are you also referring to the 3CX Phone System V10 or only VAD.

"

 

[VAD_Support]

Please, send me your e-mail in a private message and I will send you the previous version installer.
Next week we'll release a new VAD version that works with 3CX v10, as current version has some known issues. In that new VAD version we'll fix this problem too.

 

[VAD_Support]

Hi,

A new build has been released, containing a fix for this problem.

Regards,