Polycom 3725-70003-009F Manuale Utente
Customizing & Branding Your ReadiVoice System
Proprietary & Confidential
169
Deleting the prompt set from within System Administration only makes it
unavailable to the ReadiVoice system. It doesn’t delete the .wav files from the
unavailable to the ReadiVoice system. It doesn’t delete the .wav files from the
CACS server or remove the directory that contains them.
Customizing Greetings and Related Messages
In a ReadiVoice non-routed system and a ReadiVoice IP system, the bridge
plays the initial greeting. You can configure ReadiVoice to use up to 50 custom
greetings, so that it selects the appropriate greeting based on the DNIS (dialed
number identification service) digits that the network delivers to the bridge.
Custom welcome messages aren’t available in a routed (INCR) system because
the network that routes calls to the bridges plays the initial greeting (welcome
message) that callers hear. The carrier stores and plays this message.
The DNIS-specific initial greeting files you need depend on your system
configuration:
• If your system is Non-routed Private, create DNIS-specific versions of the
plays the initial greeting. You can configure ReadiVoice to use up to 50 custom
greetings, so that it selects the appropriate greeting based on the DNIS (dialed
number identification service) digits that the network delivers to the bridge.
Custom welcome messages aren’t available in a routed (INCR) system because
the network that routes calls to the bridges plays the initial greeting (welcome
message) that callers hear. The carrier stores and plays this message.
The DNIS-specific initial greeting files you need depend on your system
configuration:
• If your system is Non-routed Private, create DNIS-specific versions of the
helo_inbound.wav file.
• If your system uses only the Traditional Shared call flow, create
DNIS-specific versions of the cr_access_code_prompt.wav file.
• If your system also uses the Two-Password Shared call flow, create
DNIS-specific versions of the pw_prompt.wav file.
When you run the tnl_mkln script, it creates the DNIS-specific symbolic links
for the custom greeting files you created. See
for the custom greeting files you created. See
page 181 for a description of how symbolic links are used for greetings and
what the tnl_mkln script does.
In addition to the initial greeting, several related prompts can also be
customized based on DNIS. The DNIS-customizable files are:
what the tnl_mkln script does.
In addition to the initial greeting, several related prompts can also be
customized based on DNIS. The DNIS-customizable files are:
This feature is called Welcome on DNIS, and it works as follows:
1
During the call-setup protocol, the network delivers the call’s DNIS
number to the bridge.
number to the bridge.
2
The bridge looks in /rahome/bridge/sound/greetings/adpcm or
/rahome/bridge/sound/greetings/g711 (depending on bridge type)
for a .wav file that starts with the DNIS digits received and matches the
for a .wav file that starts with the DNIS digits received and matches the
needed event.
cf_call_not_completed
cf_conf_full_disconnect.wav
cr_access_code_collection_failure.wav
cr_access_code_good.wav
cr_access_code_prompt.wav
cr_access_code_wrong.wav
cf_conf_full_disconnect.wav
cr_access_code_collection_failure.wav
cr_access_code_good.wav
cr_access_code_prompt.wav
cr_access_code_wrong.wav
cr_access_code_wrong_.wav
_cr_access_code_wrong.wav
cr_conf_ending.wav
helo_inbound.wav
pw_prompt.wav
_cr_access_code_wrong.wav
cr_conf_ending.wav
helo_inbound.wav
pw_prompt.wav