Proprietary & Confidential
127
4
Legacy v. 2.13.0/2.30.0 PSPI
Functions
This chapter documents the PSPI functions that maintain backward
compatibility with code developed for ReadiVoice v. 2.13.x, v. 2.14.x, v. 2.30.x,
or v. 2.31.x.
For your convenience, this chapter also includes functions that remain
unchanged from previous versions. If you’re maintaining code originally
developed for v. 2.13.0 or later, but prior to v. 2.32.0, all the PSPI functions you
need are in this one chapter.
You can use the v. 2.13.0/2.30.0 PSPI functions with newer versions of the
software to avoid rewriting your code. However, you can’t access the new
options and features. To access all the features added since v. 2.31.x, 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.10.0 and v. 1.30.0). For
instance, don’t use
to add subscribers and then try to update
them with the legacy
function.
ReadiVoice-IP functionality was merged into the standard release of ReadiVoice
v. 2.30.0, so the same stored procedures are used for both the ReadiVoice-PSTN
and ReadiVoice-IP configurations.
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!
Polycom authorizes the use of only the stored procedures described in this
publication. Other
files reside in the ReadiVoice file system; however, those not