Cisco Cisco Unified Customer Voice Portal 10.5(1) 사용자 가이드
C
HAPTER
2:
B
UILDER FOR
V
OICE
XML
S
TUDIO
V
OICE
XML
S
TUDIO
U
SER
G
UIDE
FOR
C
ISCO
U
NIFIED
C
USTOMER
V
OICE
P
ORTAL
38
Suspended Message. This is a TTS message that will be played to the caller when the
application is suspended. This message typically says that the service is temporarily
down and asks the caller to call back. This setting is required.
down and asks the caller to call back. This setting is required.
Suspended Audio URI. This is a URI to a pre-recorded audio file containing the
message to play when the application is suspended. The TTS message specified in the
Suspended Message setting above is played only when the audio file specified here is not
found or corrupted. By default, Cisco Unified CVP VoiceXML Studio references an
audio file provided by Cisco.
Suspended Message setting above is played only when the audio file specified here is not
found or corrupted. By default, Cisco Unified CVP VoiceXML Studio references an
audio file provided by Cisco.
Initial On-Hold Audio URI / Main On-Hold Audio URI. Each simultaneous call to
Cisco Unified CVP VoiceXML Server takes up a Cisco Unified CVP VoiceXML Server
port. The license purchased from Cisco specifies how many ports the system can support.
If a call is received when all ports are taken, Cisco Unified CVP VoiceXML Server puts
the caller on hold, playing the initial designer-specified pre-recorded audio referenced in
the setting named Initial On-Hold Audio URI. When done playing, Cisco Unified CVP
VoiceXML Server checks if a port is available. If not, it will play the designer-specified
pre-recorded audio referenced in the setting named Main On-Hold Audio URI followed
by another check. The cycle continues by repeatedly playing the main on hold audio and
checking for a port. Once a port is available, the caller starts interacting with the
application. The initial on-hold message is intended to be a greeting and a notice to hold.
The main on-hold message is intended to be a "filler" message that is suitable for
repeating multiple times. The length of these messages determines the frequency which
the server checks for an available port. By default, Cisco Unified CVP VoiceXML Studio
references audio files provided by Cisco that contain a 30-second pause within it to
lengthen the amount of time it takes between checks.
port. The license purchased from Cisco specifies how many ports the system can support.
If a call is received when all ports are taken, Cisco Unified CVP VoiceXML Server puts
the caller on hold, playing the initial designer-specified pre-recorded audio referenced in
the setting named Initial On-Hold Audio URI. When done playing, Cisco Unified CVP
VoiceXML Server checks if a port is available. If not, it will play the designer-specified
pre-recorded audio referenced in the setting named Main On-Hold Audio URI followed
by another check. The cycle continues by repeatedly playing the main on hold audio and
checking for a port. Once a port is available, the caller starts interacting with the
application. The initial on-hold message is intended to be a greeting and a notice to hold.
The main on-hold message is intended to be a "filler" message that is suitable for
repeating multiple times. The length of these messages determines the frequency which
the server checks for an available port. By default, Cisco Unified CVP VoiceXML Studio
references audio files provided by Cisco that contain a 30-second pause within it to
lengthen the amount of time it takes between checks.
Default Audio Path URI. This setting contains a partial URI to a path containing the
audio content for this voice application. If set, the designer need only provide the audio
file name while building the application, knowing that this path will be prepended. If the
audio for this application is stored in multiple areas this field should be left blank. In this
case, the developer will have to provide the full URI for each audio file used by the
application. The default audio path can save a lot of time when moving applications
across disparate systems since only the default audio path need change rather than the
URI for each audio file in the application.
file name while building the application, knowing that this path will be prepended. If the
audio for this application is stored in multiple areas this field should be left blank. In this
case, the developer will have to provide the full URI for each audio file used by the
application. The default audio path can save a lot of time when moving applications
across disparate systems since only the default audio path need change rather than the
URI for each audio file in the application.