Nortel VT100 инструкция обслуживания

1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97

Идти на страницу of

Хорошее руководство по эксплуатации

Законодательство обязывает продавца передать покупателю, вместе с товаром, руководство по эксплуатации Nortel VT100. Отсутствие инструкции либо неправильная информация, переданная потребителю, составляют основание для рекламации в связи с несоответствием устройства с договором. В законодательстве допускается предоставлении руководства в другой, чем бумажная форме, что, в последнее время, часто используется, предоставляя графическую или электронную форму инструкции Nortel VT100 или обучающее видео для пользователей. Условием остается четкая и понятная форма.

Что такое руководство?

Слово происходит от латинского "instructio", тоесть привести в порядок. Следовательно в инструкции Nortel VT100 можно найти описание этапов поведения. Цель инструкции заключается в облегчении запуска, использования оборудования либо выполнения определенной деятельности. Инструкция является набором информации о предмете/услуге, подсказкой.

К сожалению немного пользователей находит время для чтения инструкций Nortel VT100, и хорошая инструкция позволяет не только узнать ряд дополнительных функций приобретенного устройства, но и позволяет избежать возникновения большинства поломок.

Из чего должно состоять идеальное руководство по эксплуатации?

Прежде всего в инструкции Nortel VT100 должна находится:
- информация относительно технических данных устройства Nortel VT100
- название производителя и год производства оборудования Nortel VT100
- правила обслуживания, настройки и ухода за оборудованием Nortel VT100
- знаки безопасности и сертификаты, подтверждающие соответствие стандартам

Почему мы не читаем инструкций?

Как правило из-за нехватки времени и уверенности в отдельных функциональностях приобретенных устройств. К сожалению само подсоединение и запуск Nortel VT100 это слишком мало. Инструкция заключает ряд отдельных указаний, касающихся функциональности, принципов безопасности, способов ухода (даже то, какие средства стоит использовать), возможных поломок Nortel VT100 и способов решения проблем, возникающих во время использования. И наконец то, в инструкции можно найти адресные данные сайта Nortel, в случае отсутствия эффективности предлагаемых решений. Сейчас очень большой популярностью пользуются инструкции в форме интересных анимаций или видео материалов, которое лучше, чем брошюра воспринимаются пользователем. Такой вид инструкции позволяет пользователю просмотреть весь фильм, не пропуская спецификацию и сложные технические описания Nortel VT100, как это часто бывает в случае бумажной версии.

Почему стоит читать инструкции?

Прежде всего здесь мы найдем ответы касательно конструкции, возможностей устройства Nortel VT100, использования отдельных аксессуаров и ряд информации, позволяющей вполне использовать все функции и упрощения.

После удачной покупки оборудования/устройства стоит посвятить несколько минут для ознакомления с каждой частью инструкции Nortel VT100. Сейчас их старательно готовят или переводят, чтобы они были не только понятными для пользователя, но и чтобы выполняли свою основную информационно-поддерживающую функцию.

Содержание руководства

  • Страница 1

    Meridian IVR VT100 Gate w a y De v elopment Guide Publication n umber : 555-9001-316 Product release: Meridian IVR 2.0/I Document release: Standard 1.0 Date: F ebruar y 1996 © 1996 Nor ther n T elecom All rights reser ved Printed in the United States of Amer ica Inf or mation is subject to change without notice. Nor ther n T elecom reser v es the [...]

  • Страница 2

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

  • Страница 3

    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 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .ix Additional Nor tel manuals . . . . . . . . . . . . . . . . .[...]

  • Страница 4

    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 . . . . . . . . . . . . . . . . . . . . . . . 4-2 An application using[...]

  • Страница 5

    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 Reset-action template for accounting application .[...]

  • Страница 6

    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. The [...]

  • Страница 7

    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. Addition[...]

  • Страница 8

    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 description of the TRS configuration • a bri[...]

  • Страница 9

    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. The VT100 Gateway communicates with a host through a serial port and a modem, or through a serial port and a direct c[...]

  • Страница 10

    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. A transaction is the series of steps required to perform a specific function lik[...]

  • Страница 11

    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 to Meridian Mail • be connected to one or m[...]

  • Страница 12

    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.0/I architecture, and starts when Meridian IVR 2.0[...]

  • Страница 13

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

  • Страница 14

    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. Coupled with the VT1[...]

  • Страница 15

    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 ASCII files called template files. Template files prov[...]

  • Страница 16

    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. • Screen templates , which validate each scre[...]

  • Страница 17

    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. These inconsistencies are[...]

  • Страница 18

    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 of the templates, as well as the information neces[...]

  • Страница 19

    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 extension .act. For example, if you created an actio[...]

  • Страница 20

    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 . The reset-action is reset_cust (file name reset_cust.act ), and the logou[...]

  • Страница 21

    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. However, a comment may appear after a non-comment field, such as after the screen template name as shown in Figu[...]

  • Страница 22

    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. If no reset-action template is specified and the transaction being executed by the action template fails, the[...]

  • Страница 23

    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. logout-action The logout-action specifies a logout-action template to be executed if the reset-action template fails, or if the transaction fails a[...]

  • Страница 24

    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. If for example, the transaction failed at the account number screen, the logout-action template locates the screen template with the appropriate validation t[...]

  • Страница 25

    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. Enter the screen templates in the exact order they appear during the transaction. Each s[...]

  • Страница 26

    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 the last screen of the action template that used man[...]

  • Страница 27

    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. A sample application screen showing fields is shown in Figure 2-10. He[...]

  • Страница 28

    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. For example, a transaction to locate the payment due would only need to access that field, while a transaction retrieving the customer’s ba[...]

  • Страница 29

    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. #comment screen-name v alidation tag offset v alidation tag[...]

  • Страница 30

    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 .scn extension. The “1,1” represents t[...]

  • Страница 31

    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. If a comment begins a line, n[...]

  • Страница 32

    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. For the example, “Account” is always displayed starting at location 1,1 whenever a cu[...]

  • Страница 33

    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 enters data and retrieves responses, you should enter the field-descriptor as follows: 0,0- BLANKOUT In this instance, the field-descriptor will clea[...]

  • Страница 34

    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. To locate field-names on the screen for reading, the offset of the upper left corner of the screen is 1,1 and the lo[...]

  • Страница 35

    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. For retrieving data into an output buffer, $ num indicates the number of characters to be retrie[...]

  • Страница 36

    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.g[...]

  • Страница 37

    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). As with field-descriptor lines, the entries on this line must be separated by [...]

  • Страница 38

    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 . The waiting per[...]

  • Страница 39

    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 as 0,0 @25 Initial-action templates Before you can[...]

  • Страница 40

    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 templates necessary to navigate through the host [...]

  • Страница 41

    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 process host output by eliminating the time it spends [...]

  • Страница 42

    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. If the keyword contains a space or a colon, then enclose t[...]

  • Страница 43

    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. Since it contains a “s13is” case, it also searches for the b[...]

  • Страница 44

    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. app-name The app-name entry identifies the application on the mainfra[...]

  • Страница 45

    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 the specified sessions to the screen on the host co[...]

  • Страница 46

    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 sessions that remain idle for a period of time. You ca[...]

  • Страница 47

    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.act , and • initialize sessions 15-17 for[...]

  • Страница 48

    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.conf file in Figure 3-5. Figure 3-7 vt100.ctl file for accounting application session-number de vice-name ter minal-type 2 /de v/ttyi1b vt100 3 /de v/ttyi1c vt100[...]

  • Страница 49

    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. The entry must be a single number, ranging from 2 t[...]

  • Страница 50

    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-8 com.conf file Creating the com.conf file allows you to adjust the following values[...]

  • Страница 51

    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. PAREVN sets parity to even. PARODD sets parit[...]

  • Страница 52

    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 templates in the following way: • The initial-acti[...]

  • Страница 53

    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. It then executes the screen templates acctlog1 , acctlog2 , then atacctmenu . Templates Correspond[...]

  • Страница 54

    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 following: • at the system prompt, enters the comm[...]

  • Страница 55

    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. TRS always executes th[...]

  • Страница 56

    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. Figure 3-11 shows the action tem[...]

  • Страница 57

    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 . The last line in the “customer” screen template places the contents of the field sta[...]

  • Страница 58

    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. Figure 3-12 Reset-action template [...]

  • Страница 59

    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. If the transaction fails before the [...]

  • Страница 60

    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.0/I Applications (Figure 4-1). Figure 4-1 Accessing the mainframe This chapter explains •[...]

  • Страница 61

    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.0[...]

  • Страница 62

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

  • Страница 63

    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. The cell name shown in Figure 4-3 is “start getbalance transac[...]

  • Страница 64

    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. This indicates the maximum time for the COMI [...]

  • Страница 65

    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 host computer is not sending any data to any outpu[...]

  • Страница 66

    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.” The name helps identify the function of the [...]

  • Страница 67

    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.d): • Application Name • Cell Name • Cell Number • Date and Time of Cell Execution • Contents of the Cell Comment field • Contents of the Call A[...]

  • Страница 68

    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. Connect the input branch of each subseque[...]

  • Страница 69

    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” branch. Setting the COMA cell paramet[...]

  • Страница 70

    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. This example application uses the act[...]

  • Страница 71

    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.0/I is started on the application processor). Once a call from a customer is received, the IVR[...]

  • Страница 72

    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. Step Description Cell 1 The ANSW[...]

  • Страница 73

    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 Accounts Receivable menu, one to enter the accoun[...]

  • Страница 74

    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 Receivable 2 Accounts Payable 3 Reports 4 Inventory 5 Exit Enter menu selection: Templates Corresponding Screens ACME Accounting 1 Accounts Receivable[...]

  • Страница 75

    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 been downloaded correctly. The download command sho[...]

  • Страница 76

    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 template files. Make sure they are syntax error free, r[...]

  • Страница 77

    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. The download command should be included in .profile file. ERR: xx Sessions are Opera[...]

  • Страница 78

    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, &PASSWORD, &LU_BUF1 and &LU_BUF2) are spelled cor[...]

  • Страница 79

    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. ERR: CH=xx ERR::Parse: Incorrect Action [xxx] Meanin[...]

  • Страница 80

    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. Action to take: Check t[...]

  • Страница 81

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

  • Страница 82

    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 from the envoy process node. Action to take: This e[...]

  • Страница 83

    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: Send_with_aid: failed with return code of xx Meaning:[...]

  • Страница 84

    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. Action to take: Contact your Nortel service representative. ERR: A request for [...]

  • Страница 85

    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. Action to take: Contact your Nortel service representative. ERR: [...]

  • Страница 86

    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 action Meaning: The heartbeat action templa[...]

  • Страница 87

    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.conf file. ERR: Last LU cannot be greater than xx Meaning: The last se[...]

  • Страница 88

    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 session number matches. ERR: read data from file ../3[...]

  • Страница 89

    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.dat file. A[...]

  • Страница 90

    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 .scn. ERR: Validate tag xx of screen xxx e[...]

  • Страница 91

    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 change permissions of the action template file to [...]

  • Страница 92

    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. ERR: logout action xx of the action xxx not found Meaning: Logo[...]

  • Страница 93

    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. With respect to a host compu[...]

  • Страница 94

    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. COMO Cell IVR cell that receives output from a[...]

  • Страница 95

    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. Moves data between IVR and a[...]

  • Страница 96

    [...]

  • Страница 97

    Meridian IVR VT100 Gate w a y De v elopment Guide Nor tel Customer Documentation 522 Univ ersity A ven ue, 14th Floor T oronto , Ontario, Canada M5G 1W7 © 1996 Nor ther n T elecom All rights reser ved Publication n umber : 555-9001-316 Product release: 2.0/I Document release: Standard 1.0 Date: F ebruar y 1996 Printed in the United States of Amer [...]