Avaya IR Install and Troubleshooting Guide - Avaya Support

More documents

Recommendations

Info

Installation overview― Call Data Handler (CDH) data (flat files and database tables)― User logins― Host screen files• Identifies any features or commands on the pre-migration platform that are not supportedon the Avaya IR platform and logs the results.• Includes a plan of action for each item identified by the evaluation tool. The plan of actionfor unsupported features or commands varies based on the items identified by theevaluation tool.These activities prepare the customer data for the migration to the targeted platform. Forexample:• If speech files are found, they must be converted.• If an application has unsupported features, (for example, Brook Trout external functions),manual intervention is required.Unsupported features or commands identified by the Scanit tool can be addressed by:• Manual changes made to the application• Execution of a process to update the application• Exclusion of the application from the data to be migrated to the Avaya IR platform.After reviewing the action plans, the customer may update the applications to change orremove the unsupported features or may contact Avaya or their ISV to assist with thisprocess.Migration phaseThe migration phase includes data conversion and data transport activities. Data must betransported between platforms using a LAN connection. Upgrade procedures and activitiesfor pre-migration and migration occur on the originating platform.Post-migration phaseIn the post-migration phase, verify that migrated components have reached the targetedplatform successfully, without any errors. Update custom speech files and migratedVoice@Work and IRAPI applications.If a Script Builder application requires updates, update the application on the originatingplatform and then move it to the Avaya IR platform. The Script Builder development tool is notsupported on the Avaya IR platform.46 Avaya IR R1 Install and Troubleshooting Guide
MigrationAvaya supplied Enhance Basic Speech (EBS), IRAPI commands, DIPs, TAS scripts, andstandard external functions are not migrated because they are a part of the base Avaya IRsoftware.Unpacking the migration toolsThe migration tools and all related files are delivered to the customer system as a tar filenamed mavscan.tar.To unpack the tools on the CONVERSANT system to be scanned:1. Copy the mavscan.tar file to a directory where the tool will run.2. On the command line, enter tar –xvf to unpack the tool in the current workingdirectory.Unpacking the tool populates the current directory with the scripts and supporting utilitiesneeded to run the migration tools.Pre-migration phaseThe purpose of the pre-migration phase is to determine the scope of the migration (the dataand application changes that will be moved from a current CONVERSANT platform to AvayaIR). The pre-migration scripts, including the Scanit tool, are packaged together in a premigrationpackage. You install and execute the pre-migration package on the sourceCONVERSANT system.Pre-migration scanning tool (Scanit)Scanit is the primary data gathering tool used to quantify the data and applications on sourceCONVERSANT platform. The log files from Scanit are a primary input to determining thework effort involved in the migration to an Avaya IR platform. Actual effort estimates requireanalysis of the log files created from the pre-migration tool and are expected to be made byan experienced development organization such as an ISV or Avaya professional services.Note:Scanit should not be confused with the existing SCAN tool that is run by Avayaservices. The existing SCAN tool captures an entire CONVERSANTconfiguration (boards, RTU licenses, etc). Scanit is dedicated to applicationsand data and complements the existing SCAN tool.Scanit looks at application source files for occurrences of code that are out of compliancewith the new Avaya IR release. These occurrences are referred to as tokens. The Scanit toolallows the user to configure the extensions for which to scan. The default extension typesare:Issue 3 March 2003 47
Page 1 and 2: Avaya Interactive ResponseRelease 1
Page 3: Technical SupportTo report problems
Page 6 and 7: ContentsRequirements for successful
Page 9 and 10: Hardware installationIf you purchas
Page 11 and 12: Hardware installationModem cableAn
Page 13 and 14: Hardware installation2. Connect the
Page 15 and 16: Installing the system base software
Page 23 and 24: Site-specific setupThe information
Page 25 and 26: Site-specific setup2. Select a Loca
Page 27 and 28: Site-specific setup18. Regions[ ] A
Page 29 and 30: Installing packages and setting up
Page 35: Installing packages and setting up
Page 38 and 39: Installation overviewVERSION: 1.0.0
Page 40 and 41: Installation overview4. Type uncomp
Page 43 and 44: Restoring the system from backupIf
Page 45: MigrationThis section defines the p
Page 49 and 50: Migration• Oracle Data. The data
Page 51 and 52: Migration6. Press Enter.The tool di
Page 53 and 54: MigrationFor example, if IRAPI func
Page 55 and 56: Migrationetc/init.d/etc/init.d/nfs.
Page 57 and 58: MigrationThe speech conversion tool
Page 59 and 60: Migrationb) Set the Application Tra
Page 61: MigrationIssue 3 March 2003 61
Page 65 and 66: Troubleshooting overviewThis sectio
Page 67 and 68: Troubleshooting overviewHardware ma
Page 70 and 71: Troubleshooting• Effective IR sys
Page 72 and 73: TroubleshootingInadequate systemres
Page 74 and 75: Troubleshooting6. Check the Message
Page 76 and 77: TroubleshootingAll calls droppedTo
Page 78 and 79: Troubleshooting-12 Cannot set timer
Page 80 and 81: Troubleshooting2. Enter trace tsm c
Page 82 and 83: Troubleshootingsystem overload. For
Page 86: TroubleshootingChecking Oracle obje
Page 91 and 92: Checking hardwareRestoring NETOOS c
Page 93 and 94: Checking hardware― For the VoIP c
Page 95 and 96: Checking hardware2. Note the result
Page 97 and 98:
Checking LAN communicationsTo suppo
Page 99 and 100:
Checking communications4. Click Tes
Page 101 and 102:
Checking communications• Only tra
Page 103:
Checking communications-t Set the t
Page 106:
IndexPreinstallation • 15Pre-migr
show all

Avaya IR Install and Troubleshooting Guide - Avaya Support

Create successful ePaper yourself

Delete template?

Save as template?