nanog mailing list archives

Re: Feedback - SBC Vendors.


From: Shawn Ritchie <shawnritchie () gmail com>
Date: Thu, 9 Aug 2018 16:47:04 -0500

I second what's been said about ACME Packet; loved them when we first got
them, phasing them out now in favor of Ribbon due to what a pain Oracle has
been to deal with.

We're all hardware on the Ribbon side, using both the 5k line and some
premise 1k SBC's. They've been fine so far.

On Thu, Aug 9, 2018 at 9:26 AM Ryan Finnesey <ryan () finnesey com> wrote:

Thanks I will post there as well







________________________________
From: Hiers, David <David.Hiers () cdk com>
Sent: Thursday, August 9, 2018 10:11:33 AM
To: James Milko; Ryan Finnesey
Cc: nanog () nanog org
Subject: RE: Feedback - SBC Vendors.

You might want to drop this question on the VoiceOps list:

voiceops () voiceops org

It runs at a good signal-to-noise ratio, so you'll get some useful
responses.


David


-----Original Message-----
From: NANOG [mailto:nanog-bounces+david.hiers=cdk.com () nanog org] On
Behalf Of James Milko
Sent: Thursday, August 09, 2018 7:06 AM
To: Ryan Finnesey <ryan () finnesey com>
Cc: nanog () nanog org
Subject: Re: Feedback - SBC Vendors.

 Which Ribbon product are you looking at?  There are quite a few now and
they have different code bases/features.

JM

On Wed, Aug 8, 2018 at 7:56 PM, Ryan Finnesey <ryan () finnesey com> wrote:

I am going to have to install a series of SBCs for a  voice offering
connected to Microsoft Teams.  We are going to pass the SIP traffic
off to a larger number of SIP providers.  I would like  to get some
feedback from the group on SBC vendors.  I have two options for
vendors Ribbon or AudioCodes.  I am leaning towards a software based SBC
over an appliance.

Would be helpful to get the other members feedback on Ribbon or
AudioCodes deployments within their networks.

Cheers
Ryan



----------------------------------------------------------------------
This message and any attachments are intended only for the use of the
addressee and may contain information that is privileged and confidential.
If the reader of the message is not the intended recipient or an authorized
representative of the intended recipient, you are hereby notified that any
dissemination of this communication is strictly prohibited. If you have
received this communication in error, notify the sender immediately by
return email and delete the message and any attachments from your system.



-- 
Shawn


Current thread: