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 reseller, the warranty is provided to you by said reseller and not by Avaya.
Licenses
THE SOFTWARE LICENSE TERMS AVAILABLE ON THE AVAYA WEBSITE, HTTP://SUPPORT.AVAYA.COM/LICENSEINFO/
ARE 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 T AKE 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 the Documentation(s) and Pr oduct( s) p rovided by Avaya. All content
in this documentation(s) and the product(s) pr ov id ed by Avaya including the selection, arrangement and design of the content is owned
either by Avaya or its licensors and is protected b y copyright and other intellectual property laws including the 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: http://support.avaya.com/Copyright.
Trademarks
The trademarks, logos and service marks ("Marks") displayed in this site, the documentation(s) and product(s) pr ovided 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 A vaya 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 non-Avaya
trademarks are the property of their respective owners.
Downloading documents
For the most current versions of documentation, see the Avaya Support. Web site: http://www.avaya.c om/support
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: http://
System Transfer Connection ID Datacard . . . . . . . . . . . . . . 48
Automatic Detection of Speech or DTMF Input (AUTOID) 48
# P0605081 Ver: 2.3Page 5
PeriProducer 3.00 Release Notes
This page has been intentionally left blank.
Page 6# P0605081 Ver: 2.3
Preface
PeriProducer 3.00 Release Notes
Scope
The manual PeriProducer 3.00 Release Notes provides a summary of new features
and enhancements to PeriProducer 2.30.
This manual does not describe PeriProducer 3.00 features and enhancements in detail.
For a more complete description, see the PeriProducer User’s Guide.
Intended Audience
This manual is intended for application developers of Avaya Media Processing Server
(MPS) using the PeriProducer graphical application development tool. A basic
understanding of the PeriProducer product as well as attendance in a PeriProducer
training course is highly recommended.
How to Use This Manual
This manual uses many standard terms relating to computer system, software
application functions, and the Internet. However, it contains some terminology that
can only be explained in the context of the MPS system. Refer to the Glossary of Avaya Media Processing Server Terminology for definitions of MPS specific terms.
Initially, you should read this manual at least once, from start to finish. Later, 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. <L
with your cursor over the cross-reference link. Click on any point in a Table of
Contents entry to move to that topic. Click on the page number of any Index entry to
access that topic page.
To familiarize yourself with various specialized textual references within the manual,
see Conventions Used in This Manual on page 9.
Periphonics is now part of Avaya. The name Periphonics, and variations thereof,
appear in this manual only where it is referred to in a product. (For examples, a
PeriProducer application, the PERImps package, the perirev command, etc.)
EFT> click once with your mouse while positioned
Page 8# P0605081 Ver: 2.3
Organization of This Manual
The chapters are as follows:
Chapter 1 — PeriProducer 3.00 New Features and Enhancements
Discusses features and enhancements new to PeriProducer 3.00 and related materials.
Chapter 2 — Porting 2.30 Applications to 3.00
Outlines procedures and configurations for porting applications made with
PeriProducer 2.30 and bringing them into PeriProducer 3.00.
Procedures for installing PeriProducer (as part of the complete MPS software
package) are included in the Installing MPS Software on the Solaris Platform and
Installing MPS Software on the Windows Platform.
Conventions Used in This Manual
Preface
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
NotationDescription
Normal text
important term
system
command
command,
condition
and alarm
file name /
directory
Normal text font is used for most of the document.
The Italics font is used to introduce new terms, to highlight
meaningful words or phrases, or to distinguish specific terms from
nearby text.
This font indicates a system command and/or its arguments. Such
keywords are to be entered exactly as shown (i.e., users are not to
fill in their own values).
Command, Condition and Alarm references appear on the screen
in magenta text and reference the Command Reference Manual,
the PeriProducer User’s Guide, or the Alarm Reference Manual,
respectively. Refer to these documents for detailed information
Commands, Conditions, and Alarms.
about
This font is used for highlighting the names of disk directories, files,
and extensions for file names. It is also used to show displays on
text-based screens (e.g., to show the contents of a file.)
on-screen field
<KEY NAME>
This font is used for 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.
# P0605081 Ver: 2.3Page 9
PeriProducer 3.00 Release Notes
NotationDescription
Conventions Used in This Manual Sheet 2 of 2
Book Reference
cross reference
!
This font indicates the names of other publications referenced
within the document.
A cross reference is shown on the screen in blue. Click on the
cross reference 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 improperly
followed.
The flying Window icon identifies procedures or events that apply
to the Windows 2000 operating system only.
The Solaris icon identifies procedures or events that apply to the
Solaris operating system only.
2
1
1. Windows 2000 and the flying Window logo are either trademarks or registered
trademarks of the Microsoft Corporation.
2. Solaris® is a registered trademark of The Open Group in the U.S. and other
countries.
Solaris and Windows 2000 Conventions
This manual depicts examples (command line syntax, configuration files, and screen
shots) in Solaris format. In certain instances Windows 2000 specific commands,
procedures, or screen shots are shown where required. The following table lists
examples of general operating system conventions to keep in mind when using this
manual with either the Solaris or Windows operating system.
SolarisWindows 2000
Environment$MPSHOME%MPSHOME%
Paths$MPSHOME\common\etc%MPSHOME%\common\etc
Command<command> &start /b <command>
Page 10# P0605081 Ver: 2.3
Preface
Two-Button (Windows 2000) 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, Windows 2000, 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.
# P0605081 Ver: 2.3Page 11
PeriProducer 3.00 Release Notes
This page has been intentionally left blank.
Page 12# P0605081 Ver: 2.3
PeriProducer 3.00
New Features and
Enhancements
This chapter covers:
1. New Features and Enhancements
2. PeriProducer Block Changes
3. Discontinued Features/Functions
4. Other PeriProducer Changes
PeriProducer 3.00 Release Notes
New Features and Enhancements
New Blocks
The following blocks are new to PeriProducer 3.00:
BlockFunction
AbortAbort input/output
BridgePerform bridging functions (moved from Originate block in
Call ControlSend data to telephony protocol layer/perform a hookflash
Edit SequenceManage touch tone input editing and user edit sequences
Line OperationsPerform phone line operations (e.g., offer call, accept call,
PeriProducer 2.30)
(moved from Originate block in PeriProducer 2.30)
get line/application resource from pool)
Media OperationsPerform operations on MultiMedia File elements or audio
files
Select Input* Not currently implemented
See the PeriProducer 3.00 User’s Guide for full descriptions of the blocks.
Call Conferencing
Call Conferencing allows up to 16 full participants (or 15 full participants with 19
listen port callers) to connect to a call. Per-line talk and listen privileges can be set at
the start of a conference and dynamically changed during the conference. Call
Conferencing includes the "coaching" feature which allows a conference
administrator (a "coach") to talk to another person in the conference (a "student") and
have the speech output heard only by the student.
The actual number of ports available on a system is determined by the DSP
configuration.
Block-level Access to Protocol Data
Telephone line function blocks (Answer, Disconnect, Call Control, Originate) can
send/receive protocol data directly to/from the telephony protocol layer using built-in
block functions. Specify data to send (or receive) using standard PeriProducer data
cards or literals (send only).
Page 14# P0605081 Ver: 2.3
PeriProducer 3.00 New Features and Enhancements
Blocking/Non-blocking Execution
Many PeriProducer blocks allows 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/Nonblocking Operation in the PeriProducer 3.00 User’s Guide for details.
Resource Pool Support
The MPS allows resources (such as phone lines and applications) to be defined in the
configuration files as shared pools. In the appropriate blocks (e.g., Line Operations),
PeriProducer provides built-in block access to these resources.
Saving Partial Recorded Data
PeriProducer saves partially received Caller Message Recording messages and faxes
in the event of a receive failure. The partial data is either stored in a new file (if
receiving directly into a file) or the application receives a Media Storage token which
references an element in a MultiMedia File. This behavior can be optionally enabled
and disabled in a Record block.
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, etc.) in the condition data. See the
PeriProducer 3.00 User’s Guide for details.
# P0605081 Ver: 2.3Page 15
PeriProducer 3.00 Release Notes
PeriProducer Block Changes
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 (e.g., when a resource is allocated).
Accessory Toolkit Blocks
The Table Search, Table Sort, Date Calculations, and Send email blocks moved from
the main toolkit to the accessory toolkit.
Answer Block
Continue on Ring Detect Removed
The "Continue on Ring Detect" option is removed. In general, use the "Get Call" ->
"Alert Call" states to accomplish the same result.
Get Phone Number Options Removed
The Get Dialed Phone Number and Get Caller’s Phone Number options are removed.
Depending on the specific telephony protocol, this information is automatically
returned by the system for all Answer block actions (except "Reject Call").
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 PeriReporter to display the reports.
Page 16# P0605081 Ver: 2.3
PeriProducer 3.00 New Features and Enhancements
Speak Block
Speech Recognition/Text To Speech
All speech recognition and synthesis functions are performed by external resources.
Refer to the appropriate resource guides for details on using the resource for optimal
programming results.
Speak a URL
The element to speak can be specified by a valid URL address (e.g.,
http://server1/prompts/greeting1.wav).
Read Phone Block
The Read Phone Block now handles Speech Recognition Errors and provides a failure
path for a recognition error. The following recognition errors cause the application to
follow the "Recognition Error" path:
•Speech Too Early
•Too Much Speech
•Too Slow Recognition
System Block
Diagnostic Functions Removed
The diagnostics function is removed.
Condition Data
The "Get Condition Data" function is added. This 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 (see Enhanced Condition Data on
page 22).
Send Host Block
Virtual Terminal (VT) Allocation
VT allocation functions are available from the Send Host block. These replace the VT
allocation Environment block options.
# P0605081 Ver: 2.3Page 17
PeriProducer 3.00 Release Notes
Setting Host Environment Parameters
Host environment parameters are sent from the Send Host block. This function
replaces the Environment block "host" option.
new VT options
parameter option
Receive Host Block
Asynchronous Operation
The "Asynchronous" checkbox is replaced by the "Wait" checkbox (see
Blocking/Non-blocking Execution on page 15). Receive Host operates
asynchronously when the "Wait" checkbox is unchecked.
Page 18# P0605081 Ver: 2.3
PeriProducer 3.00 New Features and Enhancements
Send Fax Block
Fax Composition Removed
The fax Composition feature is not supported. All controls/options used to create and
store composed faxes are removed.
Send Fax from TIFF File
PeriProducer 3.0 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 (this is still supported).
Fax Mode Removed
PeriProducer 3.0 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.
Saving to Named Element
A fax can be saved to a specific-named element in a MultiMedia File. If the
application does not specify an element name, the fax is stored as a new element and
can be accessed by the returned media storage token.
Local Station ID
The Local Station ID (which typically represents the phone number of the station
receiving the fax) can be specified in the block. The Local Station ID is typically
displayed on the transmitting fax machine.
Fax Mode Removed
PeriProducer 3.0 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 (the Disconnect block
can be used for this purpose).
# P0605081 Ver: 2.3Page 19
PeriProducer 3.00 Release Notes
Record Block
Asynchronous Recording
Asynchronous recording allows for an unlimited duration message. Asynchronous
recording is explicitly started and stopped by "Begin" and "End" functions of the
Record block.
Full Duplex Recording
Full duplex recording saves all audio that occurs on a phone line, caller and system.
For example, an application can record a full conversation between a caller and a
referral agent. Recording can also be set to record either caller-only or system-only
output.
Moved Functions
Element deletion functions moved to the Media Operations Block.
Recorded Element Destinations
PeriProducer 3.00 supports recording directly into a specified audio format file
(typically WAV). Applications can also append recordings to existing MMF elements.
Abort Recording using Touch Tones
Callers can abort CMR recordings using a touch tone(s). Note that this differs from
using a touch tone to terminate (and subsequently save) a recording.
Resource Block
Asynchronous Execution Changes
There is no longer an "Async" checkbox in the Resource block. To perform the
resource receive asynchronously, uncheck the "Wait" box.
Resource Support
The following new resources are available in the Resource block: lvr-p, lvr-s, extts-r,
sip, DTMF, Player, Fax, Recorder, FullDuplex Recorder. Many resources are no
longer supported (see Unsupported Resources on page 21).
Page 20# P0605081 Ver: 2.3
PeriProducer 3.00 New Features and Enhancements
Discontinued Features/Functions
Fax Composition
Fax composition is not supported in PeriPro 3.00. Faxes to be sent must be created by
external applications or received (and stored for later use) by the MPS.
Hardware Properties Window
The Hardware Properties Window is removed.
Unsupported Resources
The following resources are no longer supported in PeriProducer 3.00:
•mps
•abb
•asdi
•ast
•iwr
•ppd
•modem
•mts
•iscp
•ctx
•lcr
Obsoleted Functions
The Media Operations block in PeriProducer has obsoleted the file-to-message,
message-to-item and message-to-file functions.
# P0605081 Ver: 2.3Page 21
PeriProducer 3.00 Release Notes
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
$PPROHOME/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.
Default Text to Speech Resource Specification
To specify a default external Text to Speech resource (used with implicit resource
allocation for all "Speak as TTS" prompts), use the System folder’s DefaultTTSRsrc
datacard. The default value for DefaultTTSRsrc is "extts-b". This replaces the Text To
Speech Resource setting in the Hardware properties window of PeriProducer 2.30.
System Folder Changes
•The Constant TTSvoice card is no longer available.
•The ConfidenceLevel card is no longer available.
•The following constants are added:
•None
•All
•Any
•Flush
•On
•Off
•Speech ("S" to identify speech input)
•DTMF ("D" to identify DTMF input)
•The following datacards are added:
•AutoDetectTime
•DefaultCID
•DefaultOutPool
•TransferCID
•DefaultTTSRsc
•ApplicationNumber (replaces LineNumber)
Page 22# P0605081 Ver: 2.3
PeriProducer 3.00 New Features and Enhancements
Environment Options
Many PeriProducer 2.30 Environment options have been obsoleted or replaced by
new environment options and/or block built-in functions 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.
Environment Options Conversions Sheet 1 of 7
2.30 Environment Option3.00 Equivalent
Phone Environment
answerUnsupported as environment option. Use the Answer block
(Answer function) to answer a call.
bargeinSupported for legacy applications only
bargeineventUnsupported (for legacy applications, this is an implied "start
of speech" event)
editUnsupported as environment option. Use the Edit Sequence
Block to enable/disable DTMF input editing.
ekeybdUnsupported
emessUnsupported
eoptUnsupported
eretryUnsupported
firstDtmfFirst (Application and System Environment options)
fkeybdUnsupported
fmessUnsupported
foptUnsupported
fretryUnsupported
ikeybdUnsupported
imessUnsupported
interDtmfInter (Application and System Environment options)
ioptUnsupported
iretryUnsupported
keeptermUnsupported as environment option. Use the "Retain" option
(for the termination character) in Edit Sequence block.
termcharUnsupported as environment option. Use the Edit Sequence
block to enable/set a termination character.
timeoutUnsupported
tnabortUnsupported
tnextUnsupported
# P0605081 Ver: 2.3Page 23
PeriProducer 3.00 Release Notes
2.30 Environment Option3.00 Equivalent
tnullUnsupported
totalLineTotalCall (Application and System Environment options)
trepeatUnsupported
typeaheadUnsupported
tzoneUnsupported
Phone Line Task Environment
autoidSupported for legacy applications only
backspUnsupported as environment option. Use the Edit Sequence
busyLineStandbyMode, set to Busy (Application and System
callrefUnsupported
deleteUnsupported
Environment Options Conversions Sheet 2 of 7
block to enable/set a backspace edit sequence.
Environment options)
eXtextUnsupported. Use the Edit Sequence block to enable/set
user edit sequences.
getringUnsupported as environment option. Use the Answer block
"Get Call" and "Alert Call" functions to continue application
processing without answering the line.
noanswerLineStandbyMode, set to NoAnswer (Application and
System Environment options)
repeatUnsupported
vrepeatUnsupported
xtermUnsupported
Phone Resource Server Environment
prsUnsupported
abeepUnsupported
asetupUnsupported
cdtmfUnsupported
echoUnsupported
idleUnsupported
mdeblockUnsupported
rscconfigRscConfig (Application and System Environment options)
smaxlenUnsupported
smaxresUnsupported as environment option
Page 24# P0605081 Ver: 2.3
PeriProducer 3.00 New Features and Enhancements
Environment Options Conversions Sheet 3 of 7
2.30 Environment Option3.00 Equivalent
sminlenUnsupported as environment option
srecordUnsupported as environment option
tfieldUnsupported as environment option
tfinalUnsupported as environment option
tfirstUnsupported
tstopUnsupported as environment option
Message Recording Environment
firstsilRecFirstSil (Application and System Environment options)
intersilRecInterSil (Application and System Environment options)
maxreclengthUnsupported
silstripRecSilStrip (Application and System Environment options)
Call Origination/Referral Environment
bcttUnsupported
bcvocUnsupported
brttUnsupported
brvocUnsupported
hcttUnsupported
hcvocUnsupported
hrttUnsupported
hrvocUnsupported
numberUnsupported
pdialUnsupported
reftotUnsupported
tpickupUnsupported
vbridgeUnsupported
Call Progress Detection Environment
cpansupUnsupported
cpdialUnsupported
cpdiscUnsupported
decideUnsupported
notoneUnsupported
pickupUnsupported
# P0605081 Ver: 2.3Page 25
PeriProducer 3.00 Release Notes
2.30 Environment Option3.00 Equivalent
rsilenceUnsupported
rvoiceUnsupported
silenceUnsupported
stopUnsupported
toneUnsupported
voiceUnsupported
windowUnsupported
Speech Management Environment
clearSupported for legacy applications only. Use the Abort block
vioabortUnsupported as environment option. Use the Abort block.
Host Environment
Environment Options Conversions Sheet 4 of 7
with the "Caller I/O Only" option enabled.
erer
freevtSupported for legacy applications only. Use the Send Host
block "Free VT" (in Control > Function > Controls) option.
getvtSupported for legacy applications only. Use the Send Host
block "Get VT" (in Control > Function > Controls) option.
headermodeheadermode
hostctlhostctl
intimeintime
parameterSupported for legacy applications only. Use the Send Host
block "parameter" (in Function > Controls) option.
referrefer
rfnorfno
sessionsession
setaidsetaid
unlocksunlocks
usepoolusepool
Advanced Phone Line Management
phoneUnsupported as environment option
capdtmfUnsupported as environment option
capmfUnsupported as environment option
captddUnsupported as environment option
detectSupported for legacy applications only
Page 26# P0605081 Ver: 2.3
PeriProducer 3.00 New Features and Enhancements
Environment Options Conversions Sheet 5 of 7
2.30 Environment Option3.00 Equivalent
dfirstUnsupported as environment option
dinterUnsupported as environment option
discUnsupported
dtmfDtmfToneDur (Application and System Environment options)
elineUnsupported
endtoneUnsupported
fconnectSupported for legacy applications only. Use the Answer
block "Answer Call" function.
finishUnsupported
flashUnsupported
gobusyUnsupported
guardDtmfGuard (Application and System Environment options)
indialUnsupported
keyinUnsupported
keyoutUnsupported
mftoneUnsupported
nansupUnsupported
nofhookUnsupported as environment option. Use the Answer block
"Get Call" and "Alert Call" functions.
rendUnsupported
reortextUnsupported
ringbackUnsupported
ringtextUnsupported
rlineUnsupported
rvalidUnsupported
sendcpUnsupported
ISDN Environment
catsUnsupported as environment option. Use the "Protocol Data"
fields in the Answer, Disconnect, Originate, and Call Control
blocks (as appropriate).
ccodeUnsupported as environment option. Use the "Protocol Data"
fields in the Answer, Disconnect, Originate, and Call Control
blocks (as appropriate).
# P0605081 Ver: 2.3Page 27
PeriProducer 3.00 Release Notes
2.30 Environment Option3.00 Equivalent
cprocUnsupported as environment option. Use either the
smrtUnsupported as environment option. Use the "Protocol Data"
udataUnsupported as environment option. Use the "Protocol Data"
Optional Exception Conditions
creferUnsupported as environment option
crepeatUnsupported as environment option
rngbackUnsupported as environment option
Environment Options Conversions Sheet 6 of 7
"Protocol Data" fields in the Answer, Disconnect, Originate,
and Call Control blocks (as appropriate), or the Answer block
"Proceeding Call", function. Refer to the protocol-specific
documentation for details on sending call state information.
fields in the Answer, Disconnect, Originate, and Call Control
blocks (as appropriate).
fields in the Answer, Disconnect, Originate, and Call Control
blocks (as appropriate).
uedit3Unsupported 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
Speech Manager OptionsSuperseded by "Application and System Options"
Host Manager OptionsSuperseded by "Host Environment"
Vengine OptionsVengine Options
PeriWeb OptionsPeriWeb Options
VENGINE Environment
alarmdbtaskalarmdbtask
apprestartapprestart
centurymarkcenturymark
debugdebug
deltimedcalldeltimedcall
hnowaitUnsupported (a corresponding VENGINE runtime option is
Superseded by "Application and System Options"
available)
intermsgintermsg
maxmessageUnsupported
modemode
noticenotice
Page 28# P0605081 Ver: 2.3
PeriProducer 3.00 New Features and Enhancements
Environment Options Conversions Sheet 7 of 7
2.30 Environment Option3.00 Equivalent
numsetnumset
rscertimerscertime
rscintimerscintime
setvpslinesetvpsline
softtermsoftterm
speakspeak
timedcalltimedcall
unnoticeunnotice
vmstimedcallvmstimedcall
vpsrcvtimevpsrcvtime
webtimeoutwebtimeout
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 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 Condition3.00 ConditionConversion
abendabendabend
addfailimportfail w/Status
"ErrInUse" in condition data
addsuccimportcmpimportcmp
altlinkdownaltlinkdownaltlinkdown
ansfailanswerfailanswerfail
$addfail
asrdetasrdetasrdet
asyncdataUnsupported
# P0605081 Ver: 2.3Page 29
PeriProducer 3.00 Release Notes
2.30 Condition3.00 ConditionConversion
asyncfailUnsupported
autofaildetinputfaildetinputfail
autotimautotimautotim
avserravserravserr
badoperationbadoperationbadoperation
badparameterbadparameterbadparameter
calltimcalltimcalltim
carlossUnsupported
ccs7ccccs7ccccs7cc
Conditions Conversion Sheet 2 of 10
chartimgetinputfail w/Status
"ErrInter" field in condition
data
cmrhighUnsupported
cmrlowUnsupported
comfailcomfailcomfail
connanswercmpanswercmp
creferUnsupported
crepeatUnsupported
crepmaxUnsupported
cticondcticondcticond
ctidownctidownctidown
ctifailctifailctifail
ctiupctiupctiup
ctxccUnsupported
ctxfailccUnsupported
ctxokccUnsupported
getinputfail
cvoiceUnsupported
dcdownUnsupported
dcupUnsupported
deadlockdeadlockdeadlock
delcompdelcmpdelcmp
delfaildelfaildelfail
dialtnUnsupported
Page 30# P0605081 Ver: 2.3
PeriProducer 3.00 New Features and Enhancements
Conditions Conversion Sheet 3 of 10
2.30 Condition3.00 ConditionConversion
disableUnsupported
discDependent upon event which caused disc condition.
disc (caller hangup)$disc
disccmp (system-initiated
disconnect)
discfaildiscfail w/Status field in
condition data
dtmfzlrecordfail w/Status
"ErrZeroLengthDTMF" in
condition data
dupkeydupkeydupkey
dupvalidxdupvalidxdupvalidx
enableUnsupported
endfaildiscfail$endfail
endfileendfileendfile
errorerrorerror
ertimeoutDependent upon event which 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)
expiredexpiredexpired
faxdetfaxdetfaxdet
forcefreeforcefreeforcefree
forwardUnsupported
fromphonefromphonefromphone
frstimgetinputfail w/Status
"ErrFirst" in condition data
ftomfailUnsupported
ftomsuccUnsupported
$ertimeout
getinputfail
# P0605081 Ver: 2.3Page 31
PeriProducer 3.00 Release Notes
2.30 Condition3.00 ConditionConversion
getfailDependent upon event which caused getfail condition
Conditions Conversion Sheet 4 of 10
getfail (gen’d by VENGINE)$getfail
getrsrcfail (failed resource
get request)
rcvfaxfail w/Status
"ErrNoFaxAvail" in condition
data (failed receive fax when
fax not available)
sndfaxfail w/Status
"ErrNoFaxAvail" in condition
data (failed send fax when
fax not available)
getvtfailhgetvtfailhgetvtfail
getvtpasshgetvtcmphgetvtcmp
gotresDependent upon event which caused gotres condition
getrsrccmp$gotres
rcvfaxcmp$gotres
sndfaxcmp$gotres
greenUnsupported
hctloffhctloffhctloff
hctlonhctlonhctlon
$getfail
$getfail
$getfail
heldresUnsupported
hkfcomphookflshcmphookflshcmp
hkffailhookflshfailhookflshfail
hostasyncevthostasyncevthostasyncevt
hostdownhostdownhostdown
Page 32# P0605081 Ver: 2.3
PeriProducer 3.00 New Features and Enhancements
Conditions Conversion Sheet 5 of 10
2.30 Condition3.00 ConditionConversion
hostfailDependent upon event which caused hostfail condition
hrcvmapfail w/Status
"ErrNoData" or "ErrTimeout"
in condition data (failed to
receive map)
hrcvtxtfail w/Status
"ErrNoData" or "ErrTimeout"
in condition data (failed to
receive text)
hsndmapfail (failed to send
map)
hsndtxtfail (failed to send
text)
hsndaidfail (failed to send
AID key)
hostuphostuphostup
hstatdatahstatdatahstatdata
idleUnsupported
infDependent upon event which caused inf condition
inf (gen’d by VENGINE)$inf
rcvfaxfail w/Status
"ErrNoFaxAvail" in condition
data (failure to receive fax)
$hostfail
$hostfail
$hostfail
$hostfail
$hostfail
$inf
recordfail w/Status
"ErrZeroLengthDTMF" or
"ErrZeroLengthSilence" in
condition data (failure to
record CMR message)
intertimeoutintertimeout (gend’ by
VENGINE)
invreqinvreqinvreq
ioerrioerrioerr
iscpfiscpfiscpf
isdnccUnsupported
iupdbusyUnsupported
iupdcompUnsupported
iupdfailUnsupported
lengerrlengerrlengerr
linkdownlinkdownlinkdown
$inf
$intertimeout
# P0605081 Ver: 2.3Page 33
PeriProducer 3.00 Release Notes
2.30 Condition3.00 ConditionConversion
lockfaillockfaillockfail
logdenylogdenylogdeny
lostUnsupported
marshallmailshallmarshall
mmfhighmmfhighmmfhigh
mmflowmmflowmmflow
modvarmodvarmodvar
mpsccUnsupported
mpsinfoUnsupported
mpsocUnsupported
mpsofUnsupported
mtoffailexportfailexportfail
Conditions Conversion Sheet 6 of 10
mtofsuccexportcmpexportcmp
nilobjrefnilobjrefnilobjref
nonexistobjnonexistobjnonexistobj
norecfoundnorecfoundnorecfound
norestartnorestartnorestart
nospacenospacenospace
notfndnotfndnotfnd
notimplnotimplnotimpl
notlogonnotlogonnotlogon
notopennotopennotopen
oaspeakcmp w/Status "Abort"
in condition data
ocDependent upon event which caused oc condition
speakcmp w/Status "Done"
in condition data (completed
speak request)
sndfaxcmp (completed send
fax)
speakcmp
$oc
$oc
sndrsrccmp (completed
send resource)
$oc
Page 34# P0605081 Ver: 2.3
PeriProducer 3.00 New Features and Enhancements
Conditions Conversion Sheet 7 of 10
2.30 Condition3.00 ConditionConversion
ofDependent upon event which caused of condition
of (gen’d by VENGINE)$of
sndfaxfail w/Status
"ErrNoFaxAvail" in condition
data (failed send fax)
sndrsrcfail (failed send
resource)
speakfail (failed speak
request)
ofaxdetUnsupported
orberrorberrorberr
oscocsndrsrccmp
oscofsndrsrcfail
outbadorigfail w/Status
"ErrInvalidLineState" in
condition data
outbsyorigfail w/Status "ErrBusy" in
condition data
outcomporigcmporigcmp
outfailorigfail w/Status "ErrBusy",
"ErrInvalidLineState",
ErrNoAnswer", or
"ErrRejected" in condition
data
$of
$of
$of
origfail
origfail
$outfail
outnoaorigfail w/Status
"ErrNoAnswer" in condition
data
outrejorigfail w/Status
"ErrRejected" in condition
data
outvoaUnsupported
pgidpgidpgid
pgmlpgmlpgml
pgunpgunpgun
prsfreeDependent upon event which caused prsfree condition
prsfree (gen’d by VENGINE)$prsfree
freersrccmp (completed free
resource)
qiderrqiderrqiderr
origfail
origfail
$prsfree
# P0605081 Ver: 2.3Page 35
PeriProducer 3.00 Release Notes
2.30 Condition3.00 ConditionConversion
qzeroqzeroqzero
rcverrrcvrsrcfail$rcverr
rcvnullDependent upon event which caused rcvnull condition
Conditions Conversion Sheet 8 of 10
rcvnull (gen’d by VENGINE)$rcvnull
hrcvmapfail w/Status
"ErrNoData" in condition
data (failed receive map)
hrcvtxtfail w/Status
"ErrNoData" in condition
data (failed receive text)
rcvoiceUnsupported
rdcdownUnsupported
rdcupUnsupported
rdisableUnsupported
redUnsupported
refbadtransferfail w/Status
"ErrInvalidLineState" in
condition data
refbegtransfercmptransfercmp
refcandisccmp$refcan
reffailtransferfail w/Status
"ErrInvalidLineState" or
"ErrRejected" in condition
data
$rcvnull
$rcvnull
transferfail
$reffail
refrejtransferfail w/Status
"ErrRejected" in condition
data
reftimcalltim$reftim
renableUnsupported
reorderUnsupported
resumefailresumefailresumefail
rgreenUnsupported
ringalertcmpalertcmp
rinfailalertfailalertfail
rlostUnsupported
rngbackUnsupported
transferfail
Page 36# P0605081 Ver: 2.3
PeriProducer 3.00 New Features and Enhancements
Conditions Conversion Sheet 9 of 10
2.30 Condition3.00 ConditionConversion
rredUnsupported
rscocrscocrscoc
rscofrscofrscof
rsilenceUnsupported
rvoiceUnsupported
rxdcdownUnsupported
rxdcupUnsupported
rxdisableUnsupported
ryellowUnsupported
sentcpsndtonecmpsndtonecmp
serverdownserverdownserverdown
setfailctrlrsrcfail$setfail
setresctrlrsrccmpctrlrsrccmp
silenceUnsupported
silzlrecordfail w/Status
"ErrZeroLengthSilence" in
condition data
softtermsofttermsoftterm
sqlerrsqlerrsqlerr
sslfailsslfailsslfail
stoptimUnsupported
stpringUnsupported
tcapcctcapcctcapcc
tftprecfailtftprecfailtftprecfail
tftprecsucctftprecsucctftprecsucc
tftpsendfailtftpsendfailtftpsendfail
tftpsendsucctftpsendsucctftpsendsucc
timerestimerestimeres
toomanyrowstoomanyrowstoomanyrows
recordfail
tophonefailtophonefailtophonefail
ttdatagetinputcmpgetinputcmp
ttdetttdetttdet
# P0605081 Ver: 2.3Page 37
PeriProducer 3.00 Release Notes
2.30 Condition3.00 ConditionConversion
Conditions Conversion Sheet 10 of 10
ttfailgetinputfail w/Status
"ErrFirst" in condition data
uedit0 - uedit3uedit0 - uedit3uedit0 - uedit3
unexdataunexdataunexdata
unexhostunexhostunexhost
unexphoneunexphoneunexphone
valueperrvalueperrvalueperr
voiceUnsupported
vrtovrtovrto
webfailwebfailwebfail
webtimeoutwebtimeoutwebtimeout
xdisableUnsupported
xmtcompUnsupported
xmtfailUnsupported
yellowUnsupported
$ttfail
Using MultiMedia Elements
Deleting Elements
In PeriProducer 3.00, delete MMF elements using the Media Operations block
"Delete" function. The System Block "Delete MS Token or Vocabulary Item"
function is still available, but does not provide a failure path connector as does the
Media Operations block.
Importing and Exporting Elements
In PeriProducer 3.00, import and export MMF elements using the Media Operations
block "Import" and "Export" functions. The associated call functions are still
available, but using the System block does not provide a failure path connector as does
the Media Operations block.
Receiving Speech Recognition Resource Results
If the system uses DTMF detection and speech recognition, the application does not
need to start autoid and handle detection conditions (asrdet/ttdet). The Read
Phone operation passes back a field to the application which indicates the source of
the input (speech or DTMF, accordingly).
Page 38# P0605081 Ver: 2.3
PeriProducer 3.00 New Features and Enhancements
Play the initial prompts with "Accept Input..." to allow for both DTMF and speech
input. To allow speech recognition bargein, enable the Prompt Interrupt feature (click
the button).
Miscellaneous
VRAM Language
VRAM is no longer supported.
Downward Porting of .ppr Source Code
Source code cannot be ported to previous versions of PeriPro.
MPS Release Level
You must use PeriPro 3.0 on MPS 2.1 or above.
# P0605081 Ver: 2.3Page 39
PeriProducer 3.00 Release Notes
This page has been intentionally left blank.
Page 40# P0605081 Ver: 2.3
Porting 2.30
Applications to 3.00
This chapter covers:
1. Porting PeriProducer 2.30 applications
to the 3.00 environment
2. Porting Standard 2.30 Toolkit Applications to 3.00
3. Porting MPS Toolkit Applications to 3.00
4. Known Conversion Issues
PeriProducer 3.00 Release Notes
Porting 2.30 Applications to 3.00
PeriProducer 3.00 supports legacy (PeriProducer 2.30) applications. Load the
application into PeriProducer and PeriProducer converts the application
automatically.
Before porting the application, read through the entire Release Notes to find out what
features are not supported/have changed and other issues.
Application Porting Considerations
Consider the following when porting the legacy application:
•Make a copy of the source file and port the copy.
•Back up the source file on another system and/or external media
•Save the ported copy as a different name (like <original_name>300)
Porting Standard 2.30 Toolkit Applications to 3.00
Applications that used the standard PeriProducer 2.30 toolkit are automatically
converted by PeriProducer 3.00. No other setup or configuration procedures are
required to convert the 2.30 legacy applications.
Load into PeriProducer 3.00
Load the legacy application into PeriProducer as you would any other application. The
conversion takes place automatically. The PeriProducer logo will indicate that the
application has changed and needs to be saved.
Use the PeriProducer Command Line
Use the following command line syntax to convert a legacy application:
peripro -c <application>
For example, to convert numdemo.ppr, enter peripro -c numdemo. You can
also use filename wildcards (e.g., peripro -c num*) to batch convert
applications. The example converts all applications in the current directory whose
names start with "num".
Page 42# P0605081 Ver: 2.3
Porting 2.30 Applications to 3.00
Porting Events
During application porting, the following events occur:
•Conditions and environment options are converted when possible. Refer to
Conditions on page 29 and Environment Options on page 23 for conversions.
•Blocks are converted to their nearest possible counterparts in 3.00.
•Resources are obsoleted.
•The original file is renamed by changing its extension to .p2X.
•The "PeriPro 2.30 Runtime Behavior" option is enabled by default. See the
PeriProducer User’s Guide for information about the 2.30 Runtime Behavior
option.
•A file with name beginning with conversionlog_ followed by the
application name and with extension .txt is created and contains messages
pertaining to the conversion process. A similar file is created with the
extension .html and is in HTML format.
# P0605081 Ver: 2.3Page 43
PeriProducer 3.00 Release Notes
Porting MPS Toolkit Applications to 3.00
Applications that use the MPS Toolkit require procedures to replace the old MPS
toolkit with a special conversion toolkit for porting to the PeriProducer 3.00 toolkit.
These special conversion toolkits are distributed with PeriProducer 3.00 by default.
MPS Toolkit Replacement
There are two replacement versions of MPS Toolkit: 1.30 and 2.00. The files are
located in $PPROHOME/conv as follows:
conv/
•IMpsfolder1.3 (IMps.folder for MPS Toolkit 1.3)
•IMpsfolder2.0 (IMps.folder for MPS Toolkit 2.0)
•mpsconvkit1.3 (mps.pprotoolkit for MPS Toolkit 1.3)
•mpsconvkit2.0 (mps.pprotoolkit for MPS Toolkit 2.0, including
conference toolkit components)
•IMps.folder (working file)
•mps.pprotoolkit (working file)
•mpsContainer.ppr (for debugging only)
conv/icons
•*.icon (i.e. all component icons)
conv/pprs
•*.ppr (i.e. all component pprs, including the ones below)
•mpsSpeak1_3.ppr (Speak for MPS Toolkit 1.3)
•mpsSpeak2_0.ppr (Speak for MPS Toolkit 2.0)
•mpsMoveConditionData1_3.ppr (MoveConditionData for MPS
Toolkit 1.3, directly specified in mpsconvkit1.3)
•mpsMoveConditionData2_0.ppr (MoveConditionData for MPS
Toolkit 2.0, directly specified in mpsconvkit2.0)
Replace Previous MPS Toolkit
Before converting a legacy MPS Toolkit application, replace the previous MPS toolkit
with a special conversion toolkit using the pproinfo -m [ 1.3 (for MPS Toolkit
1.3) | 2.0 (for MPS Toolkit 2.0) ] command. pproinfo -m copies the appropriate
conversion toolkit and system folder files to the proper PeriProducer areas.
Additionally, include $PPROHOME/conv in the $PPROPATH so that the
replacement MPS toolkit can be loaded under PeriProducer 3.00. $PPROPATH should
not include a path to the old MPS Toolkit.
Page 44# P0605081 Ver: 2.3
Porting 2.30 Applications to 3.00
Load into PeriProducer 3.00
Perform the following to convert a legacy PeriProducer 2.30/MPS Toolkit 1.3/2.00
application by loading the legacy application into PeriProducer 3.00:
1. Identify which version of the MPS Toolkit was used by the PeriPro 2.30
application.
2. Replace the old MPS Toolkit (see Replace Previous MPS Toolkit on page
44).
3. Start PeriProducer with the -m option (peripro -m). This option
causes the conversion of certain conditions (generated by the MPS
resource) into their equivalent PeriProducer 3.00 conditions.
4. Load and save the PeriProducer 2.30 application.
Use the PeriProducer Command Line
Use the following command line syntax to convert a legacy application:
peripro -c -m <application>
For example, to convert numdemo.ppr, enter peripro -c -m mpsnumdemo.
You can also use filename wildcards (e.g., peripro -c mpsnum*) to batch
convert applications. The example converts all applications in the current directory
whose names start with "mpsnum".
# P0605081 Ver: 2.3Page 45
PeriProducer 3.00 Release Notes
Conversion Logs
The conversion logs are detailed lists of issues encountered during conversion of
PeriProducer 2.30 applications to PeriProducer 3.00. The conversion logs are written
to the same directory as the source (2.30) application. The logs are named
conversion_appname.txt (in plain text format) and
conversion_appname.html (in HTML format).
Each log entry indicates an application function which required some translation to
become PeriProducer 3.00 compatible. A conversion is divided into three categories:
1. Information. This indicates something which should not affect the functionality of the application. A typical information message is the conversion of a 2.30 condition name to a new 3.00 condition name. The
application will react the same way in PeriProducer 3.00, just using a different condition name.
2. Warning. This indicates something which successfully converted but
may not work as expected in 3.00. A typical warning message is for an
obsoleted block setting which should not affect application function.
3. Severe. This indicates something which requires manual application editing in order for the application to run under PeriProducer 3.00. Severe
messages can include
•using features/resources no longer supported (such as fax composition)
•obsoleted environment settings, conditions, system datacards which do
not have an equivalent in PeriProducer 3.00
Page 46# P0605081 Ver: 2.3
Known Conversion Issues
Set Resource Label in 2.30
PeriProducer 2.30 uses a Resource block Set operation to change the external resource
(e.g. OSCAR) label. PeriProducer 3.00 converts the Resource (Set) block to an
Environment block which sets the RscLabel parameter and enables the Wait option.
If the Resource (set) block had the failure connector enabled, the Environment block
has the failure connector enabled and connects to the same failure path as in the 2.30
application.
If the 2.30 application explicitly handled the setfail (or setres) condition for a
Resource set (instead of using the failure connector), you must manually edit the
converted application to explicitly handle the envfail (or envcmp) condition. The
setfail (or setres) condition in 2.30 automatically converts to
ctrlrsrcfail (or ctrlrsrccmp) in 3.00. If the resource label change fails in
3.00, the envfail condition occurs, not the ctrlrsrcfail condition.
Porting 2.30 Applications to 3.00
Unsupported 2.30 Resources
Several resources from PeriProducer 2.30 are not supported in PeriProducer 3.00 (see
Unsupported Resources on page 21). When an unsupported resource is encountered
during conversion, the unsupported resource is reported in the conversion log file. In
the application, the resource is changed from the resource name to "Unsupported" in
the associated Resource block. Depending on the resource type, you may not be able
to use the application with PeriProducer 3.00.
Resource Block Conversions
The following conversions occur automatically for 2.30 applications which use
external resources (Resources block):
•Receive Resource with the resource "phonePRS" is converted into a Read
Phone block.
•Receive Resource with the resource "lvr-X" (where X is any letter of a valid
2.30 resource) is converted into a Read Phone block.
•Send Resource with the resource "phonePRS" is converted into a Speak block
(with the prompt spoken as TTS Literal).
•Send Resource with the resource "extts-X" (where X is any letter of a valid
2.30 resource) is converted into a Speak block (with the prompt spoken as
TTS Literal).
•If Wait is enabled or a failure connector is available on a 2.30 Resource block,
Wait is enabled on the 3.00 converted block.
# P0605081 Ver: 2.3Page 47
PeriProducer 3.00 Release Notes
Flushing the Speak Prompt Buffer
The PeriProducer 2.30 System block "Start Reprompt List" function flushes the list of
previously spoken output. This function is still supported in PeriProducer 2.30.
However, it is recommended that to flush the output list buffer, use a Resource block
with the Resource field set to "Player", the CID field set to System.DefaultCID, the
Operation set to "Control", and the Send From field set to System.Constants.Flush.
This suggestion action appears in a 2.30 application’s conversion log file.
System Transfer Connection ID Datacard
PeriProducer 3.00 introduces the system datacard "TransferCID". The system returns
the Connection ID (CID) of line which is used for a transfer operation back to the
TransferCID datacard. TransferCID should not be used in PeriProducer 3.00-native
applications to specify a CID for a transfer operation.
TransferCID is populated only if the transfer operation is performed synchronously
(Originate block with Wait enabled). If Wait is not enabled, TransferCID stays empty.
During 2.30 to 3.00 conversion, PeriProducer may use TransferCID in this capacity
(to specify a CID instead of receiving a value from the system). However, this is done
only when converting applications.
Automatic Detection of Speech or DTMF Input (AUTOID)
When converting applications that perform AUTOID (automatic detection of speech
or DTMF input) it is necessary to make sure that the prompt(s) prior to the
environment block(s) that setup autoid (detect timer and enable autoid) have, at
minimal, the DTMF and LVR resources on after the prompt completes.
Page 48# P0605081 Ver: 2.3
Loading...
+ hidden pages
You need points to download manuals.
1 point = 1 manual.
You can buy points or you can get point for every manual you upload.