| M | T | W | T | F | S | S |
|---|---|---|---|---|---|---|
| « Mar | ||||||
| 1 | 2 | 3 | 4 | 5 | ||
| 6 | 7 | 8 | 9 | 10 | 11 | 12 |
| 13 | 14 | 15 | 16 | 17 | 18 | 19 |
| 20 | 21 | 22 | 23 | 24 | 25 | 26 |
| 27 | 28 | 29 | 30 | |||
Make sure that the local firewall on the machine will allow the NRPE daemon to be accessed from remote servers.
To do this, run the following iptables command. Note that the RH-Firewall-1-INPUT chain name is Fedora-specific, so it will be different on other Linux distributions.
# iptables -I RH-Firewall-1-INPUT -p tcp -m tcp –dport 5666 -j ACCEPT
Save the new iptables rule so it will survive machine reboots.
# service iptables save
Mon 17 Jan 2005 12:15:08 PM PST, PST in this case is the current timezone./usr/share/zoneinfo here you will find a list of time zone regions. Choose the most appropriate region, if you live in Canada or the US this directory is the “America” directory.mv /etc/localtime /etc/localtime-old
ln -sf /usr/share/zoneinfo/Europe/Amsterdam /etc/localtime
/usr/bin/rdate -s time.nist.gov
/etc/sysconfig/clock file (e.g. “America/Los_Angeles”)/sbin/hwclock --systohc
On *nix systems, there is a limit set in the kernel on how many open file descriptors are allowed on the system. This may be compiled in, or it may be tunable on the fly. In Linux, the value of this parameter can be read from and written to the proc filesystem.
[root@smbsrv090 proc]# cat /proc/sys/fs/file-max 52427
On this system 52,427 open file descriptors are permitted. We are unlikely to run out. If we wanted to change it, we’d do something like this:
[root@smbsrv090 proc]# echo "104854" > /proc/sys/fs/file-max [root@smbsrv090 proc]# cat /proc/sys/fs/file-max 104854
(Warning, change kernel parameters on the fly only with great caution and good cause)
But how do we know how many file descriptors are being used?
[root@smbsrv090 proc]# cat /proc/sys/fs/file-nr 3391 969 52427 | | | | | | | | maximum open file descriptors | | | total free allocated file descriptors | total allocated file descriptors (the number of file descriptors allocated since boot)
Tags: file-max, Linux, open files
Al parecer cuando se le instala un SugarCRM a un servidor donde esta corriendo un trixbox, este desconfigura el trixbox totalmente, ya que el SugarCRM instala en el php un nueva forma de capturar las secciones y donde las almacenas, causando esto un deshabilitamiento del trixbox en varias partes.
Solución
A continuación explico los pasos para rehabilitar el trixbox.
De esta manera el trixbox recuperara su funcionamiento total.
Tags: AMP_SQL, session error, sugarCRM, Trixbox
How to Boot a virtual machine automatically.
Reboot your computer. It should auto-login and immediately lock the desktop into your default screensaver.
Wait 40 seconds or so, just for fun, then enter your password. Your VMware Workstation should be booted.
As a final note, if you prefer VMWare Workstation to the VMWare Player, the launch command would be:
vmrun start /path/to/machine/machine-name.vmx
Tags: boot, virtual machine, vmware
Vamos a plantear el siguiente escenario:
Necesitamos que los servidores asterisk de un call center esten sincronizados pero estos tienen diferentes accesos a internet y las conecciones no son estables.
Vamos a tomar dos servidores como ejemplo y los llamaremos MASTER:192.168.0.1 y SLAVE:192.168.0.2.
En MASTER:
>service ntpd stop
>ntpdate -u server 0.centos.pool.ntp.org
[/etc/ntp.conf]
server 0.centos.pool.ntp.org
server 1.centos.pool.ntp.org
server 2.centos.pool.ntp.org
[/etc/ntp.conf]
restrict 127.0.0.1
restrict 192.168.0.0 mask 255.255.255.0 nomodify notrap
>chkconfig ntpd on
En SLAVE:
> service ntpd stop
[/etc/ntp.conf]
server 192.168.0.1
[/etc/ntp/step-tickers]
192.168.0.1
>ntpdate -u 192.168.0.1
> service ntpd start
>chkconfig ntpd on
VICIDIAL - LOAD BALANCING setup. (Original
This document is meant to summarize the capabilities and setup of VICIDIAL in a multi-server environment.
Why Load Balance?
The primary reason to do load balancing, or clustering of multiple VICIDIAL servers, is to spread the calls taken in or the answered calls on an outbound campaign across all of the agents that are logged into a campaign no matter what server they are on. For instance, on an outbound campaign, you have 2 servers, server one has 20 agents logged in on a campaign and the other server(two) has 5 agents logged in on the same campaign. Lets say that the campaign is set to a dial_level of 3.0 so there are 60 active calls being placed on server one and 15 active calls being placed on server two. Then 23 of the calls on server one answer meaning that there are three calls too many for the agents available on that server. Under a load-balancing-overflow setup those three calls can travel over an IAX2 trunk directly to the agents on that server that are still available. This increased efficiency in both inbound and outbound environments as well as reducing on-hold times for customers and equalizing wait times for agents across all servers for a campaign.
Another reason for load balancing is the ability to use cheaper hardware on the server side. It is much cheaper and more fault-tolerant to buy four P4 2.0GHz 1U servers for $800 a piece than it is to buy a single 4U quad Xeon 3.2GHz server. The four 1U servers will have more total capacity, can be easily scaled and if one fails you’ve only lost 25% of capacity instead of everything. This philosophy has serverd our call center very well over the last two years.
How do I set up load balancing on my two server VICIDIAL setup?
These steps are taken directly from the SCRATCH_INSTALL document, but they are all put together here to give a better idea of what is needed all in one place. It is assumed that you already have VICIDIAL up and running on both servers.
NOTE: In a multi-server setup you may want to have your database and web server on a separate machine from your Asterisk/VICIDIAL servers. Simply copy the web page directories to your new database/web server and set the AST_SERVER_conf.pl files on your VICIDIAL servers to point to that new database server. You can also have several web servers(or even load-balancing web servers) if you have more than 70 seats in one installation you may want to do that. For the web pages you just need to make sure the dbconnect.php files are configured for your database server. We have had 9 VICIDIAL servers and 2 web servers using a single database server with no problems.
1. The VICIDIAL/Asterisk servers need to have all of the perl scripts and cron jobs installed on them, except these which only need to be on one of the servers:
- AST_VDhopper.pl
- AST_cleanup_agent_log.pl
- ADMIN_adjust_GMTnow_on_leads.pl
- AST_DB_optimize.pl
2. The two servers need to be registered to each other as IAX2 friends:
SERVER ONE(ASTtest1-10.10.10.15)
iax.conf:
register => ASTtest1:test@10.10.10.16
[ASTtest2]
type=friend
accountcode=IAXtrunk2
context=default
auth=plaintext
host=dynamic
permit=0.0.0.0/0.0.0.0
secret=test
qualify=yes
SERVER TWO(ASTtest2-10.10.10.16)
iax.conf:
register => ASTtest2:test@10.10.10.15
[ASTtest1]
type=friend
accountcode=IAXtrunk1
context=default
auth=plaintext
host=dynamic
permit=0.0.0.0/0.0.0.0
secret=test
qualify=yes
3. The two servers need to have wildcard extensions assigned to the other server in the dialplan:
SERVER ONE(ASTtest1-10.10.10.15)
extensions.conf:
[globals]
TRUNKIAX2=IAX2/ASTtest1:test@10.10.10.16
[default]
exten => _010*010*010*016*8600XXX,1,Dial(${TRUNKIAX2}/${EXTEN:16},55,o)
exten => _010*010*010*016*8600XXX,2,Hangup
SERVER TWO(ASTtest2-10.10.10.16)
extensions.conf:
[globals]
TRUNKIAX1=IAX2/ASTtest2:test@10.10.10.15
[default]
exten => _010*010*010*015*8600XXX,1,Dial(${TRUNKIAX1}/${EXTEN:16},55,o)
exten => _010*010*010*015*8600XXX,2,Hangup
4. For BOTH servers the VDAD extens need to be setup there as well for the Load-Balance and Load-Balance-Overflow AGI scripts, as well as setting up the closer and inbound extens if needed:
; VICIDIAL_auto_dialer transfer script Load Balance Overflow:
exten => 8367,1,AGI(call_log.agi,${EXTEN})
exten => 8367,2,AGI(agi-VDAD_LO_transfer.agi,${EXTEN})
exten => 8367,3,AGI(agi-VDAD_LO_transfer.agi,${EXTEN})
exten => 8367,4,AGI(agi-VDAD_LO_transfer.agi,${EXTEN})
exten => 8367,5,Hangup
; VICIDIAL_auto_dialer transfer script Load Balanced:
exten => 8368,1,AGI(call_log.agi,${EXTEN})
exten => 8368,2,AGI(agi-VDAD_LB_transfer.agi,${EXTEN})
exten => 8368,3,AGI(agi-VDAD_LB_transfer.agi,${EXTEN})
exten => 8368,4,AGI(agi-VDAD_LB_transfer.agi,${EXTEN})
exten => 8368,5,Hangup
; parameters for agi-VDAD_LB_closer.agi (2 fields separated by five dashes “—–”):
; 1. the full extension formatted by VICIDIAL for internal transfers * separated
; 2. the word START to denote the beginning of the acceptance of the transfer
; inbound VICIDIAL transfer calls [INTERNAL TRANSFER]
exten => _90009.,1,Answer ; Answer the line
exten => _90009.,2,AGI(agi-VDAD_LB_closer.agi,${EXTEN}—–START)
exten => _90009.,3,Hangup
; parameters for agi-VDAD_LO_closer.agi (2 fields separated by five dashes “—–”):
; 1. the full extension formatted by VICIDIAL for internal transfers * separated
; 2. the word START to denote the beginning of the acceptance of the transfer
; inbound VICIDIAL transfer calls [LOCAL TRANSFER]
exten => _990009.,1,Answer ; Answer the line
exten => _990009.,2,AGI(agi-VDAD_LO_closer.agi,${EXTEN}—–START)
exten => _990009.,3,Hangup
; inbound VICIDIAL call with prompt for 4-digit fronter code
exten => 1234,1,Answer ; Answer the line
exten => 1234,2,AGI(agi-VDAD_LO_closer_inbound.agi,CL_GALLERIA—–7275555134—–Closer—–park———-999—–1)
exten => 1234,3,Hangup
5. Reload both Asterisk servers and for outbound change the VDAD exten to 8367 or 8368 and kill the AST_VDauto_dial.pl scripts on both servers so they can restart and you can now look at the AST_timeonVDADall.php page(per campaign time-on-VDAD available from the STATS and REPORTS link on the vicidial admin screen) that will allo you to see the server_ip of the agent and the server_ip of the call per campaign across all campaigns.
If you have any questions or problems please post to the astguiclient-users list(link available on the project website)
6. For multi-server VICIDIAL/astGUIclient installations these cron scripts only need to be set up and run on one of the servers:
- AST_VDhopper.pl
- AST_cleanup_agent_log.pl
- ADMIN_adjust_GMTnow_on_leads.pl
- AST_DB_optimize.pl
Tags: load balance, Vicidial
Para poder responder a la doble linea (CW) en troncos análogos digitando *9 se agrega un feature a la central de la siguiente forma:
1- Se registra la variable global “DYNAMIC_FEATURES”
extensions.conf
[globals]
DYNAMIC_FEATURES=>apps
(En caso de tener otras aplicaciones, estas se separan por #. Ejm: DYNAMIC_FEATURES=>features#apps)
2- Se agrega la aplicación Flash() con su código (*9).
features.conf
[applicationmap]
apps => *9,callee,Flash,
* Notas.
- Es bueno revisar que el tiempo del flash no sea muy corto o la CO no lo detectará.
zapata.conf
[channels]
flash=500
- En trixbox se usan los siguientes archivos de conf:
globals_custom.conf
features_applicationmap_custom.conf
Tags: call waiting, cw, doble linea
Para que cada agente del cc accese a su habiente de trabajo cambiamos la pagina de inicio del navegador por la direccion de nuestro servidor de vicidial, pero luego tiene que insertar el usuario y contraseña del tefelono(paso que saltaremos) luego es usuario y contraseña del agente.
Al cambiar la pagina de inicio del navegador ej: http://google.com por
http://XXX.XXX.XXXX.XXX/agc/vicidial.php esto seria lo normal pero lo haremos de la siguiente forma cambiaremos por
http://XXX.XXX.XXX.XXX/agc/vicidial.php?pl=cc111&pp=vt111
cambiando cc111 por la extencion y vt111 por la contraseña que vallan a utilizar esto hara que el agente solo tenga que insertar su usuario y contraseña del agente.
Ralf_z3
edit the file /usr/share/astguiclient/mysql_tables.sh with your favorite editor
paste this:
| Code: |
| #!/bin/sh
# this shell script finds all the tables for a database and run a command against it DBNAME=$2 printUsage() { doAllTables() { # loop through the tables and optimize them if [ $# -eq 0 ] ; then case $1 in |
do the following commands:
