![]() |
Creative VoIP Blaster Linux USB-Telephony Driver Development Homepage |
This device driver is a work in progress by Michael Bosland. Ultimately he would like to communicate with his brother Kris who only has one public IP address and can't use the software that comes with the hardware.
This site will have the source code for the driver as well as instructions on how to get it to work with your setup. That probably won't happen until I at least get the phone to ring and my voice recorded. As this is my first device driver I'm a bit shy...
The driver development that was represented here has pretty much stopped. My idea was to get a proof of concept driver going. I wanted to at least get the phone to ring!! Alas, it didn't happen. Some links follow that should help people find good stuff on the VoipBlaster. For Linux and other OSs.
| OS/Platform | Link | Description |
| FreeBSD/Windows | http://www.fobbit.com | This is the first working Open Source VoipBlaster driver that I've seen. This site describes the VoipBlaster and even has a discussion board. |
| Open H.323 | http://sourceforge.net/projects/voip-blaster/ | This is the sourceforge project where I sent most of my original files. It's main focus is to get the VoipBlaster to work with the Open H.323 project. This is also my main goal. |
| Linux | http://sourceforge.net/projects/voipblaster/ | This is the first sourceforge project setup to receive these files and take this project forward. |
| Date | Note |
|---|---|
|
Oct 14
|
I've uploaded the file's I've got to the sourceforge project: voip-blaster. Hopefully the project will be able to move along this way. I haven't been able to put enough time in to get things working. |
|
Jun 21st
|
As far as I can tell I'm using the USB system correctly, but it is not behaving as expected. Talking with folks on the mailing list it seems that hardly anyone has used the interrupt out communication method. I'm developing using an ohci driver which may behave differently than the uhci driver. My firewall has a uchi controller... |
|
Jun 15th
|
I'm back at it again. The company I'm consulting at is considering our proposal so I've some time to work on this again. I've upgraded to Linux 2.4.5 and am re-integrating my driver into the source tree. I'm still having a bit of trouble figuring out the USB layer. I'm trying to send a single shot synchronous interupt. Hopefully Linux 2.4.5 will solve all of my woes. :) |
|
Mid May
|
I'm trying to get the driver to talk with the USB layer. I'm having a bit of difficulty however... Don't have as much time to work on it as I've found gainful employment! |
|
April 30st
|
Picked up another box for the devbox. This one is a K2-266. It has 96MB of RAM. Found a $20 USB card at the local computer store... Loaded SuSE 7.1 with all of the development goodies... The other computer will become the firewall for ring.org. I have a /24 in "The Swamp" and will be multihoming as soon as I can afford another DSL. ASNs only cost $30/year from ARIN. There is a one time setup fee of $500 however... |
|
April 10st
|
Picked up several P133 computers w/ USB ports at Boeing Surplus. A pretty good deal at $70 each. Ooops one was DOA. It hard to find old Dell parts so it's probably for the best. This computer now has 64MB of RAM. |
|
April 7st
|
Actually tested the driver and actually called into the USB subsystem. The computer hung hard. Time to move the development environment... |
|
April 1st
|
ioctl() function initially defined. All that remains to be done before ringing the attached phone (at least in theory :) is URB creation and management and then submission of the URB to the USB subsystem for transmission to the device. Really. No joke... |
|
March 12th
|
Driver registers with the Linux Telephony sub system. Opening /dev/phone0 is routed through the Telephony sub system and processed by the driver. /dev/phone0 can be opened but closing doesn't work quite right. Will work on that later. |
|
March 3rd
|
Driver is integrated with the USB sub system. VoIP Blaster is detected and claimed. |
If you have any questions please send email to mike at ring.org