Polycom ReadiVoice Reference Manual page 142

ReadiVoice PSPI Reference
Caution!
Parameters
Parameter
AccessNumVerify
NotifyCallRouter
vEntryDate
vActivationDate
vBillingId
vBillingType
vBillingPhone
vBillingAddress
134
In earlier versions of ReadiVoice (prior to v. 2.50.0), the NotifyCallRouter
parameter let you choose whether to load new data into call router memory
immediately (NotifyCallRouter = 1) or write it to the CacsEventUpdate
table (NotifyCallRouter = 0).
In ReadiVoice v. 2.50.0 and later, this choice has been removed, and the
NotifyCallRouter parameter remains only to ensure backward
compatibility. Regardless of how you set this flag, the SPC puts the new data
into the CacsEventUpdate table in the database; the CACS then updates the
call router with the data from the temporary table every ten seconds.
The CacsEventUpdate table must be purged periodically using the
cleanCacsEvtUpdate.pl script, as described in the ReadiVoice Administration &
Maintenance Guide.
Specify all parameters. The constraints column shows specific value or range
constraints. Note that the vExternalId parameter must have a data type of
CHAR(30). For syntax rules and constraints applicable to all parameters, see
"Calling Stored Procedures"
Data Type Constraints
SMALLINT 0, 1
SMALLINT 0, 1
DATETIME
YEAR TO
MINUTE
DATETIME
YEAR TO
MINUTE
INT -1, >0
SMALLINT 0, 1
CHAR (30)
CHAR (255)
on page 4.
Description
Validate access number integrity. 0: No; 1: Yes.
Parameter remains only to maintain backward
compatibility. Regardless of setting, the SPC puts
new data into the CacsEventUpdate table. See
caution above about maintaining this table.
Time of creation.
Time of activation.
Existing billing ID (from database) or -1 to let
system generate a new billing ID.
Type of billing. 0: Credit card; 1: Phone
number.
Phone number to bill or empty string.
Billing address or empty string.
Proprietary & Confidential