< Previous by Date Date Index Next by Date >
  Thread Index  

[reSIProcate] ReSiprocate versus SipXphone


More than one year ago I looked into implementing an embedded VOIP phone
using an ARM CPU running at 92MHz with a VxWorks OS.  At that time, I
selected the SipXphone software from Sipfoundry.org and ported it to
VxWorks.

At that time, I came to the conclusion that the SipXphone stack is not
usable for an embedded system for the following reasons:

- It's processing time is way too slow, because the implementation is not
efficient for an embedded system.
- It creates a process/task per call, which is definitely not a good thing
for an embedded phone which can allow up to 20 calls simultaneously.
- It contains numerous memory leaks which are hard to find/debug.
- It allocates memory in tiny chunks (e.g. as low as a few bytes), which
contributes to a high rate of memory fragmentation.

Can anyone tell me if the reSiprocate stack is more appropriate for an
embedded system and satisfies the deficiencies I have listed above?