ECHI Converter

Get Version

0.0.5

→ ‘echi-converter’

The ECHI (External Call History Interface) Converter

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

Status

This is the initial alpha release that will under go extensive testing in the coming weeks. Therefore it is recommended to wait for version 0.1.0 before any production use.

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
  6. Change schema structure via YML configuration file to accommodate various releases of the ECHI format
  1. Table names:
    1. echi_records – stores all ECHI data
    2. echi_logs – stores a log entry for each file processed

Requirements

  1. Ruby v1.8.6+
  2. Rubygems v0.9.4+

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)

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
  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

Demonstration of usage

Start the daemon/service:

echi-converter start myproject

Stop the daemon/service:

echi-converter stop myproject

ToDo

Items to be done to move this out of alpha stage:

  1. ‘echi-converter-create’ works fine with OSX/Linux, need to test validate with a Win32 platform

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, 17th August 2007
Theme extended from Paul Battley