vicidial.org

we're experiencing delayed agent web page. what are the things to check?

only less than 10 agents and yet they're experiencing this.

im going to check the db. what other things should i check?

Delayed agent web page means...?

The main screen for vicidial the agent logs into is slow to perform actions?

The agent is in a call 10 seconds before the data appears on the screen?

The script that loads from an external url to load the webform is delayed?

Delayed agent web page means...?

The main screen for vicidial the agent logs into is slow to perform actions?
- yes, it takes time to load the page and the info of the called party

The agent is in a call 10 seconds before the data appears on the screen?
- sometimes longer.

The script that loads from an external url to load the webform is delayed?
- no script is loaded.

Looks like you've been playing with the system too much. What's the content of your /etc/my.cnf?

Haha. Not really.

Anyway, here is the my.cnf

Code: Select all

[mysqld]
datadir=/var/lib/mysql
socket=/var/lib/mysql/mysql.sock
# Default to using old password format for compatibility with mysql 3.x
# clients (those using the mysqlclient10 compatibility package).
old_passwords=1
skip-name-resolve
skip-host-cache
max_connections=200

[mysql.server]
user=mysql
basedir=/var/lib

# JDM
#bind-address=192.168.111.222
port=3306

[mysqld_safe]
log-error=/var/log/mysqld.log
pid-file=/var/run/mysqld/mysqld.pid


I was thinking that this might have something to do with proxy. I removed the gateway IP of all computers and use proxy instead to browse the net.

How's the load average of your server? Have you tried switching back the gateway settings of your workstation and see if everything goes back to normal?

Yep, your proxy is slowing you down. You should set up a bypass to allow direct access to Vicidial Only and proxy everywhere else. Although, honestly, they shouldn't be allowed to GO anywhere else. Often this can be accomplished with DNS (if the only record you can look up in DNS is your Vicidial server ... you can't go anywhere else).

i just want to update this. yes the proxy seems to be the culprit. i remove the proxy settings and put back their gateways. no problem so far.

my objective before was to remove their internet access (thus removing gateway) and use proxy to browse instead.

i already set the firewall/proxy to bypass it when accessing local address. im using pfSense btw.

proxies are complicated. why not just lock them to the ip address of the vicidial server for outbound access?

i use proxy to disable their direct internet access thru NAT. i removed their gateway. this way, im sure that internet access is thru proxy. and none can access directly the internet.

unfortunately the proxy breaks vicidial. so try using your router to limit outbound access to vicidial only instead. won't affect speed or throughput, just limit the locations.

i'll remove the NAT and see if the problem still occurs. if it works, my next issue is how to give them limited internet access.

proxy? haha. put back the NAT?

use the IP address of the vicidial server instead of the FQDN. Remove their DNS settings (or configure your router to refuse to respond to DNS requests from them). No DNS = no internet, no "www". But still networking will work fine (as long as it's all IP address-based, which google and facebook are NOT, LOL).

Many routers will allow functions easier than that, such as "NO access except for this list of IP addresses".

yes i use the ip address of vici for the agents to access. if i remove the dns, totally no internet. i need partial access to net.

there is a setting in pfSesne where i can make local access bypass proxy. im not sure if its working.

if you need partial (ie: one or two sites for form submission), those DNS entries can be made directly in each computer (or you can try to convince your firewall to manage this). In Windows there is a "hosts" file which can be directly edited to provide the IP address of any domain name. Anything in that file will sill "convert" and work properly, because you'd be faking the DNS record. We use this technique when building new sites to make sure they will work with their real name before they actually "go live". Works very nicely (but requires editing the "hosts" file on each participating computer).

ah yes the hosts file is there!

thanks for the tip. i guess i'll try this one for first. im sure this will work.

an interesting concept would be to create a "batch" file that activates at startup and copies that "host" file from a central server. although I'd have to review it and be sure it has nothing "personalized" for each machine on it. but that may allow a DNS change mid-shift to be accomplished with one file change and an "OK! Everybody reboot when they leave for their next break!".