<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 14 (filtered medium)"><style><!--
/* Font Definitions */
@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:"Arial Narrow";
panose-1:2 11 6 6 2 2 2 3 2 4;}
/* 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;}
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";}
p.gmail-msonormal, li.gmail-msonormal, div.gmail-msonormal
{mso-style-name:gmail-msonormal;
mso-margin-top-alt:auto;
margin-right:0in;
mso-margin-bottom-alt:auto;
margin-left:0in;
font-size:12.0pt;
font-family:"Times New Roman","serif";}
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-reply;
font-family:"Calibri","sans-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-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>Thank you George.<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>I will pass along the rfc information to those responsible for the other switch.<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>I missed the match_header addition to Asterisk.<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>Unfortunately, the only header field that seems appropriate is the To header.<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>On a separate box I am now trying to configure the endpoint recognition. Planning on multiple endpoints to the same switch, so I am trying to use the match_header field.<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>I tried programming the match_header with the To: header information. Unfortunately, it didn’t work. Apparently the To header doesn’t work with the match_header field.<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>The Asterisk debug shows the following…<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>DEBUG[2778] res_pjsip_endpoint_identifier_ip.c: SIP message contains header 'To' but value '' does not match value '<sip:286@xxx.xxx.xxx.xxx>' for endpoint '286'<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p> </o:p></span></p><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"'> asterisk-users-bounces@lists.digium.com [mailto:asterisk-users-bounces@lists.digium.com] <b>On Behalf Of </b>George Joseph<br><b>Sent:</b> Tuesday, December 19, 2017 7:57 AM<br><b>To:</b> Asterisk Users Mailing List - Non-Commercial Discussion<br><b>Subject:</b> Re: [asterisk-users] Is it possible to have two endpoints to the same IP address where one uses IP based authentication and the other requires asterisk to register to that system?<o:p></o:p></span></p><p class=MsoNormal><o:p> </o:p></p><div><p class=MsoNormal><o:p> </o:p></p><div><p class=MsoNormal><o:p> </o:p></p><div><p class=MsoNormal>On Mon, Dec 18, 2017 at 9:04 AM, Dan Cropp <<a href="mailto:dan@amtelco.com" target="_blank">dan@amtelco.com</a>> wrote:<o:p></o:p></p><div><div><p class=gmail-msonormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>Thanks George</span><o:p></o:p></p><p class=gmail-msonormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'> </span><o:p></o:p></p><p class=gmail-msonormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>I originally didn’t have the 1002@ for the identify. Changed that when things were not working. I changed it back.</span><o:p></o:p></p><p class=gmail-msonormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'> </span><o:p></o:p></p><p class=gmail-msonormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>Unfortunately, the system I am connecting with doesn’t seem to support the line support. Looking at the SIP packets, I see Asterisk send it. Unfortunately, they do not send the line information as part of the INVITE. I checked with some developers of that system and they do not know anything about the line setting.</span><o:p></o:p></p><p class=gmail-msonormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>Is there any rfcs I could refer them to?</span><o:p></o:p></p></div></div><div><p class=MsoNormal><o:p> </o:p></p></div><div><p class=MsoNormal>Yeah, I've found that some providers do and some providers don't.<o:p></o:p></p></div><div><p class=MsoNormal><o:p> </o:p></p></div><div><p class=MsoNormal><o:p> </o:p></p></div><div><p class=MsoNormal><a href="https://tools.ietf.org/html/rfc3261#section-19.1" target="_blank"><span style='font-size:9.5pt'>https://tools.ietf.org/html/rfc3261#section-19.1<br></span></a><span style='font-size:9.5pt'><br>An implementation MUST include any provided transport, maddr, ttl, or<br>user parameter in the Request-URI of the formed request. If the URI<br>contains a method parameter, its value MUST be used as the method of<br>the request. The method parameter MUST NOT be placed in the<br>Request-URI. <b><o:p></o:p></b></span></p><div><p class=MsoNormal><b><span style='font-size:9.5pt;font-family:"Arial","sans-serif"'></span></b><b><span style='font-size:9.5pt;font-family:"Arial Narrow","sans-serif"'><o:p></o:p></span></b></p></div><p class=MsoNormal><b><span style='font-size:9.5pt'>Unknown URI parameters MUST be placed in the message's<br>Request-URI</span></b><span style='font-size:9.5pt'>.</span><o:p></o:p></p></div><div><p class=MsoNormal> <o:p></o:p></p></div><div><p class=MsoNormal>The identify object also has the capability to match against a specific header and value but it looks like it only tries to match on header if it can't find a match by ip address. Here's some info on it anyway.<o:p></o:p></p></div><div><p class=MsoNormal><o:p> </o:p></p></div><div><p class=MsoNormal>If you're provider puts something unique and constant in the headers, like a User-Agent string that doesn't change, you can also try using the "match_header" parameter to an identify object.<o:p></o:p></p></div><div><p class=MsoNormal><o:p> </o:p></p></div><div><p class=MsoNormal>[my_provider]<o:p></o:p></p></div><div><p class=MsoNormal>type = identify<o:p></o:p></p></div><div><p class=MsoNormal>match_header = User-Agent: Something Unique 1.0.0<o:p></o:p></p></div><div><p class=MsoNormal>endpoint = provider<o:p></o:p></p></div><div><p class=MsoNormal><o:p> </o:p></p></div><div><p class=MsoNormal>It has to be an exact match though, no wildcards or regular expressions. <o:p></o:p></p></div><div><p class=MsoNormal><o:p> </o:p></p></div><div><p class=MsoNormal>I opened an issue[1] on separating ip matching from header matching so they can be re-ordered.<o:p></o:p></p></div><div><p class=MsoNormal><o:p> </o:p></p></div><div><p class=MsoNormal><o:p> </o:p></p></div><div><p class=MsoNormal><o:p> </o:p></p></div><div><p class=MsoNormal><o:p> </o:p></p></div><div><p class=MsoNormal>[1] <a href="https://issues.asterisk.org/jira/browse/ASTERISK-27491">https://issues.asterisk.org/jira/browse/ASTERISK-27491</a><o:p></o:p></p></div><div><p class=MsoNormal><o:p> </o:p></p></div><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=gmail-msonormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'> </span><o:p></o:p></p><p class=gmail-msonormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'> </span><o:p></o:p></p><p class=gmail-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:asterisk-users-bounces@lists.digium.com" target="_blank">asterisk-users-bounces@lists.digium.com</a> [mailto:<a href="mailto:asterisk-users-bounces@lists.digium.com" target="_blank">asterisk-users-bounces@lists.digium.com</a>] <b>On Behalf Of </b>George Joseph<br><b>Sent:</b> Thursday, December 14, 2017 10:59 AM<br><b>To:</b> Asterisk Users Mailing List - Non-Commercial Discussion<br><b>Subject:</b> Re: [asterisk-users] Is it possible to have two endpoints to the same IP address where one uses IP based authentication and the other requires asterisk to register to that system?</span><o:p></o:p></p><div><div><p class=gmail-msonormal> <o:p></o:p></p><div><p class=gmail-msonormal> <o:p></o:p></p><div><p class=gmail-msonormal> <o:p></o:p></p><div><p class=gmail-msonormal>On Wed, Dec 13, 2017 at 10:51 AM, Dan Cropp <<a href="mailto:dan@amtelco.com" target="_blank">dan@amtelco.com</a>> wrote:<o:p></o:p></p><div><div><p class=gmail-msonormal>Currently using PJSIP. First, they want me to get this working with the existing PJSIP configuration, but then setup a second box using chan_sip performing similar work.<o:p></o:p></p><p class=gmail-msonormal> <o:p></o:p></p><p class=gmail-msonormal>For PJSIP…<o:p></o:p></p><p class=gmail-msonormal>I currently have an endpoint configured to a system using IP based authentication. It is configured with a match setting in the endpoint section.<o:p></o:p></p><p class=gmail-msonormal>All channels coming from that IP address go to this endpoint.<o:p></o:p></p><p class=gmail-msonormal> <o:p></o:p></p><p class=gmail-msonormal>They want me to keep this endpoint, but add a new endpoint where we register with them.<o:p></o:p></p><p class=gmail-msonormal> <o:p></o:p></p><p class=gmail-msonormal>Existing…<o:p></o:p></p><p class=gmail-msonormal>[transport1]<o:p></o:p></p><p class=gmail-msonormal>type = transport<o:p></o:p></p><p class=gmail-msonormal>bind = 0.0.0.0<o:p></o:p></p><p class=gmail-msonormal>protocol = udp<o:p></o:p></p><p class=gmail-msonormal> <o:p></o:p></p><p class=gmail-msonormal>[1002]<o:p></o:p></p><p class=gmail-msonormal>type = aor<o:p></o:p></p><p class=gmail-msonormal>remove_existing = yes<o:p></o:p></p><p class=gmail-msonormal>contact = <a href="sip:1002@xxx.xxx.xxx.xxx">sip:1002@xxx.xxx.xxx.xxx</a><o:p></o:p></p><p class=gmail-msonormal> <o:p></o:p></p><p class=gmail-msonormal>[1002]<o:p></o:p></p><p class=gmail-msonormal>type = endpoint<o:p></o:p></p><p class=gmail-msonormal>context = mycontext<o:p></o:p></p><p class=gmail-msonormal>transport = transport1<o:p></o:p></p><p class=gmail-msonormal>accountcode = 6<o:p></o:p></p><p class=gmail-msonormal>dtmf_mode = inband<o:p></o:p></p><p class=gmail-msonormal>device_state_busy_at = 48<o:p></o:p></p><p class=gmail-msonormal>force_rport = no<o:p></o:p></p><p class=gmail-msonormal>identify_by = username<o:p></o:p></p><p class=gmail-msonormal>from_user = 1002<o:p></o:p></p><p class=gmail-msonormal>disallow = all<o:p></o:p></p><p class=gmail-msonormal>allow = ulaw<o:p></o:p></p><p class=gmail-msonormal>acl = acl1<o:p></o:p></p><p class=gmail-msonormal> <o:p></o:p></p><p class=gmail-msonormal>[identify112]<o:p></o:p></p><p class=gmail-msonormal>type = identify<o:p></o:p></p><p class=gmail-msonormal>endpoint = 1002<o:p></o:p></p><p class=gmail-msonormal>match = <a href="mailto:1002@xxx.xxx.xxx.xxx" target="_blank">1002@xxx.xxx.xxx.xxx</a><o:p></o:p></p></div></div><div><p class=gmail-msonormal> <o:p></o:p></p></div><div><p class=gmail-msonormal> <o:p></o:p></p></div><div><p class=gmail-msonormal>Check this first... identify112 probably failed to load because the match parameter can only take an ip address<o:p></o:p></p></div><div><p class=gmail-msonormal>plus an optional netmask, or a hostname. The '1002@' is invalid.<o:p></o:p></p></div><div><p class=gmail-msonormal> <o:p></o:p></p></div><div><p class=gmail-msonormal> <o:p></o:p></p></div><div><p class=gmail-msonormal> <o:p></o:p></p></div><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=gmail-msonormal> <o:p></o:p></p><p class=gmail-msonormal>I setup the registration and the endpoint.<o:p></o:p></p><p class=gmail-msonormal> <o:p></o:p></p><p class=gmail-msonormal>[286]<o:p></o:p></p><p class=gmail-msonormal>type = aor<o:p></o:p></p><p class=gmail-msonormal>remove_existing = yes<o:p></o:p></p><p class=gmail-msonormal>contact = <a href="sip:286@xxx.xxx.xxx.xxx">sip:286@xxx.xxx.xxx.xxx</a><o:p></o:p></p><p class=gmail-msonormal>qualify_frequency = 60<o:p></o:p></p><p class=gmail-msonormal> <o:p></o:p></p><p class=gmail-msonormal>[auth8]<o:p></o:p></p><p class=gmail-msonormal>type = auth<o:p></o:p></p><p class=gmail-msonormal>username = 286<o:p></o:p></p><p class=gmail-msonormal>password = yyyyyyyyyyyyyyy<o:p></o:p></p><p class=gmail-msonormal> <o:p></o:p></p><p class=gmail-msonormal>[286]<o:p></o:p></p><p class=gmail-msonormal>type = endpoint<o:p></o:p></p><p class=gmail-msonormal>context = mycontext<o:p></o:p></p><p class=gmail-msonormal>transport = transport1<o:p></o:p></p><p class=gmail-msonormal>outbound_auth = auth8<o:p></o:p></p><p class=gmail-msonormal>aors = 286<o:p></o:p></p><p class=gmail-msonormal>accountcode = 22<o:p></o:p></p><p class=gmail-msonormal>dtmf_mode = inband<o:p></o:p></p><p class=gmail-msonormal>device_state_busy_at = 48<o:p></o:p></p><p class=gmail-msonormal>force_rport = no<o:p></o:p></p><p class=gmail-msonormal>disallow = all<o:p></o:p></p><p class=gmail-msonormal>allow = ulaw<o:p></o:p></p><p class=gmail-msonormal>acl = acl1<o:p></o:p></p><p class=gmail-msonormal> <o:p></o:p></p><p class=gmail-msonormal>[registration3]<o:p></o:p></p><p class=gmail-msonormal>type = registration<o:p></o:p></p><p class=gmail-msonormal>transport = transport1<o:p></o:p></p><p class=gmail-msonormal>client_uri = <a href="sip:286@zzz.zzz.zzz.zzz">sip:286@zzz.zzz.zzz.zzz</a><o:p></o:p></p><p class=gmail-msonormal>server_uri = <a href="sip:xxx.xxx.xxx.xxx">sip:xxx.xxx.xxx.xxx</a><o:p></o:p></p><p class=gmail-msonormal>contact_user = 286<o:p></o:p></p><p class=gmail-msonormal>outbound_auth = auth8<o:p></o:p></p><p class=gmail-msonormal>expiration = 3600<o:p></o:p></p><p class=gmail-msonormal> <o:p></o:p></p><p class=gmail-msonormal>The registration for the second endpoint works fine. However, when I call through the other system for 286, it is failing. For the INVITE from the other switch, the from_user varies depending on who is calling. Asterisk logs report “No matching endpoint found” when it processes the INVITE for 286.<o:p></o:p></p><p class=gmail-msonormal> <o:p></o:p></p><p class=gmail-msonormal>I believe the reason INVITEs work for the other channel is because they are programmed to support the match for this IP address.<o:p></o:p></p><p class=gmail-msonormal> <o:p></o:p></p><p class=gmail-msonormal>Can anyone offer some suggestions?<o:p></o:p></p></div></div></blockquote><div><p class=gmail-msonormal> <o:p></o:p></p></div><div><p class=gmail-msonormal>You may be able to use the 'line and 'endpoint' registration parameters...<o:p></o:p></p></div><div><p class=gmail-msonormal>[registration3]<o:p></o:p></p></div><div><p class=gmail-msonormal>type = registration<o:p></o:p></p></div><div><p class=gmail-msonormal>...<o:p></o:p></p></div><div><p class=gmail-msonormal>line = yes<o:p></o:p></p></div><div><p class=gmail-msonormal>endpoint = 286<o:p></o:p></p></div><div><p class=gmail-msonormal> <o:p></o:p></p></div><div><p class=gmail-msonormal>This causes asterisk to put the encoded endpoint name in the outgoing Contact header. If the provider properly echos back Contact parameters when sending responses or new requests, asterisk will use the line parameter to match an endpoint. I'll have to double check but I believe we do that BEFORE checking any identify object for a match.<o:p></o:p></p></div><div><p class=gmail-msonormal> <o:p></o:p></p></div><div><p class=gmail-msonormal> <o:p></o:p></p></div><div><p class=gmail-msonormal> <o:p></o:p></p></div><div><p class=gmail-msonormal> <o:p></o:p></p></div><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'><p class=gmail-msonormal><br>--<br>_____________________________________________________________________<br>-- Bandwidth and Colocation Provided by <a href="http://www.api-digital.com" target="_blank">http://www.api-digital.com</a> --<br><br>Check out the new Asterisk community forum at: <a href="https://community.asterisk.org/" target="_blank">https://community.asterisk.org/</a><br><br>New to Asterisk? Start here:<br> <a href="https://wiki.asterisk.org/wiki/display/AST/Getting+Started" target="_blank">https://wiki.asterisk.org/wiki/display/AST/Getting+Started</a><br><br>asterisk-users mailing list<br>To UNSUBSCRIBE or update options visit:<br> <a href="http://lists.digium.com/mailman/listinfo/asterisk-users" target="_blank">http://lists.digium.com/mailman/listinfo/asterisk-users</a><o:p></o:p></p></blockquote></div><p class=gmail-msonormal><br><br clear=all><o:p></o:p></p><div><p class=gmail-msonormal> <o:p></o:p></p></div><p class=gmail-msonormal>-- <o:p></o:p></p><div><div><p class=gmail-msonormal><span style='font-size:9.5pt'>George Joseph<br>Digium, Inc. | Software Developer<br>445 Jan Davis Drive NW - Huntsville, AL 35806 - US<br>Check us out at: </span><a href="http://www.digium.com/" target="_blank"><span style='font-size:9.5pt;color:#1155CC'>www.digium.com</span></a><span style='font-size:9.5pt'> & </span><a href="http://www.asterisk.org/" target="_blank"><span style='font-size:9.5pt;color:#1155CC'>www.asterisk.org</span></a><o:p></o:p></p><div><p class=gmail-msonormal> <o:p></o:p></p></div></div></div></div></div></div></div></div></div><p class=MsoNormal><br>--<br>_____________________________________________________________________<br>-- Bandwidth and Colocation Provided by <a href="http://www.api-digital.com" target="_blank">http://www.api-digital.com</a> --<br><br>Check out the new Asterisk community forum at: <a href="https://community.asterisk.org/" target="_blank">https://community.asterisk.org/</a><br><br>New to Asterisk? Start here:<br> <a href="https://wiki.asterisk.org/wiki/display/AST/Getting+Started" target="_blank">https://wiki.asterisk.org/wiki/display/AST/Getting+Started</a><br><br>asterisk-users mailing list<br>To UNSUBSCRIBE or update options visit:<br> <a href="http://lists.digium.com/mailman/listinfo/asterisk-users" target="_blank">http://lists.digium.com/mailman/listinfo/asterisk-users</a><o:p></o:p></p></blockquote></div><p class=MsoNormal><br><br clear=all><o:p></o:p></p><div><p class=MsoNormal><o:p> </o:p></p></div><p class=MsoNormal>-- <o:p></o:p></p><div><div><p class=MsoNormal><span style='font-size:9.5pt'>George Joseph<br>Digium, Inc. | Software Developer<br>445 Jan Davis Drive NW - Huntsville, AL 35806 - US<br>Check us out at: </span><a href="http://www.digium.com/" target="_blank"><span style='font-size:9.5pt;color:#1155CC'>www.digium.com</span></a><span style='font-size:9.5pt'> & </span><a href="http://www.asterisk.org/" target="_blank"><span style='font-size:9.5pt;color:#1155CC'>www.asterisk.org</span></a><o:p></o:p></p><div><p class=MsoNormal><o:p> </o:p></p></div></div></div></div></div></div></body></html>