<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML xmlns="http://www.w3.org/TR/REC-html40" 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"><HEAD>
<META http-equiv=Content-Type content="text/html; charset=us-ascii">
<META content="MSHTML 6.00.2900.2180" name=GENERATOR><!--[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 name="place"
namespaceuri="urn:schemas-microsoft-com:office:smarttags"></o:SmartTagType><o:SmartTagType
name="country-region"
namespaceuri="urn:schemas-microsoft-com:office:smarttags"></o:SmartTagType><o:SmartTagType
name="address"
namespaceuri="urn:schemas-microsoft-com:office:smarttags"></o:SmartTagType><o:SmartTagType
name="PostalCode"
namespaceuri="urn:schemas-microsoft-com:office:smarttags"></o:SmartTagType><o:SmartTagType
name="City"
namespaceuri="urn:schemas-microsoft-com:office:smarttags"></o:SmartTagType><o:SmartTagType
name="Street"
namespaceuri="urn:schemas-microsoft-com:office:smarttags"></o:SmartTagType><o:SmartTagType
name="PersonName"
namespaceuri="urn:schemas-microsoft-com:office:smarttags"></o:SmartTagType><!--[if !mso]>
<STYLE>st1\:* {
BEHAVIOR: url(#default#ieooui)
}
</STYLE>
<![endif]-->
<STYLE>@font-face {
font-family: Tahoma;
}
@font-face {
font-family: Z@R44A.tmp;
}
@font-face {
font-family: Z@R44A.tmpOOEnc;
}
@font-face {
font-family: Verdana;
}
@page Section1 {size: 595.3pt 841.9pt; margin: 1.0in 1.25in 1.0in 1.25in; }
P.MsoNormal {
FONT-SIZE: 12pt; MARGIN: 0in 0in 0pt; FONT-FAMILY: Tahoma
}
LI.MsoNormal {
FONT-SIZE: 12pt; MARGIN: 0in 0in 0pt; FONT-FAMILY: Tahoma
}
DIV.MsoNormal {
FONT-SIZE: 12pt; MARGIN: 0in 0in 0pt; FONT-FAMILY: Tahoma
}
A:link {
COLOR: blue; TEXT-DECORATION: underline
}
SPAN.MsoHyperlink {
COLOR: blue; TEXT-DECORATION: underline
}
A:visited {
COLOR: purple; TEXT-DECORATION: underline
}
SPAN.MsoHyperlinkFollowed {
COLOR: purple; TEXT-DECORATION: underline
}
P {
FONT-SIZE: 12pt; MARGIN-LEFT: 0in; MARGIN-RIGHT: 0in; FONT-FAMILY: "Times New Roman"; mso-margin-top-alt: auto; mso-margin-bottom-alt: auto
}
SPAN.emailstyle17 {
COLOR: windowtext; FONT-FAMILY: Arial
}
SPAN.EmailStyle19 {
COLOR: navy; FONT-FAMILY: Arial; mso-style-type: personal
}
SPAN.EmailStyle20 {
COLOR: navy; FONT-FAMILY: Arial; mso-style-type: personal
}
SPAN.EmailStyle21 {
COLOR: navy; FONT-FAMILY: Arial; mso-style-type: personal
}
SPAN.EmailStyle22 {
COLOR: navy; FONT-FAMILY: Arial; mso-style-type: personal
}
SPAN.EmailStyle23 {
COLOR: navy; FONT-FAMILY: Arial; mso-style-type: personal
}
SPAN.EmailStyle24 {
COLOR: navy; FONT-FAMILY: Arial; mso-style-type: personal
}
SPAN.EmailStyle25 {
COLOR: navy; FONT-FAMILY: Arial; mso-style-type: personal
}
SPAN.EmailStyle27 {
COLOR: navy; FONT-FAMILY: Arial; mso-style-type: personal-reply
}
DIV.Section1 {
page: Section1
}
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 vLink=purple link=blue>
<DIV dir=ltr align=left><SPAN class=707512419-30082006><FONT face=Arial
color=#0000ff size=2>MGCP and CVP/H.323 cannot be compatible at this
time.</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=707512419-30082006><FONT face=Arial
color=#0000ff size=2></FONT></SPAN> </DIV>
<DIV dir=ltr align=left><SPAN class=707512419-30082006><FONT face=Arial
color=#0000ff size=2>
<DIV dir=ltr align=left><SPAN class=707512419-30082006><FONT face=Arial
color=#0000ff size=2>CVP uses voicexml and tcl in the routers to intercept and
treat calls.</FONT></SPAN></DIV></FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=707512419-30082006><FONT face=Arial
color=#0000ff size=2></FONT></SPAN> </DIV>
<DIV dir=ltr align=left><SPAN class=707512419-30082006><FONT face=Arial
color=#0000ff size=2>MGCP takes full control of the connection and backhauls all
Q931 to CallManager.</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=707512419-30082006><FONT face=Arial
color=#0000ff size=2></FONT></SPAN> </DIV>
<DIV dir=ltr align=left><SPAN class=707512419-30082006><FONT face=Arial
color=#0000ff size=2>If MGCP is in operation, voicexml and TCL never see a q.931
message to act upon.</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=707512419-30082006><FONT face=Arial
color=#0000ff size=2></FONT></SPAN> </DIV>
<DIV dir=ltr align=left><SPAN class=707512419-30082006><FONT face=Arial
color=#0000ff size=2>If someday in the future CallManager itself was capable of
VXML, this would solve the issue. Otherwise you'd need to attempt CVP
-> CRS IVR, and while CRS does "support" VXML, I wouldn't say it'd work as
well as VXML on an H.323 gateway.</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=707512419-30082006><FONT face=Arial
color=#0000ff size=2></FONT></SPAN> </DIV><FONT face=Arial color=#0000ff
size=2></FONT><BR>
<BLOCKQUOTE dir=ltr
style="PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #0000ff 2px solid; MARGIN-RIGHT: 0px">
<DIV class=OutlookMessageHeader lang=en-us dir=ltr align=left>
<HR tabIndex=-1>
<FONT face=Tahoma size=2><B>From:</B> cisco-voip-bounces@puck.nether.net
[mailto:cisco-voip-bounces@puck.nether.net] <B>On Behalf Of </B>Jason
Burwell<BR><B>Sent:</B> Wednesday, August 30, 2006 1:15 PM<BR><B>To:</B> Jason
Aarons (US); Matt Slaga (US); cisco-voip@puck.nether.net<BR><B>Subject:</B>
Re: [cisco-voip] MGCP vs H323<BR></FONT><BR></DIV>
<DIV></DIV>
<DIV class=Section1>
<P class=MsoNormal><FONT face=Arial color=navy size=2><SPAN
style="FONT-SIZE: 10pt; COLOR: navy; FONT-FAMILY: Arial">I know there is a
limitation with call manager supporting both types of facility ie which is why
Calling Party name does not work on 4ESS protocol however TAC said that
problem is fixed in CCM 4.2 by adding a Facility IE check box on the gateway
setup. I am starting to get concerned with moving from MGCP to H323, I can’t
believe that CVP is not compatible with MGCP.<o:p></o:p></SPAN></FONT></P>
<P class=MsoNormal><FONT face=Arial color=navy size=2><SPAN
style="FONT-SIZE: 10pt; COLOR: navy; FONT-FAMILY: Arial"><o:p> </o:p></SPAN></FONT></P>
<P class=MsoNormal><FONT face=Arial color=navy size=2><SPAN
style="FONT-SIZE: 10pt; COLOR: navy; FONT-FAMILY: Arial">Jason<o:p></o:p></SPAN></FONT></P>
<P class=MsoNormal><FONT face=Arial color=navy size=2><SPAN
style="FONT-SIZE: 10pt; COLOR: navy; FONT-FAMILY: Arial"><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; FONT-FAMILY: 'Times New Roman'">
<HR tabIndex=-1 align=center width="100%" SIZE=2>
</SPAN></FONT></DIV>
<P class=MsoNormal><B><FONT face=Tahoma size=2><SPAN
style="FONT-WEIGHT: bold; FONT-SIZE: 10pt">From:</SPAN></FONT></B><FONT
size=2><SPAN style="FONT-SIZE: 10pt"> Jason Aarons (US)
[mailto:jason.aarons@us.didata.com] <BR><B><SPAN
style="FONT-WEIGHT: bold">Sent:</SPAN></B> Wednesday, August 30, 2006 2:09
PM<BR><B><SPAN style="FONT-WEIGHT: bold">To:</SPAN></B> Matt Slaga (US);
<st1:PersonName w:st="on">Jason Burwell</st1:PersonName>;
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 face=Tahoma size=3><SPAN
style="FONT-SIZE: 12pt"><o:p> </o:p></SPAN></FONT></P>
<P class=MsoNormal><FONT face=Arial color=navy size=2><SPAN
style="FONT-SIZE: 10pt; COLOR: navy; FONT-FAMILY: Arial">So it’s a ccapi issue
with IOS not sending it along? I kept thinking the CallManager BU would have
to fix it versus IOS team. I’ve never look at a sniffer trace to see if
the name goes across to CallManager/H323.<o:p></o:p></SPAN></FONT></P>
<P class=MsoNormal><FONT face=Arial color=navy size=2><SPAN
style="FONT-SIZE: 10pt; COLOR: navy; FONT-FAMILY: Arial"><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; FONT-FAMILY: 'Times New Roman'">
<HR tabIndex=-1 align=center width="100%" SIZE=2>
</SPAN></FONT></DIV>
<P class=MsoNormal><B><FONT face=Tahoma size=2><SPAN
style="FONT-WEIGHT: bold; FONT-SIZE: 10pt">From:</SPAN></FONT></B><FONT
size=2><SPAN style="FONT-SIZE: 10pt"> cisco-voip-bounces@puck.nether.net
[mailto:cisco-voip-bounces@puck.nether.net] <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> <st1:PersonName
w:st="on">Jason Burwell</st1:PersonName>;
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 face=Tahoma size=3><SPAN
style="FONT-SIZE: 12pt"><o:p> </o:p></SPAN></FONT></P>
<P class=MsoNormal><FONT face=Arial color=navy size=2><SPAN
style="FONT-SIZE: 10pt; COLOR: navy; FONT-FAMILY: Arial">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 face=Arial color=navy size=2><SPAN
style="FONT-SIZE: 10pt; COLOR: navy; FONT-FAMILY: Arial"><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; FONT-FAMILY: 'Times New Roman'">
<HR tabIndex=-1 align=center width="100%" SIZE=2>
</SPAN></FONT></DIV>
<P class=MsoNormal><B><FONT face=Tahoma size=2><SPAN
style="FONT-WEIGHT: bold; FONT-SIZE: 10pt">From:</SPAN></FONT></B><FONT
size=2><SPAN style="FONT-SIZE: 10pt"> 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 Burwell</st1:PersonName><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 face=Tahoma size=3><SPAN
style="FONT-SIZE: 12pt"><o:p> </o:p></SPAN></FONT></P>
<P class=MsoNormal><FONT face=Arial color=navy size=2><SPAN
style="FONT-SIZE: 10pt; COLOR: navy; FONT-FAMILY: Arial">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 face=Arial color=navy size=2><SPAN
style="FONT-SIZE: 10pt; COLOR: navy; FONT-FAMILY: Arial"><o:p> </o:p></SPAN></FONT></P>
<P class=MsoNormal><FONT face=Arial color=navy size=2><SPAN
style="FONT-SIZE: 10pt; COLOR: navy; FONT-FAMILY: Arial">Jason<o:p></o:p></SPAN></FONT></P>
<P class=MsoNormal><FONT face=Arial color=navy size=2><SPAN
style="FONT-SIZE: 10pt; COLOR: navy; FONT-FAMILY: Arial"><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; FONT-FAMILY: 'Times New Roman'">
<HR tabIndex=-1 align=center width="100%" SIZE=2>
</SPAN></FONT></DIV>
<P class=MsoNormal><B><FONT face=Tahoma size=2><SPAN
style="FONT-WEIGHT: bold; FONT-SIZE: 10pt">From:</SPAN></FONT></B><FONT
size=2><SPAN style="FONT-SIZE: 10pt"> 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 face=Tahoma size=3><SPAN
style="FONT-SIZE: 12pt"><o:p> </o:p></SPAN></FONT></P>
<P class=MsoNormal><FONT face=Arial color=navy size=2><SPAN
style="FONT-SIZE: 10pt; COLOR: navy; FONT-FAMILY: Arial">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 face=Arial color=navy size=2><SPAN
style="FONT-SIZE: 10pt; COLOR: navy; FONT-FAMILY: Arial"><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; FONT-FAMILY: 'Times New Roman'">
<HR tabIndex=-1 align=center width="100%" SIZE=2>
</SPAN></FONT></DIV>
<P class=MsoNormal><B><FONT face=Tahoma size=2><SPAN
style="FONT-WEIGHT: bold; FONT-SIZE: 10pt">From:</SPAN></FONT></B><FONT
size=2><SPAN style="FONT-SIZE: 10pt"> 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 face=Tahoma size=3><SPAN
style="FONT-SIZE: 12pt"><o:p> </o:p></SPAN></FONT></P>
<P class=MsoNormal><FONT face=Arial color=navy size=2><SPAN
style="FONT-SIZE: 10pt; COLOR: navy; FONT-FAMILY: Arial">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 face=Arial color=navy size=2><SPAN
style="FONT-SIZE: 10pt; COLOR: navy; FONT-FAMILY: Arial"><o:p> </o:p></SPAN></FONT></P>
<P class=MsoNormal><FONT face=Arial color=navy size=2><SPAN
style="FONT-SIZE: 10pt; COLOR: navy; FONT-FAMILY: Arial">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 face=Arial color=navy size=2><SPAN
style="FONT-SIZE: 10pt; COLOR: navy; FONT-FAMILY: Arial"><o:p> </o:p></SPAN></FONT></P>
<P class=MsoNormal><FONT face=Arial color=navy size=2><SPAN
style="FONT-SIZE: 10pt; COLOR: navy; FONT-FAMILY: Arial">-Matt<o:p></o:p></SPAN></FONT></P>
<P class=MsoNormal><FONT face=Arial color=navy size=2><SPAN
style="FONT-SIZE: 10pt; COLOR: navy; FONT-FAMILY: Arial"><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; FONT-FAMILY: 'Times New Roman'">
<HR tabIndex=-1 align=center width="100%" SIZE=2>
</SPAN></FONT></DIV>
<P class=MsoNormal><B><FONT face=Tahoma size=2><SPAN
style="FONT-WEIGHT: bold; FONT-SIZE: 10pt">From:</SPAN></FONT></B><FONT
size=2><SPAN style="FONT-SIZE: 10pt"> 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 face=Tahoma size=3><SPAN
style="FONT-SIZE: 12pt"><o:p> </o:p></SPAN></FONT></P>
<P class=MsoNormal><FONT face=Arial color=navy size=2><SPAN
style="FONT-SIZE: 10pt; COLOR: navy; FONT-FAMILY: Arial">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 face=Arial color=navy size=2><SPAN
style="FONT-SIZE: 10pt; COLOR: navy; FONT-FAMILY: Arial"><o:p> </o:p></SPAN></FONT></P>
<P class=MsoNormal><FONT face=Arial color=navy size=2><SPAN
style="FONT-SIZE: 10pt; COLOR: navy; FONT-FAMILY: Arial">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 face=Arial color=navy size=2><SPAN
style="FONT-SIZE: 10pt; COLOR: navy; FONT-FAMILY: Arial"><o:p> </o:p></SPAN></FONT></P>
<P class=MsoNormal><FONT face=Arial color=navy size=2><SPAN
style="FONT-SIZE: 10pt; COLOR: navy; FONT-FAMILY: Arial">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 face=Arial color=navy size=2><SPAN
style="FONT-SIZE: 10pt; COLOR: navy; FONT-FAMILY: Arial"><o:p> </o:p></SPAN></FONT></P>
<P class=MsoNormal><FONT face=Arial color=navy size=2><SPAN
style="FONT-SIZE: 10pt; COLOR: navy; FONT-FAMILY: Arial">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 face=Arial color=navy size=2><SPAN
style="FONT-SIZE: 10pt; COLOR: navy; FONT-FAMILY: Arial"><o:p> </o:p></SPAN></FONT></P>
<P class=MsoNormal><FONT face=Arial color=navy size=2><SPAN
style="FONT-SIZE: 10pt; COLOR: navy; FONT-FAMILY: Arial"><o:p> </o:p></SPAN></FONT></P>
<P class=MsoNormal><FONT face=Arial color=navy size=2><SPAN
style="FONT-SIZE: 10pt; COLOR: navy; FONT-FAMILY: Arial"><o:p> </o:p></SPAN></FONT></P>
<P class=MsoNormal><FONT face=Arial color=navy size=2><SPAN
style="FONT-SIZE: 10pt; COLOR: navy; FONT-FAMILY: Arial"><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; FONT-FAMILY: 'Times New Roman'">
<HR tabIndex=-1 align=center width="100%" SIZE=2>
</SPAN></FONT></DIV>
<P class=MsoNormal><B><FONT face=Tahoma size=2><SPAN
style="FONT-WEIGHT: bold; FONT-SIZE: 10pt">From:</SPAN></FONT></B><FONT
size=2><SPAN style="FONT-SIZE: 10pt"> 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 face=Tahoma size=3><SPAN
style="FONT-SIZE: 12pt"><o:p> </o:p></SPAN></FONT></P>
<P class=MsoNormal><FONT face=Z@R44A.tmp size=2><SPAN
style="FONT-SIZE: 11pt; FONT-FAMILY: 'Z@R44A.tmp'">Nick,<o:p></o:p></SPAN></FONT></P>
<P class=MsoNormal><FONT face=Z@R44A.tmp size=2><SPAN
style="FONT-SIZE: 11pt; FONT-FAMILY: 'Z@R44A.tmp'"><o:p> </o:p></SPAN></FONT></P>
<P class=MsoNormal><FONT face=Z@R44A.tmp size=2><SPAN
style="FONT-SIZE: 11pt; FONT-FAMILY: 'Z@R44A.tmp'">This is from the GWGK
course book:<o:p></o:p></SPAN></FONT></P>
<P class=MsoNormal><B><FONT face=Z@R44A.tmp size=2><SPAN
style="FONT-WEIGHT: bold; FONT-SIZE: 11pt; FONT-FAMILY: 'Z@R44A.tmp'"><o:p> </o:p></SPAN></FONT></B></P>
<P class=MsoNormal><B><FONT face=Z@R44A.tmp size=2><SPAN
style="FONT-WEIGHT: bold; FONT-SIZE: 11pt; FONT-FAMILY: 'Z@R44A.tmp'">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><FONT face=Z@R44A.tmp size=2><SPAN
style="FONT-SIZE: 11pt; 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"><FONT face=Z@R44A.tmp
size=2><SPAN style="FONT-SIZE: 11pt; 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: 0.25in"><FONT face=Z@R44A.tmp
size=2><SPAN style="FONT-SIZE: 11pt; 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"><FONT face=Z@R44A.tmp
size=2><SPAN style="FONT-SIZE: 11pt; FONT-FAMILY: 'Z@R44A.tmp'">H.323
provides support for fractional PRI.<o:p></o:p></SPAN></FONT>
<LI class=MsoNormal style="mso-list: l0 level1 lfo1"><FONT face=Z@R44A.tmp
size=2><SPAN style="FONT-SIZE: 11pt; 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: 0.25in"><FONT face=Z@R44A.tmp
size=2><SPAN style="FONT-SIZE: 11pt; 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"><FONT
face=Z@R44A.tmpOOEnc size=2><SPAN
style="FONT-SIZE: 11pt; 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: 11pt; FONT-FAMILY: 'Z@R44A.tmpOOEnc'">for example,
analog-Direct<o:p></o:p></SPAN></FONT> </LI></UL>
<P class=MsoNormal style="MARGIN-LEFT: 0.25in"><FONT face=Z@R44A.tmp
size=2><SPAN style="FONT-SIZE: 11pt; 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: 0.25in"><FONT face=Z@R44A.tmpOOEnc
size=2><SPAN
style="FONT-SIZE: 11pt; 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: 11pt; 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"><FONT face=Z@R44A.tmp
size=2><SPAN style="FONT-SIZE: 11pt; 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 class=MsoNormal style="mso-list: l0 level1 lfo1"><FONT face=Z@R44A.tmp
size=2><SPAN style="FONT-SIZE: 11pt; 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: 0.25in"><FONT face=Z@R44A.tmp
size=2><SPAN style="FONT-SIZE: 11pt; 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: 0.25in"><FONT face=Z@R44A.tmp
size=2><SPAN style="FONT-SIZE: 11pt; 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: 0.25in"><FONT face=Z@R44A.tmp
size=2><SPAN style="FONT-SIZE: 11pt; 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"><FONT face=Z@R44A.tmp
size=2><SPAN style="FONT-SIZE: 11pt; 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: 0.25in"><FONT face=Z@R44A.tmp
size=2><SPAN style="FONT-SIZE: 11pt; 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"><FONT face=Z@R44A.tmp
size=2><SPAN style="FONT-SIZE: 11pt; 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: 0.25in"><FONT face=Z@R44A.tmp
size=2><SPAN style="FONT-SIZE: 11pt; 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: 0.25in"><FONT face=Z@R44A.tmp
size=2><SPAN style="FONT-SIZE: 11pt; 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"><FONT face=Z@R44A.tmp
size=2><SPAN style="FONT-SIZE: 11pt; 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: 0.25in"><FONT face=Z@R44A.tmpOOEnc
size=2><SPAN style="FONT-SIZE: 11pt; 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: 11pt; 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: 0.25in"><FONT face=Z@R44A.tmpOOEnc
size=2><SPAN
style="FONT-SIZE: 11pt; 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: 11pt; 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"><FONT face=Z@R44A.tmp
size=2><SPAN style="FONT-SIZE: 11pt; 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: 0.25in"><FONT face=Z@R44A.tmp
size=2><SPAN style="FONT-SIZE: 11pt; FONT-FAMILY: 'Z@R44A.tmp'">unless SRST
mode is enabled. With SRST enabled, the calls are
preserved.</SPAN></FONT><FONT face=Z@R44A.tmp size=2><SPAN
style="FONT-SIZE: 10pt; FONT-FAMILY: 'Z@R44A.tmp'"><o:p></o:p></SPAN></FONT></P>
<P class=MsoNormal><FONT face=Arial color=navy size=2><SPAN
style="FONT-SIZE: 10pt; COLOR: navy; FONT-FAMILY: Arial"><o:p> </o:p></SPAN></FONT></P>
<P class=MsoNormal><B><FONT face=Z@R44A.tmp size=2><SPAN
style="FONT-WEIGHT: bold; FONT-SIZE: 11pt; FONT-FAMILY: 'Z@R44A.tmp'">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><FONT face=Z@R44A.tmp size=2><SPAN
style="FONT-SIZE: 11pt; 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"><FONT face=Z@R44A.tmp
size=2><SPAN style="FONT-SIZE: 11pt; FONT-FAMILY: 'Z@R44A.tmp'">Centralized
configuration, control, and download from Cisco
CallManager<o:p></o:p></SPAN></FONT>
<LI class=MsoNormal style="mso-list: l0 level1 lfo1"><FONT face=Z@R44A.tmp
size=2><SPAN style="FONT-SIZE: 11pt; FONT-FAMILY: 'Z@R44A.tmp'">Better
feature interaction with capabilities like caller ID and name
display<o:p></o:p></SPAN></FONT>
<LI class=MsoNormal style="mso-list: l0 level1 lfo1"><FONT face=Z@R44A.tmp
size=2><SPAN style="FONT-SIZE: 11pt; FONT-FAMILY: 'Z@R44A.tmp'">Easy,
centralized dial-plan management<o:p></o:p></SPAN></FONT>
<LI class=MsoNormal style="mso-list: l0 level1 lfo1"><FONT face=Z@R44A.tmp
size=2><SPAN style="FONT-SIZE: 11pt; 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: 0.25in"><FONT face=Z@R44A.tmp
size=2><SPAN
style="FONT-SIZE: 11pt; FONT-FAMILY: 'Z@R44A.tmp'">12.3.(5</SPAN></FONT><FONT
face=Z@R44A.tmp size=1><SPAN
style="FONT-SIZE: 7pt; FONT-FAMILY: 'Z@R44A.tmp'">th</SPAN></FONT><FONT
face=Z@R44A.tmp size=2><SPAN
style="FONT-SIZE: 11pt; 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"><FONT face=Z@R44A.tmp
size=2><SPAN style="FONT-SIZE: 11pt; FONT-FAMILY: 'Z@R44A.tmp'">Q Signaling
(QSIG) supplementary services as supported by Cisco
CallManager:<o:p></o:p></SPAN></FONT>
<UL style="MARGIN-TOP: 0in" type=circle>
<LI class=MsoNormal style="mso-list: l0 level2 lfo1"><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: 11pt; FONT-FAMILY: 'Z@R44A.tmpOOEnc'">
</SPAN></FONT><FONT face=Z@R44A.tmp size=2><SPAN
style="FONT-SIZE: 11pt; 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></LI></UL>
<P class=MsoNormal style="MARGIN-LEFT: 0.5in; TEXT-INDENT: 0.5in"><FONT
face=Z@R44A.tmp size=2><SPAN
style="FONT-SIZE: 11pt; 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: 0.5in; TEXT-INDENT: 0.5in"><FONT
face=Z@R44A.tmp size=2><SPAN
style="FONT-SIZE: 11pt; 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: 0.5in; TEXT-INDENT: 0.5in"><FONT
face=Z@R44A.tmp size=2><SPAN
style="FONT-SIZE: 11pt; 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: 0.5in; TEXT-INDENT: 0.5in"><FONT
face=Z@R44A.tmp size=2><SPAN
style="FONT-SIZE: 11pt; 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"><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: 11pt; FONT-FAMILY: 'Z@R44A.tmpOOEnc'">
</SPAN></FONT><FONT face=Z@R44A.tmp size=2><SPAN
style="FONT-SIZE: 11pt; 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: 0.5in; TEXT-INDENT: 0.5in"><FONT
face=Z@R44A.tmp size=2><SPAN
style="FONT-SIZE: 11pt; 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: 0.5in; TEXT-INDENT: 0.5in"><FONT
face=Z@R44A.tmp size=2><SPAN
style="FONT-SIZE: 11pt; 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: 0.5in; TEXT-INDENT: 0.5in"><FONT
face=Z@R44A.tmp size=2><SPAN
style="FONT-SIZE: 11pt; 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: 0.5in; TEXT-INDENT: 0.5in"><FONT
face=Z@R44A.tmp size=2><SPAN
style="FONT-SIZE: 11pt; 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"><FONT face=Z@R44A.tmp
size=2><SPAN style="FONT-SIZE: 11pt; FONT-FAMILY: 'Z@R44A.tmp'">Enhanced
call survivability:<o:p></o:p></SPAN></FONT>
<UL style="MARGIN-TOP: 0in" type=circle>
<LI class=MsoNormal style="mso-list: l0 level2 lfo1"><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: 11pt; FONT-FAMILY: 'Z@R44A.tmpOOEnc'">
</SPAN></FONT><FONT face=Z@R44A.tmp size=2><SPAN
style="FONT-SIZE: 11pt; 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></LI></UL>
<P class=MsoNormal style="MARGIN-LEFT: 0.75in; TEXT-INDENT: 0.25in"><FONT
face=Z@R44A.tmp size=2><SPAN
style="FONT-SIZE: 11pt; 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: 0.5in; TEXT-INDENT: 0.5in"><FONT
face=Z@R44A.tmp size=2><SPAN
style="FONT-SIZE: 11pt; 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"><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: 11pt; FONT-FAMILY: 'Z@R44A.tmpOOEnc'">
</SPAN></FONT><FONT face=Z@R44A.tmp size=2><SPAN
style="FONT-SIZE: 11pt; 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: 0.5in; TEXT-INDENT: 0.5in"><FONT
face=Z@R44A.tmp size=2><SPAN
style="FONT-SIZE: 11pt; 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: 1in"><FONT face=Z@R44A.tmp size=2><SPAN
style="FONT-SIZE: 11pt; FONT-FAMILY: 'Z@R44A.tmp'">dropped on
fallback.<o:p></o:p></SPAN></FONT></P>
<P class=MsoNormal style="MARGIN-LEFT: 1in"><FONT face=Z@R44A.tmp size=2><SPAN
style="FONT-SIZE: 11pt; FONT-FAMILY: 'Z@R44A.tmp'"><o:p> </o:p></SPAN></FONT></P>
<P class=MsoNormal style="MARGIN-LEFT: 0.5in"><FONT face=Z@R44A.tmp
size=2><SPAN
style="FONT-SIZE: 11pt; FONT-FAMILY: 'Z@R44A.tmp'">HTH’s<o:p></o:p></SPAN></FONT></P>
<P class=MsoNormal style="MARGIN-LEFT: 0.5in"><FONT face=Z@R44A.tmp
size=2><SPAN
style="FONT-SIZE: 11pt; FONT-FAMILY: 'Z@R44A.tmp'"><o:p> </o:p></SPAN></FONT></P>
<P class=MsoNormal style="MARGIN-LEFT: 0.5in"><FONT face=Z@R44A.tmp
size=2><SPAN
style="FONT-SIZE: 11pt; FONT-FAMILY: 'Z@R44A.tmp'">Joe<o:p></o:p></SPAN></FONT></P>
<P class=MsoNormal><FONT face=Arial color=navy size=2><SPAN
style="FONT-SIZE: 10pt; COLOR: navy; FONT-FAMILY: Arial"><o:p> </o:p></SPAN></FONT></P>
<P class=MsoNormal><FONT face=Arial color=navy size=2><SPAN
style="FONT-SIZE: 10pt; COLOR: navy; FONT-FAMILY: Arial"><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; FONT-FAMILY: 'Times New Roman'">
<HR tabIndex=-1 align=center width="100%" SIZE=2>
</SPAN></FONT></DIV>
<P class=MsoNormal><B><FONT face=Tahoma size=2><SPAN
style="FONT-WEIGHT: bold; FONT-SIZE: 10pt">From:</SPAN></FONT></B><FONT
size=2><SPAN style="FONT-SIZE: 10pt"> 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 face=Tahoma size=3><SPAN
style="FONT-SIZE: 12pt"><o:p> </o:p></SPAN></FONT></P>
<P class=MsoNormal><FONT face=Arial size=2><SPAN lang=EN-GB
style="FONT-SIZE: 10pt; 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 face=Arial size=2><SPAN lang=EN-GB
style="FONT-SIZE: 10pt; FONT-FAMILY: Arial"> </SPAN></FONT><SPAN
lang=EN-GB><o:p></o:p></SPAN></P>
<P class=MsoNormal><FONT face=Arial size=2><SPAN lang=EN-GB
style="FONT-SIZE: 10pt; 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 face=Arial size=2><SPAN lang=EN-GB
style="FONT-SIZE: 10pt; FONT-FAMILY: Arial"> </SPAN></FONT><SPAN
lang=EN-GB><o:p></o:p></SPAN></P>
<P class=MsoNormal><FONT face=Arial size=2><SPAN lang=EN-GB
style="FONT-SIZE: 10pt; 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 face=Arial size=2><SPAN lang=EN-GB
style="FONT-SIZE: 10pt; FONT-FAMILY: Arial"> </SPAN></FONT><SPAN
lang=EN-GB><o:p></o:p></SPAN></P>
<P class=MsoNormal><FONT face=Arial size=2><SPAN lang=EN-GB
style="FONT-SIZE: 10pt; 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 face=Arial size=2><SPAN lang=EN-GB
style="FONT-SIZE: 10pt; FONT-FAMILY: Arial"> </SPAN></FONT><SPAN
lang=EN-GB><o:p></o:p></SPAN></P>
<P class=MsoNormal><FONT face=Arial size=2><SPAN lang=EN-GB
style="FONT-SIZE: 10pt; 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 face=Arial size=2><SPAN lang=EN-GB
style="FONT-SIZE: 10pt; FONT-FAMILY: Arial"> </SPAN></FONT><SPAN
lang=EN-GB><o:p></o:p></SPAN></P>
<P class=MsoNormal><FONT face=Arial size=2><SPAN lang=EN-GB
style="FONT-SIZE: 10pt; FONT-FAMILY: Arial"> </SPAN></FONT><SPAN
lang=EN-GB><o:p></o:p></SPAN></P>
<P class=MsoNormal style="MARGIN-BOTTOM: 12pt"><FONT face="Times New Roman"
size=3><SPAN lang=EN-GB
style="FONT-SIZE: 12pt; FONT-FAMILY: 'Times New Roman'"><o:p> </o:p></SPAN></FONT></P>
<TABLE class=MsoNormalTable style="BACKGROUND: white" cellPadding=0
bgColor=white border=0>
<TBODY>
<TR>
<TD
style="PADDING-RIGHT: 0.75pt; PADDING-LEFT: 0.75pt; PADDING-BOTTOM: 0.75pt; PADDING-TOP: 0.75pt">
<P class=MsoNormal><FONT face="Times New Roman" color=black size=3><SPAN
style="FONT-SIZE: 12pt; COLOR: black; FONT-FAMILY: 'Times New Roman'"><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></TBODY></TABLE>
<P class=MsoNormal><FONT face="Times New Roman" size=3><SPAN
style="FONT-SIZE: 12pt; FONT-FAMILY: 'Times New Roman'"><o:p> </o:p></SPAN></FONT></P>
<DIV class=MsoNormal style="TEXT-ALIGN: center" align=center><FONT face=Arial
color=gray size=2><SPAN
style="FONT-SIZE: 10pt; COLOR: gray; FONT-FAMILY: Arial">
<HR align=center width="100%" SIZE=2>
</SPAN></FONT></DIV>
<P><STRONG><B><FONT face=Verdana color=gray size=2><SPAN
style="FONT-SIZE: 10pt; COLOR: gray; FONT-FAMILY: Verdana">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 face=Verdana color=gray size=2><SPAN
style="FONT-SIZE: 10pt; COLOR: gray; FONT-FAMILY: Verdana">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 face=Arial
color=gray size=2><SPAN
style="FONT-SIZE: 10pt; COLOR: gray; FONT-FAMILY: Arial">
<HR align=center width="100%" SIZE=2>
</SPAN></FONT></DIV></DIV>
<P>
<HR SIZE=1>
<P></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>
<P>
<HR SIZE=1>
<P></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>
<P>
<HR SIZE=1>
<P></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>
<P>
<HR SIZE=1>
<P></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>
<P>
<HR SIZE=1>
<P></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></BLOCKQUOTE></BODY></HTML>