Domain: vovida.org
Stories and comments across the archive that link to vovida.org.
Comments · 22
-
Check out Vovida.org and VOCAL
Vovida.org is pretty comprehensive. Thier Vovida Open Communications Application Library (VOCAL) is pretty comprehensive, and works with many different vendor's phones, soft phones, and even Cisco's high-capacity PSTN gateways (H.323, MGCP, and SIP).
-
Re:NAT
Although there is no perfect solution I have found that STUN works quite well. It suffers most from the fact that there doesn't seem to be a standard for NAT implementation that is used by the vendors. I have used Vovida's free STUN Server and have only had some issues with LinkSys products. Unfortunately it is required to run on a public address. Vovida provides 2 public STUN Servers for people to use: The IP address of the STUN servers are: 128.107.250.38 128.107.250.39 I have not tried these and they may have changed. Maybe someone can give them a try and report back how well they work.
-
Re:CallManager *IS* being ported to Linux.There are already voice applications from Cisco that are running on Linux, take a look at the CUE (Unity Express) voice mail blade. It runs embedded Linux off a flash card and has a limited flash card life for voicemails (about 2 years). It's really a cool card. It's embeddable OS is managable by IOS on the router, and is configurable from within IOS. Sure beats the old Audix boxes that I still see running off 20Mb MFM and RLL hard drives on some old System V boxes made by AT&T.
Also, the Linux based SIP softswitch Vovida received significant dev time and resources from Cisco. They even had a contest for the ATA appliances to write the coolest Linux based voice applications. Cisco also has their own commercialized version of the Vovida softswitch, and a bulletproof carrier class SIP server that is meant to run in central offices or large enterprises. It supports Linux and Solaris.
-
Re:Does anyone actually do this?In fact, you are wrong. About 90% of PSTN traffic in Europe and North America these days is still over Common Channel Signalling System 7 (SS/7). This is a purely circuit switched system. The PSTN / POTS providers are still looking towards packet switched infrastructures for many of their advantages, but it isn't all there just yet.
Ericsson provides a good overview of signalling technologies for those who are curious.
Performance Technologies has an excellent overview of the popular VoIP technologies, although it appears slightly our of date.
For those who want to read more about SIP, there are many places to go, including: And items for the future of SIP are debated in other places: -
Re:Maybe I should RTFA, but...
Both SIP and XMPP are XML based.
There is an (apparently) open SIP implementation at www.vovida.org.
-
it's the next big thing ...
If you get the option to use some sort of standard like SIP for your
phone, you can set up your own software call distribution system where
some calls ring your phone, some go to voicemail, some get forwarded to
your mobile etc.
When I was at cisco, these sorts of services were the "bet the company
on it products of the future"
The funny thing is, some of the most interesting implementations of
this sort of thing are open source, one of which is vovidia which got bought by cisco
, but is still operating as an open source operation. The guy who
started has been aquired by cisco twice. -
it's the next big thing ...
If you get the option to use some sort of standard like SIP for your
phone, you can set up your own software call distribution system where
some calls ring your phone, some go to voicemail, some get forwarded to
your mobile etc.
When I was at cisco, these sorts of services were the "bet the company
on it products of the future"
The funny thing is, some of the most interesting implementations of
this sort of thing are open source, one of which is vovidia which got bought by cisco
, but is still operating as an open source operation. The guy who
started has been aquired by cisco twice. -
Re:WhoowhooVoIP on Linux? Swell idea. Let's put the technology to communicate via voice on a platform used by about 15 people
You are a complete fucktard.
-
open source VOIP is still not very well known !
Its amazing how open source voip is unknown. Unfortunately not many people know this even exists. What a shame !
-
more SIP phonesif you're looking for open source SIP softphones for Linux, here are two:
- Linphone (http://www.linphone.org/)
- SIPSet (http://www.vovida.org/)
-
Vonage doesn't let you tinker with the Cisco ATA
One thing I don't like about Vonage is that you have to use their Cisco ATA-186(the "POTS-to-Ethernet gizmo" you mentioned). Of course, they password protect it and provision it themselves, so it can only be used with their service. This means you don't get to play with this nifty device, 'cause they've locked you out. Goes against the hacker spirit, seems more like the Microsoft "we've set this up for you for your own protection" thing. I even emailed them to ask if I could use my own ATA, here is their response:
"We do not currently offer service on devices that we do not provide. We do include the Cisco ATA 186 free of charge. We do appreciate your interest in our service. Please do let us know if we may be of further assistance."
Why would you want to configure the Cisco ATA yourself? Well, you might want to try Free World Dialup, or you might want to play with VOCAL from vovida.org. Or whatever.
What I did was to buy a Cisco ATA-186 myself from YesMicro for about $170 with shipping. Then, I got an account at iconnecthere.com and set up my ATA using their setup instructions (it's a Word file, oh well...). I pick up the phone, and it works. When I make a call, they just charge me by the minute (2.9 cents to the U.S.). They have other plans that are cheaper, if you make a lot of calls. If you want to send and receive calls, you can do that for $8.95/month, or $10.95/month for a toll-free number (first hour is included, extra minutes at $0.10/minute). I don't, however, need my own phone number. So, here was my decision-making process, in a nutshell:
With Vonage, if I don't need my own phone number, too bad, no discount; I get a phone number anyway. I still can't tinker with the Cisco ATA, and I still need to give it back (it's not like I could do anything with it anyway, since it's locked down). $39.95 for unlimited calls to the U.S.
With iconnecthere, if I don't need my own phone number, then I don't pay the extra $8.95/month. However, I need to buy the Cisco ATA. Assuming a cost of $170, it would cost me $14.16/month to pay for it. Taking the cost of the Cisco into account, $39.95 buys me 1404 minutes/month, or about 47 minutes/day. Without the cost of the Cisco, it's 1767 minutes/month, or almost an hour/day.
However, I don't make a lot of calls every day. So, with iconnecthere, I can just pay by the minute. Assuming I make about 15 minutes of calls/day, that's $24.16/month including the cost of the Cisco as above, or $10/month not including the cost of the Cisco (with their 1000 minutes for $10 plan). Plus, I have the fun of being able to hack around on the Cisco ATA, and it's mine to keep.
So, in conclusion, if you don't want to hack around on your Cisco ATA, you don't mind giving it back, and you make over an hour's worth of calls every single day, go with Vonage. If you want to hack your Cisco ATA, own it, and make less than an hour's worth of calls a day, iconnecthere seems to be a better option. -
Seriously...
How many of these books can one own? I have plenty of books, but the mile-wide-but-foot-deep-overview books get old. I have Glass and Ables' "Unix for Programmers and Users" and Oreilly's "Running Linux". I reference there every so often (in fact just yesterday while installing VOCAL), but I'm not sure there is much more I could get out of a book that wasn't specifically about some library or application.
Most of the quick reference stuff anyone needs is on various websites and discussion boards. -
Extensively used in the SIP communityThere are quite a few different systems for telephony -- everything from traditional PSTN systems to VoIP protocols such as H.323 and SIP.
In the SIP community, Linux is used quite extensively. I just returned from an even called SIPIt which is the major interoperability event for SIP based telephony. There were around 50 vendors there -- everyone from big players like Cisco and Polycom to little startups. Many, many people there were using Linux for their products -- I would say at least 50%.
I also have worked with several SIP companies recently, Vovida, and open source SIP stack and suite of applications later aquired by Cisco, and Jasomi, a company that produces telephony boundary control products. These places used Linux extensively as the deployment platform, and there are real working deployments out there using these products.
So for SIP anyway, the answer is a resounding yes!
-
CHeck out VOCAL at www.vovida.orgVOCAL is a SIP based phone switch for handling VoIP calls. It works with Cisco 7960 phones and most of their VoIP POTS boxes (NM-HDV-1T1-24 on a 2620, or 5300 series with VoIP DSP's installed). I've used it and it is production ready. A recent test processed several million calls/hour if I remember correctly. seems pretty robust to me.
-
Other open source codecs
There is open source code for tons of the traditionally G.7xx CODECs around. The issues many of them require licensing various peoples patents. A casual look at speex would make me think that it is quite likely to infringe someone's CELP patents. Does anyone have any thoughts on this? It's really cool to see something like speex happening but there are a few other things that you might want to think about.
Global IP Sound put out a codec for voice called iLBC. It is specifically designed to avoid infringing known patents. It's sound quality vs. packet loss is very good for IP systems. This is being standardized by the IETF. All the source code is open source and in the draft which you can find at http://www.ietf.org/internet-drafts/draft-ietf-avt -ilbc-codec-00.txt.
Sun has a free implementation of CCITT compression types G.711, G.721 and G.723 at ftp://ftp.cwi.nl/pub/audio/ccitt-adpcm.tar.gz. This is just a free implementation - it does not give you a license to the patents.
Various people including Cisco have been working with the license holders of G.729 IPR to make it available for "pre-commercial" systems, developers, and education. http://www.vovida.org/applications/downloads/G729A / -
Open source IP PBX software
-
bump
I know I am just being critical, but this is a very corporate sponsored "open source" project. Look at the document control, the list of contributors, and the Cisco sponsorship. The people that made this are clearly being paid for their efforts, not that that's bad thing, but i think when people think "open source" they think more in the Eric Raymond/Cathedral and the Bizarre kind of way, not a typical corporate software project that happens to have a GPL license.
-Jon -
Vovida.org
Why wasn't a link to the project's actual webpage in the submission? Here it is.
-
So, what should I do now?H.323 and associated protocols for video conferencing and collaboration have been standardized for a while. They are kind of messy, but there were Windows implementations like NetMeeting, Linux implementations like Open H.323, and commercial implementations like CU-SeeMe (for Windows and Mac). These things could even talk to one another and to GnomeMeeting.
Fast forward to 2002. Microsoft still kind of ships Netmeeting with Windows XP Home, but there are no shortcuts, their documentation discourages you from using it (it also blue-screened my XP machine when I tried running it). Instead, they want you to use Microsoft Messenger, which only seems to want to talk through Microsoft's servers. Yahoo! give you video conferencing, but only through Yahoo! messenger and only on Windows. CU-SeeMe doesn't seem to exist anymore. In fact, I couldn't find any Windows or OSX H.323 implementations.
Instead, now the next thing seems to be SIP (Session Initiation Protocol, which is curiously what Vovida is based on. Well, it's kind of like HTTP, and that's nice compared to H.323's ASN protocols. MSN Messenger seems to be using it. There is Linphone, which is SIP based and works on Linux.
But... how do we do cross platform video conferencing now? Microsoft Messenger may speak SIP, but as far as I can tell, it doesn't let me do machine to machine calls. Even if it did, GnomeMeeting doesn't seem to support SIP (yet?) and Linphone doesn't do video. And MacOSX, as far as I can tell, is almost completely out in the cold; at least, I couldn't find any commercial video conferencing software for it. The closest is the OpenH.323 sample applications, running under X11 on MacOSX. That's not exactly what you can ask average Mac users to use.
So, if I want to do cross-platform video conferencing between Linux, Windows, and/or Macintosh, what software and protocols should I use?
-
Open Source VoIP
If you want to implement a VoIP system, there is a bunch of open source software at www.vovida.org that was put there to help make things like this happen.
<blatant ad>
There is SIP proxies and registrars, B2BUA for prepaid billing, MGCP to SIP translators, H.323 to SIP translators, voice mail system, SIP, RTSP, OSP, COPS, TRIP, RTP, RADIUS and MGCP stacks, and much more. It has been tested with phones and gateways from almost all major vendors and most of the smaller SIP vendors. It can be set up in with no single point of failure and has been tested up too 500 calls per seconds (that's a lot per day - you do the math)
</blatant ad>
There is also some good infromation at www.iptel.org
-
Re:not so sure about that...
"rtsp://" protocol, something only realnetworks software can understand
Wrong. RTSP is an open protocol. You can read RFC2326 here. Multiple implementations already exist, including an open-source one. -
Marketing troll?
This linksys/net2phone SIP-in-a-box product was just announced yesterday. What great timing to get it published on
/. :-) They haven't even updated their websites yet.
A slightly different version of this service was discussed recently on /.
We've been playing around with a SIP gateway server and a VoIP phone on our DSL connection here in Europe. It works, but phone quality to the US sucks at best. The problem is QoS. Without spending US$10,000++ per month on a dedicated IP pipe from Europe to the US with a guaranteed QoS end-to-end, VoIP just doesn't replace regular phone service. But for IP connections within Europe, we get reasonable quality. Now, if only there were more than 3 people who could call us (and two of those are inside cisco TAC who only call to test their SIP setups)
This linksys/net2phone service requires you to pay them a subscription to use their SIP gateway, and the units probably are not configurable to use alternate SIP services. So if your account expires, your box becomes an expensive blinking light source.
It should work in Europe, I doubt they care which IP block you are coming from. But all the sessions will pass to north america for processing on their VoIP network. If you do buy one of these boxes, drop me a note. I'd love to see what kind of "virtual phone number" they assign you.
the AC