On 15/10/13 18:06, Joshua Colp wrote: > Agreed. > > The only explicit con of this is that it is *not* ChanSpy functionality. > It's cool functionality that you can use to achieve similar results for > some situations. As long as everyone is okay with that... Also agreed. What Matt and you have written sounds entirely sensible to me, and I find it hard to imagine anyone objecting if similar results can be achieved. What I'd like to see is an ARI action or actions to take an existing incoming call from an endpoint, and route it to spying on an existing call with the following scenarios: 1. Spy on the call, listen only. 2. Spy on the call, and talk to a single party - presumably by specifying the channel to talk to in the ARI action. It's then up to API app developers such as us to figure out which channel is the caller and which is the called. 3. Spy on the call, and talk to all parties, i.e. form an ad-hoc conference. We don't have any need to change scenario mid-spy (using DTMF for example), but others might. Likewise, we don't have any need to talk to two or more (but not all) participants in the original call, but others might. -- Alistair Cunningham +1 888 468 3111 +44 20 799 39 799 http://integrics.com/
