Nortel NetworksメーカーVT100の使用説明書/サービス説明書
ページ先へ移動 of 97
Meridian IVR VT100 Gate wa y De velopment Guide Publication n umber : 555-9001-316 Product release: Meridian IVR 2.0/I Document release: Standard 1.0 Date: Februar y 1996 © 1996 Nor ther n T elecom All rights reser ved Printed in the United States of Amer ica Inf ormation is subject to change without notice.
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.
v Meridian IVR VT100 Gateway Development Guide Product release 2.0/I Contents About this guide ix Who should use this guide . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ix How to use this guide. . . . . . . . . . . . . . . . . . .
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 .
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 .
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 resources external to the application processor.
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 provides information on troubleshooting.
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.
1-2 About the VT100 Gateway 555-9001-316 Standard 1.0 February 1996 Figure 1-1 Terminals connected to a host computer The VT100 terminal uses an asynchronous communication protocol to transmit characters to and from a host computer.
About the VT100 Gateway 1-3 Meridian IVR VT100 Gateway Development Guide Product release 2.0/I Figure 1-2 VT100 application screen sample An active host to terminal connection is called a session. The VT100 Gateway can execute a series of transactions during a session.
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.
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 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.
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 acti ve 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.
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 and from the TRS’s buffers.
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.
Template files 2-3 Meridian IVR VT100 Gateway Development Guide Product release 2.0/I Figure 2-1 Voice response system vs. terminal operator The TRS requires two types of template files: • Action templates , which describe the sequence of screens traversed in order to perform a specific transaction.
2-4 Template files 555-9001-316 Standard 1.0 February 1996 Figure 2-2 Action and screen templates VT100 based applications often have format inconsistencies that make it difficult for the TRS to efficiently determine when the host application is ready for input and what region of the host screen contains vital information.
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.
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.
Template files 2-7 Meridian IVR VT100 Gateway Development Guide Product release 2.0/I Figure 2-4 Action 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 .
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 template. If a comment begins a line, no non-comment fields may follow the comment in that line.
Template files 2-9 Meridian IVR VT100 Gateway Development Guide Product release 2.0/I Figure 2-5 Reset-action template sequence sample Entering a hyphen “-” in the reset-action entry indicates that no reset-action template is specified.
2-10 Template files 555-9001-316 Standard 1.0 February 1996 Figure 2-6 Reset-action template sample The action template using this reset-action template would enter reset_cust as the reset-action entry.
Template files 2-11 Meridian IVR VT100 Gateway Development Guide Product release 2.0/I Figure 2-7 Logout action flow The logout-action template locates the screen where the transaction failed.
2-12 Template files 555-9001-316 Standard 1.0 February 1996 Figure 2-8 Logout-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.
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.
2-14 Template files 555-9001-316 Standard 1.0 February 1996 Figure 2-9 Screen 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.
Template files 2-15 Meridian IVR VT100 Gateway Development Guide Product release 2.0/I Figure 2-10 Application screen for accounting application Different transactions may access different fields on a screen.
2-16 Template files 555-9001-316 Standard 1.0 February 1996 Figure 2-11 Screen template syntax 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.
Template files 2-17 Meridian IVR VT100 Gateway Development Guide Product release 2.0/I Figure 2-12 Screen template for accounting application In Figure 2-12, the first line is a comment describing the screen template file. The screen-name i s “customer,” the name of the screen template file without the .
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 the “#” symbol.
Template files 2-19 Meridian IVR VT100 Gateway Development Guide Product release 2.0/I validation-tag This entry specifies the validation-tag used on the screen. The entry should be text that always appears in the same location every time this screen displays.
2-20 Template files 555-9001-316 Standard 1.0 February 1996 Figure 2-13 The field-descriptor syntax Note: If the application running on the host is stream-based, meaning the screen scrolls as the user.
Template files 2-21 Meridian IVR VT100 Gateway Development Guide Product release 2.0/I If you enter “0,0” and a hyphen for the row,column and field-name entries, the field I/O specified is executed at the current cursor location.
2-22 Template files 555-9001-316 Standard 1.0 February 1996 T able 2-1 V alid 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.
Template files 2-23 Meridian IVR VT100 Gateway Development Guide Product release 2.0/I When entering a field-descriptor , the entries on the line should be separated by white space or tab characters. If you are entering text for the field I/O, the TRS ignores any white space you include with the value until it encounters the new line character (e.
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. T able 2-2 V alid key names This line may appear anywhere after the screen-name line (i.e., the first non-comment line).
Template files 2-25 Meridian IVR VT100 Gateway Development Guide Product release 2.0/I sleep-descriptor (optional) A sleep-descripto r 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 after processing a key-descriptor .
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 .
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.
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.
Getting started 3-3 Meridian IVR VT100 Gateway Development Guide Product release 2.0/I Figure 3-1 screen.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.
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-2 screen.conf file In Figure 3-2, PROGRAM MENU is the keyword for the first screen.
Getting started 3-5 Meridian IVR VT100 Gateway Development Guide Product release 2.0/I Figure 3-3 trs.conf file syntax The colons (:) and the greater than (>) symbols are used as field delimiters and must be placed in the specified positions without any additional white space.
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.
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.
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-6 vt100.ctl file syntax Figure 3-7 shows a vt100.ctl file, based on the example trs.
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.
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.
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 detection.
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.
3-14 Getting started 555-9001-316 Standard 1.0 February 1996 Figure 3-9 Initial-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.
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.
3-16 Getting started 555-9001-316 Standard 1.0 February 1996 Figure 3-10 Logout-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 the TRS process to login.
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 that screen.
3-18 Getting started 555-9001-316 Standard 1.0 February 1996 Figure 3-11 Action 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 .
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 templates.
3-20 Getting started 555-9001-316 Standard 1.0 February 1996 Figure 3-13 Logout-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 successful.
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 script VT100 transactions as action and screen templates, you can begin integrating these templates into your IVR 2.
4-2 IVR 2.0/I call flow interface 555-9001-316 Standard 1.0 February 1996 Figure 4-2 Activating 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 the caller and create the corresponding IVR 2.
IVR 2.0/I call flow interface 4-3 Meridian IVR VT100 Gateway Development Guide Product release 2.0/I Figure 4-3 COMI cell parameter window start getbalance transaction.
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 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.
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”.
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.
IVR 2.0/I call flow interface 4-7 Meridian IVR VT100 Gateway Development Guide Product release 2.0/I 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.
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 information to the call audit statistics file (audit_stat.
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 buffers.
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.
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 computer.
4-12 IVR 2.0/I call flow interface 555-9001-316 Standard 1.0 February 1996 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.
IVR 2.0/I call flow interface 4-13 Meridian IVR VT100 Gateway Development Guide Product release 2.0/I T able 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.
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.
IVR 2.0/I call flow interface 4-15 Meridian IVR VT100 Gateway Development Guide Product release 2.0/I Figure 4-8 COMI/COMO cell parameters, TRS templates, and VT100 screens ACME Accounting 1 Accounts .
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.
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.
Host error messages A-3 Meridian IVR VT100 Gateway Development Guide Product release 2.0/I ERR: All available sessions are non-operational Meaning: None of the sessions is operational. Action to take: Make sure the communication board has been downloaded correctly.
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.
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 mode Meaning: This particular session is not working. TRS was unable to attach this session. Action to take: Contact your Nortel service representative.
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 internal variable operation.
Host error messages A-7 Meridian IVR VT100 Gateway Development Guide Product release 2.0/I Action to take: None. Notification only. ERR: 3270 Envoy Process Startup Meaning: 3270 envoy has been started up. Action to take: None. Notification only. ERR: Process Startup Meaning: The TRS process with no 3270 communication capability has been started up.
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.
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.
A-10 Host error messages 555-9001-316 Standard 1.0 February 1996 Action to take: Contact your Nortel service representative. ERR: Create_queue_object: Attempt to create Queue class instance failed Meaning: TRS was unable to allocate memory for the QUEUE_CLASS structure.
Host error messages A-11 Meridian IVR VT100 Gateway Development Guide Product release 2.0/I Action to take: Contact your Nortel service representative. ERR: Create_idle_timer: Idle timer memory allocation failed Meaning: TRS was unable to allocate memory for the idle timer structure.
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.
Host error messages A-13 Meridian IVR VT100 Gateway Development Guide Product release 2.0/I ERR: First LU cannot be less than xx. Meaning: The first session defined in the trs.conf file was less than allowed as specified by xx. Action to take: Revise the session field of the trs.
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.
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 the lu_buf1 field defined in the lubuf.
A-16 Host error messages 555-9001-316 Standard 1.0 February 1996 ERR: Screen name xx must match the file name without .scn Meaning: Invalid screen name defined in the screen template file. Action to take: Revise the screen template file and make sure the screen name is the screen template file name without .
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.
A-18 Host error messages 555-9001-316 Standard 1.0 February 1996 ERR: reset action xx of the action xxx not found Meaning: The reset action template xx defined in the action template xxx was not found under the 3270 directory. Action to take: Create the appropriate reset template file.
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 trunks connected to an AP.
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 process.
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 application processor.
.
Meridian IVR VT100 Gate wa y De velopment Guide Nor tel Customer Documentation 522 University A venue , 14th Floor T oronto , Ontario, Canada M5G 1W7 © 1996 Nor thern T elecom All rights reser ved Publication number: 555-9001-316 Product release: 2.0/I Document release: Standard 1.
デバイスNortel Networks VT100の購入後に(又は購入する前であっても)重要なポイントは、説明書をよく読むことです。その単純な理由はいくつかあります:
Nortel Networks VT100をまだ購入していないなら、この製品の基本情報を理解する良い機会です。まずは上にある説明書の最初のページをご覧ください。そこにはNortel Networks VT100の技術情報の概要が記載されているはずです。デバイスがあなたのニーズを満たすかどうかは、ここで確認しましょう。Nortel Networks VT100の取扱説明書の次のページをよく読むことにより、製品の全機能やその取り扱いに関する情報を知ることができます。Nortel Networks VT100で得られた情報は、きっとあなたの購入の決断を手助けしてくれることでしょう。
Nortel Networks VT100を既にお持ちだが、まだ読んでいない場合は、上記の理由によりそれを行うべきです。そうすることにより機能を適切に使用しているか、又はNortel Networks VT100の不適切な取り扱いによりその寿命を短くする危険を犯していないかどうかを知ることができます。
ですが、ユーザガイドが果たす重要な役割の一つは、Nortel Networks VT100に関する問題の解決を支援することです。そこにはほとんどの場合、トラブルシューティング、すなわちNortel Networks VT100デバイスで最もよく起こりうる故障・不良とそれらの対処法についてのアドバイスを見つけることができるはずです。たとえ問題を解決できなかった場合でも、説明書にはカスタマー・サービスセンター又は最寄りのサービスセンターへの問い合わせ先等、次の対処法についての指示があるはずです。