<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 12 (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:Wingdings;
panose-1:5 0 0 0 0 0 0 0 0 0;}
@font-face
{font-family:"Estrangelo Edessa";
panose-1:0 0 0 0 0 0 0 0 0 0;}
@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:Consolas;
panose-1:2 11 6 9 2 2 4 3 2 4;}
@font-face
{font-family:"Lucida Sans";
panose-1:2 11 6 2 3 5 4 2 2 4;}
@font-face
{font-family:Candara;
panose-1:2 14 5 2 3 3 3 2 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri","sans-serif";
color:black;}
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;}
pre
{mso-style-priority:99;
mso-style-link:"HTML Preformatted Char";
margin:0in;
margin-bottom:.0001pt;
font-size:10.0pt;
font-family:"Courier New";
color:black;}
p.MsoAcetate, li.MsoAcetate, div.MsoAcetate
{mso-style-priority:99;
mso-style-link:"Balloon Text Char";
margin:0in;
margin-bottom:.0001pt;
font-size:8.0pt;
font-family:"Tahoma","sans-serif";
color:black;}
p.MsoListParagraph, li.MsoListParagraph, div.MsoListParagraph
{mso-style-priority:34;
margin-top:0in;
margin-right:0in;
margin-bottom:0in;
margin-left:.5in;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri","sans-serif";
color:black;}
span.BalloonTextChar
{mso-style-name:"Balloon Text Char";
mso-style-priority:99;
mso-style-link:"Balloon Text";
font-family:"Tahoma","sans-serif";}
span.EmailStyle20
{mso-style-type:personal;
font-family:"Calibri","sans-serif";
color:windowtext;}
span.EmailStyle21
{mso-style-type:personal;
font-family:"Calibri","sans-serif";
color:#1F497D;}
span.HTMLPreformattedChar
{mso-style-name:"HTML Preformatted Char";
mso-style-priority:99;
mso-style-link:"HTML Preformatted";
font-family:Consolas;
color:black;}
span.EmailStyle25
{mso-style-type:personal-reply;
font-family:"Calibri","sans-serif";
color:#1F497D;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@page Section1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.Section1
{page:Section1;}
/* List Definitions */
@list l0
{mso-list-id:1163427388;
mso-list-type:hybrid;
mso-list-template-ids:1958226200 -294510722 67698691 67698693 67698689 67698691 67698693 67698689 67698691 67698693;}
@list l0:level1
{mso-level-start-at:9;
mso-level-number-format:bullet;
mso-level-text:-;
mso-level-tab-stop:none;
mso-level-number-position:left;
text-indent:-.25in;
font-family:"Calibri","sans-serif";
mso-fareast-font-family:Calibri;
mso-bidi-font-family:"Times New Roman";}
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 bgcolor=white lang=EN-US link=blue vlink=purple>
<div class=Section1>
<p class=MsoNormal><span style='color:#1F497D'>Wes:<o:p></o:p></span></p>
<p class=MsoNormal><span style='color:#1F497D'><o:p> </o:p></span></p>
<p class=MsoNormal><span style='color:#1F497D'> Thank you so
much for the detailed response. So it’s safe to say that using the TCP Handles within
a CCM trace (0044522 in this case) would only be reliable if the SCCP message
was received by CCM from the endpoint, correct? For example, the OffHook SCCP
message shows the TCP Handle matched with the correct IP and MAC of the
endpoint. However, the startMediaTransmission message FROM CallManager with the
0044522 TCP Handle shows the IP and MAC for the <b><i>other</i></b> endpoint.
In this case, it would be best to look further into the trace file entries and
use knowledge of SCCP signaling in order to determine exactly what’s going
on..?<o:p></o:p></span></p>
<p class=MsoNormal><span style='color:#1F497D'><o:p> </o:p></span></p>
<p class=MsoNormal><span style='color:#1F497D'>Thanks again Wes.<o:p></o:p></span></p>
<p class=MsoNormal><span style='color:#1F497D'><o:p> </o:p></span></p>
<p class=MsoNormal><span style='color:#1F497D'>-Daniel-<o:p></o:p></span></p>
<p class=MsoNormal><span style='color:#1F497D'><o:p> </o:p></span></p>
<div>
<div style='border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in 0in 0in'>
<p class=MsoNormal><b><span style='font-size:10.0pt;font-family:"Tahoma","sans-serif";
color:windowtext'>From:</span></b><span style='font-size:10.0pt;font-family:
"Tahoma","sans-serif";color:windowtext'> Wes Sisk [mailto:wsisk@cisco.com] <br>
<b>Sent:</b> Wednesday, March 12, 2008 11:06 AM<br>
<b>To:</b> Daniel Rodriquez<br>
<b>Cc:</b> cisco-voip@puck.nether.net<br>
<b>Subject:</b> Re: [cisco-voip] FW: CCM Trace - MAC & IP: Source/Dest?<o:p></o:p></span></p>
</div>
</div>
<p class=MsoNormal><o:p> </o:p></p>
<p class=MsoNormal>Hi Daniel,<br>
<br>
Unfortunately not true. The 'event correlation tags' appear at the end of
SDI trace lines and also embedded in SDL trace lines. The original idea
of correlation tags was to trace events back to the device/event that
originated. As you can see in your example they are moderately
reliable. In my own personal parsing I only 'trust' the correlation tags
for certain messages where I know they are correct, station OffHook for
example.<br>
<br>
I use offhook to then identify the TCP Handle of the SCCP device, 0044522 in
your case. Then I follow that TCP handle to see all SCCP events to/from
that endpoint.<br>
<br>
Unfortunately this does not work for SIP, MGCP, or H.323.<br>
<br>
For SIP I still do not have a clear answer. Every endpoint sets up
multiple 'dialogues' so the dialogue for SIP keepalive uses different text than
the dialgogue for a SIP call. No easy way to follow through all events
for a specific SIP endpoint. I've had moderate results following the
device IP because it is printed in every SIP message if you are running
detailed traces.<br>
<br>
For MGCP I usually follow the endpoint identifier. There is another trick
as well. The q.931 call identifer for d-channel backhaul matches the
connection identifier in the MGCP traffic. This allows matching q.931
events to MGCP messaging.<br>
<br>
For H.323 follow the GUID in asn1 decode of detailed traces. This shows
all h.225 events for the call. For h.245 follow the TtPid. You have
to use asn.1 or SDL to match the h.225 to h.245 by the h.245 port number.
once you have the h.245 TtPid grep the SDI traces:<br>
TtPid=(4,100,14,61) -Outgoing -value MultimediaSystemControlMessage ::=
response : openLogicalChannelAck :<br>
TtPid=(4,100,14,61) -Outgoing -value MultimediaSystemControlMessage ::= request
: terminalCapabilitySet :<br>
TtPid=(4,100,14,61) -Outgoing -value MultimediaSystemControlMessage ::= request
: closeLogicalChannel :<br>
TtPid=(4,100,14,61) -Incoming -value MultimediaSystemControlMessage ::= request
: closeLogicalChannel :<br>
...<br>
TtPid=(4,100,14,61) -Incoming -value MultimediaSystemControlMessage ::=
response : terminalCapabilitySetAck :<br>
<br>
/Wes<br>
<br>
Daniel Rodriquez wrote: <o:p></o:p></p>
<p class=MsoNormal><span style='color:#1F497D'>Mornin’ folks:</span><o:p></o:p></p>
<p class=MsoNormal><span style='color:#1F497D'> </span><o:p></o:p></p>
<p class=MsoNormal><span style='color:#1F497D'>Anyone happen to have any input
on this? </span><o:p></o:p></p>
<p class=MsoNormal><span style='color:#1F497D'>Thanks ahead of time for your
help.</span><o:p></o:p></p>
<p class=MsoNormal><span style='color:#1F497D'> </span><o:p></o:p></p>
<p class=MsoNormal><span style='color:#1F497D'>-Daniel-</span><o:p></o:p></p>
<p class=MsoNormal><span style='color:#1F497D'> </span><o:p></o:p></p>
<div>
<div style='border:none;border-top:solid windowtext 1.0pt;padding:3.0pt 0in 0in 0in;
border-color:-moz-use-text-color -moz-use-text-color'>
<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"'> <a
href="mailto:cisco-voip-bounces@puck.nether.net">cisco-voip-bounces@puck.nether.net</a>
[<a href="mailto:cisco-voip-bounces@puck.nether.net">mailto:cisco-voip-bounces@puck.nether.net</a>]
<b>On Behalf Of </b>Daniel Rodriquez<br>
<b>Sent:</b> Tuesday, March 11, 2008 12:29 PM<br>
<b>To:</b> <a href="mailto:cisco-voip@puck.nether.net">cisco-voip@puck.nether.net</a><br>
<b>Subject:</b> [cisco-voip] CCM Trace - MAC & IP: Source/Dest?</span><o:p></o:p></p>
</div>
</div>
<p class=MsoNormal> <o:p></o:p></p>
<p class=MsoNormal><span style='font-size:10.0pt;font-family:"Arial","sans-serif"'>Hello
and good afternoon:</span><o:p></o:p></p>
<p class=MsoNormal><span style='font-size:10.0pt;font-family:"Arial","sans-serif"'> </span><o:p></o:p></p>
<p class=MsoNormal><span style='font-size:10.0pt;font-family:"Arial","sans-serif"'>
I have a few questions regarding CCM traces. I’ve read through my fair share of
trace files but I recently noticed something within CCM traces that doesn’t
quite make sense to me. Below is an excerpt of a CCM trace for an on-net call.
The calling device is SEP001C58A2B308 (DN 3500/Line1_RTP – IP 192.168.102.175)
and the called device is SEP001C58F075EA (DN 3037/Line1_RTP – IP 192.168.102.203).
I’ve omitted a large portion of the trace and only included relevant lines.
Questions listed below trace lines.</span><o:p></o:p></p>
<p class=MsoNormal><span style='font-size:10.0pt;font-family:"Courier New"'> </span><o:p></o:p></p>
<p class=MsoNormal><b><span style='font-size:10.0pt;font-family:"Candara","sans-serif"'>:::::
Note the message ID, MAC, and IP ::::</span></b><o:p></o:p></p>
<p class=MsoNormal><b><span style='font-size:10.0pt;font-family:"Candara","sans-serif"'>:::::
Calling party pressing NewCall softkey ::::</span></b><o:p></o:p></p>
<p class=MsoNormal><span style='font-size:10.0pt;font-family:"Courier New"'>03/07/2008
12:01:21.055 CCM|StationInit: (0044624) SoftKeyEvent softKeyEvent=2(NewCall)
lineInstance=1
callReference=0.|<CLID::StandAloneCluster><NID::192.168.102.11><CT::1,100,126,1.362322><IP::192.168.102.175><DEV::SEP001C58A2B308></span><o:p></o:p></p>
<p class=MsoNormal><span style='font-size:10.0pt;font-family:"Courier New"'>03</span><o:p></o:p></p>
<p class=MsoNormal><span style='font-size:10.0pt;font-family:"Courier New"'> </span><o:p></o:p></p>
<p class=MsoNormal><b><span style='font-size:10.0pt;font-family:"Candara","sans-serif"'>:::::
Msg ID stays the same ::::</span></b><o:p></o:p></p>
<p class=MsoNormal><b><span style='font-size:10.0pt;font-family:"Candara","sans-serif"'>:::::
CCM instructing phone to display “Enter Number” on LCD screen ::::</span></b><o:p></o:p></p>
<p class=MsoNormal><span style='font-size:10.0pt;font-family:"Courier New"'>03/07/2008
12:01:21.055 CCM|StationD: (<span style='background:lime'>0044624</span>)
DisplayPromptStatus timeOut=0 Status='€ ' content='Enter Number' line=1
CI=16777355
ver=8570000c.|<CLID::StandAloneCluster><NID::192.168.102.11><CT::1,100,126,1.362322><IP::192.168.102.175><DEV::<span
style='background:lime'>SEP001C58A2B308></span></span><o:p></o:p></p>
<p class=MsoNormal><span style='font-size:10.0pt;font-family:"Courier New"'> </span><o:p></o:p></p>
<p class=MsoNormal><b><i><span style='font-family:"Candara","sans-serif"'>:::::
Skipping traces… CCM tells phone to play inside tone… user dials “3037”… DA
matches correct DN/partition ::::::::::::::::</span></i></b><o:p></o:p></p>
<p class=MsoNormal><span style='font-family:"Courier New"'> </span><o:p></o:p></p>
<p class=MsoNormal><b><span style='font-size:10.0pt;font-family:"Candara","sans-serif"'>:::::
CCM checks busy trigger of called device… CCM instructs <u>called</u> phone to
display “From 3500” on LCD screen :::::</span></b><o:p></o:p></p>
<p class=MsoNormal><b><span style='font-size:10.0pt;font-family:"Candara","sans-serif"'>:::::
CCM instructs called phone to play inside ring :::::</span></b><o:p></o:p></p>
<p class=MsoNormal><b><span style='font-size:10.0pt;font-family:"Candara","sans-serif"'>:::::
NOTICE the message ID change for the new call leg. In addition, notice how the
MAC and IP add are kept the same when this is clearly destined</span></b><span
style='font-size:10.0pt;font-family:"Courier New"'> for the called device :::::</span><o:p></o:p></p>
<p class=MsoNormal><span style='font-size:10.0pt;font-family:"Courier New"'>03/07/2008
12:01:23.805 CCM|StationD: (0044522) DEBUG whatToDo:
busy trigger not hit... send to open
appearance|<CLID::StandAloneCluster><NID::192.168.102.11><CT::1,100,126,1.362326><IP::192.168.102.175><DEV::SEP001C58A2B308></span><o:p></o:p></p>
<p class=MsoNormal><span style='font-size:10.0pt;font-family:"Courier New"'> </span><o:p></o:p></p>
<p class=MsoNormal><span style='font-size:10.0pt;font-family:"Courier New"'>03/07/2008
12:01:23.805 CCM|StationD: (0044522) DisplayPromptStatus
timeOut=0 Status='€_3500' content='From 3500' line=1 CI=16777356
ver=8570000c.|<CLID::StandAloneCluster><NID::192.168.102.11><CT::1,100,126,1.362326><IP::192.168.102.175><DEV::SEP001C58A2B308></span><o:p></o:p></p>
<p class=MsoNormal><span style='font-size:10.0pt;font-family:"Courier New"'> </span><o:p></o:p></p>
<p class=MsoNormal><span style='font-size:10.0pt;font-family:"Courier New"'>03/07/2008
12:01:23.805 CCM|StationD: (<span style='background:yellow'>0<b>044522</b></span>)
<u>SetRinger</u>
ringMode=2(InsideRing).|<CLID::StandAloneCluster><NID::192.168.102.11><CT::1,100,126,1.362326><IP::192.168.102.175><DEV::<b><span
style='background:lime'>SEP001C58A2B308</span></b>></span><o:p></o:p></p>
<p class=MsoNormal><span style='font-size:10.0pt;font-family:"Courier New"'> </span><o:p></o:p></p>
<p class=MsoNormal><b><span style='font-size:10.0pt;font-family:"Candara","sans-serif"'>:::::
Called party answers call :::::</span></b><o:p></o:p></p>
<p class=MsoNormal><b><span style='font-size:10.0pt;font-family:"Candara","sans-serif"'>:::::
Notice the MAC and IP changes for the called device :::::</span></b><o:p></o:p></p>
<p class=MsoNormal><span style='font-size:10.0pt;font-family:"Courier New"'>03/07/2008
12:01:28.695 CCM|StationInit: (<b><span style='background:yellow'>0044522</span></b>)
SoftKeyEvent softKeyEvent=11(Answer) lineInstance=1
callReference=16777356.|<CLID::StandAloneCluster><NID::192.168.102.11><CT::1,100,126,1.362329><IP::192.168.102.203><DEV::<b><span
style='background:yellow'>SEP001C58F075EA</span></b>></span><o:p></o:p></p>
<p class=MsoNormal><b><span style='font-size:10.0pt;font-family:"Courier New"'> </span></b><o:p></o:p></p>
<p class=MsoNormal><b><span style='font-size:10.0pt'>::::: CCM instructs
calling device to start sending RTP packets to called device :::::</span></b><o:p></o:p></p>
<p class=MsoNormal><b><span style='font-size:10.0pt'>::::: Notice myIP is .175
(calling device) and remoteIP is the called device, but the IP and MAC at the
end of the trace shows the called device :::::</span></b><o:p></o:p></p>
<p class=MsoNormal><span style='font-size:10.0pt;font-family:"Courier New"'> </span><o:p></o:p></p>
<p class=MsoNormal><span style='font-size:10.0pt;font-family:"Courier New"'>03/07/2008
12:01:28.805 CCM|StationD: (0044624) startMediaTransmission
conferenceID=16777355 passThruPartyID=16777905
remoteIpAddress=cb66a8c0(192.168.102.203)
remotePortNumber=26544
milliSecondPacketSize=20 compressType=4(Media_Payload_G711Ulaw64k)
qualifierOut=?. myIP: af66a8c0 (192.168.102.175)
mediaEncryption algorithmID=0 keylen=0 saltlen=0|<CLID::StandAloneCluster><NID::192.168.102.11><CT::1,100,126,1.362331><IP::192.168.102.203><DEV::SEP001C58F075EA></span><o:p></o:p></p>
<p class=MsoNormal><b><span style='font-size:10.0pt;font-family:"Courier New"'> </span></b><o:p></o:p></p>
<p class=MsoNormal><b><span style='font-size:10.0pt;font-family:"Courier New"'>
QUESTIONS:</span></b><o:p></o:p></p>
<p class=MsoNormal><b><span style='font-size:10.0pt;font-family:"Courier New"'> </span></b><o:p></o:p></p>
<p class=MsoListParagraph style='margin-left:.75in;text-indent:-.25in'><b><span
style='font-size:10.0pt;font-family:"Courier New"'>For sent StationD and
received StationInit SCCP messages, aren’t the IP and MAC addresses located at
the end of the trace line supposed to specify the source or destination of the
message? As you can see above, CCM was instructing the called device to display
“From 3500” on its LCD screen, yet the MAC and IP addresses at the end of the
trace line was for the calling device. I thought the message identifier would
be consistent with this information too.</span></b><o:p></o:p></p>
<p class=MsoListParagraph style='margin-left:.75in'><b><span style='font-size:
10.0pt;font-family:"Courier New"'> </span></b><o:p></o:p></p>
<p class=MsoListParagraph style='margin-left:.75in;text-indent:-.25in'><b><span
style='font-size:10.0pt;font-family:"Courier New"'>The Cisco IPTT book mentions
that TCP Handle are assigned to IPT devices upon boot up and can be tracked by
searching through keepalives. Am I correct to assume this was removed from CCM
traces at some point? I always review CCM traces when logging levels are set to
Detailed, yet I fail to find the TCP Handles anywhere within the trace files.</span></b><o:p></o:p></p>
<p class=MsoNormal><b><span style='font-size:10.0pt;font-family:"Courier New"'> </span></b><o:p></o:p></p>
<p class=MsoNormal><b><span style='font-size:10.0pt;font-family:"Courier New"'>Thanks
ahead of time for your input on this!</span></b><o:p></o:p></p>
<p class=MsoNormal><b><span style='font-size:10.0pt;font-family:"Courier New"'> </span></b><o:p></o:p></p>
<p class=MsoNormal><span style='font-size:10.0pt;font-family:"Lucida Sans","sans-serif"'>Daniel
Rodriguez, CCVP</span><span style='font-size:10.0pt;font-family:"Estrangelo Edessa"'><br>
</span><strong><span style='font-size:10.0pt;font-family:"Lucida Sans","sans-serif";
color:#000099'>Fidelus Technologies, LLC</span></strong><span style='font-size:
10.0pt;font-family:"Lucida Sans","sans-serif"'><br>
</span><span style='font-size:10.0pt;font-family:"Arial","sans-serif";
color:#4E4E4E'>240 West 35th Street | 6th Floor | New York, NY 10001<br>
o: 212.616-7843 | c: 917-797-2543 | f: 212.616-7850<br>
e: </span><span style='font-size:10.0pt'><a href="mailto:drodriguez@fidelus.com"><span
style='font-family:"Arial","sans-serif";color:#4E4E4E'>drodriguez@fidelus.com</span></a></span><span
style='font-size:10.0pt;font-family:"Arial","sans-serif";color:#4E4E4E'> | </span><span
style='font-size:10.0pt'><a href="http://www.fidelus.com"><span
style='font-family:"Arial","sans-serif";color:#4E4E4E'>www.fidelus.com</span></a></span><o:p></o:p></p>
<p class=MsoNormal><span style='font-size:10.0pt'><img border=0 width=129
height=73 id="Picture_x0020_1" src="cid:image001.jpg@01C88433.C6D25210"
alt="cid:image001.jpg@01C87DE0.11CDB7A0"></span><o:p></o:p></p>
<p class=MsoNormal><span style='font-size:12.0pt;font-family:"Times New Roman","serif"'> </span><o:p></o:p></p>
<div class=MsoNormal align=center style='text-align:center'><span
style='font-size:12.0pt;font-family:"Times New Roman","serif"'>
<hr size=2 width="100%" align=center>
</span></div>
<p class=MsoNormal><span style='font-size:7.5pt;font-family:"Arial","sans-serif";
color:gray'>NOTICE: This e-mail and any attachment contain confidential
information that may be legally privileged. If you are not the intended
recipient, you must not review, retransmit, print, copy, use or disseminate it.
Please immediately notify us by return e-mail and delete it. If this e-mail
contains a forwarded e-mail or is a reply to a prior e-mail, the contents may
not have been produced by the sender and therefore we are not responsible for
its contents.<br>
This notice is automatically appended to each e-mail. It is the recipient's
responsibility to take measures to ensure that this e-mail is virus free, and
no responsibility is accepted by Fidelus Technologies LLC for any loss or
damage arising in any way from its use.</span><o:p></o:p></p>
<pre><o:p> </o:p></pre><pre style='text-align:center'>
<hr size=4 width="90%" align=center>
</pre><pre><o:p> </o:p></pre><pre>_______________________________________________<o:p></o:p></pre><pre>cisco-voip mailing list<o:p></o:p></pre><pre><a
href="mailto:cisco-voip@puck.nether.net">cisco-voip@puck.nether.net</a><o:p></o:p></pre><pre><a
href="https://puck.nether.net/mailman/listinfo/cisco-voip">https://puck.nether.net/mailman/listinfo/cisco-voip</a><o:p></o:p></pre><pre> <o:p></o:p></pre></div>
</body>
</html>