Nortel VT100 Development Manual
  1. Manuals
  2. Brands
  3. Nortel Manuals
  4. Gateway
  5. VT100
  6. Development manual
Nortel VT100 Development Manual

Nortel VT100 Development Manual

Nortel networks gateway development guide
Hide thumbs
Table of Contents

Advertisement

Quick Links

Download this manual
Meridian IVR
VT100 Gateway Development Guide
Publication number:
Product release:
Document release:
Date:
© 1996 Northern Telecom
All rights reserved
Printed in the United States of America
Information is subject to change without notice. Northern Telecom reserves the right to make
changes in design or components as progress in engineering and manufacturing may warrant.
Nortel, Meridian IVR, Meridian Mail, ACCESS, and Meridian 1 are trademarks of Northern
Telecom. VT100, DEC, and VT420 are trademarks of Digital Equipment Corporation. HP, LaserJet,
and ThinkJet are trademarks of Hewlett-Packard Company. X Window System and X are
trademarks of the Massachusetts Institute of Technology. NCD is a trademark of Network
Computing Devices Inc. UNIX is a registered trademark of AT&T. Voicetek and VTK are trademarks
of Voicetek Corporation. Motif is a trademark of Open Software Foundation Inc. Touch tone is a
trademark of Bell Canada. Intel and Pentium are trademarks of Intel Corporation. SCO is a
trademark of The Santa Cruz Operation Inc.
555-9001-316
Meridian IVR 2.0/I
Standard 1.0
February 1996

Advertisement

Table of Contents
loading

Related Manuals for Nortel VT100

Summary of Contents for Nortel VT100

  • Page 1 Nortel, Meridian IVR, Meridian Mail, ACCESS, and Meridian 1 are trademarks of Northern Telecom. VT100, DEC, and VT420 are trademarks of Digital Equipment Corporation. HP, LaserJet, and ThinkJet are trademarks of Hewlett-Packard Company. X Window System and X are trademarks of the Massachusetts Institute of Technology.
  • Page 2 Publication history February 1996 This document is the first standard issue for Meridian IVR release 2.0/I. Meridian IVR VT100 Gateway Development Guide Product release 2.0/I...

  • Page 3: Table Of Contents

    The VT100 terminal ........1-1...
  • Page 4 555-9001-316 Standard 1.0 February 1996 Terminals connected to a host computer ... 1-2 VT100 application screen sample ... 1-3 Meridian IVR 2.0/I VT100 Gateway configuration ... 1-4 TRS communication process ... 1-5 Voice response system vs. terminal operator ... 2-3 Action and screen templates...
  • Page 5 TRS default communication settings... 3-10 Table 4-1 Branches of the COMO cell ... 4-9 Table 4-2 Application cell functions... 4-13 List of procedures Procedure 2-1 Accessing transaction information ... 2-5 Meridian IVR VT100 Gateway Development Guide Product release 2.0/I Contents vii...

  • Page 6: About This Guide

    How to use this guide This guide contains the following chapters and appendices: Chapter 1: About the VT100 Gateway This chapter provides an overview of the VT100 terminal and a description of the Meridian IVR 2.0/I VT100 Gateway features. Chapter 2: Template files This chapter explains how to create the necessary files for sending data to and receiving data from a remote computer.

  • Page 7: Additional Nortel Manuals

    (for example, the CURRENT MESSAGE buffer). • Items that are file names or messages are shown in bold (for example, the /u/ivr/vt100/getbalance.act file). For convenience, this guide uses the keyname <Enter> to represent both the Enter and Return keys. 555-9001-316 Standard 1.0 February 1996...

  • Page 8: Chapter 1: About The Vt100 Gateway

    Chapter 1: About the VT100 Gateway This chapter provides an introduction to the Meridian IVR 2.0/I VT100 Gateway as well as • background on the VT100 terminal • descriptions of the Meridian IVR 2.0/I VT100 Gateway software • a description of the TRS configuration •...

  • Page 9: Figure 1-1 Terminals Connected To A Host Computer

    With respect to the VT100 Gateway product, a host computer is any computer that can accept a VT100 terminal connection, including mainframes, minicomputers, and workstations.

  • Page 10: Figure 1-2 Vt100 Application Screen Sample

    Enter menu selection: vt100 An active host to terminal connection is called a session. The VT100 Gateway can execute a series of transactions during a session. A transaction is the series of steps required to perform a specific function like finding a customer’s account balance.

  • Page 11: The Vt100 Gateway Software

    1-4 About the VT100 Gateway The VT100 Gateway software You can install the Meridian IVR 2.0/I VT100 Gateway on Intel’s new generation 64-bit Pentium Gateway, the application processor must • have an ACCESS link connected to Meridian Mail • be connected to one or more host computers via an asynchronous connection •...

  • Page 12: Figure 1-4 Trs Communication Process

    A Meridian IVR 2.0/I process called the Terminal Resource Server (TRS) controls all VT100 sessions, as well as manages all host connections. The TRS runs as a stand-alone process within the Meridian IVR 2.0/I architecture, and starts when Meridian IVR 2.0/I is started. To use the TRS, place a COMI cell in the Meridian IVR 2.0/I call flow at the point where you need to...
  • Page 13 1-6 About the VT100 Gateway The TRS process for managing calls is restricted to handling one active line at a time (single threaded mode). Therefore, you should add a loop to applications that interact with the TRS so that customers who call at peak hours are informed on the status of their call.

  • Page 14: Chapter 2: Template Files

    These templates exchange information with the host application screens and transfer information to and from the TRS’s buffers. Coupled with the VT100 emulation software and hardware, they provide the host with exactly the same type of input as a terminal operator.
  • Page 15 2-2 Template files To develop a voice application that accesses the same information as a terminal operator, you need to tell Meridian IVR 2.0/I how to execute the same series of actions that the terminal operator executes. You provide this information in ASCII files called template files.

  • Page 16: Figure 2-1 Voice Response System Vs. Terminal Operator

    Screen templates, which validate each screen, define the fields on the screen that require data, and define all keystrokes required for the screen. Figure 2-2 shows how screen templates relate to action templates. Meridian IVR VT100 Gateway Development Guide Product release 2.0/I A customer follows this sequence to retrieve data: Calls into the AP, activating a voice application.

  • Page 17: Figure 2-2 Action And Screen Templates

    TRS to efficiently determine when the host application is ready for input and what region of the host screen contains vital information. These inconsistencies are due to the character based nature of the VT100 protocol. In addition, the VT100 communication protocol has no way of notifying the TRS that host data transmission has ended.

  • Page 18: Action Templates

    Action templates A VT100 transaction typically moves through several screens until it locates specific information. The screens may be a series of commands issued at the operating system prompt, or they may be screens within an application running on the host computer.

  • Page 19: Action Template Syntax

    2-6 Template files Action template syntax An action template is an ASCII file created with a text editor. The action template files you create must reside in the /u/ivr/3270 directory or in a subdirectory below /u/ivr/3270. They must also have the file name extension .act.

  • Page 20: Figure 2-4 Action Template For Accounting Application

    The first line of the template in Figure 2-3 is a comment. The comment line is not required but is recommended to describe the purpose of the action template. Meridian IVR VT100 Gateway Development Guide Product release 2.0/I reset_cust logout_cust...
  • Page 21 When you set up your application processor with the VT100 Gateway, you must create a trs.conf file that assigns TRS session numbers to the application on the host computer (the trs.conf file is described in Chapter 3).

  • Page 22: Figure 2-5 Reset-Action Template Sequence Sample

    When you create a reset-action template, do not specify reset-action or logout-action templates in it. For example, Figure 2-6 shows a sample reset-action template. Meridian IVR VT100 Gateway Development Guide Product release 2.0/I The reset-action template follows this sequence: Application...

  • Page 23: Figure 2-6 Reset-Action Template Sample

    2-10 Template files Figure 2-6 Reset-action template sample #This reset-action template returns the host computer application #to the main menu screen from the customer information screen #filename: reset_cust.act reset_cust accounting clrcust #exit the customer information screen atmenu #leave the session at the menu screen The action template using this reset-action template would enter reset_cust as the reset-action entry.

  • Page 24: Figure 2-7 Logout Action Flow

    When you create a logout-action template, do not specify reset-action or logout-action templates. Figure 2-8 shows a sample logout-action template. Meridian IVR VT100 Gateway Development Guide Product release 2.0/I Template files 2-11 Logout-action Template...

  • Page 25: Figure 2-8 Logout-Action Template Sample

    The screen-template (the file name of the template without the .scn extension) identifies the screen template used during the VT100 transaction. Enter the screen templates in the exact order they appear during the transaction. Each screen template must be listed on a separate line. The syntax for screen templates is described later in this chapter.

  • Page 26: Screen Templates

    This guide uses an accounting application as an example. Each screen contains fields. For the VT100 Gateway, a field is any place on the screen where data is entered or displayed. For example, the cursor location after a system prompt where you would type a command is considered a field.

  • Page 27: Figure 2-9 Screen Showing Fields And The System Prompt

    2-14 Template files Figure 2-9 Screen showing fields and the system prompt login: vad Password: Last login: Fri Apr 16 16:01:34 from publisher ULTRIX V4.2 (Rev. 96) System #9: Mon Jul 29 10:08:24 EDT 1994 $acct In Figure 2-9, vad has been entered into the login field. If the Return key is pressed, the application starts and the screen is replaced by the application screen.

  • Page 28: Figure 2-10 Application Screen For Accounting Application

    The screen template can include both data input entries as well as data output entries. Screen template syntax The syntax of a screen template is shown in Figure 2-11. Meridian IVR VT100 Gateway Development Guide Product release 2.0/I Template files 2-15...

  • Page 29: Figure 2-11 Screen Template Syntax

    2-16 Template files Figure 2-11 Screen template syntax #comment screen-name validation tag offset field-descriptor field-descriptor • • • key-descriptor sleep-descriptor The lines depicted as • represent additional field-descriptor lines. The example in Figure 2-12 illustrates a screen template file that obtains the balance from the screen shown in Figure 2-10.

  • Page 30: Figure 2-12 Screen Template For Accounting Application

    This would place the contents of the field starting at 2,48 into the next buffer. See “field-I/O” later in this section. An explanation of each entry in the screen template follows. Meridian IVR VT100 Gateway Development Guide Product release 2.0/I Template files 2-17...
  • Page 31 2-18 Template files #comment The first line of the template in Figure 2-12 is a comment. The comment line is not required but is recommended to describe the purpose of the screen template. Comments can be embedded anywhere in the screen template and start with the “#”...
  • Page 32 The field-descriptor lines should be entered in the same order as they are accessed for the transaction. Figure 2-13 shows the syntax for field-descriptor lines. Meridian IVR VT100 Gateway Development Guide Product release 2.0/I...

  • Page 33: Figure 2-13 The Field-Descriptor Syntax

    For unformatted, character-based applications, you must specify the exact location. In VT100 transactions, writing to the terminal screen always occurs at the current cursor position. Therefore, if the field I/O action is writing text to the host screen, the TRS will write the text to the screen at the current cursor position regardless of the row,column you specify.
  • Page 34 24,8 for the location of the action specified by the field-I/O entry. field-I/O This entry indicates the action to be taken on the field. Table 2-1 explains the valid entries for this field. Meridian IVR VT100 Gateway Development Guide Product release 2.0/I...
  • Page 35 31 characters have been retrieved. Internal variables (indicated by the % symbol) are used within the VT100 screens only and cannot be transmitted through the TRS gateway. You can only use internal variables to store and enter data from one screen to another in the host computer application.

  • Page 36: Figure 2-14 Key-Descriptor Line Syntax

    Figure 2-14 contains the format of the key-descriptor. Figure 2-14 Key-descriptor line syntax position-indicator position-indicator This entry should be set to 0,0. > This character indicates that this line contains a key. Meridian IVR VT100 Gateway Development Guide Product release 2.0/I > keyname Template files 2-23...

  • Page 37: Table 2-2 Valid Key Names

    2-24 Template files keyname The name of the key for this screen. Table 2-2 lists the valid keys you can enter. Table 2-2 Valid key names ATTENTION BACKSPACE BACKTAB BACKWORD CLEAR CURSORDOWN CURSORLEFT CURSORLEFTDBL CURSORRIGHT CURSORRIGHTDBL CURSORUP DELCHAR ENTER ERASEEOF ERASEINPUT FIELDMARK This line may appear anywhere after the screen-name line (i.e., the first...

  • Page 38: Figure 2-15 Sleep-Descriptor Syntax

    50 seconds. Therefore, the time out value should be greater than 50 seconds. Each sleep-descriptor follows the syntax shown in Figure 2-15. Figure 2-15 Sleep-descriptor syntax position-indicator Meridian IVR VT100 Gateway Development Guide Product release 2.0/I Template files 2-25...

  • Page 39: Initial-Action Templates

    Initial-action templates Before you can process any information on the host computer using the VT100 Gateway, you need to set the starting point for each of your terminal sessions. For example, you may want session 2 to start processing at an application’s main menu, whereas session 5 should start at the system...

  • Page 40: Chapter 3: Getting Started

    Chapter 3: Getting started Before using the VT100 Gateway Before you can use the VT100 Gateway, you must complete these tasks: • If necessary, install a multiport adapter board and expander box. • Create the action and screen templates necessary to navigate through the host application and return the desired information (see Chapter 2).

  • Page 41: Screen.conf File

    3-2 Getting started screen.conf file Since the VT100 protocol is character based, it has no built in mechanism for notifying the TRS that host output has ended and the application is ready for input. Creating the screen.conf file allows the TRS to quickly process host output by eliminating the time it spends waiting after host output ends.

  • Page 42: Figure 3-1 Screen.conf File Syntax

    If the end string contains a space or a colon, then place the end string in quotation marks. You must provide an end string for the screen.conf file to be valid. Meridian IVR VT100 Gateway Development Guide Product release 2.0/I Getting started 3-3...

  • Page 43: Setting Up The Trs.conf File

    3-4 Getting started Note: The TRS considers the begin string and the end string part of the data. See Figure 3-2 for an example of the screen.conf file. Figure 3-2 screen.conf file In Figure 3-2, PROGRAM MENU is the keyword for the first screen. Since it contains a “s13is”...

  • Page 44: Figure 3-3 Trs.conf File Syntax

    In the VT100 option, the session-number entry determines the number of sessions per board with session numbers ranging from 2 to 16. By using two digital boards there can be up to 15 sessions, if there is only one ACCESS link.

  • Page 45: Figure 3-4 Initial-Action Template

    3-6 Getting started initial-template The initial-template entry identifies an initial-action template (without the .act file extension) for setting the startup action for the specified sessions when connecting to the host computer. The start-up action brings the specified sessions to the screen on the host computer where the action templates start when processing requests.
  • Page 46 ENTER key and validation-tag. protocol The protocol entry indicates the communications protocol being used by app-name. This field is required and should be set to vt100. Example “trs.conf” File Consider the following example. Initial-action template files login.act and signin.act have been defined and reside in the /u/ivr/3270 directory.

  • Page 47: Setting Up The Vt100.Ctl File

    3-8 Getting started You want to set up the VT100 Gateway to initialize the sessions as follows: • initialize sessions 2-3 for accounting with acctinit.act, • initialize sessions 4-8 for market with login.act, • initialize sessions 9-10 for banking with login.act, and •...

  • Page 48: Figure 3-6 Vt100.Ctl File Syntax

    Figure 3-6 vt100.ctl file syntax session-number device-name Figure 3-7 shows a vt100.ctl file, based on the example trs.conf file in Figure 3-5. Figure 3-7 vt100.ctl file for accounting application /dev/ttyi1b vt100 /dev/ttyi1c vt100 Meridian IVR VT100 Gateway Development Guide Product release 2.0/I...

  • Page 49: Setting Up The Com.conf File

    The device-name entry is the exact name of the device file in the /dev directory to use for the VT100 Gateway for the specified sessions. Use the full directory path (as shown in Figure 3-7) when entering the device file name.

  • Page 50: Figure 3-8 Com.conf File

    Getting started 3-11 The com.conf file must be created if the baud rate is anything other than 9600. The com.conf file is located in the vt100 directory and a sample is shown in Figure 3-8. Figure 3-8 com.conf file Meridian IVR Creating the com.conf file allows you to adjust the following values.
  • Page 51 DEBUG_LEVEL 1 to 5. Setting the debug level determines how much debugging information is sent to the /u/ivr/vt100/vt100log file. MAXIMUM_WAIT_TIME This parameter tells the TRS how long to wait for the output from the host to end. Only use this parameter if you can not use a screen.conf file. The wait time is specified in seconds.

  • Page 52: A Complete Sample Transaction

    Figure 3-9 shows the initial-action template, its supporting screen templates and the corresponding screens on the host computer. Meridian IVR VT100 Gateway Development Guide Product release 2.0/I Getting started 3-13...

  • Page 53: Figure 3-9 Initial-Action Template For Accounting Application

    3-14 Getting started Figure 3-9 Initial-action template for accounting application #initial action template to start #the accounting application #filename: acctinit.act acctinit acctlog1.scn acctlog2.scn atacctmenu #screen template that logs #into the host #filename: acctlog1.scn acctlog1 > > #screen template that starts #the accounting application #filename: acctlog2 acctlog2...
  • Page 54 The initial-action template shown in Figure 3-10 specifies the clinit.act logout-action template, and does not specify a reset-action template. Figure 3-10 shows the clinit logout-action template, its corresponding screen templates, and the associated application screens. Meridian IVR VT100 Gateway Development Guide Product release 2.0/I Getting started 3-15...

  • Page 55: Plate For Accounting Application

    3-16 Getting started Figure 3-10 Logout-action template used by the initial-action template for accounting application #logout-action template for the #acctinit initial-action template #filename: clinit.act clinit accounting – – clrmenu logout #screen template to exit the #accounting application #filename: clrmenu.scn clrmenu #screen template to log off the host #computer, preparing for the initial #action template to be executed...

  • Page 56: Action Template Performing A Transaction

    COMO cell • execute a reset-action template to return the session application to the application’s menu screen Meridian IVR VT100 Gateway Development Guide Product release 2.0/I Getting started 3-17...

  • Page 57: Figure 3-11 Action Template For Accounting Application

    3-18 Getting started Figure 3-11 Action template for accounting application Templates #action template to perform steps #required to retrieve customer's balance #filename: getbalance.act getbalance accounting clr_cust logout_cust accrec #choose Ac. Rec menu acctno #enters account number customer #retrieves balance #screen template to choose accounts #receivable option, filename:accrec.scn accrec 1,20...

  • Page 58: Figure 3-12 Reset-Action Template For Accounting Application

    Figure 3-13 shows the logout-action template, and its accompanying screen templates, that return the host computer to the login screen if an error occurs and the reset-action template also experiences an error. Meridian IVR VT100 Gateway Development Guide Product release 2.0/I Screen Template #screen template to clear customer info #screen, filename: clrcust.scn...

  • Page 59: Figure 3-13 Logout-Action Template For Accounting Application

    3-20 Getting started Figure 3-13 Logout-action template for accounting application Action Template #logout-action template for the getbalance #action template, filename: logout_cust.act logout_cust accounting — clrcust #exits customer info screen clrmenu #exits applicatoin menu logout #logouts out to prepare for login The logout-action template brings the host computer back to the login screen.

  • Page 60: Chapter 4: Ivr 2.0/I Call Flow Interface

    Chapter 4: IVR 2.0/I call flow interface Now that you understand how to script VT100 transactions as action and screen templates, you can begin integrating these templates into your IVR 2.0/I Applications (Figure 4-1). Figure 4-1 Accessing the mainframe Call Flow...

  • Page 61: Setting The Comi Cell Parameters

    4-2 IVR 2.0/I call flow interface Figure 4-2 Activating the gateway from a COMI cell START ANSW GDAT MENU COMI COMO PDAT HANG To develop an application that processes one or more terminal sessions, start as if you were developing any other voice application: •...

  • Page 62: Figure 4-3 Comi Cell Parameter Window

    IVR 2.0/I call flow interface 4-3 Figure 4-3 COMI cell parameter window start getbalance transaction Meridian IVR VT100 Gateway Development Guide Product release 2.0/I...
  • Page 63 4-4 IVR 2.0/I call flow interface The following sections describe what you should enter in each area of the parameter window. COMI cell name In order to make the cell easy to identify, includes the name of the action template the cell calls out. The cell name shown in Figure 4-3 is “start getbalance transaction.”...
  • Page 64 If you need to use more than 10 input buffers in your application, make sure you select “Yes” for “More Input?”, then string COMI cells together until you have enough input buffers. Connect each additional COMI cell to the previous one’s “SUCCESS” branch. Meridian IVR VT100 Gateway Development Guide Product release 2.0/I...
  • Page 65 4-6 IVR 2.0/I call flow interface Setting the COMO cell parameters Once you have set the COMI cell to send information, code the COMO cell to receive information. You must place a COMO cell directly after the COMI cell to complete the transaction, even if the host computer is not sending any data to any output buffers.

  • Page 66: Figure 4-4 Como Cell Parameter Window

    The following sections describe what you should enter in each area of the parameter window. COMO cell name The cell name shown in Figure 4-4 is “Receive Balance.” The name helps identify the function of the cell. Meridian IVR VT100 Gateway Development Guide Product release 2.0/I...
  • Page 67 4-8 IVR 2.0/I call flow interface Call Audit Enabled Determines if this cell logs the following information to the call audit statistics file (audit_stat.d): • • • • • • The default setting is No. Call Audit Information When you enable Call Auditing, the Call Auditing process logs the contents of this buffer to the audit_stat.d file.

  • Page 68: Figure 4-5 Como Cell

    NOT READY The transaction did not complete and Blocking was set to “No” END OF DATA The transaction successfully completed Meridian IVR VT100 Gateway Development Guide Product release 2.0/I IVR 2.0/I call flow interface 4-9 Reason the branch would be taken...

  • Page 69: Figure 4-6 Coma Cell In The Cleanup Branch Of A Start Cell

    4-10 IVR 2.0/I call flow interface Table 4-1 Branches of the COMO cell (continued) MORE DATA For each COMO cell, use either the “END OF DATA” branch, or the “MORE DATA” branch, but not both. If you use the “MORE DATA” branch, the next cell must be another COMO cell.

  • Page 70: An Application Using The Comi, Como, And Coma Cells

    To illustrate the logic of the call flow, these applications are shown as one page applications with no error branches. In reality, these applications would span several pages and would have all error branches connected appropriately. Meridian IVR VT100 Gateway Development Guide Product release 2.0/I...

  • Page 71: Figure 4-7 Ivr 2.0/I Application Accessing The Trs Process From The Comi, Como Cells

    4-12 IVR 2.0/I call flow interface Figure 4-7 IVR 2.0/I application accessing the TRS process from the COMI, COMO cells Prior to the execution of this application, the initial-action template is executed (when IVR 2.0/I is started on the application processor). Once a call from a customer is received, the IVR 2.0/I application performs these steps: 555-9001-316 Standard 1.0 February 1996...

  • Page 72: Table 4-2 Application Cell Functions

    If the caller hangs up before the transaction is completed, the COMA cell in the clean-up branch of the START cell clears the memory and buffers associated with the application. Meridian IVR VT100 Gateway Development Guide Product release 2.0/I IVR 2.0/I call flow interface 4-13 Description...
  • Page 73 4-14 IVR 2.0/I call flow interface Figure 4-8 on page 4-15 shows how the COMI and COMO cell parameters relate to the screens defined on the host computer. This transaction uses an action template, getbalance, to call three screen templates - one to choose the Accounts Receivable menu, one to enter the account number, and one for the customer information screen.

  • Page 74: Figure 4-8 Comi/Como Cell Parameters, Trs Templates, And Vt100 Screens

    #screen template to obtain balance #filename: customer.scn customer 1,1 Account Number: 2,48 — Put into BALANCE buffer in COMO cell Meridian IVR VT100 Gateway Development Guide Product release 2.0/I Corresponding Screens ACME Accounting 1 Accounts Receivable 2 Accounts Payable 3 Reports 4 Inventory...

  • Page 75: Appendix A: Host Error Messages

    TRS was unable to reset the vt100 system. Check the existence of the file ../vt100/vt100.ctl. Make sure its format is correct. Look at ../vt100/vt100.log to make sure that the communication ports have been opened successfully. Also make sure the communication device is properly defined.
  • Page 76 A-2 Host error messages Action to take: ERR: Create_screen_templates Meaning: Action to take: ERR: Create_action_templates Meaning: Action to take: ERR: Order_templates Meaning: Action to take: ERR: Load_runtime_config Meaning: Action to take: ERR: Check_action_template Meaning: Action to take: ERR: All communication boards are not operational Meaning: Action to take: 555-9001-316 Standard 1.0 February 1996...
  • Page 77 Action to take: ERR: Unable to create Application Object Meaning: Meridian IVR VT100 Gateway Development Guide Product release 2.0/I None of the sessions is operational. Make sure the communication board has been downloaded correctly. The download command should be included in .profile file.
  • Page 78 A-4 Host error messages Action to take: ERR: xx is not a keyword Meaning: Action to take: ERR: BD xx SS xxx ERR: start host notify Meaning: Action to take: ERR: CH=xx ERR::Request does not contain action name Meaning: Action to take: ERR: CH= xx ERR::Invalid action name xxx Meaning: Action to take:...
  • Page 79 ERR: CH=xx BD xxx SS xxxx Read_updated:ERR: Query PS CODE= xxxxx Meaning: Action to take: Meridian IVR VT100 Gateway Development Guide Product release 2.0/I This particular session is not working. TRS was unable to attach this session. Contact your Nortel service representative.
  • Page 80 A-6 Host error messages ERR: Send Aid key failed Meaning: Action to take: ERR: CH=xx Process:ERR: Syntax error for variable operation Meaning: Action to take: ERR: CH=xx Process:ERR: write to screen Meaning: Action to take: ERR: msg_wait_start Meaning: Action to take: ERR: Initialize 3270 Controller software Meaning: Action to take:...
  • Page 81 Action to take: ERR: A flush command was sent prior to any request Meaning: Action to take: Meridian IVR VT100 Gateway Development Guide Product release 2.0/I None. Notification only. 3270 envoy has been started up. None. Notification only. The TRS process with no 3270 communication capability has been started up.
  • Page 82 A-8 Host error messages ERR: CH=xx illegal Command xxx Meaning: Action to take: ERR: Server Node file trs.node does not exist Meaning: Action to take: ERR: The server node name is the same as envoy node name Meaning: Action to take: ERR: NET_TO_ENVOY: ERR: Reply Code =xx from SERVER Meaning: Action to take:...
  • Page 83 Action to take: ERR: Ping request memory allocation failed Meaning: Meridian IVR VT100 Gateway Development Guide Product release 2.0/I TRS failed to connect to session xx before sending the aid key. Check the communication system to make sure it works properly.
  • Page 84 A-10 Host error messages Action to take: ERR: Create_queue_object: Attempt to create Queue class instance failed Meaning: Action to take: ERR: A request for this channel is already being processed Meaning: Action to take: ERR: Create_transaction_instance: Unable to create Transaction Object Instance Meaning: Action to take: ERR: Create_timer_instance: Unable to create Timer Object Instance...
  • Page 85 Action to take: ERR: Ping action missing,put - if not available Meaning: Action to take: Meridian IVR VT100 Gateway Development Guide Product release 2.0/I Contact your Nortel service representative. TRS was unable to allocate memory for the idle timer structure.
  • Page 86 Action to take: 555-9001-316 Standard 1.0 February 1996 The protocol type was missing from the trs.conf protocol field. Make sure that ‘3270’ or ‘vt100’ is specified in the protocol field. The heartbeat action template was specified incorrectly in the trs.conf file.
  • Page 87 ERR: Invalid Session Number xx specified in ../3270/map.dat Meaning: Action to take: Meridian IVR VT100 Gateway Development Guide Product release 2.0/I The first session defined in the trs.conf file was less than allowed as specified by xx. Revise the session field of the trs.conf file.
  • Page 88 A-14 Host error messages ERR: in map.dat:Session xx not defined in trs.conf Meaning: Action to take: ERR: read data from file ../3270/lubuf.dat Meaning: Action to take: ERR: Invalid Board number xx specified in ../3270/lubuf.dat Meaning: Action to take: ERR: Invalid Session Number xx specified in ../3270/lubuf.dat Meaning: Action to take: ERR: In ../3270/lubuf.dat:BD xx SS xxx not defined in trs.conf...
  • Page 89 ERR: Screen name xx exceeds xxx characters Meaning: Action to take: Meridian IVR VT100 Gateway Development Guide Product release 2.0/I Revise the password in lubuf.dat file so that the length of the password does not exceed xxx. There are too many characters in the lu_buf1 field defined in the lubuf.dat file.
  • Page 90 A-16 Host error messages ERR: Screen name xx must match the file name without .scn Meaning: Action to take: ERR: Validate tag xx of screen xxx exceeds xxx characters. Meaning: Action to take: ERR: Unable to get offset value from file xx Meaning: Action to take: ERR: Parse string xx of screen xxx...
  • Page 91 ERR: Screen xx of Action xxx not found Meaning: Action to take: Meridian IVR VT100 Gateway Development Guide Product release 2.0/I Revise the application to keep the screen templates within the limit specified by xx. TRS failed to open the action file xx.
  • Page 92 A-18 Host error messages ERR: reset action xx of the action xxx not found Meaning: Action to take: ERR: logout action xx of the action xxx not found Meaning: Action to take: ERR: Unable to find ACTION xx Meaning: Action to take: ERR: Unable to open Information Logger Meaning: Action to take:...
  • Page 93 The basic element of a IVR application. Each cell performs an action – like playing a prompt to a caller. After the cell performs its action, it determines which branch the application should follow to the next cell. Meridian IVR VT100 Gateway Development Guide Product release 2.0/I Glossary-1...
  • Page 94 Channel A telephone trunk within a cluster of APs. COMA Cell IVR cell that cancels a transaction in a VT100 terminal session. It does not terminate the session itself. COMI Cell IVR cell that sends input to a VT100 terminal session via the TRS process.
  • Page 95 The function performed by a set of action and screen template files when executed by the TRS. Terminal Resource Server. IVR process that manages the assignment of available VT100 terminal resources on the application processor. Moves data between IVR and a host application. VT100 terminal Terminal type emulated by the VT100 Gateway product.
  • Page 97 Meridian IVR VT100 Gateway Development Guide Nortel Customer Documentation 522 University Avenue, 14th Floor Toronto, Ontario, Canada M5G 1W7 © 1996 Northern Telecom All rights reserved Publication number: 555-9001-316 Product release: 2.0/I Document release: Standard 1.0 Date: February 1996 Printed in the United States of America...

This manual is also suitable for:

Meridian ivr vt100

Table of Contents