<html>
<head>
<meta content="text/html; charset=windows-1252"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
I'm not sure I share your narrow view of what an SBC is and the role
it plays in modern network architecture. <br>
<br>
There is absolutely a subset of uses for an SBC that fit perfectly
into the box you have outlined but in the broader sense it is a
demarcation and control point between network segments where you can
inject interworking and business logic. <br>
<br>
For example: <br>
<ul>
<li>Crypto offload - softswitches spending cycles on media crypto
is wasteful and occasionally not possible<br>
</li>
<li>Transcoding - G711 is a anchor we wear around our necks, and
the lack of a SINGLE clear successor means transcoding is a
necessity, I wont even open the can of worms that is faxing but
as im sure anyone who has had the displeasure of troubleshooting
a T38 negotiation with a rogue media gateway 2 carrier hops from
you can tell you, just being able to transcode and make both
sides happy is the path to a long and serene life as a network
operator. <a class="moz-txt-link-freetext" href="http://i.imgur.com/BB4T3RW.png">http://i.imgur.com/BB4T3RW.png</a><br>
</li>
<li>CALEA taps </li>
<li>IPV4/IPV6 interworking - to my knowledge most of the CPE and
commercial elements havent fully gotten on the V6 bandwagon but
anyone dealing with mobile voice knows this reality</li>
<li>Media control / monitoring - MOS monitoring / QOS enforcement</li>
<li>Security services - sanitizing SIP traffic so you dont spend
softswitch cycles on answering free-floating internet hostility</li>
<li>Abstraction and load balancing <br>
</li>
<li>Fraud mitigation - I have written whole papers on this so Ill
save the pontification on this topic<br>
</li>
</ul>
<br>
And that is beyond the massive subset of problems I have solved
using the SBC as a swiss army knife to bludgeon success into
scenarios that would otherwise be at an impasse because the elements
on either side of it did not belong to me or were not able to have
their native behavior altered for various rea$on$. <br>
<br>
An SBC is the Thneed of the modern communications network
<a class="moz-txt-link-freetext" href="https://www.youtube.com/watch?v=R7XA0h6HeOw">https://www.youtube.com/watch?v=R7XA0h6HeOw</a> <br>
<br>
<br>
<br>
<div class="moz-cite-prefix">On 4/6/2016 7:16 PM, Alex Balashov
wrote:<br>
</div>
<blockquote cite="mid:5705C2E1.80303@evaristesys.com" type="cite">That's
just it. SBCs are a terrible example of "NFV" because SBCs do not
actually perform a "network function" of the sort that begs to be
decoupled and abstracted in the way that NFV and SDN envisions,
like software-defined switches and routers. The idea that the SBC
is a kind of "voice firewall" is a fiction pushed by the marketing
departments of SBC vendors.
<br>
<br>
What is an SBC? It's a SIP B2BUA with some sort of provisioning
and management interface. If you're lucky, there are some ASICs or
kernel-mode crypto, transcoding and/or packet forwarding
functions. It's an application-layer construct, a giant softphone
touted as a condom that must go over innocent and vulnerable
"softswitches". It's not a "network" element, but it looks much
better on Visio diagrams to depict it as one.
<br>
<br>
On 04/06/2016 09:58 PM, Ryan Delgrosso wrote:
<br>
<br>
<blockquote type="cite">They have more than a buzzword for this,
its a whole movement.
<br>
<br>
Realistically NFV encompasses more than just raw virtualization
its also
<br>
elastic capacity and the orchestration layer to manage it. The
only
<br>
problem is most vendors have only accomplished the
virtualization part
<br>
and are still sorting out the orchestration while trumpeting
NFV.
<br>
<br>
<br>
<br>
<br>
On 4/6/2016 6:45 PM, Alex Balashov wrote:
<br>
<blockquote type="cite">So, it's news to the Bellhead world that
most "SBCs" run on commodity
<br>
pizza boxes & OSs that are branded by the vendor and
resold at large
<br>
markups, and that the software can be separated from the
hardware and
<br>
executed on other pizza boxes, and, indeed, inside VMs? And
they have
<br>
a whole buzzword for this?
<br>
<br>
</blockquote>
<br>
_______________________________________________
<br>
VoiceOps mailing list
<br>
<a class="moz-txt-link-abbreviated" href="mailto:VoiceOps@voiceops.org">VoiceOps@voiceops.org</a>
<br>
<a class="moz-txt-link-freetext" href="https://puck.nether.net/mailman/listinfo/voiceops">https://puck.nether.net/mailman/listinfo/voiceops</a>
<br>
</blockquote>
<br>
<br>
</blockquote>
<br>
</body>
</html>