Migrating Script Builder applications that use the vesp_dip.t external function

The vesp_dip.t external function no longer requires applications to define the vespbuf variable that was required in previous Script Builder applications. For this reason, the following steps must be performed for Script Builder applications that use the vesp_dip.t external function and the vespbuf variable:

1. Use FTP to transfer the vesp_dip.t external function from the vs/bin/ag/lib directory on the Avaya IR system to the vs/bin/ag/lib directory on the V8 or R9 CONVERSANT system. If this directory does not exist, it must be created.
2. Use FTP to transfer the vesp_dip.h and vespdipi.h header files from the vs/bin/ag/lib/dip directory on the Avaya IR system to the vs/bin/ag/lib/dip directory on the V8 or R9 CONVERSANT system. If this directory does not exist, it must be created.
3. Run verify application name on the V8 or R9 CONVERSANT system.
4. Use FTP to transfer the application to the Avaya IR system.
5. Run /vs/bin/ag/install application name on the Avaya IR system.
6. Execute the Script Builder application.
7. Assign the application to the appropriate channel or channels.

© 2006 Avaya Inc. All Rights Reserved.