Deletesubscriber() - Polycom ReadiVoice Reference Manual

DeleteSubscriber()

Caution!
Parameters
Parameter
vSubscriberId
vAccessNum
vDeletePhoneNum
vNotifyCallRouter
Proprietary & Confidential
Stored procedure for changing a subscriber's account status to 2 (deleted).
Compatible with v. 2.10.0 or later of the software. You can run a purge script
to periodically remove deleted accounts from the database.
Identify the subscriber either by the subscriber ID or by the access phone
number, if it's private. If you set DeletePhoneNum to 1, and if the access phone
number isn't being used by any other subscribers, it's removed from the
database.
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. For syntax rules and constraints applicable to all parameters, see
"Calling Stored Procedures"
Data Type Constraints
INT >0
CHAR (60)
SMALLINT 0, 1
SMALLINT 0, 1
on page 4.
Description
ID of subscriber. Must be in database.
Access phone number of subscriber (numeric
characters only). Set to empty string if not
querying by access number. Query by access
number is valid only for private access number
(only one subscriber associated with this
number).
Delete access phone number from
phonenumbers table. 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.
Legacy v. 2.10.0 PSPI Functions
199