Vicidial, Asterisk and DB+Web Separate Servers...Howto?...

[PaulScott]

Please guys,

I need some advice on how to achieve a ViciDial Install on 3 or 2 separated servers.

How could I install Vicidial to use a DB and/or Asterisk on different server?..

I cannot find any post about this.

Thank you all.

[mflorell]

I think there are at least 100 posts about this. but first, the manditory questions:

- number of agents?
- type and percentage of call handling?(Inbound, outbound, blended)
- lines-to-agent ratio?
- type of trunks(telco lines)
- If SIP, what codec?
- will you be recording all calls?

[PaulScott]

Matt,

I will like to use the new version of vicidial 2.2.0, on our production server.

We have a DELL DUAL QUAD XENON (eight cores) with 4 GB RAM as primary server and a IBM CORE 2 DUO 2.5 Ghz with 1 GB RAM as a secondary server.

Our idea is to use both servers to improve stability and performance as much as possible.

Our

- number of agents? ------> 50 agents using 50 linux workstations with ekiga (softphones)

- type and percentage of call handling?(Inbound, outbound, blended) ---> 80 % outbound / 20% inbound / blended

- lines-to-agent ratio? --- 30 lines for 50 agents

- type of trunks(telco lines) --- 1 x E1 (30 LINES) optional plus, another E1 x 30 LINES to use as PBX.

- If SIP, what codec? ULAW

- will you be recording all calls? All calls will be recorded, on MP3 if possible or GSM instead.

I will be very grateful to receive your advise.

Best Regards,

[mflorell]

50 agents, 30 lines?

Do you have any plans for expanding?

[PaulScott]

Yes Matt,

We will enable the second E1 with a 30 lines plus, once the 50 agents start working full shift.

So final count will be 60 lines to 50 agents.

[mflorell]

if this is the biggest you will be you could use the IBM server as the DB/web server and the 8-core machine as the ViciDial server, you might want to add some more RAM to the IBM server though.

The ideal solution would be to have 3 of the IBM servers and use two of them for ViciDial.

[PaulScott]

Ok Matt,

I will follow your advise, but do you have any guide or wiki on how to implement ViciDial 2.2.0 to work on a different web server?... I mind How do you connect the Asterisk Vicidial and Web Vicidial?....

Thanks...

[mflorell]

just run the install.pl on both servers and only enable Apache and MySQL on the DB/web server machine. Just make sure you point both to use the DB server.

[spaquet]

My experience: it works !

We splitted on 3 machines (1 for DB, one for "GUI" and the last one for Asterisk support).

We did exactly as said by Matt and things are OK.

Try to keep enough bandwidth for "signaling and exchange between servers" otherwise you'll be facing some strange behavior.

[PaulScott]

All right,

I'm working on the servers setup, from scratch, on CentOS 5.4

Once I have every thing up and running, I will share details here.

Thank you Matt.

Cheers!!

[mflorell]

One piece of advice

AVOID CENTOS

Just about any other distro is preferable in our experience. We like Ubuntu(debian) and OpenSuSE.

[williamconley]

One piece of advice

AVOID CENTOS

Just about any other distro is preferable in our experience. We like Ubuntu(debian) and OpenSuSE.

no joke. the best guy at it to date is ... VicidialNOW and he's already shared his experience here (in the form of an .iso). Which is BEAUTIFUL because to date he is the ONLY one who has succeeded in the installation.

if you want a short cut (and are serious about "from scratch", your best bet is to pick apart vicidialNOW's installation CD and see how it's done.

Post THAT here as a scratch install and you'll have some friends. But don't think it'll be easy to get it right with today's CentOS without some Serious Work.

[pslocom]

One piece of advice

AVOID CENTOS

Just about any other distro is preferable in our experience. We like Ubuntu(debian) and OpenSuSE.

I don't see why he would need to avoid CentOS. We currently have a cluster of 4 Asterisk Boxes, 1 DB Box, and 2 Apache Boxes, all of which are running CentOS 5.4 64Bit. We are running 1.4.17 on 3 Asterisk Boxes, and 1.4.30 on the newest one, and Vicidial 2.2.0-224. Aside from some minor hiccups everything seems to be running pretty good. All I did was follow some of the instructions on the scratch install and improvise in some spots (Using YUM to install some pre-requisites for easy updating) and all is well.

Can someone please explain why CentOS is to be avoided?

[mflorell]

I think I've gone over this about 100 times, by why not one more...

- CentOS kernel modules are optimized for desktop settings by default, even on the CentOS server installer.
- the non-standard libraries and library naming scheme
- the backporting of current kernel modules to work with older kernels so CentOS/Redhat can maintain a "stable" kernel
- the non-standard bin utils that CentOS uses
- the annoying recurring perl bugs present only in Centos/redhat
- CentOS runs at a measurably higher system load when under the exact same call load in Asterisk as other distros
- higher occurrence of system freezes under high load using Centos

We have worked on many CentOS/redhat system in the last several years, and the ones that use stock install configs and run at high load always have more problems than our OpenSuSE/Ubuntu/Slackware installs. We have even fixed many poorly stable systems simply by wiping the OS and installing another distro on the same hardware.

A final note on ViciDialNow(which we do not maintain), it is based on CentOS, but the maintainers of vicidialnow have fixed a lot of these issues in the kernel to make it more stable. We still recommend OpenSuSE and Ubuntu for production ViciDial systems(we offer ISO installers of both flavors in our downloads site)
http://download.vicidial.com/iso/vicibox/server/

[williamconley]

how many posts do you see on here where "all is well" doing a CentOS installation from scratch (easily)?

i count ... one. and yours doesn't technically say "easily", it sounds like you downplayed some things.

if you would like to see more support for CentOS ... POST your STEP BY STEP instructions or make a PDF and post a link.

that's how these things change.

otherwise, look for centos on this forum and you will see LOTS of people try and fail. with one marked exception: vicidialNOW (some say he's a god, some say he's oprah because they are never seen together, but there you have it)

[pslocom]

I appreciate the replies from both of you, although it seemed like they contained a bit of attitude aimed at my asking an honest question. I had no way of knowing right away that it was a huge issue, as far as I have seen in my looking in the forums (not a ton, but I have searched some) I hadn't noticed a trend towards CentOS.

I suppose I did not say that my installation/setup was "easy" but considering the first thing I ever did with asterisk and/or vicidial was replace a few vicidialNOW installs that weren't working correctly by following the scratch install on CentOS, I suppose I jumped to the conclusion that it was relatively simple to get it running if you had some general server/linux know-how and could follow instruction...

On that note, I did not realize CentOS had so many things working against it, as it was also the first time I had used CentOS (figuring vicidialNOW uses it, perhaps I should). Perhaps I will give another distro a shot on my next setup.

Again, I appreciate the replies and information, maybe at some point I will post step by step instructions on how I got the setup working, as I'm sure there are plenty of things I did differently than some others would, and would be happy to use the feedback...

[raysolomon]

Maybe I should chime in.

I like CentOS/RHEL. It is widely used and supported everywhere. It just might be the most widely used Linux OS in the server market. Anyway.. I am more of a Ubuntu fan, but my data center (ThePlanet.com) only supports CentOS, so that is what I use for my dialer.

Yes, its EASY to install if you have good instructions targeted for your OS.


I wrote a tutorial of how to install asterisk/vicidial, etc.. on a CentOS server. Its based off other tutorials I found on/off this forum and the install guides and my own experience as a Linux admin.
If you go though each step and install everything, you will have a working system in just under one hour.
I was going to wait to release it until 2.2.0 is out of beta, but the instructions will be very similar.
I see that many people on this forum needed help so I will offer this tutorial ahead of the release date as an unofficial guide.

As for the *kernel tweaks* that vicidialNOW supposedly applied, I am investigating that to see how it affects overall performance. Although I experience NO load/performance issues at all, some have claimed they had issues with CentOS and its performance, but it could be related to poor system administration or letting other processes chew up resources such as poor programming practices.

the unofficial version - rough draft

The official version will be in the wiki of this site when its ready.

[boybawang]

http://howtovici.blogspot.com/2009/11/v ... guide.html

[williamconley]

put yourself in the position of the newbie who is having "problems". LOL

posting a step by step tutorial is perfect. in fact, the more the merrier (if one doesn't work, for whatever reason, having another one to compare to quite often makes it "happen").

i have nothing against CentOS, but the "unofficial poll" suggests that vicibox is easier to install than scratch on CentOS. VicidialNOW/Vicibox should be about the same install, but only ONE is supported by The Vicidial Group ... which makes it the winner in my book. I love CentOS, but had to "Give It Up" for Vicidial (I chose Gentoo, others chose Ubuntu ... since the others who made this choice OWN the software ... I bowed to their choice without hesitation ... after my first install took under 30 minutes and was FLAWLESS).

For most people the only problem with the install is having the necessary network information "readily available" (easy for any computing professional, not-so-much for UnGeeks) and the carrier setup. Everything else has proven rather simple to date.

in my opinion, there should be step-by-step instructions listed by helpful (non-lurking) forum readers for every OS out there (32 and 64 bit versions) LTS and regular, everything. That would be how we get the user base UP and more motion on the package and better features. The more people .. the more help coding and the more people that will flat-out pay for a new cool feature.

[PaulScott]

Ok Matt, it seems that CentOS is not the best option to use as Vici Server.

Any way, is there any chance to make a multi server install from the REDUX Install CD?....

If it's not, what is the best procedure to install on OpenSuse, Multi server based?...

Thanks guys.

[williamconley]

multi server install instructions apply to all the server install types. vicibox, redux, and redux.

[PaulScott]

Hi guys,

I'm working on the multi server install from an vicibox installer CD.

Is there any advise on this kind of setup for the vicibox install not as standalone server?....

Will this work allright and flawless?...

Thank you

Regards..

Paul

[williamconley]

follow the multi-server installation to the letter. line by line. works great.

[gmcust3]

Can MULTIPLE server INSTALLATION possible using VNow 1.3 ?

Like 3 servers : One as DB, Another for Asterisk and last one for Webserver.

[williamconley]

yes.

cluster installations (where there is more than one server running the vicidial scripts) are valid for any vicidial installation. this includes vicibox, vicibox redux, vicidialnow AND scratch.

there are instructions available in several places. google vicibox cluster.

the best method is to install full vicidial (whatever flavor you like) on all three servers, then follow the cluster instructions for what needs to run on each server and how they interact with each other.

[gmcust3]

the best method is to install full vicidial (whatever flavor you like) on all three servers, then follow the cluster instructions for what needs to run on each server and how they interact with each other.

Thanks Williams !!!

[williamconley]

do try to install the same major revision on all three servers to be sure they send the right command set to each other. (ie: if you install 2.0.5 on one, install 2.0.5 on all three)

[williamconley]

By the Way, I love this!:

VicidialNOW CE
VERSION: 2.0.5-173
BUILD: 90320-0424
No other software installed on the box.
I've read the manager manual.

I think we should have a newbie questionnaire that asks these questions and creates the default profile just like that.

(Oops: Add asterisk version! )

oh: and since you have not yet done your cluster ... you should add "Single Server Install" on the last line.

[PaulScott]

Guys,

Based on the latest posts here, to have a multiserver / clustered vicidial we need to install the full vicibox (or any flavor) and then connect each other?....

this has not sense for me, since you will be installing unneeded services on each box... 3 mysql, 3 apache, 3 asterisk, and 3 astgui...

The point is to install each service on different servers and make them work together.

Is there any procedure to accomplish a clean and well done multi server / clustered install from vicibox without installing the whole pack on each one?....

It seems the only way to approach this is going to a scratch install.

Regards.

[williamconley]

The point of a cluster is to Increase the Capacity of your Dialer.

If you have MyZQL installed on a machine you are not using MyZQL, and an apache installed on a machine you are not using apache ... those services can be disabled at startup.

But attempting to install three (or eight) servers from scratch is not going to change the final outcome ... it won't operate different than the vicibox install with MySQL or apache turned off.

The "Master" server may have different applications "active for public consumption", but it and all the dialers still have a specific list of scripts and functions that are required.

So: Remembering that there are vicidial scripts that MUST run on ALL vicidial-related servers (except a MySQL box not being used for any other purpose) ... getting everything in place for those scripts to run (hi-res timing, no less, with ztdummy if necessary, perl scripts, everything) is not a simple task. Arguably, however, installing vicibox IS a simple task.

I suppose it would be possible, however, to modify the Vicibox install CD to "install only necessary applications" for a specific box use (Dialer vs Web vs Mysql). Although this would then limit the use of that particular box without further installation (instead of just re-activating the mysql, mysql would have to be installed).

Are you volunteering to create such a menuing system for the Vicibox install package ?

Personally, I think if you read the Cluster Installation methodology you will find that Vicidial's overhead (the scripts that MUST run) are the limiting factor on each box, not the "dormant" MySQL or Apache. So the present system is just right. But that's me.

[PaulScott]

William,

It's ok. I will try to find the "Cluster Installation methodology" and take a look at

Thanks

[subrata.sarkar]

I have two separate goautodial servers (Distro Name GoAutoDial CE 2.1 ). The server configuration are as follows:
Processors 4
Server:1.

Kernel Version 2.6.18-238.9.1.el5.goPAE (SMP)
Distro Name GoAutoDial CE 2.1


Model Intel(R) Xeon(R) CPU X3430 @ 2.40GHz
CPU Speed 2.39 GHz
Cache Size 8.00 MB
System Bogomips 19152.01
PCI Devices
- (2x) Ethernet controller: Intel Corporation 82574L Gigabit Network Connection
- Host bridge: Intel Corporation Core Processor DMI
- IDE interface: Intel Corporation 5 Series/3400 Series Chipset 2 port SATA IDE Controller
- IDE interface: Intel Corporation 5 Series/3400 Series Chipset 4 port SATA IDE Controller
- ISA bridge: Intel Corporation 3400 Series Chipset LPC Interface Controller
- PCI bridge: Intel Corporation 5 Series/3400 Series Chipset PCI Express Root Port 1
- PCI bridge: Intel Corporation 5 Series/3400 Series Chipset PCI Express Root Port 5
- PCI bridge: Intel Corporation 5 Series/3400 Series Chipset PCI Express Root Port 6
- PCI bridge: Intel Corporation 5 Series/3400 Series Chipset PCI Express Root Port 7
- PCI bridge: Intel Corporation 5 Series/3400 Series Chipset PCI Express Root Port 8
- PCI bridge: Intel Corporation 82801 PCI Bridge
- PCI bridge: Intel Corporation Core Processor PCI Express Root Port 1
- PCI bridge: Intel Corporation Core Processor PCI Express Root Port 3
- PCI bridge: Vitesse Semiconductor VSC452 [SuperBMC]
- SMBus: Intel Corporation 5 Series/3400 Series Chipset SMBus Controller
- System peripheral: Intel Corporation Core Processor Miscellaneous Registers
- System peripheral: Intel Corporation Core Processor QPI Link
- System peripheral: Intel Corporation Core Processor QPI Routing and Protocol Registers
- System peripheral: Intel Corporation Core Processor Semaphore and Scratchpad Registers
- System peripheral: Intel Corporation Core Processor System Control and Status Registers
- System peripheral: Intel Corporation Core Processor System Management Registers
- (2x) USB Controller: Intel Corporation 5 Series/3400 Series Chipset USB2 Enhanced Host Controller
- VGA compatible controller: Matrox Graphics, Inc. MGA G200EV
IDE Devices none
SCSI Devices
- ATA ST3500514NS (Direct-Access)
- HL-DT-ST DVDROM DH40N (CD-ROM)
USB Devices
- (2x) Intel Corp. Integrated Rate Matching Hub
- IBM Corp.
- SiGma Micro

Server 2:


Kernel Version 2.6.18-238.9.1.el5.goPAE (SMP)
Distro Name GoAutoDial CE 2.1




Hardware Information
Processors 2
Model Pentium(R) Dual-Core CPU E6600 @ 3.06GHz
CPU Speed 3.06 GHz
Cache Size 2.00 MB
System Bogomips 12236.34
PCI Devices
- Audio device: Intel Corporation N10/ICH 7 Family High Definition Audio Controller
- Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168B PCI Express Gigabit Ethernet controller
- Host bridge: Intel Corporation 4 Series Chipset DRAM Controller
- IDE interface: Intel Corporation N10/ICH7 Family SATA IDE Controller
- ISA bridge: Intel Corporation 82801GB/GR
- PCI bridge: Intel Corporation 4 Series Chipset PCI Express Root Port
- PCI bridge: Intel Corporation 82801 PCI Bridge
- PCI bridge: Intel Corporation N10/ICH 7 Family PCI Express Port 1
- PCI bridge: Intel Corporation N10/ICH 7 Family PCI Express Port 2
- SMBus: Intel Corporation N10/ICH 7 Family SMBus Controller
- USB Controller: Intel Corporation N10/ICH 7 Family USB UHCI Controller #1
- USB Controller: Intel Corporation N10/ICH 7 Family USB UHCI Controller #2
- USB Controller: Intel Corporation N10/ICH 7 Family USB UHCI Controller #3
- USB Controller: Intel Corporation N10/ICH 7 Family USB UHCI Controller #4
- USB Controller: Intel Corporation N10/ICH 7 Family USB2 EHCI Controller
- VGA compatible controller: Intel Corporation 4 Series Chipset Integrated Graphics Controller
IDE Devices none
SCSI Devices
- ATA Hitachi HDS72105 (Direct-Access)
USB Devices none


As I am new to this environment, can you tell me without going for anyother installation process, can I use one server as application server and another for database server? If yes/no tell me the procedure for the both.

I have one more query that some of our agents is complaining that when they are taking with one customer in predictive dialing. Suddenly another customer is coming to line, i.e. two customer is coming into the same line. It is not happening all the time, but sometimes it is happening in predictive dialing even call flow is very less. Can you please tell me why is it happening and how can I solve this problem.

Thanks for your kind reply.

[subrata.sarkar]

if you need any further information of our configuration. please let me know how can i extract the same.

[williamconley]

http://www.poundteam.com/downloads/Vici ... v1%201.pdf

There is a section for Just use a Sep DB server.