200 concurrent calls would be a good start with 20 calls a second. If there is a platform that can be virtualized on my current equipment, that would be the preferred method. We have a high available cloud that currently runs many Centos virtual PBX instances. Thanks, R. Grant Baxley President & CEO Infinity Computer Solutions 813 W Platt St. Tampa, FL 33606 Toll Free: 1.888.287.9198 Local: 813.319.3704 From: james jones [mailto:james.voip at gmail.com] Sent: Tuesday, February 19, 2013 1:56 PM To: Grant Baxley Cc: voiceops at voiceops.org Subject: Re: [VoiceOps] Session Border Controllers How many concurrent calls? How many calls per second? On Tuesday, February 19, 2013, Grant Baxley wrote: I am looking to implement a cost effective session border controller. Can anyone point me in the right direction? We would need to be able to route calls to and from different IP addresses based on source and destination. Thanks, R. Grant Baxley President & CEO Infinity Computer Solutions 813 W Platt St. Tampa, FL 33606 Toll Free: 1.888.287.9198 Local: 813.319.3704
Hi Grant - We use FreeSWITCH running on CentOS, virtualised with OpenVZ. The largest instances run up to 4,000 sessions (=2,000 concurrent calls) and have peaked at over 40 calls/sec; they use less than half of an i7-3770 CPU at this level. --Dave From: voiceops-bounces at voiceops.org [mailto:voiceops-bounces at voiceops.org] On Behalf Of Grant Baxley Sent: 19 February 2013 18:58 To: james jones Cc: voiceops at voiceops.org Subject: Re: [VoiceOps] Session Border Controllers 200 concurrent calls would be a good start with 20 calls a second. If there is a platform that can be virtualized on my current equipment, that would be the preferred method. We have a high available cloud that currently runs many Centos virtual PBX instances. Thanks, R. Grant Baxley President & CEO Infinity Computer Solutions 813 W Platt St. Tampa, FL 33606 Toll Free: 1.888.287.9198 Local: 813.319.3704 From: james jones [mailto:james.voip at gmail.com] Sent: Tuesday, February 19, 2013 1:56 PM To: Grant Baxley Cc: voiceops at voiceops.org Subject: Re: [VoiceOps] Session Border Controllers How many concurrent calls? How many calls per second? On Tuesday, February 19, 2013, Grant Baxley wrote: I am looking to implement a cost effective session border controller. Can anyone point me in the right direction? We would need to be able to route calls to and from different IP addresses based on source and destination. Thanks, R. Grant Baxley President & CEO Infinity Computer Solutions 813 W Platt St. Tampa, FL 33606 Toll Free: 1.888.287.9198 Local: 813.319.3704
Can the vm handle transcoding or is it primarily sip signaling? On Tuesday, February 19, 2013, David Knell wrote:
Hi Grant -****
** **
We use FreeSWITCH running on CentOS, virtualised with OpenVZ. The largest instances run up to****
4,000 sessions (=2,000 concurrent calls) and have peaked at over 40 calls/sec; they use less than****
half of an i7-3770 CPU at this level.****
** **
--Dave****
** **
*From:* voiceops-bounces at voiceops.org <javascript:_e({}, 'cvml', 'voiceops-bounces at voiceops.org');> [mailto:voiceops-bounces at voiceops.org<javascript:_e({}, 'cvml', 'voiceops-bounces at voiceops.org');>] *On Behalf Of *Grant Baxley *Sent:* 19 February 2013 18:58 *To:* james jones *Cc:* voiceops at voiceops.org <javascript:_e({}, 'cvml', 'voiceops at voiceops.org');> *Subject:* Re: [VoiceOps] Session Border Controllers****
** **
200 concurrent calls would be a good start with 20 calls a second. ****
** **
If there is a platform that can be virtualized on my current equipment, that would be the preferred method. We have a high available cloud that currently runs many Centos virtual PBX instances. ****
** **
** **
Thanks,****
** **
R. Grant Baxley President & CEO Infinity Computer Solutions 813 W Platt St. ****
Tampa, FL 33606 Toll Free: 1.888.287.9198 Local: 813.319.3704****
** **
*From:* james jones [mailto:james.voip at gmail.com <javascript:_e({}, 'cvml', 'james.voip at gmail.com');>] *Sent:* Tuesday, February 19, 2013 1:56 PM *To:* Grant Baxley *Cc:* voiceops at voiceops.org <javascript:_e({}, 'cvml', 'voiceops at voiceops.org');> *Subject:* Re: [VoiceOps] Session Border Controllers****
** **
How many concurrent calls?****
How many calls per second?
On Tuesday, February 19, 2013, Grant Baxley wrote:****
I am looking to implement a cost effective session border controller. Can anyone point me in the right direction? ****
****
We would need to be able to route calls to and from different IP addresses based on source and destination. ****
****
****
Thanks,****
****
R. Grant Baxley President & CEO Infinity Computer Solutions 813 W Platt St. ****
Tampa, FL 33606 Toll Free: 1.888.287.9198 Local: 813.319.3704****
****
-- Sent from Gmail Mobile
That's signalling and proxying media for most of the calls; no transcoding beyond u-law <-> A-law. --Dave From: Andrew Dixon [mailto:adixon at artjconsultants.com] Sent: 19 February 2013 20:18 To: David Knell Cc: Grant Baxley; voiceops at voiceops.org Subject: Re: [VoiceOps] Session Border Controllers Can the vm handle transcoding or is it primarily sip signaling? On Tuesday, February 19, 2013, David Knell wrote: Hi Grant - We use FreeSWITCH running on CentOS, virtualised with OpenVZ. The largest instances run up to 4,000 sessions (=2,000 concurrent calls) and have peaked at over 40 calls/sec; they use less than half of an i7-3770 CPU at this level. --Dave From: voiceops-bounces at voiceops.org <javascript:_e(%7b%7d,%20'cvml',%20'voiceops-bounces at voiceops.org');> [mailto:voiceops-bounces at voiceops.org <javascript:_e(%7b%7d,%20'cvml',%20'voiceops-bounces at voiceops.org');> ] On Behalf Of Grant Baxley Sent: 19 February 2013 18:58 To: james jones Cc: voiceops at voiceops.org <javascript:_e(%7b%7d,%20'cvml',%20'voiceops at voiceops.org');> Subject: Re: [VoiceOps] Session Border Controllers 200 concurrent calls would be a good start with 20 calls a second. If there is a platform that can be virtualized on my current equipment, that would be the preferred method. We have a high available cloud that currently runs many Centos virtual PBX instances. Thanks, R. Grant Baxley President & CEO Infinity Computer Solutions 813 W Platt St. Tampa, FL 33606 Toll Free: 1.888.287.9198 Local: 813.319.3704 From: james jones [mailto:james.voip at gmail.com <javascript:_e(%7b%7d,%20'cvml',%20'james.voip at gmail.com');> ] Sent: Tuesday, February 19, 2013 1:56 PM To: Grant Baxley Cc: voiceops at voiceops.org <javascript:_e(%7b%7d,%20'cvml',%20'voiceops at voiceops.org');> Subject: Re: [VoiceOps] Session Border Controllers How many concurrent calls? How many calls per second? On Tuesday, February 19, 2013, Grant Baxley wrote: I am looking to implement a cost effective session border controller. Can anyone point me in the right direction? We would need to be able to route calls to and from different IP addresses based on source and destination. Thanks, R. Grant Baxley President & CEO Infinity Computer Solutions 813 W Platt St. Tampa, FL 33606 Toll Free: 1.888.287.9198 Local: 813.319.3704 -- Sent from Gmail Mobile
Have you looked at Kamailio? We love it and it handles much higher volumes than you require. We are also running on centos. Sent from my iPhone On Feb 19, 2013, at 11:00 AM, "Grant Baxley" <GBaxley at hostinfinity.com<mailto:GBaxley at hostinfinity.com>> wrote: 200 concurrent calls would be a good start with 20 calls a second. If there is a platform that can be virtualized on my current equipment, that would be the preferred method. We have a high available cloud that currently runs many Centos virtual PBX instances. Thanks, R. Grant Baxley President & CEO Infinity Computer Solutions 813 W Platt St. Tampa, FL 33606 Toll Free: 1.888.287.9198 Local: 813.319.3704 From: james jones [mailto:james.voip at gmail.com] Sent: Tuesday, February 19, 2013 1:56 PM To: Grant Baxley Cc: voiceops at voiceops.org<mailto:voiceops at voiceops.org> Subject: Re: [VoiceOps] Session Border Controllers How many concurrent calls? How many calls per second? On Tuesday, February 19, 2013, Grant Baxley wrote: I am looking to implement a cost effective session border controller. Can anyone point me in the right direction? We would need to be able to route calls to and from different IP addresses based on source and destination. Thanks, R. Grant Baxley President & CEO Infinity Computer Solutions 813 W Platt St. Tampa, FL 33606 Toll Free: 1.888.287.9198 Local: 813.319.3704 _______________________________________________ VoiceOps mailing list VoiceOps at voiceops.org<mailto:VoiceOps at voiceops.org> https://puck.nether.net/mailman/listinfo/voiceops
On 02/19/2013 03:12 PM, Joshua Goldbard wrote:
Have you looked at Kamailio? We love it and it handles much higher volumes than you require. We are also running on centos.
It's quite suitable if the desire is simply to route based on that criteria. However, it falls apart once you start looking for to do some of the other things commercial SBCs out there do per se. 99% of our business comes from Kamailio-related consulting. We've done plenty of those projects. We've had folks come to us looking for us to build SBCs, complete with media hairpinning, to front Metaswitches and so on. It's not a good idea. Never again. Nowadays, when they're looking for something like that, I send them looking toward SEMS (SIP Express Media Server), or the SBC appliance that Frafos has commercialised on top of it: http://www.frafos.com/products/abc-sbc/ -- Alex -- Alex Balashov - Principal Evariste Systems LLC 235 E Ponce de Leon Ave Suite 106 Decatur, GA 30030 United States Tel: +1-678-954-0670 Web: http://www.evaristesys.com/, http://www.alexbalashov.com/
On Tue, Feb 19, 2013 at 1:48 PM, Grant Baxley <GBaxley at hostinfinity.com> wrote:
I am looking to implement a cost effective session border controller. Can anyone point me in the right direction?
We would need to be able to route calls to and from different IP addresses based on source and destination.
On Feb 19, 2013, at 15:16 , Alex Balashov <abalashov at evaristesys.com> wrote:
On 02/19/2013 03:12 PM, Joshua Goldbard wrote:
Have you looked at Kamailio? We love it and it handles much higher volumes than you require. We are also running on centos.
It's quite suitable if the desire is simply to route based on that criteria.
However, it falls apart once you start looking for to do some of the other things commercial SBCs out there do per se.
Alex, very good point: Routing calls based on From and Request-URI is really an independent problem from security functions, NAT-fixup, multi-VRF support, etc. But, Grant, Beware: You're using a term "Session Border Controller" but only talking about the call routing function. When the Big Three (Acme Packet, Metaswitch, and Sonus) use this term, "SBC", they're referring to all of these functions: -- Ability to gracefully single-source and distributed handle attacks from the Internet -- Traffic from numerous VRFs (so that customer A's 10.0.0.1 is not the same as customer B's 10.0.0.1) -- Hosted NAT Traversal -- Transcoding media -- Lawful Intercept hooks -- Demultiplexed SIP trunks (so that each SIP "path" can come from a different IP address or port) -- Constraints like Calls-per-second or Concurrent-calls (so legitimate customers don't cause a failure) -- Failover from one SBC to another -- Distributed SBC models where one box handles signaling and many more handle media -- 802.1q VLAN tagging support -- Support for failover to BroadWorks-style registrar redundancy (where the mated registrar servers have distinct IP addresses) -- SNMP management -- Interworking SIP/UDP and SIP/TCP -- Jumbo SIP (SIP datagrams over 1300 bytes, out of compliance with RFC 3261) -- SIP/TLS and SRTP, and decryption thereof -- Configurable media management (to release media when possible, steer it through the SBC when not) I use most of these features daily.
mark at ecg.co +12293160013 http://ecg.co/lindsey
Yep. That is, in essence, what I meant to say, that the Big Three definition of these is quite more elaborate than the nebulous way that the term SBC gets thrown around in a pedestrian context. The latter seems, at its essence, to consist of some sort of generalised call transit element with basic static routing based on SIP message parts, perhaps with RTP relay and maybe even transcoding--at most. Mark R Lindsey <lindsey at e-c-group.com> wrote:
On Tue, Feb 19, 2013 at 1:48 PM, Grant Baxley <GBaxley at hostinfinity.com> wrote:
I am looking to implement a cost effective session border controller. Can anyone point me in the right direction?
We would need to be able to route calls to and from different IP addresses based on source and destination.
On Feb 19, 2013, at 15:16 , Alex Balashov <abalashov at evaristesys.com> wrote:
On 02/19/2013 03:12 PM, Joshua Goldbard wrote:
Have you looked at Kamailio? We love it and it handles much higher volumes than you require. We are also running on centos.
It's quite suitable if the desire is simply to route based on that criteria.
However, it falls apart once you start looking for to do some of the other things commercial SBCs out there do per se.
Alex, very good point: Routing calls based on From and Request-URI is really an independent problem from security functions, NAT-fixup, multi-VRF support, etc.
But, Grant, Beware: You're using a term "Session Border Controller" but only talking about the call routing function. When the Big Three (Acme Packet, Metaswitch, and Sonus) use this term, "SBC", they're referring to all of these functions:
-- Ability to gracefully single-source and distributed handle attacks from the Internet
-- Traffic from numerous VRFs (so that customer A's 10.0.0.1 is not the same as customer B's 10.0.0.1)
-- Hosted NAT Traversal
-- Transcoding media
-- Lawful Intercept hooks
-- Demultiplexed SIP trunks (so that each SIP "path" can come from a different IP address or port)
-- Constraints like Calls-per-second or Concurrent-calls (so legitimate customers don't cause a failure)
-- Failover from one SBC to another
-- Distributed SBC models where one box handles signaling and many more handle media
-- 802.1q VLAN tagging support
-- Support for failover to BroadWorks-style registrar redundancy (where the mated registrar servers have distinct IP addresses)
-- SNMP management
-- Interworking SIP/UDP and SIP/TCP
-- Jumbo SIP (SIP datagrams over 1300 bytes, out of compliance with RFC 3261)
-- SIP/TLS and SRTP, and decryption thereof
-- Configurable media management (to release media when possible, steer it through the SBC when not)
I use most of these features daily.
mark at ecg.co +12293160013 http://ecg.co/lindsey
-- 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-0670 Web: http://www.evaristesys.com/, http://www.alexbalashov.com/
Also see RFC 5853. http://tools.ietf.org/html/rfc5853 Simon Le 2013-02-19 21:34, Mark R Lindsey a ?crit :
But, Grant, Beware: You're using a term "Session Border Controller" but only talking about the call routing function. When the Big Three (Acme Packet, Metaswitch, and Sonus) use this term, "SBC", they're referring to all of these functions:
-- Ability to gracefully single-source and distributed handle attacks from the Internet
-- Traffic from numerous VRFs (so that customer A's 10.0.0.1 is not the same as customer B's 10.0.0.1)
-- Hosted NAT Traversal
-- Transcoding media
-- Lawful Intercept hooks
-- Demultiplexed SIP trunks (so that each SIP "path" can come from a different IP address or port)
-- Constraints like Calls-per-second or Concurrent-calls (so legitimate customers don't cause a failure)
-- Failover from one SBC to another
-- Distributed SBC models where one box handles signaling and many more handle media
-- 802.1q VLAN tagging support
-- Support for failover to BroadWorks-style registrar redundancy (where the mated registrar servers have distinct IP addresses)
-- SNMP management
-- Interworking SIP/UDP and SIP/TCP
-- Jumbo SIP (SIP datagrams over 1300 bytes, out of compliance with RFC 3261)
-- SIP/TLS and SRTP, and decryption thereof
-- Configurable media management (to release media when possible, steer it through the SBC when not)
participants (7)
-
abalashov＠evaristesys.com -
adixon＠artjconsultants.com -
dave＠3c.co.uk -
GBaxley＠hostinfinity.com -
j＠2600hz.com -
lindsey＠e-c-group.com -
simon.perreault＠viagenie.ca