Filter channels used as internal mechanisms

This adds new flags to the channel tech properties that flag it as
different types of implementation detail used exclusively to provide a
feature. Examples of channels that would have these flags include the
announcement and recording channels used by confbridge which are the
only two marked as such by this patch.

Review: https://reviewboard.asterisk.org/r/2633/
(closes issue ASTERISK-21873)


git-svn-id: https://origsvn.digium.com/svn/asterisk/trunk@394808 65c4cc65-6c06-0410-ace0-fbb531ad65f3
This commit is contained in:
Kinsey Moore
2013-07-19 19:23:39 +00:00
parent 0b83761f9a
commit 5a8f32703c
11 changed files with 90 additions and 11 deletions

View File

@@ -854,15 +854,25 @@ struct ast_channel;
/*! \brief ast_channel_tech Properties */
enum {
/*!
* \brief Channels have this property if they can accept input with jitter;
* \brief Channels have this property if they can accept input with jitter;
* i.e. most VoIP channels
*/
AST_CHAN_TP_WANTSJITTER = (1 << 0),
/*!
* \brief Channels have this property if they can create jitter;
* \brief Channels have this property if they can create jitter;
* i.e. most VoIP channels
*/
AST_CHAN_TP_CREATESJITTER = (1 << 1),
/*!
* \brief Channels have this property if they are an implementation detail
* used for announcing messages; i.e. to a bridge
*/
AST_CHAN_TP_ANNOUNCER = (1 << 2),
/*!
* \brief Channels have this property if they are an implementation detail
* used for recording audio; i.e. from a bridge
*/
AST_CHAN_TP_RECORDER = (1 << 3),
};
/*! \brief ast_channel flags */