Polycom ReadiVoice Reference Manual page 99

Caution!
Proprietary & Confidential
additional access numbers, the procedure then attempts to add each of them
to the database, if they don't already exist, and assigns those numbers to the
subscriber.
This procedure is similar to AddSubAndAN_v2130(), but has two additional
parameters:
The vLOEntry parameter specifies whether conferences start in Listen
•
Only mode (all ordinary participants are muted and can't unmute
themselves).
The vLOEntryEnable parameter specifies whether the subscriber can turn
•
the Listen Only Entry option on or off for future conferences.
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.
Legacy v. 2.32.0 PSPI Functions
91