Addsubandanstring() - Polycom ReadiVoice Reference Manual

AddSubAndANString()

accessNum1,hiddenNum1,sharedFlag1,numberType1|accessNum2,hiddenNum2,sharedFlag2,numberType2|...
Parameter
accessNum
hiddenNum
sharedFlag
numberType
Caution!
Proprietary & Confidential
Stored procedure for adding a new subscriber and assigning four or more
access numbers to the subscriber at the same time. This procedure requires
ReadiVoice v. 2.56.0 or later.
This procedure is similar to AddSubAndAN_v2550(), but the three sets of access
number parameters have been replaced by vAccessNumberString, which can
contain up to 720 characters. Assuming ten-digit phone numbers, this enables
a single SPC to assign up to 27 access numbers to a subscriber.
Each access number requires four parameters, delimited by commas. Each set
of four parameters must be delimited by pipes. The layout is as follows:
The table below defines the four parameters for each access number.
Constraints Description
Access number (numeric characters only).
Length >0
Hidden number for this access number (numeric characters only). If
Length >0
not using hidden numbers, duplicate the access number.
Type of access number. 0: Private; 1: Shared.
0, 1
Number class of access number. Must be in numberclasses table.
>0
The procedure first adds the subscriber to the database. Then, it parses
vAccessNumberString, validates the parameters, and puts them into a
temporary table. The constraints column in the table above shows the
validation tests performed on the string data. If any parameter in the string is
invalid, the entire string is treated as invalid, the subscriber record is flagged
as deleted, and the SPC returns an error.
After the string has been parsed, validated, and written to the temporary table,
the SP adds each access number to the database (if it doesn't already exist),
removes it from the temporary table, and assigns it to the subscriber.
If you set AccessNumVerify to 1, the SPC performs access number integrity
checking. See page 17
numbers, see the restrictions regarding vExternalId described on
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.
for a description. If your system uses fixed translation
Current PSPI Functions
page 18.
29