<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
In most cases you will lose this customer. They don't see this as
their responsibility (i.e. the credit card fraud defense) but the
reality is their equipment was compromised due to their negligence.
<br>
<br>
If the customer is reasonable offer them your cost on the damages so
its just a passthrough. Otherwise you can take them to court or just
send them to collections. <br>
<br>
BTW while many will advocate fraud detection and mitigation systems
here, its been my experience (we wrote our own fraud system that
out-performs our upstream carriers by hours) that if you detect
fraud on a customer like this, and shut it down in minutes, and
mitigate what could have been thousands of dollars in damage due to
their mis-configured systems, reducing it to just tens or hundreds
they will often still fight that amount and deny responsibility. The
fraud system protects you, and by extension the customer, but the
customers don't see it that way. <br>
<br>
-Ryan<br>
<br>
<br>
<br>
<div class="moz-cite-prefix">On 02/19/2014 02:09 PM, John Curry
wrote:<br>
</div>
<blockquote
cite="mid:00e101cf2dbf$3cfbc490$b6f34db0$@InteleChoice.us"
type="cite">
<meta http-equiv="Content-Type" content="text/html;
charset=ISO-8859-1">
<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;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri","sans-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-compose;
font-family:"Calibri","sans-serif";
color:windowtext;}
.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]-->
<div class="WordSection1">
<p class="MsoNormal">I am new to your site. I was looking in the
Archives and saw in November 2013 there were some of you who
experienced fraud. We had a an Avaya IP Office customers
system who got hit pretty bad. The customer is treating the
fraudulent calls like credit card fraud and not taking any
responsibility. Does anyone have any advice on how to persuade
the customer take this issue seriously? His bill was racked
up pretty good. Strangely and coincidentally Avaya came out
with a security bulletin the end of December 2013 on this same
issue. I tried to contact Avaya with no response. It seems as
though someone has built a sniffer for the Avaya IP Offices
and gleaning their registrations.<o:p></o:p></p>
</div>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">_______________________________________________
VoiceOps mailing list
<a class="moz-txt-link-abbreviated" href="mailto:VoiceOps@voiceops.org">VoiceOps@voiceops.org</a>
<a class="moz-txt-link-freetext" href="https://puck.nether.net/mailman/listinfo/voiceops">https://puck.nether.net/mailman/listinfo/voiceops</a>
</pre>
</blockquote>
<br>
</body>
</html>