Functional Differences Between SBC Edge Portfolio Products

You can deploy the

Unable to show "metadata-from": No such page "_space_variables"

and

Unable to show "metadata-from": No such page "_space_variables"

for various applications including next-generation VoIP, unified communications, SIP trunking, wideband (HD Voice) transcoding, and multi-service business gateway. Throughout this document set, features and processes in the Unable to show "metadata-from": No such page "_space_variables"
that do not apply to the Unable to show "metadata-from": No such page "_space_variables"
are identified with the following note:

Note

Not applicable to

Unable to show "metadata-from": No such page "_space_variables"

.

When you see this note, be aware that it applies to all content on the page or the content specifies (unless noted otherwise), as well as all child pages for that page. If a note does not appear, it indicates that the feature or functionality applies to both products.

Functional/Feature Differences Between SBC Edge Portfolio Product Offerings

Function/Feature	SBC 1000/2000	Unable to show "metadata-from": No such page "_space_variables" (On Prem and Public Cloud)
Licensing Manager		Node Locked Licensing for 1000/2000 and SWe Edge SBCaaS Billing reported by Ribbon Application Management Platform. Network Wide Domain Licensing reported by Ribbon Application Management Platform.
WebUI		Elements in the User Interface that are used solely in conjunction with hardware configuration and processes not included in the Unable to show "metadata-from": No such page "_space_variables" – such as TDM, ASM modules and so on – may not be present in the Unable to show "metadata-from": No such page "_space_variables" user interface. When prominently featured in a section, these elements are identified by notes throughout this documentation set.
System - DNS Local Hosts Table		The functionality from the Unable to show "metadata-from": No such page "_space_variables" DNS Local Hosts table carries forward to the Unable to show "metadata-from": No such page "_space_variables" and provides an alternative to DNS server resolution.
DNS Forwarding
DNS, DNS Hosts, Split DNS
Dynamic IP Routing	NOTE: Dynamic Routing Protocols (OSPF/RIP) are supported.
Port Mirroring	Port Mirroring is implemented as Pipe-Pipe (that is, what comes in or goes out of a port gets forwarded onto Analyzer-Port). Port Mirroring on the SBC 1000/2000 would mainly function without missed mirror packets. Mirrors everything arriving at Mirror-Port in the SBC 1000/2000.	Some extensions (analyzer port MAC entry) are mandatory. Directional mirroring (TX/RX/Both) is supported. A port chosen as "Mirror Port" does not accept taking calls; this is specifically used to mirror packets. Mirrors only UNICAST frames within MTU size. An Analyzer port functions as a transmit-only port; no packets received on this port go through processing. Dynamic switch to Media port happens when mirroring is stopped. Packets mirrored are sent to the "analyzer port" as destination MAC; this is obtained from the user. Port mirroring is completed at the virtualized guest layers and the software. Since the amount of resources (for example, memory) is quite finite and determined during startup, packets that would need mirroring could be skipped. Processes layers of classification, and DOS attack prevents layers before Port Mirroring.
Transcoding
Application Solution Module (ASM) and supported applications, including: Microsoft Skype for Business Survivable Branch Appliance (SBA) Approved partner solutions for ASM.
Direct Routing Survivable Branch Appliance (Teams SBA)
PRI/BRI/CAS/FXS/FXO interface features (configuration, call termination/origination, and such)
One Number Fax (ONF)
Ribbon Application Management Platform Integration	supports baseline RAMP	Supports: NWDL Licensing SBCaaS Billing VQ Reporting
SIP Registrar
Azure Marketplace Deployment
AWS
SIPREC

Space shortcuts

Page tree

Functional/Feature Differences Between SBC Edge Portfolio Product Offerings