<html>
<head>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=us-ascii">
<meta name=Generator content="Microsoft Word 11 (filtered)">
<style>
<!--
/* Font Definitions */
@font-face
{font-family:Tahoma;
panose-1:2 11 6 4 3 5 4 4 2 4;}
@font-face
{font-family:"Z\@R44A\.tmp";}
@font-face
{font-family:"Z\@R44A\.tmpOOEnc";}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:Tahoma;}
a:link, span.MsoHyperlink
{color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{color:purple;
text-decoration:underline;}
span.emailstyle17
{font-family:Arial;
color:windowtext;}
span.EmailStyle18
{font-family:Arial;
color:navy;}
span.EmailStyle19
{font-family:Arial;
color:navy;}
span.EmailStyle20
{font-family:Arial;
color:navy;}
@page Section1
{size:595.3pt 841.9pt;
margin:1.0in 1.25in 1.0in 1.25in;}
div.Section1
{page:Section1;}
/* List Definitions */
ol
{margin-bottom:0in;}
ul
{margin-bottom:0in;}
-->
</style>
</head>
<body lang=EN-GB link=blue vlink=purple>
<div class=Section1>
<p class=MsoNormal><font size=2 color=navy face=Arial><span style='font-size:
10.0pt;font-family:Arial;color:navy'>Thanks for that Matt, at the moment we
only have one MGCP gateway and that is the one connected to our old PBX.</span></font></p>
<p class=MsoNormal><font size=2 color=navy face=Arial><span style='font-size:
10.0pt;font-family:Arial;color:navy'> </span></font></p>
<div>
<div class=MsoNormal align=center style='text-align:center'><font size=3
face="Times New Roman"><span lang=EN-US style='font-size:12.0pt;font-family:
"Times New Roman"'>
<hr size=2 width="100%" align=center tabindex=-1>
</span></font></div>
<p class=MsoNormal><b><font size=2 face=Tahoma><span lang=EN-US
style='font-size:10.0pt;font-weight:bold'>From:</span></font></b><font size=2><span
lang=EN-US style='font-size:10.0pt'> Matt Slaga (US) [mailto:Matt.Slaga@us.didata.com]
<br>
<b><span style='font-weight:bold'>Sent:</span></b> Wednesday, August 30, 2006
5:00 PM<br>
<b><span style='font-weight:bold'>To:</span></b> Joe Pollere (US); Nick Kassel;
cisco-voip@puck.nether.net<br>
<b><span style='font-weight:bold'>Subject:</span></b> RE: [cisco-voip] MGCP vs
H323</span></font></p>
</div>
<p class=MsoNormal><font size=3 face=Tahoma><span style='font-size:12.0pt'> </span></font></p>
<p class=MsoNormal><font size=2 color=navy face=Arial><span lang=EN-US
style='font-size:10.0pt;font-family:Arial;color:navy'>At this point, MGCP is
able to provide name/number display on a PRI (if provided from the carrier)
whereas this is not yet possible in H323.</span></font></p>
<p class=MsoNormal><font size=2 color=navy face=Arial><span lang=EN-US
style='font-size:10.0pt;font-family:Arial;color:navy'> </span></font></p>
<p class=MsoNormal><font size=2 color=navy face=Arial><span lang=EN-US
style='font-size:10.0pt;font-family:Arial;color:navy'>I have started to hear
some rumblings within Cisco about MGCP being slowly phased out and eventually
being replaced with SIP and/or H323. Sounds about right since Cisco has
been shoving MGCP down everyone’s throat for the past three years that
they would want to keep this down to a rumbling.</span></font></p>
<p class=MsoNormal><font size=2 color=navy face=Arial><span lang=EN-US
style='font-size:10.0pt;font-family:Arial;color:navy'> </span></font></p>
<p class=MsoNormal><font size=2 color=navy face=Arial><span lang=EN-US
style='font-size:10.0pt;font-family:Arial;color:navy'>Personally, I would only
use MGCP when interconnecting with a PBX during a migration to keep from having
thousands of dial peers. Or, if I needed name/number display on a PRI.</span></font></p>
<p class=MsoNormal><font size=2 color=navy face=Arial><span lang=EN-US
style='font-size:10.0pt;font-family:Arial;color:navy'> </span></font></p>
<p class=MsoNormal><font size=2 color=navy face=Arial><span lang=EN-US
style='font-size:10.0pt;font-family:Arial;color:navy'>Funny thing is (and this
may be fixed now), but with FXO-M1s the only way to get name/number display was
with H323. MGCP couldn’t do it. Sounds kind of backwards that
it’s just the opposite with a PRI</span></font></p>
<p class=MsoNormal><font size=2 color=navy face=Arial><span lang=EN-US
style='font-size:10.0pt;font-family:Arial;color:navy'> </span></font></p>
<p class=MsoNormal><font size=2 color=navy face=Arial><span lang=EN-US
style='font-size:10.0pt;font-family:Arial;color:navy'> </span></font></p>
<p class=MsoNormal><font size=2 color=navy face=Arial><span lang=EN-US
style='font-size:10.0pt;font-family:Arial;color:navy'> </span></font></p>
<p class=MsoNormal><font size=2 color=navy face=Arial><span lang=EN-US
style='font-size:10.0pt;font-family:Arial;color:navy'> </span></font></p>
<div>
<div class=MsoNormal align=center style='text-align:center'><font size=3
face="Times New Roman"><span lang=EN-US style='font-size:12.0pt;font-family:
"Times New Roman"'>
<hr size=2 width="100%" align=center tabindex=-1>
</span></font></div>
<p class=MsoNormal><b><font size=2 face=Tahoma><span lang=EN-US
style='font-size:10.0pt;font-weight:bold'>From:</span></font></b><font size=2><span
lang=EN-US style='font-size:10.0pt'> cisco-voip-bounces@puck.nether.net
[mailto:cisco-voip-bounces@puck.nether.net] <b><span style='font-weight:bold'>On
Behalf Of </span></b>Joe Pollere (US)<br>
<b><span style='font-weight:bold'>Sent:</span></b> Wednesday, August 30, 2006
10:51 AM<br>
<b><span style='font-weight:bold'>To:</span></b> Nick Kassel;
cisco-voip@puck.nether.net<br>
<b><span style='font-weight:bold'>Subject:</span></b> Re: [cisco-voip] MGCP vs
H323</span></font></p>
</div>
<p class=MsoNormal><font size=3 face=Tahoma><span lang=EN-US style='font-size:
12.0pt'> </span></font></p>
<p class=MsoNormal style='text-autospace:none'><font size=2 face="Z@R44A.tmp"><span
lang=EN-US style='font-size:11.0pt;font-family:"Z\@R44A\.tmp"'>Nick,</span></font></p>
<p class=MsoNormal style='text-autospace:none'><font size=2 face="Z@R44A.tmp"><span
lang=EN-US style='font-size:11.0pt;font-family:"Z\@R44A\.tmp"'> </span></font></p>
<p class=MsoNormal style='text-autospace:none'><font size=2 face="Z@R44A.tmp"><span
lang=EN-US style='font-size:11.0pt;font-family:"Z\@R44A\.tmp"'>This is from the
GWGK course book:</span></font></p>
<p class=MsoNormal style='text-autospace:none'><b><font size=2 face="Z@R44A.tmp"><span
lang=EN-US style='font-size:11.0pt;font-family:"Z\@R44A\.tmp";font-weight:bold'> </span></font></b></p>
<p class=MsoNormal style='text-autospace:none'><b><font size=2 face="Z@R44A.tmp"><span
lang=EN-US style='font-size:11.0pt;font-family:"Z\@R44A\.tmp";font-weight:bold'>Using
H.323 as the call control protocol to a gateway has the following advantages:</span></font></b></p>
<p class=MsoNormal style='text-autospace:none'><font size=2 face="Z@R44A.tmp"><span
lang=EN-US style='font-size:11.0pt;font-family:"Z\@R44A\.tmp"'> </span></font></p>
<ul style='margin-top:0in' type=disc>
<li class=MsoNormal style='text-autospace:none'><font size=2 face="Z@R44A.tmp"><span
lang=EN-US style='font-size:11.0pt;font-family:"Z\@R44A\.tmp"'>H.323
provides integrated access. Data and voice channels can be placed on the
same T1.</span></font></li>
</ul>
<p class=MsoNormal style='margin-left:.25in;text-autospace:none'><font size=2
face="Z@R44A.tmp"><span lang=EN-US style='font-size:11.0pt;font-family:"Z\@R44A\.tmp"'>For
example, for a service provider like AT&T, FR and PRI can be placed on the
same T1.</span></font></p>
<ul style='margin-top:0in' type=disc>
<li class=MsoNormal style='text-autospace:none'><font size=2 face="Z@R44A.tmp"><span
lang=EN-US style='font-size:11.0pt;font-family:"Z\@R44A\.tmp"'>H.323
provides support for fractional PRI.</span></font></li>
<li class=MsoNormal style='text-autospace:none'><font size=2 face="Z@R44A.tmp"><span
lang=EN-US style='font-size:11.0pt;font-family:"Z\@R44A\.tmp"'>Gateways
support caller ID on FXO ports. CallManager does not support caller ID on
FXO</span></font></li>
</ul>
<p class=MsoNormal style='margin-left:.25in;text-autospace:none'><font size=2
face="Z@R44A.tmp"><span lang=EN-US style='font-size:11.0pt;font-family:"Z\@R44A\.tmp"'>ports
from MGCP gateways.</span></font></p>
<ul style='margin-top:0in' type=disc>
<li class=MsoNormal style='text-autospace:none'><font size=2
face="Z@R44A.tmpOOEnc"><span lang=EN-US style='font-size:11.0pt;
font-family:"Z\@R44A\.tmpOOEnc"'>Many more TDM interface types and
signaling protocols</span></font><font size=2 face=Arial><span lang=EN-US
style='font-size:11.0pt;font-family:Arial'>—</span></font><font
size=2 face="Z@R44A.tmpOOEnc"><span lang=EN-US style='font-size:11.0pt;
font-family:"Z\@R44A\.tmpOOEnc"'>for example, analog-Direct</span></font></li>
</ul>
<p class=MsoNormal style='margin-left:.25in;text-autospace:none'><font size=2
face="Z@R44A.tmp"><span lang=EN-US style='font-size:11.0pt;font-family:"Z\@R44A\.tmp"'>Inward
Dialed (DID), recEive and transMit (E&M), T1 Feature Group-D (FGD), and E1</span></font></p>
<p class=MsoNormal style='margin-left:.25in;text-autospace:none'><font size=2
face="Z@R44A.tmpOOEnc"><span lang=EN-US style='font-size:11.0pt;font-family:
"Z\@R44A\.tmpOOEnc"'>R2</span></font><font size=2 face=Arial><span lang=EN-US
style='font-size:11.0pt;font-family:Arial'>—</span></font><font size=2
face="Z@R44A.tmpOOEnc"><span lang=EN-US style='font-size:11.0pt;font-family:
"Z\@R44A\.tmpOOEnc"'>can be used.</span></font></p>
<ul style='margin-top:0in' type=disc>
<li class=MsoNormal style='text-autospace:none'><font size=2 face="Z@R44A.tmp"><span
lang=EN-US style='font-size:11.0pt;font-family:"Z\@R44A\.tmp"'>H.323 drops
DSPs on hairpinned calls to enable capabilities like ISDN video switching.</span></font></li>
<li class=MsoNormal style='text-autospace:none'><font size=2 face="Z@R44A.tmp"><span
lang=EN-US style='font-size:11.0pt;font-family:"Z\@R44A\.tmp"'>Gateway
resident applications like Toolkit Command Language (TCL) and voice</span></font></li>
</ul>
<p class=MsoNormal style='margin-left:.25in;text-autospace:none'><font size=2
face="Z@R44A.tmp"><span lang=EN-US style='font-size:11.0pt;font-family:"Z\@R44A\.tmp"'>extensible
markup language (VXML) can be used. TCL and VXML applications provide</span></font></p>
<p class=MsoNormal style='margin-left:.25in;text-autospace:none'><font size=2
face="Z@R44A.tmp"><span lang=EN-US style='font-size:11.0pt;font-family:"Z\@R44A\.tmp"'>IVR
features and call control functionality such as call forwarding, conference
calling, and</span></font></p>
<p class=MsoNormal style='margin-left:.25in;text-autospace:none'><font size=2
face="Z@R44A.tmp"><span lang=EN-US style='font-size:11.0pt;font-family:"Z\@R44A\.tmp"'>voice
mail.</span></font></p>
<ul style='margin-top:0in' type=disc>
<li class=MsoNormal style='text-autospace:none'><font size=2 face="Z@R44A.tmp"><span
lang=EN-US style='font-size:11.0pt;font-family:"Z\@R44A\.tmp"'>CAC network
design with H.323 gatekeepers is often necessary when voice and video</span></font></li>
</ul>
<p class=MsoNormal style='margin-left:.25in;text-autospace:none'><font size=2
face="Z@R44A.tmp"><span lang=EN-US style='font-size:11.0pt;font-family:"Z\@R44A\.tmp"'>coexist
in a network and Cisco CallManager is not the only call controller in the
network.</span></font></p>
<ul style='margin-top:0in' type=disc>
<li class=MsoNormal style='text-autospace:none'><font size=2 face="Z@R44A.tmp"><span
lang=EN-US style='font-size:11.0pt;font-family:"Z\@R44A\.tmp"'>There are
no release dependencies between gateways and Cisco CallManager for</span></font></li>
</ul>
<p class=MsoNormal style='margin-left:.25in;text-autospace:none'><font size=2
face="Z@R44A.tmp"><span lang=EN-US style='font-size:11.0pt;font-family:"Z\@R44A\.tmp"'>supporting
new voice hardware. New hardware cards on Cisco IOS gateways become</span></font></p>
<p class=MsoNormal style='margin-left:.25in;text-autospace:none'><font size=2
face="Z@R44A.tmp"><span lang=EN-US style='font-size:11.0pt;font-family:"Z\@R44A\.tmp"'>immediately
available for use with all existing Cisco CallManager releases.</span></font></p>
<ul style='margin-top:0in' type=disc>
<li class=MsoNormal style='text-autospace:none'><font size=2 face="Z@R44A.tmp"><span
lang=EN-US style='font-size:11.0pt;font-family:"Z\@R44A\.tmp"'>H.323
enables a much easier migration architecture to SIP because the
fundamental</span></font></li>
</ul>
<p class=MsoNormal style='margin-left:.25in;text-autospace:none'><font size=2
face="Z@R44A.tmpOOEnc"><span lang=EN-US style='font-size:11.0pt;font-family:
"Z\@R44A\.tmpOOEnc"'>concepts of H.323 and SIP</span></font><font size=2
face=Arial><span lang=EN-US style='font-size:11.0pt;font-family:Arial'>—</span></font><font
size=2 face="Z@R44A.tmpOOEnc"><span lang=EN-US style='font-size:11.0pt;
font-family:"Z\@R44A\.tmpOOEnc"'>for example, distributed control with
dial-peer</span></font></p>
<p class=MsoNormal style='margin-left:.25in;text-autospace:none'><font size=2
face="Z@R44A.tmpOOEnc"><span lang=EN-US style='font-size:11.0pt;font-family:
"Z\@R44A\.tmpOOEnc"'>configurations</span></font><font size=2 face=Arial><span
lang=EN-US style='font-size:11.0pt;font-family:Arial'>—</span></font><font
size=2 face="Z@R44A.tmpOOEnc"><span lang=EN-US style='font-size:11.0pt;
font-family:"Z\@R44A\.tmpOOEnc"'>are the same.</span></font></p>
<ul style='margin-top:0in' type=disc>
<li class=MsoNormal style='text-autospace:none'><font size=2 face="Z@R44A.tmp"><span
lang=EN-US style='font-size:11.0pt;font-family:"Z\@R44A\.tmp"'>Calls from
IP phones through an H323 gateway are dropped on a CallManager failover</span></font></li>
</ul>
<p class=MsoNormal style='margin-left:.25in;text-autospace:none'><font size=2
face="Z@R44A.tmp"><span lang=EN-US style='font-size:11.0pt;font-family:"Z\@R44A\.tmp"'>unless
SRST mode is enabled. With SRST enabled, the calls are preserved.</span></font></p>
<p class=MsoNormal><font size=2 color=navy face=Arial><span lang=EN-US
style='font-size:10.0pt;font-family:Arial;color:navy'> </span></font></p>
<p class=MsoNormal style='text-autospace:none'><b><font size=2 face="Z@R44A.tmp"><span
lang=EN-US style='font-size:11.0pt;font-family:"Z\@R44A\.tmp";font-weight:bold'>Using
MGCP as the call control protocol to a gateway has the following advantages:</span></font></b></p>
<p class=MsoNormal style='text-autospace:none'><font size=2 face="Z@R44A.tmp"><span
lang=EN-US style='font-size:11.0pt;font-family:"Z\@R44A\.tmp"'> </span></font></p>
<ul style='margin-top:0in' type=disc>
<li class=MsoNormal style='text-autospace:none'><font size=2 face="Z@R44A.tmp"><span
lang=EN-US style='font-size:11.0pt;font-family:"Z\@R44A\.tmp"'>Centralized
configuration, control, and download from Cisco CallManager</span></font></li>
<li class=MsoNormal style='text-autospace:none'><font size=2 face="Z@R44A.tmp"><span
lang=EN-US style='font-size:11.0pt;font-family:"Z\@R44A\.tmp"'>Better
feature interaction with capabilities like caller ID and name display</span></font></li>
<li class=MsoNormal style='text-autospace:none'><font size=2 face="Z@R44A.tmp"><span
lang=EN-US style='font-size:11.0pt;font-family:"Z\@R44A\.tmp"'>Easy, centralized
dial-plan management</span></font></li>
<li class=MsoNormal style='text-autospace:none'><font size=2 face="Z@R44A.tmp"><span
lang=EN-US style='font-size:11.0pt;font-family:"Z\@R44A\.tmp"'>Gateway
voice security features (voice encryption) as of Cisco IOS Software
Release</span></font></li>
</ul>
<p class=MsoNormal style='margin-left:.25in;text-autospace:none'><font size=2
face="Z@R44A.tmp"><span lang=EN-US style='font-size:11.0pt;font-family:"Z\@R44A\.tmp"'>12.3.(5</span></font><font
size=1 face="Z@R44A.tmp"><span lang=EN-US style='font-size:7.0pt;font-family:
"Z\@R44A\.tmp"'>th</span></font><font size=2 face="Z@R44A.tmp"><span
lang=EN-US style='font-size:11.0pt;font-family:"Z\@R44A\.tmp"'>)T</span></font></p>
<ul style='margin-top:0in' type=disc>
<li class=MsoNormal style='text-autospace:none'><font size=2 face="Z@R44A.tmp"><span
lang=EN-US style='font-size:11.0pt;font-family:"Z\@R44A\.tmp"'>Q Signaling
(QSIG) supplementary services as supported by Cisco CallManager:</span></font></li>
<ul style='margin-top:0in' type=circle>
<li class=MsoNormal style='text-autospace:none'><font size=2 face=Arial><span
lang=EN-US style='font-size:11.0pt;font-family:Arial'>—</span></font><font
size=2 face="Z@R44A.tmpOOEnc"><span lang=EN-US style='font-size:11.0pt;
font-family:"Z\@R44A\.tmpOOEnc"'> </span></font><font size=2
face="Z@R44A.tmp"><span lang=EN-US style='font-size:11.0pt;font-family:
"Z\@R44A\.tmp"'>Cisco CallManager interconnects to a QSIG network using
an MGCP gateway and</span></font></li>
</ul>
</ul>
<p class=MsoNormal style='margin-left:.5in;text-indent:.5in;text-autospace:
none'><font size=2 face="Z@R44A.tmp"><span lang=EN-US style='font-size:11.0pt;
font-family:"Z\@R44A\.tmp"'>T1 or E1 PRI connections to a private integrated
services network (PISN). The</span></font></p>
<p class=MsoNormal style='margin-left:.5in;text-indent:.5in;text-autospace:
none'><font size=2 face="Z@R44A.tmp"><span lang=EN-US style='font-size:11.0pt;
font-family:"Z\@R44A\.tmp"'>MGCP gateway establishes the call connections.
Using the PRI backhaul</span></font></p>
<p class=MsoNormal style='margin-left:.5in;text-indent:.5in;text-autospace:
none'><font size=2 face="Z@R44A.tmp"><span lang=EN-US style='font-size:11.0pt;
font-family:"Z\@R44A\.tmp"'>mechanism, the gateway passes the QSIG messages to
the Cisco CallManager to set</span></font></p>
<p class=MsoNormal style='margin-left:.5in;text-indent:.5in;text-autospace:
none'><font size=2 face="Z@R44A.tmp"><span lang=EN-US style='font-size:11.0pt;
font-family:"Z\@R44A\.tmp"'>up QSIG calls and send QSIG messages to control
features.</span></font></p>
<ul style='margin-top:0in' type=disc>
<ul style='margin-top:0in' type=circle>
<li class=MsoNormal style='text-autospace:none'><font size=2 face=Arial><span
lang=EN-US style='font-size:11.0pt;font-family:Arial'>—</span></font><font
size=2 face="Z@R44A.tmpOOEnc"><span lang=EN-US style='font-size:11.0pt;
font-family:"Z\@R44A\.tmpOOEnc"'> </span></font><font size=2
face="Z@R44A.tmp"><span lang=EN-US style='font-size:11.0pt;font-family:
"Z\@R44A\.tmp"'>When a PBX is connected to a gateway that is using QSIG
via H.323, calls that are</span></font></li>
</ul>
</ul>
<p class=MsoNormal style='margin-left:.5in;text-indent:.5in;text-autospace:
none'><font size=2 face="Z@R44A.tmp"><span lang=EN-US style='font-size:11.0pt;
font-family:"Z\@R44A\.tmp"'>made between phones on the PBX and IP phones
attached to the Cisco CallManager</span></font></p>
<p class=MsoNormal style='margin-left:.5in;text-indent:.5in;text-autospace:
none'><font size=2 face="Z@R44A.tmp"><span lang=EN-US style='font-size:11.0pt;
font-family:"Z\@R44A\.tmp"'>can have only basic PRI functionality. The gateway
that terminates the QSIG</span></font></p>
<p class=MsoNormal style='margin-left:.5in;text-indent:.5in;text-autospace:
none'><font size=2 face="Z@R44A.tmp"><span lang=EN-US style='font-size:11.0pt;
font-family:"Z\@R44A\.tmp"'>protocol provides only the calling line ID (CLID)
and DID number, instead of Cisco</span></font></p>
<p class=MsoNormal style='margin-left:.5in;text-indent:.5in;text-autospace:
none'><font size=2 face="Z@R44A.tmp"><span lang=EN-US style='font-size:11.0pt;
font-family:"Z\@R44A\.tmp"'>CallManager providing that information.</span></font></p>
<ul style='margin-top:0in' type=disc>
<li class=MsoNormal style='text-autospace:none'><font size=2 face="Z@R44A.tmp"><span
lang=EN-US style='font-size:11.0pt;font-family:"Z\@R44A\.tmp"'>Enhanced
call survivability:</span></font></li>
<ul style='margin-top:0in' type=circle>
<li class=MsoNormal style='text-autospace:none'><font size=2 face=Arial><span
lang=EN-US style='font-size:11.0pt;font-family:Arial'>—</span></font><font
size=2 face="Z@R44A.tmpOOEnc"><span lang=EN-US style='font-size:11.0pt;
font-family:"Z\@R44A\.tmpOOEnc"'> </span></font><font size=2
face="Z@R44A.tmp"><span lang=EN-US style='font-size:11.0pt;font-family:
"Z\@R44A\.tmp"'>Calls from IP phones through an MGCP gateway are
preserved on a CallManager</span></font></li>
</ul>
</ul>
<p class=MsoNormal style='margin-left:.75in;text-indent:.25in;text-autospace:
none'><font size=2 face="Z@R44A.tmp"><span lang=EN-US style='font-size:11.0pt;
font-family:"Z\@R44A\.tmp"'>failover. This feature avoids dropped calls when
applying the monthly operating</span></font></p>
<p class=MsoNormal style='margin-left:.5in;text-indent:.5in;text-autospace:
none'><font size=2 face="Z@R44A.tmp"><span lang=EN-US style='font-size:11.0pt;
font-family:"Z\@R44A\.tmp"'>system service release on the Cisco CallManagers</span></font></p>
<ul style='margin-top:0in' type=disc>
<ul style='margin-top:0in' type=circle>
<li class=MsoNormal style='text-autospace:none'><font size=2 face=Arial><span
lang=EN-US style='font-size:11.0pt;font-family:Arial'>—</span></font><font
size=2 face="Z@R44A.tmpOOEnc"><span lang=EN-US style='font-size:11.0pt;
font-family:"Z\@R44A\.tmpOOEnc"'> </span></font><font size=2
face="Z@R44A.tmp"><span lang=EN-US style='font-size:11.0pt;font-family:
"Z\@R44A\.tmp"'>In SRST mode, calls from IP phones through an MGCP
gateway are preserved on</span></font></li>
</ul>
</ul>
<p class=MsoNormal style='margin-left:.5in;text-indent:.5in;text-autospace:
none'><font size=2 face="Z@R44A.tmp"><span lang=EN-US style='font-size:11.0pt;
font-family:"Z\@R44A\.tmp"'>MGCP fallback for calls on analog or CAS circuits.
Calls on ISDN circuits are</span></font></p>
<p class=MsoNormal style='margin-left:1.0in;text-autospace:none'><font size=2
face="Z@R44A.tmp"><span lang=EN-US style='font-size:11.0pt;font-family:"Z\@R44A\.tmp"'>dropped
on fallback.</span></font></p>
<p class=MsoNormal style='margin-left:1.0in;text-autospace:none'><font size=2
face="Z@R44A.tmp"><span lang=EN-US style='font-size:11.0pt;font-family:"Z\@R44A\.tmp"'> </span></font></p>
<p class=MsoNormal style='margin-left:.5in;text-autospace:none'><font size=2
face="Z@R44A.tmp"><span lang=EN-US style='font-size:11.0pt;font-family:"Z\@R44A\.tmp"'>HTH’s</span></font></p>
<p class=MsoNormal style='margin-left:.5in;text-autospace:none'><font size=2
face="Z@R44A.tmp"><span lang=EN-US style='font-size:11.0pt;font-family:"Z\@R44A\.tmp"'> </span></font></p>
<p class=MsoNormal style='margin-left:.5in;text-autospace:none'><font size=2
face="Z@R44A.tmp"><span lang=EN-US style='font-size:11.0pt;font-family:"Z\@R44A\.tmp"'>Joe</span></font></p>
<p class=MsoNormal><font size=2 color=navy face=Arial><span lang=EN-US
style='font-size:10.0pt;font-family:Arial;color:navy'> </span></font></p>
<p class=MsoNormal><font size=2 color=navy face=Arial><span lang=EN-US
style='font-size:10.0pt;font-family:Arial;color:navy'> </span></font></p>
<div>
<div class=MsoNormal align=center style='text-align:center'><font size=3
face="Times New Roman"><span lang=EN-US style='font-size:12.0pt;font-family:
"Times New Roman"'>
<hr size=2 width="100%" align=center tabindex=-1>
</span></font></div>
<p class=MsoNormal><b><font size=2 face=Tahoma><span lang=EN-US
style='font-size:10.0pt;font-weight:bold'>From:</span></font></b><font size=2><span
lang=EN-US style='font-size:10.0pt'> cisco-voip-bounces@puck.nether.net
[mailto:cisco-voip-bounces@puck.nether.net] <b><span style='font-weight:bold'>On
Behalf Of </span></b>Nick Kassel<br>
<b><span style='font-weight:bold'>Sent:</span></b> Wednesday, August 30, 2006
10:35 AM<br>
<b><span style='font-weight:bold'>To:</span></b> cisco-voip@puck.nether.net<br>
<b><span style='font-weight:bold'>Subject:</span></b> [cisco-voip] MGCP vs H323</span></font></p>
</div>
<p class=MsoNormal><font size=3 face=Tahoma><span lang=EN-US style='font-size:
12.0pt'> </span></font></p>
<p class=MsoNormal><font size=2 face=Arial><span style='font-size:10.0pt;
font-family:Arial'>Does anyone know if there is a document that lists the
differences or benefits of using either MGCP or H323.</span></font></p>
<p class=MsoNormal><font size=2 face=Arial><span style='font-size:10.0pt;
font-family:Arial'> </span></font></p>
<p class=MsoNormal><font size=2 face=Arial><span style='font-size:10.0pt;
font-family:Arial'>I need to install a gateway for PSTN breakout in a DR site
so it won’t be needed for redundancy or anything like that. </span></font></p>
<p class=MsoNormal><font size=2 face=Arial><span style='font-size:10.0pt;
font-family:Arial'> </span></font></p>
<p class=MsoNormal><font size=2 face=Arial><span style='font-size:10.0pt;
font-family:Arial'>All our branch offices currently use H323 and we have H323
for our HQ so that they can be used for redundancy should be an issue with the
local branch PSTN. </span></font></p>
<p class=MsoNormal><font size=2 face=Arial><span style='font-size:10.0pt;
font-family:Arial'> </span></font></p>
<p class=MsoNormal><font size=2 face=Arial><span style='font-size:10.0pt;
font-family:Arial'>Just wondering whether it might be better to go with MGCP in
this instance.</span></font></p>
<p class=MsoNormal><font size=2 face=Arial><span style='font-size:10.0pt;
font-family:Arial'> </span></font></p>
<p class=MsoNormal><font size=2 face=Arial><span style='font-size:10.0pt;
font-family:Arial'>Is it easier to mask the calling numbers with MGCP?</span></font></p>
<p class=MsoNormal><font size=2 face=Arial><span style='font-size:10.0pt;
font-family:Arial'> </span></font></p>
<p class=MsoNormal><font size=2 face=Arial><span style='font-size:10.0pt;
font-family:Arial'> </span></font></p>
<p class=MsoNormal style='margin-bottom:12.0pt'><font size=3
face="Times New Roman"><span style='font-size:12.0pt;font-family:"Times New Roman"'> </span></font></p>
<table class=MsoNormalTable border=0 cellpadding=0 bgcolor=white
style='background:white'>
<tr>
<td style='padding:.75pt .75pt .75pt .75pt'>
<p class=MsoNormal><font size=3 color=black face="Times New Roman"><span
style='font-size:12.0pt;font-family:"Times New Roman";color:black'><br>
***********************************************************************************************<br>
<br>
The information contained in this e-mail is strictly confidential, some or all<br>
of which may be legally privileged. It is for the intended recipient only.<br>
Access to this e-mail by any other person is prohibited. If you are not the<br>
intended recipient, any use, disclosure, copying, printing, distribution of,<br>
replying to or any action taken or omitted to be taken in reliance on this<br>
e-mail, is prohibited and may be unlawful. Please contact the sender immediately<br>
should this e-mail have been incorrectly addressed or transmitted.<br>
<br>
You accept that any instructions are deemed to have been given at the time the<br>
recipient(s) accesses them and that delivery receipt does not constitute<br>
acknowledgement or receipt by the intended recipient(s). You accept that there<br>
may be a delay in processing the instructions received from e-mails after<br>
Charles Stanley has received them. You are advised that urgent, time sensitive<br>
and confidential communications should not be sent by e-mail. <br>
<br>
You acknowledge that e-mails are not secure and you accept the risk of<br>
malfunction, viruses, unauthorised interference, mis-delivery or delay.<br>
************************************************************************************************<br>
<br>
<br>
Charles Stanley & Co. Ltd<br>
Registered Office: 25 Luke Street London EC2A 4AR<br>
<br>
Tel: 0207 739 8200 Fax: 0207 739 7798<br>
Registered in England No. 1903304<br>
<br>
Charles Stanley Sutherlands and Charles Stanley Securities are divisions of Charles Stanley & Co. Ltd<br>
<br>
Authorised and Regulated by the Financial Services Authority, Member of the<br>
London Stock Exchange, International Securities Markets Association, and The London International Financial Futures &<br>
Options Exchange.<br>
<br>
This footnote also confirms that this email message has been swept by McAfee<br>
VirusScan and SurfControl Email Filter software.</span></font></p>
</td>
</tr>
</table>
<p class=MsoNormal><font size=3 face="Times New Roman"><span lang=EN-US
style='font-size:12.0pt;font-family:"Times New Roman"'> </span></font></p>
</div>
<br><br><table bgcolor=white style="color:black"><tr><td><br>***********************************************************************************************<br>
<br>
The information contained in this e-mail is strictly confidential, some or all<br>
of which may be legally privileged. It is for the intended recipient only.<br>
Access to this e-mail by any other person is prohibited. If you are not the<br>
intended recipient, any use, disclosure, copying, printing, distribution of,<br>
replying to or any action taken or omitted to be taken in reliance on this<br>
e-mail, is prohibited and may be unlawful. Please contact the sender immediately<br>
should this e-mail have been incorrectly addressed or transmitted.<br>
<br>
You accept that any instructions are deemed to have been given at the time the<br>
recipient(s) accesses them and that delivery receipt does not constitute<br>
acknowledgement or receipt by the intended recipient(s). You accept that there<br>
may be a delay in processing the instructions received from e-mails after<br>
Charles Stanley has received them. You are advised that urgent, time sensitive<br>
and confidential communications should not be sent by e-mail. <br>
<br>
You acknowledge that e-mails are not secure and you accept the risk of<br>
malfunction, viruses, unauthorised interference, mis-delivery or delay.<br>
************************************************************************************************<br>
<br>
<br>
Charles Stanley & Co. Ltd<br>
Registered Office: 25 Luke Street London EC2A 4AR<br>
<br>
Tel: 0207 739 8200 Fax: 0207 739 7798<br>
Registered in England No. 1903304<br>
<br>
Charles Stanley Sutherlands and Charles Stanley Securities are divisions of Charles Stanley & Co. Ltd<br>
<br>
Authorised and Regulated by the Financial Services Authority, Member of the<br>
London Stock Exchange, International Securities Markets Association, and The London International Financial Futures &<br>
Options Exchange.<br>
<br>
This footnote also confirms that this email message has been swept by McAfee<br>
VirusScan and SurfControl Email Filter software.<br>
</td></tr></table></body>
</html>
<HTML><BODY><P><hr size=1></P><br>
<P><STRONG><br>
Disclaimer:<br>
<br>
This e-mail communication and any attachments may contain<br>
confidential and privileged information and is for use by the<br>
designated addressee(s) named above only. If you are not the<br>
intended addressee, you are hereby notified that you have received<br>
this communication in error and that any use or reproduction of<br>
this email or its contents is strictly prohibited and may be<br>
unlawful. If you have received this communication in error, please<br>
notify us immediately by replying to this message and deleting it<br>
from your computer. Thank you.<br>
</STRONG></P></BODY>
<HTML><BODY><P><hr size=1></P><br>
<P><STRONG><br>
Disclaimer:<br>
<br>
This e-mail communication and any attachments may contain<br>
confidential and privileged information and is for use by the<br>
designated addressee(s) named above only. If you are not the<br>
intended addressee, you are hereby notified that you have received<br>
this communication in error and that any use or reproduction of<br>
this email or its contents is strictly prohibited and may be<br>
unlawful. If you have received this communication in error, please<br>
notify us immediately by replying to this message and deleting it<br>
from your computer. Thank you.<br>
</STRONG></P></BODY>