CVP VVB
Useful Commands
Adding / deleting hostnames
show vvb host-to-ip utils vvb add host-to-ip mediaserver 123.123.123.123 utils vvb delete host-to-ip mediaserver 123.123.123.123
Show / Clear Cache
show vvb cache cache_entries set vvb cache stale_cache_entries
Show Call Summary
show vvb call active voice summary
Change SIP Control protocol from the default of TCP to UDP (needed for Nuance ASR/TTS)
show vvb sip controlTransport show vvb sip optionsTransport set vvb sip controlTransport set vvb sip optionsTransport
Logging Commands
Virtual Agent Logging / Cloud Connect
file tail activelog speechserver/logs/SpeechServer/SpeechServer.log
Real Time VXML Tracing
Find out which is the active log
file view activelog uccx/log/MIVR/Cisco001MIVR.index
View the log in real time:
file tail activelog uccx/log/MIVR/Cisco001MIVRxxx.log
Gather VXML Logs
(Requires an SFTP server)
file get activelog uccx/log/MIVR/Cisco001MIVR*
Or this should refine it by date
file get activelog uccx/log/MIVR/Cisco001MIVR* recurs reltime days 2
Gather Packet Capture Logs
file get activelog /platform/cli/<capture>.cap
Note: Filename is case sensative and always ends with lower case “.cap”
Example:
utils network capture size ALL count 100000 file MyFileName
file get activelog /platform/cli/MyFileName.cap
Create account for VXML Developers
set account name <username>
(Select - Advanced - Level 1)
set password change-at-login disable <username>
To view VXML in VVB trace
- navigate to Trace Configuration on the VVB Web OS Platform.
- SS_VB should be enabled for 'Debugging' by default.
- Check XDebugging1 and you will be able to view the VXML in your Trace files.
- Cisco VVB Developers also request for XDebugging2 to be enabled.
My Bugs
fetchaudio media file is not getting cleared from the PromptPlayer
https://bst.cloudapps.cisco.com/bugsearch/bug/CSCvi25666/
Fetchaudio timer does not start from the element where it is configured
https://bst.cloudapps.cisco.com/bugsearch/bug/CSCvi43768
VXML session is not getting released completely
https://bst.cloudapps.cisco.com/bugsearch/bug/CSCvi43753