Hi,
I would like to have some suggestions about a full replacement of an ACME Packet Net-Net Session Border Controller. By now, ACME SBC performs all the SBC functionalities, mainly:
- it is used as a SIP endpoint for SIP client registrations - it is used as a SIP endpoint for interconnection to multiple SIP carriers via SIP trunks - it is used for NAT traversal
In this deployment, the SIP Server communicates only with the SBC and this one takes care of the communication between the SIP Server and the external SIP entities (UA clients, SIP Trunks). In this scenario, can I consider to replace the SBC with Kamailio?
Hi Francesco,
i would recommend, you look at the SEMS-project and it's SBC module.
From the functionality perspective, i don't think you'll miss anything
compared to Acme Packet, latest trunk version even has a Registration cache, which works absolutely great...
Kind regards, Carsten
2014-02-20 17:04 GMT+01:00 Francesco Maria Magnini fmm1982@gmail.com:
Hi,
I would like to have some suggestions about a full replacement of an ACME Packet Net-Net Session Border Controller. By now, ACME SBC performs all the SBC functionalities, mainly:
- it is used as a SIP endpoint for SIP client registrations
- it is used as a SIP endpoint for interconnection to multiple SIP carriers via SIP trunks
- it is used for NAT traversal
In this deployment, the SIP Server communicates only with the SBC and this one takes care of the communication between the SIP Server and the external SIP entities (UA clients, SIP Trunks). In this scenario, can I consider to replace the SBC with Kamailio?
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
looking at this, is there some howto for setting up high-availability, LCR and route-by-route transcoding?
Melanie
On 2/20/14 7:12 PM, Carsten Bock wrote:
Hi Francesco,
i would recommend, you look at the SEMS-project and it's SBC module.
From the functionality perspective, i don't think you'll miss anything
compared to Acme Packet, latest trunk version even has a Registration cache, which works absolutely great...
Kind regards, Carsten
2014-02-20 17:04 GMT+01:00 Francesco Maria Magnini fmm1982@gmail.com:
Hi,
I would like to have some suggestions about a full replacement of an ACME Packet Net-Net Session Border Controller. By now, ACME SBC performs all the SBC functionalities, mainly:
- it is used as a SIP endpoint for SIP client registrations
- it is used as a SIP endpoint for interconnection to multiple SIP carriers via SIP trunks
- it is used for NAT traversal
In this deployment, the SIP Server communicates only with the SBC and this one takes care of the communication between the SIP Server and the external SIP entities (UA clients, SIP Trunks). In this scenario, can I consider to replace the SBC with Kamailio?
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
LCR has complex business rules and usually requires at least some third party integration or development. No howto for that, and more than there is a howto for developing a messenger and selling it to Facebook for $20bn.
Melanie Pietersen melanie.pietersen.ml@gmail.com wrote:
looking at this, is there some howto for setting up high-availability, LCR and route-by-route transcoding?
Melanie
On 2/20/14 7:12 PM, Carsten Bock wrote:
Hi Francesco,
i would recommend, you look at the SEMS-project and it's SBC module.
From the functionality perspective, i don't think you'll miss
anything
compared to Acme Packet, latest trunk version even has a Registration cache, which works absolutely great...
Kind regards, Carsten
2014-02-20 17:04 GMT+01:00 Francesco Maria Magnini
Hi,
I would like to have some suggestions about a full replacement of an
ACME Packet Net-Net Session Border Controller.
By now, ACME SBC performs all the SBC functionalities, mainly:
- it is used as a SIP endpoint for SIP client registrations
- it is used as a SIP endpoint for interconnection to multiple SIP
carriers via SIP trunks
- it is used for NAT traversal
In this deployment, the SIP Server communicates only with the SBC
and this one takes care of the communication between the SIP Server and the external SIP entities (UA clients, SIP Trunks).
In this scenario, can I consider to replace the SBC with Kamailio?
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
-- Sent from my mobile, and thus lacking in the refinement one might expect from a fully fledged keyboard.
Alex Balashov - Principal Evariste Systems LLC 235 E Ponce de Leon Ave Suite 106 Decatur, GA 30030 United States Tel: +1-678-954-0671 Web: http://www.evaristesys.com/, http://www.alexbalashov.com
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 :-)
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
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
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
On 2/27/14 10:29 AM, Luis Silva wrote:
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.
Hi Luis,
the acme product seems actually underperforming compared to Wladimir's SBC demo and measured by the technical capabilities I am interested in.
What continues to confuse me is the apparent mixture of technical and marketing terms. The infinite number is respectably long but it includes many features I will not need like H.323 or appear to be marketing. For example it appears that ABC demo can route by any SIP message element, which is clearly superior and necessary, especially in a deployment with proprietary header fields. Even if it does not make such a long element-by-element feature list :). Similarly it includes several types of traffic shaping, which seems little different from the DoS protection offered by former Acme. Acme's multistage lookup you mentioned seems to be just a fix to quite imperfect design which didn't anticipate cascaded routing logic. I mean I am a little bit careful about assessing technological supremacy based on marketing material.
Is there possibly some truly technical-based comparison? I tried to look it up in the archive but did not find some.
Melanie
Hi Melanie,
Now I'm curious about which tests are you mentioning. Also, Acme Packet/Oracle as many different SBCs models, which can be selected according with the customer's requirements. When talking about the infinite number of features I wasn't really thinking in H.323. Although, probably there were customers like you a couple of years ago that thought they wouldn't need some features and regret they didn't pick Acme Packet, after they received new requirements on their networks. Acme SBC can also route using any SIP message element. Just use an HMR and according with what you want, just add a Route header (as simple as that... :) ). Regarding traffic shaping, you can also do it based on media-profiles. Comparing traffic shaping with Acme Packet DoS protection doesn't make much sense. Their DoS is one of the features that made their SBC what it is now, the leader worldwide. And do you know what it means? It is tested against any tool out there performing attacks (more customers means more testing). Can you say the same about the ABC demo? One additional thing is that you can for sure say that when deploying a Acme Packet SBC you won't have issues interoperate with other vendors. This is not marketing material, again this is based on the number of customers/deployments that exists worldwide. Not to mention real HA (out-of-the-box), simple configuration (yeah, I've already implemented an P-CSCF using Kamailio and it was a mess...), transcoding, LI, etc.
Hope it helps, Luis
On Thu, Feb 27, 2014 at 5:33 PM, Melanie Pietersen < melanie.pietersen.ml@gmail.com> wrote:
On 2/27/14 10:29 AM, Luis Silva wrote:
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.
Hi Luis,
the acme product seems actually underperforming compared to Wladimir's SBC demo and measured by the technical capabilities I am interested in.
What continues to confuse me is the apparent mixture of technical and marketing terms. The infinite number is respectably long but it includes many features I will not need like H.323 or appear to be marketing. For example it appears that ABC demo can route by any SIP message element, which is clearly superior and necessary, especially in a deployment with proprietary header fields. Even if it does not make such a long element-by-element feature list :). Similarly it includes several types of traffic shaping, which seems little different from the DoS protection offered by former Acme. Acme's multistage lookup you mentioned seems to be just a fix to quite imperfect design which didn't anticipate cascaded routing logic. I mean I am a little bit careful about assessing technological supremacy based on marketing material.
Is there possibly some truly technical-based comparison? I tried to look it up in the archive but did not find some.
Melanie
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
I'm curious re. your statement about P-CSCF. What does LI and transcoding have to do with Kamailio? As already mentioned these functions are available only in B2BUA which Kamailio is *not*. What other issues then did you have with P-CSCF impl. using Kamailio. Also, how did P-CSCF even get into this thread?
<sarcasm>BTW, you forgot to mention the awesome price of Acme in your comparison to other alternatives</sarcasm> ;)
On Fri, Feb 28, 2014 at 11:21 AM, Luis Silva luisfilsilva@gmail.com wrote:
Hi Melanie,
Now I'm curious about which tests are you mentioning. Also, Acme Packet/Oracle as many different SBCs models, which can be selected according with the customer's requirements. When talking about the infinite number of features I wasn't really thinking in H.323. Although, probably there were customers like you a couple of years ago that thought they wouldn't need some features and regret they didn't pick Acme Packet, after they received new requirements on their networks. Acme SBC can also route using any SIP message element. Just use an HMR and according with what you want, just add a Route header (as simple as that... :) ). Regarding traffic shaping, you can also do it based on media-profiles. Comparing traffic shaping with Acme Packet DoS protection doesn't make much sense. Their DoS is one of the features that made their SBC what it is now, the leader worldwide. And do you know what it means? It is tested against any tool out there performing attacks (more customers means more testing). Can you say the same about the ABC demo? One additional thing is that you can for sure say that when deploying a Acme Packet SBC you won't have issues interoperate with other vendors. This is not marketing material, again this is based on the number of customers/deployments that exists worldwide. Not to mention real HA (out-of-the-box), simple configuration (yeah, I've already implemented an P-CSCF using Kamailio and it was a mess...), transcoding, LI, etc.
Hope it helps, Luis
On Thu, Feb 27, 2014 at 5:33 PM, Melanie Pietersen < melanie.pietersen.ml@gmail.com> wrote:
On 2/27/14 10:29 AM, Luis Silva wrote:
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.
Hi Luis,
the acme product seems actually underperforming compared to Wladimir's SBC demo and measured by the technical capabilities I am interested in.
What continues to confuse me is the apparent mixture of technical and marketing terms. The infinite number is respectably long but it includes many features I will not need like H.323 or appear to be marketing. For example it appears that ABC demo can route by any SIP message element, which is clearly superior and necessary, especially in a deployment with proprietary header fields. Even if it does not make such a long element-by-element feature list :). Similarly it includes several types of traffic shaping, which seems little different from the DoS protection offered by former Acme. Acme's multistage lookup you mentioned seems to be just a fix to quite imperfect design which didn't anticipate cascaded routing logic. I mean I am a little bit careful about assessing technological supremacy based on marketing material.
Is there possibly some truly technical-based comparison? I tried to look it up in the archive but did not find some.
Melanie
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
Hello,
I'm not going to comment on the relative merits of commercial products like Net-Net SBC and ABC SBC, as this is an open source focused list (we may continue this on kamailio-business if interested; of course I'd also have a few things to say e.g. regarding HA, DOS or interop, and we are more than happy to take into account any suggestion on how to improve the product).
But relevant to the open source community is that we (FRAFOS) are building the ABC SBC on top of the open source SEMS SBC software, thus a remarkable part of the tech lands finally in the open source version, for example off the top of my head in the last months: - registration caching, reg throttling - multipe routing target options, DNS SRV improvements, failover, blacklisting etc - many multi interfaces/bridging/if force options - RTP rate limits - hold handling options - tcp transport - extended call control interface supporting switch/pbx style call flows, with DSM scripting - lots of performance improvements and tuning options
Granted, all this is only in git master, the 1.6 release has unfortunately no yet materialized and some know-how, time and custom development is necessary to use all of that. But still it's free and open source: take it, use it, look at the source, modify it, build on it.
Enough ad of a different open source project (I hope this is OK though, remembering that SEMS and SER have the same origins)...
Best Regards Stefan
o Luis Silva on 02/28/2014 10:21 AM:
Hi Melanie,
Now I'm curious about which tests are you mentioning. Also, Acme Packet/Oracle as many different SBCs models, which can be selected according with the customer's requirements. When talking about the infinite number of features I wasn't really thinking in H.323. Although, probably there were customers like you a couple of years ago that thought they wouldn't need some features and regret they didn't pick Acme Packet, after they received new requirements on their networks. Acme SBC can also route using any SIP message element. Just use an HMR and according with what you want, just add a Route header (as simple as that... :) ). Regarding traffic shaping, you can also do it based on media-profiles. Comparing traffic shaping with Acme Packet DoS protection doesn't make much sense. Their DoS is one of the features that made their SBC what it is now, the leader worldwide. And do you know what it means? It is tested against any tool out there performing attacks (more customers means more testing). Can you say the same about the ABC demo? One additional thing is that you can for sure say that when deploying a Acme Packet SBC you won't have issues interoperate with other vendors. This is not marketing material, again this is based on the number of customers/deployments that exists worldwide. Not to mention real HA (out-of-the-box), simple configuration (yeah, I've already implemented an P-CSCF using Kamailio and it was a mess...), transcoding, LI, etc.
Hope it helps, Luis
On Thu, Feb 27, 2014 at 5:33 PM, Melanie Pietersen <melanie.pietersen.ml@gmail.com mailto:melanie.pietersen.ml@gmail.com> wrote:
On 2/27/14 10:29 AM, Luis Silva wrote: 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. Hi Luis, the acme product seems actually underperforming compared to Wladimir's SBC demo and measured by the technical capabilities I am interested in. What continues to confuse me is the apparent mixture of technical and marketing terms. The infinite number is respectably long but it includes many features I will not need like H.323 or appear to be marketing. For example it appears that ABC demo can route by any SIP message element, which is clearly superior and necessary, especially in a deployment with proprietary header fields. Even if it does not make such a long element-by-element feature list :). Similarly it includes several types of traffic shaping, which seems little different from the DoS protection offered by former Acme. Acme's multistage lookup you mentioned seems to be just a fix to quite imperfect design which didn't anticipate cascaded routing logic. I mean I am a little bit careful about assessing technological supremacy based on marketing material. Is there possibly some truly technical-based comparison? I tried to look it up in the archive but did not find some. Melanie _________________________________________________ SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list sr-users@lists.sip-router.org <mailto:sr-users@lists.sip-router.org> http://lists.sip-router.org/__cgi-bin/mailman/listinfo/sr-__users <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
Hi,
As the maintainers of SEMS we fully agree with Carsten and Alex: the SBC module of SEMS is a good replacement of a typical SBC. If one also is looking for ease of usage, support, high availability and a powerful GUI then the answer is the ABC SBC which is based on SEMS and the SBC module. A free trial is provided under http://www.frafos.com/free-trial/
The ABC SBC also enables easy configuration of LCR using provisioned tables and comes in an active-strandby configuration that enables failover without call interruption. Transcoding can be supported in software as well.
Best Regards, -Vladimir
On 27.2.2014 07:24, Melanie Pietersen wrote:
looking at this, is there some howto for setting up high-availability, LCR and route-by-route transcoding?
Melanie
On 2/20/14 7:12 PM, Carsten Bock wrote:
Hi Francesco,
i would recommend, you look at the SEMS-project and it's SBC module.
From the functionality perspective, i don't think you'll miss anything
compared to Acme Packet, latest trunk version even has a Registration cache, which works absolutely great...
Kind regards, Carsten
2014-02-20 17:04 GMT+01:00 Francesco Maria Magnini fmm1982@gmail.com:
Hi,
I would like to have some suggestions about a full replacement of an ACME Packet Net-Net Session Border Controller. By now, ACME SBC performs all the SBC functionalities, mainly:
- it is used as a SIP endpoint for SIP client registrations
- it is used as a SIP endpoint for interconnection to multiple SIP
carriers via SIP trunks
- it is used for NAT traversal
In this deployment, the SIP Server communicates only with the SBC and this one takes care of the communication between the SIP Server and the external SIP entities (UA clients, SIP Trunks). In this scenario, can I consider to replace the SBC with Kamailio?
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
Vladimir-
Transcoding can be supported in software as well.
Not at high capacity, like 20,000+ AMR-WB calls in a 1U server. My experience has been that high volume users of SBC products are SWaP constrained -- especially limited space and power consumption. Their end customers do not allow a stacks of servers for voice/video transcoding, speech recognition, etc.
-Jeff
As the maintainers of SEMS we fully agree with Carsten and Alex: the SBC module of SEMS is a good replacement of a typical SBC. If one also is looking for ease of usage, support, high availability and a powerful GUI then the answer is the ABC SBC which is based on SEMS and the SBC module. A free trial is provided under http://www.frafos.com/free-trial/
The ABC SBC also enables easy configuration of LCR using provisioned tables and comes in an active-strandby configuration that enables failover without call interruption. Transcoding can be supported in software as well.
Best Regards, -Vladimir
On 27.2.2014 07:24, Melanie Pietersen wrote:
looking at this, is there some howto for setting up high-availability, LCR and route-by-route transcoding?
Melanie
On 2/20/14 7:12 PM, Carsten Bock wrote:
Hi Francesco,
i would recommend, you look at the SEMS-project and it's SBC module.
From the functionality perspective, i don't think you'll miss anything
compared to Acme Packet, latest trunk version even has a Registration cache, which works absolutely great...
Kind regards, Carsten
2014-02-20 17:04 GMT+01:00 Francesco Maria Magnini fmm1982@gmail.com:
Hi,
I would like to have some suggestions about a full replacement of an ACME Packet Net-Net Session Border Controller. By now, ACME SBC performs all the SBC functionalities, mainly:
- it is used as a SIP endpoint for SIP client registrations
- it is used as a SIP endpoint for interconnection to multiple SIP
carriers via SIP trunks
- it is used for NAT traversal
In this deployment, the SIP Server communicates only with the SBC and this one takes care of the communication between the SIP Server and the external SIP entities (UA clients, SIP Trunks). In this scenario, can I consider to replace the SBC with Kamailio?
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
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
Francesco,
Have a look at this blog post:
http://www.likewise.am/2013/03/kamailio-as-an-sbc-session-border-controller/
That said, I agree with Carsten's suggestion of SEMS.
On 02/20/2014 11:04 AM, Francesco Maria Magnini wrote:
Hi,
I would like to have some suggestions about a full replacement of an ACME Packet Net-Net Session Border Controller. By now, ACME SBC performs all the SBC functionalities, mainly:
- it is used as a SIP endpoint for SIP client registrations
- it is used as a SIP endpoint for interconnection to multiple SIP carriers via SIP trunks
- it is used for NAT traversal
In this deployment, the SIP Server communicates only with the SBC and this one takes care of the communication between the SIP Server and the external SIP entities (UA clients, SIP Trunks). In this scenario, can I consider to replace the SBC with Kamailio?
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
Alex's article is one of my favorites. That being said, we switched out an Acme SBC for openser (at the time) and was immediately thrilled.
Fred Posner The Palner Group, Inc. 503-914-0999 (direct) 954-472-2896 (fax)
On 02/20/2014 01:14 PM, Alex Balashov wrote:
Francesco,
Have a look at this blog post:
http://www.likewise.am/2013/03/kamailio-as-an-sbc-session-border-controller/
That said, I agree with Carsten's suggestion of SEMS.
On 02/20/2014 11:04 AM, Francesco Maria Magnini wrote:
Hi,
I would like to have some suggestions about a full replacement of an ACME Packet Net-Net Session Border Controller. By now, ACME SBC performs all the SBC functionalities, mainly:
- it is used as a SIP endpoint for SIP client registrations
- it is used as a SIP endpoint for interconnection to multiple SIP
carriers via SIP trunks
- it is used for NAT traversal
In this deployment, the SIP Server communicates only with the SBC and this one takes care of the communication between the SIP Server and the external SIP entities (UA clients, SIP Trunks). In this scenario, can I consider to replace the SBC with Kamailio?
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
@Carsten I looked at http://www.iptel.org/sems and seems to be only broken links to downloads. Do you know if the project is still maintained?
@Fred Are you using openser as a B2BUA?
Il giorno 20/feb/2014, alle ore 19:42, Fred Posner fred@palner.com ha scritto:
Alex's article is one of my favorites. That being said, we switched out an Acme SBC for openser (at the time) and was immediately thrilled.
Fred Posner The Palner Group, Inc. 503-914-0999 (direct) 954-472-2896 (fax)
On 02/20/2014 01:14 PM, Alex Balashov wrote:
Francesco,
Have a look at this blog post:
http://www.likewise.am/2013/03/kamailio-as-an-sbc-session-border-controller/
That said, I agree with Carsten's suggestion of SEMS.
On 02/20/2014 11:04 AM, Francesco Maria Magnini wrote:
Hi,
I would like to have some suggestions about a full replacement of an ACME Packet Net-Net Session Border Controller. By now, ACME SBC performs all the SBC functionalities, mainly:
- it is used as a SIP endpoint for SIP client registrations
- it is used as a SIP endpoint for interconnection to multiple SIP
carriers via SIP trunks
- it is used for NAT traversal
In this deployment, the SIP Server communicates only with the SBC and this one takes care of the communication between the SIP Server and the external SIP entities (UA clients, SIP Trunks). In this scenario, can I consider to replace the SBC with Kamailio?
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
You don't need B2B functionality to provide SBC functionality. SBC is a loose term these days. All you need is properly crafted signaling to achieve you requirements. Using a SIP proxy server as an SBC is pretty common these days.
Regards Ovidiu Sas On Feb 20, 2014 5:55 PM, "Francesco Maria Magnini" fmm1982@gmail.com wrote:
@Carsten I looked at http://www.iptel.org/sems and seems to be only broken links to downloads. Do you know if the project is still maintained?
@Fred Are you using openser as a B2BUA?
Il giorno 20/feb/2014, alle ore 19:42, Fred Posner fred@palner.com ha scritto:
Alex's article is one of my favorites. That being said, we switched out
an Acme SBC for openser (at the time) and was immediately thrilled.
Fred Posner The Palner Group, Inc. 503-914-0999 (direct) 954-472-2896 (fax)
On 02/20/2014 01:14 PM, Alex Balashov wrote:
Francesco,
Have a look at this blog post:
http://www.likewise.am/2013/03/kamailio-as-an-sbc-session-border-controller/
That said, I agree with Carsten's suggestion of SEMS.
On 02/20/2014 11:04 AM, Francesco Maria Magnini wrote:
Hi,
I would like to have some suggestions about a full replacement of an ACME Packet Net-Net Session Border Controller. By now, ACME SBC performs all the SBC functionalities, mainly:
- it is used as a SIP endpoint for SIP client registrations
- it is used as a SIP endpoint for interconnection to multiple SIP
carriers via SIP trunks
- it is used for NAT traversal
In this deployment, the SIP Server communicates only with the SBC and this one takes care of the communication between the SIP Server and the external SIP entities (UA clients, SIP Trunks). In this scenario, can I consider to replace the SBC with Kamailio?
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
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
On 2/20/14, 5:55 PM, Francesco Maria Magnini wrote:
@Carsten I looked at http://www.iptel.org/sems and seems to be only broken links to downloads. Do you know if the project is still maintained?
@Fred Are you using openser as a B2BUA?
No, because of course Kamailio is not a b2bua. =)
In the case of the ACME replacement, we used it to:
- handle NAT (rtpproxy) - user regs - load balance - lcr - security - routing
and some other little hacks.
Fred,
in you ACME replacement, kamailio doesn’t rewrite headers for handling RTP/SIGNALING and stay in the middle?
Il giorno 21/feb/2014, alle ore 00:03, Fred Posner fred@palner.com ha scritto:
On 2/20/14, 5:55 PM, Francesco Maria Magnini wrote:
@Carsten I looked at http://www.iptel.org/sems and seems to be only broken links to downloads. Do you know if the project is still maintained?
@Fred Are you using openser as a B2BUA?
No, because of course Kamailio is not a b2bua. =)
In the case of the ACME replacement, we used it to:
- handle NAT (rtpproxy)
- user regs
- load balance
- lcr
- security
- routing
and some other little hacks.
-- Fred Posner | The Palner Group, Inc. http://qxork.com
Il giorno 20/feb/2014, alle ore 19:42, Fred Posner fred@palner.com ha scritto:
Alex's article is one of my favorites. That being said, we switched out an Acme SBC for openser (at the time) and was immediately thrilled.
Fred Posner The Palner Group, Inc. 503-914-0999 (direct) 954-472-2896 (fax)
On 02/20/2014 01:14 PM, Alex Balashov wrote:
Francesco,
Have a look at this blog post:
http://www.likewise.am/2013/03/kamailio-as-an-sbc-session-border-controller/
That said, I agree with Carsten's suggestion of SEMS.
On 02/20/2014 11:04 AM, Francesco Maria Magnini wrote:
Hi,
I would like to have some suggestions about a full replacement of an ACME Packet Net-Net Session Border Controller. By now, ACME SBC performs all the SBC functionalities, mainly:
- it is used as a SIP endpoint for SIP client registrations
- it is used as a SIP endpoint for interconnection to multiple SIP
carriers via SIP trunks
- it is used for NAT traversal
In this deployment, the SIP Server communicates only with the SBC and this one takes care of the communication between the SIP Server and the external SIP entities (UA clients, SIP Trunks). In this scenario, can I consider to replace the SBC with Kamailio?
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
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
On 2/20/14, 6:25 PM, Francesco Maria Magnini wrote:
Fred,
in you ACME replacement, kamailio doesn’t rewrite headers for handling RTP/SIGNALING and stay in the middle?
For nat it did. For others the media server did.
You can easily force all connections to use rtpproxy to do what you ask. We chose to do this for NAT and for media servers outside of kamailio to be the other choice. All calls were on one, the other, or both.
Hi Francesco,
Yes, SEMS is well maintained (i don't know, how well the website is maintained).
You find the souce-code here: http://git.sip-router.org/cgi-bin/gitweb.cgi?p=sems;a=summary
Kind regards, Carsten Am 20.02.2014 23:55 schrieb "Francesco Maria Magnini" fmm1982@gmail.com:
@Carsten I looked at http://www.iptel.org/sems and seems to be only broken links to downloads. Do you know if the project is still maintained?
@Fred Are you using openser as a B2BUA?
Il giorno 20/feb/2014, alle ore 19:42, Fred Posner fred@palner.com ha scritto:
Alex's article is one of my favorites. That being said, we switched out
an Acme SBC for openser (at the time) and was immediately thrilled.
Fred Posner The Palner Group, Inc. 503-914-0999 (direct) 954-472-2896 (fax)
On 02/20/2014 01:14 PM, Alex Balashov wrote:
Francesco,
Have a look at this blog post:
http://www.likewise.am/2013/03/kamailio-as-an-sbc-session-border-controller/
That said, I agree with Carsten's suggestion of SEMS.
On 02/20/2014 11:04 AM, Francesco Maria Magnini wrote:
Hi,
I would like to have some suggestions about a full replacement of an ACME Packet Net-Net Session Border Controller. By now, ACME SBC performs all the SBC functionalities, mainly:
- it is used as a SIP endpoint for SIP client registrations
- it is used as a SIP endpoint for interconnection to multiple SIP
carriers via SIP trunks
- it is used for NAT traversal
In this deployment, the SIP Server communicates only with the SBC and this one takes care of the communication between the SIP Server and the external SIP entities (UA clients, SIP Trunks). In this scenario, can I consider to replace the SBC with Kamailio?
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
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
Hi Francesco,
o Carsten Bock on 02/21/2014 12:05 AM:
Hi Francesco,
Yes, SEMS is well maintained (i don't know, how well the website is maintained).
You find the souce-code here: http://git.sip-router.org/cgi-bin/gitweb.cgi?p=sems;a=summary
Carsten is right that SEMS is maintained, but it's website not really well (the ftp server is down, thanks for letting us know, will be up soon)...
To start with SEMS sbc, have a look at the sbc module documentation: http://git.sip-router.org/cgi-bin/gitweb.cgi?p=sems;a=blob;f=doc/Readme.sbc....
You'll need to define some regex mappings to have the calls and other messages from different origins (e.g. different received interfaces, then from different remote IPs/trunks) processed with the right SBC profiles. Then in the profiles you define what should happen with that calls and where they are sent. For registrations / calls to registrations use the enable_reg_caching option; for NAT handling use dlg_nat_handling=yes, enable_rtprelay=yes, rtprelay_force_symmetric_rtp=yes, and set the interfaces used for RTP in rtprelay_interface/aleg_rtprelay_interface.
Using git master is recommended.
hth Stefan
Kind regards, Carsten
Am 20.02.2014 23:55 schrieb "Francesco Maria Magnini" <fmm1982@gmail.com mailto:fmm1982@gmail.com>:
@Carsten I looked at http://www.iptel.org/sems and seems to be only broken links to downloads. Do you know if the project is still maintained? @Fred Are you using openser as a B2BUA? Il giorno 20/feb/2014, alle ore 19:42, Fred Posner <fred@palner.com <mailto:fred@palner.com>> ha scritto: > Alex's article is one of my favorites. That being said, we switched out an Acme SBC for openser (at the time) and was immediately thrilled. > > Fred Posner > The Palner Group, Inc. > 503-914-0999 (direct) > 954-472-2896 (fax) > > On 02/20/2014 01:14 PM, Alex Balashov wrote: >> Francesco, >> >> Have a look at this blog post: >> >> http://www.likewise.am/2013/03/kamailio-as-an-sbc-session-border-controller/ >> >> >> That said, I agree with Carsten's suggestion of SEMS. >> >> On 02/20/2014 11:04 AM, Francesco Maria Magnini wrote: >> >>> Hi, >>> >>> I would like to have some suggestions about a full replacement of an >>> ACME Packet Net-Net Session Border Controller. >>> By now, ACME SBC performs all the SBC functionalities, mainly: >>> >>> - it is used as a SIP endpoint for SIP client registrations >>> - it is used as a SIP endpoint for interconnection to multiple SIP >>> carriers via SIP trunks >>> - it is used for NAT traversal >>> >>> In this deployment, the SIP Server communicates only with the SBC and >>> this one takes care of the communication between the SIP Server and >>> the external SIP entities (UA clients, SIP Trunks). >>> In this scenario, can I consider to replace the SBC with Kamailio? >>> >>> >>> _______________________________________________ >>> SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list >>> sr-users@lists.sip-router.org <mailto: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 <mailto: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 <mailto:sr-users@lists.sip-router.org> http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
-
Alex Balashov -
Carsten Bock -
Francesco Maria Magnini -
Fred Posner -
Jason Penton -
Jeff Brower -
Klaus Darilion -
Luis Silva -
Melanie Pietersen -
Olle E. Johansson -
Ovidiu Sas -
Stefan Sayer -
Vladimir Broz