VoIP Mailing List Archives

[nk3569 at yahoo.com]

--- On Mon, 5/12/08, Trixter aka Bret McDanel <trixter@0xdecafbad.com> wrote:

[asterisk at wideideas.com]

On May 12, 2008, at 4:05 PM, Nitzan Kon wrote:

[nk3569 at yahoo.com]

We can (and will) set the Caller ID for you to something you
request, and we can have multiple peer definitions with
different CIDs defined to each if you need to switch between
them.

Not as nice as setting it yourself - but it should work for
the purposes you mention.

-- Nitzan

--- On Mon, 5/12/08, Bill Michaelson <bill@cosi.com> wrote:

[jra at baylink.com]

On Mon, May 12, 2008 at 08:26:35PM -0400, Alex Balashov wrote:

[bill at cosi.com]

How does this address the forwarding requirement, for which I cannot know in advance what CID I will be sending?

Nitzan Kon wrote:

[asterisk-biz at ics-il...]

Just because something is illegal doesn't mean it can't be done. Once it left what I initially asked, I stopped paying attention, but it sounds like Steve wants to make it so it CAN'T happen.


----------
Mike Hammett
Intelligent Computing Solutions
http://www.ics-il.com

[asterisk-biz at ics-il...]

I'm going to attempt to sum up things discussed on various lists.

ANI and CNID are two different things, though are often the same number. BTN is yet another item that may or may not be the same.

ANI can be spoofed, though details not revealed on list for obvious reasons.

Toll free, premium (900), and 911 numbers receive the ANI since one of them is being billed for the call and the other is billing for services rendered. That's why collection services and private investigators have you return calls on a toll free line.

You need SS7 or someone above you that has SS7 to set ANI as CNID to view the ANI.

Some people think there should be regulation against ANI manipulation, others don't.



----------
Mike Hammett
Intelligent Computing Solutions
http://www.ics-il.com

[abalashov at evaristes...]

Jay R. Ashworth wrote:

[astmattf at gmail.com]

Hello,

I just wanted to add my personal ANI story since this thread has
gotten so long anyway. I had been under the impression for years that
ANI was always correct and could not be spoofed. that was until I met
one of my client's cut rate telco provider. They are based in Orlando,
FL(and that's all I will mention about the company itself) and somehow
they manage to not send ANI on some calls coming in on 800 numbers.
This confused the heck out of me because for years I thought that was
impossible. But there it was, blank ANI. I could not spoof CallerID as
I could on local T1 circuits, but for some reason every once in a
while the ANI on inoming 800 number calls would show up blank. The
carrier had no clue it was happening and said if that happens then
they just wouldn't bill the client. And it stayed like that for months
until something stranger happened...

One day I got a call from the client that they were being call blasted
from the same number in Orlando. So I went into their logs and noticed
the same ANI had called them over 300 times that morning already, but
the weird part is that many of those calls were answered and had talk
time. I asked the client about it and they started looking at it and
figured out that there were people on the other end of these calls,
and not all the same people. It turns out that the carrier was sending
the same ANI for every call coming into the 800 numbers from certain
areas in Florida. That stopped later that day(again with no
explanation from the carrier) and has happened again a few times since
as well.

So the lessons I took away from this is that ANI can certainly be
messed with, and stay away from cut-rate telco providers.

MATT---

On 5/12/08, Mike Hammett <asterisk-biz@ics-il.net> wrote:

[stotaro at totarotechn...]

Mike,

Apologies for taking your biz question and changing it to a biz/users
discussion. It was not my intention but as you can see, it is has
catalized from your initial post, it is not just me that has continued
this topic and brought up other valid points, my posts amount to less
than other posters.

I am not sure what the longest thread is on the Asterisk lists, but
this has got to almost be a record, hence discussion and opinion is
good.

Although there are some laws to address spoofing ANI, it can be done
with no trace as things are now. Many very serious things could be
done to ruin people's life, liberty, and pursuit of happiness with no
way to clear their name. I don't think you have the imagination of
what could be done and be totally untraceable.

Anyways, you have sole control of what you pay attention to so don't
pay attention so simply ignore the thread, it is pretty simple, just
as you would spam..

BTW, I do not use the word "CANT", you are dooming yourself to
distraction and failure.

Thanks,
Steve Totaro





On Mon, May 12, 2008 at 11:06 PM, Mike Hammett <asterisk-biz@ics-il.net> wrote:

[asterisk-biz at ics-il...]

Discussion about things semi-on topic is good. I just have little to add
because I'm not educated on the matter.

Thanks for all the constructive conversation.


----------
Mike Hammett
Intelligent Computing Solutions
http://www.ics-il.com


----- Original Message -----
From: "Steve Totaro" <stotaro@totarotechnologies.com>
To: "Commercial and Business-Oriented Asterisk Discussion"
<asterisk-biz@lists.digium.com>
Sent: Tuesday, May 13, 2008 6:51 AM
Subject: Re: [asterisk-biz] ANI

[stotaro at totarotechn...]

Nitzan,

Maybe you are unaware that all of this could be done with *absolutely*
no way to trace it back to the "Culprit".

If you cannot trace it back to the culprit AND more importantly, clear
the INNOCENT, then more regulation is needed.

"Culprit -> VoIP carrier who lets set CID/ANI -> ILEC or CLEC ->
terminated to PSTN." would be stupid.

This make more sense:
Open WiFi AP (or cracked WEP) ----> hacked Asterisk box (who sets the
CID/ANI ----> Telco ------> terminated to the PSTN

Be sure to delete appropriate logs on the hacked Asterisk boxen and just
to be safe, spoof your laptop's MAC address. Perform your exploit
somewhere inconspicuous and a good distance from "home, then clean your
laptop by using DBAN http://dban.sourceforge.net/ which is DoD 5220.22-M
compliant, before re-installing your OS"......

Thanks,
Steve Totaro


Nitzan Kon wrote:

[abalashov at evaristes...]

Steve Totaro wrote:

[trixter at 0xdecafbad.com]

On Tue, 2008-05-13 at 12:41 -0400, Steve Totaro wrote:

[stotaro at totarotechn...]

Alex Balashov wrote: