ECHI Converter

Get Version

0.3.2

→ ‘echi-converter’

The ECHI (External Call History Interface) Converter

Provides a Ruby based utility for fetching Avaya CMS / ECHI files in binary/ASCII form from an FTP server, converting them, if necessary, to ASCII and then inserting them into a database via ActiveRecord.

Status

This is the beta release now in production use within Call Centers using Avaya CMS. The utility successfully and reliably imports the data provided by the Avaya CMS ECHI into various databases, including Oracle and MySQL. This provides the repository of call segments that may then be used to provide detailed Cradle to Grave reporting for the call center.

Features

The utility provides the following capabilities:

  1. Support of ActiveRecord (means you may use Oracle, MySQL, MS-SQL, Postgres, DB2, etc)
  2. Generate your schema via ActiveRecord Migrations
  3. Fetch Binary or ASCII CSV files from the Avaya CMS platform via FTP
  4. Convert from the defined Binary format to ASCII
  5. Insert the records into the defined database table using database transactions, via ActiveRecord, on a per file basis to support recovery on failure
  6. Change schema structure via YML configuration file to accommodate various releases of the ECHI format
  7. Supports inserting agent names from agname.dat
  8. Runs as a daemon (via fork) on *NIX and a service on Windows
  1. Table names:
    1. echi_records – stores all ECHI data
    2. echi_logs – stores a log entry for each file processed
    3. echi_agents – stores the data from the agname.dat file

Requirements

  1. Ruby v1.8.6+
  2. Rubygems v0.9.4+
  3. ActiveRecord v1.15.3+
  4. ActiveSupport v1.4.2+
  5. Daemons v1.0.7+
  6. FasterCSV v1.2.0+
  7. Rake v0.7.3+
  8. UUIDTools v1.0.1+
  9. Win32-service v.0.5.0+ (Manual install for Windows only)
  10. Hoe v1.2.2+

Installing

sudo gem install echi-converter

or

gem install echi-converter

Setup

First, create the directory with all of the project files where you will run this application from:

echi-converter create myproject

Once you have installed a project into your preferred directory, you then need to configure for your environment. The first step is to modify each of these files:

  1. config/application.yml
    1. Change each of the ‘echi’ settings for connecting to your local FTP server where the CMS puts the ASCII/binary files
    2. Select which schema you would like to use (ie – extended_version12.yml) based on what you have in place
  2. config/database.yml
    1. Change to match your local database and database login credentials, full ActiveRecord support

Once this is complete, then simply run these commands from the project directory:

  1. rake migrate (creates the tables required for the system)
  2. echi-converter (starts the server daemon, refer to its usage)

Note: When using a Windows FTP server, you must configure the FTP server to provide a UNIX directory listing format

Usage

  1. echi-converter create myproject – create the local project to run the ECHI converter from
  2. echi-converter upgrade myproject – location of project to upgrade after a new gem is installed

For *NIX:

  1. echi-converter run myproject – Run the ECHI converter interactively from the location given
  2. echi-converter start myproject – Start the ECHI converter in daemon mode from the location given
  3. echi-converter stop myproject – Stop the ECHI converter daemon
  4. echi-converter restart myproject – Restart the ECHI converter
  5. echi-converter zap myrpoject – If there has been an unexpected close and the system still thinks the converter is running, clean up the pid files

For Windows:

  1. echi-converter install myproject – install the service (must specify complete path such as c:\path\to\my\project – if the directory name or path has any spaces, please enclose the “myproject” in double quotes )
  2. echi-converter start – start the service
  3. echi-converter stop – stop the service
  4. echi-converter pause – pause the service
  5. echi-converter resume – resume the service
  6. echi-converter status – returns the status of a configured service
  7. echi-converter uninstall – uninstall the service
  8. echi-converter delete – delete the service”
  1. If you would like to run the script interactively, you may also execute this command:
    1. ruby “c:\myproject\lib\main_win32.rb”

Demonstration of usage

Start the daemon/service:

echi-converter start myproject

Stop the daemon/service:

echi-converter stop myproject

Screencast

You may view the screencast on howto install and use the ECHI-Converter here.

Forum

Google Groups – ECHI Converter

How to submit patches

Read the 8 steps for fixing other people’s code and for section 8b: Submit patch to Google Groups, use the Google Group above.

The trunk repository is svn://rubyforge.org/var/svn/echi-converter/trunk for anonymous access.

License

This code is free to use under the terms of the LGPL license.

Contact

Comments are welcome. Send an email to jason [at] goecke.net.

Dr Nic, 5th November 2007
Theme extended from Paul Battley