[asterisk-app-dev] WebSocket Stasis Control Best Practice

[Joshua Colp]

Krandon wrote:
> Just to reignite this whole thread. We've had great success with Stasis
> so far. We have implemented a (imho better) AMD using TALK_DETECT and
> the ARI events. When using this, it seems like calling /play multiple
> times will just queue up the audio files. This is probably the best use
> case and most common implementation. However, if half-way through our
> third audio file we realize that we've been speaking to a machine this
> whole time and we want to start for the beginning - we thought we would
> use DELETE /playbacks/{playbackId}. If we do that, however, and then
> subsequently try to play audio on the channel (even though the call is
> still connected and in the Stasis app) we get a Channel not found. Is
> this the intended use or even a good use?

Stopping a playback, or multiple playbacks in sequence, like that 
shouldn't result in you being unable to do things on the channel. Do you 
have the output of what you are invoking and the log from Asterisk? It 
may be a bug.

-- 
Joshua Colp
Digium, Inc. | Senior Software Developer
445 Jan Davis Drive NW - Huntsville, AL 35806 - US
Check us out at: www.digium.com & www.asterisk.org