<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 TRANSITIONAL//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; CHARSET=UTF-8">
<META NAME="GENERATOR" CONTENT="GtkHTML/3.26.0">
</HEAD>
<BODY>
Using SER as an SBC poses a few problems, namely its inability to act as a B2BUA to sanitize headers and provide topology hiding. Anyone with a rudimentary knowledge of SIP can easily discern where all your network elements are and conduct targeted attacks if these services arent present in your border element. <BR>
<BR>
If you are dead set on building one out of open source, I would take a long hard look at SIPPY, as it will give you most of the features acme provides, though it wont do them out of the box. What it cannot do is provide you with a clean stateful fail-over model, anything close to the density offered by an Acme or the media handling capabilities. <BR>
<BR>
Good luck <BR>
<BR>
On Thu, 2009-10-01 at 11:00 -0500, Lee Riemer wrote:
<BLOCKQUOTE TYPE=CITE>
<PRE>
SER which is now OpenSER/Kamailio.
Jonathan Thurman wrote:
> Does anyone have a recommendation for a SBC solution based on open
> source software? I am looking to implement a small SBC, and there
> isn't much of a budget. If anyone has any specific experience one way
> or the other with the available solutions I would like to get your
> feedback. Thanks!
>
> -Jonathan
> _______________________________________________
> VoiceOps mailing list
> <A HREF="mailto:VoiceOps@voiceops.org">VoiceOps@voiceops.org</A>
> <A HREF="https://puck.nether.net/mailman/listinfo/voiceops">https://puck.nether.net/mailman/listinfo/voiceops</A>
>
_______________________________________________
VoiceOps mailing list
<A HREF="mailto:VoiceOps@voiceops.org">VoiceOps@voiceops.org</A>
<A HREF="https://puck.nether.net/mailman/listinfo/voiceops">https://puck.nether.net/mailman/listinfo/voiceops</A>
</PRE>
</BLOCKQUOTE>
</BODY>
</HTML>