Filter
Top Products
ReadiVoice Administration & Maintenance Guide
140 Proprietary & Confidential
the External ID field. If you intend to use any of these fields for recorder setup
information, it's up to you to ensure that they contain numeric data and that
your provisioning process populates the fields properly.
How Conference Recording Works
Figure 5-5 shows an example of
.odprocrc
configuration settings for
conference recording.
Figure 5-5 Example of conference recording settings in the
.odprocrc
file
In a system using the example settings shown, the following sequence occurs
when a subscriber selects the recording option:
1 The subscriber selects the option to record the conference in one of two
ways:
— Entering the touchtone command (default is *2).
— Clicking the Record button in the Moderator.
2 The ReadiVoice system dials the phone number specified by
recorderPhone
. In the example, this is 5551212.
3 The system sends the DTMF tones specified by
recorderSetupString
,
substituting actual DTMF tones for the variables. With the example
configuration shown in Figure 5-5, the system sends (with DTMF digits
replacing the variables described in brackets):
1 (pause) 4 (pause) 5 * [subscriber’s access code] # *
[start time of conference] # #
In this example, the system uses the DTMF sequence 1,,4,,5 to maneuver
through an IVR menu, with pauses between DTMF keys to allow the IVR
platform to process them (each comma represents a 20-millisecond pause).
It sends * and # to delimit the fields and ## to mark the end of the setup
string to the recording device. This is one possible implementation.
4 Conference recording begins.
5 Recording ends when the conference ends or when the recorder
telephone line is disconnected.
[modules]
[bridgeInt]
...
recorderPhone = 5551212
recorderSetupString =
1,,4,,5*{accesscode}#*{confStart}##
...
[]
[]