Nortel VT100 - Manuals

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...

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...

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...

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...

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...

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...

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 ...

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...

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 ...

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...

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...

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...

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...

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 ...

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...

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...

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 ...

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...

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...

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...

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...

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...

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,...

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...

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...

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...

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...

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...

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...

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...

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...

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...

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 /...

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...

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...

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...

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...

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...

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...

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 ...

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...

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...

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...

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...

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 ...

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....

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 ...

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.”...

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 ...

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...

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...

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 ...

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...

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...

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...

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...

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...

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...

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...

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...

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...

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 ...

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 ...

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...

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...

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...