Avaya IR Install and Troubleshooting Guide - Avaya Support

Migrationetc/init.d/etc/init.d/nfs.server stop/etc/init.d/nfs.server start2. Enter the following command:share -F nfs /3. Mount the Solaris shared directory from the legacy platform.4. After files are moved, run unshare.Migrating speech filesThe Avaya IR platform supports only the G.711 protocol for speech files. To support this, themigration process converts currently supported speech formats on CONVERSANT platformsto PCM64 which follows the G.711 protocol. The G.711 protocol is the international standardfor encoding telephone audio on a 64 kbps channel. It is an ITU-T compliant, pulse codemodulation (PCM) scheme operating at a 8 kHz sample rate, with 8 bits per sample.Avaya pre-recorded speech packages have been converted and ported into the Avaya IRbase software. They are not part of the migration process.To migrate speech files to the Avaya IR platform:1. Ensure that the source ADPCM speech files are placed on a CONVERSANT system.2. On the CONVERSANT system, run/mtce/bin/vis2wav -l –e 16 1036 1036.wavWhere /mtce/bin/vis2wav is a standard utility found on all V8 systems, 1036 is the sourceADPCM CONVERSANT speech file, and 1036.wav is an intermediate file created asoutput from the vis2wav.3. Transfer or ftp the intermediate 1036.wav file to the new Avaya IR platform that is loadedwith NMS software and utilities.4. On the Avaya IR platform, runvcecopy 1036.wav temp.wav -c10Where 1036.wav is the intermediate file generated on the V8 platform, temp.wav is outputfrom the vcecopy command and is in final G.711 format suitable for the Avaya IR system.Note:The vcecopy command keys off the .wav extensions so make sure to includethis file extension.5. Remove the .wav extension from the file name and rename the file back to its originalname or a new name.Issue 3 March 2003 55