Zoiper registers but doesn't ring

[smead]

I installed 5.0.3 on a new machine, upgraded the svn of my current 4.0.3 and applied the backup to the new one. Zoiper registers, but when I log in as agent it never rings to the phone. When I log into the asterisk -vr to view in real time I see no activity.

[williamconley]

upgraded the svn of my current 4.0.3 and applied the backup to the new one

I'm curious about what steps you took ...

1) backup on 4.0.3 server
2) copy backup file to 5.0.3 server
Everything from here is on the 5.0.3 server ...
3) extract sql file
4) drop asterisk DB
5) create asterisk DB
6) apply sql file to asterisk DB (now we have a copy of the 4.0.3 DB on the 5.0.3 server)
7) apply the "Nonexecuted" sql commands from the extras folder to the DB
* by this I mean find the db schema and search the sql files in the extras folder to find the db schema number. execute all commands after it in that file and then execute all the other files until you reach the end
8 ) admin update server IP (crucial step) with the old server ip and the new server ip
9) reboot

[smead]

Step 7 I'm not familiar with, can you explain that one a little further? Also, was only the asterisk file to be copied?

Here are the steps I took:
Old machine:
/usr/share/astguiclient/ADMIN_backup.pl --ftp-transfer
mysql -f --database=asterisk < /usr/src/astguiclient/trunk/extras/upgrade_2.4.sql
mysql -f --database=asterisk < /usr/src/astguiclient/trunk/extras/upgrade_2.6.sql
mysql -f --database=asterisk < /usr/src/astguiclient/trunk/extras/upgrade_2.8.sql
\. /usr/src/astguiclient/trunk/extras/upgrade_2.4.sq
\. /usr/src/astguiclient/trunk/extras/upgrade_2.6.sq
\. /usr/src/astguiclient/trunk/extras/upgrade_2.8.sq
perl ./install.pl
/usr/share/astguiclient/ADMIN_area_code_populate.pl --purge-table –debug
Admin -> Servers -> Modify Rebuild conf files = Y, submit
Full backup & transfer

New Machine:
cd /var/log/astguiclient/archive/
tar xvfz 192.168.2.101_ALL_2.tar.gz
cd var/log/astguiclient/archive/temp
mv 192.168.2.101* /
cd /
tar xvf 192.168.2.101_VOICEMAIL_2.tar
tar xvf 192.168.2.101_CONF_2.tar
tar xvf 192.168.2.101_BIN_2.tar
tar xvf 192.168.2.101_LINUX_2.tar
tar xvf 192.168.2.101_SOUNDS_2.tar
gunzip 192.168.2.101asterisk2.gz
mysql -e "drop database asterisk"
mysql -e "create database asterisk"
mysql asterisk < 192.168.2.101asterisk2
/usr/share/astguiclient/ADMIN_update_server_ip.pl
reboot

[williamconley]

Same general effect, but my version (as you noted) only required copying the asterisk database, everything else would be supplied by the new server.

Note that when you run install.pl, be sure you include the sample conf files (as your old server had a different asterisk version and those files will NOT work with the new server ...). And you'll need to modify the asterisk version in admin->servers and run that install script again (and pay attention during the installation ... to be very sure you get 1.8 asterisk configuration files!).

I prefer using the installer from the new machine to be sure the SVN trunk folder on that machine is the one that the install was done from. If I have need of the original files, they are there. If the old server upgraded to even ONE version different than the newly installed server's SVN (one day can make that difference ...) there could be a lot of hair-pulling six months from now when you forget that. LOL

Also be very sure the admin update ip worked properly (are all the ips in admin->servers and admin->phones showing the new server's ip?)

And as an added check, verify that the xxx-vicidial.conf files are being written on the new server. Make a change to a sip phone, an iax phone, and a carrier dialplan entry and submit them all, then verify that the new entries actually appear in the appropriate files.

[smead]

You called it. I went into the new machine and ran the install.pl again, only this time I chose yes to the sample configuration files. Then I rebuilt the config files under Admin -> Servers -> Modify. At first it didn't seem to work, but after rebooting it now connects!

Now you have me wondering... Will there be a negative effect from applying the rest of the backup to the new machine? I wasn't aware that you could merely apply the asterisk file.

I prefer using the installer from the new machine to be sure the SVN trunk folder on that machine is the one that the install was done from. If I have need of the original files, they are there. If the old server upgraded to even ONE version different than the newly installed server's SVN (one day can make that difference ...) there could be a lot of hair-pulling six months from now when you forget that. LOL

4.0.3 is considered finished, right? Wouldn't this only be applicable to a 5.0.3 > 5.0.3 migration, and not impact this scenario?

[williamconley]

The sample configuration files loaded by install.pl are matched to the asterisk version. Your old box had asterisk 1.4, your new box has asterisk 1.8. Moving the database means your asterisk version in the DB (admin->servers) is for the old server, so vicidial would issue 1.4 commands instead of 1.8 whenever it referred to this data source (php or perl scripts, either may do so). The astguiclient.conf file has an asterisk version to tell the installer which sample files to copy, and this is also available to most pl scripts and possibly to php scripts as well ... and if you brought the configuration files from the old server, this would also have 1.4 and your asterisk configuration files would be for the wrong version, causing syntax errors among other possible problems.

When porting a Vicidial install from one server to the next, you need to bring:

Client audio files (/var/spool/asterisk/monitorDONE)
Audio Store files (if you loaded any)
Any custom files (those that are not actual vicidial files, ones you created yourself) and DIFFs of any Modified files (so you can re-modify the new vicidial files)
Database

Note that if you bring the asterisk library sounds (var/lib/asterisk/sounds) from the old server to the new server, there is a chance that you will overwrite a newer file with an older file ... so you'll want to be sure to keep the newer ones by performing a bit of a shuffle during the copy process.

The same concept applies to any agi scripts (var/lib/asterisk/agi-bin).

The client audio files should have been pushed to an ftp/web location (thus no need to actually copy them, as they are now on an external web server ... but if not, an rsync will do). Same with the Audio Store but be sure to create the folder with the proper permissions since the new server will not have that old server's folder.

Custom files have to be handled carefully, to be sure they will work with the newer version. Each will have its own criteria, of course. Especially if you modified previous files and have to DIFF them. If you have not modified any files, it is much simpler to just bring the DB and let the "install.pl" handle the file dispersal after the asterisk version is correct. Oddly enough, this was already true on the new server before installation ... except for the value in the DB (which is easily changed ...). It has been observed that the the asterisk version in admin->servers may need to be FULL in asterisk 1.8 (as in something more like 1.8.x-vici instead of just 1.8, from the asterisk -R version information).

The database has to be upgraded before or after the move to match the db schema of the installed code in the final location. It also must have the proper IP address in several locations (which is where the script comes in).

In short, it is not a simple task, but it is "doable", as you're finding out. It's also quite educational.