Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

You can deploy the
Spacevars
0series4
and 
Spacevars
0series3
for a variety of 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
Spacevars
0series4
 that are not applicable to the
Spacevars
0series3
are identified with the following note:


Note used in documentation to identify content not Applicable to the

Spacevars
0series3
:

Info
titleNote

Not applicable to 

Spacevars
0series3
.


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

Functional/Feature Differences Between SBC Edge Portfolio Product Offerings

Function/FeatureSBC 1000/2000

Spacevars
0series3
 (On Prem and Public Cloud)

Licensing Manager(tick)

(tick)

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(tick)

(tick)

Elements in the User Interface that are used solely in conjunction with hardware configuration and processes that are not included in the

Spacevars
0series3
– such as TDM, ASM modules and so on – may not be present in the
Spacevars
0series3
user interface. When prominently featured in a section, these elements have been identified by Notes throughout this documentation set.

System - DNS Local Hosts Table

(tick)


(tick)

The functionality from the 

Spacevars
0product
DNS Local Hosts table carries forward to the
Spacevars
0series3
and provides an alternative to DNS server resolution.

DNS Forwarding(tick)(error)
DNS, DNS Hosts, Split DNS(tick)(tick)

Dynamic IP Routing

(tick)

NOTE: Dynamic Routing Protocols (OSPF/RIP) are supported.

(error)
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 mostly function without any missed mirror packets.
  • Mirrors everything arriving at Mirror-Port in the SBC 1000/2000.
  • Some extensions (that is, 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 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 "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) are quite finite and determined during startup, there exists a possibility of potentially skipping packets that would need mirroring.
  • Processes layers of classification and DOS attack prevents layers prior to Port Mirroring.
Transcoding(tick)(tick)

Application Solution Module (ASM) and supported applications including:

(tick)(error)
Direct Routing Survivable Branch Appliance (Teams SBA)(tick)(tick)
PRI/BRI/CAS/FXS/FXO interface features (configuration, call termination/origination, and such)(tick)(error)
One Number Fax (ONF)(tick)(error)
Ribbon Application Management Platform Integration

(tick) 

supports baseline RAMP

(tick)

Supports:

  • NWDL Licensing
  • SBCaaS Billing
  • VQ Reporting

SIP Registrar

(tick)(tick)
Azure Marketplace Deployment(error)(tick)

AWS

(error)(tick)
SIPREC(error)(tick)

...