Cisco Cisco Unified Customer Voice Portal 11.0(1) User Guide

Page of 48
C
USTOM 
C
ONTENT
 
 
S
AY 
I
S
MART 
S
PECIFICATIONS 
 
 
 
FOR 
C
ISCO 
U
NIFIED 
C
USTOMER 
V
OICE 
P
ORTAL 
R
ELEASE 
4.0(1) 
 
 
 
 
10
 
Name  
(Display Name) 
Input Format 
Depends On 
 
Description 
(Filename(s) Only)
 
complex 
resultset 
siscontent 
array 
the audio file content of the data, even if it contains TTS 
content. For the 
simple
 and 
array
 input formats, this 
output format indicates that the data contains audio files 
only. 
Filesets 
Name  
(Display Name) 
Output Format  
Depends On 
 
Description 
none
 
(No Fileset)
 
standard 
standard_no_ssml 
tts 
tts_no_ssml 
files
 
This plugin allows the developer to specify any amount 
of audio files, the names of which are determined at 
runtime. As a result, there is no need for a fileset. 
Every Say It Smart plugin, though, requires at least one 
fileset, so this one is simply named “none”. 
Audio Files 
None. The audio files will be determined by the application designer and developer. 
Examples 
Data: myGreeting.wav 
 
Data: 
This is some text to speech 
Input Format: 
simple  
Input Format: 
simple 
Output Format: 
files  
Output Format:
tts_no_ssml 
Fileset: 
none  
Fileset: 
none 
Playback: myGreeting.wav 
(with 
no TTS backup) 
  Playback: 
“This is some text to speech” 
(this is read as TTS) 
 
 
 
 
 
Data: a.wav:::backup 
for 
a|||b.wav:::backup for b 
  Data: a.wav:::|||:::some 
<break 
size=”large”> tts 
Input Format: 
complex  
Input Format: 
complex 
Output Format: 
standard_no_ssml  
Output Format:
standard 
Fileset: 
none  
Fileset: 
none 
Playback: a.wav 
(with 
TTS 
backup “backup for a”) 
b.wav (with TTS 
backup “backup for b”) 
  Playback: 
a.wav (with no TTS backup) 
“some “ <large pause> “ tts”  
(no audio file played, SSML 
tags included in VoiceXML) 
There are no examples of input formats that take Java objects as the data must be created by a 
developer in custom Java code.