Dismiss Notice
We would like to remind you that we’re updating our login process for all 3CX forums whereby you will be able to login with the same credentials you use for the Partner or Customer Portal. Click here to read more.

Urgent Licence not valid after upgrading 3cx to 12.5

Discussion in 'CRM / Helpdesk / App Integration' started by Randika, Feb 22, 2015.

Thread Status:
Not open for further replies.
  1. Randika

    Joined:
    Jan 19, 2015
    Messages:
    22
    Likes Received:
    0
    Hi

    We have just upgraded the 3cx system from version 12 to 12.5 and VAD is now giving us the following error

    Licence could not be loaded From file
    Error licence
    licence 67 system 0


    The file exist where it should be and It was working fine before the upgrade.

    Company name - Fletchers solicitors

    Thanks
     
  2. Randika

    Joined:
    Jan 19, 2015
    Messages:
    22
    Likes Received:
    0
    Hi

    We re-validate the licence key and it is accepting the licence now. However the VAD is not still working
    properly. We have a call flow which calls a "web interaction" - because of the network port changes in v12.5 we have changed the web interaction to use a specific port:

    'http://chatterbox/getRouting2.php'

    was changed to

    'http://chatterbox:81/getRouting2.php'

    We changed the IIS to port 81 and tested before carrying out the upgrade and it was working. As soon as the web interaction is called, there is a "beep" and the call is disconnected.

    Please help

    Thanks
     
  3. VAD_Support

    VAD_Support Active Member

    Joined:
    Aug 6, 2009
    Messages:
    690
    Likes Received:
    0
    Hi there!

    In first place let me say that the VAD is not ready for 3CX v12.5 yet. We're working on the changes, it's almost ready, but the current version available will not let you deploy apps to a 3CX v12.5 in "direct mode". It will work if you create a "Deployment package", but you will not have the debugging feature available until we release the new version of the VAD.

    In any case, this doesn't seem to be the issue, as this is only related to the deployment of the app to 3CX. Once the app is deployed, it should work. So, please follow the instructions in this link to start troubleshooting your app:
    http://www.3cx.com/blog/docs/troubleshooting-vad-applications/

    If you don't find the issue, post the 3CXIvrServer.log file so we check it out.

    Kind regards.
     
Thread Status:
Not open for further replies.