Sophie

Sophie

distrib > Mandriva > 2008.1 > i586 > media > contrib-updates > by-pkgid > c7095aefea7b97fbd2a596dcbfb9d481 > files > 244

asterisk-docs-1.4.26.1-1mdv2008.1.i586.rpm

<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html xmlns="http://www.w3.org/1999/xhtml"><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /><title>mgcp.conf</title><link rel="stylesheet" href="styles.css" type="text/css" /><meta name="generator" content="DocBook XSL Stylesheets V1.69.1" /><link rel="start" href="index.html" title="Asterisk™: The Future of Telephony" /><link rel="up" href="asterisk-APP-D.html" title="Appendix D. Configuration Files" /><link rel="prev" href="asterisk-APP-D-SECT-26.html" title="meetme.conf" /><link rel="next" href="asterisk-APP-D-SECT-28.html" title="modem.conf" /></head><body><div class="navheader"><table width="100%" summary="Navigation header"><tr><th colspan="3" align="center">mgcp.conf</th></tr><tr><td width="20%" align="left"><a accesskey="p" href="asterisk-APP-D-SECT-26.html">Prev</a> </td><th width="60%" align="center">Appendix D. Configuration Files</th><td width="20%" align="right"> <a accesskey="n" href="asterisk-APP-D-SECT-28.html">Next</a></td></tr></table><hr /></div><div class="sect1" lang="en" xml:lang="en"><div class="titlepage"><div><div><h2 class="title" style="clear: both"><a id="asterisk-APP-D-SECT-27"></a>mgcp.conf</h2></div></div></div><p><a id="I_indexterm_tt2654" class="indexterm"></a>The Media Gateway Control Protocol (MGCP) has only primitive
    support in Asterisk. This is likely due to the fact that SIP has stolen
    the limelight from every other VoIP protocol (except IAX, of course).
    Because of this, you should attempt to use Asterisk’s MCGP channel in a
    production environment only if you are prepared to perform extensive
    testing, are willing to pay to have features and patches implemented
    within your time frames, and have in-house expertise with the
    protocol.</p><p>Having said that, we are not prepared to pronounce MGCP dead. SIP is
    not yet the panacea it has been touted as, and MGCP has proven itself to
    be very useful in carrier backbone environments. Many believe MGCP will
    fill a niche or void that has not yet been discovered, and we remain
    interested in it.</p></div><div class="navfooter"><hr /><table width="100%" summary="Navigation footer"><tr><td width="40%" align="left"><a accesskey="p" href="asterisk-APP-D-SECT-26.html">Prev</a> </td><td width="20%" align="center"><a accesskey="u" href="asterisk-APP-D.html">Up</a></td><td width="40%" align="right"> <a accesskey="n" href="asterisk-APP-D-SECT-28.html">Next</a></td></tr><tr><td width="40%" align="left" valign="top">meetme.conf </td><td width="20%" align="center"><a accesskey="h" href="index.html">Home</a></td><td width="40%" align="right" valign="top"> modem.conf</td></tr></table></div><div xmlns="" id="svn-footer"><hr /><p>You are reading <em>Asterisk: The Future of Telephony</em> (2nd Edition for Asterisk 1.4), by Jim van Meggelen, Jared Smith, and Leif Madsen.<br />
       This work is licensed under the <a href="http://creativecommons.org/licenses/by-nc-nd/3.0/">Creative Commons Attribution-Noncommercial-No Derivative Works License v3.0</a>.<br />
       To submit comments, corrections, or other contributions to the text, please visit <a href="http://oreilly.com/catalog/9780596510480/">http://www.oreilly.com/</a>.</p></div></body></html>