[VoiceOps] Strange calling patterns
David.Hiers at adp.com
Tue Nov 6 09:38:13 EST 2012
Phone Jamming is a time-honored political tradition, just ask Allen Raymond.
Keep your logs/cdrs handy, the Feds might visit.
From: voiceops-bounces at voiceops.org [mailto:voiceops-bounces at voiceops.org] On Behalf Of Ryan Delgrosso
Sent: Monday, November 05, 2012 16:10
To: voiceops at voiceops.org
Subject: [VoiceOps] Strange calling patterns
So I know with the election tomorrow all bets are basically off for weird calling patterns but I have seen some really strange stuff today and was hoping someone else might have seen it as well or be able to validate some theories.
I had a number in a Michigan exchange receive 99,000 inbound calls in a single hour (no that is actually ninety nine thousand) and that user had their number forwarded off to another overloaded Michigan exchange so it generated nearly a million outbound call attempts as my system attempted to find an open trunk to get through. Earlier I had a similar case with a Florida exchange where a single user received 150,000 calls in an hour all with invalid source numbers, and all arrived through otherwise reputable origination carriers (L3, Paetec etc).
The commonality here is that in both cases the customer account had no registered device and had forwarding setup, and the destination for both was an overloaded exchange in a swing state. In all cases I have suspended the accounts and stopped the traffic but it still doesn't give me the warm and fuzzies.
My first inclination is this feels like some kind of DDOS to hurt polling or last minute campaigning since if the attempts were legitimate they wouldn't be winning supporters by calling them 150,000 times but im really open to ideas here.
Anyone out there with some experience or theories, feel free to chime in or reply off list if paranoid.
VoiceOps mailing list
VoiceOps at voiceops.org
This message and any attachments are intended only for the use of the addressee and may contain information that is privileged and confidential. If the reader of the message is not the intended recipient or an authorized representative of the intended recipient, you are hereby notified that any dissemination of this communication is strictly prohibited. If you have received this communication in error, please notify us immediately by e-mail and delete the message and any attachments from your system.
More information about the VoiceOps