Agreed on the SBC point. That said, I have personally set up SER (before the fork a number of years ago) to work with Level 3's Viper platform and carried a great deal of production traffic across it. The important thing to remember is that SER acts how you tell it to act, so getting it to work correctly for what L3 expects is highly dependent on your configuration and routing logic. -Scott -----Original Message----- From: voiceops-bounces at voiceops.org [mailto:voiceops-bounces at voiceops.org] On Behalf Of Matthew S. Crocker Sent: Thursday, June 03, 2010 12:34 PM To: Robert Dawson Cc: VoiceOps at voiceops.org Subject: Re: [VoiceOps] Anyone using OpenSIPS/OpenSER/Kamailio to interface with L3 OpenSIPS is not an SBC as the members of their mailing list will readily and loudly attest. OpenSIPS is a SIP Proxy. OpenSIPS + rtp-proxy can provide many of the functions of an SBC. Personally I wouldn't allow anything on your private VoIP LAN that I didn't have direct control over. I'm not against using OpenSIPS or Asterisk but I wouldn't let my customers manage it and have direct access to my switch. ----- Original Message -----
From: "Robert Dawson" <robert.dawson at mindshift.com> To: VoiceOps at voiceops.org Sent: Thursday, June 3, 2010 11:39:42 AM Subject: [VoiceOps] Anyone using OpenSIPS/OpenSER/Kamailio to interface with L3
I have a customer that I would like to setup on their own SBC to avoid adding the overhead/licensing costs to our Acmes.
Robert Dawson
_______________________________________________ VoiceOps mailing list VoiceOps at voiceops.org https://puck.nether.net/mailman/listinfo/voiceops
-- Matthew S. Crocker President Crocker Communications, Inc. PO BOX 710 Greenfield, MA 01302-0710 http://www.crocker.com P: 413-746-2760 _______________________________________________ VoiceOps mailing list VoiceOps at voiceops.org https://puck.nether.net/mailman/listinfo/voiceops