Legacy v. 2.13.0/2.30.0 PSPI Functions
Proprietary & Confidential
133
AddSubAndAN_v2130()
Stored procedure for adding a new subscriber and new access number(s) to the
database at the same time. You can specify up to three access numbers for a
new subscriber, even if those access numbers don’t currently exist in the
database.
First, the procedure attempts to add the first access number to the database. If
this access number already exists, the procedure simply skips the add process
and continues. Next, the procedure adds the subscriber to the database and
assigns the first access number to the new subscriber. If you specified
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
, but has three additional
parameters:
•
The
vPartPlayCount
flag, added in
. If it’s set to
1
,
participants entering a conference hear a message telling them the number
of people (including themselves) in conference.
•
The
vDialoutPrefix
parameter specifies a number to be dialed before the
telephone number when dialing out.
•
The
vDialoutPostFix
parameter specifies a number to be dialed after the
telephone number when dialing out.
The prefix and postfix parameters accommodate the Dial-Out Billing (UDO)
configuration, described in the
ReadiVoice Administration & Maintenance Guide
.
Using this procedure, or its siblings
and
, 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.
Содержание ReadiVoice
Страница 1: ...ReadiVoice PSPI Reference ...
Страница 134: ...ReadiVoice PSPI Reference 126 Proprietary Confidential ...
Страница 268: ...ReadiVoice PSPI Reference 260 Proprietary Confidential ...