Installing the Asterisk GUI

Asterisk 1.4 includes an HTML Asterisk GUI (well, it’s more of a package for the creation of GUIs) by Digium. Installing it is quite easy once you have installed Asterisk 1.4 itself - see node Compiling Asterisk 1.4 beta. The GUI is a nice AJAX app that will run through the Asterisk embedded web server with a recent web browser. The first thing you’ll have to do is to download the GUI, currently through Subversion only:

svn checkout http://svn.digium.com/svn/asterisk-gui/trunk asterisk-gui
don’t worry if it takes a while to get this started, just let it run until the package is downloaded.
cd asterisk-gui/
make
make install
make samples
Before the package can start, you’ll have to change a few things in your Asterisk: Continue Reading...



Compiling Asterisk 1.4 beta

If you want to check out what the buzz about the new Asterisk 1.4 is, there is one thing you got to do - download it and install it on your box. The compilation procedure is a bit different from the one of Asterisk 1.2, so we thought a brief tutorial would be helpful. As a point of reference, we imagine you’re going to build your new Asterisk on a machine preinstalled with TrixBox; this means your machine is very easy to reinstall from scratch if anything goes wrong. This also means that you can start playing with Asterisk 1.4 in a virtual machine, so you have no risk. The first thing you have to do is to create a working directory for Asterisk (say /src/asterisk14beta)and download the latest version of Asterisk 1.4 beta in it; we have used the following: Continue Reading...



Simple queue and agent debug monitoring

It may have happened to you: you get called by a busy call center to debug the functionalities of Asterisk, and you get lost in the continuous logging on the console done by tens of operators who keep on using the system. Asterisk produces a lot of information, but that very lot seems to be a bit discouraging for understanding what is going on. What we do now is automate some very simple filtering tasks so that we are not swamped anymore by unwanted information. Continue Reading...



Avoiding queue_log file rotation

If you run a call center, you will definitely want the log rotation susbsystem not to rotate your queue_log file along with the other Asterisk logs found in /var/log/asterisk. The queue_log file contains essential information on how the call-center is going that is being used by software like QueueMetrics to report on the well-being and the actual work being performed by your CC, and you surely want to keep that data in a safe place for cross-period analysis. The majority of prebuilt Asterisk distributions will instead lotate that file together with the other Asterisk logs, and this may cause lost data if you do not have a backup. Disabling log rotation Disabling log rotation is actually quite easy: go to /etc/logrotate.d and look for a file named asterisk. If you run TrixBox, you’ll find something like:

/var/log/asterisk/*log {
   missingok
   rotate 5
   weekly
   create 0640 asterisk asterisk
   postrotate
       /usr/sbin/asterisk -rx 'logger reload' > /dev/null 2> /dev/null
   endscript
}
There may as well be other sections where other files are rotated. You just delete the section above and the queue_log file will not be rotated anymore. What if my queue_log has already been rotated? Loway offers a script that makes it trivial to do the import without following the manual procedure - you’ll find it here: http://queuemetrics.com/manuals/QLoader-chunked/ar01s02.html Do an automated install using yum. Manual procedure If your queue_log has already been rotated, you’ll want to join the remaining pieces together. That’s very easy: Continue Reading...



Peering two Asterisk servers using IAX

It is quite easy to “join together” two Asterisk server using IAX. Unfortunately it takes a while to get things right by reading the docs, so here is a ready-made recipe that you can use to have two Asterisk box dial each others extensions. We imagine that we have two Asterisk boxen, called foo and bar. foo is at 192.168.1.2 while bar is at 192.168.2.3. Le’s start with foo; here is its iax.conf file:

[general]
bindport = 4569           ; Port to bind to (IAX is 4569)
bindaddr = 0.0.0.0    ; Address to bind to (all addresses on machine)
disallow=all
allow=ulaw
allow=alaw
allow=gsm
mailboxdetail=yes


[bar]
type=friend
username=foo
secret=password123
auth=plaintext
host=192.168.2.3
context=fromiax
peercontext=fromiax
qualify=yes
trunk=yes
This configuration means that on foo we can do Dial(iax2/bar/23) and this will call extension 23 at context fromiax on bar. Here is the meaning of the options: Continue Reading...



Day of Week Calculator

Day of Week Calculator //********************** // Calendar Functions (place in extensions.ael, requires 1.2) //********************* // Return the day of the week for any given date, 0=Sunday… // YY is (4) digit year // MM is (2) digit Month // DD is (2) digit Day // The day of the week is returned via ${Weekday} // Example Call: Macro(Calendar_Weekday,2006,05,14,${DayofWeek}) // Upon return ${DayofWeek} will contain the Weekday string. // macro Calendar_Weekday(YY,MM,DD,Weekday) { Set(wd=$((${DD}+1) + ${MM}2 + (${MM}+1)3/5 + ${YY} + {YY}/4 - ${YY}/100 + ${YY}/400) % 7); switch (${wd}) { case 0: Set(Weekday=Sunday); break; case 1: Set(Weekday=Monday); break; case 2: Set(Weekday=Tuesday); break; case 3: Set(Weekday=Wednesday); break; case 4: Set(Weekday=Thursday); break; case 5: Set(Weekday=Friday); break; case 6: Set(Weekday=Saturday); break; default: Set(Weekday=Unknown); }; }; Continue Reading...



Installing QueueMetrics using Yum

  • This recipe is EXPERIMENTAL - use it at your own risk!
Continue Reading...



UPDATING

We’re moving to a new server. Continue Reading...