Nortel-networks VT100 Manuel d'utilisateur

Meridian IVR VT100 Gateway Development Guide Publication number: 555-9001-316Product release: Meridian IVR 2.0/IDocument release: Standard 1.0Date:

About the VT100 Gateway 1-3 Meridian IVR VT100 Gateway Development Guide Product release 2.0/I Figure 1-2VT100 application screen sample An act

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 Gatew

About the VT100 Gateway 1-5 Meridian IVR VT100 Gateway Development Guide Product release 2.0/I A Meridian IVR 2.0/I process called the Terminal

1-6 About the VT100 Gateway 555-9001-316 Standard 1.0 February 1996 ATTENTION! The TRS process for managing calls is restricted to handling one a

2-1 Meridian IVR VT100 Gateway Development Guide Product release 2.0/I Chapter 2: Template files The TRS process uses action and screen temp

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 oper

Template files 2-3 Meridian IVR VT100 Gateway Development Guide Product release 2.0/I Figure 2-1Voice response system vs. terminal operator The

2-4 Template files 555-9001-316 Standard 1.0 February 1996 Figure 2-2Action and screen templates VT100 based applications often have format inc

Template files 2-5 Meridian IVR VT100 Gateway Development Guide Product release 2.0/I The action templates, screen templates, and screen.conf f

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 edito

iii Meridian IVR VT100 Gateway Development Guide Product release 2.0/I Publication history February 1996 This document is the first standard issu

Template files 2-7 Meridian IVR VT100 Gateway Development Guide Product release 2.0/I Figure 2-4Action template for accounting application In F

2-8 Template files 555-9001-316 Standard 1.0 February 1996 Comments start with the “#” symbol and can be embedded anywhere in the action templa

Template files 2-9 Meridian IVR VT100 Gateway Development Guide Product release 2.0/I Figure 2-5Reset-action template sequence sample Entering

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 files 2-11 Meridian IVR VT100 Gateway Development Guide Product release 2.0/I Figure 2-7Logout action flow The logout-action template

2-12 Template files 555-9001-316 Standard 1.0 February 1996 Figure 2-8Logout-action template sample screen-template The screen-template (the

Template files 2-13 Meridian IVR VT100 Gateway Development Guide Product release 2.0/I Note: You should not specify a reset-action template i

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

Template files 2-15 Meridian IVR VT100 Gateway Development Guide Product release 2.0/I Figure 2-10Application screen for accounting application

2-16 Template files555-9001-316 Standard 1.0 February 1996Figure 2-11Screen template syntaxThe lines depicted as • represent additional field-des

v Meridian IVR VT100 Gateway Development Guide Product release 2.0/I Contents About this guide ix Who should use this guide. . . . . . . . . .

Template files 2-17Meridian IVR VT100 Gateway Development Guide Product release 2.0/IFigure 2-12Screen template for accounting applicationIn Figu

2-18 Template files555-9001-316 Standard 1.0 February 1996#commentThe first line of the template in Figure 2-12 is a comment. The comment line i

Template files 2-19Meridian IVR VT100 Gateway Development Guide Product release 2.0/Ivalidation-tagThis entry specifies the validation-tag used o

2-20 Template files555-9001-316 Standard 1.0 February 1996Figure 2-13The field-descriptor syntaxNote: If the application running on the host is

Template files 2-21Meridian IVR VT100 Gateway Development Guide Product release 2.0/IIf you enter “0,0” and a hyphen for the row,column and field

2-22 Template files555-9001-316 Standard 1.0 February 1996Table 2-1Valid field I/O entriesNote: Place the asterisk and dollar sign characters in

Template files 2-23Meridian IVR VT100 Gateway Development Guide Product release 2.0/IWhen entering a field-descriptor, the entries on the line sh

2-24 Template files555-9001-316 Standard 1.0 February 1996keyname The name of the key for this screen. Table 2-2 lists the valid keys you can e

Template files 2-25Meridian IVR VT100 Gateway Development Guide Product release 2.0/Isleep-descriptor (optional)A sleep-descriptor causes the tra

2-26 Template files555-9001-316 Standard 1.0 February 1996position-indicator This entry should be set to 0,0. @ Identifies that this line is a

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

3-1 Meridian IVR VT100 Gateway Development Guide Product release 2.0/I Chapter 3: Getting started Before using the VT100 Gateway Before you

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 me

Getting started 3-3 Meridian IVR VT100 Gateway Development Guide Product release 2.0/I Figure 3-1screen.conf file syntax The colons (:) are us

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

Getting started 3-5 Meridian IVR VT100 Gateway Development Guide Product release 2.0/I Figure 3-3trs.conf file syntax The colons (:) and the gr

3-6 Getting started 555-9001-316 Standard 1.0 February 1996 initial-template The initial-template entry identifies an initial-action template

Getting started 3-7 Meridian IVR VT100 Gateway Development Guide Product release 2.0/I heartbeat You can specify an optional heartbeat action

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:• initia

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 vt10

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

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

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

3-12 Getting started555-9001-316 Standard 1.0 February 1996Baud Rate300 to 19200. Setting the baud rate tells the TRS the rate at which it is to

Getting started 3-13Meridian IVR VT100 Gateway Development Guide Product release 2.0/IA complete sample transactionThis section summarizes how th

3-14 Getting started555-9001-316 Standard 1.0 February 1996Figure 3-9Initial-action template for accounting applicationThe initial-action templat

Getting started 3-15Meridian IVR VT100 Gateway Development Guide Product release 2.0/IThe screen template acctlog1.scn does the following:• enter

3-16 Getting started555-9001-316 Standard 1.0 February 1996Figure 3-10Logout-action template used by the initial-action template for accounting a

Getting started 3-17Meridian IVR VT100 Gateway Development Guide Product release 2.0/IAction template performing a transactionAs shown in Figure

3-18 Getting started555-9001-316 Standard 1.0 February 1996Figure 3-11Action template for accounting application The number 1 and the account num

Getting started 3-19Meridian IVR VT100 Gateway Development Guide Product release 2.0/IThe reset-action template is designed to return the session

3-20 Getting started555-9001-316 Standard 1.0 February 1996Figure 3-13Logout-action template for accounting applicationThe logout-action template

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

4-1 Meridian IVR VT100 Gateway Development Guide Product release 2.0/I Chapter 4: IVR 2.0/I call flow interface Now that you understand how to

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 applica

IVR 2.0/I call flow interface 4-3 Meridian IVR VT100 Gateway Development Guide Product release 2.0/I Figure 4-3COMI cell parameter windowstart ge

4-4 IVR 2.0/I call flow interface 555-9001-316 Standard 1.0 February 1996 The following sections describe what you should enter in each area of t

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 secon

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 sen

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 fol

4-8 IVR 2.0/I call flow interface 555-9001-316 Standard 1.0 February 1996 Call Audit Enabled Determines if this cell logs the following informati

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

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

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

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 CO

4-12 IVR 2.0/I call flow interface 555-9001-316 Standard 1.0 February 1996 Figure 4-7IVR 2.0/I application accessing the TRS process from the COM

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

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 re

IVR 2.0/I call flow interface 4-15 Meridian IVR VT100 Gateway Development Guide Product release 2.0/I Figure 4-8COMI/COMO cell parameters, TRS te

A-1 Meridian IVR VT100 Gateway Development Guide Product release 2.0/I Appendix A: Host error messages Terminal Resource Server (TRS) Messages

A-2 Host error messages 555-9001-316 Standard 1.0 February 1996 Action to take: Contact your Nortel service representative. ERR: Create_screen

Host error messages A-3 Meridian IVR VT100 Gateway Development Guide Product release 2.0/I ERR: All available sessions are non-operational Meani

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

Host error messages A-5 Meridian IVR VT100 Gateway Development Guide Product release 2.0/I ERR: CH=xx BD xxx SS xxxx: Session not working-manual

1-1 Meridian IVR VT100 Gateway Development Guide Product release 2.0/I Chapter 1: About the VT100 Gateway This chapter provides an introduct

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 t

Host error messages A-7 Meridian IVR VT100 Gateway Development Guide Product release 2.0/I Action to take: None. Notification only. ERR: 327

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 a

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 Mean

A-10 Host error messages555-9001-316 Standard 1.0 February 1996Action to take: Contact your Nortel service representative. ERR: Create_queue_objec

Host error messages A-11Meridian IVR VT100 Gateway Development Guide Product release 2.0/IAction to take: Contact your Nortel service representat

A-12 Host error messages555-9001-316 Standard 1.0 February 1996ERR: Protocol missing, specify 3270 or VT100 Meaning: The protocol type was missin

Host error messages A-13Meridian IVR VT100 Gateway Development Guide Product release 2.0/IERR: First LU cannot be less than xx. Meaning: The firs

A-14 Host error messages555-9001-316 Standard 1.0 February 1996ERR: in map.dat:Session xx not defined in trs.conf Meaning: The session number xx d

Host error messages A-15Meridian IVR VT100 Gateway Development Guide Product release 2.0/IAction to take: Revise the password in lubuf.dat file s

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 a

A-16 Host error messages555-9001-316 Standard 1.0 February 1996ERR: Screen name xx must match the file name without .scn Meaning: Invalid screen n

Host error messages A-17Meridian IVR VT100 Gateway Development Guide Product release 2.0/IAction to take: Revise the application to keep the scre

A-18 Host error messages555-9001-316 Standard 1.0 February 1996ERR: reset action xx of the action xxx not found Meaning: The reset action templat

Glossary-1 Meridian IVR VT100 Gateway Development Guide Product release 2.0/I Glossary VT100 Gateway terms This section lists brief definitio

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 transac

Glossary-3 Meridian IVR VT100 Gateway Development Guide Product release 2.0/I Transaction The function performed by a set of action and screen

Meridian IVR VT100 Gateway Development Guide NortelCustomer Documentation522 University Avenue, 14th FloorToronto, Ontario, CanadaM5G 1W7© 1996 North