[VoiceOps] Phone Spoofing - Anything we can do?

Eric Wieling ewieling at nyigc.com
Thu May 26 15:21:54 EDT 2016


This accomplishes "only allow INVITES from SIP registrar" on Polycom 
SoundPoint IP and VVX phones.

     <voIpProt.SIP voIpProt.SIP.strictUserValidation="1></<voIpProt.SIP>

On 05/26/2016 03:20 PM, John S. Robinson wrote:
> 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.)
>
> 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.
>
> 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.
>
> Communichanic Consultants, Inc.
> John S. Robinson, President
> /office:/   708-246-8900
>
>
> On 5/24/2016 23:40, Mike Ray, MBA, CNE, CTE wrote:
>> 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
>> http://www.astrocompanies.com
>>
>>
>>
>>
>>
>> -----Original Message-----
>> From: VoiceOps [mailto:voiceops-bounces at voiceops.org] On Behalf Of Peter
>> Beckman
>> Sent: Wednesday, May 25, 2016 12:00 AM
>> To: VoiceOps<voiceops at voiceops.org>
>> 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
>> beckman at angryox.com                                  http://www.angryox.com/
>> ---------------------------------------------------------------------------
>> _______________________________________________
>> VoiceOps mailing list
>> VoiceOps at voiceops.org
>> https://puck.nether.net/mailman/listinfo/voiceops
>>
>> _______________________________________________
>> VoiceOps mailing list
>> VoiceOps at voiceops.org
>> https://puck.nether.net/mailman/listinfo/voiceops
>>
>>
>
>
>
> _______________________________________________
> VoiceOps mailing list
> VoiceOps at voiceops.org
> https://puck.nether.net/mailman/listinfo/voiceops

-- 
if at first you don't succeed, skydiving isn't for you

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://puck.nether.net/pipermail/voiceops/attachments/20160526/4507e405/attachment.html>


More information about the VoiceOps mailing list