Avaya IVR - Business Communications Manager Upgrade Guide

Avaya Business Communications
Manager—IVR Upgrade Guide

NN40070-400, 02.02

4.0

September 2010

©

2010 Avaya Inc.

All Rights Reserved.

Notice

While reasonable efforts have been made to ensure that the
information in this document is complete and accurate at the time of
printing, Avaya assumes no liability for any errors. Avaya reserves the
right to make changes and corrections to the information in this
document without the obligation to notify any person or organization of
such changes.

Documentation disclaimer

Avaya shall not be responsible for any modifications, additions, or
deletions to the original published version of this documentation unless
such modifications, additions, or deletions were performed by Avaya.
End User agree to indemnify and hold harmless Avaya, Avaya's agents,
servants and employees against all claims, lawsuits, demands and
judgments arising out of, or in connection with, subsequent
modifications, additions or deletions to this documentation, to the
extent made by End User.

Link disclaimer

Avaya is not responsible for the contents or reliability of any linked Web
sites referenced within this site or documentation(s) provided by Avaya.
Avaya is not responsible for the accuracy of any information, statement
or content provided on these sites and does not necessarily endorse
the products, services, or information described or offered within them.
Avaya does not guarantee that these links will work all the time and has
no control over the availability of the linked pages.

Warranty

Avaya provides a limited warranty on this product. Refer to your sales
agreement to establish the terms of the limited warranty. In addition,
Avaya’s standard warranty language, as well as information regarding
support for this product, while under warranty, is available to Avaya
customers and other parties through the Avaya Support Web site:

http://www.avaya.com/support. Please note that if you acquired the

product from an authorized Avaya reseller outside of the United States
and Canada, the warranty is provided to you by said Avaya reseller and
not by Avaya.

Licenses

THE SOFTWARE LICENSE TERMS AVAILABLE ON THE AVAYA
WEBSITE,
APPLICABLE TO ANYONE WHO DOWNLOADS, USES AND/OR
INSTALLS AVAYA SOFTWARE, PURCHASED FROM AVAYA INC.,
ANY AVAYA AFFILIATE, OR AN AUTHORIZED AVAYA RESELLER
(AS APPLICABLE) UNDER A COMMERCIAL AGREEMENT WITH
AVAYA OR AN AUTHORIZED AVAYA RESELLER. UNLESS
OTHERWISE AGREED TO BY AVAYA IN WRITING, AVAYA DOES
NOT EXTEND THIS LICENSE IF THE SOFTWARE WAS OBTAINED
FROM ANYONE OTHER THAN AVAYA, AN AVAYA AFFILIATE OR AN
AVAYA AUTHORIZED RESELLER, AND AVAYA RESERVES THE
RIGHT TO TAKE LEGAL ACTION AGAINST YOU AND ANYONE
ELSE USING OR SELLING THE SOFTWARE WITHOUT A LICENSE.
BY INSTALLING, DOWNLOADING OR USING THE SOFTWARE, OR
AUTHORIZING OTHERS TO DO SO, YOU, ON BEHALF OF
YOURSELF AND THE ENTITY FOR WHOM YOU ARE INSTALLING,
DOWNLOADING OR USING THE SOFTWARE (HEREINAFTER
REFERRED TO INTERCHANGEABLY AS “YOU” AND “END USER”),
AGREE TO THESE TERMS AND CONDITIONS AND CREATE A
BINDING CONTRACT BETWEEN YOU AND AVAYA INC. OR THE
APPLICABLE AVAYA AFFILIATE (“AVAYA”).

Copyright

Except where expressly stated otherwise, no use should be made of
materials on this site, the Documentation(s) and Product(s) provided
by Avaya. All content on this site, the documentation(s) and the
product(s) provided by Avaya including the selection, arrangement and
design of the content is owned either by Avaya or its licensors and is

HTTP://SUPPORT.AVAYA.COM/LICENSEINFO/ ARE

protected
sui generis rights relating to the protection of databases. You may not
modify, copy, reproduce, republish, upload, post, transmit or distribute
in any way any content, in whole or in part, including any code and
software. Unauthorized reproduction, transmission, dissemination,
storage, and or use without the express written consent of Avaya can
be a criminal, as well as a civil, offense under the applicable law.

Third-party components

Certain software programs or portions thereof included in the Product
may contain software distributed under third party agreements (“Third
Party Components”), which may contain terms that expand or limit
rights to use certain portions of the Product (“Third Party Terms”).
Information regarding distributed Linux OS source code (for those
Products that have distributed the Linux OS source code), and
identifying the copyright holders of the Third Party Components and the
Third Party Terms that apply to them is available on the Avaya Support
Web site:

Trademarks

The trademarks, logos and service marks (“Marks”) displayed in this
site, the documentation(s) and product(s) provided by Avaya are the
registered or unregistered Marks of Avaya, its affiliates, or other third
parties. Users are not permitted to use such Marks without prior written
consent from Avaya or such third party which may own the Mark.
Nothing contained in this site, the documentation(s) and product(s)
should be construed as granting, by implication, estoppel, or otherwise,
any license or right in and to the Marks without the express written
permission of Avaya or the applicable third party.

Avaya is a registered trademark of Avaya Inc.

All other trademarks are the property of their respective owners.

Downloading documents

For the most current versions of documentation, see the Avaya Support
Web site:

Contact Avaya Support

Avaya provides a telephone number for you to use to report problems
or to ask questions about your product. The support telephone number
is 1-800-242-2121 in the United States. For additional support
telephone numbers, see the Avaya Web site:

support

by copyright and other intellectual property laws including the

http://www.avaya.com/support/Copyright/.

http://www.avaya.com/support

http://www.avaya.com/

2 Avaya Business Communications Manager—IVR Upgrade Guide September 2010

Contents

Chapter 1: Preface.....................................................................................................................7

Scope................................................................................................................................................................7

Intended Audience............................................................................................................................................7

Customer Service..............................................................................................................................................7

Navigation.........................................................................................................................................................8

Getting technical documentation.......................................................................................................................8

Getting product training.....................................................................................................................................8

Getting help from a distributor or reseller..........................................................................................................8

Getting technical support from the Avaya Web site..........................................................................................8

How to Use This Manual...................................................................................................................................9

Organization of This Manual.............................................................................................................................9

Conventions Used in This Manual..................................................................................................................10

Solaris and Windows Conventions..................................................................................................................11

Two-Button (Windows) vs. Three-Button (Solaris) Mouse..............................................................................12

Trademark Conventions..................................................................................................................................12

Chapter 2: New in this release...............................................................................................13

Features..........................................................................................................................................................13

Revision history...............................................................................................................................................13

Other changes.................................................................................................................................................13

Chapter 3: Avaya BCM - IVR 2.1 Upgrade Overview............................................................15

The Avaya BCM-IVR 2.1 Upgrade..................................................................................................................15

New or Updated Features of Avaya BCM-IVR 2.1..........................................................................................16

Avaya BCM-IVR 1.X Configuration.................................................................................................................16

Avaya BCM-IVR 2.1 Configuration..................................................................................................................17

Prerequisites for the Avaya BCM-IVR 2.1 Upgrade........................................................................................19

Application Developer.....................................................................................................................................19

System Administrator......................................................................................................................................19

Transition Issues.............................................................................................................................................20

Transition Issues for the Application Developer..............................................................................................20

Database Access Modes................................................................................................................................20

New PeriProducer 3.00 Blocks.......................................................................................................................21

Blocking/Non-blocking Execution....................................................................................................................21

Call Progress Detection..................................................................................................................................21

PeriProducer 3.00 Block Changes..................................................................................................................22

Connection IDs (Caller I/O blocks)..................................................................................................................22

Accessory Toolkit Blocks.................................................................................................................................22

Answer Block..................................................................................................................................................22

Disconnect Block.............................................................................................................................................23

System Block..................................................................................................................................................23

Send Host Block..............................................................................................................................................23

Receive Host Block.........................................................................................................................................24

Send Fax Block...............................................................................................................................................24

Receive Fax Block..........................................................................................................................................25

Originate Block................................................................................................................................................25

Record Block...................................................................................................................................................25

Resource Block...............................................................................................................................................25

Avaya Business Communications Manager—IVR Upgrade Guide September 2010 3

Discontinued Features and Functions.............................................................................................................26

Fax Composition.............................................................................................................................................26

Hardware Properties Window.........................................................................................................................26

Unsupported Resources.................................................................................................................................26

Obsolete Functions.........................................................................................................................................27

Other PeriProducer Changes..........................................................................................................................27

Enhanced Condition Data...............................................................................................................................27

Environment Options.......................................................................................................................................27

Conditions.......................................................................................................................................................30

Miscellaneous.................................................................................................................................................39

Transition Issues for the System Administrator...............................................................................................40

Documentation Issues.....................................................................................................................................40

Issue................................................................................................................................................................40

Chapter 4: Administrator on the Windows Workstation......................................................41

Windows Workstation Operating System Upgrade.........................................................................................41

Avaya BCM-IVR 1.X Uninstall Procedures......................................................................................................42

Uninstall Procedures with MPS 2.1 Software and Document CD...................................................................42

Avaya BCM-IVR 2.1 Installation Procedures...................................................................................................46

Installing PeriProducer 3.00 and PeriStudio 2.20...........................................................................................46

Avaya BCM-IVR 2.1 Toolkit Installation...........................................................................................................51

Introduction.....................................................................................................................................................51

Installing the Avaya BCM-IVR Toolkit..............................................................................................................53

License Service Installation.............................................................................................................................53

PeriView 2.1 and PeriView 2.1 Consolidator Installation.................................................................................56

Overview.........................................................................................................................................................56

Installing Avaya BCM-IVR 2.1 PeriView Consolidator.....................................................................................57

Launching Applications in PeriView................................................................................................................63

Loading Application .vex files..........................................................................................................................63

Loading User Defined Call Function Files.......................................................................................................66

Assigning and Starting Applications................................................................................................................67

Chapter 5: Administrator on the Avaya BCM 4.0 Platform..................................................73

Numbering components using Business Element Manager...........................................................................73

Enabling Host Communications with Business Element Manager..................................................................74

Retrieving existing Host Communications License File..................................................................................75

Getting and Applying the License File.............................................................................................................77

Application Resources....................................................................................................................................79

Chapter 6: Developer Upgrade on Windows Workstation...................................................81

Porting PeriProducer 2.30 Applications to PeriProducer 3.00........................................................................81

Application Porting Considerations.................................................................................................................81

Converting Standard PeriProducer 2.30 Applications to PeriProducer 3.00...................................................82

Load into PeriProducer 3.00...........................................................................................................................82

Using the PeriProducer Command Line to Port Applications..........................................................................82

Porting Events.................................................................................................................................................83

Conversion Logs.............................................................................................................................................83

Known Conversion Issues...............................................................................................................................84

Set Resource Label in 2.30.............................................................................................................................84

Unsupported 2.30 Resources.........................................................................................................................84

Resource Block Conversions..........................................................................................................................85

Flushing the Speak Prompt Buffer..................................................................................................................85

4 Avaya Business Communications Manager—IVR Upgrade Guide September 2010

System Transfer Connection ID Datacard.......................................................................................................85

Assign and Start PeriProducer 3.00 Applications...........................................................................................85

Chapter 7: Developer Upgrade on Fedora Workstation.......................................................87

Overview.........................................................................................................................................................87

Installing Fedora..............................................................................................................................................88

Installing IVR Plugin Development Environment.............................................................................................88

Building C/C++ Call Functions Libraries.........................................................................................................88

makecall_tux Tool............................................................................................................................................89

Chapter 8: Database Access Configuration..........................................................................91

Overview.........................................................................................................................................................91

VMST 3 on the Avaya BCM Node...................................................................................................................92

Install Patches on the Windows Node.............................................................................................................92

Configuring periq on the Windows Node.........................................................................................................92

Configuring sqlclnt on Windows Node............................................................................................................93

Index.........................................................................................................................................95

Avaya Business Communications Manager—IVR Upgrade Guide September 2010 5

6 Avaya Business Communications Manager—IVR Upgrade Guide September 2010

Chapter 1: Preface

Scope

Avaya Business Communications Manager (Avaya BCM) with Interactive Voice Response
(IVR) capabilities is a communications platform that delivers multimedia voice processing,
business telephony applications, and data networking services.

The Avaya BCM-IVR 2.1 Upgrade manual explains how to upgrade an Avaya BCM-IVR 1.X
system to an Avaya BCM-IVR 2.1 system. It further explains how to port existing applications to
run on the upgraded Avaya BCM-IVR 2.1. This manual is not intended to replace individual
software manuals. It is meant only to be used as a supplement to them.

Intended Audience

This manual is intended for both IVR Application Developers and Avaya BCM-IVR System
Administrators. This manual assumes that the reader is familiar with:

• Avaya BCM application development;

• site-specific operating procedures relating to the Avaya BCM;

• specific application functions performed by the Avaya BCM; and

• other equipment to which the Avaya BCM may be connected.

Basic knowledge of your operating system software is also assumed.

Customer Service

Visit the Avaya Web site to access the complete range of services and support that Avaya
provides. Go to http://www.avaya.com or go to one of the pages listed in the following sections.

Avaya Business Communications Manager—IVR Upgrade Guide September 2010 7

Preface

Navigation

•

Getting technical documentation on page 8

Getting product training on page 8

•

• Getting help from a distributor or reseller on page 8

• Getting technical support from the Avaya Web site on page 8

Getting technical documentation

To download and print selected technical publications and release notes directly from the
Internet, go to http://www.avaya.com/support.

Getting product training

Ongoing product training is available. For more information or to register, you can access the
Web site at http://www.avaya.com/support. From this Web site, you can locate the Training
contacts link on the left-hand navigation pane.

Getting help from a distributor or reseller

If you purchased a service contract for your Avaya product from a distributor or authorized
reseller, contact the technical support staff for that distributor or reseller for assistance.

Getting technical support from the Avaya Web site

The easiest and most effective way to get technical support for Avaya products is from the
Avaya Technical Support Web site at http://www.avaya.com/support.

8 Avaya Business Communications Manager—IVR Upgrade Guide September 2010

How to Use This Manual

This manual uses many standard terms relating to computer systems, software application
functions, and the Internet. However, it contains some terminology that can be explained only in
the context of the Avaya Media Processing Server (Avaya MPS). Refer to the Glossary of
Avaya Media Processing Server Series Terminology for definitions of Avaya MPS Series
specific terms.

Read this manual from start to finish at least once. When you are familiar with the document,
you can use the Table of Contents to locate topics of interest for reference and review.

If you are reading this document online, use the cross-reference links (shown in blue) to quickly
locate related topics. Position your cursor over the cross-reference link and click once. Click
any point in a Table of Contents entry to move to that topic. Click the page number of any Index
entry to access that topic page.

Familiarize yourself with various specialized textual references within the manual, see

Conventions Used in This Manual on page 10.

How to Use This Manual

Note:

Periphonics is now part of . The name Periphonics, and variations thereof, appear in this
manual only in reference to a product (for example, the PERImps package, the perirev
command, and so on).

Organization of This Manual

This manual is organized according to the needs and requirements of two distinct Avaya BCM­IVR users: System Administrators and Application Developers.

Chapter 1 — Introduction to the Avaya BCM - IVR Upgrade

Overviews the upgraded Avaya Business Communication Manager (Avaya BCM) with
Interactive Voice Response capabilities. Explains how to access documentation on Helmsman.

Chapter 2 — Administrator Upgrade on Windows Workstation

Discusses prerequisites and steps necessary to upgrade the Avaya BCM-IVR PeriView
Consolidator workstation.

Chapter 3 — Administrator Upgrade on Avaya BCM 4.0 Platform

Discusses how to manage Avaya BCMs using Business Element Manager. Explains how to
add Avaya BCMs to the Business Element Manager administration list.

Avaya Business Communications Manager—IVR Upgrade Guide September 2010 9

Preface

Chapter 4 — Developer Upgrade on Windows Workstation

Discusses steps necessary to port PeriProducer 2.30 applications to PeriProducer 3.00, as
well as porting events and conversion issues.

Chapter 5 — Developer Upgrade on Fedora Workstation

Discusses steps necessary to configure the Fedora workstation to compile C/C++ code for
User Defined External Call Functions.

Chapter 6 — Database Access Configuration

Discusses how to configure the Windows workstation for external database access.

Conventions Used in This Manual

This manual uses different fonts and symbols to differentiate between document elements and
types of information. These conventions are summarized in the following table.

Table 1: Conventions Used in This Manual

Notation Description

Normal text Normal text font is used for most of the document.

important term The Italics font introduces new terms, highlights meaningful words

or phrases, or distinguishes specific terms from nearby text.

system command This font indicates a system command or its arguments. Enter such

keywords exactly as shown (that is, do not fill in your own values).

command, condition
and alarm

file name /
directory

on-screen field This font indicates field labels, on-screen menu buttons, and action

<KEY NAME> A term that appears within angled brackets denotes a terminal

Command, Condition and Alarm references appear on the screen in
magenta text and reference the Command Reference Manual, the
MPS Developer User's Guide, or the Alarm Reference Manual,
respectively. Refer to these documents for detailed information
about Commands, Conditions, and Alarms.

This font highlights the names of disk directories, files, and
extensions for file names. It also shows what is displayed on a text­based screen (for example, to show the contents of a file.)

buttons.

keyboard key, a telephone keypad button, or a system mouse button.

Book Reference This font indicates the names of other publications referenced within

the document.

10 Avaya Business Communications Manager—IVR Upgrade Guide September 2010

Solaris and Windows Conventions

Notation Description

cross-reference A cross-reference appears on the screen in blue. Click the cross-

reference to access the referenced location. A cross-reference that
refers to a section name accesses the first page of that section.

Note: Notes identify important facts and other keys to understanding.

The caution icon identifies procedures or events that require special
attention. The icon indicates a warning that serious problems may
arise if the stated instructions are not followed implicitly.

The flying Window icon identifies procedures or events that apply to
the Windows operating system only.

The Solaris icon identifies procedures or events that apply to the
Solaris operating system only.

(1): Windows and the flying Window logo are either trademarks or registered

trademarks of Microsoft Corporation.

(2): Solaris® is a registered trademark of The Open Group in the U.S. and other

countries.

Solaris and Windows Conventions

This manual depicts examples (command line syntax, configuration files, and screen shots) in
Solaris format. Windows-specific commands, procedures, or screen shots are shown when
required. The following table lists general operating system conventions used with either the
Solaris or Windows operating system.

(1)

(2)

Solaris Windows

Environment $PPROHOME %PPROHOME%

Paths $PPROHOME/bin %PPROHOME%\bin

Command <command> & start /b <command>

Avaya Business Communications Manager—IVR Upgrade Guide September 2010 11

Preface

Two-Button (Windows) vs. Three-Button (Solaris) Mouse

Trademark Conventions

The following trademark information is presented here and applies throughout for third party
products discussed within this manual. Trademarking information is not repeated hereafter.

Solaris® and Motif® are registered trademarks of The Open Group in the U.S. and other
countries.

Solaris, SunOS, OpenWindows, SPARC, and UltraSPARC are trademarks or registered
trademarks of Sun Microsystems, Inc. in the United States and other countries.

Microsoft, MSSQL, Windows, Internet Explorer, and the Flying Windows logo are either
trademarks or registered trademarks of Microsoft Corporation.

Oracle® is a registered trademark of Oracle Corporation.

Sybase™ and SYBASE™ are trademarks of Sybase, Inc. or its subsidiaries.

Informix® and INFORMIX® are registered trademarks of Informix Corporation or its affiliates.

12 Avaya Business Communications Manager—IVR Upgrade Guide September 2010

Chapter 2: New in this release

The following sections detail what’s new in Avaya Business Communications Manager—IVR Upgrade
Guide for release 4.0.

Navigation

• Features on page 13

• Other changes on page 13

Features

There are no feature updates in this release.

Navigation

Revision history on page 13

Revision history

May 2007

Standard 01.01. Updates to Advanced Command window graphics.

July 2006

Standard 1.0. Avaya BCM-IVR 2.1 Upgrade Guide is issued for Release 2.1.

Other changes

There are no updates for this release.

Avaya Business Communications Manager—IVR Upgrade Guide September 2010 13

New in this release

14 Avaya Business Communications Manager—IVR Upgrade Guide September 2010

Chapter 3: Avaya BCM - IVR 2.1 Upgrade

Overview

This chapter covers:

1. The Avaya BCM-IVR 2.1 Upgrade

2. New or updated features of Avaya BCM-IVR 2.1

3. Pre-requisites for the BMC-IVR 2.1 upgrade

4. Transition issues

5. Documentation issues

The Avaya BCM-IVR 2.1 Upgrade

Avaya Business Communications Manager (Avaya BCM) 4.0 is a fully integrated
communication system for small businesses, government networks, retail networks, and
enterprise branch offices.

The Avaya BCM 4.0 offers interactive voice response capabilities through Interactive Voice
Response 2.1 (IVR 2.1). IVR 2.1 is a suite of products that allows businesses to create
applications callers can use to access information by responding to a series of prompts through
their touchtone phones.

The IVR applications are developed for specific customer needs and in many cases are
integrated with databases to enable real-time queries and updates. Some examples of IVR
applications are:

Example

• A pharmacy's application that lets customers access their accounts, receive real-time
status on their prescription refills, and request prescription refills.

• A bus station's IVR application that lets customers book seats on a trip or review
projected departure times.

• A bookstore's application that lets customers hear store hours, purchase books, and
check the delivery of an existing order.

The collection of hardware and software that creates and administers IVR applications on
Avaya BCMs is collectively referred to as the Avaya BCM-IVR 2.1 system.

Avaya Business Communications Manager—IVR Upgrade Guide September 2010 15

Avaya BCM - IVR 2.1 Upgrade Overview

New or Updated Features of Avaya BCM-IVR 2.1

In previous Avaya BCM-IVR systems (such as the Avaya BCM-IVR 1.X system), both the
Avaya BCM 3.X and the IVR 1.X operated on an Embedded Windows NT platform. The IVR

1.X development and administration tools (PeriProducer 2.X, PeriStudio 1.X, PeriReporter,
and PeriView) ran on a Windows NT/2000 platform.

The Avaya BCM-IVR 2.1 system requires both the Carrier Grade Linux (NCGL) platform and
the Windows 2000 platform. The Avaya BCM 4.0 operates on the NCGL platform. The Avaya
BCM 4.0 runs IVR applications developed and administered with the latest releases of IVR
development and administration tools: PeriProducer 3.00, PeriStudio 2.20, PeriView 2.1, and
PeriReporter 1.21. These IVR development and administration tools run on the Windows 2000
platform.

In the Avaya BCM-IVR 2.1 system, Avaya BCMs are managed with Business Element
Manager, not Unified Manager (for more information about Business Element Manager, see
Avaya BCM 4.0 Networking Configuration Guide).

In the Avaya BCM-IVR 2.1 system, PeriView and PeriView Consolidator reside on a Windows
2000 workstation, and Avaya BCM 4.0 resides on an NCGL workstation. The Avaya BCMs
IVR capabilities are managed from any user PC by pointing the user PC web browser to the
PeriView/PeriView Consolidator workstation. A third workstation with Fedora Core 3 is required
if IVR applications use C/C++ external call functions.

As such, the configuration of the new Avaya BCM-IVR 2.1 system differs from that of the Avaya
BCM-IVR 1.X system.

Avaya BCM-IVR 1.X Configuration

The following figure shows a graphical representation of a typical Avaya BCM-IVR 1.X
configuration.

16 Avaya Business Communications Manager—IVR Upgrade Guide September 2010

Avaya BCM-IVR 2.1 Configuration

Avaya BCM-IVR 2.1 Configuration

The following figure shows a typical Avaya BCM-IVR 2.1 system configuration.

Avaya Business Communications Manager—IVR Upgrade Guide September 2010 17

Avaya BCM - IVR 2.1 Upgrade Overview

18 Avaya Business Communications Manager—IVR Upgrade Guide September 2010

Prerequisites for the Avaya BCM-IVR 2.1 Upgrade

Prerequisites for the Avaya BCM-IVR 2.1 Upgrade

Application Developer

Application Developers create applications that run on the Avaya BCM-IVR system. Application
Developers must upgrade their developer workstation and install Fedora Core 3 to upgrade
any external C/C++ Call Functions in existing applications.

Workstation on page 81Chapters 4 and 5 are intended for Application Developers.

An Application Developer must obtain the following CDs to upgrade the Avaya BCM-IVR
system:

• MPS 2.1 Software, Documentation and Update CD—MPS 2.1 Patch Bundle 9,
PeriProducer 3.00, PeriStudio 2.20, PeriView 2.1 and PeriReporter 1.21 and supporting
documentation

Developer Upgrade on Windows

• Avaya BCM-IVR Toolkit CD—contains Avaya BCM Toolkit for PeriProducer 3.00, NCGL
Development Environment, userdb.xml.BCM, Avaya BCM-IVR Integration Supplement,
PeriProducer for the Avaya BCM Guide, Avaya BCM-IVR 2.1 Upgrade Guide,
ReadMe_1st.

An Application Developer must have a Windows 2000 operating system.

If the IVR applications use C/C++ call functions, an Application Developer must also have a
PC with Fedora installed. See

Developer Upgrade on Fedora Workstation on page 87 for more information.

System Administrator

System Administrators monitor and maintain the Avaya BCM-IVR system. System
Administrators must uninstall existing PERI packages, install BMC/IVR 2.1 PERI packages,
and install PeriView Consolidator. System Administrators are also responsible for managing
the Avaya BCMs using Business Element Manager. See

Workstation on page 41 and Administrator on the Avaya BCM 4.0 Platform on page 73 for

more information.

Developer Upgrade on Windows Workstation on page 81 and

Administrator on the Windows

Avaya Business Communications Manager—IVR Upgrade Guide September 2010 19

Avaya BCM - IVR 2.1 Upgrade Overview

A System Administrator must obtain the following CDs in order to upgrade the Avaya BCM­IVR system:

• MPS 2.1 Software, Documentation and Update CD—MPS 2.1 Patch Bundle 9,
PeriProducer 3.00, PeriStudio 2.20, PeriView 2.1 and PeriReporter 1.21 and supporting
documentation

• Avaya BCM-IVR Toolkit CD—contains Avaya BCM Toolkit for PeriProducer 3.00, NCGL
Development Environment, userdb.xml.BCM, Avaya BCM-IVR Integration Supplement,
PeriProducer for the Avaya BCM Guide, Avaya BCM-IVR 2.1 Upgrade Guide,
ReadMe_1st.

A System Administrator must have a Windows 2000 operating system.

Note:

Before proceeding with this upgrade, the System Administrator must obtain ported IVR
applications from the Application Developer. See Porting PeriProducer 2.30 Applications to

PeriProducer 3.00 on page 81.

Transition Issues

Transition Issues for the Application Developer

In upgrading from Avaya BCM-IVR 1.X to Avaya BCM-IVR 2.1, Application Developers may
encounter transition issues due to new or obsolete PeriProducer features.

Database Access Modes

Avaya BCM-IVR 2.1 supports VTCPD and Host database access.

BMC/IVR 2.1 no longer supports native mode or Open Database Connectivity access (ODBC).
Existing applications configured for native mode or ODBC access must be reconfigured.

For more information about configuring your Avaya BCM-IVR 2.1 system for database access.
See

Database Access Configuration on page 91.

20 Avaya Business Communications Manager—IVR Upgrade Guide September 2010

New PeriProducer 3.00 Blocks

PeriProducer 3.00 introduces several new toolkit blocks; however, some are not supported in
the Avaya BCM environment. The following table lists the new blocks and whether they are
supported in the Avaya BCM Environment.

Table 2: New PeriProducer 3.00 Blocks

Block Function

Abort Abort input/output

Bridge Not supported

Call Control Send data to telephony protocol layer/perform a hookflash

(moved from Originate block in PeriProducer 2.30)

Call Conferencing Not supported

Call Progress Detection Manage call progress detection functions

New PeriProducer 3.00 Blocks

Edit Sequence Manage touch tone input editing and user edit sequences

Line Operations Perform phone line operations (such as offer call, accept call,

get line/application resource from pool)

Media Operations Not supported

Select Input Not currently implemented

See the PeriProducer 3.00 User Guide for full descriptions of the blocks.

Blocking/Non-blocking Execution

Many PeriProducer blocks provide the option of choosing blocking (execution waits at that
block until it receives success/failure message) or non-blocking (execution continues to next
block without waiting for message) execution. A Wait checkbox enables/disables blocking
execution for the applicable blocks. See Blocking/Non-blocking Operation in the PeriProducer

3.00 User Guide for details.

Call Progress Detection

Using Call Progress Detection (CPD) is updated in PeriProducer 3.00. CPD is controlled by
dynamically enabling and disabling specific tone/event detection in the Call Progress Detection
block. All CPD events return to the application as the cpd condition with the specific event

Avaya Business Communications Manager—IVR Upgrade Guide September 2010 21

Avaya BCM - IVR 2.1 Upgrade Overview

(Busy, Reorder, and so on) in the condition data. See the PeriProducer 3.00 User Guide for
details.

PeriProducer 3.00 Block Changes

Many PeriProducer 3.00 blocks have amended or improved function.

Connection IDs (Caller I/O blocks)

Phone line and resource numbers are replaced with Connection IDs (CIDs). Connection IDs
indicate the component name and the line number of the connection. For example, the CID
mps24.1 indicates the connection is from line one on component mps24. The default
Connection ID for the current phone line is available in the System folder's DefaultCID data
card. The CID for an operation is supplied by the system (for example, when a resource is
allocated).

Accessory Toolkit Blocks

The Table Search, Table Sort, Date Calculations, and Send email blocks are moved from the
main toolkit to the accessory toolkit.

Answer Block

Continue on Ring Detect Removed

The Continue on Ring Detect option is removed.

Get Phone Number Options Removed

The Get Dialed Phone Number and Get Caller's Phone Number options are supported only
with certain protocols. See the Avaya BCM 4.0 Networking Configuration Guide for more
details.

22 Avaya Business Communications Manager—IVR Upgrade Guide September 2010

Disconnect Block

Abandoned Call Counter Removed

The MPS does not automatically track system abandoned calls. The Mark as abandoned
option is removed. To track abandoned calls, create application statistics and use MPS
Reporter to display the reports

System Block

Diagnostic Functions Removed

The diagnostics function is removed.

Condition Data

Disconnect Block

The Get Condition Data function is added. This function replaces using the condition-data call
function. Get Condition Data requires a folder with the same structure, data names, and data
types expected with the condition.

Send Host Block

Virtual Terminal (VT) Allocation

VT allocation functions are available from the Send Host block. These functions replace the
VT allocation Environment block options.

Avaya Business Communications Manager—IVR Upgrade Guide September 2010 23

Avaya BCM - IVR 2.1 Upgrade Overview

Setting Host Environment Parameters

Host environment parameters are sent from the Send Host block. This function replaces the
Environment block "host" option.

Receive Host Block

Asynchronous Operation

The Asynchronous checkbox is replaced by the Wait checkbox. Receive Host operates
asynchronously when the Wait checkbox is unchecked.

Send Fax Block

Fax Composition Removed

The Fax Composition feature is not supported. All controls and options used to create and
store composed faxes are removed.

Send Fax from TIFF File

PeriProducer 3.00 supports sending faxes directly from TIFF format files. TIFF faxes no longer
need to be imported into a MultiMedia File and accessed by a media storage token.

Fax Mode Removed

PeriProducer 3.00 supports only Group 3 faxes.

24 Avaya Business Communications Manager—IVR Upgrade Guide September 2010

Receive Fax Block

Receive Fax Direct into TIFF File

Applications can save an incoming fax directly to a TIFF-format file. In previous versions of
PeriProducer, faxes were stored in MultiMedia Files and had to be exported to individual TIFFs.

Local Station ID

The user can specify the Local Station ID (which typically represents the phone number of the
station receiving the fax) in the block. The Local Station ID is typically displayed on the
transmitting fax machine.

Fax Mode Removed

PeriProducer 3.00 supports only Group 3 faxes.

Receive Fax Block

Originate Block

Moved Functions

All bridging functions are moved to the new 3.00 Bridge Block. Hookflash is moved to the Call
Control Block. The End Transfer function is deleted and the user can use the Disconnect block
instead.

Record Block

Asynchronous Recording

Asynchronous recording provides an unlimited duration message. Asynchronous recording is
explicitly started and stopped by Begin and End functions of the Record block.

Moved Functions

Element deletion functions are moved to the Media Operations block.

Resource Block

Asynchronous Execution Changes

There is no longer an Async checkbox in the Resource block. To perform the resource receive
asynchronously, clear the Wait box.

Avaya Business Communications Manager—IVR Upgrade Guide September 2010 25

Avaya BCM - IVR 2.1 Upgrade Overview

Discontinued Features and Functions

Fax Composition

Fax composition is not supported in PeriProducer 3.00. Faxes to be sent must be created by
external applications or received (and stored for later use) by the Avaya BCM.

Hardware Properties Window

The Hardware Properties Window is removed.

Unsupported Resources

PeriProducer 3.00 no longer supports the following resources:

• mps

• abb

• asdi

• ast

• iwr

• ppd

• modem

• mts

• iscp

• ctx

• lcr

26 Avaya Business Communications Manager—IVR Upgrade Guide September 2010

Obsolete Functions

The Media Operations block in PeriProducer has rendered obsolete the file-to-message,
message-to-item and message-to-file functions.

Other PeriProducer Changes

Enhanced Condition Data

Condition Data is now returned as a data structure consisting of different field/value pairs. To
access the expanded condition data, use the System block's "Get Condition Data" function
and specify the appropriate response folder (templates provided in %PPROPATH%\sample
\folders). To access all of the condition data, the folder must have data cards defined as the
same name and type as the associated condition data field. The data for one field only can be
obtained by specifying a datacard whose name matches the desired field.

Obsolete Functions

Note:

The condition data for many conditions have a Status field. The Status field value is
automatically copied into the System folder's ConditionData card.

Environment Options

Many PeriProducer 2.30 Environment options are rendered obsolete or replaced by new
environment options, block built-in functions or both, in PeriProducer 3.00. The following table
lists the 2.30 Environment options and the analogous 3.00 option (if any). Comments are
provided where appropriate.

Table 3: Environment Options Conversions

2.30 Environment Option 3.00 Equivalent

Phone Environment

answer Unsupported as environment option. Use the Answer

block (Answer function) to answer a call.

Avaya Business Communications Manager—IVR Upgrade Guide September 2010 27

Avaya BCM - IVR 2.1 Upgrade Overview

2.30 Environment Option 3.00 Equivalent

first DtmfFirst (Application and System Environment

inter DtmfInter (Application and System Environment

keepterm Unsupported as environment option. Use the "Retain"

termchar Unsupported as environment option. Use the Edit

total LineTotalCall (Application and System Environment

typeahead Unsupported

Phone Line Task Environment

backsp Unsupported as environment option. Use the Edit

options)

options)

option (for the termination character) in Edit Sequence
block.

Sequence block to enable/set a termination character.

options)

Sequence block to enable/set a backspace edit
sequence.

delete Unsupported

eXtext Unsupported. Use the Edit Sequence block to enable/

set user edit sequences.

Phone Resource Server Environment

prs Unsupported

tstop Unsupported as environment option

Message Recording Environment

intersil RecInterSil (Application and System Environment

options)

Call Progress Detection Environment

cpansup Unsupported

pickup Unsupported

Speech Management Environment

clear Supported for legacy applications only. Use the Abort

block with the "Caller I/O Only" option enabled.

vioabort Unsupported as environment option. Use the Abort

block.

Host Environment

er er

28 Avaya Business Communications Manager—IVR Upgrade Guide September 2010

Environment Options

2.30 Environment Option 3.00 Equivalent

freevt Supported for legacy applications only. Use the Send

Host block "Free VT" (in Control > Function > Controls)
option.

getvt Supported for legacy applications only. Use the Send

Host block "Get VT" (in Control > Function > Controls)
option.

headermode headermode

hostctl hostctl

intime intime

parameter Supported for legacy applications only. Use the Send

Host block "parameter" (in Function > Controls) option.

refer refer

rfno rfno

session session

setaid setaid

unlocks unlocks

usepool usepool

Advanced Phone Line Management

phone Unsupported as environment option

Optional Exception Conditions

rngback Unsupported as environment option

uedit3 Unsupported as environment option (in the context of

taking a digital system out of wait for an outdial
complete message)

Generic Environment Options

Phone Line Manager Options Superseded by "Application and System Options"

Vengine Options Vengine Options

VENGINE Environment

alarmdbtask alarmdbtask

apprestart apprestart

centurymark centurymark

debug debug

deltimedcall deltimedcall

Avaya Business Communications Manager—IVR Upgrade Guide September 2010 29

Avaya BCM - IVR 2.1 Upgrade Overview

2.30 Environment Option 3.00 Equivalent

hnowait Unsupported (a corresponding VENGINE runtime

intermsg intermsg

maxmessage Unsupported

mode mode

notice notice

numset numset

rscertime rscertime

rscintime rscintime

setvpsline setvpsline

softterm softterm

speak speak

timedcall timedcall

option is available)

unnotice unnotice

vmstimedcall vmstimedcall

vpsrcvtime vpsrcvtime

webtimeout webtimeout

Conditions

When a PeriProducer 2.30 application is opened in 3.00, PeriProducer attempts to
automatically convert handle conditions to their counterparts in 3.00. Condition conversions
shown with a preceding dollar sign ("$") are displayed in the application as the 2.30 condition
but are automatically converted to the appropriate 3.00 condition at runtime.

The following table lists the 2.30 condition, the corresponding 3.00 condition (if any), and, if
applicable, how PeriProducer 3.00 converts the condition when a 2.30 application is ported to

3.00.

Table 4: Conditions Conversion

2.30 Condition 3.00 Condition Conversion

abend abend abend

addfail importfail w/Status

"ErrInUse" in condition data

30 Avaya Business Communications Manager—IVR Upgrade Guide September 2010

$addfail