Legacy Vs. Current Pspi Functions - Polycom ReadiVoice Reference Manual

ReadiVoice PSPI Reference

Legacy vs. Current PSPI Functions

Caution!
2
ReadiVoice was known as ConferenceNow! prior to v. 2.00.0. ReadiVoice-IP
v. 1.00.0 through v. 1.1x used the same stored procedures as ReadiVoice v. 2.10.0.
ReadiVoice-IP functionality was merged into the standard release of ReadiVoice
v. 2.30.0.
Some PSPI functions can be used with all versions of
ReadiVoice/ConferenceNow! and some can't. Over time, product
enhancements have introduced new options and features that necessitated
various database changes.
New PSPI functions enable you to work with new options and features and to
access the new data. However, new PSPI functions can't be used with earlier
versions of the software. For example, the new PSPI functions introduced with
ReadiVoice v. 2.50.0 can't be used with versions prior to v. 2.50.0.
To ensure backward compatibility, however, the legacy PSPI functions are still
supported (to the extent possible) in newer versions of the software. If you
developed an interface for an earlier version of ReadiVoice/ConferenceNow!,
you can continue using it with ReadiVoice v. 2.50.0 or later, with little or no
code modifications.
If two-passcode call flow is enabled, then you can't use any pre-v.2.10.0 stored
procedures except those included in chapters
translation numbers, be aware that pre-v.2.10.0 stored procedures don't perform
the required external ID validations (see
numbers..." on page 18) and that you can't use the v.1.10.0 stored procedures
because they don't provide the required external ID. Note also that the vExternalId
parameter must now be a CHAR, even for legacy stored procedures.
The legacy v. 1.10.0 functions work with any version of the software; the
legacy v. 1.20.0 functions work with v. 1.20.0 or later; the legacy v. 1.30.0
functions work with v. 1.30.0 or later; and so forth. However, these legacy
functions can't set or retrieve the new variables available in the current version
of the ReadiVoice software. For instance:
The legacy add functions, such as AddSubscriber() and
•
AddSub_v1200(), default the new options and features, such as
PartPlayCount, to zero or an empty string, as appropriate.
• The legacy update functions, such as UpdateSubscriber() and
UpdateSub_v1200(), can't modify the new options and features settings.
The legacy get functions, such as GetSubscriber() and GetSub_v1300(),
•
can't retrieve the new options and features settings.
Do not "mix and match" current and legacy functions (or two different levels
of legacy functions, such as v. 2.00.0 and v. 1.20.0). For instance, don't use
AddSubAndAN_v2500()
UpdateSubscriber()
the legacy
2 through 5. If your system uses fixed
"If vExternalId is used for translation
to add subscribers and then try to update them with
function.
Proprietary & Confidential