Remote Upgrades on Fedora based Systems

I’m doing a remote upgrade on a test server at work(VoiceIP Solutions). So today’s article will cover upgrading from Fedora 6 to Fedora 10. Before you start, backup any important data! Every once in a while some dependency issue will crop up that blows up your server.  Also upgrading from Fedora 6 to Fedora 11 is not as easy as say, upgrading from Fedora 10 to Fedora 11.  So be careful and upgrade on a regular basis!

The Goals of this Post:

– remote upgrade from Fedora 6 to Fedora 10



Install Queuemetrics Call Center software for Asterisk on Fedora 10

What makes Asterisk so great is the growing ecosystem of 3rd party software.  For call centers based on Asterisk PBX, the best on the market is Queuemetrics.  This solution allows for over 150 different statistics to be collected.  Here is just a few:

Number of calls
Total call length
Average call length
Average call waiting
Number of unanswered calls
Average time before disconnection
Area code
Number of calls
Total calling time
Average time per call (for taken calls)
Average wait per call
Average position at disconnection (for lost calls)
Number of available agents
Total agent time
Average agent time
Minimum/ maximum agent session duration
Agent availability

If by now you are not convinced take a look at the complete list; you can check out Loway’s site and Queuemetrics here.  I have personally helped setup several commercial call centers(while working for VoiceIP Solutions) with this software and I am impressed at the value and support for our customers purchase.  So today we are going to set up a basic Queuemetrics installation; we will not be covering the Asterisk portion.  Nothing fancy here, but I can get you started.

The goal of this post:

– install Queuemetrics



Fedora Core 7 Xen Paravirtualized Guest Install

NOTE: I myself am a novice with Xen. This setup worked well for me, but I cannot guarantee results. I came across several hurdles and have worked through most issues. I hope this document helps. Please click on my adds, they help pay for the hosting. Thanks and enjoy.


This is a standard fedora 7 installation with current yum updates; in this setup we have two interfaces. One interface(eth0) provides ethernet connectivity to Dom0 (the master domain from which guest are created). The second interface, is for connecting to the paravirtualized guest. Both network cards are plugged into the same switch.

We will use the standard fedora linux networking mechanism rather than letting xen setup up our interfaces. The advantage to this is that we can easily set up multiple NIC’s, connected to Different LANs with separate firewall rules configured by the individual paravirtualized guest.


Intel Super Micro mainboard

Intel Corporation 82566DM-2 Gigabit Network (does not work with xen kernel 2.6.21-7.fc7xen)

– added 3com 3c905 100BaseTX ethernet card

– added Realtek RTL-8139/8139C/8139C+ ethernet card

Intel(R) Core(TM)2 Duo CPU E6550@2.33GHz


kernel 2.6.21-7.fc7xen

Step 1: Install libvirt and virt-manager

[root@mattcom1 ~]$ yum install libvirt


[root@mattcom1 ~]$ yum install virt-manager


Step 2: prepare installation media

Now we have to create a fedora 7 source tree for installation. One caveat, that I didn’t get at first was how to create the Fedora 7 source tree. The virt-manager tool will expect a standard source tree setup, but doesn’t tell you what that is…

I chose to install from the http, but failed when I copied the files from the Fedora DVD. After some googling I found that the directory for your web server needs to be exactly like this, ‘<files from the fedora dvd>’. Believe it or not, it wouldn’t take the install files in any other directory structure.

In Fedora 7 the default apache web root is ‘/var/www/html/’. So your full path will look like this ‘/var/www/html/fedora/linux/core/7/i386/os/<files from fedora DVD>’. It took me a while to find this information online…

step 3

I like to use the virt-manager to create guest machines. virt-manager is a graphical interface for libvirt. Libvirt is an API for interacting with Xen and other hypervisors. It is defiantly buggy though. Libvirt and Many times I’ll shut down a guest and the virt-manager still shows it running. If this happens do:

[root@mattcom1 ~]# service xend restart
[ OK ]

Then virt-manger will be fine. One other thing, virt-manger has a built in VNC client, but in my testing it failed. More on that later.

Written by mattb in: Uncategorized | Tags: , ,