Open Source Telephony Gives Customers Control
Linux.com's Tina Gasperson recently had the chance to sit down and talk with Thomas Howe, a small shop owner working to help implement open source telephony solutions. "Howe says open code is the key to highly customizable phone systems that truly meet the needs of individual companies. 'The telecom world has typically been a very closed environment. In terms of technology and deployment, they control every aspect of the experience. The idea of being open and allowing customers to have control is a radical thought.' But that is just what Howe is doing. Howe bases his custom communications solutions on Asterisk, the popular full-featured open source telephony engine that many companies are adopting as they move away from legacy phone systems in an effort to save money and gain more control over their infrastructure."
Why does that article feel like it's an advertisement? Linux.com has a particular audience and I don't believe you need to sell them on the merits of open source software...
It just felt empty.
I am a small business owner and we use Junction Networks for our telephone system. Their services are standards based (e.g. SIP federation) and don't have stupid limitations like Vonage (who charge per line instead of just usage) or Skype (who don't federate with other SIP providers). The hosted PBX is pretty nice or you can use IAX trunking if you prefer to run your own Asterisk PBX. I am not affiliated with them - just a happy customer. If you're a small business I recommend you check them out.
Bradley Holt
Sometime back, I stumbled upon this iphone+bluetooth+asterisk combo app (though works for any bt-phone) and was surprised by the power of asterisk.. From curiosity, How easy is it to set up an asterisk for personal purpose at home? Anyone implemented a setup and care to share some opinions?
lawlz
How open is open, and how open should open be?
Telecommunications is a critical commons and I fear what phishers/advertisers/malware distributors might be able to do it they are given too much access to the code.
Two wrongs don't make a right, but three lefts do.
You can in fact pass along any CallerID you like and it will be then passed along to the end user if and only if the telecom provider supports it and chooses to pass it along based on your past history of using good numbers. Any telecom provider (VOIP or Traditional) can just reject the numbers and replace it with the main number of the business.
Alright, I don't claim enough knowledge of telecommunications to respond to this. It appears to be security through obscurity. I say we try an experiment and offer knowledgeable opinions as to why or why not we should treat tcom differently from other open systems.
:)
Please write clearly as I intend to plagiarize your statements for my thesus
I read, "open source telepathy gives customers control".
fear what phishers/advertisers/malware distributors might be able to do
Well, the flipside is that of security. Open code will reveal bugs. These bugs will be fixed, and the code will be more secure. Don't forget that companies selling platforms on asterik have to support their products. Customers get mad when their telephones go down from hacking. The companies that sell asterik will have an incentive to fix the problem.
Linux.com doesn't display under IE7, so I tried it under FireFox. It loads, but there's a Windows Server ad on the front page... Wow
... to make telecoms systems work properly. Most protocol suites are sufficiently poorly specified that a certain amount of folklore, which you can only gain from years in the industry, is necessary as well as a careful reading of the specs.
... yeah, right.
... and I mean mass market rock-solid stable phones like bog standard Nokias ... where the "bug" is its failure to implement some detail of the standard that has never been needed in a live network. Great fun to play with, to be sure, if you've got your own private base station and a bunch of test SIMs, but you don't want people doing this sort of playing in important parts of the live system.)
I really do hate to think what would happen to the world's telephone system if vital pieces of infrastructure have code in them that is randomly hacked around by amateurs, well-meaning or otherwise. "Look, this must work, look, it says so here in the spec, my code follows the standards, it's all the other guys who are wrong, they should fix theirs"
(Example: as soon as you do something to base station code which looks perfectly allowed according to the GSM specs but is out of the ordinary, ie is not something that current live systems routinely do, you start coming across "bugs" in phones
yes, this sytem was found to perform brilliantly here until disaster struck
Caller ID is ancient obsolete tech anyway. The question for the future: can they forge RSA signatures? Probably not.
I might point out that you can change the number displayed by caller ID in many PBX systems, not just open source ones.
transporter_ii
Doctors destroy health, lawyers destroy justice, universities destroy knowledge, religion destroys spirituality
Slashdot | Caller ID Spoofing Becomes Easy
http://hardware.slashdot.org/article.pl?sid=06/03/02/2311218
ID Spoofing for the masses:
http://slashdot.org/article.pl?sid=04/10/28/1450205
Slashdot | Caller ID Falsification Service
http://slashdot.org/article.pl?sid=04/08/30/1620237
New Google Service Manipulates Caller-ID For Free
http://yro.slashdot.org/article.pl?sid=06/11/18/2112248&from=rss
Doctors destroy health, lawyers destroy justice, universities destroy knowledge, religion destroys spirituality
Let's say I wanted to start up a company with, say, 20 employees, probably growing to three times that in a year. I know how to setup a LAN, what to purchase in PCs and peripherals, what office furniture to get, and even what legal hurdles I have to negotiate in order to get the business license and set up all the HR stuff.
What I don't know is how to set up a IP telephone system, from scratch. I've seen lots of stuff about IP Telephony in the office, and hear it is the great new thing, but every time I search on the web, all I see are lots of paragraphs talking about "solutions" and no "here's what you need: one of these boxes, these cables, these phones, this service plan."
Assuming I am not a LINUX DIY guy, and I don't want to hire someone specifically to manage telephony in addition to the normal business IT guy, where do I go for an off the shelf, or at least easily assembled, IP Telephony solution for my new company?
A home/smb PBX still has to connect to a main secure backbone exchange and as far as I remember they should validate your allocated range of callerID numbers or simply only allow a single switchboard callerID to be sent out. ISP's and Telecom's companies like cut deals and flog "authorized/validated/authenticate" hardware, but really that is more about signals strengths and kick backs than a secure box. User premises equipment must be assumed to be inherently hackable - end of story. The server/exchange side interface (ie. trusted telephone exchange) is where hacks are supposed to be caught.
Sure in theory you could spoof the exact callerID within your range, but you can argue any 3rd party home PBX system could be capable of that. At least if the source is open, there is more change of reviewing whether it is definitively possible or not, before or after an incident. With closed systems, you are completely trusting the vendor and even with court action it would be hard if not impossible to get access to their source to prove it either way.
What your home/smb does with its local PBX side is its own biz and you have to trust that yourself, just as you had to blindly trust some 3rd party PBX manufacturer of the past.
I was skimming my rss reader and thought it said open-source tele-PATHY...darn...
Having spent the last few weeks setting up Asterisk and such i've found a few things major to most smaller companies that it doesn't do well. For one, SLA or Shared Line Appearance (aka, everyone can see who's on line 1, pick up the call and answer it). While the code exists it's hard to use, the documentation is poor, and the people in the IRC channel only manage to mock those who don't know that the secret lies in a pdf buried in the subversion source code and will only expend the energy to type out some cryptic code to their bot that points you at the same tired document that doesn't answer your questions. The SLA in Asterisk *works* if you have the right equipment and the time to set it up but Linksys does it one way, Aastra another, and Polycom one more. The goals of the Asterisk project seem alright but the developers seem to have it all wrong. Rather than focusing on the features users want and getting them right they are kinda hacking it all together and deciding it needs to be worked on later. Rather than making it run well on most systems, they sacrifice things to make it run on the 133mhz machine hiding in Edison's garage. I know making it light on memory is important as too much will make voice quality horrible but there comes a point when the user side of things has to be more important. My last gripe with Asterisk is that there are a few different people working on different versions all at the same time seemingly getting nowhere. Take Asterisk, elastix, FreePBX, OpenPBX, and whatever else may be out there and get all the devs to work together and get it up to something that feels mainstream and open source worthy. Asterisk is a great project but it's still got a ways to go before it's ready for massive rollouts. The only reason i'm setting one up is that the current BizFone system we have crapped out and has been crap from day one.
We installed an Asterisk based solution at a company I owned. All open source stuff. The features and performance per $ were amazing. We loved how it could be customized to our needs and it saved a bundle. Or so we thought. Problem was, our "control" only lasted to our door. We had a great system but our ISP (Charter Cable in this instance) would drop packets, had misbehaving routers, and generally didn't give a crap that half our customers couldn't hear us or could old hear every other word we said. We just could not get a phone system that worked because we couldn't get reliable bandwidth. (yes we had uptime "guarantees" which were worth the paper they were written on since we lacked the resources to sue) Of course we could have bought their solution for about 10X the cost and were almost forced to.
IP telephony is the wave of the future and I'm very positive on the open source stuff. But unless you have copious and reliable bandwidth, beware that you may not have the control you think you do.
There are a couple of roll-ups that include Asterisk, a GUI, and other apps along with a Linux distro on a single CD. I personally have used trixbox for a home server with a telasip VOIP line. If you just want to do an easy home install on an old machine or VM you could start with one of these.
Trixbox is one of the most popular, I found it very easy to install and use. However they were featured in yesterdays article about a phone-home "feature" that allowed Fonality to run code on an installed machine.
AsteriskNOW is made by Digium, the maintainers of Asterisk. Its still in beta, but there are prebuilt VMware and Xen virtual machines ready for download if you just want to give it a try.
Elastix seems to be getting some good reviews, but the main site has been down for the past few days. The link to the left is the sourceforge pages.
exact thing here
;)
and what internet line would be needed for 8 lines?
and will a regular (high speed) fax machine work on them?
Interesting timing, i am writing up instructions for installing one of our vintage (read analog that no vendor will touch) PBX in a remote office. Curious if the internet line + phones needed + learning to setup is cheaper than POTS lines and my $100 ! PBX system
lynxcache plain-text mirror: http://lynxcache.com/Linux_com_Open_source_telephony_gives_customers_control_consultant_says.html
I fear what phishers/advertisers/malware distributors might be able to do it they are given too much access to the code
Indeed, I reckon it's a damn good thing Microsoft keeps their source closed. The mere thought of what could have happened, if the source was open, makes me cringe.
No one who means it is relying on caller id for anything anyway.
Nerd rage is the funniest rage.
Asterisk is great! OK, its configuration language is pretty sucky, but we've done some amazing things with it -- too long to post in a /. article.
Just look at the slides instead: (1.1MB PDF file)
Before I lay out my argument, let me start by saying that I really hope that one day it will be, but I am not holding my breath.
OpenSource or any other type of software that runs on a general purpose computer will not be as efficient as say a machine from Panasonic or other phone vendor, you might be able to play with the bells and whistles more, but it will just not make the grade.
Hey KID! Yeah you, get the fuck off my lawn!
You should learn/run an openser server with Asterisk as the voicemail/POTS out. Or possibly freeswitch if you are ready to get in the steep and deep end.
Keep the fax on a POTS line.
Got Trader Joe's? friendwich.com RSS feeds work now!
Most business-level ISP's are hosting or at bare minimum reselling VOIP service. Let them handle it. VOIP (like POTS) is its own special terminology and way of working.
Got Trader Joe's? friendwich.com RSS feeds work now!
Asterisk? The gall!
There are no karma whores, only moderation johns
"As a programmer, I plead guilty to lack of well defined feature descriptions. "
As a writer I plead to...Oh wait. We're talking about your shortcomings weren't we?
"Team up a freelance programmer with a freelance writer and start creating manuals (Print/PDF). "
Somehow I'm reminded of that old saying, "Linux is free if your time is worth nothing". Wonder if that applies to free documentation? And yes you said $5-10, but I think you'll find quality documentation that would cover the (small) demographic Asterisk is aiming for would cost a bit more than that. Same with the others on the list. And lest you forget it takes more than a writer (even several) to produce good documentation.
Its (VoIP)not ready for prime time.
Imagine your business being dependent on independent data corridors which carry telco traffic globaly, not unlike our system of highways and in many ways analogous to these same highways controlled by individual states. Degregulation was great but not without cons. The old style monopolies had one advantage over the fragmented hodge podge of intra lata carriers we have today, centralized control of all high bandwidth trunking and localized or last mile loops.
What this means to you the customer is really simple, decentralized management by independent entities all vying for their own independent customer base have a tendency to oversubscribe their services resulting in a lack of adequate real time resources ala bandwidth. They continually oversell access and its the VoIP customer who is last in line due to the nature of packet switching and the existence of the traditional circuit switched services.
Yes these data highways are all interconnected but one experience is universal and a distributed phenomenom, bottlenecks aka traffic jams that are not centrally managed. What does this mean to you, simply, unintelligble phone calls from customers or customers who cant get through.
Bottom line is that your subjecting your business and its future to this jungle that is telecom. I have worked in the industry for almost 20 years and in that time have seen customer disatisfaction grow and mostly with VoIP.
The funny thing is that people have a high tolerance for a crappy sounding phone call until their level of activity reaches a point where they are spending too much time switcing carriers or logging complaints while pissing off their customer base.
With all of that time and aggravation, any savings realized from VoIP was lost in addition to the cost for blood pressure meds.
So bottom line, Circuit Switching, the premium grade telecom voice service, is here to stay and it will take a quantum leap in processing to increase bandwidth a significant factor over what it is today to allow VoIP to truly compete quality wise.
Until then, enjoy your jitter, echo, distortion and lost connectivity and dont call me, I am too busy supporting this frankenstein.