VoIP Regulation, SIP Insurrection
Chris Holland writes "As voice communications are evolving beyond traditional phone systems and making better use of the Internet, Aswath Rao is offering regulation-advocating counterpoints to Dr. Daniel Ryan's original analysis of various VoIP industry players' arguments for deregulation. Many of the above discussions revolve around closed, regulatory-scrutiny-fostering voice communications ecosystems reserved to a small, resourceful elite. Meanwhile, an open Internet protocol which provides support for all forms of real-time communications including Text, Voice and Video, with a few open-sourced server implementations and free client solutions is starting to gain serious ground: The Session Initiation Protocol enables just about anybody with little resources to become their own Real-Time Communications Giant."
Yes, you can send and recieve faxes and dial-out via modem over VOiP.
I dial out over Vonage all the time, since the only access to most of the boxes I support is via dial-up. There are still plenty of computers that aren't on the 'net, especially where privacy/security is key.
I don't need no instructions to know how to rock!!!!
These guys are upgrading a $50 Linksys router with a full SIP server and SIP NAT. Add a wireless Wifi phone you have your own wireless PBX for the house including Wifi, QoS, a killer firewall, and tons more to boot.
And it's based on Linux and open source - whoopee!I don't know where you've gotten this "No 911 with VoIP" idea from.
I work for a telco/ISP/VoIP provider, and we've offer 911 services standard with all VoIP services. It's the same E911 service that cell carriers are providing.
And most major VoIP industry players offer it as a standard, or at least optional, feature.
Cell carriers are legally bound to provide E911 services (stage 1). VoIP carriers are not, but most serious providers do anyway, to have feature parity with the POTS market.
You misread, or posted the wrong link. What that page says is that you need to verify your address with Vonage, and based on that information they'll route your 911 calls to the answering center that covers your address. They do not send your address to the 911 answering center, and in fact your Vonage 911 call doesn't necessarily go to the same lines as POTS 911 calls do.
I believe Vonage is doing a trial of E911 in Rhode Island. E911 means full POTS 911 features, including supplying your address to the 911 center.
Unrelated:
E911 is also slowly being installed for the cellular network -- instead of an address, your phone receives GPS signals and passes those to the cell tower for computation of your position. I believe the towers also do some triangulation and signal-strength calculations to help determine position.
SIP was recently made to work behind NAT just fine thanks to STUN. read the article 'till the end. STUN was introduced in 2003, while SIP's been around for nearly a decade. I've even recently pushed the envelope to verify how well STUN works by making and receiving SIP calls from/to my earthlink SIP account behind 2 layers of NAT: 192.168.1.* network, linked to a 10.0.0.* network, linked to my earthlink (verizon) dsl.
Extraordinary Vacations. Exceptional Prices
Representatives from several VoIP companies will be discussing the future of open-source, regulation, and VoIP at SCALE 3x next month. Panelists will include Louie Mamakos, (Vonage), Jeff Bonforte (SIPphone), Al Brisard (PingTel), and Darryl Strauss (President - Digital Ordnance). In addition there will be talks about setting up your own VoIP systems with Asterisk.
i don't suppose anyone on /. will mention it, but Microsoft have adopted SIP in the latest Windows Messenger client.
.NET Messenger client, which is designed for public Internet use. Windows Messenger is designed to work with a Live Communication Server, integrated into Active Directory and Microsoft Exchange. If you have the whole Microsoft suite, it actually works really well...
p pro/maintain/wmsgrfaq.mspx
Note that this is *not* the same as the
More info here... http://www.microsoft.com/technet/prodtechnol/winx
We use this for corporate IM, voice and video conferencing, as well as remote desktop support (using the "remote assistance" feature) and also for desktop application sharing.