vicidial.org

Hi All,

I just migrated my asterisk database from GoAutoDial to ViCidial. Problem encountered was it does not shows my campaigns, users, DID's and a lot more.. but if i check it on my phpmyadmin the tables have data on it. Any idea on how to fix this? Thank you

The database schema doesn't match. You need to follow the UPGRADE instructions from the version of vicidial you are on.

As I can see here my installed VICIdial now is
VERSION: 2.14-583a
BUILD: 161226-2224

I tried this steps:

mysql
use asterisk
\. /path/from/root/extras/upgrade_2.14.sql
quit

perl ./install.pl

Admin -> Servers -> Modify Server
page and set each one to "Rebuild conf files = Y" and click submit. (skip this one since in my loaded asterisk file my account has no access to view the server details)
-is there a way to rebuild the conf files = "Y" via command line?

/usr/share/astguiclient/ADMIN_area_code_populate.pl --purge-table --debug

After running this commands.

I am not able to log in as Adminstrator in the admin.php. When I click Administration it gives me:

The requested URL was not found on this server. The link on the referring page seems to be wrong or outdated. Please inform the author of that page about the error.

If you think this is a server error, please contact the webmaster.

Error 404

xxx.xxx.x.xxx
Apache

I check on the version of my GoAutodial it was 3.3-1406088000. I migrated it to Vicidial version 2.14 which is the version on the vicibox.org.

GoAutodial is almost 3 years old at this point. You will need to run more than just the 2.14 upgrade SQL script.

Ok gotcha, btw which comes first? do I have to dump first the asterisk database before running the update on the database schema or vice versa?

mflorell wrote:GoAutodial is almost 3 years old at this point. You will need to run more than just the 2.14 upgrade SQL script.

I need to start to run the lower version of upgrade sql until i reach the 2.14 upgrade?

Yes, run it from 2.2 upwards. It shouldn't matter if you start with an early version because it will just complain about duplicate column changes and you can move on to the next one.

Vince-0 wrote:Yes, run it from 2.2 upwards. It shouldn't matter if you start with an early version because it will just complain about duplicate column changes and you can move on to the next one.

Hi Vince thank you for your response. but after running the
mysql
use asterisk
\. /path/from/root/extras/upgrade_2.14.sql. Do i need to run also perl ./install.pl ?

But i have no chance to change rebuild conf files = Y from the Modify Server because my admin it will make my admin user not able to have access to view the page.

Yes! install.pl after .sql upgrades.

You must rebuild conf files. That will be a problem.

Vince-0 wrote:Yes! install.pl after .sql upgrades.

You must rebuild conf files. That will be a problem.

Thank you for this..

In fact, you should also service vicidial restart as well as service apache restart. Best to just reboot.

Check the UPGRADE in /docs.

Hi, my previous version for vicidial is 2.9 so i ran the upgrade_2.10 2.12 and 2.14.. after running it i ran the install.pl also service vicidial restart as well as service apache restart
Reboot the server


But i received a warning when checking on the admin > system settings a ( 1484 WARNING: Code expects different schema: ?)

I always start with the same version sql upgrade.
In your case upgrade_2.9 sql .

Hope you kept a backup.

Vince-0 wrote:I always start with the same version sql upgrade.
In your case upgrade_2.9 sql .

Hope you kept a backup.

I have solved it already.. I think i have done it wrong at the first time i ran it because all the upgrade sql i have copied it to the root folder then i ran mysql > use asterisk and just use this script ./upgrade_x.x.sql

Thank you for response.

I have a question. Our current server is running on a Virtual Server with ip of 45.x.x.x and running on GoAutoDial. Now i have migrated it to our physical server with ip of 192.x.x.x. So what i did is i updated the server ip and on mysql > asterisk I updated the ip of the conferences,vicidial_conferences,servers and phones. and also manually update the server of the carrier.

What else do i have to do to be able to dial with my new server? When dialing I'm getting error of
DIAL ALERT:

Call Rejected: CHANUNAVAIL
Cause: 20 - Subscriber absent.

the ip i am using is now already whitelisted on our carrier

No no no,

There is a (ADMIN_server_update_IP ?) script in /usr/share/astguiclient .
You will most likely have to input your old IP and then the new one.

Vince-0 wrote:No no no,

There is a (ADMIN_server_update_IP ?) script in /usr/share/astguiclient .
You will most likely have to input your old IP and then the new one.

Yes also do that after updating the ip's of the phones, conferences and servers..

How about the issue when making a test call. an outbound call.

Different problem,

Thanks all for the help.. It seems it's working now.. have to do more testing before deploying it on production..