Finally 100% working with not isuue at all.

[maximo]

i think i did it, let see in real life how vicidial will perform.

running 120 live calls,
Dual Xeon HP workstation xw6000
4 gig of ram
4 SCSI raid HDD stripped 75 gig each
mysql 5.XX
vicidial latest 2.0.5
i only use SIP, so, there is not Digium hardware or any other kind on it.
OS Linux Redhat 5 enterprise

so far, all work as i spected or even more.
long live to the developper.
i will be open to help in case there is any problem, i think i had passed the test, after over then 45 hours resolving issue.

[ramindia]

Hi

thats good hear

and thanks for sharing your success with other users

ram

[DarknessBBB]

Hi Maximo!
Can you talk more deeply about your hardware? It's always good to know about working hardware

[eliasferreyra]

thanks for posting your results

[maximo]

i will detail whole set as follow.

second hand box = HP workstation xw6000
4 GIG of Registered kingston Ram
2 Xeon Processors 2.4ghtz
Linux Redhat 5.0 Enterprise
4 SCSI HDD RAID set with Adaptec builtin scsi card
VICIDIAl 2.0.5 built scratch install installation
it took me 6 hours to setup everithing into a working condition
it took me to debug small stuff one week, but debugging was all explained into the scratch install.

this is all i have, and still working,

hardware cost = 650$ including everithing

[DarknessBBB]

So do you have 120 live calls, web server and db server all on the same workstation?

[maximo]

i will create later on another server, for loadbalance, however, i would like to push this to the maximum limit, so, far we are working in a busy environement, the system so far, havent crash yet.
i am using pure g711 ulaw codec, however i ill add 120 CL g729 and start making transcoding.
i will post here the result.

[enjay]

I personally try to always go with HP servers, I've had great luck with them.

A customer of mine just recently upgraded their server to a

HP ML370
Quad-core 2.33ghz
4gb RAM
3x 146gb 15kRPM SAS Drivers
So far the thing is absolutely screaming, the migration went great and I am very pleased..

As for MySQL 5.0.51 & 5.0.45 "specifically" have issues with the uniqueid properties in the database and I had to change from int to varchar(30)

5.0.22 on the other hand does not have this issue, and I have been successful with it without making those modifications to the uniqueid columns.

-not saying this will be the case for everyone, just my experience-

Art