tropo in gthe real world: handling answering machines?

Is delivering a message to a human or answering machine feasible on Tropo for Webapi? or Hosted? Both? Neither? I read the blog entry on handling answering machines (sort of) on the hosted scripts: http://blog.tropo.com/2010/12/17/human-vs-answering-machine-detection/ Even for hosted scripts, the "solution" in that blog is kind of silly... it does not address the issue of an app knowing WHEN the answering machine is DONE talking so you can leave your message. The ISSUE is getting the message to the human (or answering machine). What can we do with a webapi (or hosted) app? Thanks!


Please sign in to leave a comment.