For sure I would use Kamailio as an SBC, but nevertheless I see these sortcoming in Kamailio (I don't know hov other SBCs handle this)
- config changes require a restart: most of the time this goes fast, but sometimes processes may fail to start (ports not freed by the OS, ...). Further, statefull cal handling/filtering will be interrupted by the restart.
- multiple 'virtual' SBCs. I may want to have multiple SBC instances on my SBC. If I want to separate them (optionally different config, or crashes should not crash other instances), then I need to start multiple Kamailio servers. Combined with plenty of workers per Kamailio and high private instance this may eat my servers memory.
- registration forwarding: If you have a registrar which does not support Path, and you can not change the behavior of the registrar, then usually you have to rewrite the Contact header in REGISTER requests and responses. There is no method in Kamailio to properly do this nice and transparently in all headers. There are plenty of functions to mangle with the contacts in many ways, but the logic is hard to implement.
And for paranoid security I would add a B2BUA.
regards Klaus
Am 27.02.2014 10:43, schrieb Carsten Bock:
Hi Luis,
i wouldn't be too sure of that:
- HMR can be done with Text-Ops
- all the SIP-Routing options can be done by routing-logic (e.g. by
Route-Header, by Time of day, by method, ...)
The only thing missing here, is maybe acting as a B2BUA and proper support for Session-Timers (which are end-to-end). But if you combine Kamailio with e.g. a SEMS-SBC, you won't miss a thing. One can even discuss, if a B2BUA and Session-Timers are a required feature for an SBC. If you go for the commercial "Big-Brother" of SEMS (Frafos ABC-SBC), you even get live-failovers without service-interruption as with an AcmePacket-SBC; together with a web-based frontend for administering your services.
The difficulty is, that you have to implement the routing logic for Kamailio youself instead of having a CLI or a Windows App for administering your SBC.
After working with AcmePacket, Kamailio and SEMS, i don't miss any feature of AcmePacket.
Just my $0.02, Carsten
2014-02-27 10:29 GMT+01:00 Luis Silva luisfilsilva@gmail.com:
Don't understand how is it possible to compare Kamailio with the Acme Packet SBC. Just to give an example, the DoS mechanism available on the AP SBC can't be compared with any other solution available on the market. You will also have HMRs, SIP Routing options out-of-the-box (like time of the day routing, sip method based, cost based, traffic classification based, lb, trunk group, enum,lrt, multistage, route header based, redirect, etc etc) and infinite number of features that you will for sure miss if you plan on making that replacement.
On Thu, Feb 27, 2014 at 8:54 AM, Olle E. Johansson oej@edvina.net wrote:
On 27 Feb 2014, at 07:29, Alex Balashov abalashov@evaristesys.com wrote:
No howto for that, and more than there is a howto for developing a messenger and selling it to Facebook for $20bn.
Damn. I can stop googling now then.
/O :-) _______________________________________________ SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list sr-users@lists.sip-router.org http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list sr-users@lists.sip-router.org http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users