vicidial.org

Hi,
I hope you can help me with this issue:
I have Vicidial Multiserver version 3.1.14 64 bits with the following servers:
Data Base
24 cores Intel(R) Xeon(R) CPU E5-2620 0 @ 2.00GHz
16 GB RAM
1 TB HD
Dialer Server 1
Telefonia 1
4 core Intel(R)Xeon(R)CPU E5502@ 1.87GHz
20 GB RAM
140 GB HD
Dialer Server 2
4 core Intel(R) Xeon(R) CPU E5503@ 2.00GHz
16 GB RAM
140 GB HD
Dialer Server 3
8 core Intel(R) Xeon(R) CPU X3440@ 2.53GHz
8 GB RAM
500 GB HD

Dialer Server 4
8 core Intel(R) Xeon(R) CPU E5506@ 2.13GHz
16 GB RAM
500 GB HD

Dialer Server 5
4 core Intel(R) Xeon(R) CPU E5502@ 1.87GHz
24 GB RAM
300 GB HD

Dialer Server 6
4 core Intel(R) Xeon(R) CPU E5-24030@ 1.80GHz
14 GB RAM
500 GB HD

1 Web Server
12 core Intel(R) Xeon(R) CPU E5-24200@ 1.90GHz
14 GB RAM
1 TB HD

With that we thouht to handle about 250 sip sessions. The problem is we can not have more than 160 sip sessions. We notice this:
- Vicidial logs out the agents with the “Click here for log in again” screen
- The softphone hangs out.
- The web page does not show after a time
- Calls are being mixed between extensions
- Real Time report shows many dead calls when actually is a live call
- Real Time report does not refresh in stablished time
- Agents goes paused automatically.
- Script is not shown when the agent answers the call
- It does not let hang up a call in order to dispose a second.
We have done the next:
- eAccelerator has been upgraded to last version in Web server. With this the CPU usage is decreased.
- On Data Base Server:
We modify my.cnf file as follows:

[client]
port = 3306
socket = /var/run/mysql/mysql.sock

[mysqld]
port = 3306
socket = /var/run/mysql/mysql.sock
datadir = /var/lib/mysql
skip-locking
skip-log-warnings
key_buffer_size = 1G
max_allowed_packet = 16M
table_open_cache = 5120
sort_buffer_size = 2M
read_buffer_size = 1M
net_buffer_length = 8K
read_rnd_buffer_size = 64M
myisam_sort_buffer_size = 128M
thread_cache_size = 16
query_cache_size = 128M
thread_concurrency = 24
skip-name-resolve
connect_timeout=120
long_query_time = 3
log_slow_queries
max_connections=1000
open_files_limit=5120
max_heap_table_size = 256M
concurrent_insert=2
expire_logs_days=3
skip-innodb
read-only = 0
low_priority_updates=1

log-bin=mysql-bin

binlog_format=mixed
binlog-do-db = asterisk
slave-skip-errors = 1062,1032

server-id = 1

log-bin=mysql-bin
replicate-do-db = asterisk
[safe_mysqld]
log-error = /var/log/mysql/mysqld.log
socket = /var/run/mysql/mysql.sock

[mysqldump]
socket = /var/run/mysql/mysql.sock
quick
max_allowed_packet = 16M

[mysql]
no-auto-rehash

[myisamchk]
key_buffer_size = 20M
sort_buffer_size = 20M
read_buffer = 2M
write_buffer = 2M

[mysqlhotcopy]
interactive-timeout

[mysqld_multi]
mysqld = /usr/bin/mysqld_safe
mysqladmin = /usr/bin/mysqladmin
log = /var/log/mysqld_multi.log


realice el siguiente update:

mysql -f asterisk < /usr/src/astguiclient/trunk/extras/upgrade_2.4.sql


We have done the next alter table:

ALTER TABLE vicidial_live_agents MODIFY closer_campaigns VARCHAR(8000) default '';
ALTER TABLE vicidial_live_agents MODIFY external_ingroups VARCHAR(8000) default '';
ALTER TABLE vicidial_live_agents MODIFY agent_territories VARCHAR(1000) default '';
ALTER TABLE vicidial_live_agents ENGINE=MEMORY;
ALTER TABLE vicidial_manager ENGINE=MEMORY;

We have done a maintenance with autorepair and optimize:
How ever we follow with the same issues after login more tan 170 agents.

Any ideas?

Best regarts.

mysql -f asterisk < /usr/src/astguiclient/trunk/extras/upgrade_2.4.sql

why did you run an upgrade script? I thought you were just clustering?

i think you should just start over and install with Vicibox 4.0.3 and build your cluster correctly from the start. save yourself some hair pulling.

check your cronjobs it could be doubling up