Proprietary & Confidential
261
7
Legacy v. 1.30.0 PSPI Functions
This chapter documents the PSPI functions that maintain backward
compatibility with code developed for ConferenceNow! v. 1.3x.x. For your
convenience, it also includes functions that remain unchanged from previous
versions. If you’re maintaining code originally developed for v. 1.3x.x, all the
PSPI functions you need are in this one chapter.
You can use the v. 1.30.0 PSPI functions with newer versions of the software to
avoid rewriting your code. However, you can’t access the newer options and
features.
To access all the features added since ConferenceNow! v. 1.30.0, rewrite your
code to use the functions described in
Do
not,
however, “mix and match” current and legacy functions (or two
different levels of legacy functions such as v. 2.00.0 and v. 1.30.0). For instance,
don’t use
to add subscribers and then try to update
them with the legacy
function.
For ReadiVoice v. 2.50.0 and later, the
vExternalId
parameter must have a data
type of
CHAR(30)
, even if you’re using legacy SPs.
Caution!
If two-password call flow is enabled, then you can’t use any pre-v.2.10.0 stored
procedures except those included in chapters
through
. If your system uses fixed
translation numbers, be aware that pre-v.2.10.0 stored procedures don’t perform
the required external ID validations (see
“If vExternalId is used for translation
Caution!
Polycom authorizes the use of only the stored procedures described in this
publication. Other
files reside in the ReadiVoice file system; however, those not