The UK Home Automation Archive

Archive Home
Group Home
Search Archive


Advanced Search

The UKHA-ARCHIVE IS CEASING OPERATIONS 31 DEC 2024


[Message Prev][Message Next][Thread Prev][Thread Next][Message Index][Thread Index]

Re: Caller ID


  • Subject: Re: Caller ID
  • From: "David Buckley" <db@xxxxxxxxxxx>
  • Date: Fri, 09 Jul 2004 12:56:26 -0000

--- In ukha_d@xxxxxxx, "UKHA" <ukha@b...> wrote:
> unfortunately the author actually shows far to much
> ignorance - this is NOT A VOIP ISSUE..

Indeed.

There are two underlying problems, both to do with PRI ISDN

a) PRIs expose the connection protocols used by telephone switching
equipment in a way that analog circuits never did, and

b) Primary rate ISDN only used to go to "trustworthy-ish" folks,
who
ran standard PABXs from established manufacturers that played by the
rules, including those rules not enforced technically, but as an
agreement between organisations.

Now, anyone can have for not much money a PRI interface on their PC,
and get a PRI line for not a huge amount of money, and is then in
the world of telecom signalling, and can do lots of things they
probably shouldnt.  It just so happens that folks doing this are
running VOIP applications.

> it's bollocks...

Its not quite; it is real, it does happen, and with the aid of 20/20
hindsight perhaps it was inevitable that this would occur.  Even if
the authors of asterisk had made the program less trusting than it
is, its open source, and thus could be hacked, probably trivially.

What needs to happen is that the "proper" exchange manufacturers
need to code up filtering rule capability on each trunk port, so
that signalling manipulation can be allowed only for suitably
qualified equipment and/or organisations.


> there, I've said my piece :D

Good man!

David.





UKHA_D Main Index | UKHA_D Thread Index | UKHA_D Home | Archives Home

Comments to the Webmaster are always welcomed, please use this contact form . Note that as this site is a mailing list archive, the Webmaster has no control over the contents of the messages. Comments about message content should be directed to the relevant mailing list.