<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
<meta name="Generator" content="Microsoft Word 15 (filtered medium)">
<!--[if !mso]><style>v\:* {behavior:url(#default#VML);}
o\:* {behavior:url(#default#VML);}
w\:* {behavior:url(#default#VML);}
.shape {behavior:url(#default#VML);}
</style><![endif]--><style><!--
/* Font Definitions */
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
{font-family:Tahoma;
panose-1:2 11 6 4 3 5 4 4 2 4;}
@font-face
{font-family:Garamond;
panose-1:2 2 4 4 3 3 1 1 8 3;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman",serif;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
span.EmailStyle17
{mso-style-type:personal-reply;
font-family:"Garamond",serif;
color:#1F497D;}
.MsoChpDefault
{mso-style-type:export-only;
font-family:"Calibri",sans-serif;}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang="EN-US" link="blue" vlink="purple">
<div class="WordSection1">
<p class="MsoNormal"><span style="font-family:"Calibri",sans-serif;color:#1F497D">Both very interesting points.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-family:"Calibri",sans-serif;color:#1F497D"><br>
Mike, as for the “very lax” part, as you mentioned, the PSTN in the USA, where I am based, should ignore that field, but my provider is passing it through, so it is abnormal from that perspective, and we very seldom do calling outside of the US, so once again,
strange.<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-family:"Calibri",sans-serif;color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-family:"Calibri",sans-serif;color:#1F497D">So it looks like short of calling my provider and telling them to do it, I can either do a translation on the CUBE using regex variables, or uncheck UTF-8 and use the ASCII name
to send a different name out the trunk and manage it through CUCM is my two options right now?<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-family:"Garamond",serif;color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal" style="text-autospace:none"><b><span style="font-size:10.0pt;font-family:"Garamond",serif;color:#3B3838">Ben Amick<o:p></o:p></span></b></p>
<p class="MsoNormal" style="text-autospace:none"><span style="font-size:9.0pt;font-family:"Garamond",serif;color:#3B3838">Telecom Analyst</span><span style="font-size:9.0pt;font-family:"Garamond",serif;color:#666666"><o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-family:"Garamond",serif;color:#1F497D"><o:p> </o:p></span></p>
<p class="MsoNormal"><b><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">From:</span></b><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"> Evgeny Izetov [mailto:eizetov@gmail.com]
<br>
<b>Sent:</b> Tuesday, January 17, 2017 12:56 PM<br>
<b>To:</b> Norton, Mike <mikenorton@pwsd76.ab.ca><br>
<b>Cc:</b> Cisco VoIP Group <cisco-voip@puck.nether.net>; Ben Amick <bamick@HumanArc.com><br>
<b>Subject:</b> Re: [cisco-voip] Caller ID Manipulation<o:p></o:p></span></p>
<p class="MsoNormal"><o:p> </o:p></p>
<div>
<p class="MsoNormal"><span style="font-size:9.5pt">It still works with SIP. It is controlled by the "Transmit UTF-8 for Calling Party Name" checkbox on a SIP trunk. When unchecked (default), ASCII Display Name gets sent. If you check it, then Display Name is
sent. If ASCII Display Name is blank, then I believe just the number is going to be sent out.</span><o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
<div>
<p class="MsoNormal">On Tue, Jan 17, 2017 at 12:44 PM, Norton, Mike <<a href="mailto:mikenorton@pwsd76.ab.ca" target="_blank">mikenorton@pwsd76.ab.ca</a>> wrote:<o:p></o:p></p>
<blockquote style="border:none;border-left:solid #CCCCCC 1.0pt;padding:0in 0in 0in 6.0pt;margin-left:4.8pt;margin-right:0in">
<div>
<div>
<div>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">Oh yes, that is a good trick I used to use back when my PRI gateways were MGCP. Does it work with SIP too? I guess I just always assumed SIP would take Unicode names.<br>
<br>
Not actually using CUCM any longer, which is why I do the names on the gateway now and forgot about the ASCII Name trick.<br>
<br>
-mn<o:p></o:p></span></p>
</div>
</div>
<div class="MsoNormal" align="center" style="text-align:center">
<hr size="2" width="100%" align="center">
</div>
<p class="MsoNormal"><b><span style="font-size:10.0pt;font-family:"Tahoma",sans-serif">From:
</span></b><span style="font-size:10.0pt;font-family:"Tahoma",sans-serif">Evgeny Izetov</span><br>
<b><span style="font-size:10.0pt;font-family:"Tahoma",sans-serif">Sent: </span></b><span style="font-size:10.0pt;font-family:"Tahoma",sans-serif">17/01/2017 10:31 AM</span><br>
<b><span style="font-size:10.0pt;font-family:"Tahoma",sans-serif">To: </span></b><span style="font-size:10.0pt;font-family:"Tahoma",sans-serif">Norton, Mike</span><br>
<b><span style="font-size:10.0pt;font-family:"Tahoma",sans-serif">Cc: </span></b><span style="font-size:10.0pt;font-family:"Tahoma",sans-serif">Alan Libbee; Cisco VoIP Group; Ben Amick</span><o:p></o:p></p>
<div>
<div>
<p class="MsoNormal" style="margin-bottom:12.0pt"><br>
<b><span style="font-size:10.0pt;font-family:"Tahoma",sans-serif">Subject: </span>
</b><span style="font-size:10.0pt;font-family:"Tahoma",sans-serif">Re: [cisco-voip] Caller ID Manipulation</span><o:p></o:p></p>
<div>
<div>
<div>
<p class="MsoNormal">You could also look into changing the ASCII Display Name on line appearances as that's what gets sent to trunks by default. <o:p></o:p></p>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
<div>
<p class="MsoNormal">On Jan 17, 2017 12:18 PM, "Norton, Mike" <<a href="mailto:mikenorton@pwsd76.ab.ca" target="_blank">mikenorton@pwsd76.ab.ca</a>> wrote:<o:p></o:p></p>
<blockquote style="border:none;border-left:solid #CCCCCC 1.0pt;padding:0in 0in 0in 6.0pt;margin-left:4.8pt;margin-right:0in">
<div>
<div>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D">Alan, I think the CNAM database lookup is only U.S. thing. In Canada and presumably elsewhere, the
calling name is set by the caller (if ISDN or SIP, otherwise by their CO switch if analog POTS) and is passed all the way through the PSTN to the callee.</span><o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D"> </span><o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D">I’ve never understood why the CUCM web interface calls the field “internal caller ID” because there
is nothing internal about it. The PSTN in some countries, such as U.S.A., ignores it, but that shouldn’t be a license for Cisco to misname the field, leading to people getting surprised when they discover that the name is not kept internal.</span><o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D"> </span><o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D">Likewise, there is nothing about Ben’s SIP provider that I would agree is “very lax.” To me, it sounds
very perfectly normal, because that is the way the PSTN works for me.</span><o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D"> </span><o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D">On my PRI gateways, I modify the outgoing names by using an inbound SIP profile on the incoming SIP
dial-peer. This allows me to alter the name in SIP From field based on what number is in the From field. So I can put a generic name for certain number ranges, special names for specific numbers, no change for incoming PSTN calls that are forwarded back out
to the PSTN, etc. I think you should be able to do the same on a CUBE. Here’s some snippets of it as an example:</span><o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D"> </span><o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D">request ANY sip-header From modify "^(.+):.*(<sip:\<a href="tel:(780)%20864-3696" target="_blank">+17808643696</a>@)"
"\1: \"SPRT RVR REG AC\" \2"</span><o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D">request ANY sip-header From modify "^(.+):.*(<sip:\<a href="tel:(780)%20568-2265" target="_blank">+17805682265</a>@)"
"\1: \"TP CREEK SCHOOL\" \2"</span><o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D">request ANY sip-header From modify "^(.+):.*(<sip:\<a href="tel:(780)%20766-2294" target="_blank">+17807662294</a>@)"
"\1: \"WMBLY ELEM SCHL\" \2"</span><o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D">request ANY sip-header From modify "^(.+):.*(<sip:\<a href="tel:(780)%20532-8133" target="_blank">+17805328133</a>@)"
"\1: \"PWSD76\" \2"</span><o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D">request ANY sip-header From modify "^(.+):.*(<sip:\+178035752[01][0-9]@)" "\1: \"PWSD76\" \2"</span><o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D">request ANY sip-header From modify "^(.+):.*(<sip:\+1780357522[0-4]@)" "\1: \"PWSD76\" \2"</span><o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D">request ANY sip-header From modify "^(.+):.*(<sip:\+178083130[5-9][0-9]@)" "\1: \"PWSD76\" \2"</span><o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D">request ANY sip-header From modify "^(.+):.*(<sip:\<a href="tel:(780)%20864-3741" target="_blank">+17808643741</a>@)"
"\1: \"PWSD76\" \2"</span><o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D"> </span><o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D">Note that inbound SIP profiles has to be turned on under “voice service voip” in order to work. But
I guess you could probably do it on the outgoing dial-peer to your SIP provider if you wanted. (I have to do it on incoming because my outgoing is PRI.)</span><o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D"> </span><o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D">-mn</span><o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D"> </span><o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D"> </span><o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><b><span style="font-size:11.0pt;font-family:"Calibri",sans-serif">From:</span></b><span style="font-size:11.0pt;font-family:"Calibri",sans-serif"> cisco-voip [mailto:<a href="mailto:cisco-voip-bounces@puck.nether.net" target="_blank">cisco-voip-bounces@puck.nether.net</a>]
<b>On Behalf Of </b>Alan Libbee<br>
<b>Sent:</b> Tuesday, January 17, 2017 8:02 AM<br>
<b>To:</b> Ben Amick <<a href="mailto:bamick@humanarc.com" target="_blank">bamick@humanarc.com</a>><br>
<b>Cc:</b> Cisco VOIP <<a href="mailto:cisco-voip@puck.nether.net" target="_blank">cisco-voip@puck.nether.net</a>><br>
<b>Subject:</b> Re: [cisco-voip] Caller ID Manipulation</span><o:p></o:p></p>
<div>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"> <o:p></o:p></p>
<div>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto">Ben,<o:p></o:p></p>
<div>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"> <o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto">You can set calling name on the device or trunk level. Most landlines and businesses not using SIP will only receive the calling number, the name is looked up through the cnam database.
You can query the cnam database here: <a href="http://cp.mcafee.com/d/avndy0w920Arhouos7fzxPNKVJ55BZBcsehd79J55BZBcsY-Orhhpvuv7ffK6Qkn3hOqerTKzsSgRmlyEa9JGX3oSVsSjrlS6NJOVJ6SL-euvW_8TuhKOOqeuLsKCOepV5VVwsCZvBHFShhlKyVOEuvkzaT0QSyrpdTV5V5AQsLIIff6XCOsVHkiP2Dlm-5EqHOVLV2DPGp1h4jVsSC-Myyr1vF6y0QJSBiRiVCIBziWq81bjP_yq80Qed40TI9bdDXelo6SjhOrYBspDg4w" target="_blank">https://www.opencnam.com</a>.
The cnam database should be updated to reflect your business name, I recommend spot checking your DIDs to see what is displayed in cnam. I have access to some different sip carriers if you want to do some testing, send me a direct email and I can tell you
exactly what we are receiving for your calls. <o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"> <o:p></o:p></p>
</div>
<div>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto">-Alan<o:p></o:p></p>
</div>
</div>
<div>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"> <o:p></o:p></p>
<div>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto">On Jan 17, 2017 9:41 AM, "Ben Amick" <<a href="mailto:bamick@humanarc.com" target="_blank">bamick@humanarc.com</a>> wrote:<o:p></o:p></p>
<blockquote style="border:none;border-left:solid #CCCCCC 1.0pt;padding:0in 0in 0in 6.0pt;margin-left:4.8pt;margin-top:5.0pt;margin-right:0in;margin-bottom:5.0pt">
<div>
<div>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto">So, I’ve discovered we have a very lax SIP provider who passes through all our ID signaling from our CUCM to the WAN without any modification – which while great for our external
CID# mask, means that our internal caller ID names (Such as “HR Conference Room” and “John Smith”) are being published out as our Caller ID names to any residential or other commercial callers (or anyone who has a cell phone with a caller ID app? Haven’t tested
that as I don’t have access to one). I can change this myself, but it would require me to get rid of all our labeling and have everyone have generic internal CID, which is not preferable.<o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"> <o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto">I’ve about to be on the verge of telling our SIP provider to change this to force to our company name across the board, but I was wondering if there was any way I could elect to
enforce this on our CID myself, either on UCM or on our CUBE routers for all outbound calls. Globally would be fine, but optionally would be great if I could opt-out certain people that do our marketing and sales.
<o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span style="font-family:"Garamond",serif"> </span><o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;text-autospace:none">
<b><span style="font-size:10.0pt;font-family:"Garamond",serif;color:#3B3838">Ben Amick</span></b><o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;text-autospace:none">
<span style="font-size:9.0pt;font-family:"Garamond",serif;color:#3B3838">Telecom Analyst</span><o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"><span style="font-family:"Garamond",serif"> </span><o:p></o:p></p>
<p class="MsoNormal" style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto"> <o:p></o:p></p>
</div>
</div>
<p class="MsoNormal" style="mso-margin-top-alt:auto;margin-bottom:12.0pt"><br>
Confidentiality Note: This message is intended for use only by the individual or entity to which it is addressed and may contain information that is privileged, confidential, and exempt from disclosure under applicable law. If the reader of this message is
not the intended recipient or the employee or agent responsible for delivering the message to the intended recipient, you are hereby notified that any dissemination, distribution or copying of this communication is strictly prohibited. If you have received
this communication in error, please contact the sender immediately and destroy the material in its entirety, whether electronic or hard copy. Thank you
<br>
_______________________________________________<br>
cisco-voip mailing list<br>
<a href="mailto:cisco-voip@puck.nether.net" target="_blank">cisco-voip@puck.nether.net</a><br>
<a href="http://cp.mcafee.com/d/1jWVIg6wUedEIfce3DNMVUTsSyyO-OCe78CzASyyO-OCeuvpdEEILLfzDDT3qabxEVd7dXThKr8qHaNk54SRtxIrsKr9JGX3oSVsSzrn_7ffZvArL8Tppd7fnKnjp7cYyYYMejuLORQX8EGThsVkffGhBrwqrjdICXYyYyOqenSm7DztPpesRG9pyPtyL0QDYu1K2qKMM-l9OwXnbiFqFsPmiNLV2DPGp1h4jVsSC-Myyr1vF6y0QJSBiRiVCIBziWq81bjP_yq80Qed40TI9bdDXelo6SjhOrUuHH" target="_blank">https://puck.nether.net/mailman/listinfo/cisco-voip</a><o:p></o:p></p>
</blockquote>
</div>
</div>
</div>
</div>
</div>
<p class="MsoNormal" style="margin-bottom:12.0pt"><br>
_______________________________________________<br>
cisco-voip mailing list<br>
<a href="mailto:cisco-voip@puck.nether.net" target="_blank">cisco-voip@puck.nether.net</a><br>
<a href="http://cp.mcafee.com/d/k-Kr6h8pdEIfce3DNMVUTsSyyO-OCe78CzASyyO-OCeuvpdEEILLfzDDT3qabxEVd7dXThKr8qHaNk54SRtxIrsKr9JGX3oSVsSzrn_7ffZvArL8Tppd7fnKnjp7cYyYYMejuLORQX8EGThsVkffGhBrwqrpdICXYyYyOqenSm7DztPpesRG9pyPtyL0QDYu1K2qKMM-l9OwXnbiFqFsPmiNLV2DPGp1h4jVsSC-Myyr1vF6y0QJSBiRiVCIBziWq81bjP_yq80Qed40TI9bdDXelo6SjhOr3G60dL1V" target="_blank">https://puck.nether.net/mailman/listinfo/cisco-voip</a><o:p></o:p></p>
</blockquote>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</blockquote>
</div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
</div>
</body>
</html>
<BR>
Confidentiality Note: This message is intended for use only by the individual or entity to which it is addressed and may contain information that is privileged, confidential, and exempt from disclosure under applicable law. If the reader of this message is not the intended recipient or the employee or agent responsible for delivering the message to the intended recipient, you are hereby notified that any dissemination, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please contact the sender immediately and destroy the material in its entirety, whether electronic or hard copy. Thank you