<html>
<head>
<meta content="text/html; charset=windows-1252"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
This accomplishes "only allow INVITES from SIP registrar" on Polycom
SoundPoint IP and VVX phones.<br>
<br>
<voIpProt.SIP
voIpProt.SIP.strictUserValidation="1></<voIpProt.SIP><br>
<br>
<div class="moz-cite-prefix">On 05/26/2016 03:20 PM, John S.
Robinson wrote:<br>
</div>
<blockquote
cite="mid:594a5238-8f1a-9243-c1b0-2d2e13254860@communichanic.com"
type="cite">
<meta http-equiv="Context-Type" content="text/html;
charset=windows-1252">
In a SIP environment many UA's have a feature "only allow INVITES
from SIP registrar" or words to that effect. Another possibility
might be to challenge incoming INVITEs (and other SIP methods) if
the host switch and CPE supports challenge. (Metaswitch for
example is actually quite aggressive with use of challenge
responses on most transactions.) <br>
<br>
Those SIP techniques along with good IP access control or NAT can
substantially reduce SPIT (SPam Internet Telephony.) Is there a
Federal "Truth in Caller ID Act?" If yes, it is probably only
enforceable on Interstate calls, and then you need to find someone
who has the competence, standing and urgency to enforce it. <br>
<br>
I am not a lawyer, but I know that law can vary from State to
State. Illinois had a "don't lie about caller ID" statute before
our legislature, but it got voted down. <br>
<br>
Communichanic Consultants, Inc.<br>
John S. Robinson, President<br>
<i>office:</i> 708-246-8900<br>
<br>
<br>
<div class="moz-cite-prefix">On 5/24/2016 23:40, Mike Ray, MBA,
CNE, CTE wrote:<br>
</div>
<blockquote
cite="mid:072d01d1b63f$8dbe9f50$a93bddf0$@astrocompanies.com"
type="cite">
<pre wrap="">We get these calls all the time, and the offending call never originates
from our network. We tell the caller that they can try two remedies:
1. Call their own phone company and file a nuisance call report and,
2. Call local law enforcement and file a harassment complaint (if the case
warrants it)
3. File a complaint with the FTC if it's just a sales call to a do-not-call
list subscriber
None of these actually does anything. However, it makes the caller feel
like there is some action they can take and properly put the investigative
burden on their carrier. More likely, their carrier will give them options
for blocking the number instead of opening a nuisance incident.
Regards,
Mike
Mike Ray, MBA, CNE, CTE
Astro Companies, LLC
11523 Palm Brush Trail #401
Lakewood Ranch, FL 34202
DIRECT: call or text 941 600-0207
<a moz-do-not-send="true" class="moz-txt-link-freetext" href="http://www.astrocompanies.com">http://www.astrocompanies.com</a>
-----Original Message-----
From: VoiceOps [<a moz-do-not-send="true" class="moz-txt-link-freetext" href="mailto:voiceops-bounces@voiceops.org">mailto:voiceops-bounces@voiceops.org</a>] On Behalf Of Peter
Beckman
Sent: Wednesday, May 25, 2016 12:00 AM
To: VoiceOps <a moz-do-not-send="true" class="moz-txt-link-rfc2396E" href="mailto:voiceops@voiceops.org"><voiceops@voiceops.org></a>
Subject: [VoiceOps] Phone Spoofing - Anything we can do?
Have a customer, they are getting calls on their number that indicate
another party is spoofing their number.
"You just called me."
"I just got a call from this number?"
And it isn't them, not through my systems.
Has anyone figured out a process that is even somewhat effective in hunting
down and ending the spoofing, while actually getting that Truth in Caller ID
Act violation filed against them?
Or is it just as impossible as I suspect?
Beckman
---------------------------------------------------------------------------
Peter Beckman Internet Guy
<a moz-do-not-send="true" class="moz-txt-link-abbreviated" href="mailto:beckman@angryox.com">beckman@angryox.com</a> <a moz-do-not-send="true" class="moz-txt-link-freetext" href="http://www.angryox.com/">http://www.angryox.com/</a>
---------------------------------------------------------------------------
_______________________________________________
VoiceOps mailing list
<a moz-do-not-send="true" class="moz-txt-link-abbreviated" href="mailto:VoiceOps@voiceops.org">VoiceOps@voiceops.org</a>
<a moz-do-not-send="true" class="moz-txt-link-freetext" href="https://puck.nether.net/mailman/listinfo/voiceops">https://puck.nether.net/mailman/listinfo/voiceops</a>
_______________________________________________
VoiceOps mailing list
<a moz-do-not-send="true" class="moz-txt-link-abbreviated" href="mailto:VoiceOps@voiceops.org">VoiceOps@voiceops.org</a>
<a moz-do-not-send="true" class="moz-txt-link-freetext" href="https://puck.nether.net/mailman/listinfo/voiceops">https://puck.nether.net/mailman/listinfo/voiceops</a>
</pre>
</blockquote>
<br>
<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>
<pre class="moz-signature" cols="72">--
if at first you don't succeed, skydiving isn't for you</pre>
</body>
</html>