Cisco Cisco Unified Customer Voice Portal 11.0(1) User Guide
C
HAPTER
2:
V
OICE
XML
S
ERVER
C
OMPONENTS IN
D
ETAIL
V
OICE
XML
S
ERVER
U
SER
G
UIDE
FOR
C
ISCO
U
NIFIED
C
USTOMER
V
OICE
P
ORTAL
R
ELEASE
4.0(1)
30
date to compare.
Field
can be hour_of_day (which returns an integer from 0 to 23), minute
(which returns an integer from 0 to 59), day_of_month (which returns an integer from 1 to 31),
month (which returns an integer from 1 to 12), day_of_week (which returns an integer from 1 to
7 where 1 is Sunday), or year (which returns the 4 digit year). The children tags are used to turn
on various criteria to add to the search. The different search criteria are:
month (which returns an integer from 1 to 12), day_of_week (which returns an integer from 1 to
7 where 1 is Sunday), or year (which returns the 4 digit year). The children tags are used to turn
on various criteria to add to the search. The different search criteria are:
caller
– If this tag appears, the search looks for calls made by the current caller only. If it
does not appear, it will search all calls made by all callers. Note that if the call was not
associated with a specific UID, an error will occur if this tag is used.
associated with a specific UID, an error will occur if this tag is used.
ani
– If this tag appears, the search looks for calls made by the ANI specified in the
value
attribute. If the
value
attribute is not included, the ANI of the current caller is used.
start
– If this tag appears, the search looks for calls whose start date/time are between two
times specified by successive
<constant_date_time>
children tags. The attributes of
<constant_date_time>
define the specific date to use. The
month
attribute must be an
integer from 1 to 12. The
day_of_month
attribute must be an integer from 1 to 31. The
year
attribute must be a four digit integer. The
hour_of_day
attribute must be an integer from 0 to
23. The
minute
attribute must be an integer from 0 to 59. The
second
attribute must be an
integer from 0 to 59.
end
– If this tag appears, the search looks for calls whose end date/time are between two
times specified by successive
<constant_date_time>
children tags. See
<start>
above for
the description of the
<constant_date_time>
tag.
flag
– If this tag appears, the search looks for calls where a flag with the name given in the
name
attribute was triggered.
XML Decision Example #1
An application named “Example1” would like to play “Welcome back” for callers who have
previously called this application. The users are identified by their ANI (this application uses the
user management database only for its history tracking). A decision element named
“CalledBefore” would be needed which had two rules, one for those who the application
recognizes and one for the rest (this is being done rather than using the default exit state for
demonstration purposes). In English, the rules are:
previously called this application. The users are identified by their ANI (this application uses the
user management database only for its history tracking). A decision element named
“CalledBefore” would be needed which had two rules, one for those who the application
recognizes and one for the rest (this is being done rather than using the default exit state for
demonstration purposes). In English, the rules are:
Rule Expression
Exit State
1
The caller has called from this ANI before
say_welcome_back
2
The caller has not called from this ANI before
say_welcome
The Unified CVP decision element XML file would be named “CalledBefore” and be saved in
AUDIUM_HOME/applications/Example1/data/misc.
The XML content will be: