vicidial.org

Hello Forum!

I'd like to build a test system from my production Vicidial system so I can plan and learn more about the technology. I am no master at the Linux OS, but understand it enough to be dangerous!

The Vicidial server interfaces to my Trixbox 2.6.2 phone system using Vitelity VOIP lines on a single server that handles the calls.

I had a pro build my Vicidialer and has the following specs:

SOFTWARE:

Vicidial ISO Version: 1.2
Version: 2.0.4-146
Build: 80428-0413
(Had a handful modifications done)

HARDWARE:

Kernel Version: 2.6.18-92.el5.vnow (SMP)
Distro Name: CentOS release 5 (Final)
Hardware: Dell PowerEdge 2850
Processors: 4
Model: Intel Xeon CPU 3.20GHz
Drives: 72GB * 4 (RAID5)

I just did a basic install from the ISO on my test system and configured the network card.

My idea is to interface my test system to the Trixbox (like what was done for the production system).

Here is my question:

What directories/files should be copied/restored from the production system to the test platform? Any idea what files I would modify on the Trixbox?

Any thoughts are greatly appreciated!

I'm assuming Trixbox and VicidialNOW are on two separate servers.

Easiest way to do this is make a backup of you production Vicidial. There's a native Vici backup script called:

/usr/share/astguiclient/ADMIN_backup.pl

Run it with the "-h" flag to get more options.

The backup is save in:

/var/log/astguiclient/archive

You can then just copy the backup data to your test system and restore it there. Voila! You can then play around with it with live data.

Was able to back up easily!

I looked at the help, but there does not appear to be a RESTORE switch.

Is there a script out there that will allow for a restore?

I went to the directory and saw the file. Replaced the files from the tar in the test system. Worked fine.

I also found the SQL script to update the database. Is this something that can be run under a mysql prompt? Any recommendation on how I should run it?

the mysql backups can be "applied" like this (assuming you replace XXXX.sql with the sql backup file):

Code: Select all

mysql asterisk -p < /PATH/TO/XXXX.sql

It is not a requirement to name the database asterisk, but you should probably leave it named that until you are more familiar with the system.

Hi William; Thanks for the reply.

Before attempting running any scripts, I logged into mysql from the Linux command prompt:

Code: Select all

mysql -u root -p vicidialnow

I moved the backup SQL file to the test server and renamed the file to update.sql (just to make it a little shorter) and tried to run as instructed. But it did not work. Here's what I got:

Code: Select all

mysql> \. /var/log/astguiclient/archive/update.sql
ERROR:
Failed to open file '/var/log/astguiclient/archive/update.sql', error: 2
mysql>


However, when I ran:

Code: Select all

SOURCE /var/log/astguiclient/archive/update.sql;


it worked like a charm.

NOTE: Before you run the script, select the database by using:

Code: Select all

use asterisk;


If not, the SQL file will not be applied to the database.

Thanks for all your help!

LOL

my version was meant to be run at the linux command line, not from withing mysql.

OK. I never thought to try from regular prompt! Please forgive me; I'm pretty good with Windows; Not so much with Linux.

So here's where I'm at now:

I first update the conference IP's in the new Vicidial server per this posting:


http://www.eflo.net/VICIDIALforum/viewtopic.php?p=26299&sid=1589562f687f3cf578150e7579d6e887

I also changed the IP of the phone extension. (Remember: I'm running a separate Trixbox system).

I know that I need to do an IAX2 registration with the Trixbox. So I proceed to modify the 'iax_custom.conf' file on the Trixbox. Here is what my file currently looks like (where 192.168.50.112 is the new system) and works fine with my production install of Vicidial:

Code: Select all

register => trixbox:test@192.168.50.112:4569
register => trixbox:test@192.168.50.207:4569

[vicidial]
type=friend
context=default
auth=plaintext
host=dynamic
permit=0.0.0.0/0.0.0.0
secret=test
disallow=all
allow=ulaw
qualify=yes

[vici]
type=friend
context=default
auth=plaintext
host=dynamic
permit=0.0.0.0/0.0.0.0
secret=test
disallow=all
allow=ulaw
qualify=yes


However, looking at the PBX Status on the Trixbox, here is what I see:

IAX2 Registry
Host dnsmgr Username Perceived Refresh State
192.168.50.207:4569 N trixbox 192.168.50.201:4569 60 Registered
192.168.50.112:4569 N trixbox 60 Rejected

As you will notice, the Trixbox is Rejecting the registration from the new server (192.168.50.112). I've tried to locate any other files and played with the secret...No Go. Any ideas if I need to modify any other files on the Trixbox (or Vicidial?) to get it working?

trixbox is just freepbx. so let's talk about how you set up vicidial and freepbx to "use" each other's services.

from OUTSIDE the box, BOTH are "asterisk". And the FreePBX and Vicidial software were designed to modify the configuration files for you when you use the GUI to create trunks and extensions.

so ... to create a "trunk" for vicidial to use ... you merely create an "extension" in FreePBX. This is the same relationship you have with your VOIP Providers. You are (to them) an extension on their system. They are (to you) a trunk.

All handled from within the GUI on each system.

Once I made sure the trunks were set up on the Trixbox (see my previous post), I then needed to make the changes on the Vicidial side.

What I had to do was the following:

1) Manually change the IP of the test server on a set of files under

/etc/asterisk

modify

iax.conf

make sure there is a line to register the current server to the Trixbox. Should look like

Code: Select all

register => vici:test@192.168.50.201:4569

where the IP address is for the Trixbox. (Note the registration username & password matches up to what was in the 'iax_custom.conf' file on the Trixbox.)

and

extensions-vicidial.conf

make sure there is a line to register the extensions of the Vicidial server to the Trixbox.
Should look like

Code: Select all

exten => _192*168*050*112*.,1,Goto(default,${EXTEN:16},1)

Where the IP address (with the asterisks) is the address of the local Vicidial server.

After this step, reboot the Tribox. After it comes back up, go to the Admin side of the Trixbox and then click PBX>PBX Status. Scroll down to the IAX2 Registry & IAX2 Peers sections and you should see the new server is registered.

(Gardo helped me with the rest!)

Then go to:

/etc/astguiclient

and verify the IP address of the local server is also updated.

After all the IP's are updated, run:

Code: Select all

server_update_ip

at the prompt.

All should work just fine!

When starting from a fresh rebuild, you will need to change the IP of the base install. To do so, perform the following:

1) Do a

Code: Select all

vi ifcfg-eth0

at the root command prompt. The file is located at:

/etc/sysconfig/network-scripts/ifcfg-eth0


2) Do a

Code: Select all

service network restart

at the root command prompt.

You may need to change your gateway as well.