rayo/xmpp — pull request #87 by chewi (2014-01-30 14:08:52+00:00)
Title: timers-started event

I am using Sippy Cup to test Adhearsion but I didn't want to rely on sleep to keep things in sync. I therefore used SIP messages as a signalling mechanism instead but still required an event to trigger these messages from. This event needed to fire when the input timers start, hence I created a timers-started event. You can see a working preliminary implementation of this at chewi/FreeSWITCH@f7c56ec4fd.

There was [some discussion](http://irclogger.com/.adhearsion/2014-01-10#1389372272) about exactly what conditions this should fire under and I want to get this cleared up before I start making changes to the spec.

It was suggested that it should only apply to prompt components when barge-in = false but this does not fit my use case. My prompts have barge-in = true but I still find the event useful because even though humans can barge in if they wish, I would rather have Sippy Cup wait until the prompt has completed as that is what humans are more likely to do for this particular service.

I don't believe the event should fire if the timers are to start immediately. This would always be the case for a bare input component as @crienzo says that such components either start their timers straight away or they never do.

The current code is supposed to effectively only fire the event from prompt components, irrespective of barge-in. This is how I think it should work. However, I just tested with barge-in = false, expecting it to work, and it didn't. Seemingly there is no internal start-timers command in this scenario, @crienzo?