PRO SBC Telcobridges for 3CX Connectivity without STUN VPN or 3CX SBC

[austen]

FYI

I have been working with Telcobridges for an SBC solution for 3CX for remote offices, 3CX on Azure and AWS, and 3CX Service Providers. This SBC can be installed on VMware, bare metal and in the cloud and allows for registration of phones and endpoint devices like Yealink that accept an Outbound Proxy.

We have been working with the Telcobridges team for almost a year finalizing this product and we will roll out a hosted version of the Pro SBC as well as consulting to help other providers and companies that are looking for an Enterprise grade SBC.

Here is a link to the webinar we will be having February 25th, 2020!

https://zoom.us/webinar/register/3715819590047/WN_5u5yN_GvSkOzTUZl4sowKw

Matt Ussery

 

[BrenttG]

Unless there is something big and new that this SBC would do that the 3CX SBC's cannot what would be the point to even bother developing something like this?

And what features of the 3CX SBC would we be sacrificing by going with that one, i suspect quite a few....

 

[austen]

Hey Brent,

You will not sacrifice any 3CX features. Everything works on the endpoints. There is no BLF limitation like the 3CX SBC. The other features you get are;

- Label routing, list of DIDs that can be routed per customer
- Multiple customers per SBC instance routed by domain name ie @customer1.domain.com, @customer2.domain.com
- MOS Score
- Call tracing for each leg in a visual format
- DDOS protection
- Integration with STIR/SHAKEN or solutions like ClearIP for robocall blocking
- Can be used as a class 4 switch for SIP trunking
- Least cost routing

These are a few examples, I will cover a lot more in the webinar. It possibly is not a solution for everyone, but for service providers it gives us a lot of flexibility. The pricing is very fair, $500 for 500 simultaneous calls per year if you buy a license and host your own or we will be offering a hosted version mid March that will be very affordable.

Matt

 

[BrenttG]

i still see no reason this would have anything to do with 3CX as an SBC, and whats more, i think we are talking about oranges and avocados here. What this third-party SBC does, versus what the 3CX SBC actually does.

Seems like a bit of a pointless bolt-on in my opinion, much like the coffee can mufflers(fartcan) kids attach to their honda and nissan clunker wannabe race cars

All the modern firmware Yealink devices unless you have a troublesome firewall work perfectly fine on direct stun even in large numbers with proper port mapping, they work even better if paired to a 3CX SBC, and no you actually don't need a device that supports outbound proxy, i have paired legacy devices without such a field to a 3CX SBC perfectly fine manually, you just have to know the basics of SIP and not be a wizard jockey.

the 3CX SBC supports the same platforms, VMware, HyperV, Bare Metal, we have all three in deployment using the Debian 3CX SBC, with tons of phones behind them(150+), without any BLF issues to date on the version 16+ SBCs, and yes, we have sidecars on many of those Yealink's.

 

[austen]

Like I said it does everything the 3CX SBC does and a lot more. Just trying to contribute to the greater good. It is not a replacement but only an enhancement! Guess we will agree to disagree, have a great day sir!

 

[BrenttG]

Like I said it does everything the 3CX SBC does and a lot more. Just trying to contribute to the greater good. It is not a replacement but only an enhancement! Guess we will agree to disagree, have a great day sir!

Does it detect non-provisioned phones on the network, show us their make, model, firmware and mac address in the hosted 3CX Servers admin panel, and give us the ability to provision them with a couple clicks, does it facilitate secure SIP between itself and 3CX and the desk phones behind it if enabled on the PBX? Does it show us the packet loss metrics between itself and the 3CX server, not just between itself and the phones? Does it report to us in the 3CX admin panel every time the WAN IP its behind suddenly changes, and what the new IP is? Does it support seamless failover to another SBC in the event of failure with no assistance from a human?

And does it do all of that, with only a single vCore, and 2 GB of RAM, while utilizing only 09% of that ram?

I think not. Im quite certain 3CX wins here.

DISCLAIMER, i do not work for 3CX, even though it might sound a bit like i do

 

[austen]

Can you remotely host a 3CX SBC? I think not! There are many benefits to this SBC it was not designed by 3CX it is for service providers and companies that do not want to deploy a 3CX SBC at every location.

Does it support unlimited BLF's? Yes it does, does it give more metrics than 3CX yes it does, does it do CDR's and AAA, yes it does.

Does it support SRTP, YES. Does it support TLS, Yes. It does report the change in public IP's! We can force use of Remote Public IP, YES.

MOS score is packet loss detection which I previously put in my original post. It is scalable, it works. I do not disagree that 3CX has an awesome SBC, this is for a different use case. We host 2000 extensions using this solution.

We are not trying to replace the use case for the 3CX SBC. We are complimentary to that solution with a specific use case. This SBC also serves as a class 4 switch for SIP trunking. It is another tool you can put in your war chest for customers.

 

[BrenttG]

Actually you can host it remotely, by why would you, it serves no real useful purpose unless your hiding the PBX itself behind a firewall and only opening the tunnel port, strange scenarios...

So your saying, it will report its Public IP any time it changes due to a non static public ip at the remote site, right here so i don't have to go into some third party panel, or go digging for the most recent email about its most recent ip(that likely went into junk)?

and/or here


MOS Score also is not a true packetloss metric for network engineering purposes, im talking about a breakdown of TCP and UDP so I can see if its due to bad cable or bad device(TCP and UDP dropping), or if its due to a routing, firewall or filtering issue(only UDP dropping), or if i need to go scream at the ISP. The type of packet-loss often points directly to its cause, but not always.

So it does some fancy analytics on calls, lovely, nothing that is in my wheelhouse unless its technical in nature or that is mission critical but im sure someone who micro-manages a call center might care.

Supplementary, great, when 3CX says its supported, maybe our analytics loving sales guys can look at it, but until then, we will stay in the realm of supportable. We have hundreds of PBXs in our cloud or on premise and adding to them several a month, due to the government regs, we dont play the carrier game, we leave that to the trunk providers, less hassle for us, more time to build and sell more.

 

[austen]

Well then don't use it! LOL Again we can agree to disagree! I am not saying the 3CX SBC doesn't work. Good luck to you sir! I am not trying to argue with you.

 

[eddv123]

This I think is a positive break-through, thank-you for posting this, I have tested NAT-PASS in a similar way before and as long as you are confident (and competent) with the setup and configuration it is fine.

Telcobridges are a very well known company in the Telecoms sector also so you are also in very good hands.

As mentioned I have tested NAT-PASS before and its main purpose is to assist with tricky network and firewall related issues when using multiple STUN phones.

The downside I found is that you have to use custom templates on the end devices, which (as you are probably aware) your setup is un-supported as far as 3CX are aware.