ReadiVoice Administration & Maintenance Guide
138 Proprietary & Confidential
6 Verify that the test conference was recorded by listening to the recording.
If the test conference was recorded, continue to the next step. If not,
review the previous steps or call your Polycom Global Services
representative for assistance.
7 Instruct provisioners to turn on Recorder Dial Out for subscribers who
need to be able to record conferences.
Voice Prompts for Conference Recording
The voice prompt files used during the recording process are:
rec_change_failed.wav
rec_conf_full.wav
rec_not_enabled.wav
rec_part_join_reminder
rec_rejoin_reminder.wav
rec_setup_failed.wav
rec_start_prompt.wav
rec_started.wav
rec_stop_prompt.wav
rec_stopped.wav
rec_subs_join_reminder
rec_wait.wav
For the default prompt text and file format requirements, see Appendix A.
Figure A-9 on page 213 shows the call flow.
Recording Configuration Variables in the .odprocrc File
To enable conference recording, the
recorderPhone
and
recorderSetupString
values in the
[modules] [bridgeInt]
section of
.odprocrc
must be specified:
• For
recorderPhone
, specify the telephone number of the recording device
or service.
• For
recorderSetupString
, use valid DTMF keys (0-9, *, and #) and the
variables listed in Table 5-7 to define a setup string that will uniquely
identify each recording of each conference.
See the example shown in Figure 5-5 on page 140 for one implementation.
Table 5-7 Variables you can use in recorderSetupString
Variable Description
{subId}
Subscriber ID.
{externId}
Contents of External ID field from SUBSCRIBERINFO table.
{ccnum}
Credit card number from BILLINGINFO table.