Page 2 - iii; Publication history
iii Meridian IVR VT100 Gateway Development Guide Product release 2.0/I Publication history February 1996 This document is the first standard issue for Meridian IVR release 2.0/I.
Page 3 - Contents; About this guide
v Meridian IVR VT100 Gateway Development Guide Product release 2.0/I Contents About this guide ix Who should use this guide . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .ixHow to use this guide. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .ixAdditional No...
Page 4 - vi; Using the COMI, COMO, and COMA cells to access the host; Appendix A: Host error messages
vi Contents 555-9001-316 Standard 1.0 February 1996 Chapter 4: IVR 2.0/I call flow interface 4-1 Using the COMI, COMO, and COMA cells to access the host computer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-1 Setting the COMI cell parameters . . . . . . . . . . ....
Page 5 - vii; Logout-action template for accounting application 3-20; List of tables
Contents vii Meridian IVR VT100 Gateway Development Guide Product release 2.0/I Figure 3-10 Logout-action template used by the initial-action tem-plate for accounting application............................. 3-16 Figure 3-11 Action template for accounting application............ 3-18 Figure 3-12 Res...
Page 6 - ix; Who should use this guide; This guide contains the following chapters and appendices:; Chapter 1: About the VT100 Gateway
ix Meridian IVR VT100 Gateway Development Guide Product release 2.0/I About this guide Who should use this guide The Meridian IVR 2.0/I VT100 Gateway Development Guide is intended for use by Meridian IVR 2.0/I application developers whose voice applications require VT100 based access to computer res...
Page 7 - Appendix A: Host error messages; Additional Nortel manuals; Items that are file names or messages are shown in; bold; the; Manual; Meridian IVR Application Development Guide
x About this guide 555-9001-316 Standard 1.0 February 1996 Chapter 4: IVR 2.0/I call flow interface This chapter explains how to integrate the templates you created in Chapter 3 with your Meridian IVR 2.0/I application call flow. Appendix A: Host error messages This appendix lists error messages and...
Page 8 - Chapter 1: About the VT100 Gateway; background on the VT100 terminal
1-1 Meridian IVR VT100 Gateway Development Guide Product release 2.0/I 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 de...
Page 9 - About the VT100 Gateway; accessed; Host
1-2 About the VT100 Gateway 555-9001-316 Standard 1.0 February 1996 Figure 1-1Terminals connected to a host computer The VT100 terminal uses an asynchronous communication protocol to transmit characters to and from a host computer. The VT100 Gateway communicates with a host through a serial port and...
Page 11 - The VT100 Gateway software; You can install the Meridian IVR 2.0/I VT100 Gateway on Intel’s new; microprocessor. To support the VT100; Meridian IVR 2.0/I VT100 Gateway configuration
1-4 About the VT100 Gateway 555-9001-316 Standard 1.0 February 1996 The VT100 Gateway software You can install the Meridian IVR 2.0/I VT100 Gateway on Intel’s new generation 64-bit Pentium TM microprocessor. To support the VT100 Gateway, the application processor must • have an ACCESS link connected...
Page 14 - Chapter 2: Template files; This chapter explains how to:; Determining the required transactions
2-1 Meridian IVR VT100 Gateway Development Guide Product release 2.0/I Chapter 2: Template files The TRS process uses action and screen templates to maneuver through the screens of a host application. These templates exchange information with the host application screens and transfer information to ...
Page 15 - Template files
2-2 Template files 555-9001-316 Standard 1.0 February 1996 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 ASCI...
Page 18 - Action templates; Log on to the computer.
Template files 2-5 Meridian IVR VT100 Gateway Development Guide Product release 2.0/I The action templates, screen templates, and screen.conf file are ASCII text files that use a simple syntax to define the screen flow and input/output fields. The sections that follow provide a detailed explanation ...
Page 19 - Action template syntax; would have this path:
2-6 Template files 555-9001-316 Standard 1.0 February 1996 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 ex...
Page 20 - getbalance; Manual mode; accrec
Template files 2-7 Meridian IVR VT100 Gateway Development Guide Product release 2.0/I Figure 2-4Action template for accounting application In Figure 2-4, action-name is getbalance , the name of the action template file without the .act extension. The app-name is accounting . The reset-action is rese...
Page 22 - Entering a hyphen “-” in the
Template files 2-9 Meridian IVR VT100 Gateway Development Guide Product release 2.0/I Figure 2-5Reset-action template sequence sample Entering a hyphen “-” in the reset-action entry indicates that no reset-action template is specified. If no reset-action template is specified and the transaction bei...
Page 23 - The action template using this reset-action template would enter
2-10 Template files 555-9001-316 Standard 1.0 February 1996 Figure 2-6Reset-action template sample The action template using this reset-action template would enter reset_cust as the reset-action entry. logout-action The logout-action specifies a logout-action template to be executed if the reset-act...
Page 24 - Entering a hyphen for the
Template files 2-11 Meridian IVR VT100 Gateway Development Guide Product release 2.0/I Figure 2-7Logout action flow The logout-action template locates the screen where the transaction failed. If for example, the transaction failed at the account number screen, the logout-action template locates the ...
Page 25 - manual
2-12 Template files 555-9001-316 Standard 1.0 February 1996 Figure 2-8Logout-action template sample screen-template 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...
Page 26 - should; Screen templates
Template files 2-13 Meridian IVR VT100 Gateway Development Guide Product release 2.0/I Note: You should not specify a reset-action template in an action template that uses manual mode. Manual mode is designed to stay at a specific screen. The next transaction received by the session will start at th...
Page 27 - vad; has been entered into the login field. If the; Return key; is
2-14 Template files 555-9001-316 Standard 1.0 February 1996 Figure 2-9Screen showing fields and the system prompt 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. A sample application ...
Page 28 - example, if you created a screen template called; Screen template syntax; The syntax of a screen template is shown in Figure 2-11.
Template files 2-15 Meridian IVR VT100 Gateway Development Guide Product release 2.0/I Figure 2-10Application screen for accounting application Different transactions may access different fields on a screen. For example, a transaction to locate the payment due would only need to access that field, w...
Page 30 - An explanation of each entry in the screen template follows.
Template files 2-17 Meridian IVR VT100 Gateway Development Guide Product release 2.0/I Figure 2-12Screen template for accounting application In Figure 2-12, the first line is a comment describing the screen template file. The screen-name is “customer,” the name of the screen template file without th...
Page 31 - validation-tag offset
2-18 Template files 555-9001-316 Standard 1.0 February 1996 #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...
Page 33 - If the TRS is going to read information from a field on the
2-20 Template files 555-9001-316 Standard 1.0 February 1996 Figure 2-13The field-descriptor syntax Note: If the application running on the host is stream-based, meaning the screen scrolls as the user enters data and retrieves responses, you should enter the field-descriptor as follows: 0,0- BLANKOUT...
Page 35 - Enters the contents of internal variable n into the field.; text
2-22 Template files 555-9001-316 Standard 1.0 February 1996 Table 2-1Valid field I/O entries Note: Place the asterisk and dollar sign characters in quotation marks if your field-descriptors require their use without their associated buffer commands. For retrieving data into an output buffer, $num in...
Page 37 - keyname; The name of the key for this screen. Table 2-2 lists the valid keys
2-24 Template files 555-9001-316 Standard 1.0 February 1996 keyname The name of the key for this screen. Table 2-2 lists the valid keys you can enter. Table 2-2Valid key names This line may appear anywhere after the screen-name line (i.e., the first non-comment line). As with field-descriptor lines,...
Page 38 - Each sleep-descriptor follows the syntax shown in Figure 2-15.
Template files 2-25 Meridian IVR VT100 Gateway Development Guide Product release 2.0/I sleep-descriptor (optional) A sleep-descriptor causes the transaction to pause for a specified number of seconds. You can use a sleep-descriptor to pause the transaction for a specified period of time before or af...
Page 39 - Identifies that this line is a sleep-descriptor.; num; Specifies the number of seconds that the session should sleep. For; Initial-action templates
2-26 Template files 555-9001-316 Standard 1.0 February 1996 position-indicator This entry should be set to 0,0. @ Identifies that this line is a sleep-descriptor. num Specifies the number of seconds that the session should sleep. For example, to wait 25 seconds, you would code the sleep-descriptor a...
Page 40 - Chapter 3: Getting started; Before using the VT100 Gateway; cd
3-1 Meridian IVR VT100 Gateway Development Guide Product release 2.0/I 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 tem...
Page 41 - Getting started
3-2 Getting started 555-9001-316 Standard 1.0 February 1996 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 proc...
Page 42 - file to check for the beginning of the screen, then enter a hyphen
Getting started 3-3 Meridian IVR VT100 Gateway Development Guide Product release 2.0/I Figure 3-1screen.conf file syntax The colons (:) are used as field delimiters and must be placed in the specified positions without any additional white space. Keyword: The keyword identifies the screen. If the ke...
Page 43 - PROGRAM MENU; Setting up the trs.conf file; Meridian IVR
3-4 Getting started 555-9001-316 Standard 1.0 February 1996 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-2screen.conf file In Figure 3-2, PROGRAM MENU is the keyword for the first screen. Since it contai...
Page 45 - The
3-6 Getting started 555-9001-316 Standard 1.0 February 1996 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 t...
Page 46 - heartbeat; ENTER
Getting started 3-7 Meridian IVR VT100 Gateway Development Guide Product release 2.0/I heartbeat You can specify an optional heartbeat action for the application specified by app-nam e. You can use this feature to send an indication to the host that a session is still active. Some hosts log out sess...
Page 47 - accounting; Setting up the vt100.ctl file
3-8 Getting started 555-9001-316 Standard 1.0 February 1996 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...
Page 48 - file, based on the example
Getting started 3-9 Meridian IVR VT100 Gateway Development Guide Product release 2.0/I Figure 3-6vt100.ctl file syntax Figure 3-7 shows a vt100.ctl file, based on the example trs.conf file in Figure 3-5. Figure 3-7vt100.ctl file for accounting application session-number device-name terminal-type 2 /...
Page 49 - dev; Setting up the com.conf file; None
3-10 Getting started 555-9001-316 Standard 1.0 February 1996 The follow sections describe each entry in the vt100.ctl file. session-number The session-number entry specifies the session this line defines. For example, the first line in Figure 3-7 defines the terminal type to be used for session 2. T...
Page 50 - IXON
Getting started 3-11 Meridian IVR VT100 Gateway Development Guide Product release 2.0/I 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-8com.conf file Creating the com.co...
Page 51 - -12 Getting started; Baud Rate
3-12 Getting started 555-9001-316 Standard 1.0 February 1996 Baud Rate 300 to 19200. Setting the baud rate tells the TRS the rate at which it is to communicate with the host. Set the baud rate by typing B then the rate. For example B4800 or B19200. Parity PARENB enables parity generation and detecti...
Page 52 - Getting started 3-13; A complete sample transaction; Initial-action template
Getting started 3-13 Meridian IVR VT100 Gateway Development Guide Product release 2.0/I A complete sample transaction This section summarizes how the sample accounting application would start up, retrieve a customer’s balance and reset for the next transaction. The sample transaction uses these temp...
Page 53 - -14 Getting started
3-14 Getting started 555-9001-316 Standard 1.0 February 1996 Figure 3-9Initial-action template for accounting application The initial-action template starts the accounting session with the host computer by accessing accounting from the trs.conf file. It then executes the screen templates acctlog1, a...
Page 54 - Getting started 3-15
Getting started 3-15 Meridian IVR VT100 Gateway Development Guide Product release 2.0/I The screen template acctlog1.scn does the following: • enters the login name • enters the password • waits three seconds for the host to process the login action The screen template acctlog2.scn does the followin...
Page 55 - -16 Getting started
3-16 Getting started 555-9001-316 Standard 1.0 February 1996 Figure 3-10Logout-action template used by the initial-action template for accounting application The final screen template listed, logout, brings the host application back to the initial screen, leaving the connection open and waiting for ...
Page 56 - Getting started 3-17; Action template performing a transaction
Getting started 3-17 Meridian IVR VT100 Gateway Development Guide Product release 2.0/I Action template performing a transaction As shown in Figure 3-10, the initial-action template brings the session to the application’s menu screen. The action template created to get a customer’s balance starts at...
Page 57 - -18 Getting started
3-18 Getting started 555-9001-316 Standard 1.0 February 1996 Figure 3-11Action template for accounting application The number 1 and the account number are entered at the current cursor location. Therefore, you do not need to specify a location or a field-tag. The last line in the “customer” screen t...
Page 58 - Getting started 3-19
Getting started 3-19 Meridian IVR VT100 Gateway Development Guide Product release 2.0/I The reset-action template is designed to return the session to the “acct” application’s menu screen where it awaits the next transaction. Figure 3-12 shows the reset-action template, and its accompanying screen t...
Page 59 - -20 Getting started
3-20 Getting started 555-9001-316 Standard 1.0 February 1996 Figure 3-13Logout-action template for accounting application The logout-action template brings the host computer back to the login screen. The TRS then executes the initial-action template, as it does whenever any logout-action template is...
Page 61 - Insert a COMO cell to receive the output from the TRS transaction.; Setting the COMI cell parameters
4-2 IVR 2.0/I call flow interface 555-9001-316 Standard 1.0 February 1996 Figure 4-2Activating the gateway from a COMI cell To develop an application that processes one or more terminal sessions, start as if you were developing any other voice application: • Determine the telephone interaction with ...
Page 64 - COMI cell timeout; The application will take the timeout branch of the COMI cell if a; COMI cell buffer count
IVR 2.0/I call flow interface 4-5 Meridian IVR VT100 Gateway Development Guide Product release 2.0/I COMI cell timeout Select the number of seconds you want the TRS process to wait for the transaction to complete by moving the slider under “Timeout”. There is an available range from 1 to 75 seconds....
Page 65 - Setting the COMO cell parameters
4-6 IVR 2.0/I call flow interface 555-9001-316 Standard 1.0 February 1996 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 ...
Page 66 - COMO cell name
IVR 2.0/I call flow interface 4-7 Meridian IVR VT100 Gateway Development Guide Product release 2.0/I Figure 4-4COMO 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.”...
Page 68 - COMO cell branches; Table 4-1 describes each branch of the COMO cell.l; Branch; ERROR
IVR 2.0/I call flow interface 4-9 Meridian IVR VT100 Gateway Development Guide Product release 2.0/I Note: You must enter the output buffers in the same order they will be used by the TRS process. If your application uses more than 10 output buffers, string COMO cells together until you have enough ...
Page 69 - Setting the COMA cell parameters; MORE DATA
4-10 IVR 2.0/I call flow interface 555-9001-316 Standard 1.0 February 1996 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. The last COMO cell should use the “END OF DATA” bra...
Page 70 - An application using the COMI, COMO, and COMA cells
IVR 2.0/I call flow interface 4-11 Meridian IVR VT100 Gateway Development Guide Product release 2.0/I An application using the COMI, COMO, and COMA cells Figure 4-7 shows a sample IVR 2.0/I application that uses the COMI, COMO, and COMA cells to retrieve a customer’s account balance stored on a host...
Page 72 - The ANSW cell answers the incoming call.
IVR 2.0/I call flow interface 4-13 Meridian IVR VT100 Gateway Development Guide Product release 2.0/I 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 ...
Page 73 - , to call three screen templates - one to choose the
4-14 IVR 2.0/I call flow interface 555-9001-316 Standard 1.0 February 1996 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...
Page 75 - ERR: Unable to reset application environment; TRS was unable to reset the 3270 system.; ERR: Unable to load configuration file; TRS was unable to load the configuration file trs.conf.; ERR: Failed to startup VT100 Server; TRS was unable to reset the vt100 system.; ERR: VT100 Server startup; VT100 Server has been started up.
A-1 Meridian IVR VT100 Gateway Development Guide Product release 2.0/I Appendix A: Host error messages Terminal Resource Server (TRS) Messages ERR: Unable to reset application environment Meaning: TRS was unable to reset the 3270 system. Action to take: Stop IVR 2.0/I. Make sure the 3270 board has b...
Page 76 - Host error messages; ERR: All communication boards are not operational
A-2 Host error messages 555-9001-316 Standard 1.0 February 1996 Action to take: Contact your Nortel service representative. ERR: Create_screen_templates Meaning: TRS was unable to open a screen template file or found a syntax error in the screen template files. Action to take: Check the screen templ...
Page 78 - ERR: xx is not a keyword
A-4 Host error messages 555-9001-316 Standard 1.0 February 1996 Action to take: Contact your Nortel service representative. ERR: xx is not a keyword Meaning: The screen template contains an invalid keyword. Action to take: Revise the screen template. Make sure the KEYWORD (&LOGIN_ID, &PASSWO...
Page 80 - ERR: Send Aid key failed
A-6 Host error messages 555-9001-316 Standard 1.0 February 1996 ERR: Send Aid key failed Meaning: TRS did not succeed in sending the aid key to the host. Action to take: Make sure that the host connection exists. ERR: CH=xx Process:ERR: Syntax error for variable operation Meaning: Syntax error in in...
Page 82 - TRS received an illegal command from another process.; ERR: Server Node file trs.node does not exist; trs.node file was missing from the envoy process node.; ERR: The server node name is the same as envoy node name; Contact your Nortel service representative.; ERR: Invalid Aid key specified use the Enter Key; Define a valid aid key.
A-8 Host error messages 555-9001-316 Standard 1.0 February 1996 ERR: CH=xx illegal Command xxx Meaning: TRS received an illegal command from another process. Action to take: Contact your Nortel service representative. ERR: Server Node file trs.node does not exist Meaning: trs.node file was missing f...
Page 83 - ERR: No Match Found for field id xx
Host error messages A-9 Meridian IVR VT100 Gateway Development Guide Product release 2.0/I ERR: Send_with_aid: Connect to session xx failed Meaning: TRS failed to connect to session xx before sending the aid key. Action to take: Check the communication system to make sure it works properly. ERR: Sen...
Page 86 - A-12 Host error messages; Make sure that ‘3270’ or ‘vt100’ is specified in the protocol; ERR: Incorrect syntax for ping action; xxx is an invalid protocol.; ERR: Possibly exceeded number of allowable boards; Revise the trs.conf file and make sure the total board
A-12 Host error messages 555-9001-316 Standard 1.0 February 1996 ERR: Protocol missing, specify 3270 or VT100 Meaning: The protocol type was missing from the trs.conf protocol field. Action to take: Make sure that ‘3270’ or ‘vt100’ is specified in the protocol field. ERR: Incorrect syntax for ping a...
Page 88 - A-14 Host error messages; lubuf.dat file defined an invalid board number xx.
A-14 Host error messages 555-9001-316 Standard 1.0 February 1996 ERR: in map.dat:Session xx not defined in trs.conf Meaning: The session number xx defined in the map.dat file was not defined in the trs.conf file. Action to take: Revise the map.dat file or the trs.conf file and make sure that the ses...
Page 89 - TRS was unable to open the screen file xx.; ERR: Memory allocation failure for Screen entry; ERR: No header data for Screen file xx; Header data was missing from the screen template file xx.; ERR: Screen name xx exceeds xxx characters; Change xx so that it does not exceed xxx characters.
Host error messages A-15 Meridian IVR VT100 Gateway Development Guide Product release 2.0/I Action to take: Revise the password in lubuf.dat file so that the length of the password does not exceed xxx. ERR: In ../3270/lubuf.dat:lu_buf1 exceeds xx characters Meaning: There are too many characters in ...
Page 91 - Host error messages A-17
Host error messages A-17 Meridian IVR VT100 Gateway Development Guide Product release 2.0/I Action to take: Revise the application to keep the screen templates within the limit specified by xx. ERR: Open action file xx failed Meaning: TRS failed to open the action file xx. Action to take: Create or ...
Page 93 - Glossary; A person who creates IVR applications.
Glossary-1 Meridian IVR VT100 Gateway Development Guide Product release 2.0/I Glossary VT100 Gateway terms This section lists brief definitions of the terms appearing in this guide. Application With respect to IVR, an application is a program that controls the activity on one or more telephone trunk...
Page 94 - A telephone trunk within a cluster of APs.
Glossary-2 555-9001-316 Standard 1.0 February 1996 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 proce...
Page 95 - Terminal type emulated by the VT100 Gateway product.
Glossary-3 Meridian IVR VT100 Gateway Development Guide Product release 2.0/I Transaction The function performed by a set of action and screen template files when executed by the TRS. TRS Terminal Resource Server. IVR process that manages the assignment of available VT100 terminal resources on the a...
