<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type">
</head>
<body bgcolor="#ffffff" text="#000000">
If the gateway is configure to use SIP for the VOIP leg then then name
is transported correctly.<br>
<br>
h.323 was a stretch goal for the same project that added SIP support,
but the goal was not met. The question of HOW becomes complicated with
h.323. With SIP we delay extending the signaling into the VOIP network
until the FacitlyIE has been received. With H.323 the same does not
work so well in all cases.<br>
<br>
Linsemier, Matthew wrote:
<blockquote
cite="midAB0A35F2486F81468971AA68558BE71904AD1B6B@smieln01winm01.micoanet.com"
type="cite">
<meta http-equiv="Content-Type" content="text/html; ">
<meta name="Generator" content="Microsoft Word 11 (filtered medium)">
<!--[if !mso]>
<style>
v\:* {behavior:url(#default#VML);}
o\:* {behavior:url(#default#VML);}
w\:* {behavior:url(#default#VML);}
.shape {behavior:url(#default#VML);}
</style>
<![endif]--><o:SmartTagType
namespaceuri="urn:schemas-microsoft-com:office:smarttags"
name="PostalCode">
<o:SmartTagType
namespaceuri="urn:schemas-microsoft-com:office:smarttags" name="City"><o:SmartTagType
namespaceuri="urn:schemas-microsoft-com:office:smarttags"
name="country-region">
<o:SmartTagType
namespaceuri="urn:schemas-microsoft-com:office:smarttags" name="place"><o:SmartTagType
namespaceuri="urn:schemas-microsoft-com:office:smarttags" name="Street">
<o:SmartTagType
namespaceuri="urn:schemas-microsoft-com:office:smarttags"
name="address"><!--[if !mso]>
<style>
st1\:*{behavior:url(#default#ieooui) }
</style>
<![endif]-->
<style>
<!--
/* Font Definitions */
@font-face
{font-family:Tahoma;
panose-1:2 11 6 4 3 5 4 4 2 4;}
@font-face
{font-family:Verdana;
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:"Times New Roman";}
a:link, span.MsoHyperlink
{color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{color:blue;
text-decoration:underline;}
p
{mso-margin-top-alt:auto;
margin-right:0in;
mso-margin-bottom-alt:auto;
margin-left:0in;
font-size:12.0pt;
font-family:"Times New Roman";}
span.EmailStyle19
{mso-style-type:personal-reply;
font-family:Arial;
color:navy;}
@page Section1
{size:8.5in 11.0in;
margin:1.0in 1.25in 1.0in 1.25in;}
div.Section1
{page:Section1;}
/* List Definitions */
@list l0
{mso-list-id:563879078;
mso-list-template-ids:1875963722;}
@list l0:level1
{mso-level-number-format:bullet;
mso-level-text:\F0B7;
mso-level-tab-stop:.5in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Symbol;}
@list l1
{mso-list-id:609777818;
mso-list-template-ids:-482684078;}
@list l1:level1
{mso-level-number-format:bullet;
mso-level-text:\F0B7;
mso-level-tab-stop:.5in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Symbol;}
@list l1:level2
{mso-level-number-format:bullet;
mso-level-text:o;
mso-level-tab-stop:1.0in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:"Courier New";
mso-bidi-font-family:"Times New Roman";}
@list l2
{mso-list-id:865754453;
mso-list-template-ids:-995855740;}
@list l2:level1
{mso-level-number-format:bullet;
mso-level-text:\F0B7;
mso-level-tab-stop:.5in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Symbol;}
@list l3
{mso-list-id:1065833177;
mso-list-template-ids:1195674166;}
@list l3:level1
{mso-level-number-format:bullet;
mso-level-text:\F0B7;
mso-level-tab-stop:.5in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Symbol;}
@list l4
{mso-list-id:1073894947;
mso-list-template-ids:-1769202460;}
@list l4:level1
{mso-level-number-format:bullet;
mso-level-text:\F0B7;
mso-level-tab-stop:.5in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Symbol;}
@list l5
{mso-list-id:1241595843;
mso-list-template-ids:-667142756;}
@list l5:level1
{mso-level-number-format:bullet;
mso-level-text:\F0B7;
mso-level-tab-stop:.5in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Symbol;}
@list l5:level2
{mso-level-number-format:bullet;
mso-level-text:o;
mso-level-tab-stop:1.0in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:"Courier New";
mso-bidi-font-family:"Times New Roman";}
@list l6
{mso-list-id:1747533729;
mso-list-template-ids:1894155440;}
@list l6:level1
{mso-level-number-format:bullet;
mso-level-text:\F0B7;
mso-level-tab-stop:.5in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Symbol;}
@list l7
{mso-list-id:1851870610;
mso-list-template-ids:548424392;}
@list l7:level1
{mso-level-number-format:bullet;
mso-level-text:\F0B7;
mso-level-tab-stop:.5in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Symbol;}
@list l8
{mso-list-id:2037003791;
mso-list-template-ids:332959532;}
@list l8:level1
{mso-level-number-format:bullet;
mso-level-text:\F0B7;
mso-level-tab-stop:.5in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Symbol;}
@list l8:level2
{mso-level-number-format:bullet;
mso-level-text:o;
mso-level-tab-stop:1.0in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:"Courier New";
mso-bidi-font-family:"Times New Roman";}
@list l9
{mso-list-id:2091199446;
mso-list-template-ids:-869899608;}
@list l9:level1
{mso-level-number-format:bullet;
mso-level-text:\F0B7;
mso-level-tab-stop:.5in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Symbol;}
@list l9:level2
{mso-level-number-format:bullet;
mso-level-text:o;
mso-level-tab-stop:1.0in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:"Courier New";
mso-bidi-font-family:"Times New Roman";}
@list l10
{mso-list-id:2096054460;
mso-list-template-ids:2097202400;}
@list l10:level1
{mso-level-number-format:bullet;
mso-level-text:\F0B7;
mso-level-tab-stop:.5in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Symbol;}
@list l11
{mso-list-id:2140148665;
mso-list-template-ids:-1764349894;}
@list l11:level1
{mso-level-number-format:bullet;
mso-level-text:\F0B7;
mso-level-tab-stop:.5in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Symbol;}
@list l12
{mso-list-id:2144735870;
mso-list-template-ids:1153099450;}
@list l12:level1
{mso-level-number-format:bullet;
mso-level-text:\F0B7;
mso-level-tab-stop:.5in;
mso-level-number-position:left;
text-indent:-.25in;
mso-ansi-font-size:10.0pt;
font-family:Symbol;}
ol
{margin-bottom:0in;}
ul
{margin-bottom:0in;}
-->
</style></o:SmartTagType></o:SmartTagType></o:SmartTagType></o:SmartTagType></o:SmartTagType></o:SmartTagType>
<div class="Section1">
<p class="MsoNormal"><font color="navy" face="Arial" size="2"><span
style="font-size: 10pt; font-family: Arial; color: navy;">What is the
reasoning for not supporting
the FacilityIE or having some IOS have a feature that could read from
FacilityIE and then put it in the DisplayIE or NotifyIE fields for
delivery to
CallManager?<o:p></o:p></span></font></p>
<p class="MsoNormal"><font color="navy" face="Arial" size="2"><span
style="font-size: 10pt; font-family: Arial; color: navy;"><o:p> </o:p></span></font></p>
<p class="MsoNormal"><font color="navy" face="Arial" size="2"><span
style="font-size: 10pt; font-family: Arial; color: navy;">Matt<o:p></o:p></span></font></p>
<p class="MsoNormal"><font color="navy" face="Arial" size="2"><span
style="font-size: 10pt; font-family: Arial; color: navy;"><o:p> </o:p></span></font></p>
<div>
<div class="MsoNormal" style="text-align: center;" align="center"><font
face="Times New Roman" size="3"><span style="font-size: 12pt;">
<hr tabindex="-1" align="center" size="2" width="100%"></span></font></div>
<p class="MsoNormal"><b><font face="Tahoma" size="2"><span
style="font-size: 10pt; font-family: Tahoma; font-weight: bold;">From:</span></font></b><font
face="Tahoma" size="2"><span
style="font-size: 10pt; font-family: Tahoma;">
<a class="moz-txt-link-abbreviated" href="mailto:cisco-voip-bounces@puck.nether.net">cisco-voip-bounces@puck.nether.net</a>
[<a class="moz-txt-link-freetext" href="mailto:cisco-voip-bounces@puck.nether.net">mailto:cisco-voip-bounces@puck.nether.net</a>] <b><span
style="font-weight: bold;">On Behalf Of </span></b>Wes Sisk<br>
<b><span style="font-weight: bold;">Sent:</span></b> Wednesday,
August 30, 2006
10:14 PM<br>
<b><span style="font-weight: bold;">To:</span></b> Linsemier, Matthew<br>
<b><span style="font-weight: bold;">Cc:</span></b>
<a class="moz-txt-link-abbreviated" href="mailto:cisco-voip@puck.nether.net">cisco-voip@puck.nether.net</a>;
Matt Slaga (US); Jason Burwell<br>
<b><span style="font-weight: bold;">Subject:</span></b> Re:
[cisco-voip] MGCP vs
H323</span></font><o:p></o:p></p>
</div>
<p class="MsoNormal"><font face="Times New Roman" size="3"><span
style="font-size: 12pt;"><o:p> </o:p></span></font></p>
<p class="MsoNormal"><font face="Times New Roman" size="3"><span
style="font-size: 12pt;">You will get calling name with h.323 4.2
depending on how it is
delivered:<o:p></o:p></span></font></p>
<div>
<p class="MsoNormal"><font face="Times New Roman" size="3"><span
style="font-size: 12pt;">You will see it if delivered by:<o:p></o:p></span></font></p>
</div>
<div>
<p class="MsoNormal"><font face="Times New Roman" size="3"><span
style="font-size: 12pt;">DisplayIE<o:p></o:p></span></font></p>
</div>
<div>
<p class="MsoNormal"><font face="Times New Roman" size="3"><span
style="font-size: 12pt;">NotifyIE<o:p></o:p></span></font></p>
</div>
<div>
<p class="MsoNormal"><font face="Times New Roman" size="3"><span
style="font-size: 12pt;"><o:p> </o:p></span></font></p>
</div>
<div>
<p class="MsoNormal"><font face="Times New Roman" size="3"><span
style="font-size: 12pt;">You will not see it if it is delivered by
FacilityIE. Delivery by
FacilityIE is the most common form we encounter today. This is
commonly
referred to as 'c-nam', 'cname', or 'ni-3 name delivery'.<o:p></o:p></span></font></p>
</div>
<div>
<p class="MsoNormal"><font face="Times New Roman" size="3"><span
style="font-size: 12pt;"><o:p> </o:p></span></font></p>
</div>
<div>
<p class="MsoNormal"><font face="Times New Roman" size="3"><span
style="font-size: 12pt;">/Wes<o:p></o:p></span></font></p>
<div>
<div>
<p class="MsoNormal"><font face="Times New Roman" size="3"><span
style="font-size: 12pt;">On Aug 30, 2006, at 3:21 PM, Linsemier,
Matthew wrote:<o:p></o:p></span></font></p>
</div>
<p class="MsoNormal"><font face="Times New Roman" size="3"><span
style="font-size: 12pt;"><br>
<br>
<o:p></o:p></span></font></p>
<O:SMARTTAGTYPE
namespaceuri="urn:schemas-microsoft-com:office:smarttags"
name="PostalCode"><O:SMARTTAGTYPE
namespaceuri="urn:schemas-microsoft-com:office:smarttags" name="City"><O:SMARTTAGTYPE
namespaceuri="urn:schemas-microsoft-com:office:smarttags"
name="country-region"><O:SMARTTAGTYPE
namespaceuri="urn:schemas-microsoft-com:office:smarttags" name="place"><O:SMARTTAGTYPE
namespaceuri="urn:schemas-microsoft-com:office:smarttags" name="Street"><O:SMARTTAGTYPE
namespaceuri="urn:schemas-microsoft-com:office:smarttags"
name="address"><O:SMARTTAGTYPE
namespaceuri="urn:schemas-microsoft-com:office:smarttags"
name="PersonName">
</O:SMARTTAGTYPE></O:SMARTTAGTYPE></O:SMARTTAGTYPE></O:SMARTTAGTYPE></O:SMARTTAGTYPE></O:SMARTTAGTYPE></O:SMARTTAGTYPE>
<div>
<p class="MsoNormal" style=""><font color="navy" face="Arial" size="2"><span
style="font-size: 10pt; font-family: Arial; color: navy;">This has
been an issue since we installed CallManager almost 4
years ago. If Cisco is going to move people in a new direction
H.323/SIP
it certainly needs to support the same feature set. Can anyone confirm
that they can get Calling Name in CCM 4.2? We have had calling name in
MGCP for all this time and to remove this would cause serious havoc
amongst my
users.<O:P></O:P></span></font><o:p></o:p></p>
<p class="MsoNormal" style=""><font color="navy" face="Arial" size="2"><span
style="font-size: 10pt; font-family: Arial; color: navy;"><O:P> </O:P></span></font><o:p></o:p></p>
<font face="Times New Roman" size="3"><span times="" new=""></span></font>
<div>
<div class="MsoNormal" style="text-align: center;" align="center"><font
face="Times New Roman" size="3"><span style="font-size: 12pt;">
<hr tabindex="-1" align="center" size="2" width="100%"></span></font></div>
<p class="MsoNormal" style=""><b><font face="Tahoma" size="2"><span
style="font-size: 10pt; font-family: Tahoma; font-weight: bold;"></span>From:</font></b><font
size="2"><span style="font-size: 10pt;">
<a class="moz-txt-link-abbreviated" href="mailto:cisco-voip-bounces@puck.nether.net">cisco-voip-bounces@puck.nether.net</a> [<a
href="mailto:cisco-voip-bounces@puck.nether.net">mailto:cisco-voip-bounces@puck.nether.net</a>]
<b><span style="font-weight: bold;">On Behalf Of </span></b>Matt
Slaga (US)<br>
<b><span style="font-weight: bold;">Sent:</span></b> Wednesday,
August 30, 2006
1:55 PM<br>
<b><span style="font-weight: bold;">To:</span></b> Jason Burwell; <a
href="mailto:cisco-voip@puck.nether.net">cisco-voip@puck.nether.net</a><br>
<b><span style="font-weight: bold;">Subject:</span></b> Re:
[cisco-voip] MGCP vs
H323</span></font><o:p></o:p></p>
</div>
<span times="" new=""><O:P></O:P></span>
<p class="MsoNormal" style=""><font face="Tahoma" size="3"><span
style="font-size: 12pt; font-family: Tahoma;"><O:P> </O:P></span></font><o:p></o:p></p>
<p class="MsoNormal" style=""><font color="navy" face="Arial" size="2"><span
style="font-size: 10pt; font-family: Arial; color: navy;">H323 does
support calling party number, just not name. Like
Jason mentioned before, the options are there and you can see name
traverse
inbound in debugs, but the gateway does not send it on to CallManager.<O:P></O:P></span></font><o:p></o:p></p>
<p class="MsoNormal" style=""><font color="navy" face="Arial" size="2"><span
style="font-size: 10pt; font-family: Arial; color: navy;"><O:P> </O:P></span></font><o:p></o:p></p>
<font face="Times New Roman" size="3"><span times="" new=""></span></font>
<div>
<div class="MsoNormal" style="text-align: center;" align="center"><font
face="Times New Roman" size="3"><span style="font-size: 12pt;">
<hr tabindex="-1" align="center" size="2" width="100%"></span></font></div>
<p class="MsoNormal" style=""><b><font face="Tahoma" size="2"><span
style="font-size: 10pt; font-family: Tahoma; font-weight: bold;"></span>From:</font></b><font
size="2"><span style="font-size: 10pt;">
<a class="moz-txt-link-abbreviated" href="mailto:cisco-voip-bounces@puck.nether.net">cisco-voip-bounces@puck.nether.net</a> [<a
href="mailto:cisco-voip-bounces@puck.nether.net">mailto:cisco-voip-bounces@puck.nether.net</a>]
<b><span style="font-weight: bold;">On Behalf Of </span></b>Jason
Burwell<br>
<b><span style="font-weight: bold;">Sent:</span></b> Wednesday,
August 30, 2006
1:36 PM<br>
<b><span style="font-weight: bold;">To:</span></b> <a
href="mailto:cisco-voip@puck.nether.net">cisco-voip@puck.nether.net</a><br>
<b><span style="font-weight: bold;">Subject:</span></b> Re:
[cisco-voip] MGCP vs
H323</span></font><o:p></o:p></p>
</div>
<span times="" new=""><O:P></O:P></span>
<p class="MsoNormal" style=""><font face="Tahoma" size="3"><span
style="font-size: 12pt; font-family: Tahoma;"><O:P> </O:P></span></font><o:p></o:p></p>
<p class="MsoNormal" style=""><font color="navy" face="Arial" size="2"><span
style="font-size: 10pt; font-family: Arial; color: navy;">We have just
purchased CVP and are being told that we can no longer
use MGCP gateways and must migrate to H323. According to what I have
heard
here, H323 will not support Caller Name but will H323 support Calling
Party
Number capability?<O:P></O:P></span></font><o:p></o:p></p>
<p class="MsoNormal" style=""><font color="navy" face="Arial" size="2"><span
style="font-size: 10pt; font-family: Arial; color: navy;"><O:P> </O:P></span></font><o:p></o:p></p>
<p class="MsoNormal" style=""><font color="navy" face="Arial" size="2"><span
style="font-size: 10pt; font-family: Arial; color: navy;">Jason<O:P></O:P></span></font><o:p></o:p></p>
<p class="MsoNormal" style=""><font color="navy" face="Arial" size="2"><span
style="font-size: 10pt; font-family: Arial; color: navy;"><O:P> </O:P></span></font><o:p></o:p></p>
<font face="Times New Roman" size="3"><span times="" new=""></span></font>
<div>
<div class="MsoNormal" style="text-align: center;" align="center"><font
face="Times New Roman" size="3"><span style="font-size: 12pt;">
<hr tabindex="-1" align="center" size="2" width="100%"></span></font></div>
<p class="MsoNormal" style=""><b><font face="Tahoma" size="2"><span
style="font-size: 10pt; font-family: Tahoma; font-weight: bold;"></span>From:</font></b><font
size="2"><span style="font-size: 10pt;">
<a class="moz-txt-link-abbreviated" href="mailto:cisco-voip-bounces@puck.nether.net">cisco-voip-bounces@puck.nether.net</a> [<a
href="mailto:cisco-voip-bounces@puck.nether.net">mailto:cisco-voip-bounces@puck.nether.net</a>]
<b><span style="font-weight: bold;">On Behalf Of <ST1:PERSONNAME
u1:st="on"></ST1:PERSONNAME></span></b>Jason
Aarons (US)<br>
<b><span style="font-weight: bold;">Sent:</span></b> Wednesday,
August 30, 2006
12:52 PM<br>
<b><span style="font-weight: bold;">To:</span></b> <a
href="mailto:cisco-voip@puck.nether.net">cisco-voip@puck.nether.net</a><br>
<b><span style="font-weight: bold;">Subject:</span></b> Re:
[cisco-voip] MGCP vs
H323</span></font><o:p></o:p></p>
</div>
<span times="" new=""><O:P></O:P></span>
<p class="MsoNormal" style=""><font face="Tahoma" size="3"><span
style="font-size: 12pt; font-family: Tahoma;"><O:P> </O:P></span></font><o:p></o:p></p>
<p class="MsoNormal" style=""><font color="navy" face="Arial" size="2"><span
style="font-size: 10pt; font-family: Arial; color: navy;">I believe
the issue is with CallManager not supporting both types
of facility ie as you can see the Calling Party Name in the router’s
debug isdn
q931.<O:P></O:P></span></font><o:p></o:p></p>
<p class="MsoNormal" style=""><font color="navy" face="Arial" size="2"><span
style="font-size: 10pt; font-family: Arial; color: navy;"><O:P> </O:P></span></font><o:p></o:p></p>
<font face="Times New Roman" size="3"><span times="" new=""></span></font>
<div>
<div class="MsoNormal" style="text-align: center;" align="center"><font
face="Times New Roman" size="3"><span style="font-size: 12pt;">
<hr tabindex="-1" align="center" size="2" width="100%"></span></font></div>
<p class="MsoNormal" style=""><b><font face="Tahoma" size="2"><span
style="font-size: 10pt; font-family: Tahoma; font-weight: bold;"></span>From:</font></b><font
size="2"><span style="font-size: 10pt;">
<a class="moz-txt-link-abbreviated" href="mailto:cisco-voip-bounces@puck.nether.net">cisco-voip-bounces@puck.nether.net</a> [<a
href="mailto:cisco-voip-bounces@puck.nether.net">mailto:cisco-voip-bounces@puck.nether.net</a>]
<b><span style="font-weight: bold;">On Behalf Of </span></b>Linsemier,
Matthew<br>
<b><span style="font-weight: bold;">Sent:</span></b> Wednesday,
August 30, 2006
12:11 PM<br>
<b><span style="font-weight: bold;">To:</span></b> <ST1:PERSONNAME
u1:st="on">Matt
Slaga</ST1:PERSONNAME> (US); Joe Pollere (US); Nick Kassel; <a
href="mailto:cisco-voip@puck.nether.net">cisco-voip@puck.nether.net</a><br>
<b><span style="font-weight: bold;">Subject:</span></b> Re:
[cisco-voip] MGCP vs
H323</span></font><o:p></o:p></p>
</div>
<span times="" new=""><O:P></O:P></span>
<p class="MsoNormal" style=""><font face="Tahoma" size="3"><span
style="font-size: 12pt; font-family: Tahoma;"><O:P> </O:P></span></font><o:p></o:p></p>
<p class="MsoNormal" style=""><font color="navy" face="Arial" size="2"><span
style="font-size: 10pt; font-family: Arial; color: navy;">Calling
Name/Number is one of the main reasons we utilize MGCP over
H.323. This coupled with failover (which seems to be handled much more
gracefully then in an H.323 environment) keep us on this protocol. If
H.323 could handle Calling Name, I would definitely make the move. It
would certainly make fax integration with products such as Unity or
XMedius fax
much easier. I, however, find myself in a position where I couldn’t
possibly take away features that my users have come to expect and
love. <O:P></O:P></span></font><o:p></o:p></p>
<p class="MsoNormal" style=""><font color="navy" face="Arial" size="2"><span
style="font-size: 10pt; font-family: Arial; color: navy;"><O:P> </O:P></span></font><o:p></o:p></p>
<p class="MsoNormal" style=""><font color="navy" face="Arial" size="2"><span
style="font-size: 10pt; font-family: Arial; color: navy;">I did hear
rumblings that H.323 was going to support Calling Name
in a later IOS release. The information is there on the router, just
not
getting processed. Can any of you Cisco folks comment (off the record)?<O:P></O:P></span></font><o:p></o:p></p>
<p class="MsoNormal" style=""><font color="navy" face="Arial" size="2"><span
style="font-size: 10pt; font-family: Arial; color: navy;"><O:P> </O:P></span></font><o:p></o:p></p>
<p class="MsoNormal" style=""><font color="navy" face="Arial" size="2"><span
style="font-size: 10pt; font-family: Arial; color: navy;">-Matt<O:P></O:P></span></font><o:p></o:p></p>
<p class="MsoNormal" style=""><font color="navy" face="Arial" size="2"><span
style="font-size: 10pt; font-family: Arial; color: navy;"><O:P> </O:P></span></font><o:p></o:p></p>
<font face="Times New Roman" size="3"><span times="" new=""></span></font>
<div>
<div class="MsoNormal" style="text-align: center;" align="center"><font
face="Times New Roman" size="3"><span style="font-size: 12pt;">
<hr tabindex="-1" align="center" size="2" width="100%"></span></font></div>
<p class="MsoNormal" style=""><b><font face="Tahoma" size="2"><span
style="font-size: 10pt; font-family: Tahoma; font-weight: bold;"></span>From:</font></b><font
size="2"><span style="font-size: 10pt;">
<a class="moz-txt-link-abbreviated" href="mailto:cisco-voip-bounces@puck.nether.net">cisco-voip-bounces@puck.nether.net</a> [<a
href="mailto:cisco-voip-bounces@puck.nether.net">mailto:cisco-voip-bounces@puck.nether.net</a>]
<b><span style="font-weight: bold;">On Behalf Of <ST1:PERSONNAME
u1:st="on"></ST1:PERSONNAME></span></b>Matt
Slaga (US)<br>
<b><span style="font-weight: bold;">Sent:</span></b> Wednesday,
August 30, 2006
12:00 PM<br>
<b><span style="font-weight: bold;">To:</span></b> Joe Pollere (US);
Nick Kassel;
<a href="mailto:cisco-voip@puck.nether.net">cisco-voip@puck.nether.net</a><br>
<b><span style="font-weight: bold;">Subject:</span></b> Re:
[cisco-voip] MGCP vs
H323</span></font><o:p></o:p></p>
</div>
<span times="" new=""><O:P></O:P></span>
<p class="MsoNormal" style=""><font face="Tahoma" size="3"><span
style="font-size: 12pt; font-family: Tahoma;"><O:P> </O:P></span></font><o:p></o:p></p>
<p class="MsoNormal" style=""><font color="navy" face="Arial" size="2"><span
style="font-size: 10pt; 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.<O:P></O:P></span></font><o:p></o:p></p>
<p class="MsoNormal" style=""><font color="navy" face="Arial" size="2"><span
style="font-size: 10pt; font-family: Arial; color: navy;"><O:P> </O:P></span></font><o:p></o:p></p>
<p class="MsoNormal" style=""><font color="navy" face="Arial" size="2"><span
style="font-size: 10pt; 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.<O:P></O:P></span></font><o:p></o:p></p>
<p class="MsoNormal" style=""><font color="navy" face="Arial" size="2"><span
style="font-size: 10pt; font-family: Arial; color: navy;"><O:P> </O:P></span></font><o:p></o:p></p>
<p class="MsoNormal" style=""><font color="navy" face="Arial" size="2"><span
style="font-size: 10pt; 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.<O:P></O:P></span></font><o:p></o:p></p>
<p class="MsoNormal" style=""><font color="navy" face="Arial" size="2"><span
style="font-size: 10pt; font-family: Arial; color: navy;"><O:P> </O:P></span></font><o:p></o:p></p>
<p class="MsoNormal" style=""><font color="navy" face="Arial" size="2"><span
style="font-size: 10pt; 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<O:P></O:P></span></font><o:p></o:p></p>
<p class="MsoNormal" style=""><font color="navy" face="Arial" size="2"><span
style="font-size: 10pt; font-family: Arial; color: navy;"><O:P> </O:P></span></font><o:p></o:p></p>
<p class="MsoNormal" style=""><font color="navy" face="Arial" size="2"><span
style="font-size: 10pt; font-family: Arial; color: navy;"><O:P> </O:P></span></font><o:p></o:p></p>
<p class="MsoNormal" style=""><font color="navy" face="Arial" size="2"><span
style="font-size: 10pt; font-family: Arial; color: navy;"><O:P> </O:P></span></font><o:p></o:p></p>
<p class="MsoNormal" style=""><font color="navy" face="Arial" size="2"><span
style="font-size: 10pt; font-family: Arial; color: navy;"><O:P> </O:P></span></font><o:p></o:p></p>
<font face="Times New Roman" size="3"><span times="" new=""></span></font>
<div>
<div class="MsoNormal" style="text-align: center;" align="center"><font
face="Times New Roman" size="3"><span style="font-size: 12pt;">
<hr tabindex="-1" align="center" size="2" width="100%"></span></font></div>
<p class="MsoNormal" style=""><b><font face="Tahoma" size="2"><span
style="font-size: 10pt; font-family: Tahoma; font-weight: bold;"></span>From:</font></b><font
size="2"><span style="font-size: 10pt;">
<a class="moz-txt-link-abbreviated" href="mailto:cisco-voip-bounces@puck.nether.net">cisco-voip-bounces@puck.nether.net</a> [<a
href="mailto:cisco-voip-bounces@puck.nether.net">mailto:cisco-voip-bounces@puck.nether.net</a>]
<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; <a
href="mailto:cisco-voip@puck.nether.net">cisco-voip@puck.nether.net</a><br>
<b><span style="font-weight: bold;">Subject:</span></b> Re:
[cisco-voip] MGCP vs
H323</span></font><o:p></o:p></p>
</div>
<span times="" new=""><O:P></O:P></span>
<p class="MsoNormal" style=""><font face="Tahoma" size="3"><span
style="font-size: 12pt; font-family: Tahoma;"><O:P> </O:P></span></font><o:p></o:p></p>
<p class="MsoNormal" style=""><font face="Z@R44A.tmp" size="2"><span
style="font-size: 10pt; font-family: "Z@R44A.tmp";">Nick,<O:P></O:P></span></font><o:p></o:p></p>
<p class="MsoNormal" style=""><font face="Z@R44A.tmp" size="2"><span
style="font-size: 10pt; font-family: "Z@R44A.tmp";"><O:P> </O:P></span></font><o:p></o:p></p>
<p class="MsoNormal" style=""><font face="Z@R44A.tmp" size="2"><span
style="font-size: 10pt; font-family: "Z@R44A.tmp";">This is from the
GWGK course book:<O:P></O:P></span></font><o:p></o:p></p>
<p class="MsoNormal" style=""><b><font face="Z@R44A.tmp" size="2"><span
style="font-size: 10pt; font-family: "Z@R44A.tmp"; font-weight: bold;"><O:P> </O:P></span></font></b><o:p></o:p></p>
<p class="MsoNormal" style=""><b><font face="Z@R44A.tmp" size="2"><span
style="font-size: 10pt; font-family: "Z@R44A.tmp"; font-weight: bold;">Using
H.323 as the call
control protocol to a gateway has the following advantages:<O:P></O:P></span></font></b><o:p></o:p></p>
<p class="MsoNormal" style=""><font face="Z@R44A.tmp" size="2"><span
style="font-size: 10pt; font-family: "Z@R44A.tmp";"><O:P> </O:P></span></font><o:p></o:p></p>
<ul type="disc">
<li class="MsoNormal" style=""><font face="Z@R44A.tmp" size="2"><span
style="font-size: 10pt; font-family: "Z@R44A.tmp";">H.323 provides
integrated access. Data and voice channels can be placed on the same T1.<O:P></O:P></span></font><o:p></o:p></li>
</ul>
<p class="MsoNormal" style="margin-left: 0.25in;"><font
face="Z@R44A.tmp" size="2"><span
style="font-size: 10pt; font-family: "Z@R44A.tmp";">For example, for a
service
provider like AT&T, FR and PRI can be placed on the same T1.<O:P></O:P></span></font><o:p></o:p></p>
<ul type="disc">
<li class="MsoNormal" style=""><font face="Z@R44A.tmp" size="2"><span
style="font-size: 10pt; font-family: "Z@R44A.tmp";">H.323 provides
support for fractional PRI.<O:P></O:P></span></font><o:p></o:p></li>
<li class="MsoNormal" style=""><font face="Z@R44A.tmp" size="2"><span
style="font-size: 10pt; font-family: "Z@R44A.tmp";">Gateways support
caller ID on FXO ports. CallManager does not support caller ID on FXO<O:P></O:P></span></font><o:p></o:p></li>
</ul>
<p class="MsoNormal" style="margin-left: 0.25in;"><font
face="Z@R44A.tmp" size="2"><span
style="font-size: 10pt; font-family: "Z@R44A.tmp";">ports from MGCP
gateways.<O:P></O:P></span></font><o:p></o:p></p>
<ul type="disc">
<li class="MsoNormal" style=""><font face="Z@R44A.tmpOOEnc" size="2"><span
style="font-size: 10pt; font-family: "Z@R44A.tmpOOEnc";">Many more TDM
interface types and signaling protocols</span></font><font face="Arial"
size="2"><span style="font-size: 11pt; font-family: Arial;">—</span></font><font
face="Z@R44A.tmpOOEnc" size="2"><span
style="font-size: 10pt; font-family: "Z@R44A.tmpOOEnc";">for example,
analog-Direct<O:P></O:P></span></font><o:p></o:p></li>
</ul>
<p class="MsoNormal" style="margin-left: 0.25in;"><font
face="Z@R44A.tmp" size="2"><span
style="font-size: 10pt; font-family: "Z@R44A.tmp";">Inward Dialed
(DID),
recEive and transMit (E&M), T1 Feature Group-D (FGD), and E1<O:P></O:P></span></font><o:p></o:p></p>
<p class="MsoNormal" style="margin-left: 0.25in;"><font
face="Z@R44A.tmpOOEnc" size="2"><span
style="font-size: 10pt; font-family: "Z@R44A.tmpOOEnc";">R2</span></font><font
face="Arial" size="2"><span
style="font-size: 11pt; font-family: Arial;">—</span></font><font
face="Z@R44A.tmpOOEnc" size="2"><span
style="font-size: 10pt; font-family: "Z@R44A.tmpOOEnc";">can
be used.<O:P></O:P></span></font><o:p></o:p></p>
<ul type="disc">
<li class="MsoNormal" style=""><font face="Z@R44A.tmp" size="2"><span
style="font-size: 10pt; font-family: "Z@R44A.tmp";">H.323 drops DSPs
on hairpinned calls to enable capabilities like ISDN video switching.<O:P></O:P></span></font><o:p></o:p></li>
<li class="MsoNormal" style=""><font face="Z@R44A.tmp" size="2"><span
style="font-size: 10pt; font-family: "Z@R44A.tmp";">Gateway resident
applications like Toolkit Command Language (TCL) and voice<O:P></O:P></span></font><o:p></o:p></li>
</ul>
<p class="MsoNormal" style="margin-left: 0.25in;"><font
face="Z@R44A.tmp" size="2"><span
style="font-size: 10pt; font-family: "Z@R44A.tmp";">extensible markup
language
(VXML) can be used. TCL and VXML applications provide<O:P></O:P></span></font><o:p></o:p></p>
<p class="MsoNormal" style="margin-left: 0.25in;"><font
face="Z@R44A.tmp" size="2"><span
style="font-size: 10pt; font-family: "Z@R44A.tmp";">IVR features and
call
control functionality such as call forwarding, conference calling, and<O:P></O:P></span></font><o:p></o:p></p>
<p class="MsoNormal" style="margin-left: 0.25in;"><font
face="Z@R44A.tmp" size="2"><span
style="font-size: 10pt; font-family: "Z@R44A.tmp";">voice mail.<O:P></O:P></span></font><o:p></o:p></p>
<ul type="disc">
<li class="MsoNormal" style=""><font face="Z@R44A.tmp" size="2"><span
style="font-size: 10pt; font-family: "Z@R44A.tmp";">CAC network design
with H.323 gatekeepers is often necessary when voice and video<O:P></O:P></span></font><o:p></o:p></li>
</ul>
<p class="MsoNormal" style="margin-left: 0.25in;"><font
face="Z@R44A.tmp" size="2"><span
style="font-size: 10pt; font-family: "Z@R44A.tmp";">coexist in a
network and
Cisco CallManager is not the only call controller in the network.<O:P></O:P></span></font><o:p></o:p></p>
<ul type="disc">
<li class="MsoNormal" style=""><font face="Z@R44A.tmp" size="2"><span
style="font-size: 10pt; font-family: "Z@R44A.tmp";">There are no
release dependencies between gateways and Cisco CallManager for<O:P></O:P></span></font><o:p></o:p></li>
</ul>
<p class="MsoNormal" style="margin-left: 0.25in;"><font
face="Z@R44A.tmp" size="2"><span
style="font-size: 10pt; font-family: "Z@R44A.tmp";">supporting new
voice
hardware. New hardware cards on Cisco IOS gateways become<O:P></O:P></span></font><o:p></o:p></p>
<p class="MsoNormal" style="margin-left: 0.25in;"><font
face="Z@R44A.tmp" size="2"><span
style="font-size: 10pt; font-family: "Z@R44A.tmp";">immediately
available for
use with all existing Cisco CallManager releases.<O:P></O:P></span></font><o:p></o:p></p>
<ul type="disc">
<li class="MsoNormal" style=""><font face="Z@R44A.tmp" size="2"><span
style="font-size: 10pt; font-family: "Z@R44A.tmp";">H.323 enables a
much easier migration architecture to SIP because the fundamental<O:P></O:P></span></font><o:p></o:p></li>
</ul>
<p class="MsoNormal" style="margin-left: 0.25in;"><font
face="Z@R44A.tmpOOEnc" size="2"><span
style="font-size: 10pt; font-family: "Z@R44A.tmpOOEnc";">concepts of
H.323 and
SIP</span></font><font face="Arial" size="2"><span
style="font-size: 11pt; font-family: Arial;">—</span></font><font
face="Z@R44A.tmpOOEnc" size="2"><span
style="font-size: 10pt; font-family: "Z@R44A.tmpOOEnc";">for example,
distributed control with dial-peer<O:P></O:P></span></font><o:p></o:p></p>
<p class="MsoNormal" style="margin-left: 0.25in;"><font
face="Z@R44A.tmpOOEnc" size="2"><span
style="font-size: 10pt; font-family: "Z@R44A.tmpOOEnc";">configurations</span></font><font
face="Arial" size="2"><span
style="font-size: 11pt; font-family: Arial;">—</span></font><font
face="Z@R44A.tmpOOEnc" size="2"><span
style="font-size: 10pt; font-family: "Z@R44A.tmpOOEnc";">are
the same.<O:P></O:P></span></font><o:p></o:p></p>
<ul type="disc">
<li class="MsoNormal" style=""><font face="Z@R44A.tmp" size="2"><span
style="font-size: 10pt; font-family: "Z@R44A.tmp";">Calls from IP
phones through an H323 gateway are dropped on a CallManager failover<O:P></O:P></span></font><o:p></o:p></li>
</ul>
<p class="MsoNormal" style="margin-left: 0.25in;"><font
face="Z@R44A.tmp" size="2"><span
style="font-size: 10pt; font-family: "Z@R44A.tmp";">unless SRST mode
is
enabled. With SRST enabled, the calls are preserved.</span></font><o:p></o:p></p>
<O:P></O:P>
<p class="MsoNormal" style=""><font color="navy" face="Arial" size="2"><span
style="font-size: 10pt; font-family: Arial; color: navy;"><O:P> </O:P></span></font><o:p></o:p></p>
<p class="MsoNormal" style=""><b><font face="Z@R44A.tmp" size="2"><span
style="font-size: 10pt; font-family: "Z@R44A.tmp"; font-weight: bold;">Using
MGCP as the call
control protocol to a gateway has the following advantages:<O:P></O:P></span></font></b><o:p></o:p></p>
<p class="MsoNormal" style=""><font face="Z@R44A.tmp" size="2"><span
style="font-size: 10pt; font-family: "Z@R44A.tmp";"><O:P> </O:P></span></font><o:p></o:p></p>
<ul type="disc">
<li class="MsoNormal" style=""><font face="Z@R44A.tmp" size="2"><span
style="font-size: 10pt; font-family: "Z@R44A.tmp";">Centralized
configuration, control, and download from Cisco CallManager<O:P></O:P></span></font><o:p></o:p></li>
<li class="MsoNormal" style=""><font face="Z@R44A.tmp" size="2"><span
style="font-size: 10pt; font-family: "Z@R44A.tmp";">Better feature
interaction with capabilities like caller ID and name display<O:P></O:P></span></font><o:p></o:p></li>
<li class="MsoNormal" style=""><font face="Z@R44A.tmp" size="2"><span
style="font-size: 10pt; font-family: "Z@R44A.tmp";">Easy, centralized
dial-plan management<O:P></O:P></span></font><o:p></o:p></li>
<li class="MsoNormal" style=""><font face="Z@R44A.tmp" size="2"><span
style="font-size: 10pt; font-family: "Z@R44A.tmp";">Gateway voice
security features (voice encryption) as of Cisco IOS Software Release<O:P></O:P></span></font><o:p></o:p></li>
</ul>
<p class="MsoNormal" style="margin-left: 0.25in;"><font
face="Z@R44A.tmp" size="2"><span
style="font-size: 10pt; font-family: "Z@R44A.tmp";">12.3.(5</span></font><font
face="Z@R44A.tmp" size="1"><span
style="font-size: 7.5pt; font-family: "Z@R44A.tmp";">th</span></font><font
face="Z@R44A.tmp" size="2"><span
style="font-size: 10pt; font-family: "Z@R44A.tmp";">)T<O:P></O:P></span></font><o:p></o:p></p>
<ul type="disc">
<li class="MsoNormal" style=""><font face="Z@R44A.tmp" size="2"><span
style="font-size: 10pt; font-family: "Z@R44A.tmp";">Q Signaling (QSIG)
supplementary services as supported by Cisco CallManager:<O:P></O:P></span></font><o:p></o:p></li>
</ul>
<ul type="disc">
<ul type="circle">
<li class="MsoNormal" style=""><font face="Arial" size="2"><span
style="font-size: 11pt; font-family: Arial;">—</span></font><font
face="Z@R44A.tmpOOEnc" size="2"><span
style="font-size: 10pt; font-family: "Z@R44A.tmpOOEnc";"> </span></font><font
face="Z@R44A.tmp" size="2"><span
style="font-size: 10pt; font-family: "Z@R44A.tmp";">Cisco CallManager
interconnects to a QSIG network using an MGCP gateway and<O:P></O:P></span></font><o:p></o:p></li>
</ul>
</ul>
<p class="MsoNormal" style="margin-left: 0.5in; text-indent: 0.5in;"><font
face="Z@R44A.tmp" size="2"><span
style="font-size: 10pt; font-family: "Z@R44A.tmp";">T1
or E1 PRI connections to a private integrated services network (PISN).
The<O:P></O:P></span></font><o:p></o:p></p>
<p class="MsoNormal" style="margin-left: 0.5in; text-indent: 0.5in;"><font
face="Z@R44A.tmp" size="2"><span
style="font-size: 10pt; font-family: "Z@R44A.tmp";">MGCP
gateway establishes the call connections. Using the PRI backhaul<O:P></O:P></span></font><o:p></o:p></p>
<p class="MsoNormal" style="margin-left: 0.5in; text-indent: 0.5in;"><font
face="Z@R44A.tmp" size="2"><span
style="font-size: 10pt; font-family: "Z@R44A.tmp";">mechanism,
the gateway passes the QSIG messages to the Cisco CallManager to set<O:P></O:P></span></font><o:p></o:p></p>
<p class="MsoNormal" style="margin-left: 0.5in; text-indent: 0.5in;"><font
face="Z@R44A.tmp" size="2"><span
style="font-size: 10pt; font-family: "Z@R44A.tmp";">up
QSIG calls and send QSIG messages to control features.<O:P></O:P></span></font><o:p></o:p></p>
<ul type="disc">
<ul type="circle">
<li class="MsoNormal" style=""><font face="Arial" size="2"><span
style="font-size: 11pt; font-family: Arial;">—</span></font><font
face="Z@R44A.tmpOOEnc" size="2"><span
style="font-size: 10pt; font-family: "Z@R44A.tmpOOEnc";"> </span></font><font
face="Z@R44A.tmp" size="2"><span
style="font-size: 10pt; font-family: "Z@R44A.tmp";">When a PBX is
connected to a gateway that is using QSIG via H.323, calls that are<O:P></O:P></span></font><o:p></o:p></li>
</ul>
</ul>
<p class="MsoNormal" style="margin-left: 0.5in; text-indent: 0.5in;"><font
face="Z@R44A.tmp" size="2"><span
style="font-size: 10pt; font-family: "Z@R44A.tmp";">made
between phones on the PBX and IP phones attached to the Cisco
CallManager<O:P></O:P></span></font><o:p></o:p></p>
<p class="MsoNormal" style="margin-left: 0.5in; text-indent: 0.5in;"><font
face="Z@R44A.tmp" size="2"><span
style="font-size: 10pt; font-family: "Z@R44A.tmp";">can
have only basic PRI functionality. The gateway that terminates the QSIG<O:P></O:P></span></font><o:p></o:p></p>
<p class="MsoNormal" style="margin-left: 0.5in; text-indent: 0.5in;"><font
face="Z@R44A.tmp" size="2"><span
style="font-size: 10pt; font-family: "Z@R44A.tmp";">protocol
provides only the calling line ID (CLID) and DID number, instead of
Cisco<O:P></O:P></span></font><o:p></o:p></p>
<p class="MsoNormal" style="margin-left: 0.5in; text-indent: 0.5in;"><font
face="Z@R44A.tmp" size="2"><span
style="font-size: 10pt; font-family: "Z@R44A.tmp";">CallManager
providing that information.<O:P></O:P></span></font><o:p></o:p></p>
<ul type="disc">
<li class="MsoNormal" style=""><font face="Z@R44A.tmp" size="2"><span
style="font-size: 10pt; font-family: "Z@R44A.tmp";">Enhanced call
survivability:<O:P></O:P></span></font><o:p></o:p></li>
</ul>
<ul type="disc">
<ul type="circle">
<li class="MsoNormal" style=""><font face="Arial" size="2"><span
style="font-size: 11pt; font-family: Arial;">—</span></font><font
face="Z@R44A.tmpOOEnc" size="2"><span
style="font-size: 10pt; font-family: "Z@R44A.tmpOOEnc";"> </span></font><font
face="Z@R44A.tmp" size="2"><span
style="font-size: 10pt; font-family: "Z@R44A.tmp";">Calls from IP
phones through an MGCP gateway are preserved on a CallManager<O:P></O:P></span></font><o:p></o:p></li>
</ul>
</ul>
<p class="MsoNormal" style="margin-left: 0.75in; text-indent: 0.25in;"><font
face="Z@R44A.tmp" size="2"><span
style="font-size: 10pt; font-family: "Z@R44A.tmp";">failover.
This feature avoids dropped calls when applying the monthly operating<O:P></O:P></span></font><o:p></o:p></p>
<p class="MsoNormal" style="margin-left: 0.5in; text-indent: 0.5in;"><font
face="Z@R44A.tmp" size="2"><span
style="font-size: 10pt; font-family: "Z@R44A.tmp";">system
service release on the Cisco CallManagers<O:P></O:P></span></font><o:p></o:p></p>
<ul type="disc">
<ul type="circle">
<li class="MsoNormal" style=""><font face="Arial" size="2"><span
style="font-size: 11pt; font-family: Arial;">—</span></font><font
face="Z@R44A.tmpOOEnc" size="2"><span
style="font-size: 10pt; font-family: "Z@R44A.tmpOOEnc";"> </span></font><font
face="Z@R44A.tmp" size="2"><span
style="font-size: 10pt; font-family: "Z@R44A.tmp";">In SRST mode,
calls from IP phones through an MGCP gateway are preserved on<O:P></O:P></span></font><o:p></o:p></li>
</ul>
</ul>
<p class="MsoNormal" style="margin-left: 0.5in; text-indent: 0.5in;"><font
face="Z@R44A.tmp" size="2"><span
style="font-size: 10pt; font-family: "Z@R44A.tmp";">MGCP
fallback for calls on analog or CAS circuits. Calls on ISDN circuits are<O:P></O:P></span></font><o:p></o:p></p>
<p class="MsoNormal" style="margin-left: 1in;"><font face="Z@R44A.tmp"
size="2"><span style="font-size: 10pt; font-family: "Z@R44A.tmp";">dropped
on fallback.<O:P></O:P></span></font><o:p></o:p></p>
<p class="MsoNormal" style="margin-left: 1in;"><font face="Z@R44A.tmp"
size="2"><span style="font-size: 10pt; font-family: "Z@R44A.tmp";"><O:P> </O:P></span></font><o:p></o:p></p>
<p class="MsoNormal" style="margin-left: 0.5in;"><font
face="Z@R44A.tmp" size="2"><span
style="font-size: 10pt; font-family: "Z@R44A.tmp";">HTH’s<O:P></O:P></span></font><o:p></o:p></p>
<p class="MsoNormal" style="margin-left: 0.5in;"><font
face="Z@R44A.tmp" size="2"><span
style="font-size: 10pt; font-family: "Z@R44A.tmp";"><O:P> </O:P></span></font><o:p></o:p></p>
<p class="MsoNormal" style="margin-left: 0.5in;"><font
face="Z@R44A.tmp" size="2"><span
style="font-size: 10pt; font-family: "Z@R44A.tmp";">Joe<O:P></O:P></span></font><o:p></o:p></p>
<p class="MsoNormal" style=""><font color="navy" face="Arial" size="2"><span
style="font-size: 10pt; font-family: Arial; color: navy;"><O:P> </O:P></span></font><o:p></o:p></p>
<p class="MsoNormal" style=""><font color="navy" face="Arial" size="2"><span
style="font-size: 10pt; font-family: Arial; color: navy;"><O:P> </O:P></span></font><o:p></o:p></p>
<font face="Times New Roman" size="3"><span times="" new=""></span></font>
<div>
<div class="MsoNormal" style="text-align: center;" align="center"><font
face="Times New Roman" size="3"><span style="font-size: 12pt;">
<hr tabindex="-1" align="center" size="2" width="100%"></span></font></div>
<p class="MsoNormal" style=""><b><font face="Tahoma" size="2"><span
style="font-size: 10pt; font-family: Tahoma; font-weight: bold;"></span>From:</font></b><font
size="2"><span style="font-size: 10pt;">
<a class="moz-txt-link-abbreviated" href="mailto:cisco-voip-bounces@puck.nether.net">cisco-voip-bounces@puck.nether.net</a> [<a
href="mailto:cisco-voip-bounces@puck.nether.net">mailto:cisco-voip-bounces@puck.nether.net</a>]
<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> <a
href="mailto:cisco-voip@puck.nether.net">cisco-voip@puck.nether.net</a><br>
<b><span style="font-weight: bold;">Subject:</span></b> [cisco-voip]
MGCP vs H323</span></font><o:p></o:p></p>
</div>
<span times="" new=""><O:P></O:P></span>
<p class="MsoNormal" style=""><font face="Tahoma" size="3"><span
style="font-size: 12pt; font-family: Tahoma;"><O:P> </O:P></span></font><o:p></o:p></p>
<p class="MsoNormal" style=""><font face="Arial" size="2"><span
style="font-size: 10pt; font-family: Arial;" lang="EN-GB">Does
anyone know if there is a document that lists the differences or
benefits of
using either MGCP or H323.</span></font><o:p></o:p></p>
<O:P></O:P>
<p class="MsoNormal" style=""><font face="Arial" size="2"><span
style="font-size: 10pt; font-family: Arial;" lang="EN-GB"> </span></font><o:p></o:p></p>
<O:P></O:P>
<p class="MsoNormal" style=""><font face="Arial" size="2"><span
style="font-size: 10pt; font-family: Arial;" lang="EN-GB">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><o:p></o:p></p>
<O:P></O:P>
<p class="MsoNormal" style=""><font face="Arial" size="2"><span
style="font-size: 10pt; font-family: Arial;" lang="EN-GB"> </span></font><o:p></o:p></p>
<O:P></O:P>
<p class="MsoNormal" style=""><font face="Arial" size="2"><span
style="font-size: 10pt; font-family: Arial;" lang="EN-GB">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><o:p></o:p></p>
<O:P></O:P>
<p class="MsoNormal" style=""><font face="Arial" size="2"><span
style="font-size: 10pt; font-family: Arial;" lang="EN-GB"> </span></font><o:p></o:p></p>
<O:P></O:P>
<p class="MsoNormal" style=""><font face="Arial" size="2"><span
style="font-size: 10pt; font-family: Arial;" lang="EN-GB">Just
wondering whether it might be better to go with MGCP in this instance.</span></font><o:p></o:p></p>
<O:P></O:P>
<p class="MsoNormal" style=""><font face="Arial" size="2"><span
style="font-size: 10pt; font-family: Arial;" lang="EN-GB"> </span></font><o:p></o:p></p>
<O:P></O:P>
<p class="MsoNormal" style=""><font face="Arial" size="2"><span
style="font-size: 10pt; font-family: Arial;" lang="EN-GB">Is
it easier to mask the calling numbers with MGCP?</span></font><o:p></o:p></p>
<O:P></O:P>
<p class="MsoNormal" style=""><font face="Arial" size="2"><span
style="font-size: 10pt; font-family: Arial;" lang="EN-GB"> </span></font><o:p></o:p></p>
<O:P></O:P>
<p class="MsoNormal" style=""><font face="Arial" size="2"><span
style="font-size: 10pt; font-family: Arial;" lang="EN-GB"> </span></font><o:p></o:p></p>
<O:P></O:P>
<p class="MsoNormal" style="margin-bottom: 12pt;"><font
face="Times New Roman" size="3"><span times="" new=""><O:P><span
style="font-size: 12pt;" lang="EN-GB"> </span></O:P></span><o:p></o:p></font></p>
<table class="MsoNormalTable"
style="background: white none repeat scroll 0%; -moz-background-clip: -moz-initial; -moz-background-origin: -moz-initial; -moz-background-inline-policy: -moz-initial;"
bgcolor="white" border="0" cellpadding="0">
<tbody>
<tr>
<td style="padding: 0.75pt;">
<p class="MsoNormal" style=""><font color="black"
face="Times New Roman" size="3"><span times="" new=""><span
style="font-size: 12pt; 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: <ST1:ADDRESS u1:st="on"><ST1:STREET u1:st="on"><st1:address
w:st="on"><st1:Street w:st="on">25 Luke Street</st1:Street></st1:address> <ST1:CITY
u1:st="on"><st1:City w:st="on">London</st1:City></ST1:CITY> <ST1:POSTALCODE
u1:st="on"><st1:PostalCode w:st="on">EC2A 4AR</st1:PostalCode></ST1:POSTALCODE></ST1:STREET></ST1:ADDRESS><br>
<br>
Tel: 0207 739 8200 Fax: 0207 739 7798<br>
Registered in <ST1:PLACE u1:st="on"><ST1:COUNTRY-REGION u1:st="on"><st1:country-region
w:st="on"><st1:place w:st="on">England</st1:place></st1:country-region></ST1:COUNTRY-REGION></ST1:PLACE> 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>
<ST1:CITY u1:st="on"><st1:City w:st="on">London</st1:City></ST1:CITY> Stock Exchange, International Securities Markets Association, and The <ST1:PLACE
u1:st="on"><ST1:CITY u1:st="on"><st1:City w:st="on"><st1:place
w:st="on">London</st1:place></st1:City></ST1:CITY></ST1:PLACE> 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.<O:P></O:P></span></span></font><o:p></o:p></p>
</td>
</tr>
</tbody>
</table>
<p class="MsoNormal" style=""><font face="Times New Roman" size="3"><span
times="" new=""><O:P><span style="font-size: 12pt;"> </span></O:P></span><o:p></o:p></font></p>
<div class="MsoNormal" style="text-align: center;" align="center"><font
color="gray" face="Arial" size="2"><span
style="font-size: 10pt; font-family: Arial; color: gray;">
<hr align="center" size="2" width="100%"></span></font></div>
<p><strong><b><font color="gray" face="Verdana" size="2"><span
style="font-size: 10pt; font-family: Verdana; color: gray;">CONFIDENTIALITY
STATEMENT</span></font></b></strong><o:p></o:p></p>
<O:P></O:P>
<p><font color="gray" face="Verdana" size="2"><span
style="font-size: 10pt; font-family: Verdana; color: gray;">This communication
and any attachments are
<strong><b><font face="Verdana"><span style="font-family: Verdana;">CONFIDENTIAL</span></font></b></strong>
and may be protected by one or more legal privileges. It is intended
solely for
the use of the addressee identified above. If you are not the intended
recipient, any use, disclosure, copying or distribution of
this communication is <strong><b><font face="Verdana"><span
style="font-family: Verdana;">UNAUTHORIZED</span></font></b></strong>.
Neither
this information block, the typed name of the sender, nor anything else
in this
message is intended to constitute an electronic signature unless a
specific
statement to the contrary is included in this message. If you have
received
this communication in error, please immediately contact me and delete
this communication from your computer. Thank you.</span></font><o:p></o:p></p>
<O:P></O:P>
<div class="MsoNormal" style="text-align: center;" align="center"><font
color="gray" face="Arial" size="2"><span
style="font-size: 10pt; font-family: Arial; color: gray;">
<hr align="center" size="2" width="100%"></span></font></div>
</div>
<div class="MsoNormal" style="text-align: center;" align="center"><font
color="gray" face="Arial" size="2"><span
style="font-size: 10pt; font-family: Arial; color: gray;">
<hr align="center" size="2" width="100%"></span></font></div>
<p><strong><b><font color="gray" face="Verdana" size="2"><span
style="font-size: 10pt; font-family: Verdana; color: gray;">CONFIDENTIALITY
STATEMENT</span></font></b></strong><font face="Arial" size="2"><span
style="font-size: 10pt; font-family: Arial;"><o:p></o:p></span></font></p>
<p><font color="gray" face="Verdana" size="2"><span
style="font-size: 10pt; font-family: Verdana; color: gray;">This communication
and any attachments are
<strong><b><font face="Verdana"><span style="font-family: Verdana;">CONFIDENTIAL</span></font></b></strong>
and may be protected by one or more legal privileges. It is intended
solely for
the use of the addressee identified above. If you are not the intended
recipient, any use, disclosure, copying or distribution of
this communication is <strong><b><font face="Verdana"><span
style="font-family: Verdana;">UNAUTHORIZED</span></font></b></strong>.
Neither this
information block, the typed name of the sender, nor anything else in
this
message is intended to constitute an electronic signature unless a
specific
statement to the contrary is included in this message. If you have
received
this communication in error, please immediately contact me and delete
this communication from your computer. Thank you.</span></font><font
face="Arial" size="2"><span
style="font-size: 10pt; font-family: Arial;"><o:p></o:p></span></font></p>
<div class="MsoNormal" style="text-align: center;" align="center"><font
color="gray" face="Arial" size="2"><span
style="font-size: 10pt; font-family: Arial; color: gray;">
<hr align="center" size="2" width="100%"></span></font></div>
<div>
<p class="MsoNormal"><font face="Arial" size="2"><span
style="font-size: 10pt; font-family: Arial;"><o:p> </o:p></span></font></p>
</div>
<div>
<p class="MsoNormal"><font face="Times New Roman" size="3"><span
style="font-size: 12pt;"><o:p> </o:p></span></font></p>
</div>
<div class="MsoNormal" style="text-align: center;" align="center"><font
face="Times New Roman" size="3"><span style="font-size: 12pt;">
<hr align="center" size="1" width="100%"></span></font></div>
<div>
<p class="MsoNormal"><font face="Times New Roman" size="3"><span
style="font-size: 12pt;"><o:p> </o:p></span></font></p>
</div>
<p class="MsoNormal"><font face="Times New Roman" size="3"><span
style="font-size: 12pt;"><o:p> </o:p></span></font></p>
<p><b><font face="Times New Roman" size="3"><span
style="font-size: 12pt; font-weight: bold;"><br>
<strong><b><font face="Times New Roman">Disclaimer:</font></b></strong><br>
<br>
<strong><b><font face="Times New Roman">This e-mail communication and
any
attachments may contain</font></b></strong><br>
<strong><b><font face="Times New Roman">confidential and privileged
information
and is for use by the</font></b></strong><br>
<strong><b><font face="Times New Roman">designated addressee(s) named
above
only. If you are not the</font></b></strong><br>
<strong><b><font face="Times New Roman">intended addressee, you are
hereby
notified that you have received</font></b></strong><br>
<strong><b><font face="Times New Roman">this communication in error
and that
any use or reproduction of</font></b></strong><br>
<strong><b><font face="Times New Roman">this email or its contents is
strictly
prohibited and may be</font></b></strong><br>
<strong><b><font face="Times New Roman">unlawful. If you have
received this
communication in error, please</font></b></strong><br>
<strong><b><font face="Times New Roman">notify us immediately by
replying to
this message and deleting it</font></b></strong><br>
<strong><b><font face="Times New Roman">from your computer. Thank you.</font></b></strong></span></font></b><o:p></o:p></p>
<div>
<p class="MsoNormal"><font face="Times New Roman" size="3"><span
style="font-size: 12pt;"><o:p> </o:p></span></font></p>
</div>
<div class="MsoNormal" style="text-align: center;" align="center"><font
face="Times New Roman" size="3"><span style="font-size: 12pt;">
<hr align="center" size="1" width="100%"></span></font></div>
<div>
<p class="MsoNormal"><font face="Times New Roman" size="3"><span
style="font-size: 12pt;"><o:p> </o:p></span></font></p>
</div>
<p class="MsoNormal"><font face="Times New Roman" size="3"><span
style="font-size: 12pt;"><o:p> </o:p></span></font></p>
<p><b><font face="Times New Roman" size="3"><span
style="font-size: 12pt; font-weight: bold;"><br>
<strong><b><font face="Times New Roman">Disclaimer:</font></b></strong><br>
<br>
<strong><b><font face="Times New Roman">This e-mail communication and
any
attachments may contain</font></b></strong><br>
<strong><b><font face="Times New Roman">confidential and privileged
information
and is for use by the</font></b></strong><br>
<strong><b><font face="Times New Roman">designated addressee(s) named
above
only. If you are not the</font></b></strong><br>
<strong><b><font face="Times New Roman">intended addressee, you are
hereby
notified that you have received</font></b></strong><br>
<strong><b><font face="Times New Roman">this communication in error
and that
any use or reproduction of</font></b></strong><br>
<strong><b><font face="Times New Roman">this email or its contents is
strictly
prohibited and may be</font></b></strong><br>
<strong><b><font face="Times New Roman">unlawful. If you have
received this
communication in error, please</font></b></strong><br>
<strong><b><font face="Times New Roman">notify us immediately by
replying to
this message and deleting it</font></b></strong><br>
<strong><b><font face="Times New Roman">from your computer. Thank you.</font></b></strong></span></font></b><o:p></o:p></p>
<div>
<p class="MsoNormal"><font face="Times New Roman" size="3"><span
style="font-size: 12pt;"><o:p> </o:p></span></font></p>
</div>
<div class="MsoNormal" style="text-align: center;" align="center"><font
face="Times New Roman" size="3"><span style="font-size: 12pt;">
<hr align="center" size="1" width="100%"></span></font></div>
<div>
<p class="MsoNormal"><font face="Times New Roman" size="3"><span
style="font-size: 12pt;"><o:p> </o:p></span></font></p>
</div>
<p class="MsoNormal"><font face="Times New Roman" size="3"><span
style="font-size: 12pt;"><o:p> </o:p></span></font></p>
<p><b><font face="Times New Roman" size="3"><span
style="font-size: 12pt; font-weight: bold;"><br>
<strong><b><font face="Times New Roman">Disclaimer:</font></b></strong><br>
<br>
<strong><b><font face="Times New Roman">This e-mail communication and
any
attachments may contain</font></b></strong><br>
<strong><b><font face="Times New Roman">confidential and privileged
information
and is for use by the</font></b></strong><br>
<strong><b><font face="Times New Roman">designated addressee(s) named
above
only. If you are not the</font></b></strong><br>
<strong><b><font face="Times New Roman">intended addressee, you are
hereby
notified that you have received</font></b></strong><br>
<strong><b><font face="Times New Roman">this communication in error
and that
any use or reproduction of</font></b></strong><br>
<strong><b><font face="Times New Roman">this email or its contents is
strictly
prohibited and may be</font></b></strong><br>
<strong><b><font face="Times New Roman">unlawful. If you have
received this
communication in error, please</font></b></strong><br>
<strong><b><font face="Times New Roman">notify us immediately by
replying to
this message and deleting it</font></b></strong><br>
<strong><b><font face="Times New Roman">from your computer. Thank you.</font></b></strong></span></font></b><o:p></o:p></p>
<div>
<p class="MsoNormal"><font face="Times New Roman" size="3"><span
style="font-size: 12pt;"><o:p> </o:p></span></font></p>
</div>
<div class="MsoNormal" style="text-align: center;" align="center"><font
face="Times New Roman" size="3"><span style="font-size: 12pt;">
<hr align="center" size="1" width="100%"></span></font></div>
<div>
<p class="MsoNormal"><font face="Times New Roman" size="3"><span
style="font-size: 12pt;"><o:p> </o:p></span></font></p>
</div>
<p class="MsoNormal"><font face="Times New Roman" size="3"><span
style="font-size: 12pt;"><o:p> </o:p></span></font></p>
<p><b><font face="Times New Roman" size="3"><span
style="font-size: 12pt; font-weight: bold;"><br>
<strong><b><font face="Times New Roman">Disclaimer:</font></b></strong><br>
<br>
<strong><b><font face="Times New Roman">This e-mail communication and
any
attachments may contain</font></b></strong><br>
<strong><b><font face="Times New Roman">confidential and privileged
information
and is for use by the</font></b></strong><br>
<strong><b><font face="Times New Roman">designated addressee(s) named
above
only. If you are not the</font></b></strong><br>
<strong><b><font face="Times New Roman">intended addressee, you are
hereby
notified that you have received</font></b></strong><br>
<strong><b><font face="Times New Roman">this communication in error
and that
any use or reproduction of</font></b></strong><br>
<strong><b><font face="Times New Roman">this email or its contents is
strictly
prohibited and may be</font></b></strong><br>
<strong><b><font face="Times New Roman">unlawful. If you have
received this
communication in error, please</font></b></strong><br>
<strong><b><font face="Times New Roman">notify us immediately by
replying to
this message and deleting it</font></b></strong><br>
<strong><b><font face="Times New Roman">from your computer. Thank you.</font></b></strong></span></font></b><o:p></o:p></p>
<div>
<p class="MsoNormal"><font face="Times New Roman" size="3"><span
style="font-size: 12pt;">_______________________________________________<o:p></o:p></span></font></p>
</div>
<div>
<p class="MsoNormal"><font face="Times New Roman" size="3"><span
style="font-size: 12pt;">cisco-voip mailing list<o:p></o:p></span></font></p>
</div>
<div>
<p class="MsoNormal"><font face="Times New Roman" size="3"><span
style="font-size: 12pt;"><a href="mailto:cisco-voip@puck.nether.net">cisco-voip@puck.nether.net</a><o:p></o:p></span></font></p>
</div>
<div>
<p class="MsoNormal"><font face="Times New Roman" size="3"><span
style="font-size: 12pt;"><a
href="https://puck.nether.net/mailman/listinfo/cisco-voip">https://puck.nether.net/mailman/listinfo/cisco-voip</a><o:p></o:p></span></font></p>
</div>
</div>
<p class="MsoNormal"><font face="Times New Roman" size="3"><span
style="font-size: 12pt;"><o:p> </o:p></span></font></p>
</div>
</div>
<font face="Arial" size="2">
</font>
<p><font face="Arial" size="2"><font color="#808080">
<hr></font></font></p>
<p><font face="Arial" size="2"><font color="#808080" face="Verdana"><strong>CONFIDENTIALITY
STATEMENT</strong></font></font></p>
<p><font face="Arial" size="2"><font color="#808080" face="Verdana">This communication
and any attachments are <strong>CONFIDENTIAL</strong> and may be
protected by one or more legal privileges. It is intended solely for
the use of the addressee identified above. If you are not the intended
recipient, any use, disclosure, copying or distribution of
this communication is <strong>UNAUTHORIZED</strong>. Neither this
information block, the typed name of the sender, nor anything else in
this message is intended to constitute an electronic signature unless a
specific statement to the contrary is included in this message. If you
have received this communication in error, please immediately contact
me and delete this communication from your computer. Thank you.</font></font></p>
<p><font face="Arial" size="2"><font color="#808080">
<hr></font>
</font></p>
</blockquote>
</body>
</html>