<html><head><meta http-equiv="Content-Type" content="text/html; charset=us-ascii"><meta name="Generator" content="Microsoft Word 15 (filtered medium)"><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;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0cm;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri",sans-serif;
mso-fareast-language:EN-US;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:#0563C1;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:#954F72;
text-decoration:underline;}
span.EmailStyle17
{mso-style-type:personal-compose;
font-family:"Calibri",sans-serif;
color:windowtext;}
.MsoChpDefault
{mso-style-type:export-only;
font-family:"Calibri",sans-serif;
mso-fareast-language:EN-US;}
@page WordSection1
{size:612.0pt 792.0pt;
margin:72.0pt 72.0pt 72.0pt 72.0pt;}
div.WordSection1
{page:WordSection1;}
--></style></head><body lang="EN-CA" link="#0563C1" vlink="#954F72"><div class="WordSection1"><p class="MsoNormal"> </p><p class="MsoNormal">Anyone using SecureLogix and can comment on their ability to </p><p class="MsoNormal"> </p><table class="MsoNormalTable" border="0" cellspacing="0" cellpadding="0" width="625" style="width:468.75pt"><tr><td style="padding:0cm 0cm 0cm 0cm"><p class="MsoNormal">“<span style="font-size:9.0pt;font-family:"Arial",sans-serif;color:black">Prevent service abuse and malicious or unwanted voice traffic to lower expenses and boost your security and compliance efforts.</span></p></td></tr><tr><td style="padding:0cm 0cm 0cm 0cm"></td></tr></table><p class="MsoNormal">“</p><p class="MsoNormal"><a href="http://www.securelogix.com/Telephony-Denial-Of-Service/index.htm">http://www.securelogix.com/Telephony-Denial-Of-Service/index.htm</a></p><p class="MsoNormal"> </p><p class="MsoNormal">It sounds like it isn’t just an SBC-type prevention of SIPVicious-style attacks, but also TDM blocking based on “ policy fields— call type; absence or blocking of caller ID, call source and destination numbers; call direction; time of call; call length; and certain VoIP call attributes, such as excessive media rate”</p><p class="MsoNormal"> </p><p class="MsoNormal">I understand this can sound appealing, but having had to deal with a few TDOS attacks, I am not sure how well does this would work in practice.</p><p class="MsoNormal"> </p><p class="MsoNormal">Anyone able to comment? </p><p class="MsoNormal"> </p><p class="MsoNormal"> </p><p class="MsoNormal"><span style="color:#1f497d">Best Regards,</span><span style="mso-fareast-language:EN-CA"></span></p><p class="MsoNormal"><span style="color:#1f497d"> </span><span style="mso-fareast-language:EN-CA"></span></p><p class="MsoNormal"><span style="color:#1f497d">Ivan Kovacevic</span><span style="mso-fareast-language:EN-CA"></span></p><p class="MsoNormal"><span lang="EN-US" style="color:#1f497d">Vice President, Client Services</span><span style="mso-fareast-language:EN-CA"></span></p><p class="MsoNormal"><span style="color:#1f497d">Star Telecom | <a href="http://www.startelecom.ca/"><span style="color:blue">www.startelecom.ca</span></a> | SIP Based Services for Contact Centers | <a href="https://www.linkedin.com/company/star-telecom-www-startelecom-ca-?trk=biz-companies-cym"><span style="color:blue">LinkedIn</span></a></span><span style="mso-fareast-language:EN-CA"></span></p><p class="MsoNormal"> </p></div></body></html>