Doxygen updates

git-svn-id: https://origsvn.digium.com/svn/asterisk/trunk@48277 65c4cc65-6c06-0410-ace0-fbb531ad65f3
This commit is contained in:
Olle Johansson
2006-12-05 20:39:13 +00:00
parent 87f81679ee
commit fe53552f41
3 changed files with 82 additions and 10 deletions

View File

@@ -81,8 +81,39 @@
\arg translate.h - Transcoding support functions
\arg \ref channel_drivers - Implemented channel drivers
\arg \ref Def_Frame Asterisk Multimedia Frames
\arg \ref Def_Bridge
*/
/*! \page Def_Bridge Asterisk Channel Bridges
In Asterisk, there's several media bridges.
The Core bridge handles two channels (a "phone call") and bridge
them together.
The conference bridge (meetme) handles several channels simultaneosly
with the support of an external timer (zaptel timer). This is used
not only by the Conference application (meetme) but also by the
page application and the SLA system introduced in 1.4.
The conference bridge does not handle video.
When two channels of the same type connect, the channel driver
or the media subsystem used by the channel driver (i.e. RTP)
can create a native bridge without sending media through the
core.
Native briding can be disabled by a number of reasons,
like DTMF being needed by the core or codecs being incompatible
so a transcoding module is needed.
References:
- ast_channel_early_bridge()
- ast_channel_bridge()
- app_meetme.c
- \ref AstRTPbridge
- ast_rtp_bridge()
- \ref Def_Channel
*/
/*! \page AstFileDesc File descriptors
Asterisk File descriptors are connected to each channel (see \ref Def_Channel)