> Now I don't have any hardware background but will pick up what ever
> need.. so is there any doc or something I can start browsing through
> in my spare time.
A good place to start would be to learn a little about the sort of
microcontrollers we intend to use, for example PIC or Atmel ATMEGA.
Some devices are mentioned on previous posts. You could read about
them, or obtain a development board and/or samples.
> Also would like to know how can I help.. please let me know if I can
> be of assistance in anyway..
There are several areas that need some development for example:
1/ Audio I/O and handset interface
2/ DC-DC converter to generate ring and battery voltages.
3/ Asterisk channel driver
4/ Interface between microcontroller and router (e.g. RS232, Ethernet,
USB).
Feel free to work on any of these. I am working at a low level on (2)
using an ATmega development system.
Cheers,
David
>
> --
> Thanks
> Dp
> [The force is feminine in nature]
> >
--
Free Telephony Project
open embedded IP-PBX hardware and software
http://www.rowetel.com/ucasterisk
> A good place to start would be to learn a little about the sort of
> microcontrollers we intend to use, for example PIC or Atmel ATMEGA.
> Some devices are mentioned on previous posts. You could read about
> them, or obtain a development board and/or samples.
Has ayone looked inside the wi-fi routers/APs with built-in ATAs? The
cost differential between those with ATAs and those without seems
pretty small. Are the products integrated or are the FXS electronics a
daughter board or something? I live in a small town so I can't get one
locally to pop apart.
--john
Hi Dp,
> Now I don't have any hardware background but will pick up what ever
> need.. so is there any doc or something I can start browsing through
> in my spare time.
A good place to start would be to learn a little about the sort of
microcontrollers we intend to use, for example PIC or Atmel ATMEGA.
Some devices are mentioned on previous posts. You could read about
them, or obtain a development board and/or samples.
> Also would like to know how can I help.. please let me know if I can
> be of assistance in anyway..
There are several areas that need some development for example:
1/ Audio I/O and handset interface
2/ DC-DC converter to generate ring and battery voltages.
3/ Asterisk channel driver
4/ Interface between microcontroller and router ( e.g. RS232, Ethernet,
I haven't had a look inside any however I imagine that they have one of
the standard DSP chipset for the VOIP side plus something like a Silicon
Labs 3210 chipset for the FXS interface. It is also possible to do the
VOIP/DSP work on the host processor if it's just one or two channels.
- David
> Let's see if I can post here now, I was having problems before..
Coming thru loud and clear :-)
> Ok, I also want to help this project happen! I have some experience
> with microcontrollers, but not much. I am having problems to find a
> local suplier for an atmega16 development board. I would like to buy
> one to start testing it and be able to help the project.
You know you could probably just a buy a ATMega16 chip and wire up a
board yourself. I think all they need is a few parts to get them
started. My download cable is just a few wires from a parallel port,
and all the Linux tools I use are free.
BTW you can get PICs for free (see earlier posts on this group), mine
arrived in about 4 weeks to where I live in Australia.
> But importing one can be expencive, as the importation taxes here in
> Brazil are 60% of the total value of what you are buying. Anyway, I
> can see that you guys are more inclined at using an Atmega16
> controller, but have you guys allready decided? It seens to me that it
> is a good solution, as it is a very cheap chip.
I just chose the Atmega16 as Kiko built a similar project around this
family, and I could get a dev system easily. I also have some USB PICs
that I will try out some day. I am more interested in trying out
algorithms right now that finalising a chip selection. Once we get some
working algorithms porting between chips wont be too hard.
Thanks,
David