<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=Content-Type content="text/html; charset=iso-8859-1">
<META content="MSHTML 6.00.2800.1498" name=GENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY bgColor=#ffffff>
<DIV><FONT face=Arial size=2>I think it's important to first define what toll
fraud is to your organization. I tried to get some help from our carrier to help
define it, but with little help. We have international students so there is very
little we can do to stop calls to international countries, whether or not they
are targetted as high risk.</FONT></DIV>
<DIV><FONT face=Arial size=2></FONT> </DIV>
<DIV><FONT face=Arial size=2>There is a new 'transfer' restriction service
parameter which stops someone from transferring an offnet call to another offnet
call, something that has been identified as toll fraud in the past.</FONT></DIV>
<DIV><FONT face=Arial size=2></FONT> </DIV>
<DIV><FONT face=Arial size=2>Also, if you have Unity, you should make sure your
Unity ports do not have access to off-net dialing unless you absolutely need it,
i.e. for message notification, and then you should really only need local
access.</FONT></DIV>
<DIV><FONT face=Arial size=2></FONT> </DIV>
<DIV><FONT face=Arial size=2>And as you mentioned securing your call forwarding
search space is also important.</FONT></DIV>
<DIV><FONT face=Arial size=2></FONT> </DIV>
<DIV><FONT face=Arial size=2>That all being said, we block 900 and 976 calling
as well as 809.</FONT></DIV>
<DIV><FONT face=Arial size=2></FONT> </DIV>
<DIV><FONT face=Arial size=2>It's also important to isolate long distance versus
international charged calls which use NANP area codes and put them in a
different class.</FONT></DIV>
<DIV><FONT face=Arial size=2></FONT> </DIV>
<DIV><FONT face=Arial size=2>Hope that helps.</FONT></DIV>
<DIV>-----
-----<BR>Lelio Fulgenzi,
B.A.
<A href="mailto:lelio@uoguelph.ca.eh">lelio@uoguelph.ca.eh</A><BR>Network
Analyst (CCS)<BR>University of
Guelph
FAX:(519) 767-1060 JNHN<BR>Guelph, Ontario N1G
2W1
TEL:(519) 824-4120
x56354<BR>^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^<BR>mob
lawyer: your people insulted my brother.<BR>dr. house: what? romano in the
parmesan cheese shaker again?</DIV>
<BLOCKQUOTE
style="PADDING-RIGHT: 0px; PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #000000 2px solid; MARGIN-RIGHT: 0px">
<DIV style="FONT: 10pt arial">----- Original Message ----- </DIV>
<DIV
style="BACKGROUND: #e4e4e4; FONT: 10pt arial; font-color: black"><B>From:</B>
<A title=Scott.Voll@wesd.org href="mailto:Scott.Voll@wesd.org">Voll, Scott</A>
</DIV>
<DIV style="FONT: 10pt arial"><B>To:</B> <A title=cisco-voip@puck.nether.net
href="mailto:cisco-voip@puck.nether.net">cisco-voip@puck.nether.net</A> </DIV>
<DIV style="FONT: 10pt arial"><B>Sent:</B> Wednesday, May 04, 2005 12:26
PM</DIV>
<DIV style="FONT: 10pt arial"><B>Subject:</B> [cisco-voip] Toll Fraud</DIV>
<DIV><BR></DIV>How do I prevent toll-fraud?<BR><BR>I have route patterns that
block calls to the Bahamas, virgin islands,<BR>grenda, guam, etc. all
the numbers that look like US numbers but are<BR>not.<BR><BR>I can also setup
every ones call forward search space to only allow<BR>local calls. What
else can I do to prevent
toll-fraud?<BR><BR>Thanks<BR><BR>Scott<BR><BR><BR>_______________________________________________<BR>cisco-voip
mailing list<BR><A
href="mailto:cisco-voip@puck.nether.net">cisco-voip@puck.nether.net</A><BR><A
href="https://puck.nether.net/mailman/listinfo/cisco-voip">https://puck.nether.net/mailman/listinfo/cisco-voip</A><BR></BLOCKQUOTE></BODY></HTML>