Legacy v. 1.20.0 PSPI Functions
Caution!
Caution!
Proprietary & Confidential
This chapter documents the PSPI functions that maintain backward
compatibility with code developed for ConferenceNow! v. 1.2x.x. For your
convenience, it also includes functions that remain unchanged from v. 1.10.0.
If you're maintaining code originally developed for v. 1.2x.x, all the PSPI
functions you need are in this one chapter.
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.
You can use the v. 1.20.0 PSPI functions with newer versions of the ReadiVoice
software to avoid rewriting your code. However, you can't access the newer
options and features.
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
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).
To access all the features added since ConferenceNow! v. 1.2x.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.00.0 and v. 1.20.0). For
AddSub_v2130()
instance, don't use
them with the legacy
UpdateSub_v1200()
Polycom authorizes the use of only the stored procedures described in this
publication. Other .sp files reside in the ReadiVoice file system; however, those not
included here are designed for Polycom internal use only and may cause
unforeseen problems if used otherwise.
2
through 5. If your system uses fixed
"If vExternalId is used for translation
Chapter
2.
to add subscribers and then try to update
function.
8
281
Need help?
Do you have a question about the ReadiVoice and is the answer not in the manual?
Questions and answers