Avaya BCM-IVR 2.1 Upgrade Guide
BCM-IVR 2.1 Upgrade Guide
Publication#:
Document Release:
Release Date:
N0064485
1.0
July 13, 2006
Important Notice
Nortel reserves the right to make changes in the contents of this publication including
functions and specifications identified herein without notice.
The material contained in this document is intended for Nortel personnel and licensed
customers with a non-disclosure agreement or standard contract.
In the absence of a written agreement to the contrary, Nortel assumes no liability for
applications assistance, customer's product/application/concepts, or infringements of
patents or copyrights of third parties arising from the use of systems and architectures
described herein. Nor does Nortel warrant or represent that any license, either
expressed or implied, is granted under any patent right, copyright, or other
combination of technology, architecture, or software as might be or is already in use.
This document should not be reproduced, disseminated, or otherwise disclosed
without prior written consent from a Nortel officer.
This document has been copyrighted by Nortel and may not be duplicated.
Copyright © 2006 Nortel Networks. All Rights Reserved
Revision History
July 2006 Standard 1.0.
Revision History
# N0064485 Ver: 1.0 Nortel Confidential Page 3
BCM-IVR 2.1 Upgrade Guide
Page 4 Nortel Confidential # N0064485 Ver: 1.0
Table of Contents
Revision History . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3
Preface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
Scope . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
Intended Audience . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
How to Get Help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
Finding the latest updates on the Nortel Web site . . . . . . . . . 8
Getting Help from the Nortel Web site. . . . . . . . . . . . . . . . . . 8
Getting Help over the phone from a Nortel Solutions Center 9
Getting Help from a specialist by using an Express Routing
Code . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
Getting Help through a Nortel distributor or reseller . . . . . . . 9
How to Use This Manual . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
Organization of This Manual . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
Conventions Used in This Manual . . . . . . . . . . . . . . . . . . . . . . . . 12
Solaris and Windows Conventions . . . . . . . . . . . . . . . . . . . . . . . 13
Two-Button (Windows) vs. Three-Button (Solaris) Mouse . 14
Trademark Conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
BCM - IVR 2.1 Upgrade Overview . . . . . . . . . . . . . . . . . . . 15
The BCM-IVR 2.1 Upgrade . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
New or Updated Features of BCM-IVR 2.1 . . . . . . . . . . . . . . . . 16
Pre-Requisites for the BCM-IVR 2.1 Upgrade . . . . . . . . . . . . . . 19
Application Developer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
System Administrator . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
Transition Issues . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20
Transition Issues for the Application Developer . . . . . . . . . 20
PeriProducer 3.00 Block Changes . . . . . . . . . . . . . . . . . . . . 21
Discontinued Features and Functions . . . . . . . . . . . . . . . . . . 24
Other PeriProducer Changes. . . . . . . . . . . . . . . . . . . . . . . . . 25
Transition Issues for the System Administrator . . . . . . . . . . 37
Documentation Issues . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38
Administrator on the Windows Workstation . . . . . . . . . . . 39
Windows Workstation Operating System Upgrade . . . . . . . . . . . 40
BCM-IVR 1.X Uninstall Procedures . . . . . . . . . . . . . . . . . . . . . . 40
Uninstall Procedures with MPS 2.1 Software and Document CD
40
BCM-IVR 2.1 Installation Procedures . . . . . . . . . . . . . . . . . . . . . 43
Installing PeriProducer 3.00 and PeriStudio 2.20. . . . . . . . . 43
BCM-IVR 2.1 Toolkit Installation . . . . . . . . . . . . . . . . . . . . . . . . 48
License Service Installation . . . . . . . . . . . . . . . . . . . . . . . . . 50
PeriView 2.1 and PeriView 2.1 Consolidator Installation . . . . . . 53
Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53
# N0064485 Ver: 1.0 Nortel Confidential Page 5
BCM-IVR 2.1 Upgrade Guide
Installing BCM-IVR 2.1 PeriView Consolidator . . . . . . . . . 54
Launching Applications in PeriView . . . . . . . . . . . . . . . . . . . . . 62
Loading Application .vex files . . . . . . . . . . . . . . . . . . . . . . . 62
Loading User Defined Call Function Files . . . . . . . . . . . . . . 65
Assigning and Starting Applications . . . . . . . . . . . . . . . . . . 66
Administrator on the BCM 4.0 Platform . . . . . . . . . . . . . . . 73
Numbering components using Element Manager . . . . . . . . . . . . 74
Enabling Host Communications with Element Manager . . . . . . 75
Application Resources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80
Developer Upgrade on Windows Workstation . . . . . . . . . . 81
Porting PeriProducer 2.30 Applications to PeriProducer 3.00 . . 82
Application Porting Considerations . . . . . . . . . . . . . . . . . . . 82
Converting Standard PeriProducer 2.30 Applications to
PeriProducer 3.00 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82
Porting Events . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82
Conversion Logs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83
Known Conversion Issues . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84
Set Resource Label in 2.30 . . . . . . . . . . . . . . . . . . . . . . . . . . 84
Unsupported 2.30 Resources . . . . . . . . . . . . . . . . . . . . . . . . 84
Resource Block Conversions . . . . . . . . . . . . . . . . . . . . . . . . 84
Flushing the Speak Prompt Buffer . . . . . . . . . . . . . . . . . . . . 84
System Transfer Connection ID Datacard . . . . . . . . . . . . . . 84
Developer Upgrade on Fedora Workstation . . . . . . . . . . . . 87
Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88
Installing Fedora . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88
Installing Nortel IVR Plugin Development Environment . . . . . . 89
Building C/C++ Call Functions Libraries . . . . . . . . . . . . . . . . . . 89
makecall_tux Tool . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89
Database Access Configuration . . . . . . . . . . . . . . . . . . . . . . 91
Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92
VMST 3 on the BCM Node . . . . . . . . . . . . . . . . . . . . . . . . . 92
Install Patches on the Windows Node . . . . . . . . . . . . . . . . . 93
Configuring periq on the Windows Node . . . . . . . . . . . . . . . . 93
Configuring sqlclnt on Windows Node . . . . . . . . . . . . . . . . 94
Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97
Page 6 Nortel Confidential # N0064485 Ver: 1.0
Preface
BCM-IVR 2.1 Upgrade Guide
Scope
Business Communications Manager (BCM) with Interactive Voice Response (IVR)
capabilities is a communications platform that delivers multimedia voice processing,
business telephony applications, and data networking services.
The BCM-IVR 2.1 Upgrade manual explains how to upgrade a BCM-IVR 1.X system
to a BCM-IVR 2.1 system. It further explains how to port existing applications to run
on the upgraded 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 BCM-IVR System
Administrators. This manual assumes that the reader is familiar with:
• BCM application development;
• site-specific operating procedures relating to the BCM;
• specific application functions performed by the BCM; and
• other equipment to which the BCM may be connected.
How to Get Help
Basic knowledge of your operating system software is also assumed.
This section explains how to get help for Nortel products and services.
Finding the latest updates on the Nortel Web site
The content of this documentation was current at the time the product was released.
To check for updates to the latest documentation for the MPS 500 and 1000, click one
of the following links:
MPS 500 Takes you directly to the Nortel page for MPS 500 documentation at
www130.nortelnetworks.com/cgi-bin/eserv/cs/main.jsp?cscat=DOCUMENTATION&resetFilter=1&tranProduct=12605
MPS 1000 Takes you directly to the Nortel page for MPS 1000 documentation at
www130.nortelnetworks.com/cgi-bin/eserv/cs/main.jsp?cscat=DOCUMENTATION&resetFilter=1&tranProduct=11721
Getting Help from the Nortel Web site
The best way to get technical support for Nortel products is from the Nortel Technical
Support web site:
www.nortel.com/support
This site provides quick access to software, documentation, bulletins, and tools to
address issues with Nortel products:
Page 8 Nortel Confidential # N0064485 Ver: 1.0
Preface
• download software, documentation, and product bulletins
• search the Technical Support web site and the Nortel Knowledge Base for
answers to technical issues
• sign up for automatic notification of new software and documentation for
Nortel equipment
• open and manage technical support cases
Getting Help over the phone from a Nortel Solutions Center
If you do not find the information you require on the Nortel Technical Support web
site, and have a Nortel support contract, you can also get help over the phone from a
Nortel Solutions Center.
In North America, call 1-800-4NORTEL (1-800-466-7835).
Outside North America, go to the following web site to obtain the phone number for
your region:
www.nortel.com/callus
Getting Help from a specialist by using an Express Routing Code
To access some Nortel Technical Solutions Centers, you can use an Express Routing
Code (ERC) to quickly route your call to a specialist in your Nortel product or service.
To locate the ERC for your product or service, go to:
www.nortel.com/erc
Getting Help through a Nortel distributor or reseller
If you purchased a service contract for your Nortel product from a distributor or
authorized reseller, contact the technical support staff for that distributor or reseller.
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 MPS Series. Refer to the Glossary of
Nortel’s Media Processing Server Series Terminology for definitions of 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.
# N0064485 Ver: 1.0 Nortel Confidential Page 9
BCM-IVR 2.1 Upgrade Guide
Familiarize yourself with various specialized textual references within the manual, see
Conventions Used in This Manual on page 12.
Periphonics is now part of Nortel. 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).
Page 10 Nortel Confidential # N0064485 Ver: 1.0
Organization of This Manual
This manual is organized according to the needs and requirements of two distinct
BCM-IVR users: System Administrators and Application Developers.
Chapter 1 — Introduction to the BCM - IVR Upgrade
Overviews the upgraded Business Communication Manager (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 BCM-IVR PeriView
Consolidator workstation.
Chapter 3 — Administrator Upgrade on BCM 4.0 Platform
Discusses how to manage BCMs using Element Manager. Explains how to add BCMs
to the Element Manager administration list.
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.
Preface
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.
# N0064485 Ver: 1.0 Nortel Confidential Page 11
BCM-IVR 2.1 Upgrade Guide
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.
Conventions Used in This Manual (Sheet 1 of 2)
Notation Description
Normal text
important term
system
command
command,
condition
and alarm
file name /
directory
on-screen field
<KEY NAME>
Book Reference
Normal text font is used for most of the document.
The Italics font introduces new terms, highlights meaningful words
or phrases, or distinguishes specific terms from nearby text.
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 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
Commands, Conditions, and Alarms.
about
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.)
This font indicates field labels, on-screen menu buttons, and action
buttons.
A term that appears within angled brackets denotes a terminal
keyboard key, a telephone keypad button, or a system mouse
button.
This font indicates the names of other publications referenced
within the document.
cross-reference
!
A cross-reference appears on the screen in blue. Click the crossreference to access the referenced location. A cross-reference that
refers to a section name accesses the first page of that section.
The Note icon identifies notes, 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.
Page 12 Nortel Confidential # N0064485 Ver: 1.0
Conventions Used in This Manual (Sheet 2 of 2)
Notation Description
Preface
(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.
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.
(2)
(1)
Solaris Windows
Environment $PPROHOME %PPROHOME%
Paths $PPROHOME/bin %PPROHOME%\bin
Command <command> & start /b <command>
# N0064485 Ver: 1.0 Nortel Confidential Page 13
BCM-IVR 2.1 Upgrade Guide
Two-Button (Windows) vs. Three-Button (Solaris) Mouse
<SELECT> Left button
<ADJUST> Left and Right
<MENU> Right button
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
other countries.
Solaris, SunOS, OpenWindows, SPARC, and UltraSPARC are trademarks or
registered trademarks of Sun Microsystems, Inc. in the United States and other
countries.
®
<SELECT> Left button
<ADJUST> Middle button
together
<MENU> Right button
and Motif® are registered trademarks of The Open Group in the U.S. and
Microsoft, MSSQL, Windows, Internet Explorer, and the Flying Windows logo are
either trademarks or registered trademarks of Microsoft Corporation.
®
Oracle
Sybase
Informix
is a registered trademark of Oracle Corporation.
™
and SYBASE™ are trademarks of Sybase, Inc. or its subsidiaries.
®
and INFORMIX® are registered trademarks of Informix Corporation or its
affiliates.
Page 14 Nortel Confidential # N0064485 Ver: 1.0
BCM - IVR 2.1
Upgrade Overview
This chapter covers:
1. The BCM-IVR 2.1 Upgrade
2. New or updated features of
BCM-IVR 2.1
3. Pre-requisites for the BMCIVR 2.1 upgrade
4. Transition issues
5. Documentation issues
BCM-IVR 2.1 Upgrade Guide
The BCM-IVR 2.1 Upgrade
Business Communication Manager 4.0 (BCM) is a fully integrated communication
system for small businesses, government networks, retail networks, and enterprise
branch offices.
The 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:
• 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 BCMs is collectively referred to as the BCM-IVR 2.1 system.
New or Updated Features of BCM-IVR 2.1
In previous BCM-IVR systems (such as the BCM-IVR 1.X system), both the 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 BCM-IVR 2.1 system requires both the Nortel Carrier Grade Linux (NCGL)
platform and the Windows 2000 platform. The BCM 4.0 operates on the NCGL
platform. The 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 BCM-IVR 2.1 system, BCMs are managed with Element Manager, not Unified
Manager (for more information about Element Manager, see BCM 4.0 Networking
Configuration Guide).
In the BCM-IVR 2.1 system, PeriView and PeriView Consolidator reside on a
Windows 2000 workstation, and BCM 4.0 resides on an NCGL workstation. The
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
Page 16 Nortel Confidential # N0064485 Ver: 1.0
Fedora Core 3 is required if IVR applications use C/C++ external call functions.
As such, the configuration of the new BCM-IVR 2.1 system differs from that of the
BCM-IVR 1.X system.
BCM-IVR 1.X Configuration
The following figure shows a graphical representation of a typical BCM-IVR 1.X
configuration.
Typical BCM-IVR 1.X
System Configuration
Windows Workstation
Developer and Administrator
Workstations could be the same
machine.
BCM - IVR 2.1 Upgrade Overview
Developer Workstation
Windows NT/2K
Software Tools:
PeriProducer 2.3
PeriStudio 2.1
Administrator
Workstation
Windows NT/2K
Software Tools:
PeriView 1.0
PeriReporter
BCM 3.X
with
BCM-IVR 1.X
on Embedded Win-
dows NT
Software Tools:
Unified Manager
# N0064485 Ver: 1.0 Nortel Confidential Page 17
BCM-IVR 2.1 Upgrade Guide
BCM-IVR 2.1 Configuration
The following figure shows a typical BCM-IVR 2.1 system configuration.
Windows Workstation
The Developer and
Administrator
Workstations could be the
same machine.
Developer
Workstation
Windows 2K
Typical BCM-IVR 2.1 System
Configuration
Software Tools:
PeriProducer 3.00
PeriStudio 2.20
Administrator
Workstation
Windows 2K
Software Tools:
PeriView
Consolidator 2.1
PeriReporter
Element Manager
C/C++ Call Function
Workstation running
Fedora
BCM 4.0
with
BCM-IVR 2.1
on NCGL
The BCM-IVR 2.1 Upgrade Guide
describes the installation and
configuration of items in this box.
Page 18 Nortel Confidential # N0064485 Ver: 1.0
Pre-Requisites for the BCM-IVR 2.1 Upgrade
Application Developer
Application Developers create applications that run on the 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.
Chapters 4 and 5 are intended for Application Developers.
An Application Developer must obtain the following CDs to upgrade the 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
• BCM-IVR Toolkit CD—contains BCM Toolkit for PeriProducer 3.00, NCGL
Development Environment, userdb.xml.BCM, BCM-IVR Integration
Supplement, PeriProducer for the BCM Guide, BCM-IVR 2.1 Upgrade
Guide, ReadMe_1st.
BCM - IVR 2.1 Upgrade Overview
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 “Overview” on page 88.
System Administrator
System Administrators monitor and maintain the 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 BCMs using Element Manager. Chapters 2 and 3 are
intended for System Administrators.
A System Administrator must obtain the following CDs in order to upgrade the BCMIVR 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
• BCM-IVR Toolkit CD—contains BCM Toolkit for PeriProducer 3.00, NCGL
Development Environment, userdb.xml.BCM, BCM-IVR Integration
Supplement, PeriProducer for the BCM Guide, BCM-IVR 2.1 Upgrade
Guide, ReadMe_1st.
A System Administrator must have a Windows 2000 operating system.
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 82.
# N0064485 Ver: 1.0 Nortel Confidential Page 19
BCM-IVR 2.1 Upgrade Guide
Transition Issues
Transition Issues for the Application Developer
In upgrading from BCM-IVR 1.X to BCM-IVR 2.1, Application Developers may
encounter transition issues due to new or obsolete PeriProducer features.
Database Access Modes
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 BCM-IVR 2.1 system for database
access. See “Database Access Configuration” on page 91.
New PeriProducer 3.00 Blocks
PeriProducer 3.00 introduces several new toolkit blocks; however, some are not
supported in the BCM environment. The following table lists the new blocks and
whether they are supported in the BCM Environment.
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
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’s 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
Page 20 Nortel Confidential # N0064485 Ver: 1.0
BCM - IVR 2.1 Upgrade Overview
continues to next block without waiting for message) execution. A Wait checkbox
enables/disables blocking execution for the applicable blocks. See Blocking/Nonblocking Operation in the PeriProducer 3.00 User’s 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 (Busy, Reorder, and so on) in the condition data. See
the PeriProducer 3.00 User’s 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 BCM 4.0 Networking Configuration Guide for
more details.
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
# N0064485 Ver: 1.0 Nortel Confidential Page 21
BCM-IVR 2.1 Upgrade Guide
System Block
Diagnostic Functions Removed
The diagnostics function is removed.
Condition Data
The Get Condition Data function is added. This function replaces using the conditiondata 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.
new VT options
Setting Host Environment Parameters
Host environment parameters are sent from the Send Host block. This function
replaces the Environment block "host" option.
Page 22 Nortel Confidential # N0064485 Ver: 1.0
Receive Host Block
BCM - IVR 2.1 Upgrade Overview
parameter option
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.
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.
# N0064485 Ver: 1.0 Nortel Confidential Page 23
BCM-IVR 2.1 Upgrade Guide
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.
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.
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 BCM.
Hardware Properties Window
The Hardware Properties Window is removed.
Page 24 Nortel Confidential # N0064485 Ver: 1.0
BCM - IVR 2.1 Upgrade Overview
Unsupported Resources
PeriProducer 3.00 no longer supports the following resources:
•mps
•abb
•asdi
•ast
•iwr
•ppd
•modem
•mts
•iscp
•ctx
•lcr
Obsolete Functions
The Media Operations block in PeriProducer has rendered obsolete the file-tomessage, 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.
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.
# N0064485 Ver: 1.0 Nortel Confidential Page 25
BCM-IVR 2.1 Upgrade Guide
2.30 Environment Option 3.00 Equivalent
Phone Environment
answer Unsupported as environment option. Use the Answer block
first DtmfFirst (Application and System Environment options)
inter DtmfInter (Application and System Environment options)
keepterm Unsupported as environment option. Use the "Retain" option
termchar Unsupported as environment option. Use the Edit Sequence
total LineTotalCall (Application and System Environment options)
typeahead Unsupported
Phone Line Task Environment
Environment Options Conversions Sheet 1 of 3
(Answer function) to answer a call.
(for the termination character) in Edit Sequence block.
block to enable/set a termination character.
backsp Unsupported as environment option. Use the Edit 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
freevt Supported for legacy applications only. Use the Send Host
block "Free VT" (in Control > Function > Controls) option.
Page 26 Nortel Confidential # N0064485 Ver: 1.0
BCM - IVR 2.1 Upgrade Overview
Environment Options Conversions Sheet 2 of 3
2.30 Environment Option 3.00 Equivalent
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
Vengine Options Vengine Options
VENGINE Environment
alarmdbtask alarmdbtask
apprestart apprestart
centurymark centurymark
debug debug
deltimedcall deltimedcall
hnowait Unsupported (a corresponding VENGINE runtime option is
Superseded by "Application and System Options"
available)
intermsg intermsg
maxmessage Unsupported
mode mode
# N0064485 Ver: 1.0 Nortel Confidential Page 27
BCM-IVR 2.1 Upgrade Guide
2.30 Environment Option 3.00 Equivalent
notice notice
numset numset
rscertime rscertime
rscintime rscintime
setvpsline setvpsline
softterm softterm
speak speak
timedcall timedcall
unnotice unnotice
vmstimedcall vmstimedcall
vpsrcvtime vpsrcvtime
webtimeout webtimeout
Environment Options Conversions Sheet 3 of 3
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.
Conditions Conversion Sheet 1 of 10
2.30 Condition 3.00 Condition Conversion
abend abend abend
addfail importfail w/Status
"ErrInUse" in condition data
addsucc importcmp importcmp
altlinkdown altlinkdown altlinkdown
ansfail answerfail answerfail
$addfail
asrdet asrdet asrdet
asyncdata Unsupported
asyncfail Unsupported
Page 28 Nortel Confidential # N0064485 Ver: 1.0
BCM - IVR 2.1 Upgrade Overview
Conditions Conversion Sheet 2 of 10
2.30 Condition 3.00 Condition Conversion
autofail detinputfail detinputfail
autotim autotim autotim
avserr avserr avserr
badoperation badoperation badoperation
badparameter badparameter badparameter
calltim calltim calltim
carloss Unsupported
ccs7cc ccs7cc ccs7cc
chartim getinputfail w/Status
"ErrInter" field in condition
data
cmrhigh Unsupported
cmrlow Unsupported
comfail comfail comfail
conn answercmp answercmp
crefer Unsupported
crepeat Unsupported
crepmax Unsupported
cticond cticond cticond
ctidown ctidown ctidown
ctifail ctifail ctifail
ctiup ctiup ctiup
ctxcc Unsupported
ctxfailcc Unsupported
ctxokcc Unsupported
getinputfail
cvoice Unsupported
dcdown Unsupported
dcup Unsupported
deadlock deadlock deadlock
delcomp delcmp delcmp
delfail delfail delfail
dialtn Unsupported
disable Unsupported
# N0064485 Ver: 1.0 Nortel Confidential Page 29
BCM-IVR 2.1 Upgrade Guide
2.30 Condition 3.00 Condition Conversion
disc Dependent upon event that caused disc condition.
Conditions Conversion Sheet 3 of 10
disc (caller hangup) $disc
disccmp (system-initiated
disconnect)
discfail discfail w/Status field in
condition data
dtmfzl recordfail w/Status
"ErrZeroLengthDTMF" in
condition data
dupkey dupkey dupkey
dupvalidx dupvalidx dupvalidx
enable Unsupported
endfail discfail $endfail
endfile endfile endfile
error error error
ertimeout Dependent upon event that caused ertimeout condition
ertimeout (gen’d by
VENGINE)
hrcvmapfail w/Status
"ErrTimeout" in condition
data (failed receive map)
$disc
$discfail
recordfail
$ertimeout
$ertimeout
hrcvtxtfail w/Status
"ErrTimeout" in condition
data (failed receive text)
expired expired expired
faxdet faxdet faxdet
forcefree forcefree forcefree
forward Unsupported
fromphone fromphone fromphone
frstim getinputfail w/Status
"ErrFirst" in condition data
ftomfail Unsupported
ftomsucc Unsupported
$ertimeout
getinputfail
Page 30 Nortel Confidential # N0064485 Ver: 1.0
Loading...