<HTML><BODY style="word-wrap: break-word; -khtml-nbsp-mode: space; -khtml-line-break: after-white-space; ">You will get calling name with h.323 4.2 depending on how it is delivered:<DIV>You will see it if delivered by:</DIV><DIV>DisplayIE</DIV><DIV>NotifyIE</DIV><DIV><BR class="khtml-block-placeholder"></DIV><DIV>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'.</DIV><DIV><BR class="khtml-block-placeholder"></DIV><DIV>/Wes<BR><DIV><DIV>On Aug 30, 2006, at 3:21 PM, Linsemier, Matthew wrote:</DIV><BR class="Apple-interchange-newline"><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"> <DIV class="Section1"><P class="MsoNormal"><FONT size="2" color="navy" face="Arial"><SPAN style="font-size: 10.0pt;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></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 [<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><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">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 [<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><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 [<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><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> <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><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 [<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 w: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><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 [<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><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; <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><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 [<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><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 [<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><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"> <TBODY><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></TBODY></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> <FONT face="Arial" size="2"><P><FONT color="#808080"> <HR> </FONT></P><P><FONT face="Verdana" color="#808080"><STRONG>CONFIDENTIALITY STATEMENT</STRONG></FONT></P><P><FONT face="Verdana" color="#808080">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></P><P><FONT color="#808080"> <HR> </FONT> </P><DIV><BR class="khtml-block-placeholder"></DIV></FONT><DIV><BR class="khtml-block-placeholder"></DIV><HR size="1"><DIV><BR class="khtml-block-placeholder"></DIV><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><DIV><BR class="khtml-block-placeholder"></DIV><HR size="1"><DIV><BR class="khtml-block-placeholder"></DIV><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><DIV><BR class="khtml-block-placeholder"></DIV><HR size="1"><DIV><BR class="khtml-block-placeholder"></DIV><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><DIV><BR class="khtml-block-placeholder"></DIV><HR size="1"><DIV><BR class="khtml-block-placeholder"></DIV><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></O:SMARTTAGTYPE></O:SMARTTAGTYPE></O:SMARTTAGTYPE></O:SMARTTAGTYPE></O:SMARTTAGTYPE></O:SMARTTAGTYPE></O:SMARTTAGTYPE><DIV style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; ">_______________________________________________</DIV><DIV style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; ">cisco-voip mailing list</DIV><DIV style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; "><A href="mailto:cisco-voip@puck.nether.net">cisco-voip@puck.nether.net</A></DIV><DIV style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; "><A href="https://puck.nether.net/mailman/listinfo/cisco-voip">https://puck.nether.net/mailman/listinfo/cisco-voip</A></DIV> </DIV><BR></DIV></BODY></HTML>