Legacy v. 2.10.0 PSPI Functions
Proprietary & Confidential
177
Using this procedure, or its newer siblings, such as
reduces the traffic through the ODBC interface, since a single SPC
accomplishes what required two to four SPCs in earlier versions of PSPI. This
efficiency gain is especially helpful if you’re bulk-loading large numbers of
new subscribers.
Two options impact this SPC’s performance (the speed with which it updates
the database and returns to the client):
If you set
AccessNumVerify
to
1
, the SPC performs access number integrity
checking. This takes more time due to additional queries into the database. The
integrity checks consist of:
•
Verifying that each access number for this subscriber is in a different
access class.
•
For a shared access number, checking that the combination of hidden
number and access code is unique.
•
For a private access number, making sure all access numbers that share the
specified hidden number are marked unavailable for assignment to other
subscribers.
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.
Caution!
The CacsEventUpdate table must be purged periodically using the
cleanCacsEvtUpdate.pl script, as described in the
ReadiVoice Administration &
Maintenance Guide
.