Filter
Top Products
ReadiVoice Administration & Maintenance Guide
170 Proprietary & Confidential
For example, if the system is Non-routed Private, and the bridge receives
the digits 1111, it plays
1111helo_inbound.wav
to the caller if the file
exists. Another caller, whose DNIS digits are 2222, would hear
2222helo_inbound.wav
if the file existed.
3 If the DNIS-specific
.wav
file doesn’t exist, the bridge plays the
corresponding non-customized greeting (
helo_inbound.wav
, for
example) in
/rahome/bridge/sound/1/adpcm
or
/rahome/bridge/sound/1/g711
(depending on bridge type).
To implement this feature:
1 Create the custom messages you want to use in the required format, and
add the DNIS digits to the beginning of each standard file name.
See Appendix A for descriptions of the customizable files (listed above),
including the wording of the default versions. The appendix also describes
the bridge-specific file formats.
To use the same greeting (or other customized message) for several
DNISes or access numbers, create multiple copies of the same
.wav
files,
each named with its DNIS.
2 Place the new appropriately-named files into the correct format-specific
subdirectory (
adpcm
or
g711
) of the
/rahome/bridge/sound/greetings/
directory.
ReadiVoice uses the default greeting-related files (from the appropriate
subdirectory of
/rahome/bridge/sound/1
) for any DNIS that doesn’t
have its own
.wav
files. To use your own default greetings, replace the
supplied default greeting files with ones of the same names containing the
messages you want.
3 Create the DNIS-specific symbolic links (see “About Initial Greetings” on
page 181) by running the
tnl_mkln
script:
a Log into the CACS as root and, in an XTerm window, enter
tcsh
.
b Change to the
/rahome/bin
directory.
c Run the make link script by entering
tnl_mkln
.
d Reboot the bridge(s).
4 Inform provisioners of the system of the specific access numbers that
you’ve associated with custom welcome messages.
If you’ve created corresponding custom prompt sets, give provisioners
this information as well. See “Working with Prompt Sets” on page 166 for
more information.
Caution!
The custom file names must match exactly the DNIS digits delivered to the bridge.
Typically, on a non-routed system, a DNIS is a four-digit number. If your system
receives more DNIS digits, however, the file names must include all the digits.