16-20190307040627-37200W PID 07 SBCE 8 - 0 Final

Avaya Midmarket Solution
Product Information Document –

Session Border Controller for Enterprise R8.0
Document version 1.0
© 2019 Avaya Inc. All rights reserved. Page 1

Avaya SBCE R8.0 – Midmarket Edition
Table of Contents
Introduction to the Avaya Midmarket Solution ..........................................................................4
Introduction to Avaya SBCE R8.0 ............................................................................................5
ASBCE 8.0 Feature Descriptions.............................................................................................7
Simplification of the ASBCE user experience .......................................................................7
Better Together with Equinox .............................................................................................10
Opening Up the SBCE architecture to ecosystem ..............................................................10
Technology currency & Security.........................................................................................11
Platform support.................................................................................................................12
Security Comparison .............................................................................................................12
Business Partner Value Proposition ......................................................................................12
Market Needs, Trends and Growth ....................................................................................12
Value Proposition ...............................................................................................................14
Avaya SBCE Midmarket Use Cases ......................................................................................14
Product Specifications ...........................................................................................................15
Compatibility with Avaya Solutions .....................................................................................15
Avaya SBCE Components.....................................................................................................18
Licenses and Examples .....................................................................................................18
Avaya SBCE and IP Office.................................................................................................22
Product Structure ...............................................................................................................23
Media and Licensing Order Codes .....................................................................................23
Virtual Appliance Order Codes ...........................................................................................24
Hardware Appliances Order Codes ....................................................................................25
System Engineering Consideration ....................................................................................25
Cloud Deployments............................................................................................................29
Computing and Server Requirements ....................................................................................31
IP Office / Midmarket .........................................................................................................31
Virtualization Resource Profiles .........................................................................................32
Supported Hypervisors for Virtualized environment ............................................................32
Supported Browsers ..........................................................................................................33
Supported VPN-less SIP Remote Worker Endpoints .........................................................34
Sizing, Licensing, and Quoting ..............................................................................................35
Solution Capacities and Performance ................................................................................35
Solution capacities quick reference ....................................................................................35
PLDS Licensing .................................................................................................................36
Licensing Control ...............................................................................................................37
Quoting ..............................................................................................................................37
Services and Support ............................................................................................................38
Warranty ............................................................................................................................38
Support Services Offer .......................................................................................................38

Resources .............................................................................................................................39
Web Sites ..........................................................................................................................39
Documents.........................................................................................................................39

Introduction to the Avaya Midmarket Solution

The diagram above depicts the entire Avaya Midmarket Solution. Security is essential to the
Avaya Midmarket Solution which enables unified communications and customer engagement.
This document discusses the Avaya Session Border Controller for Enterprise and its role in the
security for the Avaya Midmarket Solution. It will cover the basic features and functions of the
solution, the components, sizing, licensing, and quoting, as well as required and optional
support services offers.

Introduction to Avaya SBCE R8.0

ASBCE release 8.0 is the latest and Avaya’s best Session Border Controller for Enterprise
(ASBCE) release to date, focused on improving the experience of the ASBCE customers with a
slew of new features as detailed in the feature section of this document. ASBCE is the only fully
stack-tested solution for all Avaya Call Servers. ASBCE release 8.0 continues as fully tested
and supported for use with Aura and IP Office to secure SIP trunking to Service Provider and
offering VPN-less secure Remote Worker functionality.
The same way Release 7.2.2 updated and replaced any Release 7.x for commercial market,
Avaya Session Border Controller for Enterprise (ASBCE) release 8.0 will replace the existing
Avaya Session Border Controller for Enterprise (ASBCE) release 7.2.2 as the current release
for new system sales.
ASBCE following the “Buy To Current” program, ASBCE customers are able to select during the
configuration process in Avaya One Source whether they will want to implement R7 or R8.
However, Avaya One Source will only offer customer the option to configure their system with
Release 8.0. By selecting deployment with R7, one will be granted access to both R8 and R7
downloads in PLDS.
ASBCE release 7.1.0 is kept available and maintained by Avaya for customers requiring Joint
Interoperability Testing Command (JITC) certification. Avaya will continue releasing security up
issues, also known as service packs, of Release 7.1.0 until it is replaced by a future version of
Release 8.x on the DISA Approved Product List (APL). The current ASBCE Service Pack
meeting JITC certification requirements is Release 7.1.0.6 at the time of issuance of this
document. (check Avaya support site for update on the latest Service Pack available).
Avaya Session Border Controller for Enterprise (Avaya ASBCE or ASBCE) brings key values to
the Avaya SIP Unified Communication solution set:
 ASBCE focuses on the Enterprise, Midmarket and SME. ASBCE’s user-friendly GUI for
provisioning and maintenance to simplify installation while still providing powerful
Enterprise-level SIP security and functionality.
 ASBCE is the only fully solution-stack tested Session Border Controller for Avaya
communications solutions. From product development through to our Global Service
provider SIP Compliance Program (GSSCP) thru which ITSP offers are tested and
certified with ASBCE, ASBCE delivers a solution that “just works” to our Business
Partners and Customers community.
 ASBCE brings unique and market-leading functionality with Advanced Services for
Remote Workers using the Avaya clients in a VPN-less environment that allow secure
access to the full Avaya feature set without the complications of VPN.
 Advanced integration with Avaya Equinox on premise or cloud based offer to enable
secure edge traversal for WebRTC communications.
The new features delivered with ASBCE 8.0 significantly improve ASBCE partners
and customers overall experience, with simpler deployment, configuration and
upgrade delivering improved OPEX as well as minimizing any service intervention
on the ASBCE uptime, especially for Multi-tenant setups.
Additional enhancement to WebRTC support, scalability with Equinox collaboration
and SIP call path restoration makes ASBCE 8.0 the network edge solution of
choice for all of Avaya’s SIP UC solution constructs from the smallest and simplest
SIP trunk solution to the largest Cloud offerings.
Key trends in the Enterprise communications market are:
 Network Transformation – embracing VoIP, centralization of infrastructure and trunking
 Evolution to SIP trunking – evolving to SIP trunks from TDM trunks
 Evolution of VoIP to SIP-based UC
 Growth of Remote/Mobile Workers

The larger enterprises with larger IT resources are driving these trends, but mid-sized and
smaller enterprises are now moving forward towards SIP-based communications and unified
communications (UC) as the vendor community and service providers have advanced
availability and simplicity. The key strategic need in both the Enterprise and the SME space is
for UC security and a strong tactical need for interoperability across the variety of SIP
implementations within the SIP vendor community. There is significant variability across the
Enterprise landscape in terms of alignment to these trends.
A key component of the delivery of a SIP-based communications solution is the device that
insures the security of SIP/VoIP connectivity for an Enterprise when reaching beyond the
Enterprise data network firewall. Data network firewalls protect a variety of traffic types;
however, they are not ‘application-aware’ for SIP-based communications. The current industry
best-practice for securing the Enterprise network edge for SIP-based communications is
implementation of a Session Border Controller (SBC) at the edge of the Enterprise network
since all SIP ingress/egress traffic crosses the SBC.
The diagram below shows the ASBCE in its space as the UC security ‘edge’ in a customer
network
Avaya SBCE resides at the edge of the network and securely enables multi-modal (Voice,
video, messaging, etc.) communications with external entities be the Service Providers,
Remote/Mobile workers, or even other enterprises ‘federating’ communications with the
customer environment.

The Enterprise market is much segmented based on size of the addressed customer, unique
Security needs, sophistication of applications, and varying sensitivity to cost. The ASBCE offer
addresses SIP-based Unified Communications security needs for both the Enterprise
(integration with Aura) and SME (integration with IPO) communications market segments.
ASBCE 8.0 Feature Descriptions

Even though ASBCE R8.0 primary theme and focus has been to simplify the user experience,
the release delivers several additional benefits:
 Improved resiliency and scalability with Equinox
 Enterprise Grade reliability for SIP contact Center with Aura 8.x
 Opening the ASBCE architecture to external ecosystems
 Keeping current with the platform technology and latest security requirements
Simplification of the ASBCE user experience

Based on customer and partner feedback, the user experience was an area that had identified
as requiring improvement. Over the past several years, ASBCE architecture and feature set had
evolved considerably to meet our large enterprises, our cloud and our SMB customers’
demands however the overall operational side of the product did not follow accordingly. Release
8.0 focus has been to deliver the necessary improvements in this area
Simplified and Improved Backup & Restore [8.0]

Lots of frictions has been removed in Release 8.0 around the backup and restore management
to minimize required OPEX for maintaining an ASBCE system, specifically when ASBCEs are
deployed in multiple pairs under the same EMS
Release 8.0 now enables backup and restore of an individual ASBCE within a multi ASBCE
system.

To facilitate hardware replacement or pre-staging, a Technician or administrator can now take

an ASBCE snapshot and restore this snapshot on an ASBCE with similar HW/virtual resources
without it being under the same EMS.
Additionally, stored backup can now be restored on any EMS/SBCE with the same build
version, Number of NICs and device type.
And finally, configuration cloning is supported independently of the EMS, however same build
version, and number of NICS are still required.
More robust and seamless upgrade [8.0]

Pre-8.0 ASBCE, upgrades were very complex, lengthy and therefore prone to errors.
With 8.0, the upgrade process has entirely been re-architected to reduce its length and
complexity.
New checks and controls have been added in the software to confirm the status and the actual
steps completion of the upgrade or roll back processes.
Additional and extra strengths in the error handling and improved clarity of steps have been
introduced in the rollback process if/when necessary to rollback.
Removal of the dependency on EMS connectivity for upgrade / rollback which used to be a very
heavy constraint for efficient pre-staging, has also been included in Release 8.0
CLI introduction for Improved pre-staging /system prepping [8.0]

Before ASBCE 8.0, EMS was the only mean to configure the system.
Starting with release 8.0, a brand-new Command Line Interface (CLI) has been introduced to
enable scripting for easier system prepping. This for instance enables a system engineer or
administrator to restore a snapshot and customize further in an automatic way via scripts
injected thru the CLI.
The list of CLI commands that are being made available starting with 8.0 are available in the
administration guide of ASBCE Release 8.0.
Additional CLI (and APIs) will be made available during the Release 8.x cycle.
Based on customer and partner follow accordingly. Release 8.0 main focus has been to deliver
the necessary improvements in this particular area
Simplified Certificate Management [8.0]

With prior releases, default certificates were preloaded into the ASBCE but complex multiple
steps, and sometime system impacting procedures were necessary to change, update and/or
remove the certificates in place, causing a lot of frustrations and were source of many
configuration errors in the field.
There was no easy way to visualize or confirm the current certificate setup, which made
erroneous configuration situations even worse since these errors were only discoverable when
encrypted traffic was attempted.
Release 8.0 introduce a set of configuration pages in its GUI(EMS) and CLI to make certificate
management clear and easily accessible.
Trough any of these two interfaces, the administrator can now install, manage and verify the
certificates in ASBCE, whether coming from a 3 rd party CA or ASBCE self-generated.
We expect this feature to receive an extremely warm welcome among our partners or
customers deploying the ASBCE in multi-tenant configuration where certificates need to
constantly be added or removed.

Non-intrusive Multi tenancy setup thru on the fly configurations changes

[8.0]
With Release 7.x, changing or removing an ASBCE tenant configuration was for certain
scenario, service impacting causing operational headaches due to the necessary scheduling of
a maintenance window off office hours, which in situations when ASBCE was deployed as the
security edge of a cloud service, could prove extremely challenging.
With Release 8.0, existing tenant configuration or deletion can happen on the fly without
requiring any restart or reboot of the application, greatly simplifying the life of the administrator.
Besides tenant parameters and deletion, on the fly configuration will be extended to additional
parameter throughout the release 8.x to cover all types of deployment situations.
Removal of Volume Tiered pricing for a simpler ordering experience [8.0]

Starting at the General Availability of ASBCE 8.0 on February 11 th 2019, the SBCE license
structure will be simplified by removing the Tiered volume structure that had been in place since
the ASBCE inception.
This will deliver an improved ordering experience and transparency for our partners and
customers.
The licenses impacted by this simplification are:
 Standard license for Aura
 Standard license for IPO
 Standard HA license for Aura
 Standard HA license for IPO
 Advanced license for Aura
 Advanced license for IPO
 Advanced HA license for Aura
 Advanced HA license for IPO
 Dynamic license for Aura (Dynamic license not offered for the IPO portfolio)
An identical simplification has also been applied for the upgrade license from R7.x to R8.0 for all
of the licenses listed above.
Bundling of ASBCE software and Hardware for small to very small

business as part of an ASBCE 8.0 - Launch promotion [ 8.0 – limited
duration]
On top of the initial licensing simplification, and for a limited period of time starting on release
8.0 GA date, the four following bundles are going to be available for IPO customers only under a
specific promotion program (see the promotion section on the sales portal for more details):
1. 10 Standard licenses
2. 30 Standard licenses
3. 20 Standard + 10 Advanced licenses
4. 50 Standard + 20 Advanced licenses
The CAD230 Portwell – low end appliance - is going to be included in this bundle, and the
licenses are based on ASBCE R8

SNMP alarming when ASBCE is nearing session saturation

ASBCE generates a new SNMP alarm when ASBCE is nearing 80% of the call leg capacity of
the system.
Better Together with Equinox

Release 8.0 continues to solidify and improves the existing integration between ASBCE and the
Equinox solution.
MSFT Edge Browser support for WebRTC communications [8.0]

Contrary to Firefox or Chrome, the Edge browser is demonstrating non-standard behaviors
during WebRTC calls. Starting with Release 8.0, the ASBCE will be able to cater for these
nonstandard patterns and properly handle them without any service impact to the end user.
Greater Turn capacity for WebRTC client aka Increased Media Tunneling
capacity [8.0]
The Turn server in the SBCE 8.0 has been enhanced to support multi-threading processing to
make use of any additional compute made available to it.
Unlike for SIP application, the overall Turn capacity the ASBCE can deliver is now directly linked
to the amount of compute available to the software.
This translates into allowing greater capacity for Turn sessions at the cost of greater OVA
footprint (up to 10Vcpu) - this feature is particularly useful for implementation expected to
require large scalability of Turn Media sessions. (like Avaya Equinox Meeting Online) where
WebRTC and/or Equinox Web Clients are expected to be heavily used.
It requires modification of the standard ASBCE OVA properties provided with Release 8.0 which
is based on 4vcpu and 8 Gig of RAM. Using VCenter, the amount of vcpu can be adjusted to up
10 VCPU.
The standard OVA will handle 100-120 Turn sessions simultaneously and the capacity will
increase by roughly 30 Turn session by additional vcpu provided up to a maximum of 300 turn
session. The Turn server application reaches a performance ceiling once 10Vcpu are provided.
Http Tunneling through Proxy SSL inspection mode [8.0]

To support the deployment of complex Equinox solutions leveraging the Equinox Web client
(WebRTC based), the Http tunneling feature was provided in prior ASBCE version to facilitate
the crossing of remote network edge(s).
However, in certain scenario, when an intermediate proxy gets involved, the certificates carried
with the message were getting changed, causing the ASBCE to fail and discard the message.
With Release 8.0, the Fingerprints parameters are also sent in the message itself (in band) to
allow the ASBCE to validate the message despite change in certificates that intermediate
proxy(ies) may have caused.
Opening Up the SBCE architecture to ecosystem

ASBCE has traditionally been a closed system with minimal interfaces to allow integration with
external trusted systems.
Starting with Release 8.0, ASBCE is exposing new interfaces to deliver added value
integrations to the ASBCE customers:
- Routing Engine with LDAP data dip

- Help with automatic and free access to Avaya Learning

As the product evolves throughout the Release 8.0, additional interfaces and API will be
exposed
Allowing ASBCE core routing decision engine connection to external data

set (LDAP) [8.0]
In an environment where the ASBCE is front ending more than one SIP call server (Aura and
Lync for instance), this feature allows the ASBCE to query an external database to understand
where the call should be routed toward based on the called number and on a per call basis.
Based on the information it will collect for each call, the ASBCE will therefore be able to:
Always route the call to Call Server #1 then fall back to Call back Server #2 on no
answer or Vice versa
On Call Server #1 if user is identified in LDAP as being on Call Server #1, on Call Server
#2 if user is identified as being on Call Server #2
Only sequential routing (i.e. no call forking ) is supported
Linking SBCE Help to Avaya learning Administrator training [8.0]

Now when accessing the online help of the ASBCE 8.0 and thru the online help interface of the
system, SBCE administrator will be granted access, free of charge, to the administrator training
available online from Avaya Learning.
Technology Currency & Security
Avaya Security Common Engineering Criteria compliance

Continuous security improvements have been included in Release 8.0 of ASBCE to ensure
adherence to Avaya security best practices. These common engineering criteria are following
very closely the Security Technical Implementation Guidelines (STIGs) as defined by the US
Department of Defense.
These covers weakness remediations, best practices configurations and hardening in the area
of :
- Authentication, Authorization and Single Sign-on
- Trust and Cert Management
- Encryption
- DoS, Firewall, and Malware Protection
- Operating System Hardening
- Web Security and Input Validation
Details about the actual implementations, fixes and hardening are available In the SBCE 8.0
release notes
Remote Workers MAC based authentication [8.0]

This feature introduced with Release 8.0 of ASBCE allows the system to use LDAP to
authenticate Avaya hardware endpoints based on the MAC address information included in the
SIP REGISTER messages sent by these devices. (+sip.instance parameter of Contact header)

ASBCE will query the LDAP server upon reception of such message to confirm that this MAC
address is indeed a valid address present in the LDAP server. The SBCE will not process the
SIP REGISER message further until successful authentication of the endpoint.
This authentication can be used in conjunction or instead of the existing MTLS authentication in
the ASBCE.
This feature is only supported with and by the Avaya Hardware endpoints ( 96x1 and J1XX
series)
Platform support
Support for vSphere 6.7 [8.0]
ASBCE Release 8.0 OVA can now be deployed on ESXi 6.7/vSphere 6.7 fixing a previous
incompatibility of the OVF file format preventing vSphere/VCenter from deploying the OVA
successfully into the VMWare environment.
ACP Hardware appliances [8.0]

ASBCE Release 8.0 is the first ASBCE release to support the ACP 110 Profile 3 and ACP 110
Profile 5 hardware appliances.
Security Comparison
The following table highlights some of differences in implementing IP Office with and without the
Avaya SBCE.
Feature IP Office Avaya SBCE

DoS Protection Limited Advanced
Topology Hiding Limited RFC 5853
NAT Traversal Supported RFC 5853
SIP Normalization Limited RFC 5853 & Advanced (SigMa Scripting)
Call Walking None Advanced
Toll Fraud Basic Advanced
Business Partner Value Proposition

Market Needs, Trends and Growth
Enterprise ASBCEs are gaining acceptance worldwide and the market is growing.
They are used as a border element on the enterprise premise to protect the
enterprise network from intrusions via the service provider network, handle NAT
and firewall traversal, and for interworking between different VoIP protocols, if
necessary. The ASBCE market is predominantly driven by medium and large
enterprises deploying SIP trunking services as a way of consolidating, centralizing,
and increasing the utilization of their trunking infrastructure.
A secondary driver of the enterprise ASBCE market is interconnection between
disparate systems, such as PBXs and UC, video telepresence systems, and
contact center platforms. In this scenario, the ASBCE is primarily handling
interworking between different VoIP protocols, or different vendor implementation of
standards. Mergers and acquisitions are directly driving the need to interoperate
between different manufacturers PBXs, as companies are trying to integrate

operations post-merger/acquisition. Perhaps not surprisingly, the financial sector

has been often cited as the top vertical—they are the perfect storm of
mergers/acquisitions, size, and large number of distributed sites.
A third driver is mobility services. With the explosion in remote employees and
cloud services and waning of Layer 3 (IP layer) VPNs, the demand for ASBCEs is
steadily increasing. Specialized VPN systems are far less needed.
Though enterprise ASBCEs hit the market in 2008, they are mainstream items in
developed markets that have healthy SIP trunking availability. In 3Q17, revenue
was $122.5M, up 26% YoY from 3Q16, and 5.6M sessions shipped, up 28% YoY.
Average revenue per session was $22, down 2% from 3Q16.
ASBCEs are impacted by the growth in SIP trunking and the migration of
businesses to IP PBXs and UC. The number-one pull for ASBCEs is SIP trunking.
In our July 2017 SIP Trunking and ASBCE Strategies North American Enterprise
Survey, the top reasons respondents have not deployed SIP trunking are security
concerns, existing service contracts not being up for renewal, and satisfaction with
existing voice services. If there are no measurable or perceived benefits — cost or
other — businesses will stick with what they have.
IHS Markit expects the enterprise ASBCE market to grow over the coming years.
Average annual revenue growth between CY16 and CY21 is 6% with CY21
revenue reaching $503M. Session growth has an 11% CAGR, growing to 26M
sessions in CY21.
In 3Q17, systems in the <151 sessions range made up 23% of all system sales,
and systems in the 151-800 range made up 31%. The SBCs in the 151-800 range
are predominantly targeted at medium enterprises and often give businesses the
chance to grow capacity as their SIP trunking requirements expand. The smaller
capacity devices (with fewer than 151 sessions) are used mainly by businesses in

the 100-500 employee range and remote offices of larger enterprises in addition
to hosted environments. Though larger enterprises are using SIP trunking, large
scale SBCs (with greater than 5,000 session capacity) have been predominantly
sold into carriers. In 3Q17, sales in the >5,000 sessions range increased 19%
YoY, making up 4% of total shipments. Even though ASBCE can range up easily
into this capacity, the carrier market segment is not a market that Avaya is
targeting at this stage.
Value Proposition
It is important to note that the ASBCE should always be recommended for any
Avaya SIP-based Unified Communications implementations and should be part of
almost every Avaya or 3rd parties (see 3rd party call server support in this document)
UC/CC sale proposal, as a general best practice for secure implementation. The
only justified exception would be if the customer already had as a corporate
ASBCE and/or does not require any VPN-less Avaya remote user.
Avaya SBCE Midmarket Use Cases

The Midmarket offers based around the Avaya IP Office platforms leverage the same Avaya
SBCE software load as in the Enterprise offer. While the software load is the same, key
differences in the offers are driven by applicability of features to the Midmarket and cross-BU
testing for delivery support.
ASBCE release 8.0 solutions provide a unique and powerful edge control solution to business
customers with IP Office. A range of use cases for this GA introduction of Avaya ASBCE 8.0
include
 SIP trunking to Carrier networks and IP Office.
o SIP trunking to Carrier networks from IP Office 8.1 (and higher). The SME customer
is evolving from TDM trunking to SIP trunking to carriers/PSTN, and this use
continues as fully supported in this latest release of the ASBCE software.
o ASBCE features for VLAN, Load Balancing, Geo-redundant HA, and multiple
interfaces/subnets all expand the breadth of this use case and are covered in the
Standard Services license.
 Remote Workers in a VPN-less environment. As Mobility, BYOD, and the applications and
services to mobile users evolve, a newer and more flexible implementation of access to SIP-
based UC is available via the Avaya ASBCE. The remote user/device can be authenticated
at the ASBCE without requiring the use of VPN to secure the access to the Aura core for
Enterprise customers.
o ABSCE capabilities for increased next-hop servers improves flexibility for
deployment and management of Remote Worker
o Introduced as of release 7.2, ASBCE now supports IPv6 for Remote Worker. This is
covered within the Standard Service license.
o Even though not absolutely required, ASBCE deployment should be considered for
security best practices and to enable advanced functionalities for JXX devices for
Mid-market on premise deployment with IPO.
o For any hosted IPO deployments, due to the exposure of the system to the public
internet, Avaya strongly recommends to front end the solution with an ASBCE.
 Scopia SIP clients as Remote Workers – The Scopia SIP XT family of video clients are
supported as VPN-less SIP Remote Workers when accessing the Scopia MCU for Scopia
video conferencing.

o Scopia Video license type, Video sessions, will specifically support the Scopia SIP
clients. This license is required for Scopia video, not ad hoc point-to-point video
calls from a client that supports it.
o The feature supports BFCP (Binary Flow Control Protocol) allowing the Scopia
features of video conferencing to be controlled through the ASBCE in this Remote
Worker scenario. The feature also supports FECC (Far End Camera Control) via
ASBCE
Product Specifications
Compatibility with Avaya Solutions
A key value of the Avaya Session Border Controller is that it is the only ‘solution-stack’ tested
product in the market for Avaya Unified Communications solutions. This is driven by Avaya’s
cross-Business Unit and Solution Interoperability testing efforts and delivers a high level of
compatibility across all the elements of the solution both for SIP trunking and VPN-less Remote
Worker.
The interoperability matrix available on the Avaya support site should be consulted for the latest
up to date compatibilities between ASBCE R8.0 and any other Avaya solutions.
Please visit https://secureservices.avaya.com/compatibility-matrix/menus/product.xhtml
Avaya Call Servers

For any interoperability questions between ASBCE and Avaya Call server, the interoperability
matrix is the reference (see above )
In regard to ASBCE direct SIP connection to Communication Manager, with the introduction of
Session Manager in R6.x of Aura, best practices have evolved and now require the Session
Manager to always be inserted between Communication Manager and ASBCE for SIP trunking.
Consequently, no further testing effort have been invested by Avaya in qualifying direct SIP
trunking between CM and ASBCE since 6.3 and therefore such setup is any longer guaranteed
as functional from ASBCE 7.x.
Avaya Endpoints
Hardware Endpoints
Avaya J129 has been supported by ASBCE as of Release 7.2 and is also supported by 3 rd party
SBC as remote worker.
Avaya J179/J169/J139 feature phones support SIP Stimulus signaling through ‘CCMS over SIP’
proprietary protocol and it is a ‘Single Connect' protocol. This protocol involves the registration
with the IP Office and the establishment of a signaling(control) channel between the phone and
IP Office (SIP call leg). This signaling connection will remain established while the phone is
registered and is only torn down under error conditions or when the phone gets unregistered.
Since ASBCE 7.2.2, special handling has been added in the ASBCE software to recognize and
make the J179/J169/J139 feature phones work as ASBCE remote workers. ASBCE treats
J179/J169/J139 phones different when compared with other standard SIP phones.
The following features are supported by ASBCE as of Release 7.2.2:
 ASBCE keeps the fixed public to private media association on the RTP port that is
advertised by Avaya J179/J169/J139 phone in CCMS Interface SIP Dialog
 ASBCE supports the SRTP key negotiation in CCMS Interface SIP Dialog
 ASBCE supports CCMS Interface SIP dialog keep-alive mechanism and IP Office link
lost detection

Note: with respect to 3rd party SBC (re non-Avaya SBC) and usage with J179/169/139 series
phone, one can expect the following issues to occur since no testing or integration verification
has been performed by Avaya between these phones and the SBCs:
 Speech path issue - IP Office does not expect the J179/J169/J139 phone to change the
port once the CCMS Interface call is established. It is quite possible that 3 rd party SBC
may change the port post the initial handshake. If the 3 rd party SBC changes the port,
IP office will not consider this change causing speech path issue.
 3rd party SBC may tear down the control channel. This is when phone is in idle and no
media flows even though SIP call (control channel) is established. This will cause
communication drops
 IP Office uses K-line along with a=crypto for SRTP key negotiation. 3rd party SBC may
omit the K-line from SDP and therefore causing the encrypted message attempt to fail.
 Lack of detection of IP Office link failure between 3rd party SBC and IP Office
preventing proper and seamless failover(s)
Software Endpoints
Like the prior version, ASBCE R8.0 supports remote worker use case with any of the Equinox
client version (all desktop and all mobile variants) starting from version 3.0. At the time of
publication of this document, ASBCE 8.0 has been tested successfully against Equinox Clients
version 3.4, Version 3.4.4, 3.4.8 and 3.5.5.
In an Equinox client remote worker situation where the call server is based on Avaya Aura,
ASBCE is not a required component of the solution due to the advanced signaling leveraged by
Equinox client but is the only SBC that supports this use case with full functionalities due to
Avaya proprietary implementations of PPM and advanced SIP extensions in AST-II.
In an Equinox client remote worker situation where the call server is based on IP Office, a
session border controller is not an absolutely required component of the solution since the IP
Office provides native NAT traversal capabilities. However, if one considers including a session
border controller as part of this solution implementation as part of security best practices, the
only SBC solution tested and officially supported by Avaya is ASBCE.
Interoperability with 3rd Parties

Due to its open implementation and rich feature set, ASBCE Release 8.0 can also be deployed
and implemented with non-Avaya based solutions: Call servers such as Cisco Call Manager or
Microsoft Lync, and/or Internet Telephony Service Providers. The following sections describes
the interoperability that have been tested, confirmed by Avaya or a 3 rd party and certified in
some situations.
3rd parties Call Server

The following table shows tested interoperability for 3rd Party Call Servers
Call Server Release ( 3rd Party Call Servers ) ASBCE R8.0 tested successfully against Call server
Cisco R8.x and R9.x Yes
Microsoft Lync 2010 and 2013 Last tested with SBCE R6.3
SfB 2015 Yes
ShoreTel R3.9.5 Last tested with SBCE R6.2.1
Mitel 330 R6.0 Last tested with SBCE R6.2.1
Asterisk R1.8+ Yes

For more details on the SBCE interoperability with SfB, please refer to the following application
note:
https://support.avaya.com/css/P8/documents/101041738
More information about Skype for Business certification can be found on the Microsoft web site
under:
https://technet.microsoft.com/en-us/office/dn947483.aspx indicating SfB2015 compliance of
ASBCE thru compliance with prior Lync Version.
and
https://technet.microsoft.com/en-us/office/dn788945 capturing ASBCE compliance with Lync
2013.
Internet Telephony Server Providers

To provide customers and partners with the best experience during SIP trunking implementation
and the operation of the service against Avaya Call server (Aura or IPO) and ASBCE, Avaya
provides Internet Telephony Service Providers (ITSP) with the option to certify their SIP trunk
offering thru Avaya DevConnect Program SIP interoperability testing.
This program ensures and guarantees, thru an end to end thorough testing, that the certified
ITSP trunking & DevConnect documented configuration will properly interoperate with the
ASBCE and the respective Avaya call server(s).
As part of the testing, the Avaya DevConnect team will identify any interoperability challenges,
remediate them thru ASBCE configuration, or ITSP trunk setup adjustment and deliver
interoperability and ASBCE configuration documentation, ready to be leveraged by Avaya
Customers or Partners.
For SIP trunking provider selection, it is therefore highly recommended that any
partner/customer considering SIP trunking implementation against their Avaya Call server to
consult the list of certified ISTPs on the DevConnect web site.
The list of currently certified ITSP and the associated application notes can be found under:
https://www.devconnectmarketplace.com/marketplace/search?categories=34&tags=118
ASBCE is also interoperable with Skype for Business. For more details, please refer to the
following application note:
https://support.avaya.com/css/P8/documents/101041738
More information about Skype for Business certification can be found on the Microsoft web site
under:
https://technet.microsoft.com/en-us/office/dn947483.aspx
and
https://technet.microsoft.com/en-us/office/dn788945
SIPconnect
Since Release 7.2, ASBCE is SIPconnect certified. For more information, visit SIP Forum.
3rd parties SIP endpoints

When used in combination with Avaya applications, ASBCE does not support 3rd parties SIP
endpoints unless validated by other Avaya offers or applications.
Avaya SBCE Components
Licenses and Examples
License Structure
The ASBCE is extremely rich in term of functionalities and offers several tiers of feature
functionality controlled by software licensing and enforced by WebLM.
For both enterprise and Mid-Market, the basic licensing options are structured identically and in
an incremental manner starting from the standard license to the High Availability license.
Other licenses offered by the ASBCE solution, which will be identified in this document as a la
carte licenses, do not follow this incremental behavior. (See license descriptions below)
Some of the a la carte licenses such as Transcoding or Scopia are not available on the Portwell
appliance- Refer to the quick reference capacity table for availability of licenses on the Portwell
appliance.
The incremental behavior can be best described as follow: If one seeks to offer any of the
functionality covered by the Advanced Services license then a standard license AND an
advanced license will need to be ordered.
In the same way if a customer seeks to gain access to the High Availability function of the
ASBCE, besides ordering an additional hardware appliance (or obtaining an additional Vapp
license), the customer will need to order a High availability license for each standard license and
advanced license associated with the appliance.
The following diagram represents the incremental structure of Standard, Advanced, and High
availability licenses
To further describe this, the following examples illustrate concretely what has been described
above:
Example 1:

A customer is purchasing an ASBCE for which it requires support for up to 50 SIP trunks
and 100 Remote users. The licensing required would then be 50 Standard for the SIP
trunks, plus 100 Standard AND a 100 advanced for the Remote users feature for a total
of 150 standard and 100 advanced.
Example 2:
If the same customer above decided to increase the reliability of its system and remove
the single point of failure, it would then need to acquire a second appliance or deploy a
second Virtual Appliance (with the associated Vapp license) but also acquire 150
Standard High Availability licenses to cover the 150 standard licenses and 100
Advanced High Availability licenses to cover the 100 advanced licenses.
Standard License
Standard Services deliver all the features necessary for the security machinery – this is the
most basic option of the ASCBE and at least one of such licenses is required for the ASBCE to
deliver any function.
The functionalities covered in a standard license are:
 EMS: Element Management system
 Standard VOIP security: toll fraud, Call walking
 Standard SIP trunk – 1 session
 Deep Packet Inspection
 DoS/DDoS (flood, Resource Hang/open transaction, Crash/Fuzz)
 ACL/White/Black listing
 SIP Normalization – ITSP integration
 Call Admission & Control
 DTMF manipulation
 Network Address Traversal(NAT)
 Load Balancing
 ENUM Routing support
 IPV6 (dual stack with IPV4) support
 Multi-tenancy
 Media Anchoring
 VLAN Routing
Advanced License
Advanced services deliver unique features that work in addition to the Standard Services
functionalities.
Access to the following features will require an Advanced license:
 Remote Worker – 1 session
 Encryption service- 1 session
 SIP TLS
 SRTP
 Media Replication
 Media forking to recording devices – SIPREC

 UCID generation
 SIP one-X Agent support (for CCaaS only)
 STUN/TURN functionality for WebRTC support.
 Reverse Proxy
High Availability License

A High Availability license is required for each standard license or advanced license in one
given appliance to enable proper licensing for a High Availability pair.
Dynamic License
Introduced with 7.2.0, Dynamic License enables be shared across ASBCEs. Session licenses
that are in use will be tracked and unused session licenses will be released back to the
shareable pool of licenses in WebLM. The number of dynamic licenses purchased must be the
same as the number of Standard licenses. However, once purchased, all the license types
(Standard, Advanced, Transcoding, and Scopia) become dynamic.
Dynamic licensing redistributes the licenses based on the traffic. Unlike with Static licensing,
there is no manual intervention required. For the dynamic licensing one will have to configure
the following only once:
 Low water mark: If number of free/unused licenses (which are already acquired) is below
low water mark then it will trigger SBC to fetch/acquire additional license in the increment
of fetch count from WebLM server.
 High water mark - If number of free/unused licenses (which are already acquired) is
above high-water mark then it will trigger SBC to release licenses in the increment of
fetch count back to WebLM server.
 Fetch count – incremental number of Licenses acquired or released
Example: Low Watermark is set at 20, High Watermark is set at100, and fetch count set as
50.
If SBC is having 500 licenses acquired and 480 used then, next session will trigger acquiring
50 more licenses (new acquired count will be 550 of which 69 will be free). Similarly, if SBC
is having 500 licenses acquired and go from 401 to 400 will trigger release 50 licenses (new
acquired count will be 450 of which 51 will be free).and so on with no limit on number of total
acquired licenses per SBC (as long as this value does not exceed the grand total number
available in WebLM).
Once this configuration is done, actual allocation is dynamic based on the traffic.
Notes: The ASBCE will not block any traffic if it fails to acquire license for the session, but
generates an incident notification (Alarm message in log).
 Since this is not a typical midmarket feature, The SBCE IP Office material codes do not
support Dynamic Licensing. SEs with Midmarket customers requiring Dynamic Licensing
would need to contact SBCE Product Management.
Additional License (“a la carte” licenses)

The following licenses are not required for basic ASBCE functions, can be ordered
independently, and each will have a different behavior & requirements regarding the need of
underlying standard and advanced licenses.
Some of these licenses will control an appliance wide characteristic / function (encryption, virtual
appliance) – some are specific for feature activation and are per session.

Client Enablement Service (CES) Inspection license

This license continues for release 8.0 providing enhanced security for Remote Workers using
the Avaya Communicator and Avaya Equinox family of Mobile clients. One such license is
required per concurrent active Avaya Mobile clients (Avaya Communicator or Avaya Equinox)
when CES setting is enabled on the mobile client.
Example 1: if a customer wants 10 SIP trunk calls and enable up to 10 mobile clients to use
the CES feature concurrently, then 10 standard licenses and 10 CES licenses are required.
Note: This license is only for Avaya Aura deployments.
Transcoding license
Transcoding will address unique requirements for subsets of trunk traffic going to, say, a 3rd
party application that has a fixed unique requirement for a different codec. Also includes the
Trans-rating feature.
This is a per session license i.e. one Transcoding license is consumed / needed by the ASBCE
for each session leveraging the transcoding or trans-rating feature (whether using the internal or
external AAMS)
Note: Since this is not a typical midmarket feature, The SBCE IP Office material codes do
not support Transcoding License. SEs with Midmarket customers requiring Transcoding
would need to contact SBCE Product Management.
Encryption license
This license is an ‘On/Off’ system level license that allows Encryption services to be provisioned
in support of the Remote Worker functionality. It encrypts both signaling and media. It is not
available in countries that don’t allow encryption in products.
This license is not available for Russia, Belarus, and Kazakhstan.
One such license is required per each appliance requiring encryption and will allow the
advanced licensed session on this appliance to deliver media + signaling encryption when
required.
This is a zero-dollar license.
Signaling only Encryption license

Introduced in conjunction with the Encryption license, the Signaling Only Encryption License is
the only encryption license allowed for Russia, Belarus, and Kazakhstan where media
encryption is prohibited by law.
One such license is required per each appliance requiring encryption and will allow the
advanced licensed session on this appliance to deliver signaling only encryption when required.
This is a zero-dollar license
Scopia Video Service license

This license is to support Scopia SIP clients in Scopia reserved conferencing application.
One such license is required for every Video call performed by the Scopia XT device (Video
conference room hardware) you want the ASBCE to support.
This Scopia Video Service license is incremental to Standard and Advanced. Licenses, meaning
that for a complete and functional licensing supporting a set number of Scopia Video call, you

will need the exact same set number of standard and advanced licenses as you have Scopia
Video Service licenses.
Example: if a customer wants to support 10 concurrent Scopia XT device video calls thru its
ASBCE then 10 Standard +10 Advanced +10 Scopia Video service licenses are required.
VMW deployment license

This is the first Virtual appliance license which was introduced for the ASBCE, this per appliance
license grants its owner the right to deploy one instance of the Virtual appliance in a VMWare
based environment.
KVM deployment license

Introduced as of ASBCE release 7.2, this is a per appliance license granting its owner the right
to deploy one instance of the Virtual appliance in a KVM based environment (inclusive of
Nutanix Acropolis or AHV)
AWS deployment license

Introduced as of ASBCE release 7.2, this is a per appliance license granting its owner the right
to deploy one instance of the Virtual appliance in Amazon Web Services (AWS) environment.
Avaya SBCE and IP Office

Avaya ASBCE 8.0 supports continuing alignment with IP Office for the SME and Mid-Market
opportunity. Avaya ASBCE software is essentially “call-server agnostic”. The good news is that
a single software product (ASBCE) can support both Enterprise and Mid-market
implementations. Key to the offer becomes understanding what is jointly tested and
implemented across the Call Server offers as relates to ASBCE features and functions.
 The software product is identical to the Enterprise offering, including both Standard
Services for SIP trunking (IPO 9.1 and higher), and Advanced Services for Remote
Worker and Encryption services (IPO 9.1 and higher). Support for ASBCE 8.0 features
is a function of cross-BU alignment for needs and testing in the Mid-market space.
Implementations with IP Office typically leverage primarily the Standard and Advanced
services and licensing.
 The Video Services supporting Scopia SIP clients as ‘Remote Worker’ is supported for
the IP Office suite as IP Office supports the Scopia SIP clients for the service.
 Software licensing and hardware part codes are specific to SME to align with IPOSS
service offers.
 Server platforms for ASBCE 8.0 are, at present, the Small, Mid-range and Virtual
platforms used in Enterprise, but uniquely identified and ordered with codes aligned to
IPOSS Maintenance offers.

Product Structure
The structure of the offer for IP Office is shown below:
Notes: Management of the SBCE is done through EMS (element management system). For
single availability deployments the core SBCE application and the EMS application can be
run on a single server; high availability deployments require three servers.
- A high availability deployment can include a mix of appliances and virtual servers as long
as the two core servers are the same model (two Dell R330 or two HP DL360G9 servers)
- HP G9 model will ship while stock lasts, after which the Dell R330 will remain
the only hardware appliance shipping for Mid-range offer for SME segment
Media and Licensing Order Codes

Aligned and essentially like Enterprise, Avaya Session Border Controller for Enterprise 8.0 for IP
Office is a single software product that can serve many applications needs for SIP-based
communications in the SME market. The software is delivered, with our Business Partners in
mind, preloaded on the hardware platform, on a DVD or Thumb Drive for physical media, and,
aligning with other Avaya applications, via PLDS.
There are also ‘hardware’ codes for the Media Kits, a DVD for servers with drives, and a thumb
drive for Portwell servers. Media Kits are evolving for ASBCE 8.0 at GA. As platforms evolve,
the newer platforms have DVD drives, and can use a DVD media Kit instead of, or in place of
the thumb drive used in earlier releases. The thumb drive for release 8.0 is specifically required
for Portwell platforms, and can be used for the newer platforms also.
ASBCE Rls 8.x Media Kits
700514240 ASBCE R8.X SYS SFTW USB
700514239 ASBCE R8.X SYS SFTW DVD

Material codes for Media Kits are the same for Enterprise and Mid-Market/SME.
The following table captures the different license material codes making up the basic
incremental licensing structure of the ASBCE, with their description.
Standard Availability High Availability

LICENSE DESCRIPTION LICENSES DESCRIPTION
Standard
397232 ASBCE R8 STD SVCS IPO LIC 397242 ASBCE R8 STD SVCS HA IPO LIC
LICENSE DESCRIPTION LICENSES DESCRIPTION

Advanced
397237 ASBCE R8 ADV SVCS IPO LIC 397247 ASBCE R8 ADV SVCS HA IPO LIC
The following table describes the a la carte licenses material codes available.
These are per session licenses
LICENSES Material code DESCRIPTION
397252 ASBCE R8 SCOPIA VIDEO CONF IPO LIC
397255 ASBCE R8 SCOPIA VIDEO HA IPO LIC
The following are per appliance or per system licenses

397216 ASBCE R8 ELEMENT MGR LIC
397217 ASBCE R8 HA LIC
397261 ASBCE R8 ENCRYPTION FOR IPO LIC
397271 ASBCE R8 SIGNAL ONLY ENCRYPTION FOR IPO LIC
Virtual Appliance Order Codes

ASBCE 8.0 can be deployed as a virtual machine within a VMware, KVM, or Nutanix AHV
environment. Either the entire ASBCE (EMS + core) or just the EMS can be deployed as a
virtual machine.
Licensing and licensing models are the same for Virtual implementations as in appliance-
oriented models.
Virtual implementation is supported in both Enterprise and Mid-market
The following tables list the different virtual appliances licenses related to the type of environment
you/your customer are/is considering deploying into
VMware Order code

397258 ASBCE R8 VE VAPP IPO FILES LIC

AWS Order Code

398472 ASBCE R8 AWS AMI ENABLE IPO LIC
KVM (Nutanix AHV) Order Code

This is also covering a Nutanix AHV deployment
398473 ASBCE R8 KVM ENABLE IPO LIC
Hardware Appliances Order Codes

Avaya Session Border Controller for Enterprise is a software product that is also supported on
its specific hardware platforms that are engineered to cost-effectively deliver the software
services at a rated capacity for scaling purposes.
The ASBCE 8.0 hardware materials required for supporting the product can be ordered
separately by Distributor Partners, or, in configurations generated by the configuration tools
Hardware ordering codes for Mid-market/IP Office are different due to requirements that they
align with IPOSS. Platforms supporting Small site and Mid-range capacities (up to 6000
sessions) are orderable for IP Office/IPOSS implementation.
ASBCE SME/IPO Hardware Codes

Part Codes DESCRIPTION
388053 ASBCE CORE PORTWELL CAD-0230 IPO
388049 R330 MID RANGE SRVR IPO ASBCE
Portwell Power Supply can be ordered separately (700513204)
System Engineering Consideration

Prerequisites
ASBCE release 8.0 is a Unified Communication & network security appliance specifically used
to secure SIP-based VoIP and Unified Communications. There are many use cases defined in
this document, and prerequisites deal with the network environment:
 LAN connectivity to the customer’s environment, switching, etc. are assumed to be
available and in place.
 Call Servers should be at the appropriate supported release to support SIP connectivity.
Supported release levels for Avaya Call Servers are detailed in a section below.
 Carrier facilities for SIP trunk implementations are assumed to be ready for SIP
connectivity to the ASBCE with appropriate LAN connectivity.
 SSL VPN connectivity and registration is assumed for IP Office implementation.

Network Rules
This offer of ASBCE 8.0 delivers Standard, Advanced, Transcoding and Scopia Video features
for the SME/IP Office customer. At a high level, following is the Sales Engineer’s required
‘thinking’ steps for ASBCE 8.0:
 Determine the access point in the customer’s network for physical location and service
access
 Engage with customer to identify if physical or virtual appliance is to be considered
(customer’s IT may have specific requirements). If virtual appliance, what virtualization
platform the customer would like to leverage. If physical, identify the growth requirements
to select the right hardware models
 Determine which services are required (i.e. SIP trunking, Remote Worker, etc.). An order
for a system consists of determining the number of sessions that are required and
choosing the appropriate hardware platforms to support the need.
 Know your traffic requirements. The Standard Services features and the Advanced
Services features are licensed on a per session basis, and usage/traffic requirements
drive the number of sessions needed for a system. Refer to the quick capacity guide in
this document
 Select the redundancy options (None, HA pair, Geo-redundancy, HA+GR) and
Encryption.
The Sales Engineer also needs to remember some key product-oriented rules:
 High Availability (HA) is only offered on the Dell and HP platforms, and in Virtualized
mode, not the Portwell platform. The HA configuration does not double the rated capacity
of the system.
 When Advanced Services, such as Remote Worker, are required, every Advanced
Service license requires a Standard Service license with it (see license section of this
document for more details). This is because the Remote Worker is leveraging the ‘full’
ASBCE software engine for every communications session.
 Encryption Services (whether media+ sig or sig only), leveraged by the Advanced
Services feature group, impact the total session capacity of the hardware configuration
(see quick capacity reference included in this document). Encryption Services are
strongly recommended for Remote Worker implementations – select the type of
encryption relevant to the final country of destination.
 ASBCE 8.0 can be deployed as a ‘mixed use’ appliance, for example serving needs for
SIP Trunking, Remote Worker and Video (Scopia Video, Scopia SIP clients) from the
same appliance configuration, but extra care must be taken to not exceed the capacity of
the configuration. Best practices for easier management of traffic, licensing and
troubleshooting are recommending separation of the SIP trunks and remote workers
traffic on separate SBCEs
Note: In the absence of a mixed-use dimensioning tool, Engagement with ATAC for such
complex dimensioning is highly recommended
The note above to ‘Know your traffic requirements’ is a key to successfully deploying ASBCE
8.0. The following licensing examples incorporate a “rule-of-thumb” estimation for active
trunking and remote worker sessions. The Avaya SBCE is a single software application driven
by different licensing types.
Example 1: A customer is implementing SIP trunking to replace TDM trunking for a
location with 150 general population users. Using the general ‘rule of thumb’ of a 5:1
user to trunk ratio, 30 simultaneous sessions are required. This requires 30 Standard
Services licenses and a Portwell server, since it can serve up to 600 Standard Service
sessions. But if the customer is likely to want HA an HP or Dell would be selected. The
choice of platform should be driven by customer desires.

Note: Mobile users require 2 SIP trunks to connect an external call to a mobile user.
Example 2: A customer desires to serve a population of 50 remote and mobile users in
a non-VPN environment. These users have varying needs for connection to services,
none are Contact Center agents. While the general rule of thumb for external SIP
trunking is 5:1, that applies to the average external calls a user makes. As Remote
Workers use services for both internal and external calls, their requirement is double the
standard external calling number. The general ‘rule of thumb’ for Remote Workers (NOT
as Contact Center agents) is 2.5-3:1. This drives a requirement for 17-20 Advanced
Services licenses and 17-20 Standard Services licenses (as every Advanced Service
license requires a Standard Service license). Also remember that using the Encryption
Service (part of the Advanced Service license) reduces the capacity of the hardware.
Since the Portwell server supports 500 encrypted sessions can easily be used; the Dell
or HP server might be recommended if the customer is thinking about HA or significant
future expansion.
Note: Telecommuters who work from home have higher activity and may need a 1:1
Remote Worker-to-session ratio. A contact center agent might have an even greater
ratio as they often have queued calls.
Example 3: A site with 250 users, containing a sub-population of 25 Remote Workers
wants to implement a mixed-use ASBCE 8.0. For the general population of 225, 45
Standard Services sessions are required at the 5:1 ‘rule of thumb’. For the 25 Remote
Workers using a 2.5: 1 ratio, the requirement is 10 Advanced Service licenses + 10
Standard Service licenses (as every Advanced Service license requires a Standard
Service license). The system totals are 55 Standard Service licenses and 10 Advanced
Service licenses. As we are running Remote Worker in the appliance, Encryption
services should be invoked, and the required total simultaneous sessions for this system
are 55. Assuming the customer does not want HA, a Portwell server can be used (with
encryption the Portwell supports 500 sessions).
Example 4: A customer wants to use an ASBCE 8.0 system to support Scopia Video
Conferencing. The customer needs 250 simultaneous sessions to meet his needs. The
maximum capacity of the Dell and HP platforms is 200 simultaneous sessions for Scopia
Video Conferencing support. This case will require two ASBCE 8.0 systems, either on
Dell or HP Mid-range platforms, and, unless other factors apply, the recommendation
would be to split the load evenly across the two systems. The Hi- capacity servers (not
available with IPOSS) will handle the traffic within one system.
Example 5: The customer in example 1 above wants to have High Availability for their
SIP trunking. To support this, the licensing would be 30 Standard Services licenses and
30 Standard Services HA licenses. Since the Portwell does not support HA, three Dell
R330 servers would be used.
Example 6: The customer in example 2 above wants to have High Availability for their
Remote Workers To support this, the licensing would be 17-20 Standard Services
licenses, 17-20 Advanced Services licenses, 17-20 Standard Services HA licenses, and
17-20 Advanced Services HA licenses. Since the Portwell does not support HA, three
Dell R330 servers would be used.
These provisioning considerations and engineering rules apply to both the Enterprise and the
Mid-market or IP Office as ASBCE is a single software product. The key extra consideration for
IP Office becomes the support for simultaneous SIP sessions supportable on the IP Office
platform.
Network Design & Best practices

ASBCE is a SIP/UC security device that protects the UC network at the edge. Avaya
recommends that the ASBCE be placed behind the network firewall, in a DMZ, for good security
practice in a layered defense strategy. This does not mean that ASBCE 8.0 cannot work when
in parallel to the Enterprise firewall, but, security best practices promote a layered defense
strategy, hence the recommendation that ASBCE 8.0 is behind the enterprise firewall.

The following topology illustrates the best practice deployment for SMB.
IP networking at the switch level needs to be planned per the ASBCE “Installing the Avaya
Session Border Controller” document for the product. The customer building the IP network that
supports ASBCE 8.0 should consider the following:
 IP networking for the ASBCE
 Remote access to the system via SSL VPN for IP Office implementations
 An ASBCE, in general, is implemented at the edge of the network where external access
is controlled. In larger multi-site networks, placement for the ASBCE and SIP trunk
access need to be considered
ASBCE 8.0 for IP Office (aligned with IPO 11 and supported on earlier releases) will leverage
the IP Office approach to remote Services access via SSL VPN. SSL VPN access is required
for Avaya Services to be able to troubleshoot and support the solution.
ASBCE 8.0 is ordered for a site that is connecting to Service Provider for SIP trunking. In a
multi-site implementation where SIP trunks are provisioned at one of the sites, the ASBCE 8.0 is
attached to that one site. If SIP trunks are provisioned at multiple sites, then an ASBCE 8.0
instance is generally required at each site using SIP trunks. Remember to select the ITSPs as
per the guidance and recommendations provided in this documentation.
Misc. Engineering Tips

A Single EMS can support up to twelve (12) HA ASBCE instances, or 24 single (non-HA)
ASBCE instances. Note that this type of configuration forces many settings to be identical for all
the HA pairs controlled by the single EMS, and has implications for Upgrades.
The main function of an ASBCE being one of a security appliance, it is of the utmost importance
to always keep the appliance up to date from a software point of view. Out of date ASBCE
software puts your networks/your customers at higher risk of security breaches.
A group of ASBCE whose licenses are managed by the same WebLM/SMGR server must all be
running the same level of major release as WebLM does not support licenses at different
release level for the same product. This also implies that a group of ASBCE upgrading from an
n-1 release (where n is major), must upgrade all at once to the same n release level.

Note: WebLM does not make the release level distinction for minor or Feature pack
Specific Engineering Rules for Mid-Market deployments

If SIP trunking is the chosen external Service Provider access for the customer’s IP Office
system, the customer needs the ASBCE 8.0 to insure a secure SIP/UC implementation. The
number of IP Office SIP trunks is equal to the number of ASBCE Standard Services licenses
that are to be ordered.
IP Office as of release 9.x supports Remote Worker with SIP clients but since IP Office offers
NAT traversal capabilities natively, a session border controller is not a strictly mandatory
element of the remote IP worker solution set. It is however highly recommended from a security
point of view to protect the IP Office from external hacking attempts and Denial of Services
attacks.
When the decision is made to include an SBC as part of an IP Office SIP implementation, the
following considerations must be taken into account
 For SIP trunking: ASBCE or 3rd party SBC can be selected and used – as an important
differentiator, ASBCE certifications with over 60 Internet Telephony Service Providers do
guarantee smooth and painless implementation with any of these ITSPs.
 For remote worker: Remote worker capabilities for SIP endpoints, such as Equinox, AC
Windows, as well as Avaya J129 SIP phone are supported with 3rd party SBCs and
ASBCE R8.0. Remote worker capabilities with any of the J139/169/179 phones require
the ASBCE R8.0.
 Regardless the SBC selected, encryption is strongly recommended (except in countries
where it is not allowed-see encryption licenses) when implementing Remote Worker.
 For any other use case, when ASBCE is present in the solution, any other ASBCE
engineering rules are the same whether in front of IP Office or Aura.
Cloud Deployments
Due to its performance, feature richness and advanced integrations with other components of
the Avaya portfolio (Equinox, Avaya Media Gateway, Session Manager etc.) or solution
(AEMO), ASBCE is the de facto, fully tested and supported ASBCE in all XCaaS offers.
It is also the Avaya recommended ASBCE for the Powered By IP Office offer addressing the
mid-market needs. The ASBCE is only available under a CAPEX model with the Powered By
offer at this stage and is under controlled introduction for the OPEX model – reach out to ASBCE
Product Management for further information on the ASBCE OPEX controlled introduction with
Powered By.
Multi-Tenancy functionality supports multiple customer entities (up to 250) in a single ASBCE
instance and is extensively leveraged by IP Office Powered By partners – Refer to Powered By
offer definition and ASBCE administration guide to learn more about Multi-tenancy setup and
limitations as well as the Multi-tenant setup guide newly released in the documentation library of
ASBCE release 8.0.
Virtualization support for VMWare, KVM and AWS expands deployment flexibility in the Cloud
offers. Besides support for vSphere 6.0 and 6.5, Release 8.0 introduces support for deployment
into vSphere 6.7 environments
The software packages available for these environments are specific for each environment and
are available and tracked under separate material codes.
Advanced Networking support features for VLAN, Load Balancing, Geo-redundancy; Multiple
interfaces/subnets all add robustness and expand the breadth of this type of deployment.

Please refer to the respective ASBCE deployment guides (VE, KVM and AWS) for more details.

Computing and Server Requirements

IP Office / Midmarket
The Hardware appliance offering for Mid-market/IP Office is more limited than the enterprise
selection to align with the lower scalability required by this market. Only hardware appliances
supporting Small site and Mid-range capacities (up to 6000 sessions) are orderable for IP
Office/IPOSS implementations. Hi-Cap appliance and Hi-Cap with accelerator are not available
for the Mid-market/IPO segment thru IPOSS.
Specification Low Range ASBCE Mid-Range ASBCE
Portwell Dell
Product Type ASBCE CORE/EMS ASBCE CORE/EMS
Part Number 388052/388053 388048/388049
Platform Type CAD-0230-4611 PE R330 (CSR3 OEM)
Life Cycle 36 months 18 months
BIOS R1.01 (Avaya only) TBA
Processor ATOM C2358 – 1.7GHz Xeon E3-1220 v5- 3.0 GHz (4 cores - 80W)
Memory 2GB DDR3L 1333MHz SODIMM 8GB (2X 4GB) DDR4 2133MT/s ECC UDIMM
RAID No RAID 1
Hard Drives 500GB (SATA) 2 X 300GB 10K (SAS)
Optical Drive - DVD+/-RW
Compact Flash - No
PCIe Cards - Quad 1GbE Port NIC PCIe-4 (Intel 1350 QP)
TPM No No
LCD/LED Display No Yes
Interfaces (Ports)
Data 6 X 1GbE 6 X 1GbE
USB 2 5 (2 front,2 rear, 1 intrl)
Console 1 (RJ-45) Cable included 1 (DB 9 - Male)
VGA No Yes
Replaceable Fan No Yes
Replaceable Hard Drive No Yes
Redundant PSU No Yes (350W)
Port Bypass No No
Management N/A N/A
Form Factor 1U (Desk or Rack Mount) 1U
Bezel - No
Dimensions
Height 1.7 in (43mm) 1.7 in
Width 8.27 in (210mm) 17.1 in
Depth 8.27 in (210mm) 24 in
Boxed
Height 7.5 in 10.5 in
Width 12 in 24 in
Depth 15 in 35.5 in
Weight
Unit 3 lbs. 25 lbs.
Boxed 6 lbs. 48 lbs.
Power
Input 100/240V AC Adaptor (12V DC) 100-240V AC 50/60Hz
Nominal Current (110V) 0.2 A 1.36A
Maximum Current (110V) 0.5 A 2A
AC Power (Max) 40 W atts 300 W atts
Calculated Power Consumption 22W/75BTU 150W/512BTU
Environmental
Nominal Operating Temp 20°C 20°C
Operating Temp Range 5°C ~ 40°C 10°C ~ 35°C
Relative Humidity (Non 20% ~ 90% 20% ~ 80%
Condensing)
Storage Temp 0°C ~ 75°C -40°C ~ 65°C
Certifications & Compliances FCC, CE, UL & RoHS FCC, CE, CSA, UL & RoHS

Virtualization Resource Profiles

Summary Table for Resource Profile and capacity
The following OVAs are the only Virtual appliance footprint supported in R8.0 for the ASBCE.
This is the footprint whose capacities and performances are previously described.
Application vCPU CPU Memory Hard Min NICs
Name reservation (GB) disk Clock
(MHz) (GB) speed
(MHz)3
ASBCE 4 9600 8 160 2200 6
Software
EMS 3 7200 8 160 2200 2
Software
Changing the OVA sizing is not supported for a SIP (trunk or Remote workers) deployment,
especially as this footprint has been designed and tested to deliver optimal capacities for the
compute and memory consumed on a set version of hypervisor (vSphere 6.7).
Additional testing with increased footprints has shown no performances in the number of SIP
session processed. The performance limitation originates from the hypervisor layer and its
ability to process network packets fast.
Note: As of Release 8.0, the OVA footprint can be adjusted (see feature set for 8.0 in this
section ) to support higher scale and density only when WebRTC traffic and Equinox web client
are being used with the Equinox solution. Please refer to the Equinox solution offer definition for
more details
For more information about deploying in virtual environment, see:
https://downloads.avaya.com/css/P8/documents/101040286
Supported Hypervisors for Virtualized environment

ASBCE 8.0 can be deployed as a Virtual appliance within a virtualized environment. Either the
entire ASBCE (EMS + core) or just the EMS can be deployed as virtual machine.
 Licensing and licensing models are the same for Virtual implementations as in
appliance-oriented models.
 Deployment configurations, i.e. SA vs HA models are similar with due diligence
required for IP addressing and placement on the physical hosts supporting the virtual
environment
 Virtual implementation is supported in both Enterprise and Mid-market
Note: Capacities for the Virtual Machine differ from the ones provided by the Avaya ASBCE
appliances in which the software runs bare-metal.
Virtualization is a ‘platform’ choice since there is no “better “implementation when comparing
virtual vs hardware appliance.
As of ASBCE Release 8.0, the following hypervisors can be leveraged to deploy the ASBCE
Virtual Appliance:
 VMWare vSphere
 KVM and in particular KVM that is RHEV based on RedHat Releases 7.x and above
 Nutanix AHV. (KVM base Nutanix hypervisor)
Note: KVM environments based on CentOS are not supported for production environments
The ASBCE solution can also be deployed in Amazon Web Services (AWS) IaaS.

VMWare vSphere
The following versions of VMware vSphere are supported with the ASBCE 8.0.
VMware ESXi ASBCE 8.0
VMware ESXi 5.0 No
VMware ESXi 5.1 No
VMware ESXi 5.5 N
VMware ESXi 6.0 √
VMware ESXi 6.5 √
VMware ESXi 6.7 √
Note: ESXi 5.0, 5.1 and 5.5 are no longer supported by ASBCE Release 8.0 due to the
evolution of the virtual hardware version of the OVA necessary to address performances
challenges created by Meltdown/Spectre fixes.
KVM
Any KVM based on Linux kernel 3.10 and above is supported.
Nutanix AHV
ASBCE R8.0was tested against Acropolis hypervisor (aka AHV or Nutanix own hypervisor)
version 5.1 is supported (AOS 5.1.1.2 which was used for the testing).
Nutanix appliances (i.e. hardware appliances) when running VMWare are and have been
supported as part the standard Virtualized environment offer as these appliances are certified
hardware with/by VMWare vSphere.
AWS
ASBCE R8.0 can be deployed on the current version of Amazon Web Service IaaS. The only
restriction in this environment is that SBCE HA is not supported when deployed in AWS.
Supported Browsers
Avaya SBCE supports following browsers for accessing EMS:
 Microsoft Internet Explorer 11.0 or later
 Microsoft Edge 20.0 or later
 Mozilla Firefox 60.0/ 60.0 ESR or later
 Google Chrome 59.0 or later
 Apple Safari (4) 9.0 or later
Avaya SBCE supports following browsers for deploying OVA:
 Microsoft Edge
 Mozilla Firefox version 60.0 and later
 Apple Safari (4) 9.0 or later

Supported VPN-less SIP Remote Worker Endpoints

When deploying VPN-less SIP Remote Workers there are specific end points to be considered.
Supported Endpoints
- Avaya Equinox client
- Avaya Communicator for Windows
- Avaya Communicator for iPad
- one-X® Mobile Preferred for IP Office for iPhone
- one-X® Mobile Preferred for IP Office for Android
- MS Lync Add-in
- E.129 sets
- J129
- J139/J169/J179 In the IP Office Branch deployments only phone types that are capable
of being Centralized endpoints are supported with ASBCE deployments
- 11xx/12xx SIP sets
- Vantage devices
Excluded Endpoints
- B179 conference unit
- E159, E169
- Avaya Scopia video endpoints (XT room systems and Elite MCU systems)
- Mac Video Softphone
- DECT D100

Sizing, Licensing, and Quoting

Solution Capacities and Performance
ASBCE 8.0 system is measured for capacity purposes in a session-driven capacity model, i.e.
capacity is rated in terms of maximum simultaneous sessions supported. The following table
states maximum SIP session capacity.
Solution capacities quick reference
For new and current hardware:
SIPREC
Remote Internal External
Non- with SIP Scopia
Appliance Encrypted Worker AAMS AAMS
Encrypted trunking Video Reverse Proxy
Model Sessions Users Transcoding Transcoding
Sessions replicated Sessions
(Sessions) Sessions Sessions
Sessions
500 HTTP
Requests
/sec.
50 TLS
5,000
Dell R330 6,000 2,000 3,000 200 300 1,250 connections
(2,000)
/sec
2000
Mid-range
concurrent
webSockets
Virtual
6,000 Same as
Appliance 5,000 3,000 2,500 200 100 1,250
(3,000) above
VMW
Nutanix
AHV on 6,000
5,000 3,000 2,500 200 100 1,250
Nutanix (3,000)
Appliance
Virtual
Appliance Same as
1500 500 500 N/A N/A 100 1,250
above
Low Range
KVM
Portwell 500 Same as

600 500 N/A N/A N/A N/A
CAD0230 (500) above
All of the capacities numbers listed above are achieved when Spectre & Meltdown fixes are
enabled.
If pre Spectre & Meltdown maximum performance is required for the Hi-Cap and Hi-Cap with
accelerator, Spectre/Meltdown fixes can be disabled to meet the original supported
performance. More details can be obtained procedure for disabling Spectre/Meltdown fix
sections in the PSN reference PSN005227u located on the Avaya Support portal.
For Mid-range and Low Range capacity is measured with Presence, having 25 contacts per
user. Increased.
The capacity specifications are based on:
 Codec specification: The G729 and G711 Codecs are used for measuring transcoded
capacities. Different codecs will have varying results.
 Call Model: The SIP RFC call model in trunk mode is used to establish these capacity
specifications.

VMware 6.x capacities are measured with the currently available Virtual Appliance OVA for
ASBCE whose footprint is described in the Virtualization resource profile section of this
document. KVM and AHV on Nutanix Hardware capacities varies from the ones available on
VMWare due to drivers’ efficiencies – please refer to the table above for the actual capacity
numbers.
Note 1: – Transcoding capacity:

 Onboard AMS Transcoding measurement for low-end hardware is measured with no
additional traffic
 Transcoding capacity is measured with G729 & G711 Codecs. Different codecs will
have varying results
 External AMS - Transcoding Capacity is measured with no additional SIP Trunk
Sessions.
 For external AMS specs, please refer to AMS documentation
Note 2: SIPREC, Scopia video and Transcoding are not supported with the Portwell appliance
due its limited computing capabilities.
Note 3: To calculate Busy Hour Call Completion (BHCC) performances, multiply the maximum
concurrent sessions by 20
PLDS Licensing
For the 8.x releases of the ASBCE, it is required to download new license files and have access
to a WebLM server. The license files must be placed on the WebLM server and the ASBCE
application must be able to access that server. The ASBCE will limit the implementation if you
have not downloaded the proper files:
 Standard License (with optional HA)
 Advanced License (with optional HA)
 CES License
 Encryption License
 Signaling only encryption license
 Transcoding License
 Scopia Video License
 Dynamic Licenses (not supported by IPOSS)
Product License Distribution System (PLDS) is the Avaya tool for managing and distributing
software product license files for Avaya applications. Avaya SBCE 8.0 leverages this tool for the
license management and also software distribution capabilities of the tool, and this usage
applies to both Enterprise/Aura and IP Office systems.
Per the Installation Guide, the license file is downloaded from PLDS and inserted in to WebLM
during the installation process. PLDS access is required for the Partner to activate and retrieve
the license file. PLDS is used for both Enterprise/Aura implementations and also IP Office
implementations.
The Avaya Product Licensing and Delivery System (Avaya PLDS) is a web based solution
located at plds.avaya.com. PLDS allows Partners, Distributors, Customers and Avaya
Associates to manage and maintain software and its corresponding licenses and support.

Licensing Control
The Avaya SBCE requires a WebLM server for licensing controls. The constructs supported are
as follows:
ASBCE System Manager Co-resident WebLM on the

Implementation VM Based WebLM WebLM SBCE
ASBCE and EMS Yes Yes Yes
ASBCE Virtual Yes Yes No
EMS Appliance Yes Yes Yes
EMS Virtual Yes Yes No
Aligned and essentially the same as for Enterprise, Avaya Session Border Controller for
Enterprise 8.x for IP Office is a single software product that can serve a number of application
needs for SIP-based communications in the SME market. The software is delivered, with our
Business Partners in mind, pre-loaded on the hardware platform, on a Thumb Drive or disk for
physical media, and, aligning with other Avaya applications, via PLDS.
Quoting
The offer for AVAYA SBCE 8.0 with IP Office 11.0/10.1 is quotable via Avaya One Source (A1S)
in the One Source Configurator to align with ordering of the IP Office 11.0 and 10.1 solutions.
This significantly simplifies quoting and ordering for the IP Office Distributor and partner when a
SBCE solution for IP Office 10.1 or higher is required.
The offer mechanics in ASD (specifically for the IP Office implementations) are simple
 The customer orders either an ‘all SIP trunking’ option, or orders SIP trunk licenses for
their IP Office to use SIP trunking
 The tool then ‘pops’ an extension to the menu that shows the AVAYA SBCE 8.0 as
‘selected’, with an option to manually de-select the SBC. The second part of this menu
extension allows inputting a desired number of SBCE Advanced Services sessions with
IP Office 11.0/10.1.
 If the customer chooses an IPOSS offer for the IP Office 11.0/10.1 solution, the
associated IPOSS offer for the AVAYA SBCE 8.0 is also quoted
 Quoting of the IPOSS for AVAYA SBCE reflects either the Portwell or the Dell
R330 and, if HA, three-server configurations for the R330 HA pair + the EMS
R330 server (Portwell does not support an HA option)
 The IPOSS quote output will show the added server (s)
Orders for IP Office solutions by Partners for end customers are all placed with Distribution.
Distribution facilitates the product ordering process for Partners and use EDI tools for ordering
to Avaya for the solution. Distributors often have their own ‘home-grown’ tools for quoting
purposes but those tools do not always contain the complete Midmarket Solution; so you can
also use Avaya tools.
It is noted here that ACSS certification on the AVAYA SBCE product is required to perform
installation and service for the product. Avaya Professional Services (APS) can perform the
AVAYA SBCE product installation for a partner that does not yet have this certification. APS
services are ordered via the PRM process for Avaya Business Partners. For this offer, APS
services are oriented to installing the AVAYA SBCE product itself, it is assumed the Business

Partner is certified to perform all services for the IP Office or will order those appropriately from
APS as needed.
Services and Support

Warranty
Avaya provides a one-year limited warranty on hardware and 90 days on ASBCE’s software.
Refer to the sales agreement or other applicable documentation to establish the terms of the
limited warranty. In addition, Avaya’s standard warranty language as well as details regarding
support, while under warranty, is available through the web site: http://support.avaya.com/ or on
the Enterprise Portal at
https://enterpriseportal.avaya.com/ptlWeb/gs/services/SV0452/JobAidsTools.
Support Services Offer

When deployed with an IP Office the SBCE is covered by the IPOSS (IP Office Support
Services) maintenance offer. Refer to the Avaya Midmarket Solution Support Services Offers
Product Information Document for additional information on the IPOSS offer.

Resources
Listed below are some of the many resources available to help support sales of Avaya Session
Border Controller for Enterprise. Although the documents listed below are available through the
Sales & Partner Portal and support.avaya.com, we have made it easier to obtain some specific
documents by listing them separately with a direct link.
Web Sites
Sales & Partner Portal – Avaya Session Border Controller for Enterprise Page
Sales & Partner Portal – IP Office Support Services (IPOSS) Page
Sales & Partner Portal – Product Licensing Delivery System (PLDS) Page
support.avaya.com - Avaya Session Border Controller for Enterprise page
Documents
Avaya Session Border Controller for Enterprise Offer Definition
Avaya One Source Cloud Job Aid
IPOSS Offer Definition
Guidelines for Securing IP Office

16-20190307040627-37200W PID 07 SBCE 8 - 0 Final

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

16-20190307040627-37200W PID 07 SBCE 8 - 0 Final

Uploaded by

Copyright:

Available Formats

Avaya Midmarket Solution

Product Information Document –

© 2019 Avaya Inc. All rights reserved. Page 1

© 2019 Avaya Inc. All rights reserved. Page 2

© 2019 Avaya Inc. All rights reserved. Page 3

Introduction to the Avaya Midmarket Solution

© 2019 Avaya Inc. All rights reserved. Page 4

Introduction to Avaya SBCE R8.0

© 2019 Avaya Inc. All rights reserved. Page 5

© 2019 Avaya Inc. All rights reserved. Page 6

ASBCE 8.0 Feature Descriptions

Simplification of the ASBCE user experience

Simplified and Improved Backup & Restore [8.0]

© 2019 Avaya Inc. All rights reserved. Page 7

To facilitate hardware replacement or pre-staging, a Technician or administrator can now take

More robust and seamless upgrade [8.0]

CLI introduction for Improved pre-staging /system prepping [8.0]

Simplified Certificate Management [8.0]

© 2019 Avaya Inc. All rights reserved. Page 8

Non-intrusive Multi tenancy setup thru on the fly configurations changes

Removal of Volume Tiered pricing for a simpler ordering experience [8.0]

Bundling of ASBCE software and Hardware for small to very small

© 2019 Avaya Inc. All rights reserved. Page 9

SNMP alarming when ASBCE is nearing session saturation

Better Together with Equinox

MSFT Edge Browser support for WebRTC communications [8.0]

Http Tunneling through Proxy SSL inspection mode [8.0]

Opening Up the SBCE architecture to ecosystem

© 2019 Avaya Inc. All rights reserved. Page 10

- Help with automatic and free access to Avaya Learning

Allowing ASBCE core routing decision engine connection to external data

Linking SBCE Help to Avaya learning Administrator training [8.0]

Technology Currency & Security

Avaya Security Common Engineering Criteria compliance

Remote Workers MAC based authentication [8.0]

© 2019 Avaya Inc. All rights reserved. Page 11

ACP Hardware appliances [8.0]

Feature IP Office Avaya SBCE

Business Partner Value Proposition

© 2019 Avaya Inc. All rights reserved. Page 12

operations post-merger/acquisition. Perhaps not surprisingly, the financial sector

© 2019 Avaya Inc. All rights reserved. Page 13

Avaya SBCE Midmarket Use Cases

© 2019 Avaya Inc. All rights reserved. Page 14

Avaya Call Servers

© 2019 Avaya Inc. All rights reserved. Page 15

Interoperability with 3rd Parties

3rd parties Call Server

© 2019 Avaya Inc. All rights reserved. Page 16

Internet Telephony Server Providers

3rd parties SIP endpoints

© 2019 Avaya Inc. All rights reserved. Page 17

© 2019 Avaya Inc. All rights reserved. Page 18

© 2019 Avaya Inc. All rights reserved. Page 19

High Availability License

Additional License (“a la carte” licenses)

© 2019 Avaya Inc. All rights reserved. Page 20

Client Enablement Service (CES) Inspection license

Signaling only Encryption license

Scopia Video Service license

© 2019 Avaya Inc. All rights reserved. Page 21

VMW deployment license

KVM deployment license