000webhost

Web hosting

Friday, December 2, 2011

Virtualisation Options

If you grew up several decades ago, then you would know the impact that vritualisation has played in both the server as well as the desktop space. It has allowed companies to reduce the total number of physical servers within the network while also allowing for extra capabilities such as high availability, redundancy, clustering and so on. It has also allowed private users to experiment with a multitude of different operating systems and applications without having to possess a expensive, high-end hardware in your home network.

Of late, I've been working on a project that requires the evaluation of current software based Unified Threat Management (UTM) devices. Obviously, I've tried using the usual suspects in terms of virtualisation such as VMWare, Xen, VirtualBox, Hyper-V, Proxmox, and VirtualPC, in both Type 1 and Type 2 hypervisor format.


However, I've found the most versatile for my needs has been, 'VMWare Server'. It can sit as an application on top of an existing Operating System, it can run other 'Hypervisors' within itself (such as XenServer and ESX/i), virtual hardware is reasonably easy to add/remove/configure, and there are reasonable logs and diagnostic messages for when and if a problem arises.

That does not mean that it is not without its 'quirks' though. Due to the way 'virtual networks' work you'll need to set read/write permissions on relevant /dev/vmnet? device files in order to achieve promiscuous mode automatically (this can also be achieved by setting them up manually using the 'promisc' option with the 'ifconfig' command and while 'iptraf' does provide the option the various /dev/vnet? device files do not seem to show up as options).


Switching to a singular technology can also lead to unusual consequences during 'changing times'.


I personally experienced a strange issue of sorts with VMWare whereupon switching between the various NIC modes (host/NAT/custom/bridge) would not take effect when using a particular VM appliance but did using others. The only way to get around it was by re-creating the VM.

Note, that in many cases performance and functionality of guest Operating Systems can be increased through add-ons such as VMWare Tools and third-party tools. Also, there may be a significant performance overhead/hit depending on your existing setup.


Not surprisingly, hardware technology has made significant strides towards commoditisation in consumer class hardware. In most cases, modern CPU's will have such capabilities built into their existing architecture. I used to use upgraded Dell Optiplex GX280/GX520 desktops because they were smaller, consumed less power, and were quite simply quieter. If you don't have specific, 'Whitebox Virtualisation Hardware' though there are options available should you wish to customise ESX/i or provide enhanced driver support.



at
Labels: ,

Friday, November 25, 2011

Server Auto-Configuration

If you've ever been involved with Linux Server Administration than you'll be more than aware of the many and varied automation/configuration options out there such as 'Chef', 'Babushka', and 'Puppet'. I've recently been working on similar technologies but to better comprehend and implement them I've had to review how the current systems work and their capabilities.

'Puppet' seems to operate in a client/server architecture using so called 'manifests' which are basically a set of instructions pertaining as to what actions you would like to complete. For instance, the remote installation of a package, the creation of a file, the setting of a certain set of permissions and so on. The 'manifests' themselves are then compiled (checked for syntax and other errors) and then applied to relevant 'nodes' within your network. Due to its relative maturity it is often available in most of the popular distribution repositories.


'Chef' has obviously been more Debian orientated. It took a while before I actually found a set of RPMs for my system. Prior to that though, I tried creating RPMs using the GIT repository with a set of autobuild 'Ruby' scripts. However, due to the state of the respositories of the time the build seemed to be broken. I used this as a learning opportunity with regards to RPM packaging (I used to create DPKG packages years ago for another project and have done some minimal RPM packaging. DPKG are basically 'ar' and RPM are basically 'cpio' archive files respectively if you're curious (much like the ZIP and other archival format)). I didn't do any research prior to testing my theories prior to test my problem solving abilities. Basically, symlinks aren't a viable means of dealing with naming issues in packaging.  Copying files/directories (though this would violate best practice) and changing of version strings in the SPEC file are the more 'valid' option. As indicated in the SPEC file itself RPM is very 'Makefile' like in the way that it is structured. In fact, if you've ever written a 'Makefile' you'll be very much at home. Use 'rpmlint' in order to check for possible problems, 'rpmdev-extract' to extract a SPEC file from an existing SRPM, and 'rpmbuild' with relevant options in order to build an installable RPM.


Obviously, I found a relevant repository later on but it was very interesting getting a better idea of the process of creating RPMs. Check out 'alien' and 'checkinstall' if you have time which, by the way is an easy manual Perl install if you can't find the required package for your distribution. There is a web based interface that seems fairly sparse, a Command Line Interface (CLI), as well as what seems to be an extensive set of online 'recipes' to allow for all sorts of remote configuration, with support for Perl as well as support for automated provisioning of servers. Note that this extra functionality seems to come at the cost of some simplicity. There are a myriad of tools that are used, certificate systems that need to be setup, and unlike 'Puppet' you will definitely need to read through at least the Quick Start documentation in order to use it. Even then, the instructions make extra assumptions... Also, as with any other large, complex Open Source project its in constant state development and may have 'issues' from time to time.


'Babushka' seems to be a work in progress and feels like a stripped down version of a more complete configuration management system. Even the documentation is incomplete at this stage. However, it deals with most of the more important issues such as remote installation of packages, dependencies, and remote configuration.


If none of these options appeal than its fairly easy to build a custom configuration/automation system using Python's 'paraminko', Perl's 'Net::SSH', and Ruby's 'Net::SSH' libraries.


http://www.openvas.org

- as usual thanks to all of the individuals and groups who purchase and use my goods and services
http://sites.google.com/site/dtbnguyen/
http://dtbnguyen.blogspot.com.au/
at
Labels: , , ,

Wednesday, November 9, 2011

IPTables Review

With all manner of configuration (CLI as well as GUI based) tools available to us now with regards to firewall configuration sometimes its hard to justify learning or knowing raw IPTables rules. Recently, I had to do some revision for a project that I've been working on (it involves automated generation of firewall rules). Some of the materials that I used included the following.

http://firehol.sourceforge.net/fwtest.html?

- as usual thanks to all of the individuals and groups who purchase and use my goods and services
http://sites.google.com/site/dtbnguyen/
http://dtbnguyen.blogspot.com.au/
at
Labels: , , ,

Software Design Patterns

I recently picked up a book on Java certification (it was on sale). Obviously being Java there was a lot of coverage with regards to OOA, OOD, OOP, UML and so on. One of the more interesting sections was regarding was so called, 'Design Patterns'. Basically, a while back some computer scientists discovered that often certain problems/programs followed a similar pattern. Moreover, you could use these (as long as you recognise and are aware of them) patterns to reduce time/effort spent on designing/building new programs by using templates of these patterns. These templates ultimately became known as 'Design Patterns' and cover everything from development of GUI applications to layout of elements on a webpage.

http://c2.com/cgi/wiki?DesignPatterns

- as usual thanks to all of the individuals and groups who purchase and use my goods and services
http://sites.google.com/site/dtbnguyen/
http://dtbnguyen.blogspot.com.au/
at
Labels: , , ,

Playing With an Android

While Windows is not the most secure Operating System in the world its certainly the most convenient. I used to install literally everything that came off the cover discs of magazines just to see what they were like simply because installation/configuration/removal was so simple. The Internet opened up the world even further. Over the last few years, 'smartphones' have become increasingly popular and tweaks/mods have made them almost as functional as desktop computers. My first foray into the Android world was a HTC Tattoo. To really exploit its capabilities though I've been exploring the the Android ADK/SDK (note that the 'HTC Dream Composite ADB Interface' driver is required for you to work with ADB and you'll need to have the 'Android ADK/SDK Platform-tools' package installed for you to do anything really interesting). Its essentially a Linux/UNIX platform with a suitable GUI on top and you can install all the same types/classes of programs that you would otherwise do on a fully fledged computer. The real difference is that unlike a lot of other platforms this one has basically been made for 'tweakers' and as such development of complementary software/hardware is significantly higher than most other platforms that I've come across. In fact, interfacing with the real world via robotics is easily possible via off the shelf kits at your local electronics store.

at
Labels: , , ,

Tuesday, November 8, 2011

HP Pavilion dv2000 Laptop Troubles

One of the things that I like to do in my spare time is tinker with computer software/hardware. Recently, I came across a product design/implementation that I thought should never have occurred/existed. Perhaps it was a one in a million case but based on my research it wasn't. It was a HP Pavilion dv2000.

Based on what I was told the working system was left in storage (inside a house so thermal/weather issues shouldn't have really been an issue) and hadn't been touched in several months. When it was turned on, all the LED's lit up but the machine didn't seem to 'boot'. There was nothing on either the LCD or an external monitor. Research and intuition thought that it had something to do with the discrete graphics chip (Nvidia) but I couldn't be sure until I had opened/examined the machine.

If you've ever opened up a laptop you've probably figured out that it is a pain and they often have design compromises with regards to accessibilty, cooling issues, and so on. A tip for those who attempt to disassemble this machine, go for the top/middle screws, then attack the left side of the top panel first and then attack the right hand side of the top panel after turning the screen towards you temporarily (you'll understand why if you ever try this). Then remove the keyboard and finally separate the main shell/panels after removing the relevant screws.

When I finally took a closer look at the graphics chip and the connection to the mainboard I noticed that some 'balls' were completely flattened and obviously could not have been connected to the mainboard. Moreover, some balls ended up being in contact with others. Removal/reshaping of damaged balls was obviously a possibility but as I've previously discovered (and documented in this blog) 're-flowing' is only a temporary solution. A 're-ball' is the only real medium/longer term solution since its an inherent design fault that never should have existed.


Obviously, I tried a re-balled mainboard. However, after re-connecting everything I discovered that the lid switch which is used to detect when to suspend the notebook was dead which led to backlighting issues and is another known design fault with this particular notebook. While a fix is possible longer term it is likely to fail anyhow and the ability to hibernate can still be accessed by using the power button. Research indicates that the 'best solution' is bypassing the problem by merely disconnecting the lid connector to the mainboard.


At the end of all of this I discovered that the power switch wires had come loose. I didn't realise was how fragile something like this was and how difficult it was to solder using a general purpose iron (though I eventually got it). From a practical perspective the wires are too small to strip easily (unless you have specialised equipment). In fact, I used small nail clippers! Thereafter, you'll notice that you must apply a coating over the wires in order for the connection to remain stable after re-assembling the laptop. I tried liquid electrical tape but while it is a good insulator it isn't as strong you would really want. Moreover, there are time issues associated with drying/curing.

Normal tape is possible but I found that it lacked 'adhesive power'. I finally tried, 'industrial strength adhesive tape'. It reminds of 'gaffa tape' but is more pliable making it easier to fit around gaps and wires. Personally, it feels like a cross between liquid adhesives and tapes. Brilliant stuff and but not as thick as 'gaffa tape' which may cause panels to be slightly out of kilter when re-assembling the machine.


Once the laptop was re-assembled you may find that device drivers may need to be updated. I discovered that I needed to manually force the Conexant HD Audio drivers to be used in order for them to work. Windows/software based hardware auto-detection just didn't work.

- as usual thanks to all of the individuals and groups who purchase and use my goods and services
http://sites.google.com/site/dtbnguyen/
http://dtbnguyen.blogspot.com.au/
at
Labels: , ,

Monday, October 31, 2011

SNMP Monitoring

Recently, I've been working on a project which involves remote monitoring and configuration of server and network devices. Obviously, my research has led me to further discover the intricacies of the SNMP protocol and agents which can often provide extensive monitoring and configuration capabilities.

I've obviously been looking at native and third-party, proprietary and open source, SNMP agents for Windows and Linux. No doubt, configuration parameters can vary drastically depending on the information and level of configurability that you desire but they all rely on similar concepts and use similar vocabulary. These concepts are best outlined in the following locations.


The best example of its structure is probably represented by the following picture.


It will most likely remind you of postal addressing systems, directory service hierarchies and other hierarchal structures such as those used by Domain Service System (DNS) with each level being represented by numbers and/or shorthand strings. At the end of the hierarchy is a string/counter/number which represents the value of the concerned attribute of the piece of hardware and/or software in question at any point in time. These attributes can range from the name of the installed Operating System, to the total number of bytes sent on a particular Network Interface Card (NIC).

Based on the intent on my project it seems clearer that using SNMP as a basis for monitoring may be overkill (though I'll add some SNMP functionality). While it allows for a more finer grained image of the situation, it is also clear that much of this information is redundant especially when you are using 'generic hardware' (whether it is server and or desktop class). As such, it becomes more obvious the reasoning behind extensive templates that often accompany more mature monitoring systems such as ZenOSS, Zabbix, and Dell OpenManage.

While it is clear that SNMP is a useful and mature protocol there have clearly been moves to modernise it (for instance, through enhanced security, accessibilty, and configurability) and there are alternative technologies such as Link Layer Discovery Protocol (LLDP) and Cisco Discovery Protocol (CDP).

http://www.networking-forum.com/blog/?p=662

- as usual thanks to all of the individuals and groups who purchase and use my goods and services
http://sites.google.com/site/dtbnguyen/
http://dtbnguyen.blogspot.com.au/
at
Labels: , , ,

Friday, October 21, 2011

NVIDIA Laptop Graphics Chip Repair

Sometimes you'll encounter a continuing problem over and over again. One of the ones that has come to light for me has been related to discrete NVIDIA graphics chip on laptops (across multiple brands believe it or not including HP, Compaq, Dell, and Apple) which have revolved around excess heat not being dispersed adequately which means that over time the graphics chip can come away from the logic board. A lot of the time this results in an unbootable laptop with the following symptons, power and LED indicator lights turn on accompanied by a black screen. Even though there has been a partial recall of affected laptops there are many 'out in the wild' which still have the same problem.

While conventional solder and mechanical pressure can be used as a means of providing a medium to long term fix on traditionally packaged and attached chips this is not the case with Ball Grid Array (BGA) graphics chips which seems to be a more popular methodology moving forward.

However, the probem is when you have mounting issues they aren't so easy to fix if you don't have the required, proper equipment required in order to complete the job. Moreover, often taking it to a 'professional' may cost the same amount as a new laptop/logic board. Numerous accounts online of this particular problem and some creative and unusual solutions have been proposed that are more 'cost effective' (but are also shorter term fixes). Some of these include:

- stripping down the machine down to the logic board and then 're-flowing' it by putting it in a convection oven or even using direct heat such as using a butane torch
- wrapping it in insulating material, turning it on and using the laptop's own heat in order to 're-flow' the connections
- using direct heat and a BGA kit in order to remove the damaged chip from the logic board, the 'balls', and then using the included solder balls (often of higher quality than the original) to fix problem areas

However, one thing I have been considering is whether or not it is feasible to attempt another solution. Namely, creating the solder balls themselves (too difficult on a large scale), or else using solder wick in order to clean up damaged BGA balls and then using flux gel in order to crudely create 'balls' between the graphics chip and the logic board. While I have been able to partially resurrect one board with this method I'll need more time to determine whether or not whether it is a complete long term fix...

at
Labels: , ,

Thursday, October 20, 2011

VERITAS Backup Exec Research Notes

The following represents some notes that I compiled while researching VERITAS Backup Exec (a commercial backup software solution that has since been purchased by Symantec). Obviously, these notes are based on an older version of Backup Exec so use your discretion.

Intro to Backup

Murphy's Law
SLA - Service Level Agreement
Full - complete copy of all files
Incremental - only files changed since last backup
Differential - all files changed since last full backup
Online Backup - everything accessible all the time
Nearline Backup - data from backup periodically archived to secondary backup server. Requires minimal effort to restore backup to main
Offline Backup - files unavailable during backup

Disaster Recovery Technologies : Hardware

Tape - linear, cheap, high storage capacity density
Hard Drives - less mobile, medium price per unit storage capacity,
Portability
Price
Network Bandwidth
Removable Disks - portable
Optical Media - cheap, portable,
NAS - relatively inexpensive now, RAID
SAN - can be expensive

Disaster Recovery Technologies : Software

Server-based Backup - server/administrator determines backup configuration
Client-based Backup - client/users determines backup configuration
Frozen Image Backup - live snapshot of files possible
SAN-based Backup - backup to SAN
LAN-free Backup - typically uses a SAN to backup using a dedicated Fibre connection
Server-free Backup - client system/software initiates the backup. Stored to tape/SAN

Applying Technologies : Client-based system

One computer
Software Choices
Backup Program on Each Machine
Backup client on each machine with a single, central backup server
Backup Program on Each Machine - often OS includes basic backup capabilities. Free options available but they often from lack of support, flexibility, and robustness
Client Controlled on a Network - user configuration, schedule, backup server stores on tape. User configuration uncommon because users want to backup everything, most users aren't technially aware eough, and most administrators want a consistent environment
Scheduling
Backup Jobs - sometimes also called policies
Generic Troubleshooting - hardware and/or software issues, test partial/complete backup and restores

Applying Technologies : Network-based System

WAN/LAN - primary difference is physical distance between systems
Server-based Solutions - most are server based with a administration utility
Heterogenous Environments - most commercial solutions now have the ability to operate across multiple platforms by using an 'agent'
Replication - latest copy and transparency during failure but server/bandwith requirements are greater along with extra resources for extra hardware/server. Run-Time Vs Traditional Vs Frozen Image backup
Scheduling Issues - timezones, resource consumption, mutual exclusion
Networking Utilization Issues - schedule during off hours, hard to schedule in a genuine 24/7 environment though
SAN Solutions - cost, compatiblity, configuration
Tape Sharing - shared tape drives, tape libraries, robotic libraries
Tape Rotation - saves from wear, space by not having irrelevant backups; schemes include daily, GFS (Grandfather-Father-Son), Tower of Hanoi
Looking Ahead in Backup Technology - increased sophistication/capacity of tape solutions, maturation of disk solutions, NAS/SAN technologies continue to evolve, new technologies will come into existance

Introduction to Backup Exec

Single and Multi-Server Editions
Remote Agents - best to check support for your OS prior to evaluating/purchasing
Autoloader/Robotic Library Support
Library Expansion Option (LEO)
Advanced Open File Option (AOFO)
Backup Options for Various Databases - MS Exchange/SQL/Sharepoint, Oracle, Lotus Domino, SAP
Intelligent Disaster Recovery (IDR) - known as bare metal restore now, involves a scripted installation of a minimal OS and then restoring to some initial configuration/restoration point from there
Shared Storage Option (SSO) - used by various servers/systems to access the same medium

Backup Exec Installation : Suggestion and Pitfalls

Install latest Service Pack/Patches
Update Microsoft Data Access Components (MDAC) - OLEDB32.dll
Update Microsoft Installer (MSI) - MSI.DLL
Check HCL/System Requirements
Try to have dedicated chain/channel for the storage/backup medium
Security Considerations - use the account that was automatically created, don't try to customise it as it can result in strange permission errors

Getting Your Hardware to Get Along with Backup Exec

Drive Pools - drives from the same server
Cascaded Drive Pools - used to deal with when normal drives can't deal with size of backup. Responsibilty of backups fall to these particular drives if the normal drives pools are unable to
Hardware Configuration Problems - determine whether it is a program, OS, BIOS issue. Use the built-in Wizard to try solve other issues
ADAMM (Advanced Device and Media Management) Log
Install drivers (all drivers in one package) from website if necessary, http://support.veritas.com
BEUTILITY.EXE - to reset hardware tracking databases, BEDB.MDF/BE_DLO.MDF
Database Catalogue - backup jobs, media set information, hardware statistics, automatically backed up after 24 hours of programs/services running
Physical Issues - BIOS, Power Cycle (server and media drives), physical connections

Media Rotations

Overwrite Protection - to stop media from being overwritten prematurely
Append Period - stops any data from being appended to media at all as opposed to overwritten
Media Sets - set of media based on overwrite/append settings
Retired/Scratch/Imported Media
Retention
Time-to-Recovery - balance between time/convenience/cost
Granularity - frequency of backups

Backup and Restore

Shadow Copy Components - System State/User Data/Service State
Remote Selections - will remove redundant data from backup selection by default
The Remote Agent for Windows Servers (RAWS) - must be installed on remote server to complete remote backup, can be installed by going to Tools > Serial Numbers and Installation or running setupaa.cmd
The Advanced Open File Option (AOFO) - must remove Remote Agent if already installed otherwise just install AOFO and it will install RAWS as well
Backup Performance - Avoiding Bottlenecks
Advanced Backup Options
Pre- and Post-Job Commands - run custom scripts
IP-only backup - as opposed to NETBIOS addressing/resolution
Backup Folders - backup to an arbitrary folder (NAS/SAN) rather than media
Hierarchical Storage Management (HSM)
Test Runs

An Introduction to Using Backup Exec with Other Platforms

Microsoft Exchange - allows for "brick level" backup of mailboxes
Microsoft Outlook - need to install MAPI compatible email client on media server (normally Outlook). Backup Exec logs in each user individually and downloads all emails to allow for "brick level" backup
Information Store - Backup Exec uses ESEBCLCLI2.DLL or EDBBCLI.DLL (Exchange 5.5) to communicate with Exchange
Types of Exchange Database Backups - Full/Database&Logs (flush committed logs), Incremental/Logs (flush committed logs), Differential/only transaction logs, Copy/same as Full (none of the transaction logs are deleted though)
Microsoft SQL Server - SQL Enterprise Manager must be installed on media server.
Types of SQL Database Backups - Database (backup everything along with transaction logs), Log (backup only transaction logs and delete old transaction logs from database), Log No Truncate (same as Log but does not delete old transaction logs from database), Consistency Check Before Backup (check database consistency before backup. This may cause a performance hit on a high transaction/traffic server though)
UNIX and Linux - be_agnt.tar

- as usual thanks to all of the individuals and groups who purchase and use my goods and services
http://sites.google.com/site/dtbnguyen/
http://dtbnguyen.blogspot.com.au/
at
Labels: ,

Wednesday, September 28, 2011

Filesystem Corruption on Android

In spite of dramatic improvements in filesystem technologies, corruption is still an issue that continues to this day in computing whether it be on the desktop and/or on more portable devices. Recently my Android based phone endured something along these lines. A number of folders had become files and there were randomly named files spread throughout the filesystem on the SD card with unreadable characters. Research indicated that this was a problem that has been experienced before by others (though the type of corruption often varies).


Luckily in my case, all important data was still retained but it was still disconcerting to say the least. The way I dealt with it was by connecting my phone via USB to my laptop and set the connection to run in mass storage mode. Thereafter, I ran 'Scandisk' (FAT32 filesystem is used on the SD card) in order to determine the causes and hopefully create the fixes required in order to achieve filesystem consistency. Obviously, it would store the files in various CHK files. Still had permission errors though. Upon further examination certain directories seemed to have have become files which resulted not being able to save files from camera shots for photos (DCIM) or wallpapers (Wallpaper). By manually recreating the relevant directories and copying back the relevant files to the relevant data directories you could restore most data. By using the built-in image viewer you could regenerate relevant metadata. Obviously, I'm still looking for a more elegant solution that can be built into the device itself.

http://www.brighthub.com/mobile/google-android/articles/37151.aspx

- as usual thanks to all of the individuals and groups who purchase and use my goods and services
http://sites.google.com/site/dtbnguyen/
http://dtbnguyen.blogspot.com.au/
at
Labels: , , ,

Monday, September 5, 2011

Open Source PBX Evaluation

A while ago I had to do evaluation of PBX systems for a company after we discovered that we didn't have enough bandwidth between two offices to offer guaranteed quality of service during peak data transfer times. These are some of the notes from that particular evaluation. Note, that this data may be invalid since the actual evaluation was conducted about a year and half ago from the data of this particular post.

- Trixbox/FreePBX/Elastix/AsteriskNOW/SwitchVox have been evaluated
- apparently custom contexts module for Elastix is in beta and has to be custom installed, http://www.freepbx.org/support/documentation/module-documentation/third-party-unsupported-modules/customcontexts
- http://mirror.freepbx.org/modules/release/contributed_modules/ Had to update to latest version of software as old version didn't seem to pick up existing settings from within our current phone network well. New version seems a little funny. Had to setup in unembedded FreePBX, then check in Elastix PBX section and apply, then go back into FreePBX before outbound routes were picked up correctly...
- VMBlast is a module that will allow you to leave voicemail for multiple users in your system, http://www.trixbox.org/forums/trixbox-forums/help/info-vmblast-please
- To install a new module in FreePBX basically download it, extract it, then within the web inteface go to unembedded FreePBX, 'Modules Admin', Install, Process, Confirm
- http://code.google.com/p/teletorture/ Telemarketer Torture module for FreePBX, generates a destination for inbound calls in FreePBX which you may send unwanted callers to Module created by James Finstrom
- Outbound Routes, Dial Patterns
NXXXXXXX
- ZAP, Dial Rules
03+NXXXXXXX
0392123+NXX
0N+NXXXXXXX
XXXXXXXXXX
0011+ZXXXXXXXXX
- AsteriskNOW, think of FreePBX on a stripped down version of Linux that is fast to install. Reminds me of LiveCD produced by Xorcom in order to test connectivity to their devices. http://www.xorcom.com/downloads/live-cd-quick-start.html
- non-critical bug in Trixbox installer. kmod does not require kernel... interesting that they've opted to go for text based installer as opposed to full blown GUI
- Trixbox have apparently setup their own init.d like start-up system, /var/trixbox_load/firstboot/
- builtin functionality to allow for reboot when no active calls are going
- true web based tick and upgrade system that will allow us to pursue more finer grained control than was previously possible with all in one support packages
- interesting that they should choose to go with phpconfig rather than a complete brand new interface for their file configuration
- SwitchVox is very slick but may end up being beyond our budget considering the number of phones in our system, http://demo.switchvox.com/admin
- http://www.freepbx.org/download-freepbx redirects to Asterisk NOW for live test CD
- http://www.freepbx.org/support/documentation/installation, installing FreePBX on various systems
- http://support.freepbx.org/book/export/html/31

- as usual thanks to all of the individuals and groups who purchase and use my goods and services
http://sites.google.com/site/dtbnguyen/
http://dtbnguyen.blogspot.com.au/
at
Labels: , , ,
Subscribe to: Posts (Atom)

List Biggest Employers in New Zealand, Random Stuff, and More

#################### START new-zealand START #################### !!!!!!!!!!!!!!!!!!!! DATE Thu 13 Aug 12:54:23 AEST 2026 DATE !!!!!!!!!...