DTMF events are now published on a channel's stasis_topic. AMI was
authorDavid M. Lee <dlee@digium.com>
Mon, 15 Apr 2013 16:22:03 +0000 (16:22 +0000)
committerDavid M. Lee <dlee@digium.com>
Mon, 15 Apr 2013 16:22:03 +0000 (16:22 +0000)
commit2450722f52401b8537e9c0ffb1192f38b7dd146d
tree2a798888a6601082b150a2eada805b0b82aadaa4
parentc6cf12408edc133c229b323a9039e04f3c12c248
DTMF events are now published on a channel's stasis_topic. AMI was
refactored to use these events rather than producing the events directly
in channel.c. Finally, the code was added to app_stasis to produce
DTMF events on the WebSocket.

The AMI events are completely backward compatible, including sending
events on transmitted DTMF, and sending DTMF start events.

The Stasis-HTTP events are somewhat simplified. Since DTMF start and
DTMF send events are generally less useful, Stasis-HTTP will only send
events on received DTMF end.

(closes issue ASTERISK-21282)
(closes issue ASTERISK-21359)
Review: https://reviewboard.asterisk.org/r/2439

git-svn-id: https://origsvn.digium.com/svn/asterisk/trunk@385734 65c4cc65-6c06-0410-ace0-fbb531ad65f3
apps/app_stasis.c
include/asterisk/cli.h
include/asterisk/strings.h
main/channel.c
main/manager_channels.c