<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:st1="urn:schemas-microsoft-com:office:smarttags" xmlns="http://www.w3.org/TR/REC-html40">
<head>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=us-ascii">
<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="Street"/>
<o:SmartTagType namespaceuri="urn:schemas-microsoft-com:office:smarttags"
name="address"/>
<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="PersonName"/>
<!--[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:"Z\@R44A\.tmp";}
@font-face
{font-family:"Z\@R44A\.tmpOOEnc";}
@font-face
{font-family:Verdana;
panose-1:2 11 6 4 3 5 4 4 2 4;}
/* 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;}
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.emailstyle17
{font-family:Arial;
color:windowtext;}
span.EmailStyle19
{mso-style-type:personal;
font-family:Arial;
color:navy;}
span.EmailStyle20
{mso-style-type:personal;
font-family:Arial;
color:navy;}
span.EmailStyle21
{mso-style-type:personal;
font-family:Arial;
color:navy;}
span.EmailStyle22
{mso-style-type:personal;
font-family:Arial;
color:navy;}
span.EmailStyle23
{mso-style-type:personal;
font-family:Arial;
color:navy;}
span.EmailStyle25
{mso-style-type:personal-reply;
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 */
@list l0
{mso-list-id:2002419082;
mso-list-type:hybrid;
mso-list-template-ids:1716698836 67698689 67698691 67698693 67698689 67698691 67698693 67698689 67698691 67698693;}
@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;
font-family:Symbol;}
@list l0:level2
{mso-level-number-format:bullet;
mso-level-text:o;
mso-level-tab-stop:1.0in;
mso-level-number-position:left;
text-indent:-.25in;
font-family:"Courier New";}
@list l0:level3
{mso-level-tab-stop:1.5in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l0:level4
{mso-level-tab-stop:2.0in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l0:level5
{mso-level-tab-stop:2.5in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l0:level6
{mso-level-tab-stop:3.0in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l0:level7
{mso-level-tab-stop:3.5in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l0:level8
{mso-level-tab-stop:4.0in;
mso-level-number-position:left;
text-indent:-.25in;}
@list l0:level9
{mso-level-tab-stop:4.5in;
mso-level-number-position:left;
text-indent:-.25in;}
ol
{margin-bottom:0in;}
ul
{margin-bottom:0in;}
-->
</style>
<!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang=EN-US 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'>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></p>
<p class=MsoNormal><font size=2 color=navy face=Arial><span style='font-size:
10.0pt;font-family:Arial;color:navy'><o:p> </o:p></span></font></p>
<div>
<div class=MsoNormal align=center style='text-align:center'><font size=3
face="Times New Roman"><span 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 style='font-size:10.0pt;
font-weight:bold'>From:</span></font></b><font size=2><span 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>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> cisco-voip@puck.nether.net<br>
<b><span style='font-weight:bold'>Subject:</span></b> Re: [cisco-voip] MGCP vs
H323</span></font><font face="Times New Roman"><span style='font-family:"Times New Roman"'><o:p></o:p></span></font></p>
</div>
<p class=MsoNormal><font size=3 face=Tahoma><span style='font-size:12.0pt'><o:p> </o:p></span></font></p>
<p class=MsoNormal><font size=2 color=navy face=Arial><span style='font-size:
10.0pt;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></p>
<p class=MsoNormal><font size=2 color=navy face=Arial><span style='font-size:
10.0pt;font-family:Arial;color:navy'><o:p> </o:p></span></font></p>
<p class=MsoNormal><font size=2 color=navy face=Arial><span style='font-size:
10.0pt;font-family:Arial;color:navy'>Jason<o:p></o:p></span></font></p>
<p class=MsoNormal><font size=2 color=navy face=Arial><span style='font-size:
10.0pt;font-family:Arial;color:navy'><o:p> </o:p></span></font></p>
<div>
<div class=MsoNormal align=center style='text-align:center'><font size=3
face="Times New Roman"><span 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 style='font-size:10.0pt;
font-weight:bold'>From:</span></font></b><font size=2><span 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><st1:PersonName w:st="on">Jason Aarons</st1:PersonName>
(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> cisco-voip@puck.nether.net<br>
<b><span style='font-weight:bold'>Subject:</span></b> Re: [cisco-voip] MGCP vs
H323</span></font><font face="Times New Roman"><span style='font-family:"Times New Roman"'><o:p></o:p></span></font></p>
</div>
<p class=MsoNormal><font size=3 face=Tahoma><span style='font-size:12.0pt'><o:p> </o:p></span></font></p>
<p class=MsoNormal><font size=2 color=navy face=Arial><span style='font-size:
10.0pt;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></p>
<p class=MsoNormal><font size=2 color=navy face=Arial><span style='font-size:
10.0pt;font-family:Arial;color:navy'><o:p> </o:p></span></font></p>
<div>
<div class=MsoNormal align=center style='text-align:center'><font size=3
face="Times New Roman"><span 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 style='font-size:10.0pt;
font-weight:bold'>From:</span></font></b><font size=2><span 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>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 w:st="on">Matt
Slaga</st1:PersonName> (US); 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><font face="Times New Roman"><span style='font-family:"Times New Roman"'><o:p></o:p></span></font></p>
</div>
<p class=MsoNormal><font size=3 face=Tahoma><span style='font-size:12.0pt'><o:p> </o:p></span></font></p>
<p class=MsoNormal><font size=2 color=navy face=Arial><span style='font-size:
10.0pt;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></p>
<p class=MsoNormal><font size=2 color=navy face=Arial><span style='font-size:
10.0pt;font-family:Arial;color:navy'><o:p> </o:p></span></font></p>
<p class=MsoNormal><font size=2 color=navy face=Arial><span style='font-size:
10.0pt;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></p>
<p class=MsoNormal><font size=2 color=navy face=Arial><span style='font-size:
10.0pt;font-family:Arial;color:navy'><o:p> </o:p></span></font></p>
<p class=MsoNormal><font size=2 color=navy face=Arial><span style='font-size:
10.0pt;font-family:Arial;color:navy'>-Matt<o:p></o:p></span></font></p>
<p class=MsoNormal><font size=2 color=navy face=Arial><span style='font-size:
10.0pt;font-family:Arial;color:navy'><o:p> </o:p></span></font></p>
<div>
<div class=MsoNormal align=center style='text-align:center'><font size=3
face="Times New Roman"><span 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 style='font-size:10.0pt;
font-weight:bold'>From:</span></font></b><font size=2><span 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><st1:PersonName w:st="on">Matt Slaga</st1:PersonName> (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;
cisco-voip@puck.nether.net<br>
<b><span style='font-weight:bold'>Subject:</span></b> Re: [cisco-voip] MGCP vs
H323</span></font><font face="Times New Roman"><span style='font-family:"Times New Roman"'><o:p></o:p></span></font></p>
</div>
<p class=MsoNormal><font size=3 face=Tahoma><span style='font-size:12.0pt'><o:p> </o:p></span></font></p>
<p class=MsoNormal><font size=2 color=navy face=Arial><span 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.<o:p></o:p></span></font></p>
<p class=MsoNormal><font size=2 color=navy face=Arial><span style='font-size:
10.0pt;font-family:Arial;color:navy'><o:p> </o:p></span></font></p>
<p class=MsoNormal><font size=2 color=navy face=Arial><span 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.<o:p></o:p></span></font></p>
<p class=MsoNormal><font size=2 color=navy face=Arial><span style='font-size:
10.0pt;font-family:Arial;color:navy'><o:p> </o:p></span></font></p>
<p class=MsoNormal><font size=2 color=navy face=Arial><span 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.<o:p></o:p></span></font></p>
<p class=MsoNormal><font size=2 color=navy face=Arial><span style='font-size:
10.0pt;font-family:Arial;color:navy'><o:p> </o:p></span></font></p>
<p class=MsoNormal><font size=2 color=navy face=Arial><span 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<o:p></o:p></span></font></p>
<p class=MsoNormal><font size=2 color=navy face=Arial><span style='font-size:
10.0pt;font-family:Arial;color:navy'><o:p> </o:p></span></font></p>
<p class=MsoNormal><font size=2 color=navy face=Arial><span style='font-size:
10.0pt;font-family:Arial;color:navy'><o:p> </o:p></span></font></p>
<p class=MsoNormal><font size=2 color=navy face=Arial><span style='font-size:
10.0pt;font-family:Arial;color:navy'><o:p> </o:p></span></font></p>
<p class=MsoNormal><font size=2 color=navy face=Arial><span style='font-size:
10.0pt;font-family:Arial;color:navy'><o:p> </o:p></span></font></p>
<div>
<div class=MsoNormal align=center style='text-align:center'><font size=3
face="Times New Roman"><span 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 style='font-size:10.0pt;
font-weight:bold'>From:</span></font></b><font size=2><span 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><font face="Times New Roman"><span style='font-family:"Times New Roman"'><o:p></o:p></span></font></p>
</div>
<p class=MsoNormal><font size=3 face=Tahoma><span style='font-size:12.0pt'><o:p> </o:p></span></font></p>
<p class=MsoNormal style='text-autospace:none'><font size=2 face="Z@R44A.tmp"><span
style='font-size:11.0pt;font-family:"Z\@R44A\.tmp"'>Nick,<o:p></o:p></span></font></p>
<p class=MsoNormal style='text-autospace:none'><font size=2 face="Z@R44A.tmp"><span
style='font-size:11.0pt;font-family:"Z\@R44A\.tmp"'><o:p> </o:p></span></font></p>
<p class=MsoNormal style='text-autospace:none'><font size=2 face="Z@R44A.tmp"><span
style='font-size:11.0pt;font-family:"Z\@R44A\.tmp"'>This is from the GWGK
course book:<o:p></o:p></span></font></p>
<p class=MsoNormal style='text-autospace:none'><b><font size=2 face="Z@R44A.tmp"><span
style='font-size:11.0pt;font-family:"Z\@R44A\.tmp";font-weight:bold'><o:p> </o:p></span></font></b></p>
<p class=MsoNormal style='text-autospace:none'><b><font size=2 face="Z@R44A.tmp"><span
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:<o:p></o:p></span></font></b></p>
<p class=MsoNormal style='text-autospace:none'><font size=2 face="Z@R44A.tmp"><span
style='font-size:11.0pt;font-family:"Z\@R44A\.tmp"'><o:p> </o:p></span></font></p>
<ul style='margin-top:0in' type=disc>
<li class=MsoNormal style='mso-list:l0 level1 lfo1;text-autospace:none'><font
size=2 face="Z@R44A.tmp"><span 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.<o:p></o:p></span></font></li>
</ul>
<p class=MsoNormal style='margin-left:.25in;text-autospace:none'><font size=2
face="Z@R44A.tmp"><span 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.<o:p></o:p></span></font></p>
<ul style='margin-top:0in' type=disc>
<li class=MsoNormal style='mso-list:l0 level1 lfo1;text-autospace:none'><font
size=2 face="Z@R44A.tmp"><span style='font-size:11.0pt;font-family:"Z\@R44A\.tmp"'>H.323
provides support for fractional PRI.<o:p></o:p></span></font></li>
<li class=MsoNormal style='mso-list:l0 level1 lfo1;text-autospace:none'><font
size=2 face="Z@R44A.tmp"><span 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<o:p></o:p></span></font></li>
</ul>
<p class=MsoNormal style='margin-left:.25in;text-autospace:none'><font size=2
face="Z@R44A.tmp"><span style='font-size:11.0pt;font-family:"Z\@R44A\.tmp"'>ports
from MGCP gateways.<o:p></o:p></span></font></p>
<ul style='margin-top:0in' type=disc>
<li class=MsoNormal style='mso-list:l0 level1 lfo1;text-autospace:none'><font
size=2 face="Z@R44A.tmpOOEnc"><span 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 style='font-size:11.0pt;font-family:Arial'>—</span></font><font
size=2 face="Z@R44A.tmpOOEnc"><span style='font-size:11.0pt;font-family:
"Z\@R44A\.tmpOOEnc"'>for example, analog-Direct<o:p></o:p></span></font></li>
</ul>
<p class=MsoNormal style='margin-left:.25in;text-autospace:none'><font size=2
face="Z@R44A.tmp"><span 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<o:p></o:p></span></font></p>
<p class=MsoNormal style='margin-left:.25in;text-autospace:none'><font size=2
face="Z@R44A.tmpOOEnc"><span style='font-size:11.0pt;font-family:"Z\@R44A\.tmpOOEnc"'>R2</span></font><font
size=2 face=Arial><span style='font-size:11.0pt;font-family:Arial'>—</span></font><font
size=2 face="Z@R44A.tmpOOEnc"><span style='font-size:11.0pt;font-family:"Z\@R44A\.tmpOOEnc"'>can
be used.<o:p></o:p></span></font></p>
<ul style='margin-top:0in' type=disc>
<li class=MsoNormal style='mso-list:l0 level1 lfo1;text-autospace:none'><font
size=2 face="Z@R44A.tmp"><span style='font-size:11.0pt;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></li>
<li class=MsoNormal style='mso-list:l0 level1 lfo1;text-autospace:none'><font
size=2 face="Z@R44A.tmp"><span style='font-size:11.0pt;font-family:"Z\@R44A\.tmp"'>Gateway
resident applications like Toolkit Command Language (TCL) and voice<o:p></o:p></span></font></li>
</ul>
<p class=MsoNormal style='margin-left:.25in;text-autospace:none'><font size=2
face="Z@R44A.tmp"><span style='font-size:11.0pt;font-family:"Z\@R44A\.tmp"'>extensible
markup language (VXML) can be used. TCL and VXML applications provide<o:p></o:p></span></font></p>
<p class=MsoNormal style='margin-left:.25in;text-autospace:none'><font size=2
face="Z@R44A.tmp"><span style='font-size:11.0pt;font-family:"Z\@R44A\.tmp"'>IVR
features and call control functionality such as call forwarding, conference
calling, and<o:p></o:p></span></font></p>
<p class=MsoNormal style='margin-left:.25in;text-autospace:none'><font size=2
face="Z@R44A.tmp"><span style='font-size:11.0pt;font-family:"Z\@R44A\.tmp"'>voice
mail.<o:p></o:p></span></font></p>
<ul style='margin-top:0in' type=disc>
<li class=MsoNormal style='mso-list:l0 level1 lfo1;text-autospace:none'><font
size=2 face="Z@R44A.tmp"><span style='font-size:11.0pt;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></li>
</ul>
<p class=MsoNormal style='margin-left:.25in;text-autospace:none'><font size=2
face="Z@R44A.tmp"><span 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.<o:p></o:p></span></font></p>
<ul style='margin-top:0in' type=disc>
<li class=MsoNormal style='mso-list:l0 level1 lfo1;text-autospace:none'><font
size=2 face="Z@R44A.tmp"><span style='font-size:11.0pt;font-family:"Z\@R44A\.tmp"'>There
are no release dependencies between gateways and Cisco CallManager for<o:p></o:p></span></font></li>
</ul>
<p class=MsoNormal style='margin-left:.25in;text-autospace:none'><font size=2
face="Z@R44A.tmp"><span style='font-size:11.0pt;font-family:"Z\@R44A\.tmp"'>supporting
new voice hardware. New hardware cards on Cisco IOS gateways become<o:p></o:p></span></font></p>
<p class=MsoNormal style='margin-left:.25in;text-autospace:none'><font size=2
face="Z@R44A.tmp"><span style='font-size:11.0pt;font-family:"Z\@R44A\.tmp"'>immediately
available for use with all existing Cisco CallManager releases.<o:p></o:p></span></font></p>
<ul style='margin-top:0in' type=disc>
<li class=MsoNormal style='mso-list:l0 level1 lfo1;text-autospace:none'><font
size=2 face="Z@R44A.tmp"><span style='font-size:11.0pt;font-family:"Z\@R44A\.tmp"'>H.323
enables a much easier migration architecture to SIP because the
fundamental<o:p></o:p></span></font></li>
</ul>
<p class=MsoNormal style='margin-left:.25in;text-autospace:none'><font size=2
face="Z@R44A.tmpOOEnc"><span style='font-size:11.0pt;font-family:"Z\@R44A\.tmpOOEnc"'>concepts
of H.323 and SIP</span></font><font size=2 face=Arial><span style='font-size:
11.0pt;font-family:Arial'>—</span></font><font size=2
face="Z@R44A.tmpOOEnc"><span style='font-size:11.0pt;font-family:"Z\@R44A\.tmpOOEnc"'>for
example, distributed control with dial-peer<o:p></o:p></span></font></p>
<p class=MsoNormal style='margin-left:.25in;text-autospace:none'><font size=2
face="Z@R44A.tmpOOEnc"><span style='font-size:11.0pt;font-family:"Z\@R44A\.tmpOOEnc"'>configurations</span></font><font
size=2 face=Arial><span style='font-size:11.0pt;font-family:Arial'>—</span></font><font
size=2 face="Z@R44A.tmpOOEnc"><span style='font-size:11.0pt;font-family:"Z\@R44A\.tmpOOEnc"'>are
the same.<o:p></o:p></span></font></p>
<ul style='margin-top:0in' type=disc>
<li class=MsoNormal style='mso-list:l0 level1 lfo1;text-autospace:none'><font
size=2 face="Z@R44A.tmp"><span style='font-size:11.0pt;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></li>
</ul>
<p class=MsoNormal style='margin-left:.25in;text-autospace:none'><font size=2
face="Z@R44A.tmp"><span style='font-size:11.0pt;font-family:"Z\@R44A\.tmp"'>unless
SRST mode is enabled. With SRST enabled, the calls are preserved.</span></font><font
size=2 face="Z@R44A.tmp"><span style='font-size:10.0pt;font-family:"Z\@R44A\.tmp"'><o:p></o:p></span></font></p>
<p class=MsoNormal><font size=2 color=navy face=Arial><span style='font-size:
10.0pt;font-family:Arial;color:navy'><o:p> </o:p></span></font></p>
<p class=MsoNormal style='text-autospace:none'><b><font size=2 face="Z@R44A.tmp"><span
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:<o:p></o:p></span></font></b></p>
<p class=MsoNormal style='text-autospace:none'><font size=2 face="Z@R44A.tmp"><span
style='font-size:11.0pt;font-family:"Z\@R44A\.tmp"'><o:p> </o:p></span></font></p>
<ul style='margin-top:0in' type=disc>
<li class=MsoNormal style='mso-list:l0 level1 lfo1;text-autospace:none'><font
size=2 face="Z@R44A.tmp"><span style='font-size:11.0pt;font-family:"Z\@R44A\.tmp"'>Centralized
configuration, control, and download from Cisco CallManager<o:p></o:p></span></font></li>
<li class=MsoNormal style='mso-list:l0 level1 lfo1;text-autospace:none'><font
size=2 face="Z@R44A.tmp"><span style='font-size:11.0pt;font-family:"Z\@R44A\.tmp"'>Better
feature interaction with capabilities like caller ID and name display<o:p></o:p></span></font></li>
<li class=MsoNormal style='mso-list:l0 level1 lfo1;text-autospace:none'><font
size=2 face="Z@R44A.tmp"><span style='font-size:11.0pt;font-family:"Z\@R44A\.tmp"'>Easy,
centralized dial-plan management<o:p></o:p></span></font></li>
<li class=MsoNormal style='mso-list:l0 level1 lfo1;text-autospace:none'><font
size=2 face="Z@R44A.tmp"><span style='font-size:11.0pt;font-family:"Z\@R44A\.tmp"'>Gateway
voice security features (voice encryption) as of Cisco IOS Software
Release<o:p></o:p></span></font></li>
</ul>
<p class=MsoNormal style='margin-left:.25in;text-autospace:none'><font size=2
face="Z@R44A.tmp"><span style='font-size:11.0pt;font-family:"Z\@R44A\.tmp"'>12.3.(5</span></font><font
size=1 face="Z@R44A.tmp"><span style='font-size:7.0pt;font-family:"Z\@R44A\.tmp"'>th</span></font><font
size=2 face="Z@R44A.tmp"><span style='font-size:11.0pt;font-family:"Z\@R44A\.tmp"'>)T<o:p></o:p></span></font></p>
<ul style='margin-top:0in' type=disc>
<li class=MsoNormal style='mso-list:l0 level1 lfo1;text-autospace:none'><font
size=2 face="Z@R44A.tmp"><span style='font-size:11.0pt;font-family:"Z\@R44A\.tmp"'>Q
Signaling (QSIG) supplementary services as supported by Cisco CallManager:<o:p></o:p></span></font></li>
<ul style='margin-top:0in' type=circle>
<li class=MsoNormal style='mso-list:l0 level2 lfo1;text-autospace:none'><font
size=2 face=Arial><span style='font-size:11.0pt;font-family:Arial'>—</span></font><font
size=2 face="Z@R44A.tmpOOEnc"><span style='font-size:11.0pt;font-family:
"Z\@R44A\.tmpOOEnc"'> </span></font><font size=2 face="Z@R44A.tmp"><span
style='font-size:11.0pt;font-family:"Z\@R44A\.tmp"'>Cisco CallManager
interconnects to a QSIG network using an MGCP gateway and<o:p></o:p></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 style='font-size:11.0pt;font-family:
"Z\@R44A\.tmp"'>T1 or E1 PRI connections to a private integrated services
network (PISN). The<o:p></o:p></span></font></p>
<p class=MsoNormal style='margin-left:.5in;text-indent:.5in;text-autospace:
none'><font size=2 face="Z@R44A.tmp"><span style='font-size:11.0pt;font-family:
"Z\@R44A\.tmp"'>MGCP gateway establishes the call connections. Using the PRI
backhaul<o:p></o:p></span></font></p>
<p class=MsoNormal style='margin-left:.5in;text-indent:.5in;text-autospace:
none'><font size=2 face="Z@R44A.tmp"><span style='font-size:11.0pt;font-family:
"Z\@R44A\.tmp"'>mechanism, the gateway passes the QSIG messages to the Cisco
CallManager to set<o:p></o:p></span></font></p>
<p class=MsoNormal style='margin-left:.5in;text-indent:.5in;text-autospace:
none'><font size=2 face="Z@R44A.tmp"><span style='font-size:11.0pt;font-family:
"Z\@R44A\.tmp"'>up QSIG calls and send QSIG messages to control features.<o:p></o:p></span></font></p>
<ul style='margin-top:0in' type=disc>
<ul style='margin-top:0in' type=circle>
<li class=MsoNormal style='mso-list:l0 level2 lfo1;text-autospace:none'><font
size=2 face=Arial><span style='font-size:11.0pt;font-family:Arial'>—</span></font><font
size=2 face="Z@R44A.tmpOOEnc"><span style='font-size:11.0pt;font-family:
"Z\@R44A\.tmpOOEnc"'> </span></font><font size=2 face="Z@R44A.tmp"><span
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<o:p></o:p></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 style='font-size:11.0pt;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></p>
<p class=MsoNormal style='margin-left:.5in;text-indent:.5in;text-autospace:
none'><font size=2 face="Z@R44A.tmp"><span style='font-size:11.0pt;font-family:
"Z\@R44A\.tmp"'>can have only basic PRI functionality. The gateway that
terminates the QSIG<o:p></o:p></span></font></p>
<p class=MsoNormal style='margin-left:.5in;text-indent:.5in;text-autospace:
none'><font size=2 face="Z@R44A.tmp"><span style='font-size:11.0pt;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></p>
<p class=MsoNormal style='margin-left:.5in;text-indent:.5in;text-autospace:
none'><font size=2 face="Z@R44A.tmp"><span style='font-size:11.0pt;font-family:
"Z\@R44A\.tmp"'>CallManager providing that information.<o:p></o:p></span></font></p>
<ul style='margin-top:0in' type=disc>
<li class=MsoNormal style='mso-list:l0 level1 lfo1;text-autospace:none'><font
size=2 face="Z@R44A.tmp"><span style='font-size:11.0pt;font-family:"Z\@R44A\.tmp"'>Enhanced
call survivability:<o:p></o:p></span></font></li>
<ul style='margin-top:0in' type=circle>
<li class=MsoNormal style='mso-list:l0 level2 lfo1;text-autospace:none'><font
size=2 face=Arial><span style='font-size:11.0pt;font-family:Arial'>—</span></font><font
size=2 face="Z@R44A.tmpOOEnc"><span style='font-size:11.0pt;font-family:
"Z\@R44A\.tmpOOEnc"'> </span></font><font size=2 face="Z@R44A.tmp"><span
style='font-size:11.0pt;font-family:"Z\@R44A\.tmp"'>Calls from IP phones
through an MGCP gateway are preserved on a CallManager<o:p></o:p></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 style='font-size:11.0pt;font-family:
"Z\@R44A\.tmp"'>failover. This feature avoids dropped calls when applying the
monthly operating<o:p></o:p></span></font></p>
<p class=MsoNormal style='margin-left:.5in;text-indent:.5in;text-autospace:
none'><font size=2 face="Z@R44A.tmp"><span style='font-size:11.0pt;font-family:
"Z\@R44A\.tmp"'>system service release on the Cisco CallManagers<o:p></o:p></span></font></p>
<ul style='margin-top:0in' type=disc>
<ul style='margin-top:0in' type=circle>
<li class=MsoNormal style='mso-list:l0 level2 lfo1;text-autospace:none'><font
size=2 face=Arial><span style='font-size:11.0pt;font-family:Arial'>—</span></font><font
size=2 face="Z@R44A.tmpOOEnc"><span style='font-size:11.0pt;font-family:
"Z\@R44A\.tmpOOEnc"'> </span></font><font size=2 face="Z@R44A.tmp"><span
style='font-size:11.0pt;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></li>
</ul>
</ul>
<p class=MsoNormal style='margin-left:.5in;text-indent:.5in;text-autospace:
none'><font size=2 face="Z@R44A.tmp"><span style='font-size:11.0pt;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></p>
<p class=MsoNormal style='margin-left:1.0in;text-autospace:none'><font size=2
face="Z@R44A.tmp"><span style='font-size:11.0pt;font-family:"Z\@R44A\.tmp"'>dropped
on fallback.<o:p></o:p></span></font></p>
<p class=MsoNormal style='margin-left:1.0in;text-autospace:none'><font size=2
face="Z@R44A.tmp"><span style='font-size:11.0pt;font-family:"Z\@R44A\.tmp"'><o:p> </o:p></span></font></p>
<p class=MsoNormal style='margin-left:.5in;text-autospace:none'><font size=2
face="Z@R44A.tmp"><span style='font-size:11.0pt;font-family:"Z\@R44A\.tmp"'>HTH’s<o:p></o:p></span></font></p>
<p class=MsoNormal style='margin-left:.5in;text-autospace:none'><font size=2
face="Z@R44A.tmp"><span style='font-size:11.0pt;font-family:"Z\@R44A\.tmp"'><o:p> </o:p></span></font></p>
<p class=MsoNormal style='margin-left:.5in;text-autospace:none'><font size=2
face="Z@R44A.tmp"><span style='font-size:11.0pt;font-family:"Z\@R44A\.tmp"'>Joe<o:p></o:p></span></font></p>
<p class=MsoNormal><font size=2 color=navy face=Arial><span style='font-size:
10.0pt;font-family:Arial;color:navy'><o:p> </o:p></span></font></p>
<p class=MsoNormal><font size=2 color=navy face=Arial><span style='font-size:
10.0pt;font-family:Arial;color:navy'><o:p> </o:p></span></font></p>
<div>
<div class=MsoNormal align=center style='text-align:center'><font size=3
face="Times New Roman"><span 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 style='font-size:10.0pt;
font-weight:bold'>From:</span></font></b><font size=2><span 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><font
face="Times New Roman"><span style='font-family:"Times New Roman"'><o:p></o:p></span></font></p>
</div>
<p class=MsoNormal><font size=3 face=Tahoma><span style='font-size:12.0pt'><o:p> </o:p></span></font></p>
<p class=MsoNormal><font size=2 face=Arial><span lang=EN-GB 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><span
lang=EN-GB><o:p></o:p></span></p>
<p class=MsoNormal><font size=2 face=Arial><span lang=EN-GB style='font-size:
10.0pt;font-family:Arial'> </span></font><span lang=EN-GB><o:p></o:p></span></p>
<p class=MsoNormal><font size=2 face=Arial><span lang=EN-GB 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><span
lang=EN-GB><o:p></o:p></span></p>
<p class=MsoNormal><font size=2 face=Arial><span lang=EN-GB style='font-size:
10.0pt;font-family:Arial'> </span></font><span lang=EN-GB><o:p></o:p></span></p>
<p class=MsoNormal><font size=2 face=Arial><span lang=EN-GB 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><span lang=EN-GB><o:p></o:p></span></p>
<p class=MsoNormal><font size=2 face=Arial><span lang=EN-GB style='font-size:
10.0pt;font-family:Arial'> </span></font><span lang=EN-GB><o:p></o:p></span></p>
<p class=MsoNormal><font size=2 face=Arial><span lang=EN-GB style='font-size:
10.0pt;font-family:Arial'>Just wondering whether it might be better to go with
MGCP in this instance.</span></font><span lang=EN-GB><o:p></o:p></span></p>
<p class=MsoNormal><font size=2 face=Arial><span lang=EN-GB style='font-size:
10.0pt;font-family:Arial'> </span></font><span lang=EN-GB><o:p></o:p></span></p>
<p class=MsoNormal><font size=2 face=Arial><span lang=EN-GB style='font-size:
10.0pt;font-family:Arial'>Is it easier to mask the calling numbers with MGCP?</span></font><span
lang=EN-GB><o:p></o:p></span></p>
<p class=MsoNormal><font size=2 face=Arial><span lang=EN-GB style='font-size:
10.0pt;font-family:Arial'> </span></font><span lang=EN-GB><o:p></o:p></span></p>
<p class=MsoNormal><font size=2 face=Arial><span lang=EN-GB style='font-size:
10.0pt;font-family:Arial'> </span></font><span lang=EN-GB><o:p></o:p></span></p>
<p class=MsoNormal style='margin-bottom:12.0pt'><font size=3
face="Times New Roman"><span lang=EN-GB style='font-size:12.0pt;font-family:
"Times New Roman"'><o:p> </o:p></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: <st1:address w:st="on"><st1:Street w:st="on">25 Luke Street</st1:Street> <st1:City
w:st="on">London</st1:City> <st1:PostalCode w:st="on">EC2A 4AR</st1:PostalCode></st1:address><br>
<br>
Tel: 0207 739 8200 Fax: 0207 739 7798<br>
Registered in <st1:place w:st="on"><st1:country-region w:st="on">England</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 w:st="on">London</st1:City> Stock Exchange, International Securities Markets Association, and The <st1:place
w:st="on"><st1:City w:st="on">London</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></font></p>
</td>
</tr>
</table>
<p class=MsoNormal><font size=3 face="Times New Roman"><span style='font-size:
12.0pt;font-family:"Times New Roman"'><o:p> </o:p></span></font></p>
<div class=MsoNormal align=center style='text-align:center'><font size=2
color=gray face=Arial><span style='font-size:10.0pt;font-family:Arial;
color:gray'>
<hr size=2 width="100%" align=center>
</span></font></div>
<p><strong><b><font size=2 color=gray face=Verdana><span style='font-size:10.0pt;
font-family:Verdana;color:gray'>CONFIDENTIALITY STATEMENT</span></font></b></strong><font
size=2 face=Arial><span style='font-size:10.0pt;font-family:Arial'><o:p></o:p></span></font></p>
<p><font size=2 color=gray face=Verdana><span style='font-size:10.0pt;
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
size=2 face=Arial><span style='font-size:10.0pt;font-family:Arial'><o:p></o:p></span></font></p>
<div class=MsoNormal align=center style='text-align:center'><font size=2
color=gray face=Arial><span style='font-size:10.0pt;font-family:Arial;
color:gray'>
<hr size=2 width="100%" align=center>
</span></font></div>
</div>
</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>
<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></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></HTML>