Very Low agents voice + high server load on GoAutoDial-3.0

[udy786]

Hello,

GOautodial CE 3.0 ISO | VERSION: 2.4-364a BUILD: 120409-1136 | Asterisk 1.4.39.1-vici.go | Single Server - CentOS release 5.5 | No Digium/Sangoma Hardware | No Extra Software After Installation

We have started our dialing with 10 agents. But there was toooo much high server load. So, we have reduced the agents to only 5. In this the load avg is somewhat controlled. But there is one more issue : The customers are not able to hear the agent's voice properly. I have unlimited bandwidth. So, that is not the issue. Will you please tell me is this the issue with GoAutoDial-3.0 or what ? What are the factors which affects the voice ?

Is GoAutoDial-3.0 stable ? or is it having bug ? As it is taking toooo much load as well.

=> Auto Outbound
=> 5 to 7 Agents Only
=> Dial Level : 4 - 5
=> G729 Codec
=> Dialing Country : USA

Configurations :

Dial Method: RATIO
Dial Timeout: 28
Available Only Tally: Y
Available Only Tally Threshold: DISABLE
Drop Percentage Limit:0
Dial Level Difference Target: 0
Adapt Intensity Modifier: 0

Server details :

No of processor : 2
vendor_id : GenuineIntel
cpu family : 6
model : 15
model name : Intel(R) Xeon(R) CPU 3040 @ 1.86GHz
stepping : 2
cpu MHz : 1596.000
cache size : 2048 KB
RAM : 8 GB

Can we continue using GoAutoDial-3.0 or not ???? Should we move to GoAutoDial CE - 2.1 ?

-Thanks

[williamconley]

if you have unlimited bandwidth turn off g729. its only use it to conserve bandwidth. but it EATS cpu power horribly.

what are the agents using for microphones? and are they adjustable? (ie: try turning up the volume ...?)

is this system virtual?

2x1.8Ghz processors is kinda tiny for a Vicidial server. I'm not surprised you hit your limit somewhere between 5-10 agents. Consider upgrading your processor. Also look at just getting a decent quad core system with more recent techology. Not "expensive latest" technology, just more recent than 1.8Ghz. And if it is virtual, get a physical machine.

[udy786]

Thank you for your reply williamconley.

what are the agents using for microphones? and are they adjustable? (ie: try turning up the volume ...?)

My agents are using hardphones. And they are not adjustable. The same hard phones they are using for other dialer. And it works without any issue. Rigth now m trying to move my agents to goautodial.

is this system virtual?

No, I m having physical system.

As I have seen that the goautodial-3.0 is taking much server load which was not the case with goatuodial-2.1 version.
Will you please guide me whether the goautodial ce - 3.0 is having issue or it will work fine with my good configured server ?
Do I need to move to goatuodial ce 2.1 ?

[gardo]

Post your load average when dialing. You can get this by running:

Code: Select all

top -c


[williamconley]

i've not heard of anyone having any problems being able to run goauto3.0 at all. certainly not someone who was previously running a goauto earlier version.

but then again, this is linux.

i will say that there should be NO volume issues at all, but the only times I have heard complaints about low volume (now that you mention it ...) has been with hard phones (usually grandstream, I think).

you could compare the sip.conf from the old to the new and see if there is anything related to volume.

also be sure the codec is the same as you were using before (and are using the same codec as the "other dialer").

failing that, of course, do try ulaw/gsm and anything else that both the phone and the asterisk server speak to see if that helps.

and check the manual for your phone to see if it really has no volume control (possible that somehow a volume control is being invoked somewhere).

[udy786]

you could compare the sip.conf from the old to the new and see if there is anything related to volume.

I dont found anything related to volume.

also be sure the codec is the same as you were using before (and are using the same codec as the "other dialer").

On the other dialer we are using g729 codec and same we are using with goautodial.

failing that, of course, do try ulaw/gsm and anything else that both the phone and the asterisk server speak to see if that helps.

I have tried changing the codec to alaw. And in my 5 hrs of shift there were not volume issue. Still we are checking. If I will get volume issue again or not.

Below is my top output :

[root@localhost astguiclient]# top
top - 20:38:32 up 1 day, 6:13, 3 users, load average: 2.53, 2.14, 2.28
Tasks: 178 total, 1 running, 174 sleeping, 0 stopped, 3 zombie
Cpu0 : 39.5%us, 8.3%sy, 0.0%ni, 51.2%id, 0.0%wa, 0.0%hi, 1.0%si, 0.0%st
Cpu1 : 35.2%us, 9.3%sy, 0.0%ni, 51.2%id, 0.7%wa, 0.7%hi, 3.0%si, 0.0%st
Mem: 8179000k total, 1071352k used, 7107648k free, 6252k buffers
Swap: 10223608k total, 0k used, 10223608k free, 221144k cached

PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND
2889 mysql 15 0 976m 339m 4936 S 15.9 4.3 95:38.38 /usr/libexec/mysqld --basedir=/usr --datadir=/var/lib/mysql --user=mysql
13392 root 18 0 2344m 89m 6168 S 15.6 1.1 88:33.28 asterisk
25520 root 15 0 75008 9784 2820 S 4.0 0.1 4:42.01 /usr/bin/perl /usr/share/astguiclient/AST_update.pl
26372 root 19 0 32940 6124 1748 S 2.3 0.1 0:00.07 /usr/bin/perl /usr/share/astguiclient/AST_send_action_child.pl --SYSLOG
26398 root 24 0 32940 6120 1748 S 2.3 0.1 0:00.07 /usr/bin/perl /usr/share/astguiclient/AST_send_action_child.pl --SYSLOG
26368 root 18 0 32940 6124 1748 S 2.0 0.1 0:00.06 /usr/bin/perl /usr/share/astguiclient/AST_send_action_child.pl --SYSLOG
26376 root 19 0 32940 6128 1748 S 2.0 0.1 0:00.06 /usr/bin/perl /usr/share/astguiclient/AST_send_action_child.pl --SYSLOG
26383 root 21 0 32936 6124 1748 S 2.0 0.1 0:00.06 /usr/bin/perl /usr/share/astguiclient/AST_send_action_child.pl --SYSLOG
26385 root 22 0 32940 6124 1748 S 2.0 0.1 0:00.06 /usr/bin/perl /usr/share/astguiclient/AST_send_action_child.pl --SYSLOG
26387 root 23 0 32940 6124 1748 S 2.0 0.1 0:00.06 /usr/bin/perl /usr/share/astguiclient/AST_send_action_child.pl --SYSLOG
26370 root 17 0 32940 6128 1748 S 1.7 0.1 0:00.05 /usr/bin/perl /usr/share/astguiclient/AST_send_action_child.pl --SYSLOG
26381 root 21 0 32936 6128 1748 S 1.7 0.1 0:00.05 /usr/bin/perl /usr/share/astguiclient/AST_send_action_child.pl --SYSLOG
26392 root 23 0 32940 6128 1748 S 1.7 0.1 0:00.05 /usr/bin/perl /usr/share/astguiclient/AST_send_action_child.pl --SYSLOG
13500 root 15 0 76244 14m 2736 S 1.3 0.2 9:54.85 /usr/bin/perl /usr/share/astguiclient/AST_VDauto_dial.pl
9941 apache 15 0 322m 21m 12m S 1.0 0.3 0:20.97 /usr/sbin/httpd
9947 apache 15 0 322m 20m 11m S 1.0 0.3 0:20.98 /usr/sbin/httpd
9948 apache 15 0 322m 21m 12m S 1.0 0.3 0:20.98 /usr/sbin/httpd
13497 root 19 0 68164 6924 2740 S 1.0 0.1 3:41.41 /usr/bin/perl /usr/share/astguiclient/AST_manager_send.pl
14992 apache 15 0 321m 19m 11m S 1.0 0.2 0:14.63 /usr/sbin/httpd
19147 apache 15 0 321m 16m 8584 S 1.0 0.2 0:08.34 /usr/sbin/httpd
19314 apache 15 0 321m 14m 7124 S 1.0 0.2 0:07.99 /usr/sbin/httpd
22558 apache 15 0 321m 14m 7228 S 1.0 0.2 0:03.77 /usr/sbin/httpd
9755 apache 15 0 321m 20m 11m S 0.7 0.3 0:21.02 /usr/sbin/httpd
13927 apache 15 0 321m 21m 12m S 0.7 0.3 0:16.39 /usr/sbin/httpd
14876 root 15 0 12740 1180 804 S 0.7 0.0 0:05.59 top
15198 apache 15 0 321m 20m 11m S 0.7 0.3 0:14.37 /usr/sbin/httpd
22553 apache 15 0 321m 14m 6968 S 0.7 0.2 0:03.66 /usr/sbin/httpd
22557 apache 15 0 321m 19m 11m S 0.7 0.2 0:03.74 /usr/sbin/httpd
13502 root 15 0 74888 9544 2816 S 0.3 0.1 1:44.84 /usr/bin/perl /usr/share/astguiclient/AST_manager_listen.pl
14883 apache 15 0 321m 20m 12m S 0.3 0.3 0:14.78 /usr/sbin/httpd
18551 root 15 0 81252 10m 1540 S 0.3 0.1 0:00.74 /usr/bin/perl /usr/share/astguiclient/FastAGI_log.pl --debug
23630 root 15 0 86972 25m 2712 S 0.3 0.3 4:32.31 /usr/bin/perl /usr/share/astguiclient/AST_VDadapt.pl --debug
25127 root 15 0 90108 3360 2604 S 0.3 0.0 0:02.66 sshd: root@pts/10
25664 root 15 0 12740 1172 804 R 0.3 0.0 0:00.35 top
1 root 15 0 10348 688 576 S 0.0 0.0 0:06.31 init [5]

[williamconley]

Hopefully switching to ulaw will be the resolution. why were you using g729 if you could be using ulaw?

load average: 2.53, 2.14, 2.28

overload! you have a 2 processor system and you are cruising above 2.0 ... not good!