VoiceXML Forum Community Message Board


Post New Topic  Post A Reply
my profile | register | search | faq | forum home
  next oldest topic   next newest topic
» VoiceXML Forum Community Message Board   » Newbies   » building a statistic tool for voicexml

 - UBBFriend: Email this page to someone!    
Author Topic: building a statistic tool for voicexml
abchilla
Junior Member
Member # 3704

Rate Member
Icon 1 posted November 23, 2006 11:09 AM      Profile for abchilla   Email abchilla   Send New Private Message       Edit/Delete Post   Reply With Quote 
Dear group,

i need some guidance. I am trying to build a statistic tool for a voicexml application. The aim is to save every event in a database in order build a statistic for a call, like how long was the call, how long did the user stuck into a dialogue. and many more things. as i wanted to build this application like a component i would like to know from you how would you implement this. i was thinking of calling a subdialog every time a user input is done. in this subdialog i would go to my server and store the event in a database.

but i think this would mean, that i had to code in the dialogue. do you think there is a better way of solving this? how would you do this? the aim is to use the statistic on applications whenever i want to do.

thanks in advance

Posts: 9 | Registered: Aug 2006  |  IP: Logged
DrBoB
Junior Member
Member # 3775

Rate Member
Icon 1 posted November 28, 2006 06:04 AM      Profile for DrBoB   Author's Homepage   Email DrBoB   Send New Private Message       Edit/Delete Post   Reply With Quote 
Depending on how complicated your application is, you can divide the call-flow up into single dialog states. Each dialog state is a single answer and reply - doesn't matter if it's ASR or DTMF.

The you decide on a fixed set of global variables that cover all the elements that you want to evaluate - number of times help was said, number of noinputs, number of nomatches, duration in the state, whether they exited here, whether they returned to the main menu, etc. Then at the end of every state you go back to the server to get the next dialog state. You send all the relevant data with the request and your application can log it in the DB.

Obviously you need a good connection between VoiceXML server and the application server - otherwise there could be latency in the dialog. And this isn't too far removed from what you were thinking of doing anyway - though here the code on the server side can be reused for other applications.

The other way of doing this is to log to the VoiceXML server log. You can add information to this. Then you analyse the logs off-line. The "catch" here is that you will probably want to use much of the VoiceXML server's own logging - which is usually proprietory. If you're going to stick to a single platform then this isn't such an issue.

[ November 28, 2006, 06:05 AM: Message edited by: DrBoB ]

--------------------
Pusing VoiceXML to the masses - www.voice-push.com

Posts: 9 | Registered: Sep 2006  |  IP: Logged


All times are Eastern  
Post New Topic  Post A Reply Close Topic    Move Topic    Delete Topic next oldest topic   next newest topic
 - Printer-friendly view of this topic
Hop To:

Contact Us | VoiceXML Forum



Powered by Infopop Corporation
UBB.classicTM 6.3.1.2