Addphonenum() - Polycom ReadiVoice Reference Manual

ReadiVoice PSPI Reference

AddPhoneNum()

Caution!
Parameters
88
Stored procedure for adding a new access phone number to the database and,
optionally, assigning it to an existing subscriber at the same time. Compatible
with v. 2.10.0 or later of the software.
The subscriber, if specified, must already exist in the database. If the access
number is already in the database as well, the access number is simply
assigned to the subscriber. To add a new subscriber and a new access number
at the same time, use AddSubAndAccNum(), AddSubAndAN_v2110(),
AddSubAndAN_v2130(), AddSubAndAN_v2500(), or AddSubAndAN_v2550().
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.
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" on page 4.
Proprietary & Confidential