Filter
Top Products
Configuring the ReadiVoice System
Proprietary & Confidential 127
3 If necessary, update your existing subscriber records with the required
identifiers.
You may want to do this using the Provisioning Stored Procedure
Interface (PSPI). See the ReadiVoice PSPI Reference.
4 As user cnow, open the
.odprocrc
file for editing and, in the
[bridgeInt]
section, configure the
dialOutSetupString
parameter to
meet your requirements (see “Dial-out Setup String Example”).
5 As root, restart the ReadiVoice application (see “Stopping and Restarting
ReadiVoice Processes” on page 111).
6 Make sure that future subscribers will be provisioned properly:
— If you’re using the Dial Out Prefix and Dial Out Postfix fields, make
sure they’re available in the Provisioning interface (see “Setting Up
the Provisioning Interface” on page 60).
— Let your ReadiVoice provisioners know how you want them to define
these two fields when adding or updating a subscriber. The two fields
together must not be more than 24 characters.
— Make sure provisioners know that, to use this feature, subscribers
must have Dial-Out Permission enabled.
Dial-out Setup String Example
To enable the Dial-Out Billing feature, you must add a line such as this to your
.odprocrc
file’s
[bridgeInt]
section:
The example shows the variables specific to Dial-Out Billing, but you can also
use the
recorderSetupString
variables (see Table 5-7 on page 138), such as
{subId}
or
{externId}
. Each comma is a 20-millisecond pause.
The Dial-Out Billing setup string example would out-pulse three values in
succession:
1 The dialed phone number,
{phoneNum}
, followed by a 60-millisecond
pause.
2 The value in the subscriber’s
DialOutPreFix
field,
{dialoutPreFix}
,
followed by another 60-millisecond pause.
3 The value in the subscriber’s
DialOutPostFix
field,
{dialOutPostFix}
.
[bridgeInt]
...
dialOutSetupString = {phoneNum},,,{dialoutPreFix},,,{dialOutPostFix}