Hello everyone,
Would an LPC2000 device be fast enough to act as a voip interface (i.e. ethernet
in one end, one channel of audio in/out at the other)?
All the VOIP software stacks I can find seem to based on Linux so I presume it
would have to run uclinux. It doesn't have much other work to do so can be
pretty much dedicated to this task.
If anybody has had any experiences in this area it would be interesting to hear
about it.
--
Tim Mitchell
voip phone using LPC2000
Started by ●May 14, 2010
Reply by ●May 14, 20102010-05-14
Hi Tim
Some of the LPC2XXX devices are quite powerful so this should not be a problem.
Although I never did it with an LPC2XXX I did voip with a 16 bit HC12. I think that the function was utilising about 40% of the processing power to handle the stream between an SPI based CODEC (interrupt based) and Ethernet so there was room for other activities alongside. The code was only about 20k in size so also various other features could be built in. It is however about 6 years since I worked on it so exact details are a bit vague.
Regards
Mark
http://www.uTasker.com
--- In l..., "Tim Mitchell" wrote:
>
> Hello everyone,
>
> Would an LPC2000 device be fast enough to act as a voip interface (i.e. ethernet in one end, one channel of audio in/out at the other)?
>
> All the VOIP software stacks I can find seem to based on Linux so I presume it would have to run uclinux. It doesn't have much other work to do so can be pretty much dedicated to this task.
> If anybody has had any experiences in this area it would be interesting to hear about it.
>
> --
> Tim Mitchell
>
Some of the LPC2XXX devices are quite powerful so this should not be a problem.
Although I never did it with an LPC2XXX I did voip with a 16 bit HC12. I think that the function was utilising about 40% of the processing power to handle the stream between an SPI based CODEC (interrupt based) and Ethernet so there was room for other activities alongside. The code was only about 20k in size so also various other features could be built in. It is however about 6 years since I worked on it so exact details are a bit vague.
Regards
Mark
http://www.uTasker.com
--- In l..., "Tim Mitchell" wrote:
>
> Hello everyone,
>
> Would an LPC2000 device be fast enough to act as a voip interface (i.e. ethernet in one end, one channel of audio in/out at the other)?
>
> All the VOIP software stacks I can find seem to based on Linux so I presume it would have to run uclinux. It doesn't have much other work to do so can be pretty much dedicated to this task.
> If anybody has had any experiences in this area it would be interesting to hear about it.
>
> --
> Tim Mitchell
>
Reply by ●May 14, 20102010-05-14
--- In l..., "Mark" wrote:
>
> Hi Tim
>
> Some of the LPC2XXX devices are quite powerful so this should not be a problem.
>
> Although I never did it with an LPC2XXX I did voip with a 16 bit HC12. I think that the function was utilising about 40% of the processing power to handle the stream between an SPI based CODEC (interrupt based) and Ethernet so there was room for other activities alongside. The code was only about 20k in size so also various other features could be built in. It is however about 6 years since I worked on it so exact details are a bit vague.
Is this a product or an experiment ?
If product, what was it ?
>
> Regards
>
> Mark
>
> http://www.uTasker.com
> --- In l..., "Tim Mitchell" wrote:
> >
> > Hello everyone,
> >
> > Would an LPC2000 device be fast enough to act as a voip interface (i.e. ethernet in one end, one channel of audio in/out at the other)?
> >
> > All the VOIP software stacks I can find seem to based on Linux so I presume it would have to run uclinux. It doesn't have much other work to do so can be pretty much dedicated to this task.
> >
> >
> > If anybody has had any experiences in this area it would be interesting to hear about it.
> >
> > --
> > Tim Mitchell
>
>
> Hi Tim
>
> Some of the LPC2XXX devices are quite powerful so this should not be a problem.
>
> Although I never did it with an LPC2XXX I did voip with a 16 bit HC12. I think that the function was utilising about 40% of the processing power to handle the stream between an SPI based CODEC (interrupt based) and Ethernet so there was room for other activities alongside. The code was only about 20k in size so also various other features could be built in. It is however about 6 years since I worked on it so exact details are a bit vague.
Is this a product or an experiment ?
If product, what was it ?
>
> Regards
>
> Mark
>
> http://www.uTasker.com
> --- In l..., "Tim Mitchell" wrote:
> >
> > Hello everyone,
> >
> > Would an LPC2000 device be fast enough to act as a voip interface (i.e. ethernet in one end, one channel of audio in/out at the other)?
> >
> > All the VOIP software stacks I can find seem to based on Linux so I presume it would have to run uclinux. It doesn't have much other work to do so can be pretty much dedicated to this task.
> >
> >
> > If anybody has had any experiences in this area it would be interesting to hear about it.
> >
> > --
> > Tim Mitchell
>
Reply by ●May 14, 20102010-05-14
Hi
I was something like this: http://www.kochag.ch/index.php?id4
It was operating over a power-line modem (simplifies installation in a lock of flats, for example) but I don't know whether it was that successful because power-line modems can still cause some difficulties.
Regards
Mark
--- In l..., "Donald H" wrote:
>
> --- In l..., "Mark" wrote:
> >
> > Hi Tim
> >
> > Some of the LPC2XXX devices are quite powerful so this should not be a problem.
> >
> > Although I never did it with an LPC2XXX I did voip with a 16 bit HC12. I think that the function was utilising about 40% of the processing power to handle the stream between an SPI based CODEC (interrupt based) and Ethernet so there was room for other activities alongside. The code was only about 20k in size so also various other features could be built in. It is however about 6 years since I worked on it so exact details are a bit vague.
>
> Is this a product or an experiment ?
>
> If product, what was it ?
>
> >
> > Regards
> >
> > Mark
> >
> > http://www.uTasker.com
> >
> >
> > --- In l..., "Tim Mitchell" wrote:
> > >
> > > Hello everyone,
> > >
> > > Would an LPC2000 device be fast enough to act as a voip interface (i.e. ethernet in one end, one channel of audio in/out at the other)?
> > >
> > > All the VOIP software stacks I can find seem to based on Linux so I presume it would have to run uclinux. It doesn't have much other work to do so can be pretty much dedicated to this task.
> > >
> > >
> > > If anybody has had any experiences in this area it would be interesting to hear about it.
> > >
> > > --
> > > Tim Mitchell
> > >
>
I was something like this: http://www.kochag.ch/index.php?id4
It was operating over a power-line modem (simplifies installation in a lock of flats, for example) but I don't know whether it was that successful because power-line modems can still cause some difficulties.
Regards
Mark
--- In l..., "Donald H" wrote:
>
> --- In l..., "Mark" wrote:
> >
> > Hi Tim
> >
> > Some of the LPC2XXX devices are quite powerful so this should not be a problem.
> >
> > Although I never did it with an LPC2XXX I did voip with a 16 bit HC12. I think that the function was utilising about 40% of the processing power to handle the stream between an SPI based CODEC (interrupt based) and Ethernet so there was room for other activities alongside. The code was only about 20k in size so also various other features could be built in. It is however about 6 years since I worked on it so exact details are a bit vague.
>
> Is this a product or an experiment ?
>
> If product, what was it ?
>
> >
> > Regards
> >
> > Mark
> >
> > http://www.uTasker.com
> >
> >
> > --- In l..., "Tim Mitchell" wrote:
> > >
> > > Hello everyone,
> > >
> > > Would an LPC2000 device be fast enough to act as a voip interface (i.e. ethernet in one end, one channel of audio in/out at the other)?
> > >
> > > All the VOIP software stacks I can find seem to based on Linux so I presume it would have to run uclinux. It doesn't have much other work to do so can be pretty much dedicated to this task.
> > >
> > >
> > > If anybody has had any experiences in this area it would be interesting to hear about it.
> > >
> > > --
> > > Tim Mitchell
> > >
>
Reply by ●May 14, 20102010-05-14
On Fri, May 14, 2010 at 9:09 PM, Tim Mitchell
wrote:
> All the VOIP software stacks I can find seem to based on Linux so
> I presume it would have to run uclinux. It doesn't have much other
> work to do so can be pretty much dedicated to this task.
>
No experiences here. But from SDCC mailing list I found this one
(Z80 based with a DSP) and it has BSD licensed Software API.
http://www.palmmicro.com/ar1688.html
http://aredfox.spaces.live.com/
--
Xiaofan http://mcuee.blogspot.com
> All the VOIP software stacks I can find seem to based on Linux so
> I presume it would have to run uclinux. It doesn't have much other
> work to do so can be pretty much dedicated to this task.
>
No experiences here. But from SDCC mailing list I found this one
(Z80 based with a DSP) and it has BSD licensed Software API.
http://www.palmmicro.com/ar1688.html
http://aredfox.spaces.live.com/
--
Xiaofan http://mcuee.blogspot.com
Reply by ●May 15, 20102010-05-15
Reply by ●May 17, 20102010-05-17
Quoting Andy B :
> It's been done with a lot less CPU:-
>
> http://www.uelectronics.info/homebrew-voip-server-pic
>
> - Andy
Andy,
That device is currently on the net. However, it also runs like it is small
CPU. Some pages load unreliably and slowly. It is nothing like LPC23xx on the
net. I would not sell that device as a finished product.
Tim,
I have not seen the code you found, but you can probably replace all OS and
network calls with other open source RTOS/stack api calls. Linux needs to much
resources. Lookup FreeRtos and uIP/lwIP.
Regards,
Michael Freeman
Principal Design Engineer
Update Systems, Inc.
> It's been done with a lot less CPU:-
>
> http://www.uelectronics.info/homebrew-voip-server-pic
>
> - Andy
Andy,
That device is currently on the net. However, it also runs like it is small
CPU. Some pages load unreliably and slowly. It is nothing like LPC23xx on the
net. I would not sell that device as a finished product.
Tim,
I have not seen the code you found, but you can probably replace all OS and
network calls with other open source RTOS/stack api calls. Linux needs to much
resources. Lookup FreeRtos and uIP/lwIP.
Regards,
Michael Freeman
Principal Design Engineer
Update Systems, Inc.
Reply by ●May 17, 20102010-05-17
